ASC 842 & IFRS 16 Compliance: A Complete Guide to AI-Powered Lease Accounting
ASC 842 and IFRS 16 changed lease accounting from a footnote exercise into a balance sheet obligation, and most facilities and finance teams are still paying for that change in spreadsheet hours. This guide covers what the standards require, where manual processes break, and what AI document processing realistically automates. We write it as operators: our own facilities company runs its lease portfolio on the same module we license, and one of our own renewal dates once hid on page 87 of a lease.
What the standards actually require
ASC 842 (US GAAP) and IFRS 16 (international) both require organizations to bring most leases onto the balance sheet:
- Leases longer than 12 months must be recorded
- A right-of-use (ROU) asset is recognized for each lease
- Lease liabilities require present value calculations against a discount rate
- Under ASC 842, operating versus finance classification changes how expense hits the P&L
- Modifications, renewals, and impairments require recalculation, not just a note
The accounting itself is well documented. The operational pain is upstream of the accounting: getting accurate data out of the lease documents and keeping it current.
Where manual lease accounting breaks
Extraction
Commercial leases run 50 to 200 pages, written to be precise rather than findable. Commencement dates, renewal options, escalation clauses, CAM terms, and termination rights are scattered through legal language and amended by later documents. Manual abstraction is slow, and a single missed date can mean an unwanted auto-renewal or an unbudgeted escalation.
Calculation
Present value math is unforgiving of small errors: discount rate selection, payment timing, and modification accounting all compound. A spreadsheet maintained by one person becomes a single point of failure that auditors increasingly refuse to accept.
Maintenance
The portfolio is not static. Every amendment, exercised option, and impairment test reopens the numbers. Quarterly close becomes a recurring archaeology project into documents nobody wants to reread.
What AI actually automates
Document reading
This is the highest-value application of AI in the entire lease workflow. Document processing extracts dates, terms, payment schedules, and obligations from PDFs into structured fields, with page references back to the source so a human can verify any extraction in seconds. Verification matters: the honest workflow is AI extracts, human confirms, system alarms. The documents themselves live alongside the data in a searchable repository, so an auditor's question is answered by a link, not a hunt.
Schedules and entries
Once lease data is structured, amortization schedules, ROU asset values, and liability balances are generated rather than maintained: modifications trigger recalculation, and journal entries carry an audit trail by construction.
Dates that defend themselves
Renewal windows, escalation triggers, and termination options become alarmed notifications months before the decision deadline. This is the feature that pays for everything else, because the only way to win a lease decision is to know it is coming.
Why this belongs next to facilities data, not in a silo
Standalone lease accounting tools treat the lease as a finance document. It is also an operating document: it says who fixes the HVAC, what the landlord owes, and which costs are recoverable. When lease terms live in the same system as work orders and space utilization, the questions that actually save money become answerable. Should we renew this floor? What is this building really costing per occupied seat? Is this repair ours or the landlord's? That cross-visibility is the argument for lease compliance inside one operating platform rather than another disconnected tool.
A realistic implementation sequence
- Inventory every lease and amendment, including the embedded leases hiding in service contracts
- Load documents and let extraction propose the data; verify against the source page by page
- Configure accounting policies, discount rates, and approval workflows with your accounting team
- Generate opening balances and run parallel with the old process for one close
- Turn on date alarms portfolio-wide, then retire the spreadsheet
For most mid-size portfolios this is weeks of focused work, not a multi-quarter project. The slow step is almost always assembling the documents, which says something about the problem being solved.
Frequently asked questions
Do we still need accountants if the calculations are automated?
Yes, for the judgment: discount rates, classification calls, impairment triggers, and policy decisions stay human. What disappears is the transcription and spreadsheet maintenance between those judgments.
How accurate is AI lease extraction?
Good systems are accurate enough to draft and never trusted enough to skip verification. The design question to ask any vendor is whether every extracted field links back to the source page, because that is what makes verification fast and audits painless.
We are a facilities team, not finance. Why should we care about ASC 842?
Because the data is the same. The renewal date finance needs for the liability calculation is the date you need to renegotiate or exit. Sharing one verified record means neither team gets surprised, and the facilities side often catches operational terms, like maintenance obligations, that a pure finance review skips.
If your lease portfolio still lives in a spreadsheet and a filing cabinet, talk to an operator. Worst case, you leave the call with a list of dates you should go look up.