IFRS 16, ASC 842, FRS 102: the three standards, side by side

If you’re a finance team reporting in just one jurisdiction, lease accounting is hard enough. If you’re reporting across the US, EU, and UK at once, you’re juggling three different standards - ASC 842, IFRS 16, and FRS 102 - each with its own rules, exemptions, and quirks.

Here’s how the three compare, where they actually differ, and how to handle all of them without running three separate processes.

The quick orientation

All three put leases under the spotlight. None of them let you hide leases in the footnotes anymore. But how they get there is where the differences live.

Where the standards actually differ

1. The lessee accounting model

This is the biggest divide.

• IFRS 16: one model. Almost every lease lands on the balance sheet as a right-of-use (ROU) asset and a lease liability. Expense = depreciation + interest.
• ASC 842: keeps the operating vs. finance split. Both types are on the balance sheet, but expense recognition differs - straight-line for operating, separate interest + amortization for finance.
• FRS 102: also keeps the operating vs. finance split - and importantly, under FRS 102 operating leases generally stay off the balance sheet (treated more like the old IAS 17). This is the standard that looks most different from the other two.

2. Income statement impact

• IFRS 16 front-loads expense - depreciation + interest hits harder in the early years.
• ASC 842 smooths it out for operating leases (straight-line), front-loads it for finance leases.
• FRS 102 keeps operating lease expense straight-line as a rental cost.

This matters for EBITDA, operating profit, and any metric your investors track closely.

3. Exemptions

• IFRS 16: short-term leases (≤12 months) and low-value assets (laptops, phones, small equipment).
• ASC 842: short-term leases only. No low-value exemption.
• FRS 102: the off-balance-sheet treatment of operating leases effectively functions as a broader simplification.

4. Modifications and remeasurement

All three require remeasurement when terms change - but the triggers and the discount rate treatment differ. IFRS 16 leans heavier on reassessing the discount rate; ASC 842 leans heavier on reassessing classification.

5. Disclosures

All three require detailed disclosures - maturity analyses, weighted-average rates, roll-forwards - but ASC 842 layers on US-specific requirements tied to SEC expectations, and FRS 102 disclosures are generally lighter than the other two.

Why it matters if you’re reporting across borders

If you’re a single-standard reporter, you pick a process and run it. Done.

If you’re a multinational - say, a US parent with EU and UK subsidiaries - you’re running three parallel processes on the same lease portfolio. That means:

• Different journal entries for the same lease, depending on which entity is reporting
• Different ROU asset and liability values across standards
• Different disclosure packages
• Different reconciliation challenges at consolidation

Spreadsheets don’t scale here. Neither does running three separate systems.

How Onederful handles all three inside Business Central

Onederful is built natively into Microsoft Dynamics 365 Business Central and supports ASC 842, IFRS 16, and FRS 102 in one environment. That means:

• One lease record, multiple standards. Apply the correct rules per entity automatically - no double entry, no parallel spreadsheets.
• Automated calculations across all three. ROU assets, lease liabilities, interest, depreciation, modifications, remeasurements - all done correctly per the applicable standard.
• Disclosures, ready on demand. Generate compliant maturity analyses, roll-forwards, and weighted-average reports for any of the three standards in a few clicks.
• Journal entries direct to your BC general ledger. Full audit trail. No re-keying.
• Multi-entity, multi-currency from day one. Track leases in USD, EUR, GBP, or any combination - consolidate cleanly in your parent currency.

For finance teams managing leases across the US, EU, and UK - that’s the difference between three processes and one.

The bottom line

The three standards aren’t going to converge any time soon. But your process for handling them can.