How to Identify and Avoid the Ten Common IFRS 16 Errors in Multinational Groups

The most challenging aspects of IFRS 16 rarely involve calculation errors. Instead, they concern completeness, professional judgment, and process management, areas where the resulting figures may appear perfectly reasonable at first glance. Drawing on the Envoria Finance team's project experience, this article examines ten recurring IFRS 16 pitfalls in multinational groups, including how to identify them, their potential impact, and how to prevent them.

Why Plausible Figures and Incomplete Lease Data Pose a Risk

A straightforward calculation error is often easy to spot: It produces an implausible figure and is usually identified when reconciling the calculation to the payment schedule. Many of the issues discussed here, however, do not trigger a system error. The figures look reasonable, reconcile correctly, and roll forward consistently throughout the lease term—until someone asks how they were determined.

An even greater risk arises when no calculation is performed at all. A contract that never enters the lease register creates no discrepancy that could draw attention. In a multinational group, the problem can be amplified: An accounting assessment adopted during a rollout may be replicated across the consolidation scope. The treatment is consistent across all entities, but consistently incorrect.

Overview of the Ten Common IFRS 16 Pitfalls

Pitfall 1 – Not All Lease Arrangements Are Identified

Under IFRS 16.9, a contract contains a lease if it conveys the right to control the use of an identified asset for a period of time in exchange for consideration. IFRS 16.B9–B31 provide further guidance. The assessment centers on three questions: Is there an identified asset? Does the customer obtain substantially all the economic benefits from its use? Does the customer have the right to direct how and for what purpose the asset is used?

This creates two completeness risks. The first is operational: Conventional rental and lease agreements never make it into the central lease register because they are negotiated locally and not reported. The second is more complex: A contract may contain a lease even if it is not labeled as a rental or lease agreement. Examples include logistics and warehousing contracts involving dedicated space, manufacturing arrangements using dedicated equipment, transportation contracts involving specified vehicles, IT and data center agreements, power purchase agreements, and outsourcing contracts.

Assessments often stop when a supplier points out that it has the contractual right to substitute the asset at any time. However, a substitution right prevents an asset from being identified only if that right is substantive. The supplier must have both the practical ability to substitute the asset and an economic incentive to do so. A substitution clause on its own is not sufficient.

• How to recognize it: The lease register is compiled exclusively from rent expense accounts, accounts payable records, or contracts containing "lease" in the title. Some entities report no new contracts for extended periods, service and outsourcing agreements are not systematically reviewed, and there is no regular reconciliation between procurement, accounts payable, and the IFRS 16 system.
• Potential impact: Right-of-use assets and lease liabilities are omitted entirely, expenses continue to be recognized as rent expense, and disclosures are incomplete. A single overlooked logistics or data center agreement may be more material than a discount rate discrepancy across the rest of the lease portfolio.
• How to prevent it: Introduce risk-based contract screening for relevant contract categories; use a standardized IFRS 16 questionnaire covering the three key assessment questions, completed by the responsible business functions when contracts are signed; establish mandatory reporting procedures involving Procurement, Legal, Facility Management, IT, and Fleet Management; and regularly reconcile the lease register with procurement and accounts payable data.

Pitfall 2 – A Single Group-Wide Discount Rate Is Applied

Under IFRS 16.26, a lessee must use the interest rate implicit in the lease if that rate can be readily determined. Otherwise, it must use the lessee's incremental borrowing rate, the rate the lessee would have to pay to borrow, over a similar term and with similar security, the funds necessary to obtain an asset of similar value to the right-of-use asset in a similar economic environment. The relevant reference point is the reporting entity.

A group-wide methodology is therefore not inherently problematic; in fact, it is beneficial. Discount rates can be derived using a documented matrix based on country, currency, and lease term bands. A portfolio approach is permitted under IFRS 16.B1, provided it is reasonably expected to produce results that are not materially different from applying the standard to individual leases. The problem arises when a single rate, often the parent company's borrowing rate, is applied indiscriminately to leases with different economic characteristics.

Calculation Example

Consider a seven-year lease with annual payments of EUR 250,000 made at year-end. The lease is measured using a flat group discount rate of 3.0%, compared with an appropriately determined entity-specific rate of 6.5% (amounts in EUR):

The lease liability would be EUR 186,441 higher than the amount calculated using the appropriate rate—approximately 13.6% above that amount. This affects the balance sheet, depreciation, EBIT, interest expense, and financial results. Under a conventional EBITDA definition that excludes depreciation and interest expense, the choice of discount rate does not affect EBITDA. However, company-specific covenant and performance measure definitions must be assessed separately. IFRS 18 also introduces additional disclosure requirements for certain management-defined performance measures.

• How to recognize it: The group accounting policy specifies only one discount rate, or there is no documented rate determination by entity, currency, and lease term band.
• How to prevent it: Establish a consistent group-wide methodology, derive rates using a documented and regularly updated matrix, and document the conditions supporting the use of a portfolio approach.

Pitfall 3 – Lease Terms Are Assessed Based on Contractual Form Rather Than Economic Substance

Under IFRS 16.18–21, the lease term includes the noncancelable period, together with periods covered by extension options that the lessee is reasonably certain to exercise and periods covered by termination options that the lessee is reasonably certain not to exercise. "Reasonably certain" requires an economic assessment, not merely a legal interpretation. Relevant factors include leasehold improvements, the strategic importance of a location, relocation costs, and operational dependencies.

Two scenarios are particularly relevant. First, the lease term is automatically set equal to the initial noncancelable period, even though significant investments in the property make relocation economically unattractive. Second, open-ended contracts are measured using only their short notice periods. Under IFRS 16.B34–B41, the enforceable period ends only when both parties can terminate the lease without incurring more than an insignificant penalty, considering the economic substance of that penalty. Another common omission is the reassessment of lease terms following significant events within the lessee's control.

• How to recognize it: Nearly every recorded lease term matches the initial noncancelable period exactly. Assessments of extension and termination options are undocumented, and no reassessments have been recorded for years.
• How to prevent it: Incorporate clearly defined criteria for assessing options into the lease onboarding process, document the rationale for each lease, and reassess the lease term when relevant triggering events occur.

Pitfall 4 – Incorrect Inputs Are Used for Initial Recognition and Measurement

Incorrect Commencement Date

Under IFRS 16.22, a right-of-use asset and lease liability are recognized at the commencement date, the date on which the lessor makes the underlying asset available for use by the lessee. This is not necessarily the contract signing date, the first payment date, the invoice date, or the contractual start date. Common risk areas include delayed handovers, early access, fit-out periods, rent-free periods, and payment schedules that begin on a different date.

Incorrect Components of the Lease Liability

Under IFRS 16.27, the initial measurement of the lease liability includes fixed and in-substance fixed payments, less any lease incentives receivable; payments that depend on an index or rate, measured using the index or rate at the commencement date; amounts expected to be payable under residual value guarantees; the exercise price of a purchase option if the lessee is reasonably certain to exercise it; and termination penalties if the lease term reflects the exercise of a termination option. Payments based solely on usage or sales are excluded.

The distinction from Pitfall 5 is important. Pitfall 5 addresses which portion of the consideration relates to a lease component. Here, the focus is on which amounts are included in the lease liability and which additional items affect the right-of-use asset.

The Right-of-Use Asset Does Not Necessarily Equal the Lease Liability

The right-of-use asset does not always equal the lease liability. For straightforward leases without advance payments, lease incentives, initial direct costs, or restoration obligations, however, the two amounts may be identical. The following reconciliation illustrates the requirements of IFRS 16.23–25 using a hypothetical five-year office lease with annual payments of EUR 120,000 made at year-end and a discount rate of 5.0% (amounts in EUR):

Assumption: The EUR 20,000 lease incentive received at commencement has not already been reflected in future lease payments or, consequently, in the lease liability. Double counting is therefore avoided.

In this example, the right-of-use asset exceeds the lease liability by approximately EUR 50,000, or 9.6%. This difference affects depreciation throughout the lease term. Initial direct costs include only incremental costs that would not have been incurred if the lease had not been executed. General personnel costs, general legal advisory fees, and due diligence costs that would have been incurred regardless of the lease generally do not qualify. Restoration obligations must be recognized in accordance with the applicable requirements, particularly IAS 37.

• How to recognize it: Right-of-use assets and lease liabilities are consistently identical across a diverse lease portfolio. This is an indicator worth investigating, not proof of an error. The contract signing date or first payment date is routinely used as the commencement date. Lease incentives, advance payments, and restoration obligations are accounted for outside the lease measurement process, while legal and advisory costs are capitalized indiscriminately.
• How to prevent it: Make the commencement date a separate mandatory data field, distinct from the contract date and payment start date. Document the reconciliation from the lease liability to the right-of-use asset for each lease.

Pitfall 5 – Lease and Non-Lease Components Are Not Properly Separated

IFRS 16.12–16.16 generally require lease and non-lease components to be separated, with consideration allocated based on relative stand-alone prices. However, IFRS 16.15 allows lessees to elect, by class of underlying asset, not to separate non-lease components from the associated lease component and instead account for them together as a single lease component. A higher recognized balance is therefore not automatically an accounting error. What matters is that the election is made deliberately, documented, and applied consistently.

A separate component generally requires the transfer of a distinct good or service to the lessee. Maintenance and tire services may therefore qualify as non-lease components. Insurance, taxes, and administrative charges require further assessment to determine whether a distinct service is actually provided. Costs incurred by the lessor or activities performed solely for its own administration do not, by themselves, constitute separate components. The label assigned to a charge is not sufficient evidence. The issue arises when the full invoiced amount is used without review, the accounting policy election is applied inconsistently, or components are classified incorrectly.

Simplified Calculation Example

Consider a full-service vehicle lease with a 36-month term and a total monthly payment of EUR 900. In this example, EUR 220 per month relates to identified non-lease components, primarily maintenance and tire services, leaving EUR 680 attributable to the lease component. The discount rate is 5.0% nominal per year, with a monthly periodic rate of 5.0% divided by 12 (per vehicle, in EUR):

Across 400 comparable vehicles, the difference would amount to approximately EUR 2.9 million. This is not an accounting error amount; rather, it illustrates the range of outcomes between separating the components and accounting for them together under the practical expedient. The example is intentionally simplified.

• How to recognize it: Recognized amounts exactly match the total amounts on supplier invoices, without a documented election under IFRS 16.15 or an assessment of the individual components.
• How to prevent it: Define classes of underlying assets, make a deliberate policy election for each class, and retain documentation supporting the allocation methodology.

Pitfall 6 – Accounting Policy Elections and Exemptions Are Applied Inconsistently

IFRS 16.5 permits lessees to elect not to recognize short-term leases and leases of low-value assets on the balance sheet. However, these elections operate differently, and the distinction is often overlooked. Under IFRS 16.8, the short-term lease exemption is applied by class of underlying asset, while the low-value asset exemption is applied on a lease-by-lease basis. A lease containing a purchase option also does not qualify as a short-term lease.

IFRS 16 does not prescribe a fixed monetary threshold for low-value assets. Under IFRS 16.B3–B8, the assessment is made on an absolute basis, using the value of the underlying asset when new, regardless of the size or nature of the lessee. Internal thresholds are not requirements of the standard; they are a practical means of implementing the assessment. Economically comparable assets should not be assessed differently across the group without a valid reason.

• How to recognize it: There is no documented group-wide definition of asset classes for the short-term lease exemption or consistent criteria for assessing low-value assets. Comparable assets receive different accounting treatment without justification.
• How to prevent it: Define asset classes, assessment criteria, and practical implementation rules in the group accounting policy, and periodically test compliance through sample reviews.

Pitfall 7 – Lease Modifications Are Incorrectly Classified and Accounted For

Not every contract amendment is a lease modification, and not every modification results in a partial termination. Before recording an adjustment, the event must be classified correctly: a reassessment of the lease term or options without a contractual change; a modification accounted for as a separate lease; another type of lease modification; a decrease in scope; or a partial or full termination.

Under IFRS 16.44, a modification that adds additional rights to use underlying assets is accounted for as a separate lease if the consideration increases by an amount commensurate with the stand-alone price of the increase in scope. Otherwise, IFRS 16.45 and 16.46 apply: The consideration must be reallocated, the lease term redetermined, and the lease liability remeasured using a revised discount rate. Where a modification decreases the scope of a lease, the portions of the right-of-use asset and lease liability attributable to the terminated rights must first be derecognized, with any resulting difference recognized in profit or loss. The remaining lease liability is then remeasured, with the subsequent adjustment generally recognized against the right-of-use asset. Simply overwriting the payment schedule or creating a new lease record does not capture these accounting requirements.

Many processing errors originate earlier in the workflow. Lease agreements are negotiated locally—by Facility Management, Fleet Management, IT, or individual subsidiaries. When amendments reach Accounting late or without a proper technical assessment, the result may be adjustments relating to closed periods, retrospective remeasurements, and a modification history that is difficult to substantiate. From an auditor's perspective, this can indicate a control deficiency, regardless of the final accounting outcome.

The underlying scope parameters, such as floor area, number of assets, or rights of use, are often not documented in a structured format. As a result, changes in scope cannot be reliably identified and measured.

• How to recognize it: Amendments are entered as new leases or recorded by overwriting existing payment schedules. Gains or losses from partial terminations are missing even though the scope of leases has been reduced. Period-end closing routinely involves a significant number of adjustments relating to prior months.
• How to prevent it: Establish defined modification types with corresponding measurement and accounting rules, mandatory reporting procedures with clear responsibilities and deadlines, technical approval supported by maker-checker controls, and a version-controlled, auditable modification history for each lease.

Pitfall 8 – Index- and Rate-Related Adjustments Are Discounted Incorrectly

IFRS 16.42 and 16.43 distinguish between two situations that are frequently confused in practice. When future lease payments change because of movements in an index or a rate used to determine those payments. For example, under an inflation-linked rent adjustment clause, the lease liability is generally remeasured using the unchanged discount rate. However, when the change results from movements in a floating interest rate, a revised discount rate must be used.

Errors occur in both directions. Some teams update the discount rate every time rent changes. Others fail to remeasure the liability and instead recognize the additional payment as a current-period expense, leaving the lease liability understated. Timing also matters: Remeasurement takes place when the adjustment becomes effective, not in anticipation of a future change.

• How to recognize it: The discount rate recorded for a lease has changed multiple times since commencement, without a documented modification, reassessment, or floating-rate arrangement.
• How to prevent it: Configure the system to distinguish index-linked adjustments from changes driven by floating interest rates, document the trigger for each remeasurement, and align the remeasurement date with the effective date of the adjustment.

Pitfall 9 – Foreign Currency Leases Are Not Translated Correctly

A lease liability is a monetary item under IAS 21 and must therefore be translated at the closing exchange rate at each reporting date (IAS 21.23(a)). Under IAS 21.28, the resulting exchange differences are generally recognized in profit or loss. By contrast, a right-of-use asset is generally a nonmonetary item. When measured under the cost model at historical cost less accumulated depreciation, it is translated using the exchange rate at the date of the transaction under IAS 21.23(b), rather than being retranslated at each reporting date.

A common mistake is to treat both balances in the same way. Either the right-of-use asset is repeatedly translated at the closing exchange rate, or the exchange difference on the lease liability is recorded against the right-of-use asset instead of being recognized in profit or loss. Both approaches can result in an incorrect depreciation base and may go unnoticed without a dedicated control.

Lease modifications require particular attention. If a modification results in an adjustment to the right-of-use asset, that adjustment is translated using the exchange rate at the modification date because it forms part of a nonmonetary asset. For practical purposes, a rate that reasonably approximates the actual transaction-date rate, such as a monthly average rate, may be used. The translated adjustment becomes part of the historical cost basis of the right-of-use asset and is therefore generally not retranslated using subsequent closing exchange rates.

• How to recognize it: The right-of-use asset and lease liability arising from the same foreign currency lease continue to move in parallel over time instead of diverging.
• How to prevent it: Configure the appropriate foreign currency treatment for each balance directly in the system rather than relying on period-end spreadsheets. Calculate exchange differences separately and recognize them appropriately in profit or loss.

Pitfall 10 – Intercompany Leases Are Not Properly Matched and Eliminated

When one group entity leases an asset to another, each party accounts for the arrangement under the requirements applicable to its role. These requirements are not symmetrical. On the lessor side, IFRS 16.61 first requires classification as either a finance lease or an operating lease. For a finance lease, the lessor recognizes a receivable equal to the net investment in the lease, measured under IFRS 16.67 and 16.68 using the interest rate implicit in the lease. For an operating lease, the underlying asset remains recognized, while lease payments are generally recognized as income on a straight-line basis or another appropriate systematic basis under IFRS 16.81. Accordingly, the carrying amounts in the separate financial statements do not necessarily mirror each other, nor must they be based on identical discount rates.

In the consolidated financial statements, the intragroup leasing arrangement is eliminated. Under IFRS 10.B86(c), intragroup assets, liabilities, equity, income, expenses, and cash flows must be eliminated in full. The asset relevant from the group's perspective, or an external head lease if the intragroup lessor does not own the underlying asset, continues to be accounted for under the applicable standards.

The main challenge is rarely the elimination logic itself. More often, it is the underlying data: missing shared contract or asset IDs, inconsistent master data, differences in reporting periods and currencies, and intercompany reconciliations in which lease arrangements are recorded only at an aggregated level.

• How to recognize it: Recurring consolidation differences are cleared manually, there is no unique identifier linking the lessee's and lessor's records, and the contract data maintained by both parties has not been reconciled.
• How to prevent it: Maintain a centralized lease register or, at a minimum, a shared identifier maintained by both parties that links the corresponding lease records and makes consolidation eliminations traceable.

What These Ten IFRS 16 Pitfalls Have in Common

These ten issues affect different areas, completeness, recognition, measurement, subsequent measurement, and consolidation, but they share one important characteristic: They generally do not trigger a system error. Missing contracts do not appear anywhere in the records, while an incorrectly assessed lease may look exactly like one that has been assessed correctly. The most effective starting points are a reliable lease identification process, a documented accounting policy covering discount rates, lease terms, and policy elections, and a controlled process for handling lease modifications.

For multinational groups in particular, it is essential that these processes are not only defined centrally but also implemented consistently across individual entities. Clear responsibilities, standardized policies, and regular controls help identify discrepancies early and maintain reliable IFRS 16 data throughout the group.

Conclusion: How Multinational Groups Can Avoid Common IFRS 16 Errors

The most material IFRS 16 risks are not found in the present value formula. Instead, they fall into four key areas.

• Completeness: Contracts, particularly leases embedded in service and outsourcing agreements, never make it into the lease register.
• Recognition and initial measurement: The commencement date, components of the lease liability, and reconciliation to the right-of-use asset are not fully or correctly reflected.
• Professional judgment: Discount rates, lease terms, component separation, and accounting policy elections are applied inconsistently across the group.
• Subsequent measurement and group processes: Lease modifications, index- and rate-related adjustments, foreign currency transactions, and intercompany leases are not properly assessed or accounted for.

IFRS 16 calculations are manageable. The real complexity arises when contracts never enter the lease register, when judgments are carried forward unchanged for years across multiple entities, and when contract amendments reach Accounting too late. A structured review of these ten areas can reveal tangible opportunities for improvement. Identified before the financial statements are finalized, an issue can be corrected proactively; identified during the audit, it may become an audit finding.

Ultimately, the difference lies less in technical accounting expertise than in having the right structures in place: moving from incomplete records to a systematic lease identification process, from inconsistent assumptions to documented accounting policies, from manual amendments to version-controlled modifications, and from isolated spreadsheets to a centralized lease register. This is where a system-supported process delivers real value.