If your organisation holds leases — property, vehicles, or equipment — you likely deal with ASC 842 or IFRS 16.
Both standards aim to bring operating leases onto the balance sheet. Before these standards, companies could hide major obligations off the books. As a result, investors, auditors, and lenders struggled to see the full financial picture. The standards fixed that — but they did not do it in exactly the same way.
US-based companies follow ASC 842, which the Financial Accounting Standards Board (FASB) published. Most other countries — including the UK, Australia, New Zealand, South Africa, and Canada — use IFRS 16, which the International Accounting Standards Board (IASB) issued.
If you work across multiple jurisdictions or advise clients in different markets, you need to understand ASC 842 and IFRS 16. This becomes critical if you want a scalable lease accounting process. This article walks through the key differences in plain language, with the operational implications that matter most to finance teams and accounting firms.
Why Both Standards Exist — and Why They Are Not Identical
FASB and the IASB developed ASC 842 and IFRS 16 in parallel, with the explicit goal of convergence. The two boards worked closely together. Both standards share the same foundational principle: lessees must recognise a right-of-use (ROU) asset and a lease liability on the balance sheet for most leases.
Overall, both standards agree on this core principle. The differences appear in the details — how companies classify leases, how they recognise expenses in the income statement, which exemptions apply, and how teams handle certain edge cases. These differences are not minor footnotes. For a company managing hundreds or thousands of leases, they translate into meaningful differences in reported profit, balance sheet presentation, and the complexity of your accounting process.
Both ASC 842 and IFRS 16 require operating leases on the balance sheet — but only IFRS 16 treats all lessee leases identically in the income statement.
ASC 842 vs IFRS 16: Side-by-Side Comparison
The table below summarises the most significant differences between the two standards. We cover each of these in more detail in the sections that follow.
| Feature | ASC 842 | IFRS 16 |
|---|---|---|
| Governing body | FASB (US) | IASB (International) |
| Geography | United States | UK, Australia, NZ, SA, most of the world |
| Applies to | All leases (with exemptions) | All leases (with exemptions) |
| Short-term exemption | 12 months or less | 12 months or less |
| Low-value exemption | Not available | Available (assets ~USD 5,000) |
| Finance vs operating distinction | Yes — different P&L treatment | No — single model for lessee |
| Operating lease — P&L | Straight-line rent expense | Depreciation + interest (no operating line) |
| Finance lease — P&L | Depreciation + interest expense | Depreciation + interest expense |
| Balance sheet impact | Right-of-use asset + liability (both) | Right-of-use asset + liability (both) |
| Sale-leaseback treatment | More restrictive | More flexible |
| Variable lease payments | Defined at commencement date | More judgment required |
| Reassessment triggers | Specific events only | Broader reassessment requirements |
| Discount rate | Rate implicit or incremental borrowing rate | Same, but more prescriptive guidance |
The Biggest Practical Difference: Lease Classification
However, this is where ASC 842 and IFRS 16 diverge most significantly — and where the operational impact is most visible.
ASC 842: Two-Model Approach for Lessees
Under ASC 842, lessees classify each lease as either an operating lease or a finance lease. The classification determines how the lease is presented in the income statement:
- Operating lease: Companies recognise a single straight-line lease expense through operating expenses. The ROU asset and liability are both on the balance sheet, but the P&L presentation looks similar to the old treatment.
- Finance lease: the company depreciates the ROU asset separately, and recognises interest expense on the lease liability. This front-loads total expense, as interest is higher in the early years.
The classification criteria under ASC 842 mirror the old tests under ASC 840 — bright-line thresholds based on lease term, present value of payments, and ownership transfer.
IFRS 16: Single-Model Approach for Lessees
In contrast, IFRS 16 takes a different approach. For lessees, there is only one accounting model, regardless of how the lease might be classified under ASC 842. Every lease that is not exempt goes on the balance sheet, and every lessee recognises depreciation on the ROU asset plus interest on the lease liability.
Why This Difference Matters in Practice
As a result, under IFRS 16,what ASC 842 would classify as an operating lease still follows finance lease expense recognition under IFRS 16. EBITDA tends to be higher under IFRS 16 because lease payments no longer appear as operating costs — depreciation (often below EBIT) and interest expense (below EBIT) replace them.
Companies that report under both standards often see material differences. These differences affect EBITDA, operating profit, and key ratios.
Low-Value Asset Exemption: IFRS 16 Only
Another key difference involves the low-value asset exemption.
IFRS 16 permits lessees to exclude leases of low-value assets from the balance sheet treatment. The IASB set this threshold at approximately USD 5,000 when the asset is new — think laptops, tablets, small office equipment. These leases can simply be expensed on a straight-line basis, keeping the accounting simple.
ASC 842 has no equivalent exemption. Companies must put every lease on the balance sheet regardless of the asset value, except short-term leases. This can create a meaningful administrative burden for US companies that have a high volume of small-ticket leases, such as office equipment or software subscriptions structured as leases.
For accounting firms managing clients across both standards, this difference matters when advising on which assets need to be captured in the lease register.
Reassessment and Remeasurement: More Judgment Under IFRS 16
In practice, both standards require lessees to reassess lease liabilities when certain events trigger a review — for example, when there is a change in the lease term, a change in the rate used to discount future payments, or when a purchase option is exercised.
However, IFRS 16 requires a broader range of reassessment triggers and generally demands more ongoing judgment. Under ASC 842, specific, defined events trigger reassessment, which makes the process somewhat more rules-based and predictable.
In practice, this means IFRS 16 compliance tends to require more active monitoring of lease portfolios. If you are managing a large number of leases across multiple jurisdictions, this can become a significant workload if you are relying on manual processes or spreadsheets.
The more leases you manage, the more reassessment events you will encounter — and the harder it becomes to track them accurately in a spreadsheet.
Sale-and-Leaseback Transactions
Sale-and-leaseback is a common financing arrangement, particularly in property and infrastructure. Under this structure, a company sells an asset and immediately leases it back — effectively unlocking the capital value of the asset while retaining the right to use it.
Both ASC 842 and IFRS 16 address sale-leaseback accounting, but with different levels of restriction.
- Under IFRS 16, if the transfer qualifies as a sale under IFRS 15, the seller-lessee recognises only the portion of any gain or loss that relates to the rights the seller transfers to the buyer-lessor. This is a relatively flexible framework.
- Under ASC 842 (read alongside ASC 606), the criteria for recognising a sale are more stringent. In many cases — particularly where the leaseback contains a repurchase option — the transaction may not qualify as a sale at all, meaning the company treats it as a financing arrangement instead.
For organisations using sale-leaseback as a financing strategy, the standard you report under can materially affect how — and whether — you recognise the gain.
Lessor Accounting: Where ASC 842 and IFRS 16 Both Diverge from Their Own Lessee Models
Most of the discussion around ASC 842 and IFRS 16 focuses on lessees, where the two standards introduced the major changes. But lessor accounting is worth a brief mention.
ASC 842 leaves lessor accounting largely unchanged from ASC 840. Lessors continue to classify leases as operating or sales-type (equivalent to finance), with similar criteria.
IFRS 16 retains a dual model for lessor accounting — finance leases and operating leases — even though it unifies the lessee model.This creates an interesting asymmetry: a lessee may account for a lease under the single IFRS 16 model while the lessor still classifies the same lease as operating or finance.
For companies that both lease assets to others and hold leases as lessees, this requires careful tracking on both sides of the ledger.
What This Means for Multi-Jurisdiction Reporting
For organisations operating across multiple countries, ASC 842 vs IFRS 16 is not just a technical accounting question — it is a practical reporting challenge.
Consider a common scenario: a US-headquartered company with subsidiaries in the UK and Australia. The parent reports under US GAAP (ASC 842); the subsidiaries report under IFRS (IFRS 16). For consolidated reporting purposes, the finance team needs to understand how lease expenses are classified in each entity, how the balance sheet is presented under each standard, and where the differences need to be reconciled.
Similar challenges arise for accounting firms advising clients across multiple markets. A firm with clients in Australia, New Zealand, and the United States needs professionals who can navigate both frameworks confidently — and a system that can manage lease schedules under both standards without duplicating effort.
Key Reporting Differences That Affect Multi-Jurisdiction Groups
- EBITDA is typically higher under IFRS 16 than ASC 842 for companies with significant operating lease portfolios, because IFRS 16 reclassifies lease costs below the EBITDA line.
- Net debt metrics differ, as many net debt calculations include lease liabilities — and the liability amounts may differ depending on discount rates and reassessment approaches.
- Key ratios — including interest cover, leverage, and return on assets — can look materially different depending on which standard the company applies.
- Teams must build audit trails that reflect the applicable standard for each entity, with clear documentation of assumptions and judgments.
Where Spreadsheets Break Down
In many cases, finance teams and accounting firms still manage lease schedules in Excel. For straightforward cases — a handful of property leases, simple terms, no reassessments — a spreadsheet can work reasonably well.
However, the limitations become clear as complexity grows.
Managing Dual Standards at Scale
Consider what happens when you need to manage a portfolio of leases under both ASC 842 and IFRS 16 at the same time.
You would need separate calculations for lease classification, different amortisation schedules, and separate journal entries for each standard.
Now multiply that across multiple entities. Each entity may have dozens or hundreds of leases. Some of these leases may also be modified or reassessed mid-term.
Common Failure Points in Spreadsheet-Based Lease Accounting
Common failure points with spreadsheet-based lease accounting:
- Version control issues — multiple team members working on different versions of the schedule, with no clear audit trail of changes.
- Formula errors — complex amortisation and interest calculations are error-prone, and a single cell error can cascade through an entire schedule.
- No reassessment tracking — when a lease is modified or a trigger event occurs, updating a spreadsheet manually is time-consuming and easy to miss.
- Dual-standard reporting — maintaining parallel schedules under ASC 842 and IFRS 16 in a spreadsheet is technically possible but practically very difficult at scale.
- Audit readiness — auditors require detailed documentation of assumptions, discount rates, and calculation methodology. Spreadsheets rarely provide this in a clean, reviewable format.
- Scalability — a 50-lease portfolio managed in Excel is very different from a 500-lease portfolio. The latter effectively requires dedicated software.
Why Spreadsheets Fail for Complex Lease Portfolios
The organisations that struggle most with lease accounting under ASC 842 and IFRS 16 are usually those still managing the process in spreadsheets.
This is not due to a lack of expertise. Instead, the tool itself was never built to handle this level of complexity.
For a direct comparison of how dedicated platforms stack up against each other, see the AssetAccountant Competitor Feature Matrix.
What Purpose-Built Lease Accounting Software Handles
Purpose-built lease accounting platforms build their logic around the specific requirements of ASC 842, IFRS 16, and related standards.
The difference from a spreadsheet-based approach is not just efficiency. It also includes accuracy, auditability, and scalability.
Core Capabilities for Multi-Standard Lease Portfolios
The core capabilities that matter most for multi-standard, multi-entity lease portfolios:
- Dual-standard calculations: the ability to run ASC 842 and IFRS 16 schedules on the same lease portfolio simultaneously, producing the correct output for each standard without duplicating manual effort.
- Automated amortisation schedules: the platform automatically calculates right-of-use asset depreciation and lease liability amortisation, including the interest allocation for each period.
- Reassessment management: when a lease is modified, extended, or a trigger event occurs, the system recalculates the affected schedules automatically and documents the change.
- Discount rate management: the platform automatically applies the correct discount rate — whether the rate implicit in the lease or the incremental borrowing rate — and documents it clearly.
- Audit-ready reporting: detailed output that shows auditors exactly how each schedule was calculated, what assumptions were used, and where changes were made.
Integration and Scalability Across Entities
- Integration with accounting platforms: the platform posts journal entries directly to Xero, QuickBooks Online, Sage Intacct, or Microsoft Dynamics 365, eliminating manual re-entry and reconciliation errors.
- Multi-entity and multi-currency support: essential for groups with subsidiaries in multiple jurisdictions, each potentially reporting under a different standard.
Why This Matters for Accounting Firms
For accounting firms managing lease schedules on behalf of multiple clients — some under ASC 842, others under IFRS 16 — a platform that handles both standards from a single interface significantly reduces workload.
At the same time, it lowers the risk of standard-specific errors.
If you are evaluating platforms, see our full breakdown of the best fixed asset accounting software in 2026.
Conclusion
ASC 842 and IFRS 16 represent the most significant overhaul of lease accounting in decades. They share the same foundational goal — bringing lease obligations onto the balance sheet — but the operational differences between them are material, particularly for organisations with complex or large lease portfolios.
For finance teams and accounting firms working across US and international markets, the core challenge is not understanding the standards — it is building a process that can handle both accurately, at scale, without relying on spreadsheets that were never built for this level of complexity.
Finance teams can manage ASC 842 and IFRS 16 compliance manually for small portfolios. But as lease volumes grow, as entities multiply, and as reassessment events accumulate, the case for purpose-built software becomes straightforward. The question is not whether to automate — it is when.
