IFRS 16, the lease accounting standard that brought operating leases onto the balance sheet, has been in effect since January 2019. Seven years on, a remarkable number of companies are still calculating their right-of-use assets and lease liabilities manually — or semi-manually, using spreadsheets that have grown to alarming complexity. Each quarter, the finance team extracts lease data from various sources, feeds it into a calculation model, reconciles the output against last quarter, and produces the disclosures. The process consumes days of senior finance time and is brittle in ways that only become apparent when something changes.

What IFRS 16 actually requires

The standard requires lessees to recognise almost all leases on the balance sheet as a right-of-use (ROU) asset and a corresponding lease liability. The lease liability is the present value of future lease payments, discounted at the incremental borrowing rate. The ROU asset is initially measured at the amount of the lease liability, adjusted for any prepayments, incentives received, and initial direct costs.

Over the lease term, the liability is unwound using the effective interest method, and the asset is depreciated. This sounds straightforward for a single lease. For a portfolio of 50 or 200 leases, each with different terms, currencies, indexation mechanisms, and modification histories, the calculation becomes a significant workload.

The key data inputs for each lease are:

  • Lease commencement and end dates (including any reasonably certain extension options)
  • Fixed lease payments (rent, guaranteed service charges)
  • Variable payments linked to an index (CPI-linked rent reviews, open-market reviews)
  • Discount rate (the rate implicit in the lease, or the company’s incremental borrowing rate)
  • Lease modifications (any amendments to the original terms)
  • Currency (for multi-currency portfolios, FX rates at commencement and at reporting date)

Where the manual process breaks

The manual calculation process is fragile at several points:

Lease modifications

When a lease is modified — a rent review is settled, a break option is exercised or waived, a term is extended — the IFRS 16 calculation must be remeasured. This requires determining whether the modification is a separate lease or a reassessment of the existing one, recalculating the liability at the revised discount rate (for reassessments) or the rate at modification date (for separate leases), and adjusting the ROU asset accordingly.

In a spreadsheet model, this is error-prone. Each modification requires manual intervention, and the accumulation of modifications over several years creates a complex audit trail that is difficult to verify.

Index-linked reviews

Many European leases include rent indexation linked to CPI or a similar index. Under IFRS 16, the liability is initially calculated using the index at commencement. When the index changes and the payment adjusts, the liability is remeasured using the revised payments and the original discount rate. For a portfolio with dozens of indexed leases, each reviewing at different dates with different indices, this is a significant quarterly calculation.

Discount rate changes

The incremental borrowing rate is not static. It reflects the company’s cost of borrowing, which changes as interest rates move. When a lease is reassessed (for example, when evaluating whether an extension option is reasonably certain), the discount rate must be updated. Maintaining current discount rates by currency, tenor, and entity is a non-trivial exercise in itself.

Currency translation

For companies reporting in a currency different from their lease currencies, the ROU asset (a non-monetary item) is translated at the historical rate, while the lease liability (a monetary item) is translated at the closing rate. The resulting translation difference flows through other comprehensive income. Getting this right for every lease at every reporting date requires disciplined tracking of historical and current rates.

The structured data advantage

Every one of these pain points traces back to the same root cause: the calculation model is disconnected from the source data. Lease terms live in PDFs, abstractions live in spreadsheets, and the IFRS 16 model is yet another spreadsheet that must be manually synchronised with both.

When lease data is structured — stored in a database with defined fields for every relevant term, date, and amount — the IFRS 16 calculation becomes a function of the data, not a separate process. A modification is recorded once, in the lease record, and the liability and asset are automatically recalculated. An index-linked review is updated when the new index is applied, and the remeasurement flows through without manual intervention.

This is not a theoretical benefit. The practical impact is:

  • Quarterly close reduced from days to hours — the calculations run automatically from the current lease data
  • Modification handling becomes routine — record the modification, the system recalculates
  • Audit trail is built-in — every change to the source data and its impact on the IFRS 16 figures is logged
  • What-if modelling is possible — should we exercise this break option? What is the balance sheet impact?

The lease data you need for IFRS 16 is the same data you need for portfolio management. Structuring it once serves both purposes.

Discount rate management

One area that deserves specific attention is discount rate management. The incremental borrowing rate is a critical input — small changes in the rate produce meaningful changes in the liability figure. Best practice is to maintain a discount rate matrix by currency and lease tenor, updated at least quarterly, with documentation of the methodology used to determine each rate.

When this matrix is maintained within the portfolio platform, it can be applied automatically to new leases and reassessments. The alternative — manually looking up and applying rates for each calculation — is both slower and more error-prone.

Connecting IFRS 16 to portfolio decisions

The most valuable consequence of automating IFRS 16 is that it enables the balance sheet impact to be considered in real-time portfolio decisions. Should we extend this lease for three years or relocate? What is the balance sheet impact of exercising versus waiving this break option? If we consolidate these two sites into one, what happens to our total lease liability?

When the IFRS 16 calculation is a manual quarterly exercise, these questions cannot be answered in the flow of decision-making. They require a separate modelling exercise, which means they are often not asked until late in the process. When the calculation is automated and connected to the portfolio data, the balance sheet impact is available as one input among many, as it should be.

IFRS 16 compliance is not optional, but the pain it causes is. The standard has been in force long enough that the manual workarounds should be retired. Structured lease data and automated calculations turn a quarterly burden into a continuous, reliable output that serves both finance and RE teams.