For many firms managing leases in the U.K. and Ireland, FRS 102 has long been a relatively stable part of the reporting landscape. However, that changes with the revised Section 20 of the financial reporting standard.
For periods beginning on or after Jan. 1, 2026, FRS 102 Section 20 moves lessee lease accounting into an on-balance-sheet model that is deliberately aligned with IFRS 16. Right-of-use assets and lease liabilities will now appear on the balance sheet for most lessee leases. Short-term and low value exemptions offer some relief, but the days of treating most leases as straight-line operating expenses are over.
Technically, the story is straightforward: a single lessee model, right-of-use assets and lease liabilities measured at the present value of future lease payments and greater disclosure requirements. In practice, the real test for firms will not be understanding the debits and credits. It will be whether their audit and accounting workflows can absorb the change without burning out staff or disrupting clients.
A familiar standard, a new operational challenge
Most of the mechanics will be familiar with groups already reporting under International Financial Reporting Standards. The updated Section 20 definition of a lease mirrors IFRS 16: a contract that conveys the right to control the use of an identified asset for a period of time in exchange for consideration. Lessees recognize an ROU asset and lease liability for most leases, with relief for short-term and low value leases.
What is different this time is timing and concentration. Under FRS 102, the lease changes arrive alongside other amendments, including revenue and disclosure updates. Many firms will be adjusting to a new leases model and revisiting revenue at the same time. The question becomes less about "Can we interpret the new rules?" and more "Can our people and processes handle this extra lift?"
Where lease accounting strains audit workflows
The first challenge is building a complete lease population. It is easy enough to list the obvious contracts, but less obvious to find service arrangements that contain embedded leases or recurring payments in the general ledger that represent lease arrangements in all but name. That work requires structured searching and judgment, not just a skim through the trial balance.
Then there is the issue of exemptions. Section 20 gives more flexibility than IFRS 16 on low-value leases. There is no explicit monetary threshold. Instead, the standard lists categories of assets that cannot be treated as low value and leaves firms to define what does qualify. Short-term leases are elected by class of underlying asset. Low-value leases are elected lease by lease. Without clear, documented policies, different teams will inevitably make different calls on similar leases, and reviewers will spend time unpacking those differences.
Once leases are identified and scoped, firms still have to turn principle into process. Initial recognition of the ROU asset and lease liability, ongoing depreciation and interest, and the entries required for reassessments and modifications when terms change all have to be handled consistently. A spreadsheet and a handful of templates may be enough for a small portfolio, but as the number of leases and entities grows, errors become more likely, and small changes turn into hours of rework.
Judgment also plays a larger role than many expect. The revised standard imports the IFRS 16 "reasonably certain" concept. Lessees must weigh contract terms, economic incentives, historic behavior and other factors to decide whether extension or termination options are reasonably certain to be exercised and whether purchase options will be taken. These are not one-off decisions made on day one. Significant events and changes in circumstances can trigger reassessment and, with it, changes to both the lease liability and the ROU asset. If there is no clear way to capture and track those events and judgments, review teams end up trying to reconstruct why something changed rather than assessing whether the current position is defendable.
On top of this, the disclosure bar rises. The new Section 20 asks lessees for more than the old guidance did: movements in ROU assets by class, analyses of short-term and low-value leases, maturity analyses of lease liabilities, and information on discount rates, options and key terms.
What FRS 102 Section 20 changes for U.K. and Ireland specifically
Because Section 20 is so heavily based on IFRS 16, some assume an IFRS 16 playbook can be dropped straight into an FRS 102 environment. While true broadly, some of the key differences include:
- Low-value leases: IFRS 16 points to a conceptual low-value threshold and gives examples of assets that typically qualify. FRS 102 does not set a hard number. Instead, it provides a list of assets that cannot be treated as low value, including vehicles, land and buildings and heavy production equipment.
- Discount rates: Both standards prefer the rate implicit in the lease if it can be readily determined; otherwise an incremental borrowing rate. FRS 102 adds the notion of an "obtainable borrowing rate" based on borrowing the total undiscounted lease payments over a similar term.
- Transition approach: FRS 102 Section 20 uses a modified retrospective approach, so comparatives are not restated. In many cases, the ROU asset at transition will equal the lease liability, adjusted for existing prepayments and accruals.
None of these differences changes the core model, but they do affect what data firms need to collect, how they document policy decisions and where they focus review time.
Lessons from IFRS 16 and ASC 842 adopters
The advantage of adopting later is that other firms have already been through something similar. In our work with IFRS 16 and ASC 842 adopters, the firms that fared best tended to share a few habits.
They began with inventory and policy, not with spreadsheet design. They built lease inventories, including potential embedded leases, and agreed early on how they would apply short-term and low value exemptions. They decided how ROU assets and lease liabilities would be presented.
They standardized the way they recorded leases by defining a small set of journal entry patterns for initial recognition, ongoing accounting and common modification scenarios. Those patterns were built into methodology and training and, where possible, into the tools they used.
They realized that lease accounting software helped to streamline most of the processes. Purpose-built lease accounting tools reduced manual work; kept ROU assets, lease liabilities and disclosures in sync; and made it much easier to cope with reassessments and modifications.
Where to focus now
FRS 102 Section 20 is now in effect for periods beginning on or after Jan. 1, 2026. Whether your first affected period is already underway or still ahead this year, the priority is the same. The most effective use of that time is not memorizing every paragraph of the standard. It is designing workflows that make compliance repeatable.
That means taking a sample of clients and identifying how leases and lease-like arrangements are recorded today, agreeing on policies for short-term and low-value leases with concrete examples, mapping the process from client data intake through calculations to disclosures, and determining when software makes the most sense.
At its core, FRS 102 Section 20 is a familiar lease-accounting model. The firms that navigate it most smoothly will be the ones that have clear, repeatable workflows their people can follow, even in the busiest weeks of the year.
Jess Vento is the senior director of solution engineering, education and support at
Steve Stock is an ACA-qualified accountant and ICAEW member who trained at KPMG. Over the 15 years since, he moved from group reporting accountant to financial director and shareholder across industries including automotive leasing, professional services and pharmaceuticals, working with both IFRS and U.K. GAAP along the way. He now leads FRS 102 Section 20 support and training at
