Closing under ASC 842 without quarter-end surprises
Where lease accounting breaks down at scale, and how to keep every figure traceable to the clause behind it.
ASC 842 turned leases into balance-sheet items, which means a lease error is now an accounting error. Quarter-end surprises, a liability that does not tie out, a schedule that has to be redone, a modification no one booked, almost always trace back to the lease data underneath rather than the accounting itself.
That is the uncomfortable part. You can run a clean close process on bad inputs and produce clean, confident, wrong numbers. The risk is real, and a restatement is expensive in both time and credibility.
Treat lease data as the foundation
Closing without surprises means treating lease data as the foundation it is. The terms that drive the liability, commencement, term, payments, escalations, options reasonably certain to be exercised, have to be accurate and current before close, not reconciled under deadline. That is why a clean close depends on accurate lease abstraction and critical dates upstream, and why a change to a lease needs a disciplined remeasurement rather than a manual scramble.
Frequently asked questions
What causes ASC 842 quarter-end surprises?
- Almost always lease data that is wrong, incomplete, or entered late: a mis-keyed date, a missed modification, an option treated inconsistently. The accounting inherits the error.
How does REAL support ASC 842 and IFRS 16?
- REAL produces the lease accounting these standards require from the structured lease data underneath, so the liability and schedules trace back to verified terms rather than rekeyed inputs.
See REAL run end to end.
Watch a demoRelated posts
A remeasurement checklist for changing leases
The events that trigger a remeasurement, and how to post each one without breaking the audit trail.