Understanding Lease Population Completeness: A Complete Guide for Accounting Professionals
Introduction
For controllers and accounting managers, lease population completeness is more than a procedural step. It is a core requirement for accurate financial reporting under ASC 842.
The lease population is every contract that is or contains a lease under ASC 842's definition (ASC 842-10-15-3). Completeness is the work of showing that each one has been identified, evaluated and recorded in the financial statements. A missed lease can produce a material misstatement, closer audit scrutiny, and significant restatement risk.
ASC 842 audit procedures put heavy weight on validating this completeness. The auditor's primary question is: are all leases on the books? If not, the financial statements will not accurately show the company's assets and liabilities, and that leaves a compliance and reporting gap. The effect goes beyond the balance sheet, to key financial ratios and compliance with debt covenants.
Lease population completeness is therefore vital for credible financial reporting. It drives the reliability of every lease accounting calculation that follows, from right-of-use asset recognition to lease liability measurement.
What is lease population completeness under ASC 842?
Q: How do auditors check if all leases are accounted for under ASC 842? A: Auditors verify lease population completeness by performing substantive procedures involving contract review, inquiry with management, and analytical procedures to confirm that all lease agreements within the scope of ASC 842 have been properly identified, classified, and recorded in the financial statements. This includes both explicit and embedded lease discovery.
How Auditors Test the Lease Population
Auditors approach lease population completeness with a skeptical mindset. They focus on the assertions of completeness and accuracy. Their goal is to confirm, with their own evidence, that management has a sound process for identifying all lease agreements, not just those labeled as leases. That means learning the different ways the entity buys goods and services, and the types of contracts it signs.
Grant Thornton describes a two-step approach to finding embedded leases. First, identify and train the lease owners across the business, so every group that negotiates a lease is cataloged. Then, in Grant Thornton's words, "perform a completeness check by searching accounts payable for recurring payment streams."1 Auditors also look for evidence that the process is applied the same way in every department that can sign a binding agreement.
Key Audit Focus Areas for Lease Completeness
| Audit Focus Area | Auditor's Objective | Evidence Requested |
|---|---|---|
| Policy & Procedures | Understand the process management has set for identifying leases and accounting for them. | Lease accounting policy, process flowcharts, training documentation. |
| Population Data Integrity | Verify that the lease data provided is sound and complete. | Lease schedules, reconciliations to general ledger, data extraction reports. |
| Embedded Leases | Confirm that the process finds leases that are not obvious. | Sample of service contracts, procurement agreements, IT contracts, supply agreements. |
| New & Terminated Leases | Ensure proper accounting for changes in the lease portfolio during the period. | New contract register, termination notices, modifications log. |
| System Controls | Evaluate how well the control activities over lease data capture work. | System access logs, control narratives, evidence of periodic management review. |
⚠️ Risk Alert: A common audit finding is that management does not know how each part of the business buys. Different departments may have their own authority to sign contracts, which raises the risk of unrecorded leases. Auditors will ask about these decentralized arrangements.
Auditors perform lease audit procedures to validate disclosures and calculations. They trace a sample of identified leases to the general ledger and to supporting documents. They also perform reverse testing: reviewing vendor invoices or general ledger accounts for payments that might point to an unrecorded lease. This work is how they assess the risk of an incomplete lease population, and whether management's controls have reduced that risk enough.
Where Leases Go Missing From the Population
Several factors can put lease population completeness at risk. Each can lead to material misstatements and more audit time.
Decentralized Procurement: Departments such as IT, fleet management and facilities may sign contracts on their own, with no central review for lease components. When they do, the chance of an unrecorded lease rises sharply. For example, a marketing department might sign a contract for event space that includes a long-term right-of-use. That is an undisclosed lease.
Lack of Training on ASC 842 Scope: The people who negotiate and review contracts need to know what counts as a lease under ASC 842. If they are not trained well enough, they may miss embedded leases in service or supply agreements. This often causes problems in the ROU asset audit.
Over-reliance on "Lease" Label: It is a critical error to assume that only contracts titled "Lease Agreement" contain a lease component. Many service contracts can contain an embedded lease. Common examples are IT contracts (data center capacity, cloud infrastructure) and transportation contracts (dedicated freight services). In IT arrangements the line matters. ASC 842-10-15-1(a) puts leases of intangible assets outside Topic 842. A right to use software is not a lease. Dedicated servers or data center space can be an identified asset.
Inadequate Data Aggregation: Companies that run several ERP systems, or track contracts by hand, may struggle to pull every contract into one full review. That leaves blind spots in their lease population.
Screening Example: Identifying Potential Embedded Leases
Scenario: A company enters into a five-year service contract for dedicated trucking services to transport goods between its distribution centers. The contract specifies a particular fleet of trucks to be used exclusively for the company's deliveries for the entire contract term. The company also has the right to direct when and where the trucks operate within the agreed routes.
| Component | Value (Illustrative) | Calculation |
|---|---|---|
| Contract Value (5 years) | $1,500,000 | $300,000 per year for dedicated trucking services. |
| Identified Asset | Fleet of Trucks | The contract specifies an identified fleet of trucks. Supplier does not have a substantive right to substitute (ASC 842-10-15-9; ASC 842-10-15-10). |
| Right to Direct Use | Yes | The company directs the use, schedule, and routes of the trucks. |
| Benefit from Use | Yes | The company obtains substantially all the economic benefits from the use of the trucks throughout the contract term. |
| Lease Component Indication | Strong | Presence of an identified asset with the company having the right to direct its use and obtain substantially all benefits, despite being structured as a "service" contract. This would likely be an embedded lease. |
Key Takeaway: This screening example shows that a service agreement that looks simple can contain an embedded lease. Contract titles do not decide the question. ASC 842-10-15-2 requires an entity to determine at inception whether a contract is or contains a lease. ASC 842-10-15-3 supplies the test. A contract is or contains a lease if it conveys the right to control the use of identified property, plant, or equipment for a period of time in exchange for consideration.2 That test, not the title on the cover page, is what management must apply and what the auditor will look for.
🚨 Critical: Missing an embedded lease can cause a material misstatement that understates both ROU assets and lease liabilities (ASC 842-20-25-1). That can lead to significant audit adjustments and possible restatements. It is a primary driver of common lease population completeness audit findings.
Practical Checklist or Framework
To ensure lease population completeness, controllers should follow a structured approach. The framework below helps you identify, catalog, and keep monitoring lease agreements over time.
How to ensure lease completeness for ASC 842 compliance?
Q: What's the process for ensuring all leases are included for ASC 842? A: Ensuring all leases are included for ASC 842 involves a multi-step process: inventory contracts across every department, search the ledger for recurring payments, review service contracts for embedded leases, and reconcile the result to the lease system.
- Centralize Contract Review: Assign one owner to review all new and existing contracts for lease components.
- Define Scope Broadly: Train staff to look beyond traditional lease agreements and find embedded lease discovery components in service or supply contracts.
- Leverage Technology: Use lease accounting software to hold contract data in one place, automate calculations, and simplify reporting.
- Regular Reconciliation: On a set schedule, reconcile your lease portfolio to general ledger accounts, vendor payment reports, and fixed asset registers.
- Cross-functional Collaboration: Build regular contact between procurement, legal, facilities, IT, and accounting.
This proactive approach is the base of strong lease identification audit practices.
| Checklist Item | Description | Status | Evidence |
|---|---|---|---|
| 1. Comprehensive Contract Inventory | Build one master list of all contracts in every department: service agreements, rental agreements, software licenses, and procurement contracts. | [In Progress/Done] | Centralized contract database, spreadsheet register |
| 2. Lease Definition Application | Apply the ASC 842 lease definition to every contract, the same way each time, to identify explicit and embedded leases. | [In Progress/Done] | Documented decision tree analysis for each contract, memo for complex cases |
| 3. General Ledger Review | Review general ledger accounts (rent expense, equipment rental, software subscription, transportation expense) for recurring payments that may point to a lease not yet identified. | [In Progress/Done] | GL detail reports, analysis of unusual or significant payments, reconciliation of GL accounts to lease schedule |
| 4. Inquiries with Functional Leads | Interview key people in procurement, IT, facilities, and operations. Ask about the contracts they manage and any rights to use assets. | [In Progress/Done] | Interview notes, questionnaires, list of interviewed personnel |
| 5. Cross-Referencing | Compare the identified lease population against fixed asset registers, insurance schedules, and property listings. | [In Progress/Done] | Reconciliation reports, variance explanations |
| 6. Documentation of Exceptions/Conclusions | For each contract you conclude is not a lease, document why you excluded it. | [In Progress/Done] | Exclusion memos, contract summaries with non-lease conclusions |
✅ Best Practice: Companies that do this well hold quarterly lease reviews and keep teams from across the business involved. This ongoing monitoring cuts the risk of missed leases sharply and strengthens lease accounting compliance.
For more on this, see Preparing for ASC 842 Audits.
How to Evidence a Complete Population
Validating lease population completeness is an ongoing process, not a one-time event. Accounting teams must do more than identify the leases. They must also show auditors that the process they used is sound and reliable.
- Process Documentation: Write down the step-by-step method for identifying leases: who is responsible, what systems are used, and what criteria you apply. This roadmap is what lets auditors understand the "how."
- Internal Control Testing: Put in place internal controls built to ensure lease population completeness, and test them on a set schedule. These could include controls over new contract intake, periodic review of vendor master files, or a required lease assessment checklist for procurement.
- Regular Reconciliation: Reconcile the identified lease population to the relevant general ledger accounts (rent, equipment rental) and to vendor payment records, on a regular basis. This helps you spot any recurring payment not tied to an existing lease.
- Management Review: Senior accounting management should review the completeness assertion on a set schedule, often by signing off on the lease schedule or summary reports. This adds one more layer of oversight and accountability.
The completeness assertion is management's representation that all transactions and accounts that should be recorded have been included in the financial statements. Auditors test it; they do not take it on faith. To satisfy it, accounting teams should prepare their documentation in advance. Management's representations alone are not enough. Corroborating evidence is essential.3
ASC 842's Master Glossary defines a right-of-use (ROU) asset as "an asset that represents a lessee's right to use an underlying asset for the lease term." Identifying all leases accurately directly affects the initial measurement and subsequent accounting for these assets and their related liabilities.
Common Completeness Gaps and How to Close Them
Auditors often find the same issues in companies that struggle with lease population completeness. Knowing these common pitfalls helps accounting teams strengthen their processes in advance.
What documentation is required for lease population completeness?
Q: How do I document lease population completeness for an audit? A: Documenting lease population completeness requires a comprehensive approach. You need copies of all identified lease contracts, a summary of non-lease conclusions, general ledger reconciliation reports, interview notes from critical personnel, and process narratives detailing how you identify and track leases. Additionally, lease accounting software reports and exception logs are essential.
| Common Mistake | Best Practice | Audit Impact |
|---|---|---|
| 1. Assuming "No Lease" Means No Lease | Search every service, supply, and procurement contract for embedded leases, not just the ones labeled as leases. | ROU assets and lease liabilities are understated. Significant audit adjustments follow. |
| 2. Siloed Contract Management | Put in place one central contract management system or process that requires a review for lease components in every department (IT, Facilities, etc.). | Leases missed in some departments leave the population incomplete. Auditors will widen their scope to other departments, which adds audit time and cost. |
| 3. Lack of Definition Training | Train procurement and operations staff on the ASC 842 definition of a lease, especially how to identify identified assets and control. | Staff miss lease components without meaning to, which leads to material omissions. This often flags a significant control deficiency. |
| 4. Inconsistent Use of Lease Accounting Software | Make sure every identified lease is entered in the lease accounting software and kept current there, with a formal review process. | Manual spreadsheets or uneven data entry cause errors, missing leases, and reconciliation problems. That weakens the reliability of the lease data. |
| 5. Ignoring Short-Term Leases for Completeness | Short-term leases may qualify for an accounting policy election, but they must still be identified for proper classification and disclosure (ASC 842-20-25-2; disclosure of short-term lease cost under ASC 842-20-50-4(c)). | Short-term leases that are not identified drop out of the population entirely. They may then be misclassified as operating expenses with no proper disclosure, a common area of auditor inquiry. |
| 6. No Formal Review of GL Accounts for Unknown Leases | On a set schedule, review general ledger expense accounts for recurring payments that point to unrecognized leases (for example, steady payments to an equipment provider). | Payments on leases no one has identified cannot be told apart from non-lease expenses. That makes it impossible to ensure a complete lease population or satisfy the lease accounting compliance assertion. |
💡 Key Takeaway: Identifying leases in advance, backed by a sound internal control framework, is far more efficient and far cheaper than fixing gaps during the audit. These points underpin every successful lease accounting compliance program.
What a Complete Lease Population Looks Like
Companies that excel in lease population completeness show a clear commitment to ASC 842 from the top down. They build lease identification into their core business processes, rather than treating it as a once-a-year accounting exercise.
Consider an illustrative example, a multinational manufacturer that took a phased approach:
- Centralized Contract Repository: They invested in a digital contract management system and uploaded every contract to it, whatever its type. That made keyword searches and central review possible.
- Cross-Functional Task Force: They set up a dedicated task force with members from legal, procurement, facilities, IT, and accounting. It met quarterly to review new contracts and to analyze large existing service agreements for embedded leases.
- Standardized Checklist: They built a sound "lease vs. service" checklist, aligned with ASC 842 guidance, into the procurement system. Any contract above a set threshold triggered this review automatically.
- Automated Reconciliation: They linked their lease accounting software to their ERP system. That allowed automated reconciliation of lease payments to the general ledger, and any discrepancy was flagged at once.
In an arrangement like this, the finance team can point to a repeatable process when the auditor asks how the population was assembled.
Grant Thornton makes the same point about the control value of one repository. Collecting lease data in a single, centralized repository is, in its words, "a vital key control that your external auditors will expect."4
Where to Go From Here on Completeness
Reaching and keeping lease population completeness is ongoing work. It takes careful processes, teamwork across functions, and the right technology. Review your controls and processes regularly to find any gaps.
Related Reading
- ASC 842 Audit Readiness Checklist
- Guides to Successfully Complete an ASC 842 Lease Accounting Audit
- The Ultimate Guide to ASC 842 Lease Accounting
Sources and further reading
Grant Thornton, How private companies can meet the ASC 842 compliance challenge, p. 6 ↩
FASB Accounting Standards Codification, ASC 842-10-15 ↩
AICPA, Statements on Auditing Standards, currently effective (AU-C section 500, Audit Evidence) ↩
Grant Thornton, How private companies can meet the ASC 842 compliance challenge, p. 3 ↩
