Of all the operational challenges that IFRS 16 introduces, lease modifications are the one that most consistently catches finance teams off guard.
The initial recognition of a lease, calculating the right-of-use asset and lease liability at commencement, is complex, but it happens once per contract. Teams adapt to it. They build processes around it. They learn the discount rate logic and the payment schedule inputs and the FI-AA integration. After a few months of live operation, inception accounting becomes manageable.
Remeasurement is different. It does not happen on a predictable schedule. It is triggered by events, a rent indexation applied mid-year, a lease extension negotiated with a landlord, an early termination option exercised, a change in the assessment of whether a renewal period will be taken. These events happen continuously, across a portfolio of dozens or hundreds of contracts, at irregular intervals that no finance team can anticipate with precision.
For organisations managing IFRS 16 remeasurement manually or semi-manually, this unpredictability is where the material accounting risk lives. And it is precisely where SAP CLM’s automation delivers its most significant operational value.
Understanding What Triggers a Remeasurement
Before examining how SAP CLM handles remeasurement, it is worth being precise about what actually triggers one under the standard, because this is an area where organisations frequently misapply IFRS 16, either remeasuring when they should not or failing to remeasure when they should.
IFRS 16 requires a lessee to remeasure the lease liability, and adjust the right-of-use asset accordingly, in the following circumstances.
A change in the lease term. If the lessee reassesses whether it is reasonably certain to exercise a renewal option or not to exercise a termination option, and that reassessment results in a change in the lease term, the lease liability must be remeasured using a revised discount rate and the updated payment schedule over the revised lease term.
A change in the assessment of a purchase option. If the lessee’s assessment of whether it will exercise a purchase option changes, this triggers remeasurement of both the lease liability and the right-of-use asset.
A change in amounts payable under a residual value guarantee. Where the expected payments under a residual value guarantee change, the lease liability is remeasured to reflect the updated amounts.
A change in future lease payments resulting from a change in an index or rate. This is the most operationally frequent trigger for most organisations with property lease portfolios. When an index-linked rent review is applied, based on a consumer price index, a construction cost index, or another reference rate, the revised future lease payments must be reflected in a remeasured lease liability. The remeasurement uses the discount rate applicable at the date of the revision, not the original commencement rate.
A lease modification that is not accounted for as a separate lease. Where the scope or consideration of a lease changes in a way that does not qualify for treatment as a separate new lease, the modification triggers remeasurement of the existing liability and a corresponding adjustment to the right-of-use asset.
Each of these triggers has specific accounting consequences. The remeasured lease liability may be higher or lower than the carrying value immediately before the event. The difference adjusts the right-of-use asset, upward if the liability increases, downward if it decreases. Where the downward adjustment exceeds the carrying value of the right-of-use asset, the excess is recognised immediately in profit or loss.
Managing this correctly, across a large portfolio, without automation, is where organisations accumulate accounting errors that are systematic, compounding, and extremely difficult to unwind at year-end.
How SAP CLM Handles Remeasurement Automatically
SAP CLM’s remeasurement architecture is built around the integration with SAP RE-FX. When a contract event occurs in RE-FX, a rent indexation is applied, an extension is agreed, a termination is processed, CLM receives the updated contract data and initiates the remeasurement calculation without requiring manual intervention from the finance team.
The remeasurement process in CLM follows a defined sequence that mirrors the IFRS 16 requirements precisely.
First, CLM identifies the nature of the triggering event and determines the appropriate accounting treatment. A rent indexation linked to a CPI revision is treated differently from a negotiated lease extension, which is treated differently from an early termination. The system applies the correct methodology for each event type automatically, based on the configuration established during implementation.
Second, CLM calculates the revised lease liability. It takes the updated payment schedule from RE-FX, reflecting the new rent amounts, the revised lease term, or whatever change has occurred, and discounts it at the appropriate rate. For index-based remeasurements, this is the discount rate applicable at the date of the revision. For lease term reassessments, it is also the revised rate at the reassessment date. The system holds the discount rate history for each contract and applies the correct rate to each remeasurement event automatically.
Third, CLM computes the adjustment required to the right-of-use asset. The difference between the remeasured lease liability and the carrying value immediately before the event is applied to the asset value in FI-AA. If this adjustment would reduce the right-of-use asset below zero, CLM recognises the excess in profit or loss through the appropriate FI posting.
Fourth, CLM generates all required accounting entries and posts them to SAP FI. The remeasurement entries, adjusting the lease liability, adjusting the right-of-use asset, recognising any profit or loss element, are created automatically and posted to the general ledger without any manual journal entry preparation.
Fifth, FI-AA receives the updated asset value and recalculates the depreciation schedule going forward. The revised carrying value of the right-of-use asset is depreciated over the remaining revised lease term, and the updated depreciation charge is reflected in all subsequent period close runs.
The entire sequence, from the contract event in RE-FX to the updated depreciation schedule in FI-AA, is executed by the system. The finance team receives the outputs. They do not build them.
The Rent Indexation Problem at Scale
Rent indexation is worth examining in more detail because it is the remeasurement trigger that most consistently overwhelms finance teams managing large property portfolios without adequate automation.
In a typical European commercial real estate portfolio, a significant proportion of leases include annual rent review clauses linked to a published index, the French ICC construction cost index, the ILC commercial lease index, the Belgian health index, or a consumer price index in whichever jurisdiction the property is located. These reviews typically apply on the lease anniversary date, although the actual notification of the new rent amount often arrives weeks or months after the review date.
For an organisation with one hundred property leases across five European markets, this means potentially one hundred separate remeasurement events per year, each involving a different index, a different review date, a different current discount rate, and a different remaining lease term. Each event requires a recalculation of the full future payment schedule, a new present value calculation, an asset adjustment, and a set of accounting entries.
Managed manually, this is weeks of work per year, with significant exposure to calculation errors, inconsistent discount rate application, and missed events where the rent revision notification was not processed in time for the period close.
In SAP CLM, each indexation event is processed as follows. RE-FX applies the updated rent condition based on the new index value. CLM detects the change in the payment schedule, identifies it as an index-based remeasurement, retrieves the current discount rate, recalculates the lease liability, adjusts the right-of-use asset in FI-AA, and generates the accounting entries. The finance team reviews the output. They do not perform the calculation.
At scale, across a large portfolio with multiple indexation events occurring throughout the year, this automation is not simply a matter of efficiency. It is the difference between a lease accounting process that is reliably compliant and one that is not.
Multi-Standard Reporting: IFRS, FR-GAAP and US-GAAP in Parallel
For European enterprises that report under multiple accounting frameworks, IFRS for consolidated group reporting, French GAAP or another local standard for statutory entity reporting, SAP CLM provides parallel accounting treatment within the same system.
This is architecturally significant. Without this capability, organisations must either maintain separate systems for each reporting framework or perform manual adjustments to translate IFRS lease accounting into local GAAP at each period close. Both approaches introduce reconciliation risk and manual effort.
CLM’s multi-ledger architecture allows a single contract to generate accounting entries simultaneously under multiple standards. The IFRS 16 treatment, right-of-use asset and lease liability on balance sheet, is produced for the IFRS ledger. The local GAAP treatment, which in French GAAP, for example, continues to treat operating leases as off-balance-sheet commitments with straight-line expense recognition, is produced for the local ledger. Both sets of entries are generated automatically from the same contract data in RE-FX.
For group finance teams managing consolidation across multiple European entities with different statutory reporting requirements, this parallel treatment eliminates one of the most time-consuming manual reconciliation tasks in the period close cycle.
Building the Audit Trail That External Auditors Actually Need
One final dimension of SAP CLM’s remeasurement architecture deserves attention: the audit trail it generates as a natural output of the automated process.
External auditors examining IFRS 16 compliance need to be able to trace every right-of-use asset and lease liability carrying value back to the contract data and calculations that produced it. For remeasured contracts, they need to understand what triggered the remeasurement, what discount rate was applied, what the revised payment schedule was, and how the adjustment to the right-of-use asset was determined.
In a manual or semi-manual process, assembling this evidence is a significant year-end exercise. Spreadsheets must be retrieved, calculation assumptions must be documented, and the link between contract events and accounting entries must be reconstructed.
In SAP CLM, every remeasurement event is logged with a complete record of the inputs, the calculation methodology, and the outputs. The accounting entries are directly traceable to the contract event that triggered them. The discount rate applied to each remeasurement is recorded against the event. The adjustment to the right-of-use asset is linked to both the remeasurement calculation and the corresponding FI-AA posting.
Audit readiness is not a preparation exercise. It is a permanent state of the system.
Lumveris specialises in SAP CLM and RE-FX implementation for IFRS 16 compliance across European enterprises. If your organisation is managing lease modifications manually or operating with a CLM implementation that is not performing as expected, contact us for a diagnostic assessment.
