IFRS standards are not an isolated concern for accounting leadership. They dictate the very structure of your chart of accounts, the granularity of your journal entries, and the reporting architecture of your ERP. Since IFRS 16 took effect in 2019 and IFRS 17 in 2023, European listed groups have faced a precise operational challenge: running local GAAP and international standards in parallel within a single information system.
This guide explains concretely how to configure your ERP to meet these two standards, which modules to activate in SAP, Oracle, and Microsoft, and how to organize dual reporting without extending your monthly close.
Why IFRS Standards Directly Impact Your ERP
The Dual Reporting Requirement
Dual reporting means producing financial statements that simultaneously comply with local standards — UK GAAP, HGB in Germany, PCG in France — and IFRS for group consolidation. This means each accounting entry may be treated differently depending on the applicable framework.
In the ERP, this requirement translates into parallel ledgers, mapped charts of accounts, and distinct valuation rules. Without a dedicated architecture, finance teams multiply manual spreadsheet adjustments — a source of errors and close delays.
Who Is Affected
The obligation to publish under IFRS applies to approximately 7,000 listed companies in the European Union (EC Regulation 1606/2002). But the real scope is much broader: any subsidiary of a listed group must report IFRS data, even if it maintains its statutory accounts under local GAAP. Companies preparing for an IPO or fundraising round must also plan for compliance, typically 18 to 24 months in advance.
IFRS 16: Accounting for Lease Contracts in the ERP
What IFRS 16 Changes
Before IFRS 16, most operating leases remained off-balance sheet. Since 1 January 2019, lessees must recognize on the balance sheet a right-of-use asset and a lease liability for virtually all contracts lasting more than 12 months or of significant value.
The impact on financial ratios is substantial. According to the impact analysis published by the IASB, liabilities for companies in transport, distribution, and telecommunications increased by more than 20% on average following adoption. Net debt ratios deteriorate mechanically, while EBITDA improves as lease charges become depreciation and interest.
Impact on ERP Modules
IFRS 16 touches several modules simultaneously:
- Fixed assets: creation of a right-of-use asset with a depreciation schedule aligned to the lease term
- Treasury: splitting payments between principal repayment and interest expense (actuarial model)
- General ledger: initial recognition entries, monthly depreciation, debt unwinding
- Reporting: dedicated disclosures (commitment schedule, sensitivities)
How SAP, Oracle, and Dynamics Handle IFRS 16
SAP S/4HANA offers two approaches. The RE-FX (Flexible Real Estate Management) module handles property lease accounting with direct FI/CO integration. For non-property contracts (vehicles, IT equipment), SAP Contract and Lease Management (CLM) provides broader coverage. Both support parallel ledgers via distinct valuation areas — for example HGB and IFRS on the same contract.
Oracle Fusion Cloud includes a native Lease Accounting module that automatically classifies leases as finance or operating, calculates present value through a built-in amortization engine, and posts entries to the General Ledger. Integration with Oracle Assets and Payables is native.
Microsoft Dynamics 365 Finance embeds an Asset Leasing module that supports IFRS 16 and ASC 842 simultaneously. The dual reporting feature allows multiple books on the same contract, each with its own classification and depreciation rules.
Common Implementation Pitfalls
Four situations generate the majority of implementation difficulties:
- Foreign-currency leases: the lease liability must be remeasured at each closing date at the spot rate, creating foreign exchange differences that must be isolated
- Lease modifications: any amendment — extension, space reduction, rent indexation — triggers a full recalculation of the right-of-use asset and liability
- Subleases: an intermediate lessor must treat the sublease under IFRS 16 as a receivable asset while maintaining the head lease as a liability
- Exemptions: short-term leases (under 12 months) and low-value leases (under USD 5,000) may remain as expenses, but the low-value threshold requires explicit configuration in the ERP
IFRS 17: Insurance Contracts in the ERP
What IFRS 17 Changes
IFRS 17, effective 1 January 2023, replaces IFRS 4 and introduces a radically different measurement model for insurance contracts. Three measurement approaches coexist:
- BBA (Building Block Approach): the general model for long-term contracts, with a contractual service margin (CSM) amortized over the coverage period
- PAA (Premium Allocation Approach): a simplified model for short-duration contracts (coverage of less than 12 months)
- VFA (Variable Fee Approach): dedicated to contracts with direct participation features (unit-linked life insurance)
The actuarial complexity far exceeds traditional accounting standards: it requires probabilistic future cash flows, discount rates by contract cohort, and isolation of the financial component from the service component.
Why Standard ERPs Do Not Handle IFRS 17 Natively
General-purpose ERPs (SAP, Oracle, Dynamics) are built for standard enterprise accounting. IFRS 17 requires actuarial calculations that only specialized engines can perform: stochastic cash flow projection, best estimate liability calculation, risk adjustment for non-financial risk.
No standard ERP module replaces an actuarial engine. The standard demands contract-group granularity (annual cohorts) that exceeds the capabilities of traditional charts of accounts.
Specialized Solutions
The market has consolidated around a few key players:
- Willis Towers Watson (WTW) with its IFRS 17 subledger platform, which feeds actuarial results into the ERP general ledger
- Moody’s Analytics (formerly GGY AXIS) for life insurance modeling and CSM calculations
- SAP for Insurance with the FPSL (Financial Products Subledger) module, which serves as an intermediary layer between the actuarial engine and SAP FI
The investment is considerable. According to a WTW study, the global cost of IFRS 17 compliance for the insurance industry reached USD 18–20 billion, with an average cost of USD 175–200 million for the 24 largest multinational groups.
Target Architecture: ERP Plus Actuarial Engine
The recommended architecture follows a three-layer model:
- Actuarial engine (AXIS, Prophet, ResQ): calculates technical provisions by cohort
- IFRS 17 subledger (SAP FPSL, Oracle Insurance Accounting Analyzer, WTW solution): aggregates actuarial results, manages cohorts, and produces compliant accounting entries
- ERP / General Ledger: receives aggregated entries and integrates them into the group close
The interface between these layers is critical. Flows must be traceable, reconcilable, and auditable, with a complete audit trail from individual contract to GL entry.
Dual Reporting in Practice: Running Local GAAP and IFRS in Parallel
Parallel Ledgers vs. Consolidation Adjustments
Two approaches coexist:
Approach 1: parallel ledgers in the ERP. Each entity maintains accounts simultaneously in two (or more) frameworks. SAP uses ledgers (0L for local, 2L for IFRS), Oracle uses secondary ledgers, Dynamics uses books. Advantage: IFRS reporting available in real time. Drawback: complex configuration and doubled entry volume.
Approach 2: adjustments at the consolidation level. Statutory accounting is maintained in the ERP; IFRS restatements are posted in the consolidation tool (SAP BPC, Oracle FCCS, Tagetik). Advantage: simpler ERP. Drawback: restatements are often manual, difficult to audit, and a source of close delays.
The 2026 trend is clearly toward parallel ledgers, especially for groups with a high volume of recurring restatements (IFRS 16, IAS 37 provisions, goodwill).
Multi-Standard Chart of Accounts
Mapping between local GAAP and IFRS requires a chart of accounts structured at two levels:
- Level 1 (local): statutory accounts complying with the applicable local GAAP
- Level 2 (IFRS): IFRS accounts with segmentation by nature per IAS 1
The mapping is not always one-to-one. For example, a single operating lease expense account may split under IFRS between right-of-use depreciation (asset nature) and interest expense (financial nature), requiring separate line items in the IFRS ledger.
Impact on the Monthly Close
Dual reporting structurally extends the closing calendar:
- Additional controls on inter-ledger consistency
- Reconciliation of equity between the two frameworks
- Validation of the “bridge” between local and IFRS profit or loss
- Documentation for auditors (justification of each significant difference)
A well-organized group absorbs this additional workload in 1 to 2 extra closing days. A poorly prepared group may see its close extend by a full week.
IFRS Compliance Checklist for the ERP
Before declaring your ERP “IFRS-ready,” verify these eight points:
- IFRS ledger activated: a dedicated ledger or book for international standards is configured and automatically populated
- Account mapping documented: the local GAAP to IFRS correspondence table is formalized, versioned, and audited
- Fixed assets module configured: IFRS 16 right-of-use assets are managed as standalone assets with their own depreciation schedule
- Cash flows split: lease payments are correctly separated between principal and interest in the statement of cash flows
- IAS 1-compliant reporting: IFRS financial statements are generatable directly from the ERP (balance sheet, income statement by nature, cash flow statement, statement of changes in equity)
- Complete audit trail: each IFRS entry is traceable to its source (contract, invoice, actuarial calculation)
- Teams trained: accountants and controllers understand both frameworks and can interpret differences
- Close rehearsals completed: at least two full dry-run closes have been performed before go-live, with complete equity reconciliation
2026 Trend: Toward Unified Financial and Non-Financial IFRS Reporting
The ISSB (International Sustainability Standards Board), hosted by the same IFRS Foundation as the IASB, published IFRS S1 and S2 on sustainability reporting, effective from January 2024. In 2026, 21 jurisdictions have adopted these standards on a voluntary or mandatory basis.
For European groups, the convergence between CSRD/ESRS (European standards) and IFRS S1/S2 (international standards) creates a third reporting axis. ERPs will need to progressively integrate non-financial data — carbon emissions, energy consumption, social indicators — into the same infrastructure as financial data.
CFOs who invest today in a robust multi-ledger reporting architecture for IFRS 16/17 are laying the foundation for a system capable of absorbing ESG reporting tomorrow without a major overhaul.
To explore related topics, see our guides on ERP cost optimization after go-live, CSRD compliance and ERP systems, and our analysis of anti-corruption compliance automation in ERP.
