Lease Accounting - Modifications is where ERP discipline either begins or breaks.
Lease Modification and Remeasurement looks operational from far away. In a real finance team, it is a chain of assertions: the right actor started the work, the required records existed, the control policy was applied, the state change was preserved, and the outcome can be explained later without rebuilding the transaction from emails and spreadsheets.
The expected business outcome is specific: Lease modifications reflected in balance sheet within the period of modification; amortization schedule accurate from modification date forward; no restatement of prior periods for a non-retrospective modification.
The control flow a finance team actually needs.
Step 1
Modification Workflow Requires Approval...
Step 2
Determines Separate-Lease Vs...
Step 3
Remeasurement Uses Revised IBR At...
Step 4
Catch-Up Journal Posts Atomically With...
Step 5
Prior Period Schedules Remain Intact...
The ERP surface involved.
Module
Lease Accounting - Modifications
Actors
Lease Administrator, Controller, ERP System
Tier
Tier 2
Finance area
Fixed Assets & Lease Management
Region lens
US and UK finance teams
Publication date
June 12, 2026
Modification workflow requires approval before remeasurement posts; system determines separate-lease vs modification-of-existing per ASC 842-20-45 criteria (scope increase + proportionate payment increase = separate); remeasurement uses revised IBR at modification date; catch-up journal posts atomically with schedule regeneration; prior period schedules remain intact and auditable; modification history log with before/after lease terms retained; remeasurement report shows old vs new liability and ROU asset.
US and UK teams have different compliance hooks, but the same control problem.
US teams usually care about clean evidence for audit support, vendor records, payment controls, tax reporting, and management review. UK teams usually care about VAT-ready records, approval evidence, digital-record discipline, and traceable postings. The country-specific details differ, but the operating pattern is the same: the ERP needs controlled records, explicit ownership, defensible state changes, and evidence that survives beyond the person who completed the task.
The control matrix.
| Control area | Requirement | Acceptance proof |
|---|---|---|
| Control 1 | Modification workflow requires approval before remeasurement posts | Given an active lease in ACTIVE status and a modification event (extended term, revised payments, updated IBR |
| Control 2 | system determines separate-lease vs modification-of-existing per ASC 842-20-45 criteria (scope increase + proportionate payment increase = separate | when the lease administrator submits the modification after controller approval |
| Control 3 | remeasurement uses revised IBR at modification date | then the system determines modification type (separate lease vs modification of existing), remeasures PV of remaining payments at revised IBR, adjusts lease liability and ROU asset atomically, posts a catch-up JE, regenerates the amortization schedule from modification date, and retains the prior schedule as locked history |
| Control 4 | catch-up journal posts atomically with schedule regeneration | negative) when a modification is submitted without controller approval then the system rejects with 403 APPROVAL_REQUIRED. |
| Control 5 | prior period schedules remain intact and auditable | Lease modifications reflected in balance sheet within the period of modification; amortization schedule accurate from modification date forward; no restatement of prior periods for a non-retrospective modification. |
| Control 6 | modification history log with before/after lease terms retained | Lease modifications reflected in balance sheet within the period of modification; amortization schedule accurate from modification date forward; no restatement of prior periods for a non-retrospective modification. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | A lease term is extended by mutual agreement or a new lessee option becomes reasonably certain. The lease administrator enters the modification effective date and revised terms (new lease end date, revised payments, updated discount rate). The system identifies the modification type: scope increase treated as separate lease vs. modification of existing lease. For modifications not treated as separate leases, the system recalculates the revised present value of remaining payments using the revised discount rate, adjusts the lease liability to the new PV, and adjusts the ROU asset by the same amount, posting a catch-up journal entry. The amortization schedule is regenerated from the modification date forward. |
| Control rules | Modification workflow requires approval before remeasurement posts; system determines separate-lease vs modification-of-existing per ASC 842-20-45 criteria (scope increase + proportionate payment increase = separate); remeasurement uses revised IBR at modification date; catch-up journal posts atomically with schedule regeneration; prior period schedules remain intact and auditable; modification history log with before/after lease terms retained; remeasurement report shows old vs new liability and ROU asset. |
| Acceptance proof | Given an active lease in ACTIVE status and a modification event (extended term, revised payments, updated IBR); when the lease administrator submits the modification after controller approval; then the system determines modification type (separate lease vs modification of existing), remeasures PV of remaining payments at revised IBR, adjusts lease liability and ROU asset atomically, posts a catch-up JE, regenerates the amortization schedule from modification date, and retains the prior schedule as locked history; (negative) when a modification is submitted without controller approval then the system rejects with 403 APPROVAL_REQUIRED. |
| Data record | |
| System event | |
| Lifecycle state | |
The useful version of this workflow is not only fast. It is inspectable. A controller, auditor, or operator should be able to move from source event to system record to state transition to final business outcome without guessing.
Implementation contracts.
Reference data model
`lease_modifications` { id: string, external_id: string, lease_id: string, modification_date: date, modification_type: enum(SEPARATE_LEASE,MODIFICATION_OF_EXISTING), revised_end_date: date, revised_ibr: decimal, old_liability_minor: int64, new_liability_minor: int64, old_rou_asset_minor: int64, new_rou_asset_minor: int64, currency_code: char(3), catch_up_je_id: string, approved_by: string, status: enum(PENDING_APPROVAL,POSTED) }; related `lease_amortization_schedule`; (reference, product may differ).API and events
`POST /v1/leases/{id}/modifications` { modification_date, revised_end_date, revised_payment_schedule, revised_ibr, modification_type, external_id } -> 201 { id, status: PENDING_APPROVAL }; `POST /v1/lease-modifications/{id}/approve` -> 200 { status: POSTED, catch_up_je_id }; `GET /v1/leases/{id}/modification-history`; emits `lease.modified` event; idempotent via `external_id`.State transitions
`PENDING_APPROVAL -> POSTED`; guard: posting remeasures liability + ROU asset atomically; prior amortization periods locked; schedule regenerated from modification_date; POSTED is irreversible within closed periods.Common implementation traps.
Treating the workflow as data entry
If the ERP only stores the final record, the team loses the decision trail that explains how the record became valid.
Hiding exception logic
Exceptions need owners, reason codes, and time stamps. A vague pending state is not a control.
Posting without recovery design
Retries, duplicate submissions, and partial failures must be explicit so the system does not create inconsistent records.
Skipping evidence design
A workflow that cannot produce evidence on demand will eventually push finance teams back into manual screenshots and spreadsheets.
Where Rivane fits.
Rivane is built for finance workflows where automation must stay tied to source documents, approvals, state transitions, ledger impact, reporting, and audit evidence. Use this guide as a checklist for evaluating whether an ERP workflow is merely digitized or actually controlled.
References and source basis.
These sources provide the standards, regulatory, or government context around the flow. They are included so the guide is useful to finance operators, auditors, and implementation teams, not only buyers reading software copy.