ASC 842 vs IFRS 16: 2026 compliance checklist for lease accounting

For real estate professionals managing leases across multiple entities or jurisdictions, understanding the differences between ASC 842 and IFRS 16 is a practical operational requirement. Both standards brought most leases onto the balance sheet, transforming how organizations report their financial obligations, but they do so through different frameworks, with different classification models, exemptions, and income statement impacts.

Getting the details right matters. Misclassification, incomplete disclosures, or inconsistent application of policy elections can create audit exposure and financial reporting risk. For organizations reporting under both standards simultaneously, the complexity compounds further.

This guide compares ASC 842 and IFRS 16 across the dimensions that matter most for 2026 compliance – classification, measurement, transition, disclosure, and special transactions, and provides a practical checklist for finance and real estate teams to work through.

Key differences between ASC 842 and IFRS 16

ASC 842 is the US GAAP lease accounting standard issued by the Financial Accounting Standards Board (FASB). IFRS 16 is the international standard issued by the International Accounting Standards Board (IASB). Both require lessees to recognize most leases on the balance sheet as right-of-use (ROU) assets and corresponding lease liabilities – a significant shift from the previous treatment that kept operating leases off-balance-sheet entirely.

Lease classification and scope

The most significant structural difference is the lessee model. ASC 842 distinguishes between operating and finance leases, with different income statement treatment for each. IFRS 16 applies a single model – nearly all leases are accounted for the same way. For organizations with large volumes of low-value equipment leases, the absence of a low-value exemption under ASC 842 has a meaningful practical impact on balance sheet scope.

Measurement and accounting mechanics

A right-of-use (ROU) asset represents a lessee’s right to use an underlying asset for the duration of the lease term, initially measured at the value of the lease liability adjusted for prepaid payments, initial direct costs, and lease incentives. The lease liability represents the present value of future payments not yet made.

Both standards use the same core measurement logic, but differ in the details. On discount rates, ASC 842 allows nonpublic entities to use a risk-free rate as a practical expedient; IFRS 16 does not permit this, requiring the incremental borrowing rate whenever the implicit rate is unavailable. On variable payments, IFRS 16 requires liability remeasurement whenever an index or rate changes, while ASC 842 typically treats index changes as variable expenses in the period unless a specific remeasurement trigger is present.

The income statement consequences are significant, particularly for EBITDA-focused reporting:

Entity reporting operating leases under IFRS 16 will typically show a higher EBITDA than an equivalent entity under ASC 842, a distinction investors and lenders should factor into covenant analysis and performance comparisons.

Transition and implementation considerations

Organizations that have not yet fully embedded ASC 842 or IFRS 16 into their reporting processes – or that are revisiting their implementation ahead of 2026 audits – should work through the following steps systematically.

Transition methods differ between the standards. ASC 842 requires the modified retrospective approach, meaning the cumulative effect of adoption is recognized at the date of initial application, with prior periods not restated. IFRS 16 offers more flexibility, permitting either a full retrospective approach (restating comparative periods) or a simplified transition approach (similar to ASC 842’s modified retrospective, with some additional practical expedients available).

A practical implementation sequence could look something like this:

• Review lease definitions – reassess all contracts to confirm which arrangements contain a lease under the relevant standard’s definition, including embedded leases within service agreements
• Centralize lease contracts – consolidate all lease documentation into a single repository, ensuring completeness before commencing measurement
• Document policy elections – formally record all practical expedients applied, including short-term lease exemptions, low-value exemptions (IFRS 16), and any transition elections
• Calculate ROU assets and lease liabilities – apply the appropriate discount rates and payment schedules for each lease
• Configure reporting workflows – establish processes for ongoing remeasurement, modification accounting, and disclosure preparation
• Validate against the general ledger – reconcile opening balances to confirm accuracy before the first compliant reporting period

Specialized lease accounting software significantly reduces the risk of error in this process. MRI’s lease accounting software supports both ASC 842 and IFRS 16 workflows within a centralized platform, with built-in calculation engines and audit trails that support the documentation requirements of both standards.

Disclosure requirements and financial reporting impact

Both standards require enhanced disclosures that go beyond the balance sheet recognition of ROU assets and lease liabilities. The goal is to give financial statement users enough information to understand the nature, timing, and uncertainty of lease-related cash flows.

Required disclosures under both standards include maturity analyses of lease liabilities, qualitative descriptions of leasing policies (including discount rate methodology and lease term assumptions), expense breakdowns by lease type, and the carrying amounts of ROU assets and lease liabilities.

The financial statement presentation differences between the standards are significant for organizations focused on EBITDA metrics:

For organizations comparing performance metrics across entities reporting under different standards, these presentation differences require careful consideration. An entity reporting under IFRS 16 will typically show a higher EBITDA than an equivalent entity reporting operating leases under ASC 842, even where the underlying economics are identical – a distinction that investors and lenders should factor into covenant testing and performance analysis.

Special transactions and lease modifications

Sale-and-leaseback transactions – where an entity sells an asset and immediately leases it back from the buyer – are treated differently under each standard. ASC 842 may allow full gain recognition on the sale portion of the transaction where the transfer qualifies as a sale under the revenue recognition standard. IFRS 16 restricts gain recognition to the portion of the asset effectively transferred to the buyer, limiting the gain to the rights not retained through the leaseback.

Subleases – where a lessee leases the asset to a third party – are classified differently. Under ASC 842, sublease classification is based on the nature of the underlying asset. Under IFRS 16, classification is based on the right-of-use asset itself, which generally results in more subleases being classified as finance leases under IFRS 16 than under ASC 842.

Lessor accounting also diverges. ASC 842 distinguishes between sales-type leases and direct financing leases on the lessor side. IFRS 16 uses a simpler framework of finance leases and operating leases for lessors – a distinction that matters for real estate entities that both lease and sublease property.

Lease modifications – changes to the scope, term, or consideration of a lease – require remeasurement under both standards, but the triggers and mechanics differ. Documentation of the modification, the original lease terms, and the basis for remeasurement should be captured at the time of change, not reconstructed later. Both standards require updated discount rate calculations at modification, using current rates rather than those applied at lease commencement.

Compliance challenges for dual reporting entities

Dual reporters are entities required to prepare financial statements under both US GAAP and IFRS – typically multinational organizations with operations subject to different regulatory regimes, or companies listed on both US and international exchanges.

For these organizations, the differences between ASC 842 and IFRS 16 are a persistent operational challenge. The same underlying lease must be classified, measured, and disclosed differently depending on which standard applies – meaning two parallel sets of calculations, elections, and disclosures must be maintained with accuracy and consistency.

The primary challenges for dual reporters include:

• Classification divergence – the same lease may be an operating lease under ASC 842 and treated as a finance-type lease under IFRS 16’s single model
• Remeasurement differences – variable payment remeasurement triggers differ, requiring separate tracking of when and how each standard requires liability updates
• Disclosure gaps – the specific disclosure requirements of each standard differ in detail, requiring separate disclosure packages rather than a single unified note
• Policy election management – elections made under one standard (such as the risk-free rate practical expedient under ASC 842) may not have an equivalent under IFRS 16, requiring careful documentation of which elections apply to which reporting framework
• Audit support – auditors reviewing both sets of financials will expect clear evidence that the two frameworks have been applied independently and correctly

Centralizing lease data in a system that supports both standards is the most effective way to manage this complexity. A single source of contract data, with parallel calculation and reporting workflows for each standard, reduces the risk of inconsistency and provides the audit trail that both sets of auditors require.

2026 compliance checklist for lease accounting

Leveraging Technology for Lease Accounting Compliance
Manual and spreadsheet-based lease accounting processes present significant compliance risk. Spreadsheets are error-prone, difficult to audit, and poorly suited to managing the volume of calculations, remeasurements, and disclosures that ASC 842 and IFRS 16 require – particularly for portfolios with hundreds of leases or dual reporting obligations.

Purpose-built lease accounting software addresses these risks directly. Key capabilities to look for include centralized contract storage, a built-in calculation engine that handles both ASC 842 and IFRS 16 simultaneously, automated remeasurement workflows triggered by index changes or lease modifications, full audit trails documenting every calculation and assumption, and disclosure reporting outputs formatted to each standard’s requirements.

MRI Software’s lease accounting solution and dedicated ASC 842 software are designed to meet these requirements within a platform that integrates with broader property management and financial reporting workflows. For organizations working through initial implementation or reviewing their current approach ahead of 2026 audits, MRI’s implementation guidance and lease accounting resources provide a practical starting point.

Stakeholder communication and audit readiness

The balance sheet and income statement impacts of ASC 842 and IFRS 16 affect more than the finance team. Lenders, investors, auditors, and tax teams all have a stake in understanding how lease accounting changes affect reported figures – and organizations that communicate these impacts proactively manage stakeholder relationships more effectively than those that leave interested parties to interpret the numbers independently.

Best practices for stakeholder communication and audit readiness include:

• Preparing regular reports that quantify balance sheet changes, EBITDA impact, and the effect on debt covenant calculations – particularly for covenants referencing net debt, leverage ratios, or EBITDA
• Maintaining complete audit trails for every lease, covering original contract terms, subsequent modifications, discount rate assumptions, remeasurement calculations, and disclosure inputs
• Documenting all policy elections and practical expedients applied, with a clear rationale for each decision
• Preparing reconciliations that tie lease accounting balances to the general ledger and to prior period disclosures
• Scheduling post-implementation reviews to confirm that processes are working as intended and that any new leases entered since initial adoption have been captured correctly

FASB and IASB both continue to issue guidance and narrow-scope amendments to their respective standards. Assigning clear responsibility for monitoring these updates – and assessing their impact on current elections and processes – is an important part of maintaining compliance as the standards evolve beyond their initial adoption dates.

Frequently asked questions