A remeasurement checklist for changing leases

A lease is not a static document. Tenants amend them, exercise options, add or surrender space, and renegotiate payments, and under ASC 842 and IFRS 16 many of those events require the lease liability and the right-of-use asset to be remeasured. Get the remeasurement right and the books stay clean. Handle it informally and the gap surfaces later, usually at audit, as a correction nobody budgeted for.

This piece covers when a change triggers a remeasurement, why classification drives everything, the checklist to run on each change, and why the discipline depends on the underlying data.

When a change triggers a remeasurement#

The common remeasurement triggers under ASC 842 are predictable: a lease modification, a change in the lease term, a change in the assessment of whether an option is reasonably certain to be exercised, a change in an index or rate that drives payments, and certain reassessments of residual value guarantees. Each requires the inputs behind the liability to be revisited. Miss a trigger and the schedules quietly diverge from the contract.

Classification drives the treatment#

Not every change is a modification, and the label matters. A change can be a modification, a reassessment of an existing lease, or, in some cases, a separate new lease, and the three are accounted for differently. Treating a separate new lease as a modification, or booking a payment change without reassessing the discount rate, produces a number that looks fine and is wrong. Classifying the change correctly is the step that most often gets skipped under time pressure.

The checklist#

Run the same steps on every change, so nothing depends on memory:

1. 01Capture what changed, with the source. Tie the change to the amendment or notice that caused it, so the remeasurement is traceable.
2. 02Classify it. Modification, reassessment, or separate new lease. The classification determines the accounting.
3. 03Reset the affected inputs. Update term, payments, the discount rate where required, and any option assessments the change affects.
4. 04Regenerate the schedules and entries. Recompute the liability and right-of-use asset and the resulting journal entries.
5. 05Document the judgment. Record why the change was classified as it was, since the judgments are exactly what auditors test.
6. 06Keep the calculation and the document together. Store the amendment and the remeasurement as one record for audit.

Why the checklist depends on the data#

A checklist only works if the change is caught and the starting data is right. A renewal that became reasonably certain has to be noticed before it can be remeasured, which is the same lease intelligence that drives a clean ASC 842 close. When the change involves a tenant improvement allowance or other incentive, the remeasurement and the TIA recovery draw on the same lease data.

REAL ties each change to the source amendment, updates the affected inputs and regenerates the schedules, and keeps the calculation and the document together, so a modification is handled as a controlled remeasurement rather than discovered later as a restatement.