Finanza

Changes to IFRS 16 Ahead? IASB Considers Simplifications for Discount Rates and Remeasurements

Nov. 17, 2026

The IASB has completed its Post-implementation Review of IFRS 16 with a clear conclusion: the Standard is generally working as intended, but ongoing application costs in certain areas are higher than originally expected. The IASB is therefore considering targeted simplifications to discount rates and the remeasurement of lease liabilities. These could reduce the technical and administrative effort involved in subsequent measurement in particular.

This article explains which changes are under consideration, which requirements are likely to remain, and how much relief companies could realistically expect.

The short answer

In July 2026, the IASB decided to add a research project to its project pipeline. The project will examine how to reduce the higher-than-expected ongoing costs lessees incur in applying the measurement requirements of IFRS 16, without significantly compromising the usefulness of lease-related financial information. Two areas are in focus:

  • Remeasurement of lease liabilities: for example, reducing the frequency of remeasurements and simplifying the requirements for variable lease payments linked to an index or rate.
  • Discount rates: for example, permitting a simplified rate instead of the incremental borrowing rate and allowing an unchanged discount rate for certain remeasurements.

The potential cost savings do not arise because an individual present value calculation becomes technically cheaper. Rather, fewer remeasurement triggers and simpler discount rate requirements could reduce technical and administrative effort: circumstances would need to be reassessed less frequently, discount rates recalculated less often, and changes processed and documented less frequently. The actual impact therefore depends largely on how extensively a company's IFRS 16 process is already automated. No timetable or draft amendments are available yet.

The IASB's Findings Confirm What Practitioners Have Long Known

In June 2025, the IASB published its Request for Information for the Post-implementation Review (PIR) of IFRS 16, with the comment period ending in October 2025. The findings were largely expected in substance, but the message was clear: the Standard generally provides better information about an entity's lease obligations than IAS 17. At the same time, numerous stakeholders indicated that the ongoing costs of applying the Standard, particularly for subsequent measurement, were higher than the Board had originally anticipated.

In March 2026, the IASB tentatively decided to establish a research project specifically addressing this cost burden. In July 2026, the Board confirmed the decision and completed the PIR on that basis. A project summary and feedback statement is expected in the fourth quarter of 2026, subject to approval by the Due Process Oversight Committee. The IASB has not yet determined when substantive work on the research project will begin.

Two Key Areas Under Consideration

1. Remeasurement of lease liabilities

The IASB is considering reducing the frequency of remeasurements. When an assessment of the lease term changes as a result of a relevant event or a significant change in circumstances within the lessee's control, this may trigger a remeasurement of the lease liability and a corresponding adjustment to the right-of-use asset. Depending on the reason for the remeasurement, a revised discount rate may also be required. In manual or highly decentralized processes, this creates recurring assessment, data entry, calculation, documentation and control activities. The potential simplification specifically targets this ongoing application effort.

Another topic under discussion is simplifying the remeasurement requirements for variable lease payments linked to an index or rate. Under the current IFRS 16 requirements, a lease liability must be remeasured when a change in an underlying index or rate results in an adjustment to contractual lease payments that takes effect. The remaining lease payments are then recalculated based on the adjusted contractual amounts. Particularly in large portfolios with frequent index adjustments, identifying, recording and processing these changes can create significant ongoing administrative effort.

2. Discount rates

The second area is even more fundamental: the IASB is considering allowing or requiring entities to use a simplified discount rate instead of the incremental borrowing rate (IBR). Since IFRS 16 was introduced, determining the IBR has been one of the most complex and judgment-intensive aspects of lease accounting, particularly for companies with diverse lease portfolios across multiple currencies, lease terms and contract types.

At the same time, the IASB is exploring whether an unchanged discount rate could be permitted for certain remeasurement events, rather than requiring a new rate to be determined at the relevant measurement date. This would address another less visible driver of complexity in subsequent measurement: the need to maintain and trace several different discount rates for the same lease over time.

Which Issues the IASB Is Not Pursuing Following the PIR

Just as informative as the topics selected for further research are the issues raised during the PIR for which the IASB has not decided to take further action at this stage. These include:

  • recognition exemptions,
  • disclosure requirements,
  • the accounting treatment of intragroup leases, and
  • the clarity of the guidance for determining the lease term and discount rate.

The IASB has not decided on additional measures for these matters as part of the PIR. However, this does not mean that professional judgment, particularly regarding lease terms and discount rates, will become less important. Consistent methodologies, well-supported assessments and reliable documentation remain essential.

The point that is often overlooked

Reducing the frequency of remeasurements or allowing an unchanged discount rate can reduce technical and administrative effort, especially where remeasurements are assessed, calculated, documented and reviewed manually. In a largely automated process, however, the recalculation itself accounts for only a small part of the overall workload. The need to identify relevant contract changes and maintain a clear audit trail of the accounting treatment applied remains unchanged.

What Simplification Would Really Mean in Practice

Even if the proposed reliefs were eventually implemented, a substantial part of the process requirements would remain. Less measurement complexity does not mean fewer requirements for complete contract data, consistent assessments and transparent processes.

Area

Current requirements

Potential simplification

What remains unchanged

Remeasurement frequency

A relevant remeasurement trigger can require the lease liability to be recalculated.

Fewer remeasurement triggers and potentially simpler treatment of index- or rate-linked payments. Assessment, processing and documentation activities could therefore occur less frequently.

Contract data and relevant changes must still be captured completely to identify the remaining remeasurement triggers.

Determining the discount rate

An IBR is determined for the relevant lease or portfolio, often involving significant judgment.

A simplified rate could be permitted or required instead of the IBR, potentially reducing the effort involved in determining and documenting discount rates.

The definition, consistent application, and basis for determining the simplified rate would still need to be documented and reviewed.

Discount rate on remeasurement

Depending on the remeasurement trigger, either the existing or a revised discount rate is used.

An unchanged discount rate could be permitted for certain remeasurement events.

Entities must demonstrate which treatment applies to each remeasurement trigger, for each contract and over time.

Five Signs That Today's Complexity Is Already Costing You Money

If several of the following situations apply, subsequent measurement under IFRS 16 is already generating noticeable manual effort, regardless of what the IASB decides in the future:

  1. Multiple discount rates for the same lease are maintained over time in different Excel worksheets, without clear version control.
  2. Whether the discount rate remains unchanged or must be recalculated during a remeasurement depends on the knowledge of individual employees.
  3. Auditors regularly request explanations of how discount rates were determined or why a new rate was not applied to a particular remeasurement.
  4. There is no automated history showing which discount rate applied to which lease, when it applied, and why.
  5. Remeasurement triggers are collected and processed retrospectively in batches rather than being recorded continuously.

What IFRS 16 Software Can Already Address Today

The extent to which fewer remeasurements would actually save costs depends largely on the existing IFRS 16 process. In manual or decentralized workflows, each remeasurement trigger can create additional work: contract changes must be recorded, discount rates assessed, calculations updated, journal entries generated, and supporting documentation prepared. With Envoria, calculations and the resulting IFRS 16 journal entries are generated systematically from the contract data stored in the system. Contract changes and discount rates are retained in a historical record, allowing accounting teams to focus more on assessment, review, and approval.

One point is particularly relevant when evaluating costs: Envoria's pricing is based on the number of contracts or active assets, rather than the number of calculations or journal entries generated from a contract. If an existing lease is recalculated due to an index adjustment, remeasurement, or contract modification, this does not result in additional transaction-based Envoria charges. IFRS 16 journal entries generated from the contract data are not charged separately either.

Potential IASB simplifications could therefore primarily reduce the technical and administrative effort involved in applying IFRS 16. Regardless of these developments, complete contract data, consistent assessments and a transparent change history remain essential.

Manual or decentralized processes

With Envoria

Calculation logic and controls depend heavily on individual files and working methods.

Calculations are derived consistently from centrally stored contract parameters. Technical assessment, review and approval remain the responsibility of accounting teams.

Discount rate determination and historical records are often maintained separately in spreadsheets.

Discount rates and their application can be retained and documented transparently for each lease and measurement event.

Remeasurement triggers must be identified, communicated, and processed manually.

Changes can be recorded through structured workflows and incorporated into subsequent measurement according to defined rules.

Audit evidence must be compiled from different files and versions.

Contract, change and calculation histories can be made available centrally for controls and audit documentation.

Future changes in accounting requirements must be incorporated into individual calculation models.

New measurement logic can be implemented centrally in the system configuration and applied consistently.

Under transaction-based pricing models, additional recalculations or journal entries may result in additional software costs.

Costs are based on the number of contracts or active assets. Recalculations and the resulting IFRS 16 journal entries are not charged separately.

Answers to the Five Most Frequently Asked Questions

1. When will the potential simplifications take effect?

Not yet. The IASB has only added a research project to its project pipeline and has not set a start date. In practice, several years typically pass between such a decision and a binding amendment to an IFRS Accounting Standard, including a discussion paper or exposure draft, a consultation period, and a final Board decision.

2. Do I need to change my process now?

No. The current requirements for discount rates and remeasurements remain in force. However, it makes sense to assess the effort involved in your existing process. Regardless of the IASB project, a reliable, system-supported foundation for contract data and discount rate histories already offers benefits today.

3. Will the incremental borrowing rate be abolished entirely?

No. The discussion concerns whether entities could be permitted or required to use a simplified rate instead of the IBR in certain circumstances, not the complete abolition of the concept. Details of the scope and methodology for determining such a simplified rate are not yet available.

4. Will simplification reduce documentation requirements?

Not necessarily to the same extent as the number of calculations. Fewer remeasurement triggers could reduce assessment, processing and documentation activities. However, the fundamental requirement remains: relevant changes must be identified, and the accounting treatment applied must be clearly justified and documented. The actual level of relief will therefore also depend on how extensively the existing process is automated.

5. What should companies do now?

Establish a reliable, audit-ready foundation for contract data, discount rate determination and change histories, regardless of how IFRS 16 develops in the coming years. This foundation is essential for implementing both today's requirements and any potential future simplifications efficiently.

Why the Greatest Savings Potential Lies in the Process

Even a straightforward five-year lease can generate around 300 journal entries when current/non-current reclassifications are taken into account, without any foreign-currency accounting or contract modifications. Depending on the posting logic, foreign-currency entries can double or triple that number.

The greatest potential to reduce effort therefore lies not only in the IFRS 16 simplifications under discussion, but above all in automating lease accounting. While potential amendments to the Standard could simplify individual measurement and documentation activities, a system-supported process can already reduce the recurring workload associated with calculations, journal entries, reconciliations and controls.

How robust is your IFRS 16 process?

In a no-obligation IFRS 16 process assessment, we jointly review the areas where manual effort and audit risks typically arise: discount rate methodology, remeasurement triggers, change histories, controls and journal entry processes. You will receive a clear assessment of which parts of your current process are already robust and where action is needed, regardless of whether or when the IASB actually implements its proposed simplifications.

→ Request an IFRS 16 process assessment

Conclusion

The completion of the Post-implementation Review sends two clear signals: the IASB remains committed to the fundamental IFRS 16 model, but sees opportunities to reduce ongoing application costs in certain areas of subsequent measurement. Fewer remeasurement triggers and simpler discount rate requirements could primarily eliminate assessment, processing, and documentation effort. However, the actual cost savings will depend largely on how the IFRS 16 process is currently organized and automated.

Until any potential relief takes effect, the situation remains unchanged: companies must maintain complete records of their leases, determine and document discount rates transparently, and reliably identify remeasurement triggers. The same principle will continue to apply in the future: less measurement complexity does not mean lower process quality. In a system-supported process, the recalculation itself can already be largely automated today. With Envoria, there are also no additional transaction-based charges simply because a lease is recalculated or further IFRS 16 journal entries are generated. Complete contract data, consistent assessments, and a transparent change history therefore remain the foundation of reliable and efficient IFRS 16 accounting.
 

Di Maximilian Koch & Stefan Lorenzen