RoundLedger
Back to insights

Multi-jurisdiction reporting: the operating playbook

Coordinating accounting books, tax filings, and statutory reporting across multiple countries from one operator.

Visakh Sethumadhavan March 25, 2026 5 min read

Companies with entities in multiple countries face three parallel reporting tracks: management books in a single group format, statutory books in each jurisdiction's required format, and tax filings under each jurisdiction's rules. The three rarely align by default. Coordinating them takes operating discipline.

The three tracks

1. Management books

Run in the group's chosen accounting framework — usually US GAAP or IFRS. Used for internal reporting, board materials, fundraising, and management of the business.

2. Statutory books

Each jurisdiction has its own statutory accounting requirements. India, for example, requires Schedule III format under Companies Act, 2013. UK requires FRS 102 for medium-sized entities. These get filed locally and are visible to local regulators.

3. Tax filings

Each jurisdiction has its own tax rules, often distinct from the statutory accounting framework. Differences between book income and tax income (depreciation, accruals, provisions) create deferred tax and require schedule maintenance.

The coordination model

Run one set of underlying transactions per entity. From those transactions, derive the management view (via group COA), the statutory view (via local-format mapping), and the tax view (via book-to-tax reconciliation). Each view sits on top of the same source — different lenses, same underlying truth.

Companies that try to maintain three separate sets of books end up with three sets of errors. Companies that maintain one underlying source and three lenses end up with one error surface and a defensible audit trail.

Want this kind of operating discipline on your books?

We run crypto subledger implementations, global close, and India compliance day-to-day. If anything here fits a problem you have, let's talk.