What is ongoing ASC-842 compliance and why is it harder than implementation?
ASC-842 requires that every lease modification, renewal, termination, and new lease is accurately reflected in right-of-use asset and lease liability balances — continuously, not just at go-live. For any organization with an active portfolio, this means a steady stream of accounting events that need to be captured, assessed, and recorded correctly. Most operators complete implementation successfully and then underestimate what it takes to maintain compliance from that point forward.
The ASC-842 implementation is done. The transition journal entries are recorded. The right-of-use assets are on the balance sheet. Auditors have signed off. After months of preparation, data migration, and testing — you can exhale.
Except you can't, quite. Because ASC-842 compliance isn't a project that ends at go-live. It's an ongoing operational requirement. And the complexity doesn't reduce after implementation — in some ways, it increases, because the standard has to be maintained through every lease event that happens from that point forward.
After implementation, the standard requires that every lease modification, renewal, termination, and new lease is reflected accurately in your right-of-use asset and lease liability balances. That sounds straightforward. In practice, it means:
In a portfolio with active lease management — where leases are being amended, extended, new locations added, and acquisitions integrated — this is a continuous stream of accounting events. Not a once-a-year update.
What we observe in most post-implementation environments is a gradual drift between the operational lease record and the ASC-842 accounting record. Leases get amended operationally but the accounting treatment lags. New locations open and aren't reflected in the compliance system for months. Renewal options get exercised without triggering the required remeasurement.
The drift is usually unintentional. It happens because real estate is moving fast and accounting is stretched thin, and the handoff process between the two isn't robust enough to catch every event that creates an accounting consequence.
At audit time — or when a transaction requires clean, auditable financial statements — the gap becomes visible. And cleaning it up retroactively is significantly more expensive and time-consuming than maintaining it properly from the start.
In many organizations, ongoing ASC-842 maintenance is effectively nobody's primary job. The implementation consultant is long gone. The real estate team doesn't think of lease changes in accounting terms. The accounting team doesn't always have the operational context to know when a lease event creates an accounting consequence.
The answer is usually a hybrid model — operational lease management that's tightly integrated with the accounting team, with a clear handoff process for every event that creates an accounting consequence. That process needs to be designed, documented, and consistently followed. Left to emerge naturally, it usually doesn't.
Here it is, plainly: accounting purchases an ASC-842 platform that real estate can't actually use operationally. The platform is configured for compliance output — journal entries, disclosures, rollforward schedules — but it doesn't support the day-to-day operational workflows that real estate actually needs to manage leases.
The result: real estate maintains their own separate record in whatever system they're comfortable with, accounting maintains the compliance platform, and they reconcile periodically — which is to say, imperfectly and reactively. The compliance record is always somewhat behind the operational reality.
The solution is a lease management model where operational and compliance functions are aligned from the start, not bolted together after the fact. When the same data that real estate uses to manage leases flows cleanly into the accounting treatment, both sides win.
If your ASC-842 implementation was completed in the last one to three years, it's worth asking honestly: how well has the standard been maintained since go-live? Is every lease event being captured and reflected correctly? Is the accounting team getting what they need from the operational team without significant friction?
If the answer to any of those questions is uncertain, a post-implementation review is a worthwhile investment. The cost of finding and correcting drift proactively is significantly lower than the cost of cleaning it up when an audit or transaction forces the issue.
Frequently Asked Questions
Does ASC-842 compliance require ongoing work after implementation?
Yes. Every lease amendment, renewal, termination, new lease, and change in option probability creates an accounting event that must be assessed and potentially recorded. For active portfolios, this is a continuous process — not an annual update.
What is "drift" in ASC-842 compliance?
Drift is the gradual gap that opens between the operational lease record and the ASC-842 accounting record when lease events aren't captured promptly. It typically happens because real estate is moving fast and the handoff process to accounting isn't robust enough to catch every event with an accounting consequence.
Who is responsible for ongoing ASC-842 maintenance?
In most organizations, it's effectively nobody's primary job — which is exactly the problem. The answer is usually a hybrid model with a clear, documented handoff process between operational lease management and accounting, triggered by every event that creates an accounting consequence.
What's the most common post-implementation mistake?
Purchasing a compliance-oriented platform that real estate can't use operationally. The result is two parallel records — one in the compliance platform, one in whatever system real estate is comfortable with — that get reconciled imperfectly and reactively. The compliance record is always behind.
How do I know if my ASC-842 compliance has drifted?
Ask: has every lease amendment since go-live been assessed for accounting impact? Has every renewal exercised triggered a remeasurement? Are new locations being classified and measured from day one? If any of those answers are uncertain, a post-implementation review is the right next step.