The Critical Role of AP Data in Uncovering Unrecorded Leases
For controllers, accounting managers, and auditors, identifying all lease obligations is foundational to ASC 842 audit readiness. We've seen firsthand how entities often overlooked lease components tucked away in service agreements or simply failed to capture every contract that truly met the definition of a lease. Using AP data to identify unrecorded leases means ensuring all contracts meeting ASC 842's definition of a lease have been properly identified, evaluated, and recognized on the books. A persistent challenge remains achieving lease completeness for ASC 842 compliance, especially when so many contracts aren't explicitly labeled as leases. This article details how Accounts Payable (AP) data offers a reliable, and frankly, often underutilized, pathway to proactively identify and mitigate the risks tied to missing leases.
Q: What is an unrecorded lease? An unrecorded lease refers to any contract or portion of a contract that meets the definition of a lease under ASC 842 but hasn't been recognized on the lessee's balance sheet, either as a Right-of-Use (ROU) asset or a corresponding lease liability. We typically find these hiding within service agreements, purchase orders, or master service agreements.
What Auditors Are Actually Looking For
Auditors approach lease accounting with a healthy skepticism, focusing heavily on the completeness and existence assertions. The completeness assertion refers to an auditor's objective to verify that all transactions and accounts that should be recorded have been included in the financial statements. When performing lease audit procedures, we're particularly keen to ensure that the entire population of contracts containing a lease has been properly identified. This is a critical area because an incomplete population directly impacts the accuracy of ROU assets, lease liabilities, and related expenses.
Deloitte notes that a key step in evaluating lease completeness involves understanding the client’s process for identifying potential leases and then testing the effectiveness of that process. 1 This absolutely includes examining non-lease contracts for embedded leases. Auditors expect robust controls around contract review and a methodical approach to contract identification. The risks of what are the risks of incomplete lease population include material misstatements of financial statements, non-compliance with generally accepted accounting principles (GAAP), and potentially costly restatements.
| Audit Assertion | Auditor Focus | Evidence Sought |
|---|---|---|
| Completeness | Are all contracts containing a lease identified and recorded? (Including embedded lease discovery) | Contracts register, AP listings, GL expense accounts, vendor agreements, review notes |
| Existence | Do recorded leases actually exist and pertain to the entity? | Signed lease agreements, asset tags, payment evidence |
| Valuation/Allocation | Are ROU assets and lease liabilities calculated correctly? | Discount rate analysis, payment schedules, remeasurement calculations |
| Presentation/Disclosure | Are financial statement disclosures complete and accurate as per ASC 842? | Footnote documentation, journal entries, policy notes |
⚠️ Risk Alert: A common audit finding we see relates to companies overlooking service contracts that contain an identified asset and give the company control over its use for a period. This often leads to material misstatements.
Q: How do auditors test using ap data to identify unrecorded leases? Auditors will typically perform a detailed review of accounts payable vendor listings and general ledger expense accounts. We’re looking for recurring payments, large sums, or vendor descriptions that suggest access to or use of assets. We then select a sample of these payments and request the underlying contracts to assess for lease components, forming a key part of our lease identification audit work.
Key Risks and Failure Points
Failing to properly identify and record all leases, especially those embedded within other contracts, poses significant risks under ASC 842. The most prominent failure point is an incomplete lease population, directly impacting the accuracy of financial reporting.
- Understated ROU Assets and Lease Liabilities: This is the most immediate consequence. If leases are missed, the balance sheet simply won't reflect the economic substance of the entity's rights and obligations. This impacts key financial ratios and stakeholders' perception of financial health. A Right-of-use (ROU) asset is defined as an asset that represents a lessee's right to use an underlying asset for the lease term under ASC 842.
- Non-Compliance with ASC 842 Disclosure Requirements: The standard requires extensive disclosures about lease arrangements. Missing leases means incomplete or inaccurate disclosures, which can lead to audit qualifications or regulatory scrutiny, as outlined in FASB ASC 842-20-50.2
- Material Weakness in Internal Controls: An inability to adequately identify and account for all leases indicates a weakness in internal controls over financial reporting. This can be viewed negatively by stakeholders and increase audit costs.
- Inefficient Use of Capital: Without a complete picture of lease liabilities, management may make suboptimal capital allocation decisions, potentially hindering strategic growth or operational efficiency.
Scenario: ABC Corp., a manufacturing company, enters into a multi-year service agreement for specialized machinery. The agreement states that ABC Corp. has exclusive use of a specific machine, identified by serial number, located at their facility, and operated by ABC Corp. personnel. For years, this was treated as an operating expense. Under ASC 842, this clearly constitutes an embedded lease, as ABC Corp. controls an identified asset for a period. Failure to identify this embedded lease leads to an understated ROU asset and lease liability on their balance sheet, and an inaccurate expense recognition pattern. This oversight directly impacts the company's debt-to-equity ratio, which is closely monitored by their lenders. An ROU asset audit would certainly flag this.
🚨 Critical: Failure to identify embedded leases can result in material misstatement, requiring costly restatements and damaging an organization's reputation. This is where using ap data to identify unrecorded leases controls becomes vital.
Practical Checklist for Using AP Data to Identify Unrecorded Leases
AP data is a rich source for identifying potential leases. We've found this checklist invaluable for systematically reviewing AP records for ASC 842 compliance. It forms a robust strategy for how to identify embedded leases in contracts.
| Step | Action Item | Details for Execution |
|---|---|---|
| 1 | Extract AP Vendor Spend Data | Obtain detailed annual or quarterly AP transaction data. Focus on recurring payments over a certain threshold (say, a $5,000 threshold, for instance) for service or rental-type vendors. Include vendor name, invoice description, payment amount, frequency, and G/L account. |
| 2 | Identify High-Risk Keywords & Vendors | Search invoice descriptions and vendor names for terms like "rent," "lease," "equipment rental," "storage," "fleet," "maintenance," "data center," "copier," "scaffold," "transport," or specific asset types (e.g., "forklift," "server"). Target recurring vendors with varied or vague descriptions. |
| 3 | Analyze Recurring Payments without Fixed Assets | Identify recurring payments to vendors where no corresponding fixed asset exists on the balance sheet. For example, monthly payments to a "machine services" vendor should prompt further investigation into the underlying agreement. |
| 4 | Review General Ledger Accounts | Scrutinize expense accounts like "rent expense," "equipment rental," "vehicle expense," "warehouse expense," "IT services," or "maintenance contracts." Any significant or recurring balance warrants contract review. |
| 5 | Investigate Anomalous Payment Schedules | Look for payments with unusual patterns (e.g., consistent large amounts paid monthly for several years) that might indicate a long-term contractual obligation for asset use. |
| 6 | Request Underlying Contracts | For identified high-risk transactions, request the complete underlying vendor agreements or contracts. Don't rely solely on summarized invoices; the devil's in the details. |
| 7 | Perform Lease Assessment | Evaluate requested contracts against the ASC 842 definition of a lease: Does it convey the right to control the use of an identified asset for a period of time in exchange for consideration? We always ensure an identified asset and scope of protection exist. According to FASB ASC 842-10-15, 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. |
| 8 | Document Findings & Update Lease Register | For all identified leases, ensure they are properly documented, classified, and added to the organization's centralized lease accounting system or register. |
💡 Key Takeaway: The completeness assertion is one of the most scrutinized areas in an ASC 842 audit. Proactive AP data analysis significantly strengthens your defensibility.
How Accounting Teams Should Validate Their Approach
Validation is key to demonstrating effective internal controls and accurate financial reporting. After using AP data to identify unrecorded leases, accounting teams absolutely must have a structured process to confirm the completeness of their lease population. This involves not only identifying potential leases but also rigorously evaluating them against ASC 842 criteria.
- Cross-Functional Review: Collaborate with procurement, operations, and IT departments. These teams are often the originators or primary users of assets under contract and can provide valuable context on existing agreements. For additional guidance, consider a review of the ASC 842 audit readiness checklist.
- Regular Reconciliation: Reconcile your lease register to relevant general ledger accounts (e.g., rent, equipment rental) periodically. Any significant variances should trigger further investigation.
- Third-Party Lease Software: Implement specialized lease accounting software. These platforms often include robust contract intake and workflow tools that can aid in identifying and managing leases more efficiently, providing a single source of truth for lease accounting compliance.
- Policy and Procedure Documentation: Document the process for identifying, evaluating, and recording leases, including specific steps for reviewing AP data. This demonstrates a well-defined control environment.
- Sampling and Retesting: Select a sample of high-value vendor contracts (both identified leases and those initially deemed non-leases) and re-perform the lease assessment. For guidance on appropriate sample sizes, refer to the AICPA Audit Guide. This helps confirm the effectiveness of the initial review process.
Q: How do I find unrecorded leases using accounts payable data? To find unrecorded leases, focus on recurring payments in AP data, especially to vendors not typically associated with asset purchases. We look for vague invoice descriptions, significant payments that lack a clear asset on the balance sheet, or payments to vendors known for providing equipment services rather than outright sales.
Common Mistakes and How to Avoid Them
Even with robust processes, organizations can fall into common traps when using AP data to identify unrecorded leases. Understanding these pitfalls is crucial for a successful ASC 842 audit.
| Common Mistake | Best Practice for Avoidance |
|---|---|
| Focusing only on "Lease Expense" G/L accounts. | Expand review to relevant expense accounts: Analyze "Rent Expense," "Equipment Rental," "IT Services," "Maintenance Contracts," "Office Expenses," and "Warehouse Expenses" in detail. We've found many embedded leases reside here. Remember that what documentation is required for using ap data to identify unrecorded leases includes payment histories and GL detail. |
| Assuming service contracts cannot contain leases. | Train staff on embedded lease identification: Educate procurement personnel and accounting staff on the ASC 842 definition of a lease, emphasizing the "identified asset" and "right to control" criteria. An embedded lease refers to a lease component contained within a larger contract that may not be explicitly identified as a lease. |
| Relying solely on keyword searches in invoice descriptions. | Combine keyword searches with vendor analysis and payment patterns: Some descriptions are vague. Cross-reference payments with vendor types and look for consistent, large, or long-term payments that suggest ongoing asset use. |
| Not investigating contracts below a materiality threshold. | Establish a reasonable materiality for lease identification, but consider cumulative effect: Even small individual leases can become material in aggregate. Consider qualitative factors. PwC often recommends a lower threshold for identifying leases than for other assets given the aggregate impact. 3 |
| Lack of a centralized contract repository. | Implement a robust contract management system: This provides a single source of truth for all contractual obligations, making it easier to identify and manage leases from inception. This supports effective lease management. |
Example: A mid-sized tech company we worked with identified nearly a dozen "server hosting" contracts through AP data review that were previously expensed. While labeled as services, the contracts specified dedicated servers by serial number and granted the company exclusive operational control. These were clearly embedded leases. Failure to identify them would have led to an audit finding of incomplete lease population and understated liabilities. This scenario exemplifies what are common using ap data to identify unrecorded leases audit findings. Auditors specifically look for these types of "hidden" leases.
What Strong Execution Looks Like in Practice
Organizations that excel in using AP data to identify unrecorded leases demonstrate a proactive, systematic approach to lease accounting compliance. Their financial reporting is more accurate, and their audit processes are smoother, incurring fewer management letters and audit adjustments. This proactive stance supports continuous, robust lease completeness testing procedures.
A well-executed process typically involves:
- Proactive System Integration: AP systems are integrated with lease accounting platforms or, at a minimum, regularly export data for analysis, facilitating monthly or quarterly reviews rather than just annual exercises.
- Trained Personnel: Accounting, procurement, and operational staff are well-versed in ASC 842's lease definition, enabling frontline identification of potential leases. We've found this investment in training significantly reduces the downstream effort of cleanup.
- Clear Policies and Procedures: Documented guidelines exist for contract review, lease assessment thresholds, and data analytics routines using AP data. These policies are consistently applied and periodically audited internally.
- Regular Review Cycles: Beyond annual audits, management conducts quarterly reviews of AP expenditures for potential new leases or changes to existing agreements. This helps maintain a continuously accurate lease population.
- Audit Readiness: When auditors arrive, the company can readily provide reconciliation of their lease register to GL accounts, detailed AP analysis results, and supporting contract documentation for all identified leases. The auditors guide to evaluate ASC 842 lease accounting compliance confirms this readiness.
✅ Best Practice: Organizations with strong execution maintain quarterly lease reviews aided by AP data analysis, significantly reducing the risk of audit findings related to completeness.
Next Steps
Ensuring the completeness of your lease population is an ongoing process, not a one-time event. Controllers and accounting managers should establish proactive routines for reviewing source data, particularly AP records, to identify potential unrecorded leases. Implementing a robust methodology for using AP data to identify unrecorded leases will enhance financial reporting accuracy and streamline your annual audit.
Related Articles
- ASC 842 Audit Readiness Checklist
- Lease Completeness Testing Procedures
- ASC 842 Management Assertions
- Continuous Lease Compliance
