How IFRS 16 experience gives you a faster FRS 102 transition

Three years into IFRS 16 compliance, a finance controller at a UK subsidiary gets a question from the group treasury team: their Irish entity needs to transition to FRS 102 Section 20 by year-end. Her first thought is reasonable: do we start over, or does what we've built carry across? Her second thought is sharper. The vendor we're evaluating has a brand-new FRS 102 module, and nobody has said where it came from or who stress-tested it. Both questions have the same answer, and they're connected.

FRS 102 Section 20, effective for accounting periods beginning on or after 1 January 2026, aligns lessee accounting with the IFRS 16 model. For a December balance date, that means transition by December 2026; for a June balance date, June 2026. For organisations already running IFRS 16, the practical answer is that most of the hard work has already been done. This piece explains what transfers, what genuinely requires fresh work, and why a vendor's IFRS 16 production history is a more meaningful credential than a recently published FRS 102 module.

Written with input from Maeve O'Connell, LOIS Head of EMEA and CA-qualified accountant with over 25 years of leasing finance experience. Updated August 2026.

The shared conceptual foundation

FRS 102 Section 20 was revised precisely to align with IFRS 16. The FRC consulted extensively before publishing revisions effective from 1 January 2026, and the resulting lessee model is built on the same core architecture: a right-of-use asset and a lease liability recognised at the commencement date, the lease liability unwound using an interest rate, and the ROU asset depreciated over the lease term. That isn't a coincidence; it's a design decision intended to make the two standards comparable across entities of different sizes and listing status.

For a finance team that has lived with IFRS 16 for several years, this means the mental model is already in place. The balance sheet impact, the split between depreciation above EBITDA and interest below it, the lease liability maturity schedule. None of it is unfamiliar territory. The differences that matter are specific and operational, not conceptual. For a full side-by-side of where the standards diverge, see FRS 102 vs IFRS 16: key differences finance teams need to know. This piece focuses on what that alignment means for your transition workload and your vendor selection.

What transfers directly from your IFRS 16 implementation

The organisations that move fastest through FRS 102 aren't the ones who plan best in the weeks before transition. They're the ones who built clean IFRS 16 infrastructure three years ago and maintained it. The assets that carry over aren't just data; they're disciplines.

Your lease register. The lease identification work you did for IFRS 16, including the embedded lease review of service contracts, applies directly under FRS 102. The definition of a lease in Section 20 is substantively aligned with IFRS 16. An organisation with a complete, current register doesn't need to restart from zero; it needs to verify the register reflects the current portfolio and check it against the FRS 102 low-value and short-term exemption criteria (which differ from IFRS 16 in ways covered below).

Your GL integration. This is the most underrated asset in an IFRS 16-to-FRS 102 transition, and the one most often overlooked when teams compare the two standards in the abstract. Your chart of accounts already has the accounts for ROU assets, accumulated depreciation, lease liability (current and non-current), depreciation expense, and interest expense. The mapping between your lease system and your general ledger has been built, tested, and reconciled through real audit cycles. Under FRS 102, the same accounts serve the same purpose. You're not re-mapping; you're extending the configuration to cover any FRS 102-only leases that weren't previously in scope.

Your modification and remeasurement workflows. IFRS 16 teams have processed lease extensions, rent reviews, scope changes, and early terminations. The triggers for a FRS 102 remeasurement are parallel: a change in lease term, a change in payments tied to an index or rate, a change in the assessment of purchase options. The process your team follows to capture a modification, update the calculation, regenerate the schedule, and post the journals is the same process FRS 102 will require. Teams that have let this discipline drift (modifications not captured promptly, remeasurements done manually in spreadsheets) face a harder FRS 102 transition not because the standard is harder but because the process problem has been deferred, not resolved.

Your audit trail discipline. IFRS 16 auditors examine how decisions were made, how modifications were tracked, and how consistency was maintained across periods. That scrutiny doesn't diminish under FRS 102; auditors who cut their teeth on IFRS 16 are more rigorous reviewers, not less. An organisation whose lease system carries a timestamped audit trail for every modification, exemption decision, and rate change is carrying that credibility directly into its first FRS 102 audit.

Your IBR documentation process. FRS 102 introduces the obtainable borrowing rate (OBR) as the primary discount rate option, and the OBR is actually less administratively demanding than the incremental borrowing rate your IFRS 16 team used. The OBR references figures already in the lease contract rather than requiring a broader entity creditworthiness assessment. The IBR process your team developed (the rate sourcing, the documentation, the audit file) is the template for your OBR process. You're not starting from scratch; you're working from an established methodology and applying a simpler definition.

What transfers from IFRS 16 to FRS 102, and what doesn't

What genuinely requires fresh judgement

The transfer items above are substantial. But FRS 102 isn't IFRS 16 in every respect, and the differences require real new work, not a renaming exercise.

The obtainable borrowing rate is not just a simpler IBR. The OBR is a different calculation approach. Where the IBR asked what it would cost your entity to borrow the equivalent amount over the lease term (requiring an entity-level creditworthiness assessment), the OBR asks what rate you'd pay to borrow an amount equal to the total undiscounted lease payments over a similar term. The difference matters in practice: you can't simply repurpose your IFRS 16 IBR as your FRS 102 OBR. Each lease or portfolio group requires a fresh assessment. What your IFRS 16 team gives you is the documentation methodology and the relationships (bank, treasury) to source rates efficiently. The rate itself is new. For the full mechanics, see FRS 102 discount rates: how to determine the obtainable borrowing rate.

Vehicles cannot be low-value under FRS 102. IFRS 16 used an indicative USD 5,000 monetary threshold. Some organisations applied the low-value exemption to certain vehicles under IFRS 16, defensibly so where individual per-unit values fell below the threshold. FRS 102 replaces the monetary test with explicit asset class lists. Vehicles are excluded from the low-value exemption regardless of their individual value. An organisation leasing 60 company cars that applied low-value treatment to some under IFRS 16 will need to bring all 60 onto the balance sheet under FRS 102. This is one area where FRS 102 is actually more demanding, not less, and it requires a deliberate review of your current low-value exemption decisions before transition date.

Short-term lease assessments need an honest review. The short-term exemption applies to leases with a term of 12 months or less at the commencement date, including renewal options. Under IFRS 16, some teams took a broad view of what qualified as short-term. FRS 102 is equally clear that the lease term assessment must reflect the honest expectation of actual use, not just the contractual rolling structure. Any rolling short-term leases your organisation classified as exempt under IFRS 16 need to be re-examined with fresh documentation of expected term before being carried across.

The disclosure format, though parallel, is distinct. FRS 102 Section 20 disclosure requirements are structurally similar to IFRS 16 paragraphs 51-60: ROU asset movements by class, lease liability maturity analysis, depreciation charges, interest expense, and short-term and low-value lease costs. But the specific presentation requirements reference FRS 102 and its section structure, not IFRS 16 paragraphs. Your audit team will be looking for FRS 102-referenced disclosures. The data driving them is the same; the template isn't. For a full walkthrough of what each FRS 102 disclosure requires, see FRS 102 Section 20 disclosure requirements: what UK and Irish lessees must report.

Why IFRS 16 experience makes a vendor more credible

When you're evaluating lease accounting software for FRS 102, one question separates vendors with genuine depth from those who have built quickly to meet a compliance window: how many IFRS 16 modifications, remeasurements, and live audit cycles has this platform actually processed?

The edge cases in lease accounting don't appear in the standard. They appear in production, usually at the worst moment. A CPI adjustment lands mid-period, between payment dates, and the calculation has to hold. A partial surrender gets treated as a scope reduction rather than a termination, and the journal is wrong. A sublease requires classification by reference to the head lease ROU asset; something the standard describes in three sentences and production makes genuinely complicated. These aren't exotic scenarios for a diverse portfolio. They're the normal ones. But handling them correctly requires calculation logic that has been written, tested against live data, and then corrected when an auditor pointed out the first implementation wasn't quite right.

A platform that has processed IFRS 16 portfolios across hundreds of client organisations has encountered these edge cases in live audit engagements. It has been told by an auditor that its output for a specific modification scenario wasn't adequate, and it has corrected the platform to handle that scenario correctly. That process (edge case surfaces, platform responds, auditor validates) takes years. It can't be replicated by building a new FRS 102 module in advance of the effective date and testing it on synthetic data.

Vendors built specifically for FRS 102 in 2025/2026 haven't faced an auditor with a live FRS 102 portfolio yet. Their first clients will. That's a real due diligence question: whose clients absorb the first-year audit learning, and whose clients benefit from it? For the six compliance areas that IFRS 16 and AASB 16 auditors scrutinise most closely, and the parallel audit focus FRS 102 will attract, see IFRS 16 and AASB 16 in practice: the 6 compliance areas auditors focus on.

How LOIS's AASB 16 track record translates to UK and Irish FRS 102

LOIS has operated across Australia and New Zealand since the AASB 16 and NZ IFRS 16 transitions, processing lease portfolios from 30 to over 10,000 leases. AASB 16 is substantively identical to IFRS 16: same recognition model, same modification triggers, same remeasurement mechanics, same disclosure architecture. The standards differ in some local adoption choices, but the calculation engine and audit output requirements are the same. The edge cases that surface in AASB 16 production are the same edge cases that appear in IFRS 16 and will appear in FRS 102 under Section 20.

What that means in practice: the LOIS platform has been through CPI adjustments on long-running property leases, mid-term IBR resets, fleet bulk-loading across multiple providers, sublease classification disputes, and partial scope reductions that had to be unwound and reclassified. These are portfolios auditors have reviewed and signed off, not test cases run before the effective date. The CA-qualified accountants who worked through those audit cycles with ANZ clients are now supporting FRS 102 engagements in the United Kingdom and Ireland, with the same platform and the same output disciplines.

Maeve O'Connell, LOIS Head of EMEA, brings over 25 years of leasing finance experience to UK and Irish FRS 102 engagements. The LOIS team's FRS 102 support isn't a helpdesk operation. It's CA-qualified practitioners who understand the standard in practice, can interpret a judgement call under audit pressure, and have the platform output disciplines built in from years of IFRS 16 production. Whether the standard is IFRS 16, AASB 16, or FRS 102, the support is delivered by the same team with the same expertise.

The fastest path for teams already on IFRS 16

For a team with clean IFRS 16 infrastructure, the FRS 102 transition isn't a project in the same sense that the original IFRS 16 adoption was. It's an extension job: take what's working, review what needs updating, and add what's genuinely new. The sequence below reflects what LOIS sees in practice with UK and Irish teams that already have the fundamentals in place.

For teams working through their first period under FRS 102 rather than transition planning, the five-point readiness check in your first FRS 102 period: why it's less daunting than IFRS 16 covers what a well-prepared close actually looks like.

Frequently asked questions