Most UK and Irish finance teams have now worked through the technical requirements of FRS 102 Section 20. The on-balance-sheet model is understood, the obtainable borrowing rate is on the agenda, and the first transition calculations are either done or underway. The question that will define the next several years, however, is not whether your team understands the standard. It is whether your system can sustain compliant, defensible reporting as leases change, portfolios grow, and auditors ask harder questions.
That is the lesson from IFRS 16. The teams that struggled were rarely those who got the initial accounting wrong. The risk surfaced later, when a lease was modified and the system could not handle it cleanly, when an auditor asked for the full history of a reassessment and the team could not reconstruct it, or when a key person left and no institutional memory remained in the tool itself. FRS 102 preparers have the advantage of seeing this pattern in advance.
This guide is for finance managers, financial controllers, and CFOs evaluating software for FRS 102 Section 20 compliance. It covers the six criteria that separate adequate systems from genuinely reliable ones, a comparison of the main software categories, the questions to ask vendors before signing, and an introduction to how LOIS approaches FRS 102 support.
Updated May 2026.
FRS 102 Section 20, effective for accounting periods beginning on or after 1 January 2026, requires lessees to recognise most leases on the balance sheet as a right-of-use (ROU) asset and corresponding lease liability. The modified retrospective transition approach is the only option available under the standard, with no restatement of comparative periods. Approximately 3.4 million businesses in the UK and Republic of Ireland are affected (FRC estimate).
The initial transition calculation, while complex, is a one-time exercise. What creates sustained operational pressure is everything that comes after: lease modifications, reassessments of the lease term, changes in index-linked payments, renewals, and early terminations. Every one of these events requires recalculation, documentation, and consistent application across reporting periods. A system that handles initial recognition but struggles with ongoing modifications is not fit for the standard. For the mechanics of how right-of-use assets are measured at initial recognition, see our plain-English IFRS 16 ROU asset guide, which covers the same foundational concepts that carry through to FRS 102.
Spreadsheets carry a specific risk in this environment. They rely on process discipline rather than embedded controls. Version history, access rights, and audit trails sit outside the tool. As portfolios grow and team members change, cumulative risk increases quietly until an auditor surfaces it. The FRC's experience reviewing IFRS 16 disclosures showed that audit scrutiny shifted away from whether the numbers were correct and toward how decisions were made, how changes were tracked, and whether consistency could be demonstrated over time.
Generic accounting add-ons present a different problem. Most ERP lease modules and bookkeeping software bolt-ons were built to handle initial recognition and basic amortisation. They were not designed around the ongoing modification lifecycle that FRS 102 requires, and they typically produce compliance outputs rather than audit trails. For straightforward portfolios with few changes and no audit pressure, they may be adequate. For organisations with dynamic lease portfolios and external audit obligations, they tend to fail on modifications and reassessments.
For a detailed explanation of what FRS 102 Section 20 requires from a technical accounting perspective, see FRS 102: what UK businesses need to know about the new standard. For the mechanics of ROU asset measurement under the standard, including how the OBR interacts with initial recognition, see our FRS 102 right-of-use assets guide.
These six criteria reflect what distinguishes systems that hold up under sustained FRS 102 reporting from those that handle initial transition but create problems later. They are ordered by the sequence in which they typically matter during the post-transition reporting cycle.
The table below assesses three categories of software against the criteria above. It is designed to help finance teams quickly identify where different approaches are likely to hold up and where they typically fall short under sustained FRS 102 reporting. Specific tools within each category will vary, so use this as a framework for your own evaluation rather than a definitive verdict on any individual product.
| Criterion | Purpose-built lease accounting platform (e.g. LOIS) | Generic accounting add-on or ERP module | Spreadsheets |
|---|---|---|---|
| Automated ROU and liability calculations incl. OBR | Full support, including OBR as a direct input and portfolio discount rate grouping | Partial: IBR typically supported, OBR may require a workaround or be absent | Manual: rate entered by user with no calculation validation or version control |
| Modification and reassessment handling | End-to-end within the platform: modification type, remeasurement, and ROU adjustment all handled | Partial: basic modifications may be supported; complex reassessments often require manual workarounds | Manual: each modification requires a new calculation, with high risk of version error |
| Audit trail for every change | Full: every change is timestamped, attributed, and stored within the platform | Partial: change logs exist but may be at system level rather than lease level | None: no embedded audit trail; history depends on file naming and version discipline |
| GL integration and automated reconciliation | Full: direct journal generation and automated sub-ledger to GL reconciliation | Partial: native to the parent ERP but may require manual mapping for lease-specific entries | None: journals prepared manually from schedule outputs |
| Disclosure reporting | Full: FRS 102-aligned disclosure outputs produced directly from the platform | Partial: standard reports exist but may not align to FRS 102 Section 20 disclosure requirements specifically | Manual: disclosures assembled from schedule data, requiring significant reformatting |
| Expert support beyond go-live | CA-qualified lease accounting experts available for accounting judgements, not just platform support | Vendor helpdesk covers platform questions; accounting judgements referred back to the user or external advisers | None: all judgements and calculations rest with the preparer |
The IFRS 16 transition gave the accounting profession a detailed case study in where on-balance-sheet lease accounting creates sustained operational risk. The initial adoption calculations were manageable for most organisations. The difficulties came later, during the ongoing reporting cycle, and they were concentrated in a few specific areas.
"The teams that struggled under IFRS 16 were rarely those who got the initial accounting wrong. The risk surfaced when a lease was modified and the system could not handle it cleanly."
LOIS lease accounting experts, drawing on IFRS 16 transition experience
Lease modifications were the primary failure point. When a tenant renegotiated terms, extended a lease, or reduced scope, systems that had handled initial recognition adequately were often unable to process the modification correctly. The remeasurement logic was either absent or required substantial manual intervention, creating a gap between the system output and the required accounting. Teams that had started with spreadsheets found that each modification compounded the complexity of the model, and by the second or third year, reconciling back to the original transition calculation had become a significant annual exercise.
Audit readiness was the second failure point. FRC thematic reviews of IFRS 16 disclosures revealed consistent weaknesses in how organisations documented reassessments and justified discount rate selections. Auditors began asking for the complete history of a lease, including every modification and the basis for any change in lease term assumptions. Organisations that held this information in spreadsheets or in disconnected systems could not produce it efficiently, leading to extended audit timelines. For teams new to the on-balance-sheet model, our IFRS 16 ROU asset guide explains the foundational concepts that apply equally under FRS 102 Section 20.
Key person dependency was a quieter risk. Lease accounting under IFRS 16 is technically demanding, and in many organisations, one person held the spreadsheet model, understood the discount rate logic, and managed the modification process. When that person left, the institutional knowledge left with them. A purpose-built system embeds that logic in the platform itself, making the accounting reproducible and transferable regardless of team changes.
FRS 102 preparers are entering this environment with the benefit of hindsight. The standard's requirements are substantively similar to IFRS 16 in the areas where IFRS 16 created the most operational difficulty. Organisations that choose their software with the modification lifecycle and audit trail requirements at the centre of their evaluation will be in a substantially better position than those who optimise for the transition calculation alone.
LOIS is not the only purpose-built option available to FRS 102 preparers. A fair evaluation should include platforms that have been specifically developed or adapted for UK GAAP requirements. The following are the most frequently shortlisted alongside LOIS in the UK and Irish market.
The differentiating factor for LOIS in this field is the combination of CA-qualified lease accounting experts embedded in the support model and the availability of a Managed Service option for organisations that want expert-run monthly processing rather than a self-service platform. That combination is not available from the other platforms listed above in the same form.
A vendor demo will typically show you the best-case scenario. These eight questions are designed to surface the areas where systems most commonly fail under sustained FRS 102 reporting. Ask for a live demonstration of each, not a description.
Eight questions to ask every vendor
LOIS is an expert-led lease accounting and management platform built by CA-qualified accountants. It handles lease portfolios from 30 to over 10,000 leases across property, fleet, and equipment asset classes. For FRS 102 preparers, LOIS provides:
For finance teams that want the compliance outcomes without managing the monthly processing themselves, the LOIS Managed Service combines the platform with expert-run monthly processing. LOIS experts validate lease data, run calculations, prepare journals mapped to your GL, and deliver a fully reconciled, audit-ready reporting pack each month. It is the option chosen by organisations that want the standard met reliably, without building internal lease accounting capacity around it.
To see how LOIS handles FRS 102 Section 20 in practice, including the modification workflow and disclosure outputs, visit the LOIS lease accounting platform page.
Related FRS 102 guides
Yes. LOIS supports FRS 102 Section 20 lease accounting, including automated ROU asset and lease liability calculations using the obtainable borrowing rate (OBR), full modification and reassessment handling, GL integration, and FRS 102-aligned disclosure reporting. The platform is supported by CA-qualified lease accounting experts who can advise on accounting judgements specific to the standard, not just platform configuration. A Managed Service option is also available for organisations that want expert-run monthly processing.
The obtainable borrowing rate (OBR) is the discount rate used under FRS 102 Section 20 to calculate the present value of future lease payments. It is defined as the rate of interest that a lessee would have to pay to borrow, over a similar term and with a similar security, the funds necessary to obtain an asset of a similar value to the right-of-use asset in a similar economic environment. The OBR differs from the incremental borrowing rate (IBR) used under IFRS 16 in its precise definition; in practice, the two concepts are closely related, but software built specifically around IBR methodology may require adaptation to accept OBR as a direct input. For a detailed explanation of how OBR interacts with ROU asset recognition, see our FRS 102 right-of-use assets guide and our plain-English IFRS 16 ROU asset guide.
For organisations with a small number of simple, unchanged leases and no external audit obligation, a carefully maintained spreadsheet may be sufficient for initial compliance. For the majority of organisations subject to external audit, with portfolios that will experience modifications, renewals, or reassessments over time, a purpose-built lease accounting platform provides materially stronger audit readiness, reduces the risk of error in ongoing reporting, and removes the key person dependency that spreadsheet-based processes create. The question is not only whether you can adopt the standard, but whether your system can sustain compliant reporting across the full life of each lease.