The SAP implementation, delivery and methodology approach for the SAP BA/ IA Analyser techniques to achieve the IFRS Regulatory reporting using SA(FSPL) with HANA

SAP techniques applicable at a basic level on sap package / component solution customization –I call this Vision of Finance Transformation From daily routine to supporting growth and new business models

 Not applicable for the  SAP upgrade but to the new/ greenfield implements new SAP Bank analyser, or insurance analyser - on HANA, (FSPL).  The three keys to be successful -IFRS 9 and IFRS 17 implementation. How the SAP Activate approach (HANA with Solution Manager) Delivery approach can help in Close alignment of all project streams. See Diagrem below.. 

 There are many Opportunities for alignment between both (IFRS9 and IFRs17) implementations can be identified in the early project phases starting from the FIT Gap analyses, the Analyse and classify instrument and contracts affected by both standards to Full end to end testing. Pease contact me for any consultation requirement, or formal engagement to provide lesson learned...  

·     How to Address organizational responsibilities aligning actuaries, risk, finance, ALM and accounting etc (Worksop, Q&A, Show and tell session etc)

·         How to Identify shared risk and actuarial data and Conduct parallel analyse (SDL, DDL) and RDL, testing and pilot phases for increased efficiency (POC of FSPL business contents using KDV, and other valuation run)

2) Harmonized data collection inside the FSPL (SDL using reuse of Business partner)

Designing a harmonized data management strategy an efficient and reliable outputs, which can be achieved for the harmonization of IFRS 9 and IFRS 17 requirements (single version of truth)        

A profitable ALM strategy to implement using agile integrated transformation approach is our proved methodology in an integrated transformation approach for IFRS 17 and IFRS 9 provides multiple benefits and allows raising synergies (expert consultancy around):

·         Early identification and mitigation of dependency risks (business model review – e.g. FVOC- SPL)

·         Quick responsibility clarification (actuarial, risk, accounting department) of the existing risk models

·         Consistent accounting principle interpretations against the business model

·         Avoidance of Accounting mismatches

·         Easier Golden Source identification and data harmonization

·         Consistent auditor approvals

2) Harmonized data collection inside the FSPL (SDL using reuse of Business partner)

AS IS - disintegrate, too many small systems , no harmonisation of data... too risky to manage change,, 

TO BE 

SAPs IFRS17 Subledger, Data Management and Finance and Risk Calculation Engines. the S4HANA FSPL -Clint can choose a single-instance installation (one software stack) or a dual instance installation (two software stacks) as illustrated below. In a single-instance deployment, you deploy the back-end and front-end together, whereas in a dual instance installation, you deploy them separately.

 The IT architecture and infrastructure harmonization for valuations and CSM calculations using SAP HANA, BW/BI – and FPSL add on and Joint source for market and valuation data, such as interest rates and risk assessments on the FSPL//