IFRS 16 has been in force since 1 January 2019 for groups reporting under IFRS. Yet seven years on, the majority of mid-sized companies subject to the standard still manage their lease contracts in spreadsheets or via a standalone tool that sits entirely outside their ERP. The result: laborious period-end closes, manually recalculated lease liabilities, and a real risk of error whenever a contract is revised.
This guide is aimed at CFOs and management controllers who want to move past that situation. The goal is to understand exactly what the standard requires, how to configure it in your ERP, and which modules to activate depending on your vendor.
What IFRS 16 Changes for Your Accounting
Before IFRS 16, operating leases stayed off the balance sheet. Only the rent expense appeared in the income statement. Under the new standard, almost all lease contracts must be recognised on the balance sheet, regardless of their classification.
Two new lines appear in your financial statements: an asset (the right-of-use asset, or ROU asset) and a liability (the lease liability). This change has a direct impact on your financial ratios: reported debt, EBITDA, and the debt-to-EBITDA ratio. For a listed company or one subject to banking covenants, the figures can be material.
Scope of the Standard: Which Contracts Are Covered and What Exemptions Apply
Any contract that gives the right to control the use of an identified asset for a specified period falls within the scope of IFRS 16. In practice this covers: office leases, warehouse leases, company vehicle fleets, industrial equipment under finance lease, dedicated server hosting contracts, and materials-handling equipment.
The standard provides two practical exemptions:
- Short-term leases: contracts with an original term of 12 months or less (applied as an accounting policy by asset class).
- Low-value assets: the underlying asset has a value of approximately USD 5,000 or less when new, regardless of its residual value. Software subscription contracts with no access to a physical asset often fall into this category.
These two exemptions do not alter the contracts themselves but allow them to be expensed on a straight-line basis rather than capitalised. In your ERP, this means a filtering rule must be applied when each contract is entered.
The Three Accounting Objects to Create
For each capitalised contract, IFRS 16 requires three objects in your chart of accounts and in your ERP configuration:
- The ROU asset: a fixed asset depreciated over the lease term (or the useful life of the underlying asset if shorter). It is measured at the present value of future lease payments at commencement date.
- The lease liability: a financial liability equal to the discounted future lease payments. It decreases with each lease payment (principal repayment portion) and increases with each periodic interest charge.
- The interest expense: calculated on the outstanding lease liability at the discount rate used. It is recognised in financial results, not in operating expenses.
This three-way split is fundamental to ERP configuration: your general ledger accounts, analytical dimensions, and approval workflows must all correspond to these three objects.
How to Configure Your ERP for IFRS 16
Contract Reference Framework: Data Structure and Mandatory Fields
The first building block is a contract register within your ERP. Each contract must populate at minimum:
- Unique contract identifier
- Asset class (real estate, vehicle, equipment, other)
- Commencement date and contractual end date
- Renewal options and the probability of exercise assumed
- Periodic lease payment amounts and indexation terms
- Discount rate (IBR or the rate implicit in the lease if determinable)
- Legal entity and country (for multi-entity groups)
- Currency (the liability must be remeasured at each period-end for foreign-currency contracts)
Without a single register, every contract revision triggers a manual search. Groups with portfolios of dozens of leases quickly lose visibility.
Calculating the Incremental Borrowing Rate (IBR) and Its Impact on the Liability
The incremental borrowing rate (IBR) is the rate at which the entity could borrow to acquire a similar asset under comparable conditions. It depends on the country, the currency, the contract term, and the entity’s credit quality.
This rate is an accounting judgement, not a fixed parameter. It must be documented, validated by the statutory auditor, and revised when significant contract modifications occur.
Numerical illustration: for an office lease at £10,000 per month over 5 years, with an IBR of 4% per annum, the initial lease liability amounts to approximately £542,000, calculated using the present value of an annuity formula:
Liability = monthly payment × [(1 − (1 + monthly rate)^−n) / monthly rate]
= 10,000 × [(1 − (1 + 0.003333)^−60) / 0.003333]
≈ 542,000This amount appears on the balance sheet as financial debt. The ROU asset recognised as the counterpart entry is for the same amount, adjusted for any lease incentives or prepayments.
The ERP implication is direct: the IBR must be entered contract by contract in the lease management module. If your ERP has no dedicated field, one must be added or managed via a custom attribute.
Generating Journal Entries Automatically: ROU Depreciation and Lease Liability Interest
The key benefit of a dedicated IFRS 16 ERP module is the automatic generation of recurring journal entries. At each payment date, the module must produce:
Entry at each lease payment:
- Debit: lease liability (principal repayment)
- Debit: interest expense (interest on the outstanding balance)
- Credit: cash account (total lease payment disbursed)
Monthly depreciation entry:
- Debit: ROU asset depreciation charge
- Credit: accumulated depreciation — ROU asset
These entries must be verifiable through a depreciation schedule accessible within the ERP, detailing for each period: opening liability balance, interest, repayment, closing balance, and net ROU asset value.
Practical Guidance for the Main ERP Systems
SAP S/4HANA: FI-LA (Lease Administration)
SAP has offered a native module called FI-LA (Lease Administration) since S/4HANA 1809, integrated directly into Finance. It handles contract entry, automatic depreciation schedule generation, and the production of IFRS 16- and ASC 842-compliant journal entries.
FI-LA is separate from the RE-FX (Real Estate Flexible Framework) module, which manages property portfolio management. For strict IFRS 16 compliance, FI-LA is the correct entry point. RE-FX can be activated alongside it for organisations managing a large real estate portfolio.
Key configuration points for SAP:
- The contract type must be correctly set to trigger IFRS 16 accounting rather than straight-line expensing.
- FI-LA transactions must be integrated into the period-end close calendar (both controlling and financial management are affected).
- Contract revisions require modification of the FI-LA object itself, not just a manual note.
Oracle ERP Cloud: Native Lease Management Module
Oracle ERP Cloud includes a Lease Management module in its Financials Cloud suite. It covers IFRS 16 and ASC 842 compliance, with a dedicated interface for contract entry, liability calculation, and journal entry generation into Oracle Financials.
Oracle’s advantage here is its native integration with the Fixed Assets module (for the ROU asset) and the Payables module (for lease payments). The compliance dashboard provides a consolidated view of the contract portfolio with maturity dates, revision dates, and risk indicators.
Oracle also handles contract modifications (remeasurement) directly within the module, with automatic recalculation of the residual liability and generation of the adjustment entry.
Sage Intacct, Dynamics 365, and Odoo: Alternatives and Third-Party Modules
The picture is more varied for mid-market ERP platforms:
Sage Intacct offers native lease accounting capabilities in its Finance suite, covering IFRS 16 and ASC 842. For groups on other Sage products (Sage X3 / Sage Enterprise Management), no native IFRS 16 module exists. Integrators often propose third-party connectors or custom developments — check with your implementation partner for your specific version.
Microsoft Dynamics 365 Finance includes a complete Asset Leasing module, available since version 10.0.14. It supports both IFRS 16 and ASC 842, with liability calculation, journal entry generation, and contract modification management. This is a robust option for groups already on the Microsoft ecosystem.
Odoo has no native IFRS 16 module in either the Community or Enterprise edition as standard. Modules are available through the OCA (Odoo Community Association) or third-party vendors, but their maturity and maintenance track record vary considerably. For a mid-sized company subject to IFRS 16 running Odoo, the typical approach is to manage leases in a third-party tool synchronised with Odoo accounting via periodic imports — which largely eliminates the automation advantages.
Period-End Pitfalls: Revisions and Contract Modifications
Contract Modification: Recalculating the Residual Liability
IFRS 16 requires the lease liability to be remeasured whenever a significant event occurs on the contract. These events include:
- Exercise (or non-exercise) of a renewal option whose probability changes.
- A change in the lease payment amount (index revision, renegotiated rent).
- A change in term (early termination, extension outside of an option).
- A change in the scope of the underlying asset (expanded floor area, additional equipment).
For each significant modification the procedure is: calculate the new present value of the remaining future lease payments at the current (or revised) IBR, compare it with the current liability balance, and recognise the difference as an adjustment to the ROU asset. If the asset is fully depreciated, the adjustment goes directly to the income statement.
The classic pitfall is processing these modifications in an external spreadsheet without updating the ERP. At the annual close, the reconciliation between the ERP balance and the reference schedule reveals irreconcilable discrepancies.
Annual IFRS 16 Close: Balance Sheet, P&L, and Disclosure Note
The annual IFRS 16 close involves three distinct accounting deliverables:
1. Balance sheet reconciliation: the ROU asset balances (gross and accumulated depreciation) and the lease liability (current and non-current) must be reconciled contract by contract.
2. P&L reconciliation: the IFRS 16 interest expense and depreciation charge must be separated from other finance charges and other depreciation. Many groups create dedicated accounts (e.g. a specific interest account for IFRS 16 and a separate accumulated depreciation account for ROU assets) to make this isolation automatic.
3. Mandatory disclosure note: the standard requires a note detailing the maturity analysis of lease liabilities (less than one year, between one and five years, more than five years), interest charges, depreciation, and cash outflows for the period. Your ERP must be capable of generating this disclosure without manual reworking.
If your ERP cannot produce all three directly, that is the signal to either activate a dedicated module or invest in a third-party tool before the next close.
IFRS 16 ERP Compliance Checklist
Before your next close, work through each of the following:
- Contract inventory: all potentially in-scope contracts have been identified (real estate leases, vehicles, equipment, long-term asset rentals).
- Exemption filtering: contracts of 12 months or less and assets below USD 5,000 are identified and expensed on a straight-line basis.
- IBR documented: an IBR has been determined and documented for each contract, validated by the statutory auditor or CFO.
- Contract register in ERP: mandatory fields (dates, payment amounts, IBR, renewal options) are populated in the ERP module or in the synchronised satellite tool.
- Automatic journal entries: depreciation schedules and liabilities are calculated by the system, not manually.
- Dedicated general ledger accounts: specific IFRS 16 accounts are configured for the ROU asset, accumulated depreciation, current and non-current lease liability, and interest expense.
- Contract modification workflow: a process exists to handle every modification event (renegotiation, option exercise, partial termination) with automatic recalculation.
- Close reporting available: the lease liability maturity table and the IFRS 16 disclosure note can be extracted directly from the ERP.
- Balance sheet-to-ERP reconciliation: a reconciliation control is included in the monthly close checklist.
- ROU impairment testing: if the recoverable amount of an underlying asset decreases, an impairment test on the ROU asset is performed and documented.
To go further on period-end processes in your ERP, see our operational monthly close checklist: from D-5 to D+3 and our complete guide to management control and analytical accounting in ERP.
If you want to assess the IFRS 16 readiness of your current ERP before deciding on an additional module, download our ERP evaluation grid (30 criteria across 100 points for comparing up to 3 solutions side by side).
