Guides › Operating across borders
AccountingEntity managementCompliance

Statutory reporting for multinationals

A group closes its books once. Every entity inside it still answers to its own jurisdiction — in that country’s accounting standard, language, format and deadline. This guide covers what that obligation actually is, where it breaks at scale, and how to run it as a process rather than a scramble.

The annual cycle, per entity
  1. Close the local booksTrial balance in local GAAP, reconciled, with intercompany agreed.Post year-end
  2. Convert and adjustGAAP adjustments, account mapping and disclosures the group pack does not carry.Adjustment layer
  3. Audit, where requiredThresholds, exemptions and the local auditor’s opinion.If in scope
  4. Approve and fileBoard or shareholder approval, correct language and digital format, before the deadline.Statutory deadline
Last updated18 November 2026
Reading time10 min
Written byHSP Group’s accounting and entity teams
Written forGroup finance and controllership
On this page

On this page

Filing across a growing entity footprint? We run statutory accounting and filings in 100+ countries.

Talk to an expert
Key takeaways
  • Statutory reporting applies at individual legal-entity level. Consolidated group accounts rarely satisfy a local requirement on their own, and a reformatted group P&L is not a compliant local filing.
  • The variable is not just the deadline. Accounting framework, language, currency, digital format, approval process and audit threshold all differ by jurisdiction.
  • The real work is the adjustment layer between group IFRS and local GAAP — intercompany balances, reserves, depreciation, tax treatments and disclosures.
  • Failures cluster. Where one subsidiary misses, several usually have, because the cause is almost always a process gap rather than a local accident.

What statutory reporting actually is

Statutory reporting is the legally required provision of financial information — and increasingly non-financial information — to government authorities and regulators. What exactly is required depends on where the entity sits, what legal form it takes, and what industry it operates in.

The defining characteristic is that the obligation attaches to the legal entity, not to the group. A German subsidiary cannot file the group’s consolidated accounts with the Bundesanzeiger and consider the job done. It files its own financial statements, prepared under German rules, in German, in the prescribed format, by the German deadline.

How it differs from everything else finance produces

ReportPrepared forBasis
Management reportingInternal decision-makersWhatever metrics the group finds useful; no external constraint
Consolidated group accountsThe group’s own shareholders and marketsGroup framework, usually IFRS, covering the group as a whole
Statutory reportsThe regulator in each jurisdictionLocal GAAP, at individual entity level, in the local language and format

The practical gap between the second and third rows is where almost all the cost and risk sits. Intercompany balances, reserves, depreciation methods, tax treatments and required disclosures may all need to be adjusted — and those adjustments are entity-specific, not a single conversion you can apply once across the group.

What an entity may have to file

  • Annual financial statements
  • Corporate income tax returns
  • Corporate governance disclosures
  • Reports required by an industry regulator
  • Workforce, environmental or sustainability information

Not every entity files all of these. Which apply depends on local law, entity type and size, and they change as the entity grows past thresholds it was previously under.

The core statutory package

Subject to local rules and size-based exemptions, the foundation of most local filings is:

  • Income statement — revenue, expenses and the resulting profit or loss for the period.
  • Balance sheet — assets, liabilities and equity at the reporting date.
  • Cash flow statement — movements in cash from operating, investing and financing activity.
  • Notes — accounting policies, significant judgments, material estimates, commitments, related-party matters and anything the headline figures do not explain on their own.
  • Auditor’s report, where local law requires an audit.

Smaller entities frequently qualify for abbreviated disclosures or audit exemption, and dormant entities often face reduced requirements. The thresholds are usually based on some combination of revenue, assets and headcount — and they are assessed per entity, so a group can be well over them while several of its subsidiaries sit comfortably under.

That matters more than it sounds. Entities cross thresholds quietly as they grow, and the year an entity becomes audit-eligible is a year the finance team needs to have planned for in advance, not discovered in month ten.

The adjustment layer between group and local

If there is one thing that distinguishes a group that files cleanly from one that does not, it is how deliberately it handles the conversion from group reporting to local statutory reporting.

The group pack is built for consolidation. It carries group accounting policies, group materiality, and a chart of accounts designed for the group’s own reporting. A local filing needs something different, and the differences are specific:

  • GAAP differences. Revenue recognition, lease treatment, provisions, capitalisation thresholds and depreciation methods frequently differ between the group framework and local GAAP.
  • Account mapping. The local statutory format usually prescribes a layout. Group accounts have to be mapped into it, and that mapping has to be maintained as the chart of accounts evolves.
  • Intercompany. Balances eliminated on consolidation are real, disclosable balances at entity level — and they have to agree with the counterparty entity’s books.
  • Tax treatments. Deferred tax in particular is computed on a different basis locally than in the group pack.
  • Disclosures. Local statements require notes the group pack never produced, often covering related parties, directors’ remuneration, employee numbers and commitments.

Each of those is manageable once. The difficulty is that they recur annually, per entity, and the knowledge of why a given adjustment exists tends to live with whoever made it last year.

Deadlines, formats and digital mandates

The jurisdictional variables are wider than most groups plan for. Running the same process everywhere does not work, because the inputs genuinely differ.

VariableWhat changes between jurisdictions
Accounting frameworkLocal GAAP, IFRS, or a local variant of IFRS with carve-outs
DeadlineMeasured from year end, from approval, or from a fixed calendar date — and extension regimes differ
LanguageOften the local language only, which makes translation part of the process rather than a courtesy
CurrencyFunctional currency may differ from the group’s presentation currency
Digital formatStructured filing such as iXBRL or a national e-filing portal, each with its own tagging rules
ApprovalBoard approval, shareholder approval, or both, with their own notice periods before filing
AuditThresholds, exemptions and whether a local statutory auditor must be appointed

Digital mandates are the fastest-moving of these. Structured filing requirements such as iXBRL tagging, alongside real-time or near-real-time tax reporting, have expanded steadily, and they change what finance has to be able to produce rather than merely when. A process that depends on a spreadsheet and a PDF does not survive the move to structured filing.

Sustainability and workforce disclosure obligations are moving in the same direction and are landing on entities that have never had to report anything but financials.

Adding entities faster than you can file for them?

Tell us how many entities you have and where. We will map the obligations, deadlines and audit thresholds against your current footprint.

Talk to an expert

Where it breaks at scale

One entity in one country is an administrative task. Fifteen entities across twelve countries is a coordination problem, and the failure modes are consistent enough to be predictable.

The handoffs

A statutory filing needs inputs from group finance, local bookkeeping, payroll, HR and tax, and then has to pass through a local accountant and often an auditor. Nobody in that chain owns the whole thing. Where coordination is weak, the symptoms are always the same: missed deadlines, records that disagree between group and local, and remediation that costs several times what the original work would have.

Knowledge that lives in people

The reason an entity makes a particular GAAP adjustment, or why its filing is late every year, is usually undocumented. When the person who knew leaves — or the local firm is changed — the group rediscovers it the hard way.

Entities nobody is watching

Dormant entities, entities held after a disposal, entities created for a transaction that did not complete. They still have filing obligations, often reduced but rarely zero, and they are the ones that produce penalty notices nobody expected.

Growth outrunning the process

Every new entity adds a full annual cycle of obligations. Groups that add entities faster than they add capacity to file for them accumulate a backlog that only becomes visible when something external forces a look — an audit, a refinancing, or diligence before an exit.

That last point is worth stating plainly: statutory non-compliance is usually discovered by a buyer, a lender or an auditor rather than by the group itself. It is a diligence finding, and findings are expensive at exactly the moment you have least leverage.

Building a compliance calendar that holds

The fix is unglamorous and it works. A single, maintained view of every obligation, per entity, per jurisdiction.

What it needs to carry:

  • Every entity, including dormant ones and ones acquired mid-year.
  • Every obligation per entity — statutory accounts, tax return, annual return, governance and regulator filings, with its statutory due date.
  • The prerequisites and their dates, working backwards: local close, GAAP adjustments, audit fieldwork, board or shareholder approval, translation, format conversion.
  • A named owner per obligation, internal or external, with an escalation point.
  • The threshold position for each entity, so the year an audit requirement switches on is foreseen rather than discovered.

Three practices separate the groups that keep this working:

  1. Centralised oversight, local execution. One group-level view of status, with in-country people doing the work. Neither alone is sufficient — pure central control lacks the local knowledge, pure local autonomy produces no visibility.
  2. Standardise what can be standardised. Close timetable, chart of accounts mapping, adjustment documentation and working paper format. Accept that the filing itself cannot be standardised.
  3. Document the adjustments as you make them. Why, not just what. This is the single highest-return habit, because it is what survives staff turnover.

Technology helps once the process exists. It does not substitute for one — a tool pointed at an undefined process produces a faster version of the same confusion.

The mistakes that cost the most

  • Treating the group pack as a filing. A reformatted consolidated P&L is not a compliant local statement, and submitting one produces rejections or, worse, acceptance followed by a problem later.
  • Not tracking threshold crossings. An entity that becomes audit-eligible needs an auditor appointed and fieldwork scheduled, both of which have lead times. Finding out after year end costs a late filing.
  • Forgetting dormant and post-disposal entities. Reduced obligations are not absent obligations, and these are the entities with no one watching them.
  • Leaving adjustments undocumented. The group repeats the analysis every year and gets a different answer whenever the person changes.
  • Letting intercompany disagree. Balances eliminated at group level are disclosable at entity level and have to agree with the counterparty. Disagreements surface in audit, late.
  • Assuming the local accountant has it covered. Local firms generally do what they are instructed to do. If nobody has specified the full obligation list, the gaps are invisible until a deadline passes.
  • Planning around the deadline rather than the approval. Where board or shareholder approval is required before filing, the real deadline is earlier than the statutory one, sometimes by weeks.

How HSP helps

We run statutory accounting and filing as a managed process rather than as a set of local engagements you coordinate yourself.

  • Global statutory accounting. Local GAAP bookkeeping, the adjustment layer between group and local, statutory financial statements and the filing itself.
  • Entity management. The compliance calendar across every entity, registered office and local officers, annual returns and governance filings.
  • Global tax. Corporate income tax returns, VAT and indirect tax, and the local filing position in each jurisdiction.
  • Audit support. Preparation, local auditor coordination and the working papers they will ask for.

One group-level view of status, in-country people doing the work, and documentation that survives whoever happens to be in the seat. Talk to an expert.

Frequently asked questions

What is statutory reporting?

The legally required provision of financial, and sometimes non-financial, information to government authorities or regulators. It applies at individual legal-entity level and follows the rules of the jurisdiction where the entity operates — its accounting standard, language, format and deadline.

How is statutory reporting different from group reporting?

Group consolidated accounts present the corporate group as a whole, usually under IFRS, for the group's own shareholders. Statutory reports are prepared per entity under local GAAP for a local regulator. A reformatted consolidated profit and loss statement is not a compliant local filing — intercompany balances, reserves, depreciation, tax treatments and disclosures may all need adjusting.

Does every entity need a statutory audit?

No. Most jurisdictions set thresholds, commonly based on some combination of revenue, assets and headcount, below which an entity qualifies for audit exemption or abbreviated disclosure. Those thresholds are assessed per entity, so a large group can contain several subsidiaries that are exempt. Entities cross thresholds as they grow, which needs tracking in advance.

Do dormant entities still have to file?

Usually yes, though often with reduced requirements. Dormant entities, entities retained after a disposal, and entities created for transactions that did not complete all tend to retain some filing obligation — and because nobody is actively watching them, they are a common source of unexpected penalty notices.

What is iXBRL and does it apply to us?

It is a structured, machine-readable filing format that tags financial statement data so regulators can process it automatically. A growing number of jurisdictions mandate it or an equivalent national e-filing format. It changes what finance has to be able to produce, not merely when — a process that ends in a spreadsheet and a PDF does not survive the transition.

How do we keep statutory reporting under control as we add entities?

A maintained compliance calendar covering every entity and every obligation, with prerequisites dated backwards from each statutory deadline and a named owner against each line. Centralised oversight with in-country execution, standardised close and mapping, and adjustments documented with the reasoning rather than just the number.

How many entities, and where?

That is usually enough for us to map your obligations, deadlines and audit thresholds, and tell you which entities are currently exposed. We reply within one business day.