Opening an entity in a new country takes weeks. Building a finance function that works across several countries takes design. Most groups do the first many times before they attempt the second.
The pattern is familiar. Each new entity is set up with a local accountant, a local chart of accounts, and its own way of closing the month. For a while the group consolidates by spreadsheet. Then an investor, lender, or acquirer asks for group numbers on a timetable, and the spreadsheet cannot deliver.
Decide what is central and what is local
The first design decision is which parts of finance are set once for the group and which belong to each country.
- Local by nature: statutory accounts, tax filings, payroll compliance, and dealings with local authorities and banks
- Central by design: accounting policies, the chart of accounts, the close timetable, the reporting pack, controls, and treasury policy
Trouble starts when the second list is left to each entity. Different policies and account structures make consolidation a translation exercise every month.
One chart of accounts, two sets of books
Groups often believe they must choose between local compliance and group consistency. They do not. The usual solution is a single group chart of accounts with a mapping to each country's statutory format, and an adjustment ledger for differences between group policy and local rules.
The entity then keeps one set of transactions that can be reported both ways. The mapping is built once and maintained centrally.
Intercompany discipline
Intercompany balances are where multi-entity closes usually fail. Each side records the transaction at a different time, in a different currency, or not at all.
- Written agreements for every recurring intercompany service or loan
- A pricing policy that can be defended to tax authorities in both countries
- Invoices raised on a fixed monthly schedule
- Balances agreed between entities before the close, not after
- Regular settlement, so balances do not build up indefinitely
Groups that agree intercompany positions on a set day each month remove the single largest cause of delay in consolidation.
Cash and currency
With several entities come several bank accounts and currencies. The group needs one view.
- Daily or weekly cash by entity and currency in a single report
- A forecast showing where cash will be short and where it will be idle
- A policy on moving cash between entities, within local rules
- A measured view of currency exposure, and a decision on whether to hedge
Without this, groups regularly borrow in one entity while holding surplus cash in another.
People and systems
A common model is a central finance team that owns policy, consolidation, and reporting, supported by local providers for statutory work. Each entity has a named owner responsible for its numbers.
A multi-entity ERP makes all of this easier, but it should follow the design, not precede it. Migrating unclear processes into a new system preserves the confusion and makes it more expensive to change. Agree the chart of accounts, policies, and close calendar first; then configure the system to enforce them.
A sequence that works
- Map the current state: entities, systems, policies, and who does what
- Agree group policies and the chart of accounts
- Set a single close calendar
- Document and regularise intercompany arrangements
- Build the consolidation and reporting pack
- Then select or reconfigure systems to support it
Most mid-market groups can complete the first five steps within two quarters.
The anatomy of a group close
A common close calendar is the most useful single tool in multi-entity finance. It lists, for every entity, what must be done on each working day after month-end.
- Day 1 to 2: cut-off, bank reconciliations, sub-ledger closes
- Day 2 to 3: intercompany agreement between entities
- Day 3 to 5: accruals, payroll, revenue recognition, fixed assets
- Day 5 to 6: entity review and sign-off by the named owner
- Day 6 to 8: consolidation, eliminations, currency translation
- Day 8 to 10: group review, reporting pack, commentary
The exact days vary. What matters is that every entity works to the same timetable and that slippage in one is visible immediately.
Controls that travel
As entities multiply, the risk of error or misuse rises, particularly where local teams are small.
- A group approval matrix setting who may commit and pay what
- Bank mandates requiring two signatories, with central visibility of all accounts
- Separation between those who raise payments and those who approve them
- Standard reconciliations reviewed by someone outside the entity
- Controlled access to the accounting system
- A periodic review of each entity by the central team
These controls should be the same everywhere. A weaker standard in a small entity is where problems tend to occur.
Consolidation mechanics
Consolidation is more than adding entities together.
- Intercompany sales, costs, loans, and balances must be eliminated
- Each entity's results must be translated into the group currency on a consistent basis
- Differences between local and group accounting policies must be adjusted
- Interests held by outside shareholders must be shown separately
- Acquired entities bring goodwill and fair value adjustments
Performed in spreadsheets, this is slow and error-prone. Performed in a system, with intercompany balances already agreed, it can be done in a day or two.
Managing local advisers
Each country usually has its own accountant, auditor, payroll provider, and tax adviser. Left unmanaged, they work to their own timetables and standards.
A central owner should hold the calendar of all statutory deadlines, set expectations for each provider, receive regular confirmation that filings are made, and review fees. Standard instructions and a common format for what each provider returns reduce the effort considerably. As the group grows, consolidating providers across countries can improve both quality and cost.
Shared services
Once a group has several entities, it becomes efficient to perform routine finance work in one place: payables, receivables, bank reconciliations, payroll processing, and reporting.
A shared service team, whether internal or outsourced, brings consistent process, cover for absence, and lower cost. Local presence is then needed only for matters that require it. The move works when processes have been standardised first. Centralising work that is still done differently in each entity transfers the confusion to a new location.
Measuring the finance function
- Working days to close each entity and the group
- Number and value of adjustments after close
- Unreconciled intercompany differences
- Statutory filings made on time
- Audit adjustments
- Cost of finance relative to revenue
Tracked over time, these show whether the design is working and where to direct attention.
When to act
The right moment is before the third entity or the first external investor, whichever comes first. Up to that point informal methods cope. Beyond it, each new entity makes the eventual clean-up larger. Groups that standardise early find that adding a country becomes a routine exercise. Those that wait find that each addition makes the month-end longer.
Mistakes to avoid
- Letting each entity choose its own chart of accounts and policies
- Buying a multi-entity ERP before agreeing the design
- Reconciling intercompany balances only at year-end
- Applying lighter controls in smaller entities
- Leaving statutory deadlines with local providers and no central calendar
- Centralising work before standardising it
These are the usual reasons a multi-entity close takes weeks. All of them are design choices, and all can be reversed.
How FundVice approaches it
We have run finance functions across six and seven entities for clients, so we start from how a group close actually fails and work back to the design.
A typical engagement begins with a map of entities, systems, policies, and people, followed by a group chart of accounts, a single close calendar, and regularised intercompany arrangements. We then run the close ourselves for several cycles, which is the quickest way to find what the design missed. System selection or migration follows once the process is stable. Where the client prefers, we continue as the central finance team, with local providers reporting to us.
Questions to ask in your own business
- Do all our entities close on the same day, to the same standard?
- Could we produce consolidated accounts within ten working days of month-end?
- Are intercompany balances agreed between entities every month?
- Can we see group cash by entity and currency today?
- Who is accountable for each entity's numbers?
The takeaway
Multi-jurisdiction finance works when the group decides once how it will report and each entity follows the same design. The design costs little. Its absence is paid for every month, and most heavily during a transaction.
Keep Reading
Related Insights
Article · Finance Function Excellence • SaaS
The Cost Of Scaling Before Finance Is Ready
Why investor-grade reporting becomes a competitive advantage long before the next funding round.
Read article →Article · Investment Advisory • IT Services
What Buyers Really Diligence In IT Services Businesses
The metrics, governance structures, and operational indicators that influence valuation outcomes.
Read article →Article · Finance Function Excellence • Consumer Products
Building Finance Infrastructure For Modern Consumer Brands
How growing brands can improve visibility, working capital control, and reporting discipline.
Read article →