The ASC 842 lease data auditors actually test

The accounting policy for leases is settled at most companies. The classification decisions were made during adoption, the model was chosen, the memo was written and reviewed. What was not settled, and in many portfolios still is not, is the data underneath it. Auditors test inputs, and the inputs come out of lease abstraction rather than out of the policy memo.

ASC 842 under US GAAP and IFRS 16 both require a lessee to recognize a right-of-use asset and a lease liability for most leases, and both have been in effect for years. The operational difference that still matters is that ASC 842 retains a dual lessee classification, operating and finance, which drives expense presentation, while IFRS 16 applies a single lessee model.

For a controller with a large leased footprint, the exposure is not the standard. It is whether the population is complete, whether each abstracted field ties to the executed document, and whether modifications were recognized as events when they happened rather than discovered during a year end walkthrough.

The fields auditors actually test

Testing rarely starts with the model. It starts with a sample of leases and a request to agree the inputs to source. If the commencement date, the term, the payment schedule and the discount rate basis tie to the executed document, the schedule follows as arithmetic. If one of them was typed from a summary spreadsheet nobody can source, the sample expands, and expanding samples are how a routine test becomes a finding.

• Commencement date, which is when the lessor makes the underlying asset available for use, and which often differs from the execution date, the rent start date and the occupancy date on the same lease.
• Term and option assessment, covering the non-cancellable period plus renewal or termination options where exercise is reasonably certain, with the judgment documented rather than inferred from the current schedule.
• Fixed and variable payments, separating amounts included in the liability from variable payments tied to usage or sales, with index-linked escalations captured on their stated mechanics rather than as an assumed percentage.
• Incentives, allowances and initial costs, recording improvement allowances, free rent periods, initial direct costs and prepaid amounts, since each adjusts the right-of-use asset rather than the liability alone.
• Discount rate basis, documenting whether the rate implicit in the lease was determinable and, if it was not, how the incremental borrowing rate was developed, with the inputs and the date it was set.

Each of those is a judgment or a fact that lives in a document. That is why abstraction quality, not calculation, is where audit attention concentrates. The second area is harder, because it asks a question the ledger cannot answer on its own. Is the population complete? A schedule can be correct on every line it holds and still be missing leases.

Embedded leases and where they hide

Both frameworks can capture leases inside contracts that are not called leases. The test turns on whether there is an identified asset and whether the customer holds the right to control its use throughout the period, which generally means directing how and for what purpose the asset is used and obtaining substantially all of the economic benefits from it. Contracts written as services often meet that description.

• Logistics and warehousing agreements. A dedicated warehouse bay, a fixed set of assigned trailers or a named vessel can be an identified asset. A capacity commitment with no specified asset usually is not, so the drafting detail decides it.
• IT and data center contracts. Colocation space, dedicated racks and named hardware behave differently from shared cloud capacity. The question is whether a specific asset was assigned and whether the supplier holds a substitution right it can exercise.
• Manufacturing and tooling arrangements. Equipment placed at a supplier site for your exclusive production, or tooling you effectively control, can carry a lease inside a supply agreement that is priced entirely per unit produced.
• Vendor placed equipment. Analyzers, printers, dispensing units and similar assets installed at no separate charge and recovered through consumable pricing are a recurring source of unrecognized right-of-use assets.
• Advertising, energy and utility contracts. Billboards, dedicated generation capacity and similar arrangements frequently specify a physical asset. Where they do, the service label on the cover page does not settle the accounting question.

A five-step plan for lease data readiness

Step 1, Rebuild The Population From Contracts

Do not start from the lease schedule, because it can only confirm what it already contains. Start from the contract repository, the accounts payable vendor file and the property register, then reconcile to the schedule. The exceptions on that reconciliation are the completeness work, and they are what testing will look for.

Step 2, Standardize The Abstraction Field Set

Define the fields once, with a written definition for each, and abstract every lease into the same structure. Commencement date, term, option dates, payment lines, escalation mechanics, incentives and discount rate basis are the minimum. Shared definitions stop two abstractors from producing two defensible but different answers.

Step 3, Screen Other Contracts For Embedded Leases

Run the identified asset and right to control test across service, logistics, IT and equipment agreements above a threshold. Record the conclusion for every contract screened, including the negative ones. A documented no is evidence, and an undocumented no looks identical to a contract nobody read.

Step 4, Link Every Field To Its Source

Attach the executed document and record the clause or page each abstracted value came from. When a sample request arrives, the answer is retrieved rather than reconstructed. This is also what makes an abstraction reviewable by somebody who did not perform it, which is the point of a second level review.

Step 5, Track Modifications As Dated Events

Amendments, renewals, terminations, option exercises and index resets change the measurement. Route them into the same record as dated events with an owner, so remeasurement lands in the period it belongs to. Modifications found at year end are the most common cause of a late adjustment.

Why the audit finds the gap

Adoption was run as a project. A team abstracted the known leases, the model was built, the memo was approved, and the work was declared finished. What rarely followed was an operating routine, so the portfolio kept moving while the data stopped. New leases signed by regional teams did not reach accounting. Amendments were filed with the property manager. A logistics contract was renegotiated with a dedicated fleet attached. None of that is exotic, and none of it announces itself in the ledger. The gap opens between adoption and the first year somebody tests completeness properly, which is why lease data belongs inside lease lifecycle management rather than a spreadsheet beside it.

The abstraction fields and the evidence behind them

The table below sets out the fields that draw the most attention, what each drives in the measurement, the source that supports it, and the event that forces a revisit. Option and notice dates need the treatment described in a guide to critical-date and lease obligation management, and the portfolio view they feed is covered in a piece on portfolio intelligence for CRE contracting.

The standards have been settled for years, and the arguments worth having are no longer about them. They are about whether the population is complete, whether each field ties to a document somebody can produce on request, and whether the last twelve months of amendments reached the schedule. Those are operational questions with operational answers. One abstraction standard, one linked source for every value, one screening routine for contracts that do not look like leases, and modifications handled as events rather than as year end discoveries.

For related guidance, see Embedded leases under ASC 842, finding them in contracts, What CAM reconciliation demands from your lease data and Ground lease rent reset: why the date needs a plan.

Aavenir Commercial Real Estate PracticeThe Aavenir research team covers lease administration, contract data quality and obligation management across corporate real estate portfolios.