Embedded Leases in Service Contracts: Identification Checklist
Finding embedded leases in service contracts, and booking them correctly, is a key part of ASC 842 compliance. Many companies struggle to tell a service contract from a true lease. That can lead to large misstatements in the financial statements. Auditors watch this area closely. A missed embedded lease can have a material effect on a company's balance sheet, income statement, and statement of cash flows. The main risk is understating right-of-use (ROU) assets and lease liabilities. The same miss can also breach debt covenants and regulatory reporting rules. Getting this right starts with a sound process. To answer "How do I identify embedded leases in service contracts?", you need a set method for contract review and assessment, built on the specific criteria in ASC 842. Understanding ASC 842 lease accounting basics is the first step.
For a complete breakdown, see our lease accounting guide.
Embedded leases in service contracts: identification checklist is the practice of checking service and supply agreements for an identified asset whose use the customer controls. When a contract conveys the right to control the use of an identified asset for a period of time in exchange for consideration, it contains a lease even if it never uses the word (ASC 842-10-15-3). Control means the customer has both the right to substantially all the economic benefits from using the asset and the right to direct its use throughout the period of use (ASC 842-10-15-4). Lease completeness under ASC 842 is not just an accounting exercise. It is essential to the audit, and it bears directly on the accuracy of financial reporting.
What Auditors Check for Embedded Leases
Auditors bring a high degree of skepticism to embedded leases, above all when they review service contracts. Their main goal is to verify that management has sound controls and procedures to ensure the completeness assertion: that all leases, including embedded ones, are identified and recorded. Completeness is one of the assertions management makes in the financial statements: that all transactions and accounts that should be presented are included. The auditor's job is to obtain enough evidence about that assertion, which for leases means testing whether the lease population is whole (PCAOB AS 1105, Audit Evidence, paragraphs .04 and .11). To test it, auditors look at contract populations beyond what is labeled a "lease" agreement. They scrutinize contracts for indicators that convey control over the use of an identified asset for a period of time. This diligence is part of a thorough ASC 842 audit.
The audit process usually involves inquiry, inspection, observation, and recalculation. Auditors evaluate the design and operating effectiveness of internal controls over lease identification. If they find the controls ineffective, they expand substantive procedures. A common procedure is a look-back: select service contracts signed after adoption and check that each was evaluated for an embedded lease. Deloitte's Roadmap lists "identifying the complete population of contracts to evaluate" among the adoption-period internal controls over lease identification, and "determining whether a contract or arrangement meets the new requirements of a lease" among the ongoing ones1. This helps answer "how do auditors test embedded leases in service contracts: identification checklist." Auditors apply substantive testing procedures to verify that all leases are captured.
💡 Key Takeaway: The completeness assertion is one of the most scrutinized areas in an ASC 842 audit. Auditors will not rely on management's assertions alone; they seek independent evidence about them, including evidence that points the other way.
Key Audit Focus Areas for Embedded Leases
| Audit Area | Auditor's Objective | Evidence Requested |
|---|---|---|
| Completeness | Ensure all contracts with embedded leases are identified. | Contract inventory, lease policy, control descriptions. |
| Assessment | Verify proper application of "control" criteria per ASC 842. | Accounting memos, lease classification analysis. |
| Documentation | Confirm sufficient evidence supports identification and accounting decisions. | Lease system data, contract abstracts, management review records. |
| Data Integrity | Evaluate processes for extracting lease data from identified contracts. | System reports, reconciliation of data, control testing results. |
| ROU Asset & Liab. | Validate initial measurement and subsequent accounting for identified leases. | Lease amortization schedules, journal entries, disclosure notes. |
Where Embedded Leases Hide in Service Contracts
A failure to identify and account for embedded leases creates major financial reporting and operational risks. An embedded lease is a lease component inside a larger contract that may not be explicitly identified as a lease. Such a miss can lead to material misstatements, which then require costly restatements or audit adjustments. The effect on debt covenants and credit ratings can be large, because lease liabilities increase under ASC 842.
- Understated Lease Liabilities and ROU Assets: The most direct risk is that lease liabilities and the matching right-of-use (ROU) asset values are left off the balance sheet. This distorts key financial ratios and can give a false view of the company's true financial position. An ROU asset audit is a common focus area for auditors.
- Non-Compliance with ASC 842: A missed lease directly violates ASC 842 requirements. That can lead to audit qualifications or large audit adjustments. It can also damage a company's reputation and draw regulatory scrutiny.
- Ineffective Internal Controls: Weak or missing controls over contract review mean the issue is systemic, not isolated. Auditors will escalate findings tied to control deficiencies.
- Inaccurate Financial Projections: If large obligations sit off-balance sheet, forecasts and budgets will be flawed.
- Increased Audit Scrutiny and Costs: Repeat problems with embedded lease identification will lead to expanded audit procedures and may raise audit fees.
🚨 Critical: A missed embedded lease can result in material misstatement, non-compliance with ASC 842, and higher audit costs. This is a common audit finding, and companies must address it early.
Example Scenario: Undetected IT Service Contract
Scenario: A company enters into a five-year IT outsourcing agreement. The contract states the vendor will manage and operate the company's core servers and network infrastructure, hosted in a specific data center. The company has the exclusive right to use these identified servers and decides how they are used, within set limits. No explicit lease component is stated in the contract.
Risk: Without a careful review for embedded leases, this contract would likely be treated as a service contract only, with payments expensed. But the company controls the use of identified assets (the servers) for a period, so the contract contains an embedded lease. Missing this leaves an ROU asset and a lease liability unrecorded.
Impact: The balance sheet is misstated by hundreds of thousands, or even millions, of dollars, depending on the scale and value of the underlying assets. That is a large audit adjustment. A common failure point is overlooking embedded leases in service contracts.
Practical Checklist for Embedded Lease Discovery
Identifying embedded leases takes a structured approach to contract review. This checklist gives a framework for embedded lease discovery and makes sure every potential lease is evaluated under ASC 842. This helps answer, "Alexa, what's a checklist for identifying embedded leases?"
How to Identify Embedded Leases in Contracts
| Step | Action Item | Key Questions to Ask | Red Flags/Indicators |
|---|---|---|---|
| 1 | Gather all relevant contracts (e.g., IT, logistics, utilities, manufacturing, warehousing). | What types of service agreements does the company typically enter? | High-value, long-term service agreements; contracts involving specific assets. |
| 2 | Does the contract convey the right to control the use of an identified asset? | Is there a specific asset (or assets) explicitly or implicitly identified? | Asset serial numbers, IP addresses, specific locations, asset specifications. |
| 3 | Does the customer obtain substantially all economic benefits from the use of the asset? (ASC 842-10-15-4(a)) | Who uses the asset, and who gains from its primary output (revenue/cost reduction)? | Customer receives product output or service directly from asset. |
| 4 | Does the customer direct the use of the identified asset? (ASC 842-10-15-4(b)) | Who decides "how" and "for what purpose" the asset is used over the period of use? | Customer specifies operating procedures, production schedules, access times. |
| 5 | Is there an identified asset? (Explicitly or implicitly specified) (ASC 842-10-15-9; substantive substitution rights, ASC 842-10-15-10) | Can the supplier substitute the asset? If so, does the supplier benefit economically? | Contract refers to specific equipment, pipelines, servers. Supplier has no practical substitution right. |
This checklist is central to a sound lease identification audit.
✅ Best Practice: Establish an internal "Lease Champion" or a cross-functional team (procurement, legal, accounting, operations) to review contracts with this framework, the same way every time. This gives full coverage and a range of viewpoints.
How to Evidence Your Embedded Lease Review
Validation builds auditor confidence and shows that internal controls are sound. Accounting teams must test and review their lease identification process, above all for embedded leases in service contracts. Doing this early cuts surprises in the annual audit and ensures lease accounting compliance. For more validation steps, see our lease management documentation compliance guide.
- Perform "Look-back" Procedures: Select a sample of new or renewed service contracts from the past year. Review each one as if for the first time, and apply the embedded lease checklist to confirm that identification is complete.
- Document Decision-Making: For every significant service contract, document the analysis behind the conclusion on whether it contains an embedded lease. That record should cite the specific ASC 842 paragraphs that support the conclusion. Per FASB ASC 842-10-15-3, 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.
- Cross-Functional Review: Require a review by staff from procurement, legal, and operations for every high-value or complex service agreement. These people often know things about how the assets are used that accounting may not.
- Leverage Technology: Use lease accounting software that includes embedded lease identification features, or that allows custom flagging and workflows for complex contracts.
- Reconcile Contract Populations: From time to time, reconcile the list of identified leases with raw contract populations from procurement systems, property records, or payment systems. Are any contracts expensing large payments for specific assets that might have been missed?
⚠️ Risk Alert: A common audit finding is a company that overlooked service contracts with large asset components, which led to material misstatements. That is why a thorough review matters.
Common Identification Errors and How to Avoid Them
Even with a detailed checklist, companies often make errors in identifying embedded leases. These mistakes usually come from a weak grasp of the details of ASC 842, or from internal processes that fall short. The result can be audit findings that delay the audit or require material adjustments.
Common Mistakes vs. Best Practices
| Common Mistake | Audit Implication | Best Practice to Avoid |
|---|---|---|
| Focusing only on explicit lease language | Missed embedded leases, understated balance sheet. | Train staff to identify control indicators, not just explicit lease terms. |
| Over-reliance on vendor classification | How the vendor labels or papers the contract is not determinative; an entity determines at inception whether a contract is or contains a lease (ASC 842-10-15-2), and Deloitte's Roadmap: Leases notes that "not all leases will be labeled as such, and leases may be embedded in larger arrangements." | Perform independent analysis of all relevant contracts based on ASC 842 criteria. |
| Ignoring low-value or short-term contracts with embedded components | While individually small, cumulative impact can be material. | Set materiality thresholds for embedded lease reviews, and remember the short-term lease exemption is an accounting policy election made by class of underlying asset (ASC 842-20-25-2): an embedded lease either meets the short-term definition, a lease term of 12 months or less at commencement with no purchase option the lessee is reasonably certain to exercise, or it is recognized. ASC 842 has no low-value exemption. |
| Lack of centralized contract repository | No way to be sure every embedded lease in a service contract has been found. Hard to review the entire population. | Implement a centralized contract management system and standardized review process. |
| Insufficient documentation of conclusions | Auditors cannot verify management's judgments without supporting evidence. | Create detailed accounting memos for each significant contract, clearly outlining the ASC 842 assessment. |
| Inadequate training for procurement and operations teams | Staff are unaware of the need to flag contracts for lease assessment. | Conduct regular training on ASC 842 and embedded lease indicators for all relevant departments. |
💡 Tip: Keep one repository for all contracts, not just those labeled as leases; you cannot review a population you cannot list. PwC makes a related point: identifying embedded leases "often requires broader discussions throughout the organization beyond the accounting function, involving procurement, legal, engineering, manufacturing, IT and more," and a blanket conclusion by arrangement type "may not sufficiently eliminate the risk of an embedded lease"2. This helps address "How do I find embedded leases in service agreements?"
What a Thorough Contract Review Looks Like
Strong execution on embedded leases in service contracts means the needed processes and controls are built into day-to-day operations. Companies that reach this point have smoother audits, fewer adjustments, and more confidence in their financial statements. This approach supports sound lease accounting compliance.
A well-run process usually involves:
- Early Identification: Procurement or legal teams flag potential embedded leases at the drafting stage, which triggers an accounting review.
- Standardized Review: Accounting uses one consistent checklist (like the one above) and written procedures for every new or amended service contract.
- Technology Integration: Use lease accounting software to track and report every identified lease, whatever its source.
- Regular Training: Ongoing training for everyone involved (procurement, legal, operations, accounting) on ASC 842 principles and embedded lease indicators. This makes sure all relevant staff understand "what are the red flags for embedded leases under ASC 842?".
- Internal Audit Review: Internal audit, where it exists, reviews the embedded lease identification process from time to time as part of its control testing program.
This level of rigor ensures that nearly all embedded leases are identified, properly accounted for, and backed by sound documentation. The result is a "cleaner" ASC 842 audit. Companies with strong execution hold quarterly lease reviews and update their contract inventory.
Where to Go From Here on Embedded Leases
To improve how your company handles embedded lease identification, start by reviewing your current contract intake and assessment processes. Consider a cross-functional team devoted to this work, and targeted training for key staff. Acting early on embedded leases will greatly reduce audit risk and improve the accuracy of your financial reporting. Engaging with your auditor early on your approach can give you useful insight and prevent problems later.
Related Articles
- Guide to Embedded Lease Identification
- ASC 842 Audit Readiness Checklist for Controllers
- Understanding ROU Asset Calculations
- Implementing Top 10 Lease Accounting Internal Controls
