Multi-Entity Accounting: Consolidation, FX and a Worked Elimination

Keep entity books intact before producing a group view#

Multi-entity accounting keeps records for separate legal entities and then produces a controlled group view. Each company still has its own transactions, obligations and reporting needs. Consolidation combines entities within the reporting perimeter and removes internal activity so the group does not report a sale to itself as external revenue.

For a payment platform, start by identifying which company contracts with the customer, owes the seller or contractor, holds each bank or provider account, and pays each supplier. A location or department tag within one company is useful segmentation; it does not create another legal entity. Conversely, routing a payment through a group account does not automatically make the account holder the owner of the underlying revenue.

This guide uses IFRS consolidation principles and the ordinary, non-hyperinflationary foreign-currency treatment described by IAS 21. The numerical example is illustrative. A group reporting under US GAAP or another framework must apply its own consolidation and currency policies rather than importing the example as a universal posting rule.

Define which companies belong in the consolidation#

IFRS 10 bases consolidation on control: power over the investee, exposure or rights to variable returns, and the ability to use that power to affect those returns. Common branding, a shared payment provider or a minority investment alone does not establish that every company should be consolidated line by line.

Record the parent, subsidiaries, ownership percentages, acquisition or disposal dates and the control assessment. Account for non-controlling interests where relevant. IFRS 10 includes a qualifying intermediate-parent exemption and investment-entity exceptions; determine whether an exception applies before treating every parent as subject to the same presentation requirement. Associates and joint arrangements require their relevant accounting treatment, rather than automatic inclusion as subsidiaries.

Group finance should approve the perimeter and changes to it. A company may need local statutory books even when it is consolidated. The consolidation process should preserve those books and show group adjustments separately, including policy alignment, acquisition accounting and eliminations.

Build an entity-to-group mapping that can be reviewed#

Entities can use a shared chart of accounts or local charts mapped into the group structure. A common chart reduces translation between account labels; local charts can serve local reporting requirements. In either case, account mapping does not fix a different recognition policy. IFRS 10 requires uniform group accounting policies for like transactions in similar circumstances, with adjustments when necessary.

Approve mappings for new accounts before close, and report posted balances with no group destination. Retain the effective date and version of each mapping. If one local balance contains different group treatments, split it using documented dimensions or adjustment logic. Do not force an ambiguous balance into one category merely to make the rollup complete.

ERP restrictions are product-specific. Confirm whether your selected system permits changing a chart after posting, how it stores consolidation mappings and whether its consolidation company accepts daily entries. Those implementation limits should shape the configuration; they are not general accounting rules for every ERP.

Separate entity currency measurement from group translation#

IAS 21’s overview distinguishes foreign-currency transactions from translating financial statements into another presentation currency. Its Australian equivalent, AASB 121 for 2025–2026 periods, gives the detailed requirements in paragraphs 21–32 and 38–45.

A period average can approximate transaction-date rates for income and expenses when appropriate, but is unsuitable when rates fluctuate significantly. Preserve the rate source, date, direction and precision. Consistent sources and policies improve reconciliation; they do not make legitimate exchange differences disappear.

Keep exceptions explicit. A qualifying monetary item forming part of a net investment in a foreign operation can have different exchange-difference treatment in individual and consolidated statements. Hedge accounting can also change presentation. Hyperinflation and lack of exchangeability require their applicable rules. Do not label every intercompany payable a net-investment item to move an ordinary exchange loss out of profit or loss.

Work through an intercompany service invoice and its FX difference#

Assume parent P has USD functional currency, subsidiary S has EUR functional currency, and the group presents in USD. P provides a service that S expenses immediately and invoices EUR 1,000. The transaction-date rate is USD 1.10 per EUR; the closing rate is USD 1.20. The invoice is unpaid at close. This is an ordinary short-term monetary balance, with no hedge or net-investment designation. Ignore taxes and all other balances to isolate the entries.

The $100 FX gain in profit or loss and the $100 translation loss in other comprehensive income remain in this simplified group example. They are different accounting effects, even though the intercompany receivable and payable have been eliminated. Paragraph 45 of IAS 21/AASB 121 explains why eliminating an intragroup monetary balance cannot erase the effects of currency fluctuations; the net-investment exception has its own treatment.

Changing S’s expense translation to $1,200 just to match the payable would distort the service elimination. Posting a $100 balancing adjustment without explaining its classification would also hide the issue. Reconcile the EUR 1,000 obligation first, then reconcile the measurement and translation stages. When the invoice is subsequently paid, record settlement and any further exchange difference using the actual applicable rate.

This example covers an expensed service, not inventory or an acquired subsidiary. Intercompany profit embedded in inventory or fixed assets requires additional elimination, and related tax effects may arise. Investment-versus-equity elimination, acquisition adjustments and non-controlling interests also belong in a full consolidation. A two-line receivable/payable elimination is not a complete group close.

Reconcile each intercompany pair before elimination#

Match entity, counterparty, invoice or loan reference, transaction currency, original amount, outstanding amount and cutoff. A group-wide net balance of zero can hide two unrelated errors. Keep receivables and payables paired at transaction level, including credit notes and partial settlements.

Classify each break before changing a journal: missing counterparty entry, different recognition dates, partial payment, wrong entity, wrong transaction amount, or an explained FX measurement difference. Correct an entity error in the relevant entity books or use an approved group adjustment where appropriate. Preserve the original reference, correction and reviewer decision. Legitimate FX presentation requires explanation, not an arbitrary write-off.

Use the same reporting date for consolidation, subject to the framework’s permitted exceptions. IFRS 10 generally requires aligned reporting dates and explains the limited impracticability exception, including adjustments for significant intervening events. An ERP can combine different periods technically while still producing an unsuitable statutory consolidation.

Connect payment operations without substituting them for accounting#

Keep customer collections, provider fees, seller liabilities, transfers between group entities and bank payouts identifiable. A successful payout proves a payment outcome; it does not prove the correct revenue recognition, entity attribution or elimination. Reconcile provider balances and bank activity to each entity’s ledger before rolling those balances into the group.

For a repeated provider event, apply a durable duplicate check together with its accounting effect. For an outgoing payment whose outcome is unknown, resolve the original attempt before sending a replacement from another entity or provider. A retry or rerouting decision can change which company supplied cash, but it must not silently change which company owes the counterparty.

If P pays a supplier expense belonging to S, document the expense owner and the resulting intercompany amount rather than recording the same supplier expense in both companies. The exact tax, transfer-pricing and legal treatment needs its own policy. Group consolidation removes internal balances; it does not remove the need to document a cross-company arrangement.

Run a reproducible close with separate approvals#

1. Close each entity’s source books: complete bank/provider reconciliation, accruals, cutoff and required currency measurement.
2. Review intercompany pairs, correct errors and approve explained differences and open items according to materiality policy.
3. Apply approved account mappings and group-policy adjustments to versioned entity trial balances.
4. Translate foreign-operation balances and results into the group presentation currency using documented rate rules.
5. Post and review eliminations, acquisition adjustments, non-controlling interests and other applicable consolidation entries.
6. Tie the consolidated statements to the entity balances and adjustments; approve the group close and retain the calculation inputs.

An entity accountant approves the local books; the group controller approves consolidation. Save source trial balances, rates, mapping versions and adjustment journals with the close. A later source correction should produce a new controlled consolidation version, with the changed inputs and impact visible. Rerunning the same inputs should not duplicate eliminations or create another payment.

Before adding an entity, test one local transaction, one intercompany invoice, a foreign-currency monetary balance and a group elimination. Trace a material group figure back to the originating entity journal. Those tests establish whether the accounting design works; a faster payout or a shorter report-generation time does not establish consolidation accuracy.

Add entities after the first close can be explained#

Start with reliable entity records and an approved reporting perimeter. Then map, translate and eliminate with enough detail to explain the group figures. The useful result is a consolidation that remains understandable when an invoice arrives late, a currency moves or a new company joins the group.