Choose a local ERP, a local ledger or a global localization
A country expansion does not always require the same system arrangement as the parent company. The useful question is which system can operate the business and produce its required records with a maintainable division of responsibility.
Use this guide when selecting a system for a subsidiary or reviewing a country that relies on manual accounting work. The result is a documented choice with evidence gaps, interface responsibilities and acceptance conditions. The decision method is editorial guidance, not a national accounting requirement.
Describe the operation before comparing products
Record the legal entity, registrations, industry, transaction volume and people who will operate the system. Identify the documents that must be issued locally and the reports the group needs. Include production, inventory, projects or service delivery where relevant.
Separate an operational requirement from a statutory output. A warehouse team needs stock movements and reservations throughout the day. An accountant may need a particular annual file only once a year. Frequency alone does not determine importance, but the two requirements can have different system owners.
A local accounting product and an operational ERP are not interchangeable. For example, Monitor describes manufacturing, inventory and integrated financial functions. That establishes a different product category from a bookkeeping-only offering, without proving every country's tax support. Monitor product scope.
Compare three arrangements
| Arrangement | Suitable starting point | Principal question |
|---|---|---|
| Global ERP with country functionality | Group processes fit the operation and the country package has adequate evidence | Who maintains the local module, provider connection and reports? |
| Local operational ERP | Local industry processes or service support are better served by a country or regional product | Can the system supply complete group reporting and controlled data exports? |
| Global operations with a local statutory ledger | Operations fit the global system but local accounting or filing needs another application | Can documents, balances and corrections reconcile across the boundary? |
These arrangements describe responsibility, not a ranking. A local product may be a global vendor's country edition. A regional ERP may have separate national packages. Headquarters, language availability and a domestic reseller do not establish a product's tax functionality.
Assign the authoritative record
For each record, name the system that creates it and the people allowed to correct it. Cover legal invoices, customer balances, supplier liabilities, inventory value, fixed assets, payroll journals and statutory adjustments.
If the operational ERP creates a legal invoice, a local accounting import must not create another legal invoice for the same sale. If the local system owns invoicing, the global system needs its identifiers and states. A reconciliation is easier when this decision is made before interface design.
Name the source of the entity's consolidation package. Importing both the global mirror and the local trial balance as separate entity results duplicates the entity. Ordinary intercompany elimination is not a remedy for that mistake.
Compare evidence at product level
For each shortlisted product, record the edition, release, country package and external services. Describe what is documented for sending, receiving, reporting and correction separately. An exported XML file and a filed return are different results.
The Serbian PANTHEON offering illustrates a dependency worth recording: its DMS page identifies services and SEF access prerequisites. The ERP name alone does not describe the complete contracted route. PANTHEON DMS.
Do not remove a candidate merely because a feature is not yet verified. Record the missing evidence and whether it is essential to the decision. A vendor response that names an exact module and demonstrates the required outcome is more useful than an unsupported country-coverage tick.
Work through a practical comparison
Consider a hypothetical manufacturer opening a small sales subsidiary. The parent system already manages production and stock. The subsidiary needs local invoices, accounts, tax outputs and group reporting, but no separate factory planning.
First assess the global system's country package. If it produces the required documents and reports with supported services, adding another ledger may create unnecessary reconciliation work. If a local filing output is missing, compare a reporting service or local ledger with replacing the operational system.
Now change the scenario: the new subsidiary has a factory with local scheduling and service requirements that the parent template cannot support. A local operational ERP becomes a stronger candidate. The decision still depends on its accounting evidence, group interfaces and support arrangements. The country alone did not determine the answer; the operating model did.
Make costs comparable
Ask each supplier to describe the same boundary: software, country modules, transmission services, implementation, upgrades, support and historical access. Include the internal effort of operating an interface and resolving exceptions. Do not compare a bookkeeping subscription with a complete ERP implementation as if they cover the same work.
Record assumptions without inventing a precise five-year total. A provider may price documents or entities separately. An adviser may prepare returns outside the software. An export may require a higher edition. Those differences can change the result more than the headline licence price.
Complete the decision record
| Decision field | Record |
|---|---|
| Entity and operating scope | Legal entity, registrations, activities and users |
| Chosen arrangement | Global localization, local operations or local ledger |
| Authoritative records | System and owner for invoices, balances and adjustments |
| Required outputs | Country obligation, format, period and recipient |
| Product evidence | Edition, release, module, service and source |
| Interfaces | Data, frequency, identifiers and correction route |
| Remaining evidence | Unresolved capability and decision owner |
| Acceptance conditions | Demonstration, reconciliation and historical retrieval |
| Reconsideration trigger | New activity, failed support, mandate or product retirement |
Approve the arrangement only after the material gaps have a documented resolution. Preserve the record so the next country team can see why this configuration was chosen.
Related: Read an ERP country-support claim, parallel books, and local-ledger operation.
Worksheet: Choose a local ERP, a local ledger or a global localization worksheet
Copy this worksheet for each case. It records decisions and evidence; it does not determine the tax or legal treatment.
Show the worksheet
Copy this worksheet for each country or entity decision.
Scope
- Legal entity:
- Country:
- Period covered:
Decisions
- Arrangement chosen:
- System owning legal invoices:
- System owning statutory reports:
- Interface owner:
Evidence to retain
- ☐ Product/edition documented
- ☐ Filing or export sample reviewed
- ☐ Acceptance criteria signed
Related on this site
- Country pages: key facts with sources
- E-invoicing matrix: country × ERP support
- All guides
Vendor documentation is cited only as an example of the level of evidence to ask for; it is not a recommendation or a ranking. This guide is general information, not tax or legal advice. Checked 2026-10-19.
Related: Glossary – abbreviations and terms used in these guides (SAF-T, Peppol, CTC, EN 16931, IFRS and more).
Page last updated: · Markdown version