Showing posts with label IFRS9 linked to IFRS17. Show all posts
Showing posts with label IFRS9 linked to IFRS17. Show all posts

Saturday, 22 August 2020

How Does the IFRS9 and IFRS17 interact each other and /or does both standard provide valuation for the asset and liability using same principles?

 

IFRS 9 introduced a situation whereby satisfying both criteria, insurers can use the measurement options of amortised cost and the fair value through other comprehensive income (FVOCI).

In the ongoing global economical climate, the volatility situations are impacting the IFRS9 and IFRS17 principles and overall asset and liability management, note the IFRS9 approach that was implemented in 2017/18, in operational need adjustment, provisions in the credit risks model for the valuations precision of expected cash flows.. 

Lets, look my point of views. the IFRS9 classified and measured investment on the assets side of the balance sheet.  This predominantly allowed account for the investment using (at) Fair value on the balance sheet, further more it allowed more dynamic / forward looking views of the impairments of the investments. The impact of the different treatments of changes in assets and liabilities resulting from interest rate movements on the P&L, OCI and Balance Sheet of Insurer. Insurance entities, particularly those who currently hold amortised cost based assets or make use of the Available for Sale category (“AFS”) under IAS 39 will need changes.

In contracts of IFRS9, the IFRS17 cater more on the Liability side of the Balance sheet that will be measured at fulfilment value of insurance contracts by 2022/23. What does that meant, on the insurance contract is that what is promised to end client, the coverage the insurance claim, (obligation of payment made in future (many year), As we know the value of liability changes as a result of impact of changes in interest rate on the discount rate (change goes through OCI).

The challenge coming here when the Interest rate is a quite important factor of volatility, however the Accounting value of asset not affected by interest rate movements is/ being valued (impacted by amortisation/impairment principles) on the balance sheet.The insurance liability (IFRS 17) is closely connected to the financial instruments (IFRS 9) within insurers. When a individual buys an insurance, the insurance liability is created and with the paid premiums is a financial instrument (purchased). the Insurers want to reduce the volatility in earnings hence there are some choices within IFRS 9 and IFRS 17 that can make which impact the volatility. Under IFRS 17 insurers can decide whether results of changing financial risk assumption go through OCI or through the profit and loss account in recognition phase.

In the balance sheet under 17, these payments claim / payments valued according to their time values, essential, discounted current interest rate,

As results P&L will be based on current measurement and will be recognised as insurance provided to customer  ... Not sure in this circumstance, How both contract accounting standard (IFRS9 and IFRS 17) intact each, though both based use the Fair value approach, how come the ‘asset and liability’ on the balance sheet match accounting unless Assumption applied, Provision are allowed. These clearly diminish the criteria / objectives of the regulation.

How both IFRS 9 and IFRS 17 approaches will be able to continue measures asses when there is increase in the  interest rate (consistently affecting the market value of both sides (A&L) balance sheet. 

The IFRS17 is more on Liberality impacts, The Asset side market side value will decrease and the Liability side fulfilment value decreased due to the higher discount rates. isn't insurers must consider the expected impact of this new Insurance Standard, they need to be aware of the interrelationship with the Financial Instruments Standard – IFRS 9 – which impacts the valuation of insurers’ assets for accounting purposes???

As the P&L statements will be impacted due to Covid19, (changing situations), In contrast effects in the balance sheet, the Recognition in the statement P&L is going to be bit tricky,  Under the IFRS9, effective interest rate (long term market fluctuation), such as simple bond for assets were reflected considering all market fluctuation, Now, Let’s look in isolation, the  association if asset classified in  fair value thru the P&L account caused volatility, the P&L treatment under the 17 differ depending upon applicable measurement model’ like General Model (GM), Premium Allocation Approach (PAA) and the  ... Fee Approach (VFA) . This Applies to contracts with direct participation features, as defined by three criteria for the P&L side, based on policyholders sharing in the profit from a clearly identified pool of underlying items.. I see this is CLOSE TO IFRS9 APPROACH....

the market fluctuation, we should look in association to 'Asset F&L, P&L causing the volatility .The P&L treatment in the IFRS17 also differ depending upon the measurement model, Like property causality, non participating Life business the  interest (accretion) in the P&L account will be quite stable as it is based on historical Interest rates, the compounding with the historical interest rates, providing here more stability as no market changes to reflected in the interest rates whilst valuation.

  From system perspective, both standards, the IFRS 9 and IFRS 17 require organisations to ensure data governance, lineage, quality and transparency, integration of data flows across the entire reporting chain. This includes a wide spectrum of data that will be used, from historic or current data (e.g. policy , instruments positions, and premium data or data to produced the risk adjustment etc) to forward-looking views data (e.g. data used to produce cash flow projections in the CRR, probability).

this new Insurance Standards are focusing on insurance liability reporting, MUST have far-reaching consequences for an insurer in terms of modelling, data, processes and IT systems; ultimately resulting in a different statement of OCI comprehensive income and more onerous disclosure requirements

 In conclusion: the Insurance Earnings are a Consequence of both Liability and Asset Movement.

 With IFRS 17 making significant changes to the valuation of liabilities of insurers, Less on assets as being used (current measurement and will be recognised as insurance provided to custome. the  IFRS 9 has made changes to the valuation and income recognition of assets. especially when classification categories have been redefined in IFRS 9 and consideration is being given to whether the entity’s business model is evaluated as one held to collect contractual cash flows, one where the intention is to hold to collect and sell or one where the intention is just sales. 

This assessment, combined with the assessment of the contractual cash flow characteristics were impacted the measurement option available to insurers.

The IFRS 17 introduces a situation where by satisfying both criteria, insurers can use the measurement options of amortised cost or fair value through other comprehensive income (FVOCI). The introduction of the FVOCI category to IFRS 9 was seen as a positive development and represented a significant improvement to the standard, in combination with the use of FVOCI in IFRS 17, for insurance companies. The IFRS9 and IFRS 17 insurance contracts accounting standard considerations for data, systems and processes having similar impact, the Large enterprise in Finance, insurer MUST start looking for an integrated data management, reusable risk assessment model. 

More robotics process systems, The AI and Machine learning model to support business operation and regulatory reporting....





 

 

Saturday, 9 May 2015

IFRS 9: Impairment & Implementation differ to Insurance entities -Interactions between IFRS 9 and IFRS 17..

Anyone interested to join workshop about the Interactions between IFRS 9 and IFRS 17.. 


please ping me also about the comparison of the 'IFRS9 and IFRS17'; white paper. 

With accounts departments generally dealing with historical data and risk functions dealing with forward looking models, questions are being raised as to what overlap there is between current risk management and accounting information and the roles of risk and finance departments in the programmes.
the  IFRS 9 Impairment And IFRS17 CSM Implementation  are bringing together the leading independent experts and financial risk, finance and accounting experts to address the critical challenges, and opportunities, being faced in IFRS 9 and IFRS 19. As the IFRS 17 making changes to the valuation of liabilities, IFRS 9 mainly have had (or will be) impacting the valuation of assets. 
IFRS 9 affects measurement, impairment and hedge accounting of financial instruments.
and the IFRS 17 (principle based approach) evaluates all relevant insurance contracts and introduces a contractual service margin A new KPI form the Balance sheet figures. 
AS we predicted the accounting mismatches aroused from IFRS 9 valuated instruments on the asset side are to be expected to improved, since insurance contracts could have will be included on the financial instruments which are linked to corresponding investments (especially life insurance contracts category).

It made surprised to know that insurers can postpone the original IFRS 9 implementation date (01.01.2018) to the IFRS 17 effective (now revised to 2023, date to cover up the accounting mismatches (deferral approach) upfront.



Wednesday, 12 February 2014

SAP Bank Analyzer Implementation Strategy -High Level Implementation / Overview (High level Process)



 SAP Bank Analyzer –

This article will explain best approach and Implementation approach for the SAP Bank Analyzer solutions, upgrade or integration. Recently I've had opportunity to work on two demo solutions for a banking system SAP Bank analyzer implementation within risk and profit analyses team and a short term test strategy development for rapid SAP bank analyzer implementation within an investment bank.

This article will explain best approach to implement SAP Bank Analyzer solution 8.0 or  upgrade from or integration. Recently we worked on two demo solutions for a banking risk system SAP Bank analyzer implementation within risk and profit analyses team and a short term test strategy development for rapid SAP bank analyzer implementation within an investment bank.


In next couple of blogs we will detail an effective way to test SAP Bank analyzer and its individual components.

 - SAP BA - Objectives in upgrade and in new Implementation Solution Architecture to  future looking business Architecture      
      

As IS Approach- There could be two scenarios either – Accounting IFRS implementation or risk architecture – see below diagram for both .. the Accounting IFRS implementation (accounting consequence, FSPL scenarios)



B) Risk architecture scenario



 
Transformation, and loading process (ETL process).  The SDL saves, consolidates, and manages the original data. At the same time it provides interfaces to additional operational systems.
The primary objects of the Source Data Layer (SDL) and their scenario versions are a flexible way of saving master data, flow data, and market data. They also group this data into units that belong together logically from a business perspective. This ensures that the Bank Analyzer components that are linked to the SDL have a standard, consistent data source.In addition to storing primary object data, the SDL provides the following primary objects functions for applications linked to it:
 See SDN for more detail

●     Access to source data
●     General functions for source data layer
●     Methods for source data
●     General access to corrections
●     Tools
 
Integration
The SDL provides both the central original data basis and a part of the underlying infrastructure for linked applications. It is therefore a key element in ensuring the consistency of data and results.
 <To be updated soon) - if you need detail document, please email your request

 Category 1 - Business transactions

  • Post external business transactions
  • Update secondary business Transactions

Category 2 - Date valuation
 
  • Key date valuation for all financial positions
  • Financial Positions for Period (PICC) event processing etc
  • Update costing for period before GL and during transferring GL documents
  • Calculation for all PICC
  • Balance carry forward etc..  Create FT and BT, Period Open( Previous year),Set the posting date,register contract, Open new fiscal and End-of -day processing before you click on Execute BCF

Category 3 – SAP GL Postings

  • GL Connector and document generation – Journal and document review and finance reconciliation of the GL, Profit centre and any material code posting review
  • Balance processing step 1 - (SV)
  • Balance processing step 2 - (ATP)

Testing of the accounting for FI with Aggregation (AFI) for Accounts Results before RDL and GL
Category 1 – position management
  • Generate Finance Instruments position
  • Aggregate Financial Transactions
  • Prepare Business Transactions for Aggregation
  • Process Reassignments for Business Transactions
  • Aggregate Business Transactions
  • Aggregate Current Accrual Results
  • Process Reassignments for Accrual results
  • Aggregate Retroactive
  • Accrual Results
  • Derive Application Events for source data aggregation

Imported Sub-Ledger Documents (ISD) for Results
 ISD sub-ledger import
- Please email if you need full info ....
 




 

SAP S/4HANA -Financial Services for Intelligent Enterprise - IFRS

About Us- SAP TAO Ltd - IT Consulting & Services

 SAP TAO Ltd - IT Consulting & Services SAP TAO is a specialist provider of SAP and Non SAP software development and SAP Enterprise int...