Multi-Country Accounting: Chart Mapping, Intercompany and Coordinated Close (2026)

You operate a French OpCo, a Spanish subsidiary, perhaps a German GmbH, with a Dutch entity in the works. The legal stack is set. But behind it, the group's accounting is a patchwork: Pennylane in France, FacturaScripts in Spain, DATEV in Germany, monthly Excel exports for consolidation. Numbers don't reconcile. Year-end close takes 4 months.

This topic is rarely treated head-on: it's usually addressed either upstream (consolidation and IFRS, see our dedicated article) or downstream (currencies and conversion, see multi-currency accounting). This article covers the missing operational layer: how to set up coherent multi-country accounting and industrialise the group close.

Audience: CFO, controller, or owner of an SME or scale-up steering a group with 2 to 6 entities across countries.

Operational multi-country accounting rests on 4 pillars:

1. A single group chart of accounts, mapped to each local chart;
2. A rigorous intercompany framework (who bills whom, on which account, in which currency);
3. A coordinated close calendar with local and group deadlines;
4. Tooling capable of multi-entity processing (single ERP or a consolidation layer above local tools).

The goal is not accounting perfection. It is reliable consolidated accounts every month within 15 days, and timely statutory filings.

As long as you have a single French entity, the PCG is enough. As soon as a foreign subsidiary appears, several frictions arise simultaneously:

• Different chart of accounts: German SKR03/SKR04, Spanish PGC, Italian Codice Civile do not share the same nomenclature.
• Different currency (unless a euro-zone subsidiary) ⇒ conversion differences to manage (see multi-currency accounting).
• Different fiscal calendars: calendar year in France, possible offset in Germany, filing deadlines that don't align.
• Different tools: local adoption of national software (DATEV, Sage 50, Cegid Loop, Pennylane) for lack of a satisfactory global option.
• Different teams: local outsourced bookkeeping, sometimes only in the local language.

Without a group framework, each subsidiary produces accounts under its local rules. Consolidation becomes a high-friction monthly Excel exercise.

The group chart of accounts is a single repository shared by all entities. It does not replace local charts; it sits on top of them and is used to produce consolidated accounts.

Recommended granularity#

• Too granular (5 digits and beyond, mirroring the full PCG): unmanageable at group level, redundant with local charts.
• Too broad (3-4 lines per category): impossible to analyse cost structure.
• Right size: 60 to 150 group accounts max, organised in classes 1 to 7 PCG-style or by function (revenue, COGS, OpEx, capex, financial, tax).

Three mandatory sub-repositories#

1. Counterparty accounts: segment intra-group vs external customers/suppliers from the chart itself (e.g. accounts 411A external / 411B intra-group).
2. Cost centres: by legal entity, by product/service, by geography.
3. Statutory equity and reserves accounts: differentiated by entity to ease equity consolidation.

Our recommendation: take a PCG-compatible repository as the group base (1-7 logic), then add accounts for items that do not exist in PCG (e.g. deferred revenue in SaaS).

Each entity keeps its statutory accounting in the local chart (PCG in France, SKR03 or SKR04 in Germany, PGC in Spain). Mapping is the lookup table that pushes each local entry up to the group account.

Mapping best practices:

• Keep the table in a central repository (shared Google Sheet, or consolidation tool such as Pennylane Holding, Lucanet, Tagetik).
• Audit the mapping each quarter: new local accounts created ⇒ assign to group without delay.
• Document exceptions (account with no direct equivalent, IFRS treatment differing from local).
• Version: any mapping change ⇒ document for retrocompatibility.

Intra-group transactions are the leading source of consolidation gaps. Three operational principles:

Principle 1: absolute symmetry#

Every intra-group invoice must be booked symmetrically in the issuing entity and the receiving entity, in the same month, for the same amount. This requires:

• A formalised intra-group invoicing procedure (distinct numbering, dual validation);
• A current intra-group contracts repository (who bills what, at which price — see our transfer pricing documentation kit);
• An identical cut-off calendar across entities.

Principle 2: neutral currency#

If the French OpCo invoices the German GmbH in EUR, both are euro-zone: no gap. If the French OpCo invoices the US subsidiary in USD, you automatically generate FX differences as long as the invoice is open. Recommendation: invoice in the recipient's currency to minimise friction, and use a dedicated intercompany reconciliation account.

Principle 3: dedicated reconciliation account#

Set up a dedicated intra-group payable/receivable account per counterparty entity. Example:

• Account 451 - Intra-group current account (PCG)
• Subdivided into 451100 (France OpCo ↔ GmbH); 451200 (France OpCo ↔ UK subsidiary), etc.

Every month, reconcile the cross balances: balance 451100 in the French OpCo must be the opposite of the mirror in the GmbH. Any gap above a defined threshold ⇒ a reconciliation ticket to clear before consolidation.

Target: monthly close by D+11 for an SME with 2-4 subsidiaries. The standard reached by properly tooled groups. A close at D+25 or beyond signals a framing gap.

Note: this calendar assumes preparation tasks (paid-leave provision, accruals, prepayments, subscriptions) are automated or kept up to date continuously, not rebuilt at month-end.

Two approaches dominate:

Approach A: single ERP (NetSuite, SAP, Microsoft Dynamics)#

Pros:

• A single configured chart of accounts;
• Native multi-entity multi-currency;
• Instant consolidated reporting.

Cons:

• High cost (typically €50-200k/year minimum for an SME);
• French compliance to configure (FEC, see our NetSuite & French compliance article);
• Long implementation (6-18 months).

Relevant from ~ €30M consolidated revenue or 4+ subsidiaries.

Approach B: local stack + consolidation platform#

Pros:

• Local tools familiar to teams (Pennylane FR, DATEV DE, FacturaScripts ES);
• Native local tax compliance;
• Lower cost.

Cons:

• Mapping and imports to maintain;
• Potentially longer close;
• Dependence on a consolidation layer (Pennylane Holding, Lucanet, Sage Intacct, Tagetik, or a structured spreadsheet).

Relevant for SMEs up to ~ €30M revenue, or as a stepping stone to a single ERP.

Our recommendation for a scaling SME: start with local stack + lightweight consolidation (Pennylane, Lucanet), and switch to a single ERP only when operational complexity demands it.

Our conviction is that 80 % of multi-country friction comes from the intercompany framework, not the tools. We regularly see groups equipped with high-end ERPs that still spend a week per month reconciling intercos because no one set the upstream rule: who bills whom, when, in which currency, on which account.

Before investing in a group ERP, formalise:

1. The intercompany matrix (who bills whom, for what, at which price, in which currency);
2. The group chart of accounts and its local mapping;
3. The monthly close calendar;
4. The pivot role of a group coordinator (often an outsourced CFO for SMEs — see our outsourced CFO service).

Once these foundations are laid, tooling becomes an efficiency choice, not a structuring concern.

The most underestimated risk is not an accounting error. It is the statutory filing delay. A French SME must file annual accounts within 6 months of year-end. A German subsidiary has a different calendar, ditto Spain. Without group synchronisation, you risk:

• Late filing of annual accounts (civil and criminal penalties possible);
• Consolidation closing in month 8 or 9, making it impossible to engage with banks, investors, and statutory auditors;
• Costly retroactive realignment of fiscal years.

For an SME mid-fundraise, a 3-month delay on group annual accounts costs several thousand euros in additional audit fees and can push the signing date.

• ☐ Group chart granularity (60 to 150 accounts recommended);
• ☐ Consolidation tool (structured Excel, Pennylane Holding, Lucanet, Tagetik);
• ☐ Target monthly close calendar (D+11 vs D+15 vs D+25);
• ☐ Intercompany framework signed by each entity;
• ☐ Group reference standard (PCG, IFRS — see why adopt IFRS);
• ☐ Group coordinator (internal or outsourced);
• ☐ Annual budget tooling + group resources.

1. e-Reporting and e-Invoicing: France is rolling out B2B e-invoicing (see our e-invoicing service). Cross-border intra-group flows are partly affected.
2. DAC 7: stronger duties for digital platforms.
3. CESOP (cross-border payments): quarterly reporting of cross-border payments > 25 per beneficiary per quarter.
4. IFRS evolutions: new IFRS 18 (presentation of financial statements) effective from 2027.
5. Audit reinforcement: statutory auditors give increased attention to intercompany reconciliations.