# ERP localization rollout: a practical framework

Rolling an ERP out to a new country means meeting local tax, invoicing, reporting and accounting rules from the first day of trading. This guide sets out a vendor-neutral way to choose how each country is localized, decide which countries need the most attention, and collect the facts needed before design starts. It applies to any ERP.

## 1. Three ways to localize a country

| Approach | What it means | Fits best when | Watch out for |
|---|---|---|---|
| **Native** | Use the localization features the ERP vendor ships for that country (tax codes, reports, e-documents). | The vendor covers the country's current mandates and transaction volumes are moderate. | Coverage gaps (for example a report or e-invoicing channel that is not supported), and the timing of vendor updates when rules change. |
| **Native + add-on** | Keep the vendor's base localization and add a certified extension or connector for specific requirements, often e-invoicing, SAF-T or bank formats. | A clearance or real-time mandate applies, or native output needs heavy manual work. | Extra integration points to test and monitor; clarify who owns updates when the authority changes a schema. |
| **Native + local partner** | Run core accounting in the ERP and have a local accounting or tax firm prepare and file statutory returns from ERP data. | Small entities, low volumes, or countries with complex local filings that are cheaper to outsource than to automate. | Data hand-offs and close timelines; real-time mandates (e-invoicing, transaction reporting) still have to be met by the system, not the filer. |

Many groups mix the approaches by country. Revisit the choice whenever a country announces a new mandate.

## 2. Risk vs effort decision matrix

Score each country on two axes, for example from 1 to 5.

- **Compliance risk:** real-time or clearance obligations, penalty regime, audit-file requirements, how often the rules change, and how material the entity is. 
- **Implementation effort:** gaps in native coverage, number of filings, integrations needed, language and chart-of-accounts specifics, and internal know-how.

|  | Low effort | High effort |
|---|---|---|
| High risk | **Do first.** Configure native features early and test filings against the authority's validation. | **Plan carefully.** Start early, consider an add-on, pilot with real data and set up monitoring of rule changes. |
| Low risk | **Standardize.** Use native features and a template rollout. | **Simplify or outsource.** A local partner for filings may beat building automation. |

Re-score at least yearly, and whenever a mandate date is published. The country pages track [e-invoicing](https://erplocalization.com/e-invoicing/), [VAT reporting](https://erplocalization.com/vat-reporting/) and [SAF-T](https://erplocalization.com/saf-t/) requirements.

## 3. E-invoicing in the rollout plan

E-invoicing mandates usually carry the hardest deadlines because invoices cannot be issued without them. Identify the model each country uses (see [e-invoicing models explained](https://erplocalization.com/guides/e-invoicing-models/)), the go-live dates for issuing and receiving, the required format, and whether a certified provider or access point is needed.

## 4. Discovery checklist

**Entities and scope**

- Legal entities, VAT registrations and fixed establishments per country
- Go-live date per entity and any statutory year-end constraints
- Transaction types: B2B, B2G, B2C, intra-EU, exports, imports
- Monthly invoice volumes, inbound and outbound

**Tax and invoicing**

- VAT return frequency and deadlines; other periodic returns (EC sales lists, Intrastat)
- E-invoicing or real-time reporting mandates and dates
- SAF-T or audit-file obligations, periodic or on request
- Invoice content, numbering and language rules
- Withholding taxes and local surcharges

**Accounting and reporting**

- Local chart of accounts or mapping requirements
- Local GAAP vs group GAAP, statutory financial statements and filing format
- Fixed-asset depreciation rules
- Record retention period and archiving format

**Systems and operations**

- ERP edition and localizations available for the country
- Integrations: banks and payment formats, e-invoicing network, payroll, tax engine
- Who prepares and files each return; access to tax portals and digital certificates
- Testing approach against authority validators or sandboxes
- Owner for monitoring rule changes after go-live

## 5. After go-live

- Reconcile ERP output with filed returns for the first periods.
- Track authority schema and rate changes; plan a regression test for each update.
- Keep evidence of submissions and acknowledgements for audits.

This guide is general information, not tax or legal advice. Confirm requirements with the tax authority and a qualified adviser.

---
Canonical: https://erplocalization.com/guides/erp-localization-rollout/ · Last updated: 2026-10-16 · Informational only; not tax, legal or implementation advice. Featured placements are paid or promotional and do not affect the compliance data. Data: CC BY-NC 4.0 (commercial use needs a licence: https://erplocalization.com/data-licence/), attribution "ERP Localization (erplocalization.com)".