Lease Lifecycle Governance: Sustaining ASC 842 Compliance

Sustain ASC 842 Compliance with Effective Lease Governance

Lease lifecycle governance is the ownership, controls and routines that keep lease data right from the day a contract is signed, through each change, to the day it ends. For controllers, accounting managers, and auditors, ongoing lease lifecycle governance is not just an ideal; it is a must in daily work. The shift to ASC 842 put virtually all leases on the balance sheet. That brought work that goes far past the first year.

Without strong governance, a company runs a higher risk of material misstatements and audit findings. Its financial reports also become less reliable. This article sets out what lease lifecycle governance covers. It walks through the key parts and the practical steps it takes to keep following the standard, year after year.

What is Lease Lifecycle Governance under ASC 842?

Lease lifecycle governance in ASC 842 compliance means the full, structured way a company runs its leases from start to end. It covers the policies, steps, controls, and software that keep every lease task in line with ASC 842. It keeps the lease accounting sound for the whole lease term. It takes in changes and new contracts and shows their effect on the books.

Good governance cuts the risk of falling out of line with the standard. It also lets auditors rely on the lease numbers. A well-built framework sets clear owners and steps you can repeat. Those cover how you find, classify, and measure each lease, and how you remeasure it later, which keeps the reports right.

What Auditors Look For in Lease Lifecycle Governance

Auditors look hard at lease lifecycle governance. They want to see that a company has put working controls over all of its leases. Their main goal is to check that lease assets and liabilities are complete, correct, and shown the right way in the financial statements. So they look past the first-year adoption and also test the ongoing controls and steps.

Auditors know that changed lease terms, new contracts, and embedded leases keep coming. They focus on the checks a company has in place to prevent and catch lease misstatements.

The completeness assertion is an auditor's goal to check that every deal and account that should be recorded is in the financial statements. For leases, this means making sure the company has found every contract that holds a lease. Auditors often work top-down. They start with the entity's whole system of internal control over financial reporting.

They expect proof of regular, set steps for lease identification testing in many departments, not just accounting. That means going through buying policies, vendor contracts, and IT deals to look for embedded leases.

Auditors also judge the skills of the people who do lease accounting and whether the software is up to the job. A sound lease compliance procedure should be written down and used the same way each time. It should cover everything from the first data entry to the math for right-of-use (ROU) assets and lease liabilities.

The Financial Accounting Standards Board (FASB) sets the test in ASC 842-10-15-3. A contract is or contains a lease if it "conveys the right to control the use of identified property, plant, or equipment (an identified asset) for a period of time in exchange for consideration"¹. Auditors will trace some leases through the whole accounting process. They check that the math fits the standard and that the disclosures say enough.

Audit Focus Areas for Lease Compliance

✅ Best Practice: Write down formal policies and procedures for identifying and accounting for leases. They give auditors something to test. Share these steps across the company. That includes teams outside accounting that start contracts.

Auditors want to see how lease lifecycle governance really works, not just the spreadsheets. They walk through the lease accounting process and ask questions of managers and staff. They often run data tests on general ledger accounts to spot patterns or odd items that might point to unrecorded leases. This broad approach helps them catch the risk of a lease list that is not complete, which is a common audit trap.

Ongoing Risks After the Initial Implementation

Putting ASC 842 in place was a big job. But keeping up ROU asset compliance brings its own ongoing problems and risks. If you do not deal with them, they can lead to material misstatements, restatements, and adverse audit opinions.

• Incomplete Lease Identification: The risk of missing contracts that count as leases stays high, most of all embedded leases. Many companies look only at contracts labeled "lease agreements." They miss service contracts, buying deals, or IT deals that hold an identified asset and give control of it. This hits the completeness assertion head on.
• Data Inaccuracies and Inconsistencies: Lease data often sits in separate systems (e.g., procurement, real estate, IT). Without one central system and the same data entry steps each time, errors creep in. Wrong lease terms, payment schedules, or option exercise assumptions can lead to wrong ROU asset and lease liability math. This can badly hurt accurate lease payment recognition ².
• Improper Discount Rate Selection: Picking the right discount rate takes judgment. A lessee uses the rate implicit in the lease when that rate is readily determinable, and otherwise its incremental borrowing rate. A lessee that is not a public business entity may use a risk-free rate in place of its incremental borrowing rate. It makes that accounting policy election by class of underlying asset (ASC 842-20-30-3). Rates used unevenly, or rates with no support, can lead to large errors in both ROU assets and lease liabilities. The incremental borrowing rate often varies with lease terms and the entity's own credit rating.
• Lack of Control Over Lease Modifications: Lease modifications (e.g., extensions, terminations, scope changes) need specific accounting under ASC 842. You need a clear process to catch these changes and book them fast. Without one, the financial statements can soon be out of date and wrong. This is where the importance of critical date notification in lease management becomes paramount.
• Insufficient Documentation: Auditors lean hard on full records to back lease entries. Missing audit trails, unsupported judgments, or an unreconciled lease sub-ledger can result in audit qualifications. Companies need lease management documentation for compliance.

⚠️ Risk Alert: A common audit finding is that a company missed some embedded leases. It overlooked service contracts, supply deals, or software licenses where it gets the right to control an identified asset. This miss hurts the completeness of the lease portfolio reported.

Example Scenario: Undiscovered Embedded Leases

Scenario: A manufacturing company (e.g., Widgets Corp) signs a multi-year outsourcing deal with a logistics provider (Logistics Solutions Inc.) to run all of its warehousing and freight.

Under the contract, Widgets Corp gets sole use of a set section of Logistics Solutions Inc.'s warehouse. It also gets access to specific forklifts. And it controls when and how its inventory is stored and moved in that space. The contract never says "lease."

Failure Point: Widgets Corp's accounting team first treats this as just a service contract. It books only the monthly service fees as expenses. The team misses the embedded lease parts of the deal: the set warehouse space and the specific forklifts.

Impact:

1. Understated ROU Assets: The company does not recognize ROU assets for the warehouse space and forklifts.
2. Understated Lease Liabilities: The corresponding lease liabilities are not recorded on the balance sheet.
3. Misstated Lease Cost: The service fees are expensed as billed. The right expense pattern depends on how each embedded lease is classified. An operating lease gets a single lease cost, generally straight-line (ASC 842-20-25-6), so the main error is on the balance sheet. A finance lease gets amortization of the ROU asset plus interest on the lease liability (ASC 842-20-25-5).
4. Audit Finding: At the year-end audit, outside auditors do lease identification testing. They review large service contracts and find the embedded lease. They raise an audit finding on the completeness assertion and require a material adjustment to the financial statements. This could even raise concerns about material weakness or significant deficiency around leases.

Key Takeaway: This case shows why you must check every contract for embedded leases to stay in ASC 842 compliance. It also shows why strong internal controls over finding leases matter.

Practical Checklist for Sustaining ASC 842 Compliance

Staying in ASC 842 compliance takes a planned, step-by-step approach that gets ahead of problems. This checklist gives controllers, accounting managers, and auditors a way to test and build up their ongoing lease lifecycle governance.

How Can We Ensure Lease Completeness for ASC 842 Compliance?

Companies must set up a regular process to review all new and existing contracts in every department. That means purchase agreements, service contracts, IT licenses, and real estate papers. The goal is to cast a wide net and catch every possible lease, most of all those not labeled as one.

Train procurement, legal, and operations teams often on how to spot embedded leases in contracts. That training is key, so they can flag possible lease parts. Central lease management software helps a lot here. It gives one source of truth for all lease data and runs the workflows for you.

Monitoring Procurement and Vendor Activity for New Leases

Accounting teams play a central role in checking that their lease lifecycle governance works. That check mixes ongoing monitoring, regular reviews, and reconciliations. Together they keep the lease list complete and correct.

First, you must watch procurement and vendor systems all the time for embedded lease discovery. Accounting teams should work with other departments to set up automatic alerts. The alerts should fire on new contracts, or on big changes to old ones, that might hold lease parts.

Second, you must tie the lease software totals to the general ledger on a regular basis. That covers ROU assets, lease liabilities, and the related expenses, and it is not optional. Look into any gaps and clear them fast. This includes tying sub-ledger details to the general ledger and making sure the right cutoff steps are used at period-end.

Auditors expect proof of strong internal controls over the whole lease accounting process. Accounting teams should test these controls through self-assessment or internal audit. That covers controls over finding new leases, data entry, correct math, and modification accounting. For more checks and what records you need, see our lease management documentation for compliance.

💡 Key Takeaway: The end goal of these checks is reasonable assurance that the financial statements are materially correct on leases. For SEC registrants, it also supports management's assessment of internal control over financial reporting.

Calculation Example: Lease Liability Remeasurement

Scenario: Company X has an existing operating lease for equipment. After 2 years, it negotiates a 1-year extension with the lessor. The extension is negotiated, not the exercise of a renewal option in the original contract. It is not accounted for as a separate contract (ASC 842-10-25-8), so it is a modification that extends the term (ASC 842-10-25-11(b)).

All 36 remaining monthly payments are $5,500, up from $5,000. The original present value used a 5% discount rate. On the modification date, the incremental borrowing rate is 5.2% (the rate implicit in the lease is not readily determinable). ASC 842-10-25-11 requires remeasuring the lease liability at a rate determined at the modification's effective date.

The example assumes payments at the end of each month (in arrears) and a monthly rate equal to the annual rate ÷ 12. The "old" present value equals the lease liability just before the modification only if the original schedule was amortized at 5% in arrears.

Key Takeaway: A modification that extends the term, and is not accounted for as a separate contract (ASC 842-10-25-8), requires remeasuring the lease liability. The discount rate is determined at the modification's effective date (ASC 842-10-25-11), and the change adjusts the ROU asset (ASC 842-10-25-12). Company X also reassesses whether the modified lease is still an operating lease (ASC 842-10-25-9).

Accounting teams need a clear process to catch such changes and book them right, so ASC 842 balances stay correct over time.

Unsupported Entries From Overlooked Documentation

Even with the first ASC 842 rollout done, companies often fall into common traps in ongoing governance. These mistakes often lead to audit findings and material adjustments. Missing documentation is a common gap: entries often have no support for the judgments behind them. Many companies struggle with implementing top 10 lease accounting internal controls.

🚨 Critical: Failing to find and properly book every lease modification is a major governance weakness. These changes hit the lease liability and ROU asset balances directly. Late or wrong accounting can lead to material misstatements on the financial statements.

One of the biggest mistakes under lease accounting compliance is to treat ASC 842 as a one-time project, when it takes steady effort.

For example, a company might classify all its first leases correctly. But then it might fail to account for renegotiated lease terms, such as an extension at a new rate. The first accounting goes out of date, and later periods are wrong. That is why a proactive lease accounting lifecycle approach is critical.

Lease Accounting as an Integrated, Ongoing Process

Doing lease lifecycle governance well means more than dodging audit findings. It also brings smoother operations, reliable financial reporting, and sure decisions. Companies that do it well treat lease accounting as a joined-up, ongoing process, not a chore they do now and then. That way, every lease the company holds is watched all the time, measured right, and reported the same way each time.

For example, a company with strong governance might have its own lease accounting software that links to its ERP system. The system flags contracts on their way to a modification, renewal, or end date on its own. That way the company reviews them again under ASC 842 on time. Procurement and legal teams are trained on embedded lease discovery.

Those teams work with accounting to review new contracts and spot possible leases at the start. Discount rates get reviewed and written up from time to time. The company often uses outside treasury work or financial models to back up its current incremental borrowing rates.

Each quarter, the whole lease list gets a review as a matter of course. Accounting leaders check the data closely, review all modification accounting, and test the judgments made on lease terms and options. Getting ahead like this cuts audit work a lot. Auditors can rely on the set processes, the records, and the strength of internal controls over lease accounting compliance.

A well-run lease program builds a habit of getting things right and owning them. The result is smooth audits, fewer questions, and more trust in the reported financial position.

Putting Lifecycle Governance in Place

Sustaining ASC 842 compliance is ongoing work that takes steady care and strong governance. Use the practical steps above, from careful lease identification to full checks and working controls. Then a company can keep its lease reporting correct and complete. Stop thinking of it as a one-time project and build lease lifecycle governance into the normal finance routine.

Related Articles

• Ultimate Guide to ASC 842 Lease Accounting
• New Lease Accounting Standard Implementation Challenges
• Top 10 Year-End Lease Accounting Challenges and Solutions for ASC 842 Compliance
• How to Ensure Lease Completeness for ASC 842 Compliance