Embedded Leases: How to Spot One in a Contract
Not every lease has the word 'lease' on the front page. A logistics agreement, a data-hosting contract, or a supply deal with a manufacturer can all contain one, buried in the small print. Under ASC 842 and IFRS 16, a contract contains a lease the moment it conveys the right to control the use of an identified asset for a period of time in exchange for payment. That test applies to the whole contract, regardless of what it's called.
This matters because an embedded lease that nobody spots doesn't just vanish. It sits quietly off the balance sheet until an auditor, a new finance hire, or a lender's due-diligence team finds it, usually at the least convenient moment. The good news is that finding one isn't guesswork. There's a clear, repeatable process, and this guide walks through it step by step.
- An embedded lease can hide inside a service, supply, outsourcing or hosting contract that never uses the word 'lease'
- Two tests decide it: is there an identified asset, and does the customer control how it's used
- Contracts for dedicated vehicles, power plants, servers and production lines are the most common places embedded leases turn up
- Software subscriptions usually aren't leases, but dedicated hosting and colocation deals sometimes are
- Once you confirm a lease exists, you separate it from the service elements and measure it like any other lease
Step 1: Work out which contracts are worth reviewing
You don't need to re-read every contract in the filing cabinet. Start by pulling a list of active contracts above your capitalisation or materiality threshold, then filter for the ones that involve an ongoing supply of a physical asset or dedicated capacity, rather than a one-off purchase.
The categories that turn up embedded leases most often are fairly predictable: transportation and logistics agreements, power purchase agreements, IT hosting and colocation deals, managed print or equipment services, security or facilities contracts, and manufacturing supply agreements with take-or-pay terms. If a contract runs for more than 12 months, involves recurring payments, and gives you the use of something physical to do your business, it belongs on the review list.
A quick screen: does the contract mention a specific piece of equipment, a dedicated site, a fixed number of units, or exclusive access to capacity? If yes, move it to step 2. If the supplier is clearly just selling you a generic, interchangeable service, like a standard courier delivery or a shared-tenancy cloud subscription, it's probably not worth the deeper dive.
Step 2: Apply the identified asset test
For a contract to contain a lease, there has to be an identified asset. That means the asset is either explicitly named, for example by serial number, registration plate or a specific server rack, or implicitly identified because the supplier has no practical way to fulfil the contract except by using that particular asset.
The test has one important escape hatch: substitution rights. If the supplier can swap the asset for another one at any point, and that right is substantive rather than just theoretical, then there's no identified asset and the contract isn't a lease. A substantive substitution right means the supplier could actually benefit economically from swapping the asset, and is practically able to do so throughout the contract.
In practice, the difference is stark. A contract that says 'the supplier will deliver goods using a dedicated fleet of ten trucks, registration numbers listed in Schedule A' points towards an identified asset. A contract that says 'the supplier will deliver goods using vehicles from its general fleet as operationally required' almost certainly doesn't, because the supplier has genuine flexibility over which vehicle turns up.
Step 3: Apply the control test
Finding an identified asset only gets you halfway. The second test asks whether the customer controls how that asset is used throughout the period of the contract. Control has two parts, and both need to be true.
First, the customer needs the right to obtain substantially all the economic benefits from using the asset over the contract term. Second, the customer needs the right to direct how and for what purpose the asset is used, deciding things like the operating parameters, the output produced, or when and where it runs. Rights that only protect the supplier's investment in the asset, such as maintenance standards or safety limits, don't count as control on their own.
A useful shortcut: if the supplier decides how the asset gets used and simply delivers an output or outcome to you, that points towards a service. If you decide how it gets used and the supplier just keeps it running, that points towards a lease. Plenty of real contracts sit somewhere in between, which is exactly why this step needs a proper, documented judgement rather than a quick guess.
Step 4: Work through the classic real-world examples
Four scenarios come up again and again in embedded-lease reviews, and it's worth knowing them by heart. A logistics contract with a dedicated fleet of delivery trucks reserved solely for one customer's routes. A power purchase agreement tied to output from a specific power plant or a named set of turbines. A data-centre colocation or dedicated-server hosting contract where particular racks or machines are reserved exclusively for one customer, rather than pooled across a shared, multi-tenant environment. And a manufacturing take-or-pay supply contract that runs off one dedicated production line rather than general factory capacity.
Here's how this plays out in practice. Picture a mid-sized software company that signed a three-year hosting agreement with a data-centre provider several years ago, filed it under 'IT operating expenses', and never thought about it again. During a year-end audit, the auditor asks to see the contract and notices it names specific server racks reserved exclusively for the company, with no right for the provider to move the workload elsewhere without consent. The company directs exactly how those servers are configured and used. That's an identified asset plus control: an embedded lease, sitting inside a line item everyone assumed was a straightforward service cost. The finance team now has to go back, measure a right-of-use asset and lease liability for the remaining term, and correct prior disclosures.
That scenario is more common than it sounds, especially with IT and hosting arrangements. It's also precisely the grey area regulators have flagged as an ongoing sticking point: recent post-implementation review work on IFRS 16 found real application issues around scope for intangible assets like software licences and cloud services, and around telling a lease apart from an in-substance purchase. This isn't a problem that only existed when the standards were new; it's still catching finance teams out today.
Step 5: Separate the lease and measure it properly
Once you've confirmed a contract contains a lease, the next job is unbundling it. Most contracts with an embedded lease also include genuine service elements, maintenance on the trucks, IT support on the servers, staffing on the production line, and those need to be split out from the lease component. The usual approach allocates the total contract consideration between the lease and non-lease components based on their relative standalone prices, though a practical expedient exists to combine them if you'd rather account for the whole thing as a single lease.
After that split, the lease component is treated exactly like any other lease. You work out the lease term, pick a discount rate (often the incremental borrowing rate if the rate implicit in the lease isn't readily available), calculate the present value of the lease payments, and recognise a right-of-use asset and lease liability on the balance sheet. You'll also need to classify it as operating or finance under ASC 842, or determine the appropriate treatment under IFRS 16, and build out the amortisation schedule and journal entries from there.
It's worth checking the short-term lease exemption too, since some embedded leases, particularly shorter service contracts, may qualify for simplified treatment if the remaining term is under 12 months at the point you identify them.
Run the numbers on your calculator
Once you've confirmed an embedded lease and worked out its term and payment stream, the fastest way to see the accounting impact is to run it through the free calculator. Enter the lease payments, term and discount rate, and it will build the right-of-use asset, lease liability, amortisation schedule and journal entries for you, so you can see exactly what needs to go on the balance sheet before you finalise the write-up.
| Test | Key question | Contract is probably NOT a lease if... |
|---|---|---|
| Identified asset test | Is a specific, physical asset named or implied in the contract, with no substantive right for the supplier to swap it out? | The supplier can substitute the asset at will, and that right is real, not just written into the small print |
| Control test | Does the customer get substantially all the economic benefit from the asset, and decide how and for what purpose it's used? | The supplier decides how the asset is used, or the customer's rights are limited to protecting the supplier's investment |
Frequently asked questions
Can a service contract be a lease?
Yes. Under both ASC 842 and IFRS 16, the label on a contract doesn't matter. What matters is whether it conveys the right to control the use of an identified asset for a period of time in exchange for payment. A contract titled 'managed services agreement' or 'logistics services contract' can contain an embedded lease if it hands the customer control over a specific truck, server or production line, even though the word 'lease' never appears.
What is the identified asset test?
It's the first of two tests used to work out if a contract contains a lease. An asset is identified if it's explicitly named in the contract (by serial number, location or another specific reference) or implicitly identified because the supplier only has one way to fulfil the contract. If the supplier holds a substantive right to substitute that asset for another one at any time, and would actually benefit from doing so, the asset isn't identified and the contract can't be a lease.
Do software and cloud computing contracts count as leases?
Sometimes, and this is exactly where companies are getting tripped up right now. The IASB's Post-Implementation Review of IFRS 16 found ongoing application issues around whether certain contracts fall within scope, particularly for intangible assets such as software licences and cloud computing services, plus the challenge of telling a lease apart from an in-substance purchase. Most SaaS subscriptions aren't leases because there's no identified physical asset, but a dedicated hosting or colocation arrangement tied to specific servers can be.
What happens if a company misses an embedded lease?
The lease liability and right-of-use asset simply go unrecorded, which understates both assets and liabilities on the balance sheet. When auditors or a new controller catch it later, the fix is usually a prior-period adjustment or restatement, plus reworking every affected disclosure. Our piece on ASC 842 restatements and what went wrong walks through how these errors tend to surface and what they cost to unwind.
How is an embedded lease different from a fully separate lease contract?
Mechanically, it isn't, once you've found it. The extra step with an embedded lease is separating the lease component from the non-lease service elements in the same contract, usually by allocating the contract price based on standalone prices. After that split, the lease component is measured, classified and disclosed exactly like any lease you signed on purpose.
Sources
Compute this lease for real
Free, no account required. Get the right-of-use asset, lease liability, full amortization schedule, journal entries and disclosures — every number cited.