Multi-Entity Bookkeeping Guide

Foundations before you pick a platform

Tooling decisions made before the chart of accounts is designed get reversed within a year. This page is the groundwork that makes a platform selection answerable.

Four foundations, settled before software enters the room

Chart of accounts design

Shared core, entity extensions — one code structure the whole group can read.

Decide first

Intercompany accounts

Due-from and due-to pairs, in the shared chart, matched by counterparty.

From day one

Multi-currency policy

Transactional rates and translation rates carried as two separate policies.

Write it down

Entity-level reporting

Statutory and management views cut from the same trial balance, by design.

Same source

Month-end close sequence

Eight ordered steps, one owner each, with a working-day target per step.

8 Steps in the close

Start with the foundations Compare platforms against these foundations

Before the software conversation

None of it is exotic

Singapore groups feel the pain of a bad multi-entity setup in the same three places every year: an intercompany elimination that needs a spreadsheet, a consolidated pack that will not tie, and a close whose critical path runs through one person.

The remedy is not a cleverer tool. It is a set of decisions a group finance team can write down in an afternoon — where accounts come from, what currencies mean, which entity reports what, and in what order the month closes. Get those four right and every platform you look at afterwards is judged against a real requirement instead of a demo.

What this page settles

One chart of accounts, or several that reconcile

Shared core with entity extensions vs. separate charts with a maintained mapping table.
Dedicated intercompany accounts

Balance-sheet pairs, so the elimination is matcher work and not detective work.
Transactional vs. translation currency

Two rates, two policies, two places those differences are supposed to land.
Entity view and group view

Both outputs of one close, both traceable back to the same entity balances.
Close sequence and its shortening

Write the steps down with owners and targets — usually two then run in parallel.

Chapter one

One chart of accounts, or several that reconcile

The first decision is whether entities share a chart of accounts. Both answers work — but only one of them stays cheap to maintain.

Shared chart

One chart, one code structure

A shared chart makes consolidation straightforward because account codes line up across entities. Intercompany pairing becomes mechanical rather than interpretive — a due-to account in one entity is matched by code, not by judgement.

The cost is that entity-specific reporting gets slightly blunter, because every entity carries accounts it doesn't use. For a group running similar operations across two or three entities, that bluntness is a fine trade.

Suited to: groups of 2–4 entities with related operations and a small finance team.

Mixed activity

Shared core plus entity extensions

Singapore groups with mixed activity often run a shared core chart with account codes for the common spine of every entity — bank, trade receivables, trade payables, intercompany, tax — then allow each entity a small block of extensions for what only it needs.

The group reports on the shared core; an entity that holds a shipping operation or a lease can add the codes it requires without forcing the whole group to carry them. This is a reasonable compromise and the one we would default to.

Suited to: most Singapore groups of 3–10 entities with mixed trading and service activity.

Separate charts

Separate charts, one mapping table

Separate charts suit entities with genuinely different operations — a trading company and a service company sit on different account structures for good reasons, and forcing one onto the other produces noise in every management report.

The cost is the mapping table between entity accounts and group accounts. Someone has to own it, keep it current when an entity opens a new account, and treat it as a control rather than a helper. That table becomes the single point that either keeps the consolidation honest or quietly breaks it.

Watch for: an entity that opens a new account without updating the mapping.

Practice

Write down the decision

Whichever shape a group picks, the decision belongs in a document that names the account families, the codes that belong to the shared core, and the mechanism for adding entity-specific accounts. Without that document, every new entity becomes a negotiation.

The document is short — one page of families and one page of rules — and it is the difference between a chart of accounts that scales to a tenth entity and one that has to be rebuilt when the fifth entity arrives.

Owner: usually the group financial controller or the finance lead closest to the close.

Chapter two

Intercompany transactions need dedicated balance sheet accounts, and they need to be a pair. Post them to ordinary trade receivables and payables and the elimination becomes a research project.

Give intercompany its own accounts from day one

A due-from account in one entity has a due-to account in another. Both need to live in the shared chart so the elimination can be automated, or at least reliably matched at month end, by the person closing rather than by whoever happens to know the intercompany spreadsheet.

The structure itself is not complicated: a small block of intercompany balance sheet accounts, one pair per counterparty relationship, kept under the group's control rather than under each entity's discretion. What that buys is a monthly listing that a controller can pull in a few minutes and trust.

The practical test: at any point in the month, a controller should be able to pull a listing of intercompany balances by counterparty and see it net to zero across the group. If that listing requires a spreadsheet built from three exports, the accounts aren't structured yet.

A worked illustration

Entity A — due from B Dr

Entity B — due to A Cr

Group elimination 0

A properly paired intercompany set nets to zero. Any residual on the group level is either a timing difference or a misposting — and both are cheap to see when the accounts are paired.

Chapter three

Multi-currency: transactional and translation are different jobs

Groups commonly conflate two things that use different rates and serve different purposes. Set both policies in writing before the first close, because ambiguity here produces a consolidated pack that won't tie — and the fix lands on the person closing.

Transactional currency

Recording a USD supplier invoice inside a SGD-functional entity, at the transaction date rate. The functional currency of the entity does not change: the entity is a SGD book, and this invoice happens to be denominated in USD.

The rate source belongs in writing. Groups commonly settle on a published mid-rate for the invoice date, with the entity booking the payable and the FX gain or loss on settlement to a designated account. What matters is that the entity's own books stay legible to its own management.

Rate source: Transaction-date rate
Affects: The entity's own books
Lands in: Entity P&L or balance sheet

Translation currency

Converting a foreign subsidiary's full trial balance into the group's presentation currency, at period rates. Singapore groups with a Malaysian or Indonesian subsidiary face this every month, and the ambiguity shows up first as a difference that nobody can source.

Three decisions belong in writing before the first close: a defined closing rate source, a defined average rate source for the P&L, and a defined treatment for translation differences. Those differences belong in equity rather than the income statement, and the choice is not a matter of taste.

Rate source: Closing and period average
Affects: The group's consolidated pack
Lands in: Equity, not income statement

Where the close happens

A close is a set of rules holding under real pressure

A Singapore finance office at close: a long workbench with monitors, a coffee cup and a filing bank against the back wall. — Singapore groups close in a room like this one — near-white light, a screen in the middle of the desk, and the same paper trail every month.

Chapter four

Entity-level reporting is the deliverable, not the by-product

A group close produces two outputs: the consolidated pack and each entity's own reporting. The entity view matters for statutory filing, GST returns and, in many structures, for management's view of how each business is performing. If the consolidation process destroys or obscures entity detail, the group has traded one problem for another.

Design reports so entity-level and group-level views come from the same data. In practice this means the trial balance can be cut by entity at any point, and intercompany eliminations are applied as a visible adjustment rather than buried in an entity's books. A reader of the consolidated pack should be able to trace a group figure back to the entity balances and the elimination between them.

One test, two views

01

Cut the trial balance by entity

Each entity's own numbers should be visible without a fresh export.
02

See eliminations as an adjustment

A dated, auditable adjustment rather than a silent change to the entity's own ledger.
03

Trace a group figure to source

Any consolidated number should be explainable by the entity balances and the elimination behind it.

Chapter five

Month-end close: sequence it, then shorten it

Singapore group closes have a natural order, and the order matters because some steps cannot begin until an earlier one resolves. Write the sequence down with an owner and a working-day target for each step. Groups that never write it down tend to discover that the close's critical path runs through one person — often the same person who knows where the intercompany spreadsheet lives.

Step	What happens	Owner	Working day
01	Bank reconciliations — every entity's bank accounts cleared against the ledger.	Each entity's finance lead	WD 1–2
02	Intercompany matching — both sides of every pair posted before matching can close.	Group finance	WD 2–3
03	Accruals and provisions — routine month-end adjustments captured before review.	Each entity's finance lead	WD 2–3
04	GST review — returns and reconciliation reviewed per entity before the group consolidates.	Tax lead	WD 3–4
05	Currency translation — foreign trial balances brought into the presentation currency.	Group finance	WD 4
06	Elimination — intercompany balances collapsed, once matching has resolved.	Group finance	WD 4–5
07	Consolidated pack — group statements assembled, with the elimination visible as an adjustment.	Group financial controller	WD 5
08	Entity reporting — statutory, GST and management views cut from the same data.	Each entity's finance lead	WD 5–6

The working-day figures above are illustrative targets, not a benchmark. Groups should set their own — the useful part is naming a target, not the number itself.

Chapter six

The mistakes, in the order they bite

Six things go wrong in a Singapore multi-entity setup before the platform conversation even starts. Each is fixable; each is cheaper to fix before the platform decision than after.

01

Intercompany charges posted to trade accounts

The elimination becomes manual because the balances cannot be distinguished from third-party receivables and payables at a glance.
02

Separate charts without a maintained mapping

A mapping table that no one owns drifts out of date the first time an entity opens a new code, and the drift is invisible until it reaches the consolidated pack.
03

Choosing a consolidation platform before the chart exists

The platform selection is judged against a demo rather than a requirement, and the shortlist looks reasonable until the second close.

04

One entity closing on a different timetable

A late entity delays intercompany matching for everyone in the group, and no downstream step can bring the pack back on schedule.
05

Presentation currency mistaken for functional currency

An entity that clearly operates in another currency is booked as if it is a group-currency book. Translation differences then appear where they have no business being.
06

Never writing the close sequence down

The critical path runs through one person, and the fix is an afternoon of sequencing that also reveals two steps that could run in parallel.

Questions a finance lead usually asks

Where to take the foundations next

Six questions that come up before a Singapore group commits to a platform — with plain answers, not a sales script.

Do we have to pick one chart of accounts for the whole group?

No. Separate charts are fine — what matters is that the mapping table between entity accounts and group accounts has an owner and is maintained as a control. Most Singapore groups with mixed activity settle on a shared core chart with a small entity extension, because it keeps most of the consolidation mechanical without forcing a shipping operation into a service company's account list.

How many intercompany account pairs does a group of five entities need?

Up to ten pairs if every entity transacts with every other entity. Most Singapore groups do not, and the practical answer is to open pairs only where transaction flows exist and to name the counterparty in the account description. The account structure is cheap to extend later; what is expensive is discovering a transaction was posted to trade receivables because the pair did not exist yet.

What closing rate source should we use for translation?

A published, defined source that everyone agrees on before the first close — not the rate somebody retrieves from a bank portal on the day. What matters most is consistency and traceability: a reader of the consolidated pack should be able to see which closing rate was used, which average rate was used for the P&L, and where the resulting difference landed.

Can we keep using spreadsheets for the intercompany listing?

A spreadsheet is fine as a working listing. It is not fine as the source of truth for intercompany balances, because the accounts are already carrying the balances and the spreadsheet becomes a second, drifting version. If the spreadsheet is unavoidable, treat it as a view of the ledger, not a substitute for it, and rebuild it from the trial balance each close.

Which should we do first — foundations or platform selection?

Foundations. Four decisions — chart structure, intercompany accounts, currency policy, close sequence — take an afternoon and give you the requirement against which any platform can be judged. A platform chosen first is chosen against a demo, and the tools that look strongest in a demo are rarely the ones that survive the second close.

How does this connect to GST and e-invoicing?

Entity-level reporting is where GST returns are prepared, so an entity whose books are being obscured by the consolidation process cannot file cleanly. Getting the entity view right is a prerequisite for GST readiness — and it is also what makes a per-entity review before the consolidated pack possible.