Meridian Ledger Meridian Ledger

8 Marina View, #28-01 Asia Square Tower 1, Singapore 018960

Monday–Friday, 9:00 AM – 6:00 PM

Meridian Ledger · Singapore · Intercompany & Consolidation

The total is the only thing that should look live.

Intercompany balances, eliminations and group consolidation, run as a sequence a finance team can hand to a new hire — not a reconciliation sprint rebuilt every month. This page describes how the process actually runs in a cloud bookkeeping workflow, and what a platform needs to support before it can call itself multi-entity.

Where the month actually goes

Tag & post with counterparty

Fixed once

account structure

Match by counterparty listing

Query

not text search

Clear differences inside tolerance

Next period

with an owner

Run elimination as adjustment layer

Reversible

never into entity

Group pack ready for review

One figure

consolidated

Working through the sequence below tells you which platform questions to put to a vendor — and which answers mean the platform only supports the ledger, not the close.

Read the foundations guide first Review the platform comparisons

Where the process usually breaks

Well-kept entity books still stall at consolidation.

The gap is almost never the ledger. Intercompany balances are matched late, eliminations are rebuilt from scratch each month, and nothing in the workflow enforces the sequence — posting, tagging, matching, eliminating, then consolidating.

The rest of this page walks the sequence in order. Each stage names what the workflow has to do, and the specific question to put to a platform vendor to find out whether that stage is genuinely supported or only drawn on a slide.

How the month actually runs

Three stages that decide whether the close is short.

These are the stages the process runs through — in this order. Skipping one puts the cost back into a later stage, where it's harder to see and harder to fix.

Stage 01 — posting

Tagging before matching

Intercompany starts at posting. When an entity records a charge to an affiliate, the entry needs a counterparty identifier and a matching intercompany account — not just a name in a description field.

That tag is what allows the group to produce a by-counterparty listing and identify what hasn't matched. Without it, matching is a text search. With it, matching is a query. The difference in effort per month is large, and it's the single change most likely to shorten a close.

Groups running QuickBooks Online or Xero per entity can still tag this way: the tag lives in the account structure rather than in a dedicated module.

Stage 03 — elimination

Eliminations as a controlled adjustment

Elimination removes intercompany income and expense, along with intercompany receivables and payables, so the consolidated pack reflects only transactions with parties outside the group.

It should appear as a visible adjustment layer — never as entries posted back into entity books. If eliminations live in entity books, entity-level reporting stops representing the entity, and statutory reporting gets harder.

The question to put to any vendor: can eliminations be reversed and re-run without touching entity ledgers? Platform capability varies sharply on this point.

Stage 02 — matching

Matching, tolerance and the review threshold

Matching means confirming that entity A's due-from balance to entity B equals entity B's due-to balance from entity A, in both amount and currency. In practice small differences arise: FX timing on a cross-currency charge, a charge booked in one entity and not yet in the other, a misposted amount.

Set a tolerance and a review threshold before close, not during it. Timing differences under the threshold can be cleared next period; anything above it needs an owner and a decision.

This is where automation helps and judgment can't be removed. Software can flag differences — someone still has to decide whether a difference is a timing item or an error.

Stage 04 — consolidation

What consolidation adds beyond addition

Consolidation is not summing trial balances. It requires currency translation of foreign entities at period rates, elimination of intercompany balances, recognition of non-controlling interests where applicable, and consistency of accounting policies across entities.

If one entity capitalizes software and another expenses it, the group must pick one treatment before consolidation means anything. For Singapore holdco structures, the consolidation layer is where group policy is enforced.

That is a reason to choose a platform with multi-book or policy-mapping capability when the group's entities differ in accounting treatment. Adding entities to a structure that already has policy drift multiplies the problem rather than adding to it.

Illustrated top-down view of a finance desk at close, hands moving paper and marking a ruled worksheet
This is the room where the close happens: worksheets on the desk, a calculator in reach, the elimination layer waiting for the entity packs to settle.

Where automated intercompany sits

The automation is real — the prerequisite is that the tagging above is already clean.

Automation and the platforms behind it

What automated intercompany actually changes about the month.

Where the automation is genuinely in place, a single intercompany charge can post both sides, and matching becomes confirmation rather than search. Automated intercompany on a messy chart of accounts produces automated mess — groups moving to this tier should expect the first close to be a cleanup close, and the second to be the one that shows the benefit.

What it does wellPosts both sides of an intercompany charge from a single entry when the accounts are tagged correctly.

Where it stops for a groupStops the moment the counterparty tag is missing — the entry lands in the wrong intercompany account and matching fails at the listing.

AxisPosting

What it does wellTurns monthly matching from a text search into a by-counterparty query once the tagging is in place.

Where it stops for a groupFlags a difference, but someone still has to decide whether it is a timing item or an error — the tolerance threshold belongs to the group, not the software.

AxisMatching

What it does wellApplies eliminations as a group-level layer that can be reversed and re-run without touching entity ledgers, so entity reporting keeps its own meaning.

Where it stops for a groupPlatform capability varies sharply. Some tools display consolidated output with eliminations applied; others require a group-level journal rebuilt each month.

AxisElimination

What it does wellTranslates foreign-entity trial balances at period rates and applies one accounting policy across the group in the consolidation layer.

Where it stops for a groupDoes not resolve policy drift. If one entity capitalizes software and another expenses it, the group has to pick one treatment before consolidation means anything.

AxisConsolidation

What it does wellNetSuite OneWorld is known for automated intercompany as part of its multi-entity and multi-currency scope. Sage Intacct's Singapore positioning highlights automating multi-entity processes. AccountsIQ is cloud financial management software aimed at medium-sized and multi-entity organizations, described as suitable for group reporting and finance control.

Where it stops for a groupAutomation depends on the group's own account structure and tagging being clean first. Feature lists rarely answer the question — how much of the process the group can standardize, whether a local implementation partner is available, and how many entities will be added in the next two years matter more.

AxisPlatform fit

A platform chosen for today's three entities and tomorrow's eight is a cheaper decision than one chosen twice. See how the field actually sits in our platform reviews and comparisons.

Running the sequence, month after month

Three moves that hold the close together.

The stages above tell you what has to happen. These three moves are how finance teams keep the sequence from drifting as entities are added.

01

Set tolerance

Agree the tolerance and the review threshold with the group controller before the close window opens, not while the numbers are arguing with each other.

02

Name the owner

Every unmatched difference above the threshold gets a named owner and a decision date. Differences under the threshold roll forward on their own — that is what the tolerance is for.

Matching is not a report somebody reads at the end. It is a working list that closes row by row, and the group needs to be able to open that list by counterparty at any point in the month.

03

Keep elimination outside the entity books

The elimination adjustment sits in the group layer, reversible and re-runnable. Entity ledgers keep representing the entity. The consolidated pack reflects the group.

When a new entity joins the structure, the same three moves apply from the first close: tolerance, owner, layer. A structure with policy drift multiplies the problem rather than adding to it.