Localisation apps, VAT configuration, statutory reporting and electronic documents translated into country/region configuration, Electronic Reporting, Tax Calculation Service and Globalization Studio
How Business Central's country/regional localisation apps, VAT posting setup, statutory reports and electronic document formats translate into D365's country/region configuration layers, Electronic Reporting framework, Tax Calculation Service and Globalization Studio — with an honest treatment of what each product covers and where gaps require ISV or custom development.
What you will be able to do
Inventory every country-specific feature the BC localisation app provides and classify its D365 equivalent
Map BC VAT determination onto D365 sales-tax codes, groups, item groups and the Tax Calculation Service
Explain when Electronic Reporting replaces a BC report layout and when a custom solution is needed
Describe Globalization Studio's role in e-invoicing and regulatory feature management
Identify gaps where D365 country/region coverage does not match BC localisation and plan the remediation
Introduction
Business Central's localisation model is extension-based. Each supported country receives a localisation app — an AL extension that adds country-specific fields, validation rules, tax calculations, statutory reports, e-invoicing formats and regulatory integrations.
The BC localisation model — what it contains
The localisation app also configures default number series, VAT posting groups, and chart-of-accounts templates for new companies in that country.
D365's regulatory delivery model
D365 delivers compliance through multiple channels, each with different update cadences:
Translating BC VAT to D365 sales tax
The Posting Engine chapter covered the structural difference between BC's VAT Posting Setup matrix and D365's multi-object tax model. This section adds the country-specific dimension.
Statutory reporting — from BC reports to Electronic Reporting
BC statutory reports are typically RDLC or Word report layouts driven by data from account schedules, VAT entries, or ledger queries. They are report objects within the BC application.
E-invoicing — from BC extensions to Globalization Studio
Some countries have mature BC e-document extensions (Italy FatturaPA, PEPPOL for Nordic countries). Others rely on ISV solutions or custom development.
Country-coverage gap analysis
The programme should produce a country-specific compliance matrix during the Discover stage:
Planning Optimization and country-specific supply chain
Some BC localisations include supply-chain features with regulatory roots — for example, excise-duty tracking, origin-of-goods certification, or country-specific customs declarations.
Sequencing localisation validation
[!TIP] Contact the local tax authority or filing platform to confirm test-submission availability for e-invoicing. Some platforms have sandbox environments; others accept test submissions only during defined windows. Plan around this constraint.
Knowledge check
Summary
Business Central's localisation is delivered as per-country AL extensions. D365's localisation is delivered through base-application regulatory features, Electronic Reporting configurations, Tax Calculation Service and Globalization Studio. There is no conversion path between the two runtimes.