UK and Irish retailers face FRS 102 Section 20's hardest challenge at scale: concurrent CPI reviews, break options, and store closures. Here is how to manage it.
The spreadsheet had 220 tabs. One per store. The financial controller had built it over two weeks before the first FRS 102 reporting period, colour-coded by review date, and it was, by any reasonable measure, a serious piece of work. Then April came, and 47 of those tabs needed updating at once because 47 stores had CPI reviews falling in the same quarter. Each one a discrete FRS 102 Section 20 event. Each one requiring its own remeasurement calculation, its own revised amortisation schedule, its own journal entries. That's what "managing a retail lease portfolio at scale" actually means: not a one-off transition project, but a continuous operational process where the events never stop coming.
FRS 102 Section 20 is effective for accounting periods beginning on or after 1 January 2026. For a December balance date, transition must be complete by December 2026. For a March or June balance date, those deadlines are March and June 2026 respectively. This post is written for finance directors and financial controllers at UK and Irish retail groups who have adopted the standard and are now managing a large portfolio in the periods that follow. It covers the specific mechanics that make retail portfolios complex, where property and finance teams typically diverge, and how a unified platform removes the recurring risk from each. For a broader introduction to the standard, see: What is FRS 102? A plain-English guide for UK and Irish finance teams.
Updated August 2026.
Most sectors face FRS 102 Section 20 complexity at transition: a large balance sheet uplift, data collection work, and a new set of accounting policies to document. Retail carries all of that and adds something the hospitality or construction sectors don't face at the same scale: a portfolio of stores where lease events (rent reviews, break decisions, closures, extensions) happen continuously, across hundreds of sites simultaneously, driven by a property team that works to commercial timelines rather than accounting periods.
For an indicative picture: a 220-store UK high street retailer with average annual property rent of £120,000 per site and average remaining lease terms of eight years is looking at an opening lease liability somewhere in the range of £140–160 million on the balance sheet at transition. That number will change every quarter as CPI reviews fall due, break option assessments are revisited, and individual stores are extended or surrendered. Managing the accuracy of that liability is a permanent part of the finance team's monthly and quarterly workload, not a one-time transition exercise.
For context on how the standard changed reported financial ratios alongside the balance sheet, see: FRS 102 vs IFRS 16: Key differences finance teams need to know.
Under FRS 102 Section 20, a CPI-linked rent review is a variable lease payment linked to an index. When the reviewed rent takes effect (when the landlord confirms the new payment and your lease is updated to reflect it), that change triggers a remeasurement. Your right-of-use (ROU) asset and lease liability must be recalculated from the modification date, using the revised future payments discounted at the original obtainable borrowing rate. A new amortisation schedule is generated. New journal entries follow.
One remeasurement is manageable. Now consider a retail estate where CPI review dates were staggered at lease commencement, as they almost always are, and 50 of your 220 stores happen to have annual reviews falling in the same quarter. You have 50 concurrent FRS 102 events, each requiring its own calculation. If your finance team is managing this on spreadsheets, each remeasurement is a manual rebuild of a model that was last touched when the store was onboarded. If the spreadsheet contains an error, or if a review was agreed informally and the confirmation date was recorded differently by property and finance, those discrepancies compound quietly across the estate.
The problem is not the arithmetic; any competent model can run a remeasurement calculation. The problem is the operational workflow: capturing the confirmed new rent at the right date, triggering the recalculation for the right store, and ensuring the resulting journal is posted to the correct GL code in the right period. For a retail estate, that workflow needs to run dozens of times a quarter, reliably, without depending on a finance team member manually checking in with property to see whether a review has been settled.
For a detailed technical explanation of how CPI adjustments work under the standard, see: CPI adjustments under IFRS 16: How the accounting actually works.
What triggers an FRS 102 remeasurement in a retail portfolio?
Each of the following is a discrete FRS 102 Section 20 event that requires the ROU asset and lease liability to be recalculated:
Break options are one of the more nuanced ongoing judgements under FRS 102 Section 20, and retail's estate management reality makes them particularly demanding. The accounting treatment turns on a simple question: is it reasonably certain the break will not be exercised? If yes, the full lease term beyond the break is included in the liability. If circumstances change and the answer shifts, the lease term must be reassessed, and that reassessment is itself a Section 20 event.
In retail, that judgement is rarely static. A flagship store on a 15-year lease with a tenant break at year 8 is straightforward: strong trading, high investment in fit-out, no commercial reason to vacate. The break is almost certainly not going to be exercised; the full 15-year term is used and the liability is larger. But a marginal store in a secondary high street location, under-performing against targets, with a break option in 18 months' time and a lease review under way: that's a different assessment entirely. The property team managing that conversation knows before the finance team does.
What makes break options operationally difficult at scale is the communication lag. Property decides whether to pursue a break. The commercial rationale is often implicit; the property director knows which stores are under review without writing a memo to the financial controller. Under FRS 102 Section 20, that knowledge needs to translate into a documented accounting judgement before the reporting period closes. The contractual rolling structure does not determine the conclusion; the honest assessment of expected use does, and that assessment needs to be recorded, with supporting reasoning, in a form auditors can inspect. For a 220-store estate, a finance team that isn't directly connected to property's leasing decisions will always be working with a lag.
| Event | FRS 102 Section 20 consequence | Timing requirement |
|---|---|---|
| CPI rent review: new payment effective | Remeasurement of ROU asset and lease liability using revised payments at original discount rate. New amortisation schedule and journal entries. | From the date the new payment takes effect, not the review negotiation date. |
| Break option reassessment | Change in the assessed likelihood of exercising a break triggers lease term reassessment. Liability remeasured from the reassessment date with updated term. | When a significant event or change in circumstances affects whether it is reasonably certain the break will or won't be exercised. |
| Lease extension agreed | Lease modification (new or separate right of use). A new ROU asset and liability are recognised at the modification date; the original liability is derecognised for that element. | From the modification date (when both parties agree to the extension terms). |
| Store closure / early surrender | Scope reduction modification. Lease liability and ROU asset reduced proportionately; gain or loss on derecognised portion recognised in P&L immediately. | From the date the scope reduction takes legal effect. |
| Negotiated mid-term rent change | Lease modification requiring remeasurement of lease liability and, where the modification creates a new right of use, a corresponding ROU asset adjustment. | From the modification date. New discount rate applies if the modification creates a separate lease. |
| New store lease commenced | Initial recognition of ROU asset and lease liability. Discount rate set at obtainable borrowing rate; amortisation schedule established from commencement date. | At the commencement date of the new lease. |
Property teams manage locations. Finance teams manage the balance sheet. Under the old operating lease model, those two functions rarely needed to speak in real time: the rent hit the P&L and the balance sheet was unaffected. That separation was inefficient but it wasn't dangerous.
Under FRS 102 Section 20, that separation is the primary source of ongoing compliance risk. Every decision property makes about a lease is potentially a Section 20 event. When a property director agrees a new CPI-linked rent with a landlord in February, finance needs to know by the end of the period to process the remeasurement for Q1. When property decides not to exercise a break option on a store that is under strategic review, finance needs to know to reassess the lease term before the next reporting date. If those communications happen through email, verbal update, or periodic property-to-finance meetings, the lag between the commercial event and the accounting entry grows, and that lag turns into missed remeasurements.
Maeve O'Connell, LOIS Head of EMEA and a CA-qualified accountant with over 25 years' experience in lease accounting, describes the pattern across retail clients: "The complexity in a retail estate isn't any individual calculation; it's the fact that property events are happening all the time, and the finance team doesn't always know when one has accounting consequences. A break option decision happens in a property meeting. A rent review gets agreed in a landlord call. None of that is flagged as 'this now needs a journal.' A system that sits between property and finance makes those consequences visible as the events happen, not three months later in an audit query."
A missed remeasurement is not immediately visible. Your balance sheet continues to carry the previous liability schedule; journals post correctly against it; the period closes. The error sits in the amortisation schedule, growing quietly as each subsequent period uses the wrong opening balance. By the time the discrepancy surfaces, typically in an audit query about the movement in lease liabilities or during the year-end reconciliation between the lease subledger and the GL, it has affected multiple periods and the correction requires restating each of them.
Here's what that looks like in practice. Five stores have CPI reviews settled in Q1; the property team confirms the new rents informally and no one notifies finance until month four. Those five stores have had wrong journals posting since February. Fixing it means tracking down the precise modification date for each site, rebuilding the calculation from that date, reversing every incorrect entry, and posting replacements. Then the auditors ask for the documented rationale behind each correction, the date it was identified, and evidence the error has been corrected across every affected period. The finance team time is significant. The effect on audit confidence is worse, because it raises a question auditors don't easily put down: what else wasn't captured in time?
For a thorough breakdown of how modifications and reassessments are processed, see: FRS 102 lease modifications under Section 20: What triggers a remeasurement.
LOIS is designed for exactly the kind of portfolio a UK or Irish retailer operates: a large number of property leases, staggered review cycles, break options requiring documented judgements, and a property team that needs to track milestones without relying on finance to run each query. The platform brings lease accounting and property management into a single system, removing the handoff that sits between property decisions and accounting entries.
Consider what this looks like in a quarter where 40 stores have CPI reviews falling due. The LOIS property module sends automatic reminders as each review date approaches. When the property team confirms the new agreed rent for a site, they record it in the platform with the effective date. That change triggers a workflow notification to finance, who can action the FRS 102 remeasurement calculation directly in the same system. The revised liability schedule, updated amortisation, and new journal entries are generated from the modification date. Nothing is re-keyed. Nothing is sent by email. The audit trail records who confirmed the rent, when, and which calculation was produced as a result.
For break options, LOIS's portfolio timeline gives the property team visibility of every break date across the estate, with alerts as key dates approach. When a reassessment happens, the property team records the updated judgement and the reasoning, and finance can action the lease term update and associated remeasurement. The documented rationale sits permanently in the lease record, retrievable in seconds for any audit query.
The platform handles portfolios from 30 to 10,000+ leases, and retail is one of the LOIS Ideal Customer verticals: the combination of large property portfolios, continuous lease events, and the need to connect property and finance teams is exactly the operational profile the platform was built for. The financial controller with 220 tabs doesn't need a better spreadsheet. She needs a system that removes the manual rebuild entirely. For more on how the property management module works, see: LOIS Property Management.
FRS 102 Section 20 requires lessees to disclose a maturity analysis of undiscounted future lease payments, broken into standard bands: within one year, one to five years, and over five years. For a 220-store retailer, producing that analysis means aggregating the future payment schedules for 220 leases, each with a different remaining term, different review dates, and potentially different terms following the most recent modification. The FRC's guidance on Section 20 disclosures and the ICAEW technical guidance on the standard both make clear that this analysis is based on undiscounted contractual cash flows, which means it must reflect the current lease terms as at the reporting date, including any remeasurements processed during the period.
Assembling that from a spreadsheet model with 220 tabs is not a realistic exercise at close. Even if the model is technically correct, the number of inputs needed to confirm that every lease reflects its most recent modification, across a quarter in which 40 stores had reviews and three had break option assessments, is impractical to verify manually. The maturity analysis needs to be generated from a centralised system that holds the current position for every lease and can aggregate the undiscounted cash flows by band at the point of reporting. LOIS produces this as a standard output from the lease register, directly from the data used to generate the FRS 102 journals.
The other disclosure the FRC and ICAEW both emphasise is the qualitative narrative around key judgements: the basis for determining lease terms, the approach to break option assessments, and the rationale for any significant changes in estimates during the period. For a retail group where break option judgements are actively changing as the estate evolves, that narrative needs to be grounded in documented decisions, not reconstructed from memory at year-end. The audit trail sitting behind every modification and reassessment in LOIS is what makes that narrative defensible rather than approximate.
For the full breakdown of FRS 102 Section 20 disclosure requirements, see: FRS 102 Section 20 disclosure requirements: What UK and Irish lessees must report.
Does every CPI rent review trigger a fresh FRS 102 Section 20 remeasurement?
Yes. Under FRS 102 Section 20, a CPI-linked rent review is treated as a variable lease payment linked to an index. When the reviewed rent takes effect and the new payment amount is confirmed, that change triggers a remeasurement of the lease liability. The ROU asset and lease liability must be recalculated from the modification date using the revised future payments discounted at the original obtainable borrowing rate. For a 220-store retailer with annual reviews staggered across the estate, this is a recurring quarterly process, not a one-off event.
How does LOIS connect property and finance teams when a rent review is agreed?
LOIS provides a unified platform where the property team can record the agreed rent change, and the finance team can action the FRS 102 remeasurement calculation from the same system. The LOIS property module tracks upcoming rent reviews with automatic reminders and portfolio timelines. When property confirms a new CPI-adjusted rent, the workflow and approvals functionality notifies finance, who can action the remeasurement calculation without a manual handoff or email chain. The audit trail records who confirmed the new rent, when, and which calculation was produced as a result.
How do break options affect the lease liability for a retail store?
Under FRS 102 Section 20, a break option changes the lease term used to calculate the liability. If a break option is not reasonably certain to be exercised, the full lease term beyond the break is included in the liability, and the balance recognised is larger as a result. If circumstances change and the assessment shifts (a store becomes loss-making, or the landlord is unlikely to agree a rent reduction), the lease term must be reassessed. That reassessment is itself a Section 20 event. The judgement must be documented with reference to commercial factors, not just the contractual structure; auditors will scrutinise break clause assessments closely across a retail estate.
What does the FRS 102 Section 20 maturity analysis disclosure require for a large retail portfolio?
FRS 102 Section 20 requires lessees to disclose a maturity analysis of undiscounted future lease payments in standard bands: within one year, one to five years, and over five years. For a retailer with 200+ stores, each with different rent review dates, break options, and remaining terms, this disclosure cannot be assembled manually. The data must be drawn from a centralised lease register that holds the exact payment schedule for each lease (reflecting the most recent modification) and can aggregate undiscounted cash flows by maturity band as at the reporting date. LOIS produces this as a standard system output.
Can a retailer with 200+ stores manage FRS 102 Section 20 without specialist software?
It isn't practical. A portfolio of 200+ stores generates dozens of Section 20 events every quarter: CPI remeasurements, break option reassessments, lease extensions, and store closures each require updated calculations, revised amortisation schedules, and new journal entries. Managing that volume on spreadsheets introduces version control risk, removes the audit trail, and makes the maturity analysis disclosure almost impossible to produce accurately. LOIS is designed for portfolios from 30 to 10,000+ leases and handles retail-scale FRS 102 Section 20 compliance in a single platform that connects property and finance.
Manage your retail lease portfolio and FRS 102 Section 20 compliance in one platform
LOIS tracks CPI rent reviews, break option milestones, and lease modifications across your full retail estate. Property and finance teams work from the same data source, so every Section 20 event is captured and actioned in time, every period.
See FRS 102 on LOIS LOIS property management
UK hospitality and leisure businesses face some of the largest FRS 102 balance sheet impacts of any sector. Here is what hotels, pubs, and restaurant...
Your first FRS 102 reporting period is structurally simpler than it looks: no comparative restatement, a clearer discount rate, and an explicit...
Under FRS 102 Section 20, a lease requires three things: an identified asset, the right to substantially all economic benefits, and the right to...
Subscribe to our blog for fresh ideas and practical resources from the LOIS team.