ASC 842 lease accounting, closed with audit-grade governance.
For a CPA or advisory firm running an outsourced lease-accounting practice, the hard part of ASC 842 isn’t the standard — it’s holding a decentralized, multi-unit portfolio together: hundreds of leases, each with its own commencement date, discount rate, embedded-equipment terms, and a modification history that keeps triggering remeasurement. Aurgus keys every balance to the source event that produced it — so the trail back to why a right-of-use asset changed is queryable, not reconstructed by hand at quarter-end.
Note: Aurgus isn’t an “ASC 842 module.” It’s a governed-calculation substrate — immutable events, supersession rather than overwrite, replayable lineage — and that pattern is what makes a lease close defensible the same way it makes a rebate close defensible. The product is the substrate; the compliance is what it enables. If your firm already runs this practice, the conversation starts with how your current trail holds up under review.
The standard is settled. Holding the portfolio together is the work.
For a firm serving multi-unit retail, restaurant, or franchise clients, the risk in ASC 842 lives in the population and its changes — not in the textbook treatment. Five places the manual close gives way.
- The lease population is never complete on the first pass. Store leases, equipment schedules, and embedded leases buried inside service and supply contracts all have to be found and abstracted. A contract that never says the word "lease" can still convey the right to control identified equipment — and still needs a right-of-use asset.
- Lease and non-lease components have to be split. Rent, common-area maintenance, and service elements travel together in one contract; ASC 842 requires allocating consideration between them on a relative standalone-price basis unless the combine expedient is elected. Doing that consistently across a decentralized portfolio is where consistency slips.
- Modifications keep triggering remeasurement. A term extension, a rent concession, a space reduction — each can force a remeasurement of the ROU asset and liability. When the trail of which modification drove which balance lives in spreadsheet tabs, "why did this number move?" becomes a reconstruction project.
- Overwriting the prior figure loses the history. When a schedule recalculates, overwriting last period's number erases the record of what was carried and why. Supersession — a new event that references the one it replaces — keeps the full chain. A workbook, by default, overwrites.
- The client’s auditor wants the trail, lease by lease. Classification, discount rate, the modification that moved the balance, the component allocation — reviewers increasingly want to see it reproducibly per lease, not explained in aggregate narrative at quarter-end.
Lineage as a property of the data model — not a quarter-end pass.
The same governed-calculation pattern that defends a rebate close defends a lease close: every figure is keyed to the event that produced it, from abstraction onward.
- 1
Each lease enters as a recorded abstraction event.
Commencement date, term, classification, discount rate, the lease and non-lease components, and the component allocation are captured as the originating event — with the source contract behind it. An embedded lease found inside a service contract enters the same way, on its own record.
- 2
Remeasurements post as events that supersede, never overwrite.
A modification — extension, concession, space change — posts a remeasurement event that supersedes the prior schedule and references the modification that drove it. The original stays on the log. The chain of what the balance was, why it moved, and what replaced it is fully traceable.
- 3
Operator approval is a first-class event.
Every judgment — a classification call, a discount-rate selection, a remeasurement sign-off — is captured as an Approval event with the preparer’s reasoning and the source-cited rationale. Your firm’s review is documented as it’s made, not reconstructed after.
- 4
The lineage chain is machine-readable, lease by lease.
From a period balance, click through to the remeasurement, then to the modification, then to the source contract. Export it. Your client’s auditor gets a queryable dataset per lease, not a binder of tabs.
- 5
Replayable end-to-end.
Re-run any lease schedule against its source inputs and get the same result. The deterministic engine returns the same number for the same inputs, every time. Reproducibility is the review standard; Aurgus is built around it.
Most lease workpapers hold the numbers — but not the trail behind them.
Honest comparison of what an outsourced lease-accounting practice typically uses, and where each falls short of a reproducible, lease-by-lease trail.
The numbers live. The history overwrites.
Amortization and liability schedules in a workbook produce the figures, but the last recalculation overwrites the one before it. When the auditor asks why a balance moved, the answer is rebuilt from memory and tabs — not read off a trail.
Produces balances. Not a per-event chain.
Dedicated tools compute ROU assets and liabilities well, but a period export is a snapshot. Re-running it after a modification may give a different figure, and the link from a balance back to the specific modification that drove it is often not queryable.
Expert. Periodic. Not a substrate.
An outside specialist can review methodology and sign off once a year. That review can’t be the calculation substrate that makes every balance self-documenting as the portfolio changes through the year.
Lineage as the data model.
Every abstraction, every remeasurement, every approval is written with its full chain at the moment it occurs — superseding, never overwriting. Replayable, queryable, machine-readable, lease by lease. The trail isn’t a quarter-end project; it’s the byproduct of running the close.
ASC 842 lease accounting, honestly answered.
- What makes ASC 842 lease accounting hard for multi-unit retail or restaurant portfolios?A decentralized portfolio can carry hundreds of leases across locations, each with its own commencement date, modification history, and embedded-equipment terms — tracking classification, discount rate, and remeasurement triggers across all of them by hand is where ASC 842 compliance breaks down.
- What is an embedded-equipment lease under ASC 842?An embedded lease exists when a service or supply contract conveys the right to control use of identified equipment for a period of time, even though the contract is not labeled a lease — ASC 842 requires identifying and accounting for that right-of-use asset and liability regardless of the contract’s title.
- How should lease and non-lease components be split for ASC 842?ASC 842 requires separating the lease component (the right-of-use asset) from non-lease components like maintenance or common-area services, allocating the contract’s consideration between them on a relative standalone-price basis unless the practical expedient to combine them is elected.
- How do firms track ongoing ASC 842 lease modifications across a decentralized portfolio?Each modification — a term extension, a rent concession, a space reduction — can trigger remeasurement of the right-of-use asset and liability; a calculation-native close keys every remeasurement to its source modification event so the trail back to why a balance changed is queryable, not reconstructed by hand. See also how Aurgus builds an audit trail.
Other places the same governed-calculation trail holds up.
Discuss your ASC 842 lease portfolio.
A working session with someone who understands what a decentralized lease population does to an outsourced close. No pitch. We map how your current trail — abstraction, remeasurement, approval — holds up when your client’s auditor asks why a balance moved.