Tuesday, February 23, 2016

Solvency II and SAP Insurance Analyzer.

Dear,
As you probably know, since January 1st 2016, all the European insurance companies must be compliant with the new Solvency II Directive.

The European Union Solvency II Directive represents a major change in the insurance industry regulation. The Directive's main priorities are increasing the solvency of the Insurance companies and harmonizing the EU regulation, with the final objective of achieving a solvent and single EU insurance market.

From some perspective, the Solvency II regulation represents to the insurance companies what the Basel III and the EU Bank Recovery and Resolution Directive represents to the European banks.

This is a major challenge on the Information Systems of the Insurance companies, just for giving an idea of the complexity of implementing these regulations, we must consider that the final implementation date has been delayed 4 years from the initial proposals. Initially, regulators looked at October of 2012 as the implementation date.

Among many other changes, implementing Solvency II has requested the creation of the European Insurance and Occupational Pensions Authority (EIOPA) that, with more competencies, replaces the Committee of European Insurance and Occupational Pensions Supervisors (CEIOPS).

The Solvency II Directive is structured in three main areas or Principles.
- Pillar 1 establishes the quantitative models which must prove that the insurance company has the capacity to fulfill its obligations, like determining the capital requirements.
- Pillar 2 sets out requirements for the governance and risk management framework that identify and measure the risk to which the insurance company is exposed, and the supervision model.
- Pillar 3 focuses on disclosure and reporting of the company risk exposures and capital requirements.

Additionally, Insurance companies must also be compliant with the IFRS standards, particularly IFRS 9 for Financial Instruments.

For helping insurance companies to meet with these regulations, SAP has delivered the Insurance Analyzer System.

https://help.sap.com/insurance-fsia

Technically the Insurance Analyzer system is an evolution of the Bank Analyzer system, it's also built following the principles of the Integrated Financial and Risk Architecture, providing the full potentiality of the Financial Database.

As Bank Analyzer, the Insurance Analyzer System provides two groups of functionalities or modules.
- SAP Accounting for Insurance Contracts, equivalent to the Accounting for Financial Instruments module of Bank Analyzer.
- Solvency Management for Insurers, equivalent to the Credit Risk Analyzer (Basel III) module of Bank Analyzer.

And as in Bank Analyzer, the Insurance Analyzer System is also structured in 4 Layers.
- Source Data Layer.
- Processes and Methods Layer.
- Results Data Layer.
- Analytical Layer

The final objective of this 4 Layer Architecture is providing a single source of truth for Accounting, Risk and Liquidity Information

As it happens with the banks, in which sophisticated reporting tools have to coexist with non-integrated, heterogeneous operational systems, often supported by manual processes and non-integrated spreadsheets, it's going to take years before the insurance companies are fully compliant with the Data Governance requirements of the new regulation.

During this transition, the Data Governance capabilities of the 4 Layers, Integrated Financial and Risk Architecture of Insurance Analyzer will be a great help.

On the Source Data Layer, we can integrate all the data, provided by heterogeneous legacy systems, in an homogeneous Data-model of Master, Operational and Market Data.
For Instance.- Many insurance companies lack on an integrated vision of their customers data. Customers data is spread among legacy systems with very limited integration with each other, which is a root cause for undetectable fraud and inaccurate risk management.

With Insurance Analyzer, the insurer company can integrate in the Source Data Layer all these divergent versions of their Customer data in a single and integrated repository, building the foundation for customer-centric analysis of profitability and risk management.

Transforming the whole landscape of an Insurance company will represent an enormous effort of systems migration that will require much of the company resources. Without the integrated risk & accounting vision of Insurance Analyzer, it's not possible to align the IT strategy on the direction of the new requirements of Solvency II and IFRS 9, which are going to be the main concern for the IT executives of the industry in the oncoming years.

At the end, the stability of the insurance industry is not just a European issue, the global industry is facing major challenges, as it moves to a model driven by efficient management of Capital, and very sensitive to risk management.

Join the SAP Banking Group at: http://www.linkedin.com/e/gis/92860

Looking forward to read your opinions.
K. Regards,
Ferran.

Wednesday, February 3, 2016

Fulfilling IFRS-9 and IFRS-15 Sub-ledger requirements with SAP Bank Analyzer.

Dear,
One of the main concerns of the banks' IT executives today is the implementation of the International Accounting Standard IFRS 9 Standard, “Financial Instruments”

Impairment Calculations, Fair Value and Hedge Accounting adjustments represent a challenge for current Banking Information Systems and an opportunity to replace some of their components with modern technologies, like the Accounting for Financial Instruments module of SAP Bank Analyzer.

SAP Bank Analyzer covers the three main groups of calculation requirements of the IFRS-9 standard.

- Fair Value calculation of Over the Counter, Securities and Listed Derivatives contracts.- Financial Instruments and Financial Transactions. (Mark-to-Market, Cash Flow Discounting, Forward Transactions, Options, Futures and Structured Products).

- Impairment Adjustments.- Calculation of the Risk Provisions, write-down, write-off and the unwinding with full integration with Accounting.

- Hedge Accounting Adjustments for Fair Value, Cash-Flow and Portfolio Fair Value Hedging.

On the other hand, there's a common difficulty on understanding the implications of the IFRS requirements; many clients see IFRS 9 just as a reporting requirement that must be fulfilled before January 2018.

But limiting an IFRS compliance program to the IFRS 9 requirements is an incomplete vision of the implications of the new IFRS Regulatory framework. IFRS requirements must be seen as a transformation process, and not as unconnected pieces of regulation.

An interesting example of the above is the Accounting Standard IFRS 15 “Revenue from Contracts with Customers”.

IFRS 15 puts the focus in the Revenue Recognition of the customer contracts individually. While this standard has not been specifically designed for banks, underestimating the impact of the “Revenue from Contracts with Customers” in the bank's architecture would be a serious mistake.

Banks have to disclosue the revenues generated when they charge their customers for the services they're receiving; services like securities broking, wire transfers, accounts maintenance fees, etc. Accounting adjustments must be allocated to every customer contract, challenging portfolio-based adjustments, which are very common in the banking industry.

Bank Analyzer AFI (subledger scenario) provides a complete Financial Statement (Profit & Loss, Balance Sheet and Off-balance positions) per customer contract, and fully reconcilable with the General Ledger. This is the main requirement of IFRS 15.

By implementing the AFI module of SAP Bank Analyzer, we're not only fulfilling the accounting requirements of IFRS 9, but also preparing our system for the future requirements of IFRS 15.

We also must remember that Inefficient integration between the Operational and Analytical Systems limits the capacity of providing reporting Profit and Loss analysis functionalities on contract level.

Current Banking Information Systems, supported by Legacy systems suffer from inefficient integration between the Operational and Accounting Systems. Even some banks which have replaced some of their Information Systems in the last years have failed in improving the integration between their Operational and Analytical-Accounting Information Systems.

Typically, Operational and Analytical banking Systems come from different vendors with heterogeneous data-models, in which the incompatibilities between the data-models must be overcome with “reasonable” hypothesis developed as conversion routines in the Extraction and Transformation Layer.

In this scenario contract-base valuations and adjustments are usually replaced by portfolio-based adjustments which contradicts the requirements of IFRS 15.

SAP Banking has provided a seamless integration between the Operational and Analytical Banking components of Banking Services by using Integration Operational Analytics technology, this is the base for transferring all the necessary information to the Accounting System, according to the IFRS requirements.

As a conclusion, Financial institutions need to look at the IFRS requirements as a process; while IFRS 9 are increasing the effort on determining the value of the Financial Instruments and the recognitions of the related revenue, IFRS 15 puts the focus in reporting determining the revenue recognition contract by contract.

Join the SAP Banking Group at: http://www.linkedin.com/e/gis/92860

Looking forward to read your opinions.
K. Regards,
Ferran.