Guide · Multi-country ERP
Use one core workflow. Validate every operating country.
A multi-country ERP evaluation should show what the business shares and what each entity needs to handle differently. Use this checklist for Canada, the United States, Australia and EU operations without treating any region as a single compliance configuration.
By the Tellency team · Updated
1. Build the entity and location map
List legal entities, registered countries, transaction currencies, warehouses, user groups, working languages and the systems used today. Separate a physical branch from a distinct legal entity.
Mark the master data that needs to be shared: products, suppliers, customers and units. Agree ownership and duplicate-handling rules before importing records.
2. Run the same transaction across the shortlist
Use an order-to-cash or purchase-to-pay scenario with partial delivery, a discrepancy and a correction. Give every vendor the same inputs and expected outputs.
For manufacturing, add a BOM revision, material shortage, scheduling decision, quality outcome and costing review. For retail, add a return, till reconciliation and stock transfer. Preserve evidence from the demonstration.
3. Maintain a separate local acceptance sheet
Ask the appropriate advisers to list required tax codes, invoice fields, accounting exports, payroll outputs if in scope, and any statutory or electronic submissions. Add the required language and currency presentation.
For each requirement, record the entity, expected output, responsible reviewer, supported configuration or integration and acceptance evidence. Do not infer local filing support from a generic tax or finance screen.
4. Agree operating and data responsibilities
Identify hosting location, administrative access, backups, restore tests, retention, exports and support hours. Confirm the effect of time zones on cutover and incident handling.
Review privacy and contract requirements for the specific deployment with the appropriate specialists. Cloud or self-hosted deployment is an operating choice; neither is a blanket compliance certification.
5. Rehearse the migration and compare full cost
Reconcile sample customer and supplier balances, stock by location, opening journals and document references. Record how incomplete or rejected imports are corrected. Rehearse the cut-off and agree rollback criteria.
Compare subscription, implementation, migration, integrations, training, support and usage charges. Tellency platform pricing starts at $79 USD per user per month; a scoped proposal determines the actual configuration and cost.
Your questions, answered
Should every country have its own website page?
Only where it helps a distinct audience with useful and accurate information. Near-identical country or city pages do not replace a verified implementation or local buyer evidence.
Can we use this for an EU-wide rollout?
Yes as an evaluation checklist. Complete a separate acceptance sheet for each entity and country; the guide does not certify tax, payroll, privacy or electronic-filing coverage.
Evaluate Tellency against your own workflows.
Bring your current systems, user count, and operating requirements. We’ll discuss the fit, migration scope, deployment, and total cost.
Book a personalised demo