Every sale inside the group needs to know which boundary it crossed.

An implementation checklist.

1. 1.Write down where the boundary of your reporting entity runs, counterparty by counterparty. A subsidiary sits inside it, so a gain on a sale to one is eliminated in full under IFRS 10. An associate sits outside it, which is why its treatment is a separate question at all. Hold the relationship, the basis for it, and the ownership percentage as data on the counterparty rather than as knowledge in the consolidation team.
2. 2.Give every counterparty relationship an effective date. Groups reorganise. An entity that was a subsidiary in March can be an associate by October, and the treatment of a transaction depends on what the relationship was on the day it happened, not on what it is when the books close. Without effective dates, restatements become archaeology.
3. 3.Record the direction of every internal transaction. Downstream means a sale or contribution from the investor to the associate; upstream means a sale from the associate to the investor. The proposed disclosures split on exactly this line, since a full-recognition investor discloses downstream gains while a restricted-recognition investor discloses both, so direction is a reporting attribute rather than a piece of trivia.
4. 4.Record what actually moved, and be precise about a business. Gains on the transfer of a business are to be recognised in full whatever policy a company chooses, and an investor choosing restricted recognition would restrict the gain on losing control of a subsidiary that is not a business. Whether the thing transferred met the definition of a business is therefore a field with consequences, not a description.
5. 5.Keep a running balance for anything held back, and name what releases it. A restricted gain on inventory is released when the associate sells that inventory to a third party. A restricted gain on equipment unwinds over its useful life. The Board itself listed this tracking as one of the real costs of restricted recognition, so if you choose it, build the subledger rather than the spreadsheet.
6. 6.Decide the policy consciously, and record it twice. The choice between full and restricted recognition can differ between consolidated and separate financial statements, and the policy itself is disclosed. A group that never chooses is effectively choosing the habit its software already encodes, which is a poor answer to give when asked what its policy is.
7. 7.Flag sidestream trade rather than assuming a treatment. The IASB decided not to add requirements for transactions between two associates of the same investor. That makes it a matter of judgement, and judgement applied consistently needs the population identified first. A flag costs little now and saves an argument later.
8. 8.Run one exception query before each close. Transactions with no relationship recorded, relationships with no effective date, restricted gains with no release event, businesses recorded as restricted, gains that cannot be attributed to an individual associate, unflagged sidestream trade, and balances that do not roll forward are the gaps. While that list has entries, the group numbers rest on assumptions rather than records.

Failure modes, framed so you can plan around them.

• Treating elimination as a property of the software rather than a decision the group makes. Most consolidation tools ship with a default: eliminate against subsidiaries in full, pro-rate against associates. It works quietly for years, which is exactly the problem, because when the standard turns that behaviour into a disclosed accounting policy, nobody can point to where it was chosen or by whom. The remedy is small and worth doing now: write the policy down, state it for the consolidated and the separate statements, and check that the system actually implements what the note would claim.
• Carrying the group structure without effective dates. A counterparty table that records what each entity is today, with no history, cannot answer what it was when a transaction happened. That is survivable until a group reorganises, an entity moves from subsidiary to associate, or a retrospective transition asks for prior periods. Effective dating a relationship costs one column and removes a whole class of reconstruction work.
• Letting direction go unrecorded because it seems obvious. Upstream and downstream feel self-evident when you are looking at a single transaction, and become guesswork across thousands. Since the proposed disclosures ask a restricted-recognition investor for gains in both directions and a full-recognition investor for downstream only, direction determines what gets reported, and inferring it later from account codes tends to produce a number that cannot be tied out.
• Blurring the line between a business and an asset. It is tempting to treat any transfer of a group of assets as a transfer of a business, or to avoid the question entirely. The decisions taken so far make that distinction do real work: a business is recognised in full regardless of policy, and the restricted route applies to losing control of a subsidiary that is not a business. Left unrecorded, the same fact pattern gets two answers in two periods.
• Holding restricted gains in a spreadsheet. A restricted gain is not a period entry, it is a balance that waits for an event, sometimes for years, sometimes unwinding over an asset’s useful life. Spreadsheets lose the release trigger, survive staff changes badly, and cannot produce the opening-to-closing reconciliation the Board intends to require. A subledger with a release condition on each balance is the honest form of this data.
• Assuming upstream information will be available when needed. The Basis for Conclusions notes that difficulties sometimes arise in accessing the information needed for elimination entries on upstream transactions, which is a polite way of saying the associate does not report to you. If you choose restricted recognition, the data-sharing arrangement with the associate is part of the accounting policy, and it is far easier to agree while relations are good than during a close.
• Treating the September 2024 proposal as the current state of the project. Full recognition for everything was the proposal. It is not where redeliberation landed. A team that reads the exposure draft and stops there will prepare for a change that is no longer coming and miss the one that is, which is a policy choice plus disclosure plus retrospective transition on the unrecognised portion of previously restricted gains.
• Waiting for the final amendments before improving the data. The counterparty relationships, the effective dates, the direction flags, the business test and the restricted-gain balances are all useful today. They make the current close faster, they make the current disclosures defensible, and they are the same fields the amendments will need. Building them on the effective date turns a steady task into a scramble, and leaves this year’s statements no better than last year’s.

What this asks of the data model.

• The counterparty carries the boundary. Each entity the group trades with records its relationship, the basis for it, the ownership percentage and the interests of unrelated investors, so the question of whether a gain is internal to the reporting entity is answered by a field rather than by a memory.
• Relationships are effective dated. A relationship is a fact about a period, not about today, so it is stored with the date it began and the relationship it replaced, which is what makes the treatment of a past transaction reproducible and a retrospective transition possible.
• Direction is a first-class attribute. Every internal transaction records whether it is downstream, upstream or sidestream, because the proposed disclosures split on that line and because sidestream trade is deliberately left to judgement and so has to be found before it can be handled consistently.
• What moved is recorded, including whether it was a business. Inventory, property, plant and equipment, a subsidiary, or a business are different facts with different outcomes, and the business test is captured at the time of the transaction while the evidence is at hand.
• A restricted gain is a balance, not an entry. Anything held back carries its own running balance with the condition that releases it, whether that is the associate’s onward sale to a third party or the passage of an asset’s useful life, so the reconciliation from opening to closing balance is a report rather than a reconstruction.
• The policy is stored beside the numbers, and stored twice. The choice between full and restricted recognition is recorded for the consolidated statements and, separately, for the separate statements, so the same transaction can be treated correctly in both without one overwriting the other.
• Attribution to an individual associate is preserved. The proposed exemption from disclosure turns partly on whether the information can be attributed to an individual associate, so aggregation happens in the report rather than in the underlying record.
• Completeness reduces to one exception query. Missing relationships, undated changes, orphaned restricted balances, misrecorded businesses, unattributable gains and unflagged sidestream trade are the exception list, run before a period is relied on rather than discovered when the group numbers are questioned.

The evidence to keep.

• The counterparty register, showing each entity the group trades with, its relationship, the basis for that relationship, the ownership percentage, and the date the relationship took effect, so the boundary of the reporting entity is evidenced rather than asserted.
• The intercompany transaction population, showing for each internal sale the counterparty, the relationship at the transaction date, the direction of travel, what was transferred, and the gain or loss, which is the population any test of eliminations has to start from.
• The business determinations, showing for each transfer of a subsidiary or a group of assets whether it met the definition of a business and on what basis, since that decides whether the gain is recognised in full regardless of the policy chosen.
• The restricted gains subledger, showing each balance held back, the transaction it came from, the condition that releases it, and the movement from opening to closing balance, which is what the proposed reconciliation disclosure would ask for.
• The recorded accounting policy, stated for the consolidated financial statements and for the separate financial statements, together with evidence that the consolidation system implements the policy as stated.
• The disclosure working, showing gains and losses by direction, attributable to individual associates, and reconciling to the transaction population rather than assembled separately.
• The exception query output, ideally empty, listing transactions with no relationship, relationships with no effective date, restricted gains with no release condition, businesses recorded as restricted, unattributable gains, unflagged sidestream trade and balances that do not roll forward.

Questions worth asking in your own review.

• Can we list, today, every transaction the group had with each of its associates in the period, with the direction of travel and what was transferred?
• Does our counterparty table record when each relationship began, and what it was before, or only what each entity is right now?
• Where is our elimination policy written down, and does it match what the consolidation system actually does when it runs?
• For every gain we are currently holding back on a transaction with an associate, do we know the balance and the specific event that will release it?
• When a subsidiary or a group of assets was transferred, did we record whether it met the definition of a business, and can we show the basis?
• If we choose restricted recognition, do we have a reliable way to get the information we need from the associate for upstream transactions?
• Would a retrospective change of policy be a query we can run over history, or a reconstruction from old journals and correspondence?
• Could we produce the reconciliation of restricted gains from opening to closing balance without building it by hand?

What this adds up to.

The equity method project started as a tidy-up of a standard first issued in 1989 and turned into a useful argument about where a reporting entity ends. The answer the Board has reached is pragmatic. Groups get a choice between recognising gains on transactions with associates in full and restricting them, transfers of a business are recognised in full either way, IFRS 10 is aligned to follow the choice, and the choice itself becomes something a company states and supports with numbers.

For a finance systems owner that is good news, because a choice is easier to implement than a rule you disagree with, and because the data it needs is data worth having regardless. A counterparty register that knows what each entity is and when it became that. Internal transactions that know their direction and what moved. A subledger for gains held back, each with the event that releases it. None of that is exotic, and all of it makes the current close faster while making the next set of amendments a configuration change rather than a scramble.

If there is one place to start before the amendments are issued, it is the restricted balances you are already carrying. Pull them into one list, give each the transaction it came from and the event it is waiting on, and check that the total rolls forward from the opening balance to the closing one. Transition will ask for the unrecognised portion of those balances, retrospectively, without an impracticability exemption to fall back on. For a group that has kept the record, that is a query. For a group that has kept a habit, it is the work, and it is a great deal cheaper to do now than under a deadline.

Sources.

• IFRS Foundation, Exposure Draft ED/2024/7, Equity Method of Accounting: IAS 28 Investments in Associates and Joint Ventures (revised 202x), published 19 September 2024, comment period closed 20 January 2025. Downloaded and read directly, page by page, rather than through a summary. Source for Question 4 on transactions with associates, which states that paragraph 28 of IAS 28 requires an investor to recognise gains and losses resulting from transactions between itself and an associate only to the extent of unrelated investors’ interests in the associate, and that this applies to both downstream transactions, such as a sale or contribution of assets from an investor to an associate, and upstream transactions, such as a sale of assets from an associate to an investor; for the statement that where an investor loses control of a subsidiary in a transaction with an associate, the IAS 28 requirement to recognise only a portion of the gain or loss is inconsistent with the IFRS 10 requirement to recognise the gain or loss in full on losing control of a subsidiary; for the proposal itself, set out in draft paragraph 53, that an investor or joint venturer shall recognise in full the gains and losses resulting from all upstream and downstream transactions with its associates or joint ventures; for the footnote recording that the IASB amended the paragraph 28 requirement when it issued Sale or Contribution of Assets between an Investor and its Associate or Joint Venture (Amendments to IFRS 10 and IAS 28) in 2014 but deferred the effective date of those amendments indefinitely; and for the proposed IFRS 12 and IAS 27 disclosures on gains or losses from downstream transactions.
• IFRS Foundation, Basis for Conclusions on Exposure Draft ED/2024/7, Equity Method of Accounting, September 2024. Read directly rather than through a summary. Source for the reasoning at paragraphs BC76 to BC80 on the boundary of the reporting entity: that in a group a parent controls its subsidiaries and so cannot recognise gains or losses on transactions with them, because consolidated financial statements report the parent and its subsidiaries as a single economic entity and subsidiaries sit within the boundary of the reporting entity; that the IAS 28 requirement to eliminate the investor’s portion could be viewed as implying the boundary is extended to include the associate or the investor’s share of it; that in the Conceptual Framework and other IFRS Accounting Standards an associate is not within the definition of a group; and that the IASB observed it is unclear why IAS 28 requires the investor’s share of such a gain or loss to be eliminated. Also the source for paragraph BC75 on costs, which records that restricted recognition requires an entity to gather the information needed for elimination entries, with difficulties sometimes arising in accessing information for upstream transactions, to exercise judgement when allocating a restricted gain or loss on a transfer of a business, and to track the restricted gain or loss in future periods to determine when it is recognised, for example on the sale of inventory to a third party or over the useful life of an item of property, plant and equipment.
• IFRS Foundation, IASB Update May 2026. Source for the pivotal redeliberation decision taken at the meeting of 20 May 2026: to introduce an accounting policy choice permitting an investor to choose either full or restricted recognition of gains or losses on all transactions with associates, except gains or losses on the transfer of businesses, which would be recognised in full; to confirm the exposure draft proposal to withdraw the 2014 amendments on sale or contribution of assets between an investor and its associate or joint venture; and to amend IFRS 10 to require an investor that chooses to restrict gains and losses on transactions with associates also to restrict gains and losses on the loss of control of a subsidiary that is not a business. Twelve of thirteen IASB members agreed. The same meeting retained within the scope of the project the application question on the inconsistency between IAS 28 and IFRS 10.
• IFRS Foundation, IASB Update June 2026. Source for the decisions taken at the meeting of 24 June 2026 on separate financial statements: that an investor applying the equity method to associates or joint ventures in its separate financial statements may choose either to restrict recognition of gains or losses, except on transfers of businesses which are recognised in full, or to recognise gains and losses in full on all transactions with associates, and that the investor need not apply the same accounting policy in its consolidated and separate financial statements; and that a parent applying the equity method to subsidiaries in its separate financial statements may likewise choose restricted or full recognition on transactions with those subsidiaries.
• IFRS Foundation, IASB Update July 2026. Source for the decisions taken at the meeting of 22 July 2026 on disclosure, transition, first-time adopters and sweep issues: that an entity would disclose its accounting policy choice for the recognition of gains or losses from transactions with associates; that an investor choosing full recognition would disclose gains or losses from downstream transactions while an investor choosing restricted recognition would disclose gains or losses from both downstream and upstream transactions; that investors would disclose the nature of transactions with associates and whether those transactions are included in the disclosure; that an exemption from disclosing those gains and losses applies only where the information can be attributed to an individual associate and the transactions are part of the investor’s ordinary activities; that the reconciliation between the opening and closing balance of restricted gains and losses is retained; that a change in the accounting policy for recognising gains or losses from transactions with associates is applied retrospectively, subject to relief where retrospective application would involve undue cost or effort, applying only to the unrecognised portion of a previously restricted gain or loss at the transition date, and not subject to the impracticability exemption in IAS 8, with all other requirements applied prospectively from the effective date; and that the IASB decided not to add requirements on sidestream transactions.
• IFRS Foundation, Equity Method project page, IFRS Foundation work plan. Source for the project status as at the time of writing: that the comment period on the exposure draft closed on 20 January 2025, that the IASB discussed a feedback summary at its May 2025 meeting without being asked to make decisions, that redeliberations continued through 2026 with the July 2026 meeting covering transition and sweep issues, and that the next milestone recorded on the project is the final amendments, with the next meeting listed as September 2026. Also the source for the note that IAS 28 was first issued in 1989 and that the IASB has taken the opportunity to reorder the standard in a more logical and consistent way.
• IFRS Foundation, Exposure Draft and comment letters, Equity Method of Accounting. Source for the publication date of 19 September 2024, for the scope of the exposure draft covering both proposed amendments to IAS 28 and complementary disclosure proposals in IFRS 12 Disclosure of Interests in Other Entities and IAS 27 Separate Financial Statements, and for the IASB’s stated expectation that the proposed amendments will reduce diversity in practice and give users of financial statements more comparable and useful information.
• IFRS Foundation, IAS 28 Investments in Associates and Joint Ventures. The standard as currently in effect, which is the baseline every group applies until the amendments are issued, and the source of the paragraph 28 elimination requirement the project is revisiting.

The paragraph 28 requirement, the upstream and downstream definitions, the inconsistency with IFRS 10, the proposal in draft paragraph 53, the indefinitely deferred 2014 amendments, the boundary of the reporting entity reasoning and the cost analysis were read directly from the exposure draft and its Basis for Conclusions, which were downloaded and read page by page rather than through a summary. The redeliberation decisions of 20 May, 24 June and 22 July 2026, and the project status showing the final amendments as the next milestone, are from the IASB Update records and the project page. Every decision taken after the exposure draft is tentative: the amendments have not been issued, and an effective date will follow when they are. No embedded posts from X appear here, because no public post on this topic could be verified as current, relevant, and authentic at the time of writing, and an unverified embed is worse than none. Nothing here is accounting, tax, or legal advice for a specific company, and the names, percentages and amounts in the worked record are placeholders for shape rather than real values.