Lease accounting standards moved most leases onto the balance sheet, and the implementation projects that followed concentrated, reasonably enough, on the population everyone could see. Real estate leases, vehicle fleets and equipment schedules were abstracted, modeled and loaded. The work was substantial and it is largely complete in most organizations.
What remains open is the population nobody sent to lease accounting, because the agreements are not called leases and do not sit with the real estate or fleet teams. A managed services contract that dedicates specific servers. A logistics agreement with named trailers. A supply agreement where the vendor installs equipment on your site for your exclusive use. Each of these can contain a lease, and each is usually owned by procurement or IT rather than by finance.
The consequence is a completeness issue rather than a measurement issue, and completeness is what auditors test. This article covers the identification tests, where embedded leases actually hide, and how to make identification a routine part of contract review rather than a periodic sweep.
The identification test in practice
Both frameworks ask whether a contract conveys the right to control the use of an identified asset for a period in exchange for consideration. That resolves into a small number of questions that can be applied consistently during contract review.
- Is there an identified asset, specified explicitly or implicitly, including a physically distinct portion of a larger asset, such as a defined floor, a specific line or named units of equipment.
- Does the supplier have a substantive substitution right, the practical ability to substitute alternative assets throughout the period and an economic benefit from doing so, which if genuinely present means there is no identified asset.
- Who obtains the economic benefits, whether the customer receives substantially all of the economic benefits from use of the asset throughout the period of use.
- Who directs the use, whether the customer decides how and for what purpose the asset is used, or whether those decisions were predetermined and the customer operates the asset or designed it in a way that predetermines use.
- Is there a defined period of use, the term over which the right applies, which may be expressed in time or in units of output rather than as a lease term.
The substitution question is where judgment concentrates. Suppliers frequently have a contractual right to substitute that is not substantive in practice, because the asset is installed at the customer site, configured for the customer, or would cost the supplier more to swap than to leave in place. A right that exists on paper but that the supplier would not rationally exercise does not defeat the identified asset condition.
Auditors rarely challenge the measurement of a lease that has been identified. They challenge whether the population is complete. An organization that can describe the process by which non-lease contracts are screened, and evidence that it ran, is in a materially better position than one presenting a schedule with no stated method.
Where embedded leases usually hide
These categories account for most of what organizations find when they look systematically.
- Data center and hosting arrangements. Dedicated racks, cages or specified physical servers can meet the identified asset test, while genuinely shared cloud capacity typically does not. The distinction is whether the asset is physically distinct and dedicated.
- Managed services with dedicated equipment. Print, imaging, laboratory and diagnostic arrangements where the vendor installs named equipment at your site for your exclusive use are among the most common findings.
- Dedicated logistics and transport. Agreements specifying named trailers, vessels, railcars or a dedicated fleet, particularly where the customer schedules the assets, frequently contain leases.
- Supply agreements with dedicated production capacity. Where a supplier dedicates a specific line or facility to one customer and that customer takes substantially all the output, the identified asset and benefits conditions can both be met.
- Energy and utility arrangements. Power purchase and on-site generation agreements involving a specific plant or installation require careful analysis, as the outcome turns on output rights and control of operation.
A five-step identification process
Step 1, Screen at contract intake, not at year end
Add lease screening questions to the contract review process so new agreements are assessed when they are signed. Retrospective sweeps are expensive and they repeat every period.
Step 2, Write a decision tree, not a policy statement
Convert the identification tests into a short sequence of yes or no questions that a contract reviewer without accounting training can apply, with a referral path for anything ambiguous.
Step 3, Target the legacy sweep by category
Rather than reviewing every historical contract, prioritize the categories above and any agreement above a value threshold with a physical asset component. That focuses effort where the findings concentrate.
Step 4, Record the conclusion and the reasoning
For every screened contract, record whether a lease was identified and why. The negative conclusions matter as much as the positive ones, because they are the evidence that the population is complete.
Step 5, Re-screen on modification
A contract modification can create, change or terminate an embedded lease. Tie re-screening to the amendment process, which is where critical date and lease obligation management already tracks change.
Screen contracts for embedded leases at intake
Aavenir routes lease screening into contract review and holds the conclusion, the reasoning and the evidence on the record.
Why this is a contract data problem more than an accounting one
Lease accounting teams are not short of technical capability. What they are short of is visibility into agreements owned by other functions, which is a contract management problem with an accounting consequence. The organizations that handle this well do two things. First, they push the screening question upstream into the contract intake process, so the assessment happens once, at the point where someone is already reading the agreement, rather than becoming a periodic project. Second, they keep the asset-relevant attributes on the contract record itself, including whether an identified asset exists, the period of use, the consideration allocated to lease and non-lease components, and any renewal or termination options that affect the term. Once those attributes exist as data, the accounting population is a query and the completeness evidence is a byproduct rather than a separate exercise. That is the same argument for structuring lease data generally, set out in lease lifecycle management.
Applying the test to common arrangements
The table below shows how the tests typically resolve. It is illustrative rather than determinative, and the specific terms of each agreement govern the conclusion.
| Arrangement | Identified asset | Control of use | Typical outcome |
|---|---|---|---|
| Shared public cloud capacity | No, capacity is fungible | No | Usually not a lease |
| Dedicated cage or named servers | Often yes, physically distinct | Depends on operating rights | Frequently a lease |
| Vendor equipment placed on your site | Yes, specified units | Usually yes, exclusive use | Frequently a lease |
| Dedicated trailers or railcars | Yes if named or effectively fixed | Yes if customer schedules them | Frequently a lease |
| Output from a shared production line | No, unless a line is dedicated | Usually no | Usually not a lease |
Embedded lease identification is a completeness exercise that depends on seeing agreements owned by procurement, IT and operations rather than by finance. Screening at intake, recording the reasoning for both positive and negative conclusions, and holding the asset attributes on the contract record turns a recurring year-end scramble into a routine step. The wider case for treating lease data as portfolio intelligence is made in modernizing CRE contracting.
For related guidance, see ASC 842 and IFRS 16, the lease data auditors test, What CAM reconciliation demands from your lease data and Ground lease rent reset: why the date needs a plan.
