FRS 102 lease accounting software: How to choose the right system

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.

Why FRS 102 Section 20 demands a purpose-built system

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.

Six criteria for evaluating FRS 102 lease accounting software

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.

• Automated ROU asset and lease liability calculations, including OBR support. The system must handle the full measurement model: present value of future lease payments, initial direct costs, lease incentives received, and ROU asset depreciation over the lease term. Critically, it must support the obtainable borrowing rate (OBR) as the discount rate input. The OBR is unique to FRS 102 and does not exist under IFRS 16; software built purely around IBR methodology will require workarounds to comply. Ask specifically whether OBR can be entered and used directly, and whether portfolio discount rates (permitted under FRS 102 for portfolios with similar characteristics) are supported.
• Full modification and reassessment handling. This is where most systems are tested and many fail. Lease modifications under FRS 102 Section 20 require the system to assess whether a change creates a new separate lease or modifies the existing one, recalculate the lease liability at a revised discount rate, and adjust the ROU asset accordingly. Reassessments of lease term, purchase options, and variable payments add further complexity. The system must handle these scenarios reliably without requiring manual spreadsheet work to supplement it. Confirm by asking for a worked example of a mid-lease extension processed end-to-end within the platform.
• Audit trail for every change. The system must record who changed what, when, and why, across the full life of every lease. This is not optional under FRS 102 reporting: auditors reviewing leases in year two or three of the new standard will ask for the complete history of a lease, including the basis for any reassessments and the discount rate applied at each modification date. A system that overwrites prior data or holds history only in export logs is not audit-ready in the way the standard requires.
• GL integration and automated reconciliation. The system should generate journal entries directly compatible with your general ledger, with automated reconciliation between the lease sub-ledger and the GL. Manual journal preparation from a system that produces schedules but not postings introduces a reconciliation step that consumes time at month-end and creates a gap between the system of record and the reported numbers. Ask whether the integration is bi-directional, whether it handles multiple entities, and whether reconciliation reports are produced automatically.
• Disclosure reporting. FRS 102 Section 20 requires quantitative and qualitative disclosures including ROU asset movement schedules by asset class, a maturity analysis of lease liabilities (disaggregated by year for the first five years, then in aggregate), interest expense, depreciation, and short-term or low-value lease commitments. The system should produce these reports in a format that can be included directly in financial statement preparation, not in a format that requires significant reformatting. Ask what the disclosure output looks like and whether it has been reviewed against the FRC's requirements.
• Expert support beyond go-live. Software without accounting expertise behind it transfers compliance risk back to the user. The questions that arise during the first full reporting cycle under FRS 102 are not configuration questions; they are accounting judgements: whether a particular contract modification is a new lease or a modification, how to treat a break option that has become reasonably certain to be exercised, or how to document the basis for an OBR where the entity has limited recent borrowing history. The support team needs to understand FRS 102 Section 20, not just the platform. Assess whether your support contact is an accountant or a helpdesk agent.

Software categories compared against the six criteria

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.

The IFRS 16 lesson for FRS 102 preparers

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.

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.

Other FRS 102 lease accounting platforms worth evaluating

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.

• Rubli is a purpose-built UK GAAP lease accounting platform designed specifically for SMEs adopting FRS 102 Section 20. It is built around the modified retrospective transition and supports OBR as a discount rate input. A strong option for smaller portfolios where simplicity and a straightforward user experience are the primary requirements.
• FinQuery (formerly LeaseQuery) is a US-origin platform with a significant UK client base and confirmed support for FRS 102. It is strong on disclosure reporting and GL integration, and is a credible option for mid-market to enterprise organisations with established US-style accounting infrastructure.
• House of Control is a cloud-based platform with a specific Section 20 implementation module. It is particularly well-suited to organisations managing property-heavy portfolios and has a focus on the lease event management (rent reviews, expiries, break options) that sits alongside the accounting requirement.

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.

Eight questions to ask in vendor demos

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.

How LOIS supports FRS 102

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:

• Automated ROU asset and lease liability calculations with OBR support as a direct input
• Full modification and reassessment handling within the platform, with no manual supplementation required
• A complete, timestamped audit trail for every lease event and change
• GL integration with automated sub-ledger to GL reconciliation
• FRS 102 Section 20 disclosure reporting produced directly from the platform
• CA-qualified lease accounting expert support for accounting judgements, not just platform queries

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.

Frequently asked questions

Does LOIS support FRS 102?

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.

What is the obtainable borrowing rate under FRS 102?

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.

Do I need specialist software for FRS 102 Section 20?

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.