Lease accounting standards define a lease by substance rather than by label. A contract contains a lease if it conveys the right to control the use of an identified asset for a period of time in exchange for consideration, and nothing in that definition requires the parties to have used the word lease anywhere in the document.
That produces a recurring problem for finance teams. The real estate and equipment leases are known, they were captured at transition, and they sit in the lease system. The embedded leases are inside contracts owned by procurement, IT, logistics and operations, described as services or supply arrangements, and nobody involved in negotiating them was thinking about right-of-use assets.
This article covers how the identification test actually applies, where embedded leases most often sit, why the substitution right analysis decides most cases, and how to turn a one-time identification exercise into something that keeps working as new contracts are signed.
The identification test, applied practically
The test has a small number of components, and in practice most contracts resolve on one or two of them. Working through them in order is faster than reading the contract for lease-like language.
- Is there an identified asset, specified explicitly or implicitly, which can include a physical portion of an asset such as a defined floor or a dedicated server rack
- Does the supplier hold a substantive substitution right, practical ability to substitute throughout the period and economic benefit from doing so, both of which are required for the right to be substantive
- Who obtains the economic benefits, whether the customer receives substantially all the economic benefits from use of the asset throughout the period
- Who directs the use, whether the customer decides how and for what purpose the asset is used, or those decisions are predetermined and the customer operates the asset
- Is there consideration and a period, an identifiable term and payment, including arrangements structured as usage or throughput charges
The substitution analysis is where most contracts are decided, and it is frequently misapplied. A supplier's contractual right to substitute is not substantive unless it has the practical ability to do so throughout the period and would benefit economically from substituting. Language reserving a right to substitute for maintenance, or only on the customer's consent, generally does not meet that bar, and a supplier that would incur cost to substitute rarely does either. Where the analysis is genuinely uncertain, the standards direct that the customer presumes the substitution right is not substantive if it cannot readily determine otherwise, which resolves a useful number of borderline cases in a practical direction.
An identified asset can be a physically distinct portion of a larger asset: a defined area of a warehouse, a specific floor, a dedicated rack in a colocation facility, a named vehicle in a fleet. Contracts that grant capacity without specifying a physical portion generally do not, which is why the distinction between dedicated and shared capacity is worth reading carefully.
Where embedded leases are usually found
Certain contract types produce embedded leases with enough regularity that a targeted sweep is more productive than reviewing the whole portfolio.
- Logistics and warehousing. Dedicated warehouse space, dedicated trailers or a named vehicle fleet in a transport agreement frequently meet the test even where the contract is priced per shipment.
- IT hosting and colocation. Dedicated racks, cages or specified hardware create identified assets, while shared or burstable capacity generally does not.
- Manufacturing and supply. Supplier agreements where the customer funds or specifies dedicated tooling, production lines or equipment located at the supplier's site.
- Energy and utilities. Power purchase arrangements involving a specified generating facility, and on-site plant installed for a single customer.
- Facilities and outsourced services. Cleaning, catering, security and medical equipment service contracts that include dedicated equipment placed at the customer's premises.
A five-step approach to a repeatable sweep
Step 1, Target the contract population
Rather than reviewing everything, filter the portfolio to the categories that produce embedded leases and to contracts above a value threshold. Category and spend data usually narrow a portfolio of thousands to a few hundred candidates worth reading.
Step 2, Screen on asset language
Search the candidate population for the indicators: dedicated, exclusive use, specified equipment, named facility, capacity reserved, equipment provided on site. This screening pass is where structured contract text search does most of the work a manual review would otherwise consume.
Step 3, Apply the test and document the conclusion
Work the identification test for each candidate and record the reasoning, particularly for contracts concluded not to contain a lease. Auditors ask about the negatives as often as the positives, and an undocumented negative conclusion has to be reperformed.
Step 4, Extract the measurement inputs
For contracts concluded to contain a lease, pull the term including renewal and termination options, the payment structure, any non-lease components requiring allocation, and the information needed to determine the discount rate.
Step 5, Wire identification into contract intake
Add the lease-identification questions to the contract intake process so new and modified agreements are screened at signature rather than in an annual sweep. Modifications matter as much as new contracts, since a scope change can create an identified asset where none existed.
Screen the contract portfolio for embedded lease indicators
Aavenir applies structured search and clause extraction across executed service and supply agreements so the embedded lease population can be identified and documented.
Why the annual sweep approach keeps failing
Most organizations identified their embedded leases once, at transition, through a substantial manual exercise. The population has been changing ever since. New service agreements are signed, existing ones are modified, dedicated equipment is added to arrangements that previously had none, and renewal terms are exercised. An annual sweep catches these late, which produces prior period adjustments and audit findings that are tedious rather than serious but consume disproportionate effort to resolve. Moving identification to the point of contract intake is a modest process change with a large effect, because the person negotiating the contract can answer the asset questions readily and the accounting conclusion can be reached while the facts are available. Organizations already running structured critical-date and lease obligation management generally find the embedded population can sit in the same register as the real estate and equipment leases, which is also where the auditor expects to find it. The connection to lease lifecycle management is direct, since the measurement inputs and the option dates are the same fields.
Contract types and how they usually resolve
The table summarizes how common arrangements tend to resolve under the identification test. It is a screening aid rather than a conclusion, and the specific facts of each contract govern.
| Contract type | Usual determining factor | Typical outcome |
|---|---|---|
| Dedicated warehouse space | Physically distinct area specified | Frequently contains a lease |
| Shared warehouse, capacity only | No identified asset, capacity fungible | Frequently does not |
| Colocation with dedicated racks | Specified racks or cage, no substitution | Frequently contains a lease |
| Cloud hosting, shared infrastructure | Supplier substitutes freely, no identified asset | Frequently does not |
| Supplier-held dedicated tooling | Customer directs use, benefits substantially | Requires close analysis |
Embedded leases are not an exotic technical issue, they are an identification problem in a contract population that most finance teams cannot search. The organizations that handle them without recurring audit friction do two things: they screen at contract intake rather than annually, and they document the conclusions they reach on contracts they decide do not contain a lease. Both depend on being able to find the relevant contracts and read the relevant terms, which is a contract data capability rather than an accounting one. The finance teams that find this manageable are the ones that stopped treating it as a periodic project and started treating it as a screening question attached to contract intake, answered by the person who negotiated the arrangement while the facts are still fresh.
For related guidance, see ASC 842 and IFRS 16, the lease data auditors test, CAM reconciliation and lease audit rights, explained and Ground lease rent reset: why the date needs a plan.
