ASC 842 lease abstraction for lease accounting

ASC 842 measures a lease liability as the present value of the remaining lease payments, and a right-of-use asset built from that liability adjusted for prepayments, incentives, and initial direct costs. Everything in those two calculations comes out of the lease document. The abstraction step is what turns a 90 page contract into the handful of inputs the model needs.

Classification runs on five tests, and any single one being met makes the lease a finance lease: transfer of ownership at the end of the term, a purchase option reasonably certain to be exercised, a lease term covering the major part of the asset's remaining economic life, a present value of payments amounting to substantially all of the asset's fair value, or an asset so specialized it has no alternative use to the lessor. ASC 842 removed the bright lines that Topic 840 used, though many companies still apply the old 75% and 90% thresholds as a documented policy.

For real estate this matters less often than people expect. Most commercial property leases stay operating leases, because the term rarely covers the major part of a building's economic life and the payments rarely approach its fair value. The classification work concentrates in ground leases, build-to-suit arrangements, and leases with bargain purchase options, and those are exactly the ones where the abstract needs to carry the option language verbatim rather than a summary.

The test that most often decides a borderline lease is the fourth one, and it is decided by the lease term you feed it. A renewal option judged reasonably certain of exercise extends the term, which raises the present value of payments, which can push a lease across the substantially-all threshold on its own. Our guide to operating lease vs finance lease classification works a dollar example where exactly that happens, with the resulting difference in first-year expense and the effect on EBITDA.

The lease term under ASC 842 is the non-cancellable period plus any renewal option the lessee is reasonably certain to exercise, plus any period covered by a termination option the lessee is reasonably certain not to exercise. Reasonably certain is a high threshold, and it is an economic test rather than an intention: significant leasehold improvements with remaining useful life, a below-market renewal rate, relocation costs, and the importance of the location all push toward inclusion.

Practically, this is where abstraction and accounting have to meet. The abstractor records every option, its rate mechanism, and its notice deadline. The accountant decides which ones are reasonably certain. An abstract that flattens an option into a single line without the rate mechanism forces the accountant back into the PDF, which is where the reassessment work in most implementations gets stuck. Our renewal options page covers what to capture.

The term also has to start somewhere, and that is the other place implementations go wrong. ASC 842 runs the term from the date the asset is made available for use, which is frequently months earlier than the date the lease calls rent commencement. Getting that anchor wrong shifts the straight-line expense, the measurement date, and every option deadline derived from it, as the guide to the lease commencement date versus the rent commencement date works through with a dollar example.

A tenant improvement allowance is a lease incentive when the improvements are lessee assets, and it reduces the right-of-use asset. It is never netted against the leasehold improvement balance, which stays capitalized at gross cost and amortizes over the shorter of its useful life or the remaining lease term. When the improvements are lessor assets, meaning the landlord owns and controls the finished build-out, money the tenant spends is effectively a receivable from the landlord rather than a fixed asset of its own, and the allowance settles it. The determining question is ownership and control of the resulting asset, which the lease and the work letter answer, not the size of the allowance.

The timing matters too. An allowance paid at or before commencement reduces the ROU asset directly. One receivable later is included in the measurement as a reduction of payments. Unused portions that are forfeited, which is common, need to be recorded so the model is not carrying an incentive that never arrives. The wider family of lease incentives under ASC 842 follows the same timing rules, with the notable exception that a free rent period is not an incentive at all. Our tenant improvement allowance page goes deeper on the accounting treatment.

Almost every ASC 842 implementation runs late for the same reason: the lease population is larger and messier than the register suggested. Embedded leases inside service contracts, month to month arrangements that have run for years, and equipment schedules sitting with operations rather than finance all belong in scope and rarely appear in the accounting system.

The sequence that works, set out step by step in our ASC 842 implementation guide, is to build the complete population first, then abstract against a fixed field list, then measure. Abstracting before the population is settled means doing it twice. Abstracting without a fixed field list means each lease comes back with a different level of detail, and the gaps only surface during audit. A source-linked abstract solves the third problem, which is evidence: when an auditor asks why the term is 87 months, the answer should be a clause reference rather than a spreadsheet note.

Whichever platform you land on, the leases arrive through a structured import template, and nothing in that template fills itself. Accounting tools such as EZLease, FinQuery, and Crunchafi all assume the abstraction already happened, which is why the data entry line is the one most often missing from an implementation budget.

Expect requests for the lease document itself, the extraction of the inputs used, the discount rate and its support, the classification memo for anything not obviously operating, and the judgment support for every option included in or excluded from the term. The last one causes the most rework, because reasonably certain conclusions reached two years ago are rarely documented well enough to defend later.

Source-linking is what makes this cheap. If every input in the schedule carries a page and clause reference, the audit request becomes a lookup instead of a re-read across a portfolio of leases. That is the practical case for abstracting once, properly, at the start of an implementation rather than field by field as questions arrive.