Requirements · ERP
ERP requirements for multi-entity and multi-country finance
Last updated 25 October 2026 · 2 sources listed · Reading time about 3 minutes
Short answer
Multi-entity finance needs more than a chart of accounts. Specify intercompany transactions and eliminations, multiple currencies and revaluation, parallel ledgers for different accounting frameworks, local tax and statutory reporting, entity-level security, and consolidation. Define each in terms of a close process you must complete, and verify that local statutory needs are covered by the product or by a supported localization.
Who this is for: A controller or finance systems lead specifying what an ERP must do for several legal entities across countries.
What to evaluate
Intercompany handling
Transactions between entities must be matched and eliminated on consolidation. Weak support causes manual spreadsheets at close.
How to check: Run an intercompany sale with a currency difference and watch posting, matching and elimination.
Multi-currency and revaluation
Transaction, functional and reporting currencies behave differently, and revaluation creates entries that must be traceable.
How to check: Review a sample revaluation run and the accounts it posts to.
Parallel ledgers
Entities may report under different accounting frameworks, requiring adjusting entries for each.
How to check: Ask how one transaction posts to more than one ledger and how adjustments are tracked.
Local statutory and tax support
Each country has its own invoicing rules, tax filings and chart requirements.
How to check: Ask which countries are covered by the vendor and which depend on third-party localizations.
Entity-level access control
Users should see only the entities they are responsible for, with segregation of duties.
How to check: Create a role limited to one entity and test restricted views and approvals.
Consolidation and reporting
Group reporting must reconcile to the entity ledgers and support audit review.
How to check: Trace a consolidated figure down to source entries.
Comparison
| Approach | Good when | Watch out for |
|---|---|---|
| Built-in ERP consolidation | Entities share one platform and chart structure | Limited flexibility for unusual ownership structures |
| Dedicated consolidation tool | Group reporting is complex or involves several ERPs | Integration and mapping overhead |
| Spreadsheet-based consolidation | Few entities and simple structures | Error risk, weak audit trail, key-person dependency |
| Shared service center on one instance | Standardized processes across entities | Needs strong governance for local variation |
| Separate ERP per country with a group layer | Local autonomy is essential | Duplicated cost and inconsistent processes |
Decision worksheet
Rate up to three options against this guide’s own criteria. It runs in your browser and saves only on this device. It is a thinking aid, not a recommendation.
1. Have you checked each criterion?
0 of 6 criteria checked.
2. Compare options (0 = fails or unknown, 3 = meets it well)
| Criterion | |||
|---|---|---|---|
| Intercompany handling | |||
| Multi-currency and revaluation | |||
| Parallel ledgers | |||
| Local statutory and tax support | |||
| Entity-level access control | |||
| Consolidation and reporting | |||
| Total (max 18) | 0 | 0 | 0 |
Questions to ask before you commit
- Which countries have supported localizations, and who maintains them?
- How are intercompany balances matched, and what happens to differences?
- How does the product support more than one accounting framework at once?
- How are exchange rates loaded, and can rates be locked after close?
- Which statutory reports are delivered out of the box?
- How does the audit trail show who changed what, and for which entity?
- Can we segregate duties by entity and by process step?
- How are chart of accounts changes managed across entities?
Typical trade-offs
One shared chart of accounts versus local charts with mapping
- Upside
- A shared chart simplifies consolidation.
- Downside
- It may not satisfy local statutory expectations.
Single instance versus multiple instances
- Upside
- A single instance gives consistent processes and easier reporting.
- Downside
- Local requirements may strain a shared configuration.
Centralized close versus local close
- Upside
- Central control improves consistency.
- Downside
- It can slow local responsiveness.
Common mistakes
- Specifying features without describing the close. Write requirements as a month-end sequence of tasks.
- Assuming localization exists for every country. Verify each jurisdiction and the vendor's update commitment.
- Ignoring audit access. Auditors need read access and traceable evidence.
- Designing the chart of accounts last. Decide structure early because everything depends on it.
- Overlooking intercompany policies such as transfer pricing documentation. Involve tax advisers early.
Related questions
How do we document these requirements usefully?
Write them as scenarios tied to a deliverable: for example, complete an intercompany sale between two entities in different currencies and produce the consolidated result. Each scenario lists inputs, expected postings and the report that proves it. Vendors can then demonstrate against the same script, which makes comparison objective.
What about tax and statutory compliance?
Rules vary by country and change over time, so rely on the relevant tax authority and your advisers for requirements, and ask vendors how they track regulatory changes. Establish who delivers updates, how quickly, and whether they are included in the subscription or charged separately.
Is consolidation inside the ERP enough?
For simple structures with one platform it can be. Complex ownership, minority interests or several ERPs often justify a dedicated tool. Judge by how many manual adjustments you make today and how much audit scrutiny the numbers face.
How should access and approvals be designed?
Define roles by process and entity, separate creation from approval for payments and journals, and review permissions regularly. Test with realistic user accounts before go-live, and ensure the audit trail records approvals and changes at each step.
Sources and further reading
These pages were reachable when we last checked. They informed definitions and rules referred to above; they do not endorse this guide. Where rules differ by country, check the authority for your location.
- IFRS Foundation — IFRS Foundation, retrieved 27 October 2026
- Internal Revenue Service — Internal Revenue Service, retrieved 27 October 2026
Related guides
How to choose · ERP
How to choose an ERP for a mid-sized manufacturer
Choose an ERP by testing how it handles your production reality: bills of material, routings, lot or serial tracking, planning logic, costing and shop floor reporting. Demonstrations with scripted scenarios drawn from your own products expose gaps faster than feature lists. Weigh fit to your manufacturing mode, the depth of inventory and costing, the quality of the implementation partner, and how much customization the design will require.
Comparison · ERP
Single-suite ERP versus a best-of-breed application stack
A single-suite ERP offers one data model, one vendor relationship and consistent reporting, but individual modules may be shallower. A best-of-breed stack gives deeper functions in each area at the price of integration work, divided accountability and reconciliation effort. The right balance depends on how unusual your processes are in the areas that create competitive advantage and how much integration capability you can sustain.
Cost factors · ERP
What drives ERP implementation cost and overruns
ERP cost is dominated by effort rather than licenses: scoping, data cleanup and migration, configuration, integration, customization, testing, training and change management. Overruns usually come from unclear scope, poor data, late requirement changes, and underestimated internal staff time. Budget by workload, hold contingency for discovery, and make scope decisions explicitly rather than letting them accrete.
Requirements · Accounting software
Accounting software requirements for multi-currency books and audit readiness
Multi-currency accounting needs a defined base currency, transaction-date exchange rates, revaluation of foreign balances, realized and unrealized gain tracking, and consistent reporting. Audit readiness needs immutable audit logs, period locking, approval workflows, supporting document attachment, and accessible reports reconciling to the ledger. Specify these as testable scenarios and verify the software supports your jurisdiction's reporting framework.
Comparison · HR and payroll software
PEO or outsourced payroll versus in-house payroll software
In-house payroll software gives you control and often a lower unit cost but leaves compliance responsibility and filing oversight with you. Outsourced payroll services run calculations and filings for you, and a professional employer organization goes further by sharing certain employment responsibilities through a co-employment arrangement. The distinction matters legally and varies by country, so confirm what responsibilities actually transfer and which remain yours.
Requirements · HR and payroll software
Payroll software requirements for employees in several jurisdictions
Multi-jurisdiction payroll requires software or services that apply the right tax, social contribution, leave and reporting rules for each location, maintain accurate rate tables, handle currency and statutory payslip formats, and produce the filings each authority expects. Specify coverage per place, update responsibility, audit trails and data protection, and confirm with advisers or regulators because rules vary and change.
How to choose · Business operations
How to choose a point-of-sale system for a shop, cafe or restaurant
Match the system to your workflow first: counter service, table service, appointments or online ordering each stress different features. Then weigh hardware, offline behavior, inventory and reporting depth, integrations with accounting and delivery channels, payment lock-in, support responsiveness and how easily you can export your data. Run a trial during a busy period before committing to a contract.