Multi entity accounting is the practice of maintaining separate, complete books for each legal entity in a group while producing consolidated statements that present the whole as a single economic unit. Both halves are obligatory: entities have their own statutory and tax obligations, and the group has its own reporting duty.
​

Most of the difficulty is structural rather than technical. Decisions made early about chart of accounts, entity coding, and currency conventions determine how much manual effort every future close requires, and those decisions are expensive to reverse once several periods have been reported on them.
​

It is running a distinct ledger per legal entity, each capable of standing alone for statutory reporting, plus a consolidation process that combines them and removes internal activity. Each entity keeps its own trial balance, functional currency, and reporting obligations, while the group layer produces the combined view.
​

The consolidation step is defined by standard rather than convention. Under ASC 810, in preparing consolidated financial statements, intra-entity balances and transactions shall be eliminated, which is what stops internal activity inflating group results.
​

Which entities belong in the consolidation is a separate question from how they combine. IFRS 10 sets out a control-based test for which entities to consolidate, and it requires elimination of intra-group balances, transactions, income and expenses once they are in scope.
​

Use one shared account structure across every entity, with the entity itself as a separate dimension rather than encoded into account numbers. Entity-specific accounts should be rare exceptions for genuine local requirements, not the default, because divergent charts make consolidation a mapping exercise repeated every period.
​

Encoding entity into the account code is the classic early mistake. It looks tidy when there are three entities and becomes unworkable at fifteen, since every new entity requires a new set of accounts and every group report requires a translation table that someone must maintain.
​

Counterparty is the dimension most often omitted and most missed later. Without a field recording which group entity the other side of a transaction is, intercompany activity cannot be isolated for elimination, and the group is left inferring it from account descriptions. Since ASC 810 requires elimination in full, an unidentifiable intercompany balance is a reporting problem rather than a housekeeping one.
​

The table sets out the four decisions that determine how much work each close takes, the option that scales, the option that does not, and what breaks when the second is chosen. All four are cheap to set correctly at the start and expensive to change afterward.
​

The pattern across all four is the same. Standardizing at the group level costs a little local flexibility and removes a recurring cost from every subsequent period, which is a trade that improves as entity count grows.
​

Entities close in parallel to a common cut-off, intercompany balances are agreed before that cut-off rather than after, then the group performs eliminations, currency translation, and any consolidation adjustments. The sequence matters: consolidation cannot begin while entity positions are still moving.
​

Agreeing intercompany before close is the single change that most reduces close duration. A group that starts reconciling internal balances after the period ends has placed a negotiation between finance teams on the critical path of its reporting timetable.
​

Local statutory differences should be handled as adjustments layered onto group-basis numbers rather than as a separate parallel set of books. Maintaining two independent versions of the truth doubles the reconciliation surface and creates a permanent question about which is authoritative. A 2006 Journal of Accountancy analysis made the timing case plainly, urging that reconciliations complete early enough for adjustments to reach the ledger before reporting.
​

Each entity keeps a functional currency and the group reports in a presentation currency, with translation applied at consolidation. The rates used must come from one central table applied consistently, because two entities translating the same internal transaction from different sources will always disagree.
​

Translation differences on external balances are a legitimate accounting outcome and belong in their own reserve. Differences arising on internal balances because of inconsistent rate application are not an accounting outcome; they are a process defect that recurs every period until the rate convention is fixed.
​

Cross-border payment standards are converging on richer structured data that makes these flows easier to decompose. Swift states that the cross-border coexistence period ended on 22 November 2025, with ISO 20022 now the global standard for cross-border payments.
​

Three are needed beyond ordinary entity-level controls: a defined owner for group accounting policy, segregation between entities that raise internal charges and those adjudicating disputes, and a documented elimination process an independent reviewer can reproduce from the underlying records without asking anyone.
​

Segregation is not optional even inside a group. GAO's internal control standards hold that key duties and responsibilities need to be divided or segregated among different people, and an entity that both raises a charge and decides whether the other entity must accept it has no such division.
​

The reproducibility requirement carries audit weight. Under PCAOB AS 2201, a material misstatement that the company's own control did not detect is a strong indicator of a material weakness, and consolidation adjustments are a natural place for one to hide.
​

Allocations should follow a documented basis agreed in advance, post with a counterparty code, and require acceptance above a threshold. An allocation the receiving entity never agreed to becomes an intercompany dispute at close, which is the most predictable and most avoidable category of group reconciliation work.
​

The documented basis matters more than its sophistication. A simple headcount driver everyone accepted beats an elaborate activity-based model nobody signed off on, because the purpose is a number both entities will book without argument.
​

Where allocations involve margin rather than cost recovery, unrealized profit arises if the receiving entity capitalizes any of it. Intercompany income should be eliminated from the applicable asset on a before-tax basis, using gross profit or loss as the concept applied.
​

The number of entity pairs grows faster than the number of entities, so intercompany workload rises faster than headcount or revenue. A group with four entities has a manageable set of relationships; one with twelve has enough that anything handled by correspondence rather than by rule stops working.
​

Engines that reconcile AR, AP, bank, PSP, and intercompany data through one rule-based engine exist because that shift happens at a fairly predictable size, usually somewhere between five and ten entities.
​

This is why the structural decisions compound. A shared chart, mandatory counterparty coding, and a central rate table are mild conveniences at four entities and the difference between a three-day and a three-week close at twenty.
​

Acquisitions apply this pressure suddenly rather than gradually. A newly purchased subsidiary arrives with its own conventions, and the periods before it adopts group protocols reliably produce the largest reconciliation differences of the year, which is worth planning for rather than discovering.
​

Consolidation scope is a control question rather than an ownership percentage question. An entity the group controls is consolidated in full, with any outside interest presented separately, while entities that are influenced but not controlled are accounted for differently and are not part of the elimination process.
​

The two major frameworks reach this by different routes. IFRS 10 applies a single control test based on power over the investee and exposure to variable returns, while US GAAP distinguishes voting interest entities from variable interest entities before arriving at a consolidation conclusion.
​

Once an entity is in scope, the elimination mechanics are effectively identical under both. That is why scope decisions deserve careful attention early: they determine which relationships enter the intercompany process at all, and revisiting them later restates prior periods.
​

Outside interests do not reduce eliminations. Under ASC 810, the amount of intra-entity income to be eliminated is not affected by the existence of a noncontrolling interest, which is a point groups with partially owned subsidiaries frequently get wrong.
​

Work backwards from the group reporting date. Intercompany cut-off comes first, several days before period end, followed by entity close, then group elimination and translation, then review. Each step needs a named owner and a deadline, because a calendar without ownership is a diagram rather than a control.
​

The timing logic is not new. A 2006 Journal of Accountancy analysis argued that reconciliations should complete before reporting so adjustments feed the numbers rather than following them, and a group calendar is where that principle either holds or fails.
​

The intercompany cut-off ahead of period end is the part most often omitted and the part that most determines close length. It gives entities time to post corrections while the period is still open, rather than discovering disagreements when nothing can be adjusted without a journal at group level.
​

Materiality thresholds should be set in the calendar too. A policy stating which differences must be resolved and which are absorbed prevents small items consuming the same attention as large ones during the days when attention is scarcest.
​

Escalation needs to be automatic rather than requested. If an unresolved difference above a threshold routes to a named decision maker on a fixed day, deadlock becomes a decision instead of an open item carried into the next period.
​

Cash sits in entity bank accounts and belongs to those entities, even when managed centrally. Any pooling, sweeping, or on-lending arrangement creates intercompany positions that must be recorded on both sides and eliminated later, so treasury structure and accounting structure have to be designed together.
​

The frequent error is treating a group cash position as though it were fungible. Moving cash between entities is a financing transaction with legal, tax, and accounting consequences, not an internal transfer between accounts, and recording it casually creates balances nobody agreed.
​

Physical pooling and notional pooling differ here in a way that matters. Physical movement creates real intercompany loans requiring interest, documentation, and elimination; notional arrangements may not move funds at all, and conflating the two produces balances that cannot be substantiated.
​

Cross-border pooling adds the currency and messaging dimension on top. Swift describes ISO 20022 as carrying richer, better structured and more granular data end-to-end in payments messages, which is what allows an internal cross-border movement to arrive with enough detail to book correctly on both sides.
​

Adopt the group protocol before the first close rather than after it. That means the shared chart of accounts, the counterparty coding scheme, the central rate table, and the close calendar, all applied from the entity's first reporting period in the group.
​

Migrating the entity's underlying system is a separate and usually later decision. The four protocol items can be imposed across heterogeneous ledgers, and doing so captures most of the benefit without the risk and duration of a system migration during an integration.
​

Opening balances deserve their own reconciliation. A newly purchased subsidiary's first group close inherits positions nobody in the group has verified, and treating those as given rather than as items to substantiate is how errors persist across periods undetected.
​

Budget for a noisy first period rather than treating it as a failure. The integration work that reduces differences is counterparty mapping, rate alignment, and cut-off alignment, and each takes at least one full cycle to settle.
​

Segregation should be established at the same time. GAO's standards on dividing key duties among different people apply from the first transaction, and retrofitting separation after roles have settled is harder than defining it at the start.
​

Four recur: encoding entity into account numbers, omitting counterparty on intercompany postings, letting each entity pick its own currency rates, and closing entities independently before agreeing internal balances. Each is inexpensive to prevent and expensive to unwind after several reported periods.
​

A fifth, subtler one is treating consolidation as a spreadsheet step outside the accounting system. Eliminations maintained in a workbook are difficult to reproduce, easy to break, and hard to evidence, which makes them a natural place for an undetected error to survive.
​

That matters directly for audit. Under PCAOB AS 2201, a material misstatement the company's own control failed to catch is a strong indicator of a material weakness, and a consolidation nobody can reproduce independently is weak evidence that any control operated.
​

The remedy in each case is the same: make the group structure explicit in the data rather than implicit in someone's method. Explicit structure survives staff changes, acquisitions, and growth in entity count; implicit method does not, which is the practical reason to fix these things while the group is still small enough that fixing them is cheap.
​

Three views that reconcile to each other: each entity on its own basis for statutory purposes, the group consolidated view, and a management view that may cut across entities by business line. All three should derive from the same underlying postings rather than being separately maintained.
​

The reconciliation between views is what makes them trustworthy. Anyone should be able to move from the sum of entity results to the consolidated result through a stated bridge of eliminations, translation effects, and consolidation adjustments, with each line traceable to records.
​

Deriving all three from one set of postings is what prevents the views drifting apart over time, since separately maintained versions diverge the moment one is adjusted and the other is not.
​

Management cuts are where independence from legal structure matters most. If business line reporting requires legal entity to be a proxy for business line, the group loses the ability to reorganize entities without breaking its own reporting, which is a real constraint on corporate change and one that surfaces at the worst moment, during a restructuring.
​

The consolidated view is the one carrying external obligations, and it is defined by the elimination requirement: intra-entity balances and transactions shall be eliminated so the group presents only its dealings with the outside world.
​

It removes in-transit differences on internal transfers, which are the largest category by count in most intercompany queues. When a transfer between entities settles and confirms immediately, both sides record it in the same period instead of straddling a cut-off.
​

Everything substantive is untouched. Elimination entries, unrealized profit, allocation disputes, currency conventions, and consolidation adjustments are accounting judgments that no settlement mechanism performs, and a faster rail changes none of them.
​

The effect is largest on cross-border internal transfers, which carry the longest settlement windows. The stablecoin market held $311.0 billion in total supply as of September 9, 2026, led by USDT at $183.4 billion and USDC at $74.4 billion, according to DeFiLlama.
​

Eco operates the routing and execution layer that stablecoin value moves through, so a transfer between two group entities produces a single settlement record both can reference, rather than two systems recording the same movement and later disagreeing on its timing or amount.
​

That addresses in-transit differences and nothing beyond them. Eco is not a consolidation system, does not produce group statements, and does not perform eliminations. Multi entity accounting remains an accounting discipline, and the structural decisions above matter far more to close speed than settlement speed does.
​

For the settlement record those processes reconcile against, Eco's comparison of stablecoin settlement APIs with audit trails covers what that record should expose.
​

Methodology. Elimination requirements and the before-tax treatment of intercompany income are from PwC Viewpoint's summary of ASC 810 intercompany transactions, retrieved September 9, 2026, citing ASC 810-10-45-1 and related paragraphs. The control-based consolidation scope and full elimination requirement are per IFRS 10. Segregation of duties is per GAO internal control reporting; audit consequences per PCAOB AS 2201. This article describes general requirements and is not accounting advice for a specific structure. Stablecoin supply is from DeFiLlama as of September 9, 2026 and moves intraday.
​