Most CFOs know what IFRS 16 is. The standard, effective for annual periods beginning on or after 1 January 2019 (IFRS Foundation), eliminated the distinction between finance leases and operating leases for lessees. But between understanding the standard and running it correctly inside an ERP, there are often two years of patches, re-configuration, and manual month-end reconciliations.
The question is not theoretical. If your IFRS 16 module is not configured to automatically recalculate the lease liability when a lease is modified, your accounting team reprocesses every amendment by hand. If your fleet of 60 company cars is not fed into the leasing module, those contracts remain off-balance sheet. If the IBR is not set up per entity and per currency, your initial measurement is wrong.
This article walks through the IFRS 16 accounting flows, the coverage offered by the leading ERP platforms, and the four implementation pitfalls to avoid.
IFRS 16 Refresher: What the Standard Changed in 2019
The End of the Finance Lease / Operating Lease Distinction for Lessees
Before IFRS 16, lessees classified contracts into two categories: finance leases (on-balance sheet) and operating leases (expensed as incurred, off-balance sheet). This distinction allowed many organisations to keep significant commitments off their balance sheets.
IFRS 16 removes this distinction for lessees. Since 1 January 2019, virtually all leases with a term greater than 12 months, for underlying assets with an individual value above USD 5,000 (IFRS Foundation), must be recognised on the balance sheet.
Balance Sheet Impact: ROU Asset and Lease Liability
Implementing IFRS 16 creates two new lines in the lessee’s financial statements:
- Right-of-use (ROU) asset: represents the lessee’s right to use the underlying asset over the lease term. It is amortised over the lease term, typically on a straight-line basis.
- Lease liability: represents the present value of future lease payments. It decreases as payments are made and generates a finance charge calculated on the outstanding balance.
The impact on financial ratios is mechanical and significant: EBITDA improves (the previous lease expense is replaced by depreciation and finance charges, which are excluded from EBITDA), while net debt increases and leverage ratios deteriorate.
Who Is Affected and Available Exemptions
IFRS 16 applies to companies reporting under IFRS standards — primarily listed companies in Europe and elsewhere (mandatory for consolidated accounts), and subsidiaries of international groups consolidating under IFRS.
Unlisted SMEs reporting under local GAAP (such as UK GAAP FRS 102 or equivalent national standards) are generally not required to apply IFRS 16 in their standalone accounts. However, any subsidiary of an international group consolidating under IFRS must provide data compliant with this standard.
Two exemptions are available under the standard (IFRS Foundation):
- Short-term leases: initial lease term of 12 months or less
- Low-value assets: individual underlying asset value below USD 5,000 at the date of assessment, evaluated independently regardless of the total portfolio value
IFRS 16 Contract Types and Their ERP Specifics
Real Estate Leases
Commercial property leases typically represent the largest financial exposure. Long contractual terms, multiple renewal options, and rent escalation clauses tied to market indices: each parameter affects the lease term used in the ROU asset calculation and the payment schedule.
The ERP risk: failing to include renewal options that are “reasonably certain to be exercised” in the lease term. A lease renewed consistently for 15 years should likely incorporate several renewal periods in the IFRS 16 lease term.
Vehicle Fleet Leasing
Short contracts (24 to 48 months), homogeneous assets, high volume. Fleet leasing often represents the second-largest IFRS 16 exposure after real estate. The ERP challenge is scale: a mid-size business with 200 field staff and 200 vehicles under operating leases generates 200 individual contracts to initialise, amortise, and close out.
High-performing IFRS 16 modules handle fleet management with replicable contract templates and bulk initialisation via CSV import or API.
IT and Office Equipment
Servers, copiers, production equipment: these contracts are often scattered and under-reported. The first step before any ERP configuration is a comprehensive contract inventory. It is not uncommon for a business to discover 30 to 40 per cent of IFRS 16 contracts that have not been processed during an initial audit.
The low-value asset exemption (below USD 5,000 per individual asset) can exclude small items, but each asset must be assessed individually.
Service Contracts with an Identifiable Lease Component
IFRS 16 requires that, for mixed “service + lease” contracts, the lease component be identified and accounted for separately. A maintenance contract that includes the right to use an identified asset may contain an IFRS 16 component. In practice, finance teams tend to underestimate this risk.
Key point: pure SaaS contracts (cloud software with no identified underlying asset that the customer controls) are outside the scope of IFRS 16. The distinction hinges on whether an identified asset exists and whether the customer controls its use.
How the Leading ERPs Handle IFRS 16 Natively
SAP S/4HANA: Two Modules Depending on Asset Type
SAP S/4HANA offers two approaches depending on the nature of the contract (PIKON SAP Consulting):
- SAP RE-FX (Flexible Real Estate Management): recommended for real estate leases. It handles full lease contract management, automatic ROU asset and liability calculation, and integration with FI, CO and FI-AA. Available in both SAP ECC and S/4HANA.
- SAP Contract and Lease Management (CLM): for non-real-estate assets (fleet, IT equipment, machinery). Integrated in SAP S/4HANA Cloud, it covers contract classification, present value liability calculation, initial recognition entries, and monthly amortisation.
SAP’s functional coverage is the most comprehensive on the market. The configuration complexity — two distinct modules, IFRS chart of accounts setup, integration with SAP Group Reporting for consolidation — makes it a standalone project that justifies a specialist implementation partner.
Oracle Fusion Cloud: Lease Accounting Subledger
Oracle Fusion Cloud Financials includes a dedicated Lease Accounting module with its own subledger (Oracle Docs 26A). It covers:
- Contract entry (assets, payments, options, IBR by entity)
- Amortisation schedules for ROU assets and lease liability repayment plans
- Automatic journal entries: initial recognition, monthly charges, modifications, terminations
- Accounting event classes: Booking, Expense, Revision, Termination, Payment Approval
The integration with Oracle EPM Cloud (Financial Consolidation and Close Service) is native and allows IFRS 16 data to feed directly into consolidated group accounts without manual extraction.
Microsoft Dynamics 365 Finance: Native Asset Leasing Since 2020
Microsoft introduced the Asset Leasing module in Dynamics 365 Finance in November 2020 (Microsoft Dynamics 365 Blog). It automates:
- Calculation of the net present value of future payments
- ROU asset depreciation
- Finance charge on the lease liability
- Automatic lease classification (finance, operating, short-term, low-value)
Coverage is solid for SMEs and mid-market organisations, with native integration into the Dynamics 365 Finance General Ledger. Functional depth is below SAP or Oracle for complex multi-entity groups, but sufficient for most non-listed subsidiaries of IFRS-reporting parents.
Sage X3: Partial Coverage
Sage X3 does not offer a fully native IFRS 16 module. Managing ROU assets and lease liability requires either manual configuration within the fixed assets module, or integration of a third-party add-on. This is an important consideration for businesses evaluating ERP platforms under IFRS 16 obligations: always verify the implementation partner’s IFRS 16 coverage and request a documented reference case before signing.
Odoo 18: Add-On Required
Odoo — in neither Community nor Enterprise version 18 — includes a native module that fully covers IFRS 16. Third-party applications are available on Odoo Apps, but they vary considerably in quality and functional scope. A business subject to IFRS 16 that selects Odoo must plan for either a custom development or a rigorous evaluation of a third-party add-on before go-live, with sign-off from its statutory auditors.
Key Data Points to Capture in the ERP for ROU Asset Calculation
Incremental Borrowing Rate (IBR): The Critical Parameter
The IBR (Incremental Borrowing Rate) is the hypothetical rate at which the entity would borrow, at the lease commencement date, for a similar asset over a similar term. IFRS 16 requires this rate to discount future cash flows when the rate implicit in the lease cannot be readily determined — which is nearly always the case for real estate leases and operating leases with purchase options.
In the ERP, the IBR must be configured per legal entity (a subsidiary in Spain does not carry the same credit risk as one in Germany), per currency, and per duration band. A single IBR applied to all entities is not IFRS 16-compliant and will typically be flagged during a statutory audit.
Lease Term and Renewal Options
The term used for the IFRS 16 calculation is not necessarily the minimum contractual term. If exercising a renewal option is “reasonably certain” within the meaning of IFRS 16 (an accounting judgement), the lease term must include those optional periods.
That judgement must be documented, reassessed whenever a significant modification occurs, and tracked in the ERP module with a full audit trail.
Variable Payments, Escalation Clauses and Periodic Reassessments
Variable lease payments indexed to a rate or index (e.g. CPI-linked rent reviews, annual market rent escalations) are included in the IFRS 16 calculation under the remeasurement rules. The ERP module must be able to handle these periodic reassessments and generate the corresponding remeasurement entries without manual intervention.
IFRS 16 Accounting Flows the ERP Must Automate
At Commencement: Initial Recognition
At the lease commencement date, the ERP must simultaneously generate:
- Debit ROU asset / Credit Lease liability for the present value of future lease payments at the IBR
- Adjustments for any initial direct costs incurred by the lessee, lease prepayments, and lease incentives received from the lessor
Through Each Period: Depreciation and Finance Charge
At each monthly close, three entries must be fully automated:
- Depreciation charge on the ROU asset, calculated on a straight-line basis over the lease term
- Finance charge on the lease liability, calculated by applying the IBR to the opening liability balance for the period
- Liability repayment equal to the cash payment made, net of the finance charge (effective interest method)
A close that requires manual entry of these three journals is a significant operational risk, particularly for groups managing several dozen or hundreds of active contracts.
Lease Modifications: Remeasurement or New Contract
When the terms of a lease change — renewal, change of leased space, renegotiation of rent, partial early termination — IFRS 16 requires either remeasurement of the existing contract or recognition of a separate new contract. The qualification rules are precise and must be applied contract by contract.
In the ERP, the module must allow the modification to be entered, automatically recalculate the residual liability based on the revised payment schedule, and generate the adjustment entry with full traceability.
IFRS 16 Reporting: What Your ERP Module Must Produce
IFRS 16 disclosures require several elements in the notes to the financial statements:
- ROU asset movement table: opening balance, additions, disposals, scope changes, closing balance
- Maturity analysis of future lease payments: reconciliation between undiscounted future minimum payments and their present value — the IFRS 16 lease liability on the balance sheet
- Breakdown of IFRS 16 charges for the period: ROU depreciation, finance charges, variable lease payments excluded from the calculation, charges on short-term leases and low-value assets
A mature IFRS 16 module produces these schedules directly, without Excel reprocessing. For group consolidation, the connection with CPM tools (SAP Group Reporting, Oracle FCCS, LucaNet, Tagetik) is decisive: ROU asset and liability data must flow into the consolidated accounts with proper intercompany elimination treatment.
The 4 IFRS 16 Implementation Pitfalls in Your ERP
1. Underestimating the Number of In-Scope Contracts
A comprehensive contract inventory is the step most consistently underestimated. Real estate leases are generally well identified, but fleet vehicles, production equipment, copiers, co-location racks, and rented materials-handling equipment: each category can contain IFRS 16 contracts. An incomplete inventory means an incomplete balance sheet — and painful corrective adjustments at the first audit.
2. Neglecting Modifications and Recurring Remeasurements
The initial recognition is usually handled carefully, as it forms part of a visible project. Subsequent modifications receive far less attention. Yet every lease amendment — rent renegotiation, term extension, additional asset, partial early termination — triggers a mandatory remeasurement under IFRS 16. Without an automated tracking process in the ERP, these modifications go unnoticed and generate accounting variances that accumulate over multiple reporting periods.
3. Misconfiguring the IBR by Entity and Currency
A group with subsidiaries in multiple countries must maintain an up-to-date IBR table by legal entity, currency, and lease term band. A single rate applied to all entities is non-compliant, because the rate must reflect the borrowing conditions specific to each entity in its local market. This issue is frequently raised by auditors of mid-market groups in their first year under IFRS 16.
4. Disconnecting the Lease Module from the Automated Monthly Close
The IFRS 16 module is only useful if it is fully embedded in the monthly close calendar. If depreciation and finance charge entries are not generated within the automated close batch jobs, the accounting team must post manually each month for every contract. This operational risk is observed regularly on mid-market ERPs where the IFRS 16 module was bolted on after go-live, without a revision of the existing close workflows.
To go deeper on related topics, read our guide on ERP fixed assets management: depreciation, inventory and disposal and our analysis of group financial consolidation: native ERP module vs CPM tools. For finance leaders integrating IFRS 16 with financial planning, see our guide on Rolling Forecast and Zero-Based Budgeting in your ERP.
