Opening a subsidiary in Frankfurt, Madrid or Warsaw is a growth milestone — and, from day one, the trigger for a silent IT crisis. Your ERP was built for domestic accounting standards, local VAT rates, and national payroll rules. It knows nothing of Germany’s GoBD archiving requirements, Spain’s FacturaE mandate, or Poland’s KSeF e-invoicing platform. The typical result: months of manual configuration, duplicate data records, and group consolidation done by hand in a spreadsheet.
This guide is written for CFOs and CIOs at fast-growing SMBs and mid-market companies planning to open two to five subsidiaries in Europe. The goal: identify the six ERP dimensions to validate before you sign the first foreign lease, choose the right architecture, and select a vendor whose international coverage actually holds up.
Why International Expansion Exposes the Limits of Your Current ERP
The Classic Scenario
A 150-person company running a well-configured ERP for its domestic market opens a subsidiary in Germany. First surprise: the system cannot generate a GoBD-compliant archive for accounting records. Second surprise: the payroll module does not know German social insurance contribution rates. Third surprise: consolidating the two entities requires a weekly Excel export and three days of manual rework.
This is the norm, not the exception — and it repeats with every new country.
The Three Most Common Mistakes
Cloning the home instance without localisation. The IT team duplicates the existing environment, translates the labels, and leaves local teams to “figure out” the tax rules. The first tax audit reveals the full cost of that shortcut.
Creating isolated instances without consolidation. Each country runs its own ERP with no data flow back to the group. Group finance has no real-time consolidated view.
Choosing local ERPs without group alignment. The acquired Spanish subsidiary keeps its Holded instance, the new Polish entity adopts a local system. Within two years, the group is running four different platforms with no data coherence.
The Strategic Imperative
An internationalised IT stack built from the first subsidiary costs two to three times less than a forced migration three years later, once each entity has its own data history, processes, and change-resistance. The decision is made upstream, not under pressure.
The 6 ERP Dimensions to Validate Before Opening a Foreign Subsidiary
1. Local Chart of Accounts
The German HGB, the Spanish PGC, and IFRS (required for listed group subsidiaries) are fundamentally different from each other and from any domestic standard. An internationalised ERP must support multiple charts of accounts on a single instance, with automatic mapping to the group reference for consolidation.
Key question to ask your vendor: can I run two legal entities with two separate charts of accounts, separate tax filings, and a consolidated group balance sheet in group GAAP — with no double entry?
2. Payroll and Local HR Compliance
Payroll is the highest-risk dimension. Social contribution rules, payslip formats, and reporting obligations vary radically from country to country. Two options exist:
- Native payroll module: the vendor maintains local payroll compliance (e.g. Sage HRSM for Germany, A3 Innuva for Spain). Advantage: native integration, regulatory updates guaranteed by the vendor.
- Third-party connector: the ERP connects to a local payroll specialist (DATEV in Germany, ADP in the UK or across Europe). Advantage: flexibility; drawback: one more integration point to maintain.
3. VAT and Local E-Invoicing
Every European country is rolling out its own mandatory e-invoicing timeline. In 2026, the picture looks like this:
- Germany: ZUGFeRD 2.3 or XRechnung for B2G invoices, progressive B2B adoption underway
- Spain: FacturaE mandatory for B2G since 2015, B2B extension expected for 2026–2027
- Poland: KSeF mandatory since 1 February 2026 for large companies (2024 turnover above PLN 200M) and since 1 April 2026 for other taxpayers (source EY)
- UK: Making Tax Digital (MTD) programme for VAT fully live; no mandatory e-invoicing yet but digital record-keeping required
Your ERP must handle these formats natively or connect to certified operators. The EU’s ViDA directive, adopted by the Council of the EU on 11 March 2025 (source banqup), will make cross-border digital VAT reporting mandatory from 1 July 2030. Any ERP deployed today must be ViDA-ready within less than four years.
4. Languages and Locales
Two distinct concepts to keep separate:
- Interface translation: menus, buttons, and labels in German, Spanish, or Polish. Most mid-market ERPs cover the main European languages.
- Regulatory locale: date formats (DD.MM.YYYY in Germany vs DD/MM/YYYY in the UK), thousand separators, IBAN formats, postal address structures. These details generate EDI or e-invoicing rejections if the ERP does not handle them correctly.
5. Currencies and Exchange Rates
A Polish subsidiary invoices in PLN, a Swiss entity in CHF, the parent company consolidates in EUR. The ERP must:
- Handle transaction-date rates and average period rates (for consolidated income statements)
- Calculate translation differences automatically at period close
- Manage cross-currency intercompany transactions (a EUR entity recharging a PLN entity)
ERPs without a native multi-currency module delegate this calculation to Excel exports — a major fragility point at significant intercompany volumes.
6. Legal Entities and Intercompany Structure
Intercompany flows (shared services recharges, management fees, intra-group loans) must be tracked, reconciled, and eliminated in consolidation. In practice:
- When the parent entity recharges HR services to the German subsidiary, the ERP should automatically generate the corresponding vendor invoice on the German side
- Intercompany balances must be reconciled and eliminated at period close
- Transfer pricing (intercompany pricing) must be documented for tax authorities in each country
Some ERPs handle this natively. Others require a dedicated consolidation tool such as Tagetik or Lucanet.
Single Instance vs. Multi-Instance: The Defining Choice
Single Instance: Unified Group View
In a single-instance architecture, all group entities share one ERP database with logical data segregation by legal entity.
Advantages: real-time group visibility without reconciliation, licence and administration savings, shared master data (items, suppliers), native consolidation without ETL.
Disadvantages: complex localisation configuration, strong access rights segregation required, upgrades are riskier because they affect all entities simultaneously.
Best suited for: SAP S/4HANA, Microsoft Dynamics 365 Finance & Operations, Oracle Cloud ERP — products architected for multi-entity from the ground up.
Multi-Instance: Local Autonomy
Each country or region runs its own ERP instance. Instances communicate via EDI, API, or ETL.
Advantages: local adaptations without impact on other entities, independent upgrades, risk isolation.
Disadvantages: manual consolidation or additional middleware, master data synchronisation (items, customers, suppliers), higher infrastructure and administration cost.
Best suited for: highly autonomous subsidiaries, acquired entities with an entrenched ERP that would be too costly to migrate immediately, countries with strict data sovereignty regulations.
Hybrid Architecture
A central instance handles the group (consolidation, reporting, shared services); satellite instances cover subsidiaries with highly specific localisations. This is often the trajectory of growing groups: start single-instance for the first countries, then isolate an acquired subsidiary whose ERP is too deeply embedded.
What the Major ERP Suites Offer for International Operations
SAP S/4HANA covers 60 standard country localisations in its Cloud Public Edition at the 2026 release (source SAP / erpresearch.com), with the option to extend to 160+ countries via its localisation configuration tool. GoBD, ZUGFeRD, FacturaE, Polish SAF-T, KSeF: all covered. The reference choice for groups with five or more entities. High cost — reserved for mid-market companies whose revenue justifies the licence investment.
Microsoft Dynamics 365 Finance & Operations covers EU localisations via the Regulatory Configuration Service (RCS), with regulatory updates managed by Microsoft. Coverage is solid across Western Europe; Eastern European localisations (Poland, Czech Republic, Hungary) are available via certified partners. Strong local partner ecosystem across EMEA.
Oracle Cloud ERP offers cloud-native localisations for the EU, the US, and Latin America. Its native financial consolidation solution (Oracle FCCS) makes it a coherent choice for groups requiring robust group reporting. Positioned at mid-to-large market.
Odoo publishes official fiscal localisations for 50+ countries in its documentation (source Odoo docs), supplemented by OCA community modules. Excellent price-to-functionality ratio for an SMB opening two or three European subsidiaries. Limitations to anticipate: community localisation quality varies; complex multi-entity consolidation reaches its limits beyond five entities without custom development.
Sage X3 has native localisations for France, the UK, Spain, Italy, and the US. Particularly well-suited to industrial SMBs. Less relevant for expansion into Asia-Pacific or Eastern Europe.
IFS Cloud is strong in industries with high regulatory constraints (defence, utilities, precision manufacturing). Solid EU localisations, mature multi-entity architecture. Less visible in the SMB segment.
Use Case: A Mid-Market Company Opening Subsidiaries in Germany, Spain, and Poland
Take a 200-person company on Odoo 18 or Sage X3, planning to open three subsidiaries in 24 months. What are the ERP workstreams per country?
Germany: the ERP must generate GoBD-compliant exports (immutable archiving of accounting documents), produce invoices in ZUGFeRD 2.3 or XRechnung format, and integrate ELSTER declarations for tax. On payroll, DATEV is the market standard: if the ERP does not have a native German payroll module, a DATEV connector is essential.
Spain: PGC 2007 chart of accounts, FacturaE for public-sector clients, SII declarations (Suministro Inmediato de Información) for companies above the AEAT revenue threshold. Payroll can rely on A3 Innuva (Wolters Kluwer) as a connector, or on a native module if the vendor offers one.
Poland: KSeF has been live in production since 1 February 2026 for large companies and 1 April 2026 for others. The JPK file (Jednolity Plik Kontrolny, Poland’s SAF-T equivalent) remains mandatory for tax audits. Payroll involves ZUS declarations. Odoo has a community localisation for Poland; Sage X3 has more limited coverage in this market.
Summary: Odoo covers all three countries with variable-quality localisations. Sage X3 is solid for Germany and Spain but weaker in Poland. SAP S/4HANA covers all three perfectly but at a cost that often exceeds a 200-person SMB’s budget. Dynamics 365 F&O is a credible alternative if the company is already in the Microsoft ecosystem.
A Typical 12-to-18-Month Roadmap for International Deployment
Months 0–2 — Audit and architecture decision: audit of the existing ERP (localisation coverage, multi-entity capacity, multi-currency handling), mapping of regulatory obligations in each target country, single-instance vs. multi-instance decision, vendor selection or confirmation.
Months 2–5 — Country 1 configuration: local chart of accounts, VAT and e-invoicing setup, payroll module or third-party connector, local team training, intercompany testing with the parent entity.
Months 5–8 — Country 1 go-live: historical data migration (opening balance), first local accounting period close, intercompany flow validation, group consolidation testing.
Months 8–12 — Countries 2 and 3 in parallel: Country 1 configuration accelerates subsequent work (shared master data, tested processes, trained teams). Timelines typically shrink by 30–40% on follow-on deployments.
Months 12–18 — Group optimisation: unified consolidated reporting, automated intercompany reconciliation, ViDA preparation (mapping flows for the mandatory cross-border digital VAT reporting effective 1 July 2030).
8 Questions to Ask Your ERP Vendor Before Signing for International Deployment
- How many country localisations are included in the standard offer vs. as paid options? What is the cost of an additional localisation?
- Does your payroll module natively cover Germany, Spain, and Poland? If not, what is your recommended payroll partner and how mature is the connector?
- Do you natively support ZUGFeRD, KSeF, FacturaE, and the ViDA roadmap to 2030?
- How do you handle transfer pricing and intercompany eliminations? Native or via a third-party tool?
- What is your localisation update latency when regulatory changes occur? (Example: Polish KSeF was delayed twice before going live — how long after official publication was your localisation operational?)
- Do you offer a demo instance with three legal entities configured across three different countries?
- Who are your certified partners in each target country, and how deep is their local presence?
- What is your ViDA roadmap to cover mandatory cross-border digital VAT reporting from 1 July 2030?
A Note on Non-EU Expansion
Opening a subsidiary in Morocco, Canada, or Singapore adds further complexity: personal data transfers (GDPR adequacy or standard contractual clauses), local privacy equivalents (PIPEDA in Canada, PDPA in Thailand), customs regulations. This scope falls outside this article, but it warrants dedicated analysis as soon as target markets extend beyond the EU.
To go deeper on two key dimensions covered in this guide: our article on multi-site, multi-entity ERP: consolidation, intercompany flows and multi-currency in 2026 covers the technical mechanics of group consolidation and intercompany elimination. Our guide on international multi-country payroll and ERP: 7 pitfalls to avoid addresses the most common errors when managing payroll across borders during an international expansion.
