Country setup and localisation in Business Central

Business Central runs in dozens of countries. Each country has its own statutory and operational requirements — tax structure, VAT/sales tax rules, statutory reports, payment file formats, banking schemes, audit-trail rules, language. Country localisations package the country-specific functionality on top of the base BC; understanding what's localised and where the gaps are is essential before signing on to BC in any given country.

Microsoft's country versions. Microsoft directly publishes localisations for around 20 countries — including United States, Canada, United Kingdom, Germany, France, Italy, Spain, Netherlands, Belgium, Denmark, Sweden, Norway, Finland, Iceland, Australia, New Zealand, Mexico, and several others. Each Microsoft country version includes:

• VAT / sales tax engine configured for the country's rules.
• Statutory reports — VAT returns, intrastat, country-specific aging.
• Payment file formats — SEPA in Europe, ACH in the US, Bacs in the UK, Autogiro in Sweden, etc.
• Bank statement import formats — country-standard formats.
• Document layouts — invoice templates conforming to country statutory requirements.
• Number sequences — sometimes country-specific (e.g. continuous numbering for invoices where statute requires).
• Language translations — country's primary language(s).

Microsoft-published localisations are maintained as part of the base BC, updated with each release wave.

Partner-published localisations. For countries Microsoft doesn't directly support, partner-published country localisations on AppSource fill the gap. Partner localisations exist for many countries including Brazil, India, China, Russia, South Korea, Thailand, Indonesia, Malaysia, Vietnam, Turkey, Saudi Arabia, UAE, Egypt, South Africa, Argentina, Chile, Colombia, Peru, and many more.

Quality varies — large established partner localisations (e.g. for Brazil with its complex tax requirements) are mature and well-maintained; smaller-country localisations may have narrower coverage. Always evaluate the localisation's feature list against statutory requirements before committing.

Real-time invoice reporting. Many countries now mandate real-time or near-real-time transmission of invoice data to tax authorities:

• Spain SII — invoices transmitted within 4 days.
• Italy Fatturazione Elettronica (SDI) — every B2B invoice through the SDI platform.
• Hungary RTIR — invoices reported in real time.
• Mexico CFDI — invoices must be issued by an authorised PAC.
• Brazil NFe — every invoice through SEFAZ.

These requirements are handled by country localisations (Microsoft- or partner-published) and may involve additional integration with country-specific government endpoints.

E-invoicing trends. The EU's VAT in the Digital Age (ViDA) initiative is driving mandatory e-invoicing across member states by ~2030. Watching the regulatory landscape per country is part of operating BC internationally.

Multi-country tenants. A single BC tenant can host multiple companies, each in a different country with its own localisation. The companies share the same tenant, users, extensions, and base configuration, but each company's posting rules, VAT engine, and reports respect its country localisation.

This is the standard pattern for international SMBs — one BC tenant, one company per country, with each company localised. Country-specific extensions (e.g. Brazil Localisation by partner X) install per-tenant and apply to relevant companies.

Common gaps.

• Country with no Microsoft or partner localisation — typically means BC isn't the right answer for that country. Some customers run a generic country localisation and supplement with custom AL extensions for statutory needs — viable for small operations, fragile at scale.
• Country localisation behind on regulatory changes — new tax rules sometimes lag in localisation updates. Stay close to the localisation vendor.
• Conflicting localisations — if multiple country localisations are installed and they conflict, troubleshooting is painful. Install only what's needed.

Operational discipline. When entering a new country:

1. Verify Microsoft or trusted partner localisation exists and is currently maintained.
2. Map statutory requirements against the localisation's feature list.
3. Identify gaps; either accept (small ones), customise (medium), or reconsider BC (large).
4. Pilot before scaling.

Where BC fits less. Very complex regulatory regimes (Brazilian tax with its many layers, French chart-of-accounts statutory requirements at the highest detail) sometimes push customers to country-specialised ERPs alongside or instead of BC. Evaluate per country before committing.