The thesis: the lease and revenue rewrite is not where a group's first close gets hard.
On March 27, 2024, the Financial Reporting Council issued Amendments to FRS 102, the Financial Reporting Standard applicable in the UK and Republic of Ireland, and other FRSs, Periodic Review 2024, concluding its second periodic review of UK and Irish GAAP. The two headline changes, an on-balance-sheet right-of-use model for lessees in Section 20 and a five-step revenue recognition model aligned to IFRS 15 in Section 23, are effective for accounting periods beginning on or after January 1, 2026. For a calendar-year UK or Irish group, that is the period closing right now, the first annual report prepared entirely under the new standard.
Grant Thornton, citing the FRC's own estimate for the wider FRS 100 to 105 suite, puts the number of affected UK and Irish businesses at roughly 3.4 million, with more than three million of those reporting directly under FRS 102 itself. That is the scale of the change. The design question is narrower and less discussed: five sections carry the label "no major changes" in the FRC's own summary, and one of them, Sections 11 and 12 on financial instruments, contains a real consolidation-governance requirement inside what reads like a footnote.
What actually changed, section by section.
The FRC rates Section 20 and Section 23 as the two areas of fundamental change, and every piece of practitioner guidance published since March 2024 has focused there, for good reason. The table below adds the sections that matter for a group close but rarely make the headline summary.
| Section | What changed | Why it matters for the group close |
|---|---|---|
| Section 20, Leases | New right-of-use model for lessees; removes the operating and finance lease distinction; short-term and low-value exemptions remain off-balance sheet | Every material lease becomes a balance sheet item, with initial measurement, ongoing interest, and depreciation entries to run per lease |
| Section 23, Revenue | A single five-step model for revenue from contracts with customers, aligned to IFRS 15 | Contract-level judgment on distinct performance obligations and transaction price replaces the older, less structured revenue model |
| Section 9, Consolidated and Separate Financial Statements | The FRC’s own summary calls this “no major changes,” with minor clarification to the parent exemption test | Consolidation scope barely moves. That stability is exactly why the real governance gap sits in the sections rated as minor |
| Sections 11 and 12, Financial Instruments | An entity can no longer change its accounting policy between these sections and IAS 39, except to make its policy consistent with the consolidated financial statements it is included in | A first explicit, standard-level link between a subsidiary’s own policy election and the group’s consolidated policy |
| Section 35, Transition to this FRS | New transitional provisions for first-time application of the lease and revenue models, plus disclosure of the transition impact and elections taken | Each subsidiary’s transition choices need to be documented and available for group-level review, not filed locally and forgotten |
| Section 2A, Fair Value Measurement | Definitions updated to align with IFRS 13 | Affects property under the revaluation model, investment property, and associates or joint ventures held at fair value, all of them consolidation inputs |
The FRC is explicit about scope, too. The Periodic Review 2024 amendments do not introduce an expected credit loss model of financial asset impairment, the approach used in IFRS 9, and they do not align FRS 102 with IFRS 17 on insurance contracts. Any further move in either direction is a separate future project, subject to its own consultation. That containment is worth stating plainly: this is a scoped, deliberate rewrite of two sections, not an open-ended alignment exercise, and a group finance team can plan against a known perimeter.
Entity-level bookkeeping versus group-level policy governance.
Calculating a right-of-use asset and a lease liability per lease, and applying the five-step revenue model per contract, is thoroughly documented. Every major accounting firm has published a detailed guide, and lease accounting software already understands the mechanics. That is the well-covered half of the work, and it happens once per entity.
The less-covered half is what Sections 11 and 12 quietly introduce: an entity can no longer switch its accounting policy between applying Sections 11 and 12, or a combination of IFRS 9 and IAS 39, except specifically to make its own policy consistent with the consolidated financial statements the entity is included in. That is the first time the standard ties a subsidiary's own policy choice directly to the parent's consolidated policy, rather than leaving it as a standalone judgment. A group with forty FRS 102 subsidiaries now has forty policy elections that need to agree with one consolidated policy, and no built-in way to check that beyond asking each entity individually.
| Dimension | Entity-level work | Group-level governance |
|---|---|---|
| Lease measurement | Calculate the right-of-use asset and lease liability per lease, using the discount rate and payment schedule | Confirm whether the group already applies IFRS 16, and whether those existing carrying amounts can become the FRS 102 opening balance instead of a second calculation |
| Revenue recognition | Apply the five-step model contract by contract at the entity | Track which subsidiaries used which practical expedients and transition approach, so the group’s own transition note is consistent across entities |
| Financial instruments policy | Choose a Section 11 and 12 treatment for each instrument class | Confirm every subsidiary’s policy actually matches the parent’s consolidated policy, a stated requirement now rather than a standalone entity’s discretionary choice |
| Transition disclosure | Disclose the impact of transition at the entity’s own financial statements | Aggregate and evidence transition elections across every FRS 102 subsidiary for the group auditor and, where relevant, the parent’s own reporting |
| Audit evidence | One entity’s file, reviewed by one local auditor | One controller able to show the same policy and the same transition story holds across every subsidiary that reports under FRS 102 |
The transition relief that only works with a connected ledger.
There is a genuine efficiency built into the transition rules, and it rewards groups that already have their data connected. Practitioner guidance on the 2026 transition confirms that where an entity already reports into a group applying IFRS 16, the existing carrying amounts can be used as the opening balance for the FRS 102 subsidiary's own right-of-use asset and lease liability, rather than recomputing the same lease from scratch under a second framework.
That relief is only available in practice if the group's lease register already flows down to each subsidiary's statutory books. A group that keeps its IFRS 16 lease data in one system and its FRS 102 subsidiary accounts in another, disconnected one gets no benefit from the transition rule, and ends up running the same lease calculation twice, once at group level and once again, independently, at every subsidiary. The design work worth doing now is making that connection explicit, not assuming it already exists.
Entity identifier
The subsidiary or reporting entity this register row belongs to, tied to the same identifier used in the group consolidation system.
Financial instruments policy elected
Which treatment the entity applies under Sections 11 and 12, and the date it was last confirmed.
Group consolidated policy reference
The equivalent policy the parent applies in the consolidated financial statements, so the two can be compared directly rather than from memory.
Consistency status
Matched, divergent with a documented reason, or pending review, since a divergence is now a standard-level question, not a local judgment call.
Lease transition approach
Full retrospective, modified retrospective, or reuse of existing group IFRS 16 carrying amounts as the opening balance.
Opening balance source
Whether the right-of-use asset and lease liability were recomputed at the entity or carried down from the group’s own IFRS 16 ledger.
Transition disclosure owner
The named person who confirms the entity’s transition note is complete and consistent with the group narrative before sign-off.
Next review date
When this row is checked again, timed ahead of the FRC’s further IFRS 18 aligned amendment, effective for periods beginning on or after January 1, 2027.
The record one subsidiary's transition needs.
A structured record like the one below, held alongside the group's existing consolidation workpapers, keeps the financial instruments policy check and the lease transition decision visible together, instead of splitting the audit trail across a local statutory file and a group spreadsheet that may or may not be current.
Example subsidiary transition and policy-consistency record
{
"entity_id": "sub-uk-0417",
"framework": "FRS 102 (Periodic Review 2024)",
"financial_instruments_policy": {
"elected": "Section 11 and 12, basic and other financial instruments",
"group_consolidated_policy": "Section 11 and 12, basic and other financial instruments",
"consistency_status": "matched",
"last_reviewed": "2026-06-30"
},
"lease_transition": {
"approach": "modified_retrospective",
"opening_balance_source": "reused_from_group_ifrs16_ledger",
"opening_rou_asset": 4218500,
"opening_lease_liability": 4360200,
"practical_expedients_applied": ["short_term_exemption", "low_value_exemption"]
},
"revenue_transition": {
"approach": "cumulative_catch_up",
"contracts_reassessed": 214,
"material_judgment_areas": ["variable_consideration", "principal_vs_agent"]
},
"transition_disclosure_owner": "Group technical accounting lead",
"next_review": "2027-01-01"
}The consistency status field is what turns Sections 11 and 12's new requirement from a standard clause into something a group controller can actually confirm, entity by entity, before sign-off.
Implementation checklist.
Build one policy-consistency register covering every FRS 102 subsidiary, recording each entity’s financial instruments policy against the group’s consolidated policy, rather than trusting that local statutory accounts already agree.
Ask whether the group already prepares consolidated numbers under IFRS 16. If it does, confirm which subsidiaries can reuse those carrying amounts as their FRS 102 opening right-of-use balance instead of running a second lease calculation.
Assign a single transition approach per subsidiary, full retrospective or modified retrospective for both leases and revenue, and record it once rather than letting each preparer choose independently.
Capture the practical expedients used at each entity, short-term and low-value lease exemptions in particular, so the group note on transition reads as one coherent policy rather than a patchwork.
Route the Section 11 and 12 policy check through the same sign-off as the group’s own consolidated accounting policy note, since the standard now treats the two as connected.
Document the judgment areas in the new five-step revenue model, principal versus agent and variable consideration in particular, at the entity level, and flag any that affect intercompany trading eliminated on consolidation.
Rehearse the transition disclosure for at least one subsidiary before the group’s first full close under the new standard, so the evidence format is proven before every entity needs it at once.
Set a review date tied to the FRC’s further amendment aligning FRS 102 to IFRS 18 presentation, effective for periods beginning on or after January 1, 2027, so this register extends rather than needing to be rebuilt.
Start with the subsidiaries carrying the largest lease portfolios or the most complex customer contracts, since those are where a transition judgment has the most financial weight. Smaller, single-lease entities still need a register row, but they carry less risk if the review happens a week later.
Constructive failure modes to design around.
Treating the lease and revenue rewrite as a set of forty separate entity-level projects, one per subsidiary, with no shared register to confirm the group’s own consolidated policy is actually being followed everywhere.
Recomputing right-of-use assets and lease liabilities from scratch at every FRS 102 subsidiary, when the group already holds the same leases on an IFRS 16 basis and could hand down the opening balance instead.
Reading Section 9’s “no major changes” rating as meaning nothing about consolidation changed, and missing that Sections 11 and 12 now make policy consistency across the group an explicit standard requirement.
Filing each subsidiary’s transition disclosure locally with no group-level view of which entities chose which approach, so the group auditor has to reassemble the picture from scratch at year end.
Leaving the policy-consistency check as a one-time exercise for the 2026 transition, instead of a standing register that also covers the FRC’s further IFRS 18 aligned amendment landing for periods from January 1, 2027.
Each of these is a coordination gap a shared register closes directly. None of them requires new lease accounting technology; most require deciding, once, that the group level is where the FRS 102 transition gets confirmed, not just where it gets reported.
What to ask consolidation and lease accounting vendors now.
Can the consolidation platform hold a per-subsidiary accounting policy register, and flag automatically when a subsidiary’s Section 11 or 12 election diverges from the group’s consolidated policy?
If the group already reports under IFRS 16, can the same lease data feed both the group consolidation and each FRS 102 subsidiary’s opening right-of-use balance, rather than requiring separate entry?
Does the system record which transition approach, full retrospective or modified retrospective, each entity used for leases and for revenue, as a queryable field rather than free text in a memo?
Can it produce, for a group auditor, a single view of every subsidiary’s transition elections and practical expedients used, rather than requiring a file pulled from each entity separately?
Is the platform’s FRS 102 configuration already tracking the FRC’s further IFRS 18 aligned presentation amendment, effective for periods beginning on or after January 1, 2027, or will that be a separate project?
A vendor that answers all five with a working feature, not a roadmap promise, has already built the group-connected path this transition rewards, which leaves the policy review itself as the only judgment call left for the technical accounting team.
Practical takeaway.
The Periodic Review 2024 amendments to FRS 102 are a scoped, well-telegraphed rewrite of two sections, and the entity-level mechanics of applying them are already thoroughly documented. The opportunity a group finance team should not leave on the table is the quieter part: a connected lease ledger that lets FRS 102 subsidiaries reuse group IFRS 16 numbers instead of recomputing them, and a policy-consistency register that turns Sections 11 and 12's new requirement into something confirmed once, across every entity, rather than discovered separately in each one. The FRC's own further amendment aligning FRS 102 to IFRS 18 presentation, effective for periods beginning on or after January 1, 2027, is confirmation that this alignment programme is not finished. A register built now extends for that round instead of needing to be rebuilt.
Sources.
- Financial Reporting Council: Financial reporting standards, Periodic Review 2024, Key changes
- EY UK: FRS 102 Periodic Review 2024, What is changing? (February 2026)
- Grant Thornton UK: Summary of 2024 amendments to FRS 102
- Grant Thornton Northern Ireland: FRS 102, what’s changing and why it matters
- ICAEW: FRC issues amendments to FRS 102 and FRS 105 (March 2026)
- FM Magazine (AICPA and CIMA): FRC issues amendments to FRS 102 (February 2026)
- PKF Smith Cooper: FRS 102 changes effective from 1st January 2026
Targeted searches for public X and Twitter commentary on FRS 102's Periodic Review 2024 and its January 2026 effective date returned only accounting-firm and standards-body pages, short of a credible set of two to four high-signal posts from a regulator or an independent practitioner. Ordinary citations are used instead, and nothing is fabricated.