Tax complexity in multi-entity setups: what accounting teams need to watch.

When one entity becomes many: where complexity changes shape

Most finance teams first meet tax complexity as a volume problem: more invoices, more reconciliations, more month-end journal entries. That is real, but it understates what actually happens when a group moves from one or two entities into a genuine multi-entity, multi-country structure. The change is not incremental. It is structural.

A single-entity business can run compliant tax reporting largely as a downstream consequence of clean bookkeeping. A group with entities across jurisdictions cannot. Every intercompany transaction, every cross-border sale, every seconded employee, every royalty or service charge between related companies now raises questions that a purely bookkeeping-level view of the ledger was never designed to answer. The accounting function does not need to become a tax function — but it does need to hold the data in a shape that lets a tax function do its job.

Intercompany transactions and the transfer-pricing question

The moment two related entities transact with each other — a management fee, a shared-services recharge, a licence for group IP, a transfer of goods between a manufacturing entity and a sales entity — a general principle applies across essentially every jurisdiction: pricing between related parties should reflect what independent parties would have agreed, and in many cases that pricing needs to be documented and defensible. Exactly which transactions require which level of documentation, and at what scale, depends on the jurisdictions involved and changes over time. That is precisely the kind of question that belongs with a qualified tax advisor, not in a piece of website content.

What does belong here is the operational implication. Once a group has more than a handful of intercompany flows, someone needs to be able to answer, for any given period, which entities transacted with which other entities, on what basis, at what price, and against what documented policy. That answer either exists because the finance system was built to produce it — or it gets reconstructed, transaction by transaction, when an advisor or auditor asks for it. The second path is materially slower and more expensive than the first.

The question we hear most often from finance leaders is not "are we compliant" — it is "could we answer that question quickly if we were asked". For a genuine multi-entity group, the honest answer usually depends entirely on how the chart of accounts and dimensions were designed, not on how careful the accounting team is.

Cross-border VAT and indirect tax: obligations that follow the goods

Indirect tax — VAT, GST, sales tax, depending on the jurisdiction — follows a similarly structural logic: obligations generally attach to where goods and services are supplied and where inventory is held, not to where the parent company happens to be incorporated. As a group adds sales channels, adds warehousing locations, or starts shipping and invoicing across more borders, the number of jurisdictions in which an indirect-tax obligation can arise tends to grow faster than the number of legal entities does. A single new fulfilment location in a new country, or a new direct-to-consumer channel into a market the group previously only served through distributors, can change the indirect-tax picture even without a new entity ever being created.

Specific registration thresholds, rates, and simplification schemes vary by country and change frequently, so they are deliberately not detailed here. What is worth building into the finance architecture, regardless of jurisdiction, is the ability to see — by entity, by country of supply, by warehousing location, by sales channel — where transactions are actually happening, so the question of where an indirect-tax obligation might exist can be answered from the data rather than from memory.

Withholding tax and permanent establishment: risks that hide in ordinary activity

Two further areas tend to surface only once a group has been operating cross-border for a while, and both are easy to miss because they emerge from otherwise ordinary business activity rather than from an obvious event.

Withholding tax on intercompany charges

Intercompany service charges, management fees, and royalty or licence payments between entities in different countries can, depending on the treaty position between the countries involved, raise withholding-tax questions on the paying side. Whether withholding applies, at what rate, and whether relief is available under a specific treaty is a jurisdiction- and treaty-specific question that changes with tax residency, treaty updates, and the nature of the payment — a question for the group's tax advisor on a case-by-case basis, not a general rule that holds across countries.

Permanent-establishment exposure

When staff, decision-making, or substantive business activity in one country persist over time on behalf of an entity based elsewhere, that pattern can create permanent-establishment exposure — meaning the local tax authority may consider that the group has a taxable presence in that country, independent of whether a local entity was ever formally set up. This tends to creep in through ordinary operational decisions: a sales lead working remotely from a second country, a delivery team based where a major client sits, a subsidiary's staff performing functions that look more like the parent's core business than local support. None of this means such arrangements are wrong. It means they deserve periodic review with tax and legal advisors as the group's footprint evolves, rather than being reviewed once, at entity setup, and never again.

Statutory reporting and management reporting: two views that must reconcile

A related and quieter problem shows up in reporting itself. As a group grows, statutory reporting — the local-GAAP, tax-driven view each entity must file in its own jurisdiction — and management reporting — the group's own view of performance, often organised by business line, region, or product rather than by legal entity — tend to diverge. That divergence is normal, and in a mature structure, useful: management reporting should reflect how the business actually thinks about itself, not just how each entity happens to be legally structured.

The risk is not that the two views differ. The risk is that they are built as two disconnected systems, reconciled manually and inconsistently, so that nobody can confidently say why a number in the management P&L differs from the corresponding statutory figure, or whether that difference is intentional, an error, or something that needs explaining to an auditor. A group that treats statutory and management reporting as two outputs of one well-designed data model, rather than as two separate exercises, tends to close faster and defend its numbers more comfortably.

Designing for tax visibility from day one

Everything above points to the same underlying design question, not a compliance checklist. None of it is optional cleanup that can be deferred until the group is "big enough" to justify the investment. The cost of reconstructing entity, jurisdiction, and transaction-type detail retroactively — from a structure that was never designed to hold it — is consistently higher than the cost of designing for it from the outset.

In practice, this means a chart of accounts and dimension structure that carries entity, jurisdiction, and transaction-type as first-class, consistently applied tags across the ERP, not as an afterthought bolted onto a generic setup. Intercompany transactions tagged clearly enough that a transfer-pricing review does not require weeks of forensic reconstruction. Sales and inventory data structured so that an indirect-tax question can be answered by jurisdiction and channel. Cross-border charges visible enough that a withholding-tax or permanent-establishment review is a periodic exercise, not a fire drill. And a reporting model where statutory and management views reconcile by design, not by year-end heroics.

This is precisely where finance architecture earns its keep — and precisely where JPS-iQ's role is deliberately bounded. Tax, within our five core areas of expertise, sits inside Finance: our work is to design and operate the finance systems, chart of accounts, and reporting structures that give a group real visibility into its own entities, transactions, and jurisdictions. We do not replace the client's tax and legal advisors, and we do not give tax advice. What we do is make sure that when your advisors need an answer, the data is already there to give it to them — accurately, and on time.