Lease modifications are inevitable. Remeasurement headaches aren’t.

Lease contracts change. Tenants renegotiate. Equipment gets swapped. Renewal options get exercised - or quietly dropped.

Every one of those changes is a lease modification under ASC 842. And most of them trigger a remeasurement - meaning your lease liability and right-of-use (ROU) asset need to be recalculated and reposted before close.

Here’s how to handle it without spreadsheet chaos.

What counts as a lease modification

A lease modification is any change to the original terms of a lease contract - payments, term, or the underlying asset itself.

The most common scenarios:

• Extending or shortening the lease term
• Early termination
• Renegotiated payments (up or down)
• Adding or removing leased assets
• Expanding or reducing leased space
• Changes to variable payments (CPI, index, usage)

Each one affects the lease liability, the ROU asset, or both. Misclassify the modification, and your balance sheet tells the wrong story.

Separate lease, or modification of an existing one?

Before you touch any numbers, ASC 842 wants you to answer one question: is this a brand-new lease, or a change to the one you already have?

It’s a separate lease if both are true:

• The change adds the right to use one or more additional assets, and
• The payment increase reflects the stand-alone price of those added assets.

If either condition fails, it’s a modification of the existing lease - which means you remeasure.

This call matters. It decides how the lease liability is recalculated, how the ROU asset is adjusted, which discount rate applies, and what ends up in your disclosures.

How remeasurement actually works

When you’re modifying an existing lease (not creating a separate one), here’s the playbook:

• Identify what changed. Payments, term - pin down the new terms.
• Update the payment schedule. Future payments get recalculated based on the modified contract.
• Apply the revised discount rate. ASC 842 requires the updated rate as of the modification date for most remeasurements.
• Recalculate the lease liability. New liability = present value of the updated future payments.
• Adjust the ROU asset. It moves in line with the liability - unless a termination reduces it directly.
• Post the journal entries. Interest, depreciation, remeasurement adjustments - all need to hit the GL.

Six steps. Sounds manageable. Then multiply it by 40 leases across 5 entities, mid-close, with audit two weeks out.

That’s where spreadsheets break.

Where finance teams lose time (and accuracy)

Manual remeasurement is one of the top sources of close-cycle pain. The usual failure points:

• Wrong discount rate applied
• Payment updates missed or entered twice
• Formulas broken after the third “minor” tweak
• ROU asset and liability out of sync
• Disclosure reports that don’t match the underlying schedules
• No clear record of who changed what, when, or why

None of these are skill problems. They’re tooling problems.

How Onederful handles remeasurement inside Business Central

Onederful is built natively into Microsoft Dynamics 365 Business Central - so modifications and remeasurements happen where your finance data already lives. No middleware. No re-keying. No second system to reconcile.

When a lease changes, Onederful recalculates the lease liability using the revised discount rate and updated payment schedule, adjusts the ROU asset automatically, and posts the updated journal entries straight to your BC general ledger. Your disclosures - maturity analysis, roll-forwards, weighted-average rates - refresh instantly.

Every change is logged in a full audit trail: who changed what, when, and why.

No broken formulas. No version-three-final-FINAL spreadsheets. Just clean numbers, ready for close.

The bottom line

Lease modifications aren’t going away. Neither is the remeasurement work that comes with them.