IFRS 19 retires the second set of books, one subsidiary at a time.

The thesis: this is an entity master data decision wearing accounting clothes.

Most groups carry a quiet tax that nobody has ever put a number on. A subsidiary keeps one set of records to satisfy its local statutory filing and another to satisfy the group reporting pack, and somebody reconciles between them every period. It is not dramatic. It shows up as a few extra days in the local close, a line of local GAAP expertise the shared service centre has to keep hiring for, and a reconciliation that gets explained to the auditor the same way every year.

IFRS 19 is aimed squarely at that tax. It is a voluntary IFRS Accounting Standard, issued on 9 May 2024, that lets an eligible subsidiary keep full IFRS recognition, measurement and presentation while publishing a much shorter set of notes. It takes effect for annual reporting periods beginning on or after 1 January 2027, with earlier application permitted. The UK Endorsement Board approved the final adoption documents at its public meeting on 23 April 2026 and published them on 13 May 2026. In the EU the Accounting Regulatory Committee voted in favour on 5 June 2026, and EFRAG expects endorsement in the third or fourth quarter of 2026, ahead of the effective date.

The interesting part for anyone who runs finance systems is not the disclosure list. It is the unit of decision. IFRS 19 is elected by an entity, for a period, against three tests that are assessed at the end of that reporting period. Two of those three tests depend on facts that live outside the entity. That combination makes it a dated attribute of a legal entity, sitting next to functional currency and consolidation method, rather than a group accounting policy written down once.

There is a second consequence, and it is the one worth getting right before anything else. IFRS 19 changes what a subsidiary publishes. It changes nothing about what the group needs, because the parent still prepares full IFRS consolidated financial statements. A group that holds those two ideas in the same field will save a fortnight in the local close and lose the data the consolidation depends on. A group that holds them separately gets the simplification for free.

What the standard actually does, in three sentences and one table.

IFRS 19 specifies the disclosure requirements an entity is permitted to apply instead of the disclosure requirements in other IFRS Accounting Standards. It does not change recognition, measurement or presentation, which must still be followed. An eligible subsidiary applying it still asserts compliance with IFRS Accounting Standards and states that it has applied IFRS 19.

The reduced disclosures are organised under the heading of each IFRS Accounting Standard, so the requirements for inventories sit under IAS 2 and the requirements for financial instruments sit under IFRS 7. That structure matters more than it looks: it means the reduced set can be modelled as a scope matrix keyed by standard rather than approximated as a shorter checklist. The standard also requires additional disclosures where the reduced set would leave users unable to understand the entity’s financial position, performance and cash flows, so the shorter list is a floor with a judgement attached.

The three eligibility conditions are assessed at the end of the reporting period, and an entity may elect in its consolidated, separate or individual financial statements. That last point is easy to skip past. An intermediate parent that meets the conditions can apply IFRS 19 in its own consolidated financial statements, which means the election is available partway up a chain rather than only at the bottom of it.

The public accountability test has two limbs. An entity has public accountability if its debt or equity instruments are traded in a public market, or it is in the process of issuing such instruments for trading in one, including local and regional markets and over the counter markets. It also has public accountability if it holds assets in a fiduciary capacity for a broad group of outsiders as one of its primary businesses, which is the limb that commonly captures banks, credit unions, insurance companies, securities brokers and dealers, mutual funds and investment banks.

One more piece of housekeeping is worth knowing about, because it creates a standing maintenance job. Amendments issued on 21 August 2025 completed catch-up work for standards and amendments issued between February 2021 and May 2024, including IFRS 18, supplier finance arrangements, the Pillar Two model rules amendments, lack of exchangeability, and the classification and measurement of financial instruments. From here the IASB has said IFRS 19 will be amended at the same time as it issues or revises other standards. The reduced disclosure list is a living document, and whatever holds it in your architecture should carry a version.

The population is large, and most of it is somewhere else.

The UK Endorsement Board did the arithmetic as part of its adoption work. Its current estimate puts the number of subsidiaries owned by entities listed on the London Stock Exchange, as of January 2025, that would be eligible to apply IFRS 19 at approximately 78,000. Around 21,000 of those are domiciled in the UK. Around 57,000 are domiciled abroad. Separately, the UKEB estimates that about 14,000 unlisted UK-registered companies already take up the option to use UK-adopted international accounting standards.

Those figures come with caveats the assessment states itself, and they are worth carrying. The count is built from Reuters data with sectors likely to have public accountability stripped out, and the underlying classification treats a subsidiary as ownership of more than half the voting stock rather than applying the control definition in IFRS 10. The UKEB also says plainly that it could not estimate the number of eligible subsidiaries owned by private or foreign-domiciled groups because the data was not available. So this is an order of magnitude rather than a register.

Even as an order of magnitude, the split is the useful part. Roughly three quarters of the eligible population sits outside the jurisdiction doing the adopting. That is what makes this a group reporting problem rather than a local statutory one. The entity that saves time is in one country, the decision is made in another, and the benefit only shows up in the group numbers when enough entities move.

The UKEB is direct about that last point. It found that for groups to realise significant benefit from the alignment IFRS 19 offers, they need a critical mass of eligible subsidiaries using it, which depends on global adoption of the standard and on local law in the jurisdictions where the subsidiaries operate. It notes that in some jurisdictions unlisted entities are required to prepare financial statements under local GAAP, for example for tax purposes. Availability is a per-country fact, and a business case built on entity counts alone will be wrong in a predictable direction.

The line that has to hold: two scopes, one entity.

Here is the design decision that determines whether this goes well. A subsidiary in an IFRS group feeds two different obligations. It publishes its own financial statements, and it supplies data into a consolidation that produces the parent’s full IFRS financial statements. IFRS 19 applies to the first of those and has nothing to say about the second.

The failure mode writes itself. A group elects for forty entities, someone reasonably concludes that those entities no longer need to report fair value hierarchy detail or maturity analyses or related party breakdowns, and the collection template gets shortened to match. The local close gets faster. Twelve months later the group auditor asks for the disaggregation behind a consolidated note and it is not there, because the only place it was ever captured was the template that got shortened.

The fix is a modelling choice rather than a control. Hold the group collection scope as a property of the consolidation, and hold the publication scope as a property of the entity. The election then sets the second and cannot reach the first. If your reporting architecture currently has one field that does both jobs, splitting it is the highest value hour of work in this whole exercise, and it is worth doing whether or not you ever elect.

It helps to know what the shorter list is actually built around. The Basis for Conclusions on IFRS 19 records at paragraph BC33 that in assessing the needs of users of eligible subsidiaries’ financial statements, the principles focused on information about short-term cash flows, liquidity, measurement uncertainties, disaggregation of amounts in the financial statements, and accounting policy choices. That is a coherent set, and it explains a lot of the specific outcomes. It is why the UKEB found that applying those principles produced relatively few reductions to the disclosures required by IFRS 7, and it is why a statement of cash flows survives.

The user picture behind those principles is worth knowing too, because it changes which entities deserve a conversation. The UKEB found that financial statements of subsidiaries without public accountability typically have few users, that the main users are internal such as parent entities, and that the main external users are providers of credit such as bank lending departments, along with non-controlling shareholders and some suppliers. Internal users can ask management directly. Lenders are described as particularly interested in a subsidiary’s statements when external borrowings are not supported by parent or intragroup guarantees.

For UK groups, two data grains get exposed on the way in.

UK groups have had a reduced disclosure framework since 2012. FRS 101, maintained by the Financial Reporting Council, lets a qualifying entity apply adopted IFRS with a set of disclosure exemptions. IFRS 19 and FRS 101 have similar objectives and different scopes, and the UKEB published a comparison specifically so that stakeholders could see how the two fit together. Three of the differences it names have direct systems consequences.

The related party one is the sharp edge. A UK group with a wholly owned subsidiary on FRS 101 today can be exempt from disclosing that subsidiary’s transactions with other members of the group. IFRS 19 requires most of IAS 24. For a group with heavy intercompany trading, electing means producing intercompany balances and transactions by counterparty and by category at entity level, in a form that can be published and audited.

Plenty of consolidation systems cannot do that comfortably, because intercompany has historically been carried at whatever grain the elimination needed and no finer. The encouraging part is that the finer grain is useful well beyond this standard. The same data makes eliminations explainable rather than merely balanced, gives transfer pricing documentation a source, and answers the intragroup questions that come up in any group audit. It is work that gets used more than once.

The cash flow difference is smaller but more likely to surprise a project plan. IFRS 19 requires a statement of cash flows and FRS 101 does not. If a group derives cash flow once a year at consolidated level from a movement analysis, the inputs to produce one for a single legal entity may simply not exist in reusable form. That is a build, and the right time to find out is now.

The artefact: an eligibility and election record on every entity.

Everything above resolves into one artefact. Each legal entity needs a dated record of whether it is eligible, what evidence supports each of the three conditions, whether the standard is available in its jurisdiction, the facts that inform the decision, and the election itself. The shape below is a worked example of what that record holds. It is not an extract from any customer system.

{
  "entity": {
    "code": "NL-0420",
    "legal_name": "Placeholder Netherlands B.V.",
    "jurisdiction": "NL",
    "functional_currency": "EUR",
    "consolidation_method": "full",
    "parent_entity": "NL-0400",
    "ultimate_parent": "GB-0001"
  },
  "ifrs19_eligibility": {
    "assessed_at": "2026-12-31",
    "is_subsidiary": true,
    "public_accountability": {
      "traded_instruments": false,
      "issuing_into_public_market": false,
      "fiduciary_assets_as_primary_business": false,
      "evidence": "treasury debt register extract, 2026-12-31"
    },
    "qualifying_parent": {
      "entity": "GB-0001",
      "publishes_public_ifrs_consolidated": true,
      "evidence": "GB-0001 annual report 2026, filed 2027-03-14"
    },
    "eligible": true
  },
  "local_framework": {
    "statutory_framework_permitted": ["IFRS", "NL GAAP"],
    "local_gaap_required_for_tax": false,
    "blocking_local_requirement": null
  },
  "decision_inputs": {
    "external_borrowings_without_group_guarantee": false,
    "non_controlling_interest_present": false,
    "lender_disclosure_covenants": [],
    "prior_framework": "NL GAAP"
  },
  "election": {
    "status": "elected",
    "first_period": "2027-01-01",
    "approved_by": "group controller",
    "approved_on": "2026-11-18",
    "reassess_at_each_period_end": true
  }
}

Four things in that structure are doing real work. The assessment carries a date, because the conditions are tested at each period end. Each condition carries its evidence, because two of the three are facts about entities other than this one. Jurisdictional availability sits beside the entity rather than in a global assumption. And the decision inputs are held separately from the eligibility tests, because being eligible and it being sensible are different questions.

That last separation is the one people skip. External borrowings without a group guarantee, the presence of non-controlling shareholders, and any disclosure commitments made to a lender do not affect whether an entity qualifies. They affect whether a shorter note set is the right answer for that entity, and they belong in the record so the decision can be explained later by somebody who was not in the room.

On non-controlling interests, the UKEB’s own data is a reasonable calibration. From the 2023 consolidated financial statements of UK listed entities, it put the total book value of non-controlling interests at around forty billion pounds, representing roughly 2.5% of aggregate net assets, with about 26% of UK listed entities reporting non-controlling interests in equity. Fewer than ten entities accounted for approximately 80% of that book value, concentrated in energy and basic materials. For most groups this is a short list of specific entities rather than a general constraint, which is exactly the kind of thing a register is good at showing.

An implementation checklist for the next two quarters.

The effective date is 1 January 2027 and the standard is voluntary, so nothing forces a timetable. What does create urgency is that the useful version of this needs data work, and the data work is easier to schedule before a close than during one.

• Build the eligibility record before you build the decision. Three tests, each with a source and a date, held against the legal entity rather than in the memo that supported this year’s conclusion. Two of the three depend on facts outside the entity, which is exactly why they need evidencing rather than assuming.
• Date the assessment and repeat it. The conditions are tested at the end of the reporting period, so eligibility is a state on a date rather than a permanent status. A group that files an intermediate holding company’s first public bond has changed that entity’s answer, and nothing in the subsidiary ledger will tell you.
• Keep the group collection scope and the entity publication scope in separate fields. This is the single design decision that determines whether IFRS 19 is a simplification or a data loss. The consolidation pack still needs everything it needed before, because the parent still prepares full IFRS consolidated statements.
• Check what each jurisdiction actually permits before counting any saving. The UKEB assessment is explicit that benefits depend on local law in the jurisdictions where subsidiaries operate, and notes that some jurisdictions require local GAAP financial statements for tax purposes. Availability is a per-country fact and belongs beside the entity, not in a global assumption.
• Look at the intercompany grain now rather than in the transition. If your group currently relies on the FRS 101 exemption for wholly owned intragroup related party transactions, IFRS 19 does not carry that exemption forward. Being able to produce intercompany balances and transactions by entity, by counterparty and by category is the work, and it is worth doing whether or not you elect.
• Find out whether you can produce a statement of cash flows per legal entity. IFRS 19 requires one and FRS 101 did not. If the honest answer is that cash flow is assembled once a year at group level, that is a build, and it is better discovered in a planning meeting than in an audit.
• Sequence the entities instead of switching the group. The UKEB found that a phased approach spreads cost across periods and can reduce it overall through learning effects from the earliest transitions. Pick entities where the prior framework is furthest from IFRS and the local law is clearest, and let the second wave benefit from the first.
• Count the entities where a second set of books actually exists today. The saving the standard offers is the removal of dual accounting records for subsidiaries that keep one set for local statutory purposes and another for group reporting. A subsidiary already reporting under full IFRS gains a shorter note set and little else.
• Ask treasury which entities borrow externally without a group guarantee. The UKEB outreach found that lenders are the main external users of subsidiary financial statements, and that they pay closest attention when borrowings are not supported by parent or intragroup guarantees. That is a short list, and it is the list where a shorter note set needs a conversation first.
• Put the reduced disclosure set under change control. The IASB has said IFRS 19 will now be amended at the same time it issues or revises other standards, so the list of what an electing entity discloses moves with the standards themselves. That is an ongoing maintenance item at both entity and group level, which the UKEB assessment records as an expected cost.

On sequencing, the UKEB assessment is encouraging and specific. It found that groups may implement a phased approach to transitioning subsidiaries, that this spreads cost over several periods, and that it can reduce cost overall through learning effects from early implementation experience. It also identified accounting system changes as a one-off cost at both subsidiary and group level, which is a standard setter saying in its own words that this lands in the systems rather than only in the notes.

Failure modes, and what each one looks like from inside.

• Reading a disclosure standard as a data reduction. IFRS 19 shortens what an entity publishes. The parent still prepares full IFRS consolidated financial statements, so the group still needs the underlying data at the same grain. Switching off a collection because an entity elected is the one mistake that turns a saving into a restatement.
• Treating eligibility as a status rather than a dated test. All three conditions are assessed at the end of the reporting period. An entity that qualified last year can fail this year because a parent changed, a bond was issued, or the group reorganised, and none of those events originate in that entity’s own ledger.
• Assuming the parent condition holds. The third test is about the ultimate or intermediate parent producing consolidated financial statements available for public use that comply with IFRS Accounting Standards. In a group with intermediate holding companies in several jurisdictions, which parent satisfies that condition is a real question with a real answer, and it should be recorded.
• Modelling the saving before checking availability. IFRS 19 has to be available for use in the relevant jurisdiction. The UKEB assessment notes that in some jurisdictions unlisted entities are required to prepare financial statements under local GAAP, for example for tax purposes. A business case built on entity counts rather than on jurisdiction rules will overstate the benefit.
• Losing the FRS 101 intragroup related party exemption quietly. A wholly owned UK subsidiary using FRS 101 today can be exempt from disclosing transactions with other group members. IFRS 19 requires most of IAS 24. For a group with heavy intercompany trading, this is more disclosure at entity level rather than less, and it is easy to miss because the headline is a reduction.
• Expecting audit cost to fall everywhere. The UKEB notes that a subsidiary moving to IFRS 19 may see audit costs rise where the transition results in a greater amount of information subject to audit. The clearer group-level benefit it identifies is a reduction in reconciling items between subsidiary local GAAP records and group IFRS reporting.
• Electing one entity and calling it a programme. The same assessment found that realising significant benefit depends on reaching a critical mass of eligible subsidiaries using the standard. A single election proves the mechanics work. The alignment benefit arrives when a shared service centre stops maintaining several local frameworks.
• Ignoring non-controlling shareholders. Where an entity has minority holders, its own financial statements may be the only account they receive, and they cannot ask management for more the way a parent can. That is a reason to think about the specific entity rather than a reason not to elect, and it is worth naming in the decision record.

Data and interface considerations.

• The legal entity master is the right home for this, and it probably needs new fields. Consolidation method and ownership percentage are usually there. A dated eligibility assessment, the evidence behind each of the three tests, the jurisdictional availability of IFRS 19, and the election itself usually are not.
• Intercompany data needs to be queryable by entity, counterparty, and transaction category, not only as an elimination total. This is the grain IAS 24 disclosure needs at entity level, and it is the same grain that makes eliminations explainable and transfer pricing documentation easier to assemble.
• Entity-level cash flow requires movement data that survives the consolidation. If your cash flow statement is derived once at group level from opening and closing balance sheets, the inputs for a single entity may not exist in a reusable form, and building them is a genuine project rather than a report change.
• The disclosure requirements in IFRS 19 are organised under the heading of each IFRS Accounting Standard, so the reduced set maps standard by standard. That structure is directly usable: a per-entity disclosure scope matrix keyed by standard is a faithful model of the requirement rather than an approximation of it.
• Interfaces that pull subsidiary data into the group pack should carry the entity’s election as an attribute of the entity, not as a filter on the feed. The election is metadata about publication. The moment it starts controlling what gets transmitted, the consolidation has been made dependent on a statutory reporting choice.
• The reduced disclosure list is versioned by the IASB from here on, since IFRS 19 will be amended alongside other standards. Whatever holds your per-entity disclosure scope should carry a version, so the set applied in a given period can be reproduced later.

The group-level prize the UKEB describes is worth stating plainly, because it is what the data work buys. Preparers told the board that IFRS 19 would remove the need to maintain multiple accounting records, that they expect the consolidation process to be streamlined and subject to a lower risk of errors through alignment across the group, and that the need for reconciliation would be eliminated. Groups running shared service centres expect the largest gains, because the standard reduces the number of local frameworks in use and the reliance on local GAAP expertise, at a scale where process efficiency compounds.

Audit evidence worth capturing from the first election.

• The eligibility assessment for each electing entity, dated at the period end, with the source behind each of the three conditions. The parent condition in particular is satisfied by a document the subsidiary does not produce, so the reference to the parent’s published consolidated statements belongs in the file.
• The treasury confirmation that the entity has no traded debt or equity and is not in the process of issuing into a public market. This is the limb of public accountability most likely to change mid-year and least likely to be visible from the entity’s own trial balance.
• The jurisdictional availability determination, with the local requirement it was checked against. Where local law requires statutory accounts under local GAAP, the record should say so and name the requirement.
• The election approval itself, with who approved it, when, and for which first period. An accounting policy election that appears in the financial statements without an approval trail is the version an auditor will raise first.
• The additional disclosures assessment. IFRS 19 requires an entity to provide more than the reduced set if users would not otherwise understand its financial position, performance and cash flows, so the conclusion that the reduced set was sufficient is itself a judgement that should be written down.
• The mapping from the group collection scope to each entity’s publication scope, held per period. This is the artefact that demonstrates the consolidation still receives everything it needs, which is the control question a group auditor will actually ask.