Lease accounting is rarely just a month-end journal entry. The numbers depend on contracts held across procurement, facilities, legal, operations and local finance teams—and on judgments that can change when a location is renewed, equipment is replaced or payment terms are amended. A lease population that looked complete at implementation can become incomplete as the business grows.
For controllers, the goal is to maintain a controlled process from contract identification through accounting, payment, reassessment and disclosure. That process should also preserve the distinctions between US GAAP, IFRS and Canadian Accounting Standards for Private Enterprises (ASPE).
1. Start with a complete lease population
The first control is not a calculation; it is completeness. A lease system cannot account for a contract it never receives. Do not rely only on the lease-accounting team’s spreadsheet or the general ledger. Potential lease arrangements may sit in real-estate agreements, vehicle fleets, IT equipment, warehouses, embedded service contracts and purchase orders.
Establish a recurring intake process with procurement, legal, facilities, IT, fleet management and business-unit finance. Ask these teams to identify new contracts, renewals, extensions, cancellations, asset substitutions and amendments. Include a documented assessment of service agreements that may contain a right to control the use of an identified asset; not every service contract contains a lease.
Practical control: each month, reconcile contract-system additions and amendments to the lease register. Investigate vendor spend patterns—such as recurring rent or equipment charges—to identify possible arrangements missing from the register. A spend report is a detective control, not a substitute for reviewing contractual terms.
2. Separate accounting policy from data entry
Build a standard intake record for every arrangement. At minimum, capture the legal entities, asset and location, commencement date, contractual term, renewal and termination options, fixed and variable payments, incentives, prepayments, non-lease components where relevant, currency, payment frequency, and responsible business owner.
Require preparer and reviewer sign-off on the accounting assessment. The reviewer should be able to trace key inputs to the signed contract and understand why options were included or excluded from the lease term. Avoid allowing a system default to become the accounting conclusion.
3. Document lease term and option judgments
Lease term judgments can affect the right-of-use asset, lease liability, expense pattern and maturity disclosures. The evidence should explain the relevant contractual options and the facts supporting the conclusion—not merely repeat that an option is or is not expected to be exercised.
For example, a retailer with a renewal option may have invested significantly in leasehold improvements, while a distribution site may be critical to a long-term supply chain. Those facts may be relevant to the assessment, but the conclusion must be made under the applicable accounting framework and the contract’s actual terms.
Set a reassessment trigger when business plans, approved capital spending, site strategy or contract terms change. Keep the original judgment, the new evidence, the approver and the resulting accounting impact together.
4. Govern discount rates and calculations
Lease liability measurement depends on payment data and a discount rate determined under the applicable standard. Establish who approves the rate methodology, how rates are sourced, how currency and term are matched, and how exceptions are documented. Do not let individual preparers select rates without a controlled policy.
At implementation and after system changes, independently recalculate a sample of lease liabilities and right-of-use assets. Include leases with different terms, currencies, payment patterns and options. Reperform the calculation using contract-backed cash flows and compare the result with the lease system and general ledger.
Use a controlled rate table with effective dates, permitted users, review evidence and change history. Where an accounting framework permits alternatives or practical expedients, document the entity’s election and confirm that it is applied consistently within the relevant scope.
5. Treat modifications and reassessments as controlled events
Lease changes often arrive through business conversations rather than formal accounting workflows: a landlord grants rent relief, a site expands, equipment is swapped, or a business exits a location early. Require business owners to route amendments to finance before the revised payments are processed or the contract is closed.
For each event, document the date, the contract terms affected, the accounting analysis, any revised assumptions, system changes and reviewer approval. Distinguish a contractual modification from a change in estimate or a reassessment event; the accounting treatment depends on the facts and applicable guidance.
Example: a warehouse lease is extended and the fixed rent changes. The controller should ensure the revised agreement reaches the lease team, the extension-option analysis is updated, the accounting treatment is reviewed, and the new schedule ties to the revised contract. Simply changing the monthly payment field may not capture the full accounting consequences.
6. Reconcile the lease subledger to the general ledger
At each close, reconcile the lease system’s rollforward to the general ledger. The reconciliation should explain opening balances, new leases, modifications and reassessments, cash payments, interest or accretion, amortization or depreciation, terminations, foreign-exchange effects where applicable, and closing balances.
Do not accept a net-zero difference without understanding the components. Use account-level and entity-level reconciliations, investigate stale or unusual balances, and separate timing items from mapping errors. Confirm that the posting interface completed successfully and that rejected or duplicated entries were resolved.
For SAP or another ERP, maintain controlled account mappings for right-of-use assets, accumulated depreciation or amortization, lease liabilities, interest, lease expense and relevant clearing accounts. Restrict changes to mappings and posting rules, test them before release, and retain evidence of transport or configuration approval. If the lease calculation is performed in a separate application, reconcile both the interface totals and the resulting general-ledger balances.
7. Keep the US, IFRS and Canadian ASPE models distinct
The frameworks are not interchangeable. Under US GAAP, FASB Topic 842 requires lessees to recognize lease assets and liabilities for leases, subject to the standard’s requirements and applicable elections, while retaining finance-versus-operating lease classification. The classification affects expense presentation and cash-flow treatment.
Under IFRS 16, lessees generally apply a single recognition model for leases longer than 12 months, unless the low-value exemption applies. Expense presentation differs from the US GAAP model for leases classified as operating leases under Topic 842.
For Canadian private enterprises applying ASPE, Section 3065 has a different lease-accounting model and classification approach. The AcSB’s materials hosted by CPA British Columbia summarize Section 3065 as distinguishing lease types based on the risks and benefits associated with ownership: ASPE leases resources. Confirm the current Handbook requirements, the entity’s reporting basis and any relevant elections with the accounting policy owner.
For groups reporting under more than one framework, maintain a documented bridge from local statutory books to group reporting. Avoid forcing local accounting entries to match group reporting without an approved adjustment process. Reconcile the differences and preserve the reason, calculation, reviewer and reversal or ongoing treatment for each adjustment.
8. Make disclosures and audit evidence part of the close
Assign ownership for lease disclosures before year-end. The close checklist should cover maturity analyses, expense and cash-flow information, significant judgments, variable payments, options and other required qualitative or quantitative disclosures under the applicable framework. Reconcile disclosure data to the lease register and general ledger, and document how completeness was tested.
Maintain a compact audit trail for each material lease: executed contract and amendments, accounting assessment, rate support, calculation, approval, journal entries, reconciliation, and any reassessment history. Store evidence in a controlled repository rather than relying on email threads or an individual employee’s files.
Controller’s checklist
- Reconcile contract sources and vendor-spend analytics to the lease register.
- Confirm every material lease has a documented accounting assessment and owner.
- Review lease-term options, discount rates and significant assumptions.
- Route amendments, renewals, terminations and reassessments through finance.
- Recalculate a risk-based sample and test system-generated schedules.
- Reconcile the lease subledger, interface totals and general ledger each close.
- Control ERP mappings, access, configuration changes and posting exceptions.
- Document framework-specific differences for US GAAP, IFRS and Canadian ASPE.
- Reconcile disclosure schedules to underlying records and retain review evidence.
Conclusion
A strong lease-control environment combines contract completeness, documented judgments, reliable calculations, disciplined change management and a close reconciliation that explains the movement—not just the ending balance. Controllers should revisit the process whenever the business adds locations, changes procurement practices, migrates systems or expands across reporting frameworks.
Informational only: This article is a practical control overview, not accounting, legal or audit advice. Apply the current authoritative literature to the facts and reporting framework of your entity.
