Cross-border expansion is usually driven by a commercial opportunity: a customer base, a talent pool, a supplier relationship. The finance implications get treated as administrative detail to be sorted out once the decision is made.
They are not administrative. Opening an entity in a second country adds three things at once, each of which breaks a different assumption in a single-country accounting setup. Handled early they are manageable. Handled after the entity is trading they are expensive, because unwinding a structure or restating a year of transactions costs far more than setting it up correctly.
Three things that arrive together
A second currency, in three different senses. Transactions denominated in another currency. A subsidiary whose books are kept in that currency. And a group result that has to be presented in one. These are distinct problems. A system that handles the first, invoicing a customer in another currency, may have no answer at all for the third, translating a full set of subsidiary books at the right rates for each line.
A second set of statutory obligations. The new country has its own filing requirements, its own chart of accounts conventions, often its own indirect tax regime and its own deadlines. These obligations are local and non-negotiable, and they exist whether or not your group reporting is ready for them.
A second entity to consolidate. Even a small foreign subsidiary has to be combined with the parent, with intercompany transactions eliminated, on your normal reporting cycle.
Why currency is harder than it looks
Most finance teams expect currency to mean applying an exchange rate. The difficulty is that different items require different rates, and the difference between them is not an error to be eliminated.
Balance sheet items are generally translated at the rate on the reporting date. Income statement items are generally translated at rates approximating those in effect when the transactions occurred, often an average for the period. Equity is generally carried at historical rates. Because these three sets of rates differ, the translated statements do not naturally balance, and the difference accumulates in a separate component of equity.
That is the correct outcome, not a mistake. But a system that cannot perform this translation leaves someone doing it in a spreadsheet every period, tracking the cumulative difference by hand across years. It is exactly the kind of calculation that is fine for two periods and unreliable by period twenty.
Separately, transactions settling in a different currency from the one they were recorded in produce real gains and losses that belong in the income statement, and these are different from translation effects. Systems that treat all currency movement the same way tend to put both in the wrong place.
The decision that is hardest to reverse
Of everything involved in cross-border expansion, the entity structure is the choice most worth slowing down for, because it is the one that costs the most to change afterwards.
A branch, a subsidiary and a representative office have materially different consequences for taxation, liability and filing obligations, and the right answer depends on the specific countries, the activity being performed and the plan for the next few years. That determination belongs with a tax adviser who knows both jurisdictions, before anything is registered.
What matters from a systems perspective is simpler: whatever structure is chosen, your accounting setup has to be able to keep books for it and roll it up. Discovering after registration that the structure you chose cannot be represented in your system without workarounds is a bad sequence, and a common one.
A sensible order of operations
- Settle the entity structure with tax advice in both countries before registering anything
- Establish which currency the subsidiary will keep its books in, and confirm your system can hold books in a currency other than the group currency
- Confirm how the system handles translation for consolidation, and specifically whether it tracks the cumulative translation difference automatically
- Define intercompany transaction types before they start happening, including how they will be identified and eliminated
- Understand the local filing calendar and who is responsible for meeting it, whether internal or a local accountant
Done in this order, the finance side is a project. Done after trading begins, each item becomes a correction, and corrections in a foreign subsidiary tend to involve a local adviser, your auditor and a restatement.
Where single-country systems run out
These gaps appear within the first few reporting cycles after a foreign entity starts trading.
The system holds one currency and calls that enough
Being able to invoice in another currency is not the same as being able to keep a full set of books in one. If the subsidiary's ledger has to be maintained in the group currency because the system cannot do otherwise, local reporting and the local filing obligation both become manual exercises performed outside the system.
Translation done by hand every period
Where the system cannot translate a subsidiary using different rates for balance sheet, income statement and equity, someone rebuilds it in a spreadsheet each period and carries the cumulative translation difference forward manually. This is accurate for a while and then quietly is not, and the error is difficult to find because it accumulates across periods.
Intercompany transactions with no matching mechanism
Once two entities transact, both sides have to be identified and eliminated so revenue and cost are not double counted. Across currencies they also have to be eliminated at consistent rates. Without system support this is a monthly reconciliation that grows with transaction volume and fails silently when a pair is missed.
Two charts of accounts that have to agree
The local entity may need to report on a locally conventional account structure while the group consolidates on its own. Maintaining a mapping between them is routine when the system supports it and a permanent manual translation layer when it does not, with a person in the middle of every period.
Questions we hear most often
Do we need a new accounting system before opening a foreign entity?
Not always, but you need an honest answer to three questions first: can the system keep a full set of books in a currency other than your group currency, can it translate that subsidiary for consolidation using different rates by statement type, and can it identify and eliminate intercompany transactions. If the answer to any is no, someone will be doing that work manually every period from the first month.
Can we just use a local accountant in the new country?
For local filing obligations that is often the right answer, and in many jurisdictions it is effectively required. It does not solve group consolidation. The local accountant produces statutory accounts to local rules on a local calendar. Turning those into a line in your group numbers on your reporting deadline is a separate exercise that still lands with your team.
What is the difference between transaction gains and translation adjustments?
A transaction gain or loss is real and belongs in the income statement: you invoiced in one currency, were paid at a different rate, and the difference is an actual economic outcome. A translation adjustment arises from restating a subsidiary's whole set of books into the group currency and generally sits in a separate component of equity rather than in earnings. Systems that treat both the same way put one of them in the wrong place.
How far ahead should we start on the finance side?
Before the entity is registered, because the structure decision is the one that is most expensive to reverse and it has tax, liability and filing consequences that differ by jurisdiction. Once trading begins, every gap becomes a correction rather than a setup task, and corrections in a foreign subsidiary usually involve a local adviser and your auditor.
We are only opening a small sales office. Does all of this apply?
Some of it, in proportion. A small office may not need full local statutory accounts depending on structure and jurisdiction, which is exactly why the structure decision comes first. What does apply regardless is currency and consolidation: as soon as there is activity in another currency that has to appear in your group numbers, translation and intercompany elimination are in scope, however small the office is.
Related problems
- Consolidating multiple entitiesWhy group reporting slows down as entities are added, and what fixes it.
- We acquired a company and now run two systemsWhat the first close after an acquisition reveals, and what it costs.
- Why your month-end close keeps getting longerThe complete breakdown of what stretches a close and what shortens it.
- Reports take days to buildWhy a simple report takes days to assemble and what real-time reporting requires.
Get a clear picture of where your gaps actually are
The free ERP Readiness Scorecard covers reporting, inventory, purchasing, multi-entity complexity, and more. Get a score based on your specific situation in under 5 minutes.
No sales pitch. No vendor push. Just a clear picture of where your systems stand.