Business Central localization: choosing and setting up country versions

What a Business Central localization adds to the base product

Every environment starts from a shared base application. A localization sits on top of it. It adds what the law demands. That means tax rules, payment file formats and the reports an authority expects. The United States version, for example, has sales tax by jurisdiction, check printing and vendor tax form reporting.

Microsoft builds some localizations itself. For many others, a partner adds the local functions as an app. We confirm which model applies to each place you operate before we create any environment. A wrong answer here is hard to fix later.

One Business Central localization per environment, not per company

The country version belongs to the environment. Every company inside that environment shares it. So a United States parent with a Canadian and a Mexican subsidiary needs three environments, one per version. Even so, all three can live in one tenant, and one sign-in reaches them.

That layout shapes what follows. It decides where extensions go and how the group consolidates. So we draw the entity map first. We agree which entities can share an environment. Only then do we create anything. One page also gives finance, IT and auditors the same picture.

Setting up local tax and reporting features

Once the environment exists, the local features still need setup. In a North American company, that means tax areas, tax jurisdictions and tax groups. For Canada, it also means GST and provincial tax. In a VAT version, it means VAT posting groups, the VAT statement and the return periods.

We set these up against real transactions, not a checklist. First, we post a handful of actual sales and purchase documents from each entity in a sandbox. Then we compare the tax entries and reports with what your accountants filed for the same documents. We explain any gap before go-live.

Extensions across more than one localization

An extension built for one country version can fail to install on another, because local fields and objects differ. So groups that want one shared custom feature need it built on the international base. Small companion apps then hold the local differences. That split keeps the shared part easy to install and update everywhere.

The same check applies to any app you buy from AppSource apps. Each listing names the markets it supports. A US app may not exist for your subsidiary's version. So we confirm availability for each environment before it joins the design.

Localization mistakes that are costly to undo

The costliest mistake is creating a production environment in the wrong version and posting into it. There is no conversion. You must set up the company again in a new environment. Then you move the data across with configuration packages. That is a small migration of its own.

A quieter mistake is to assume a local version settles every compliance question. Rules change. Some duties, such as filing in many US states, suit a tax service that connects to Business Central. So we say plainly where standard features stop and an add-on is the sounder choice.

Business Central localization questions

Can the Business Central localization of an environment be changed later?

No. The country version is fixed when you create the environment. To move a company to a different version, you create a new environment. Then you set the company up again. After that, you migrate master data and open balances into it. That is why we confirm the version for every entity before anything is built.

Is localization the same as translating the screen?

No. Language controls the captions a user reads, and each person can change it at any time. Localization controls tax rules, statutory reports and bank formats. It applies to the whole environment. You pick the two on their own. So a French-speaking user can work in a United States environment with no trouble.

What if Microsoft does not publish a version for our subsidiary's country?

Then the subsidiary normally runs the international version, with a partner-built local app on top. We help you find the apps on offer. Then we check what each one covers and test it against your filing needs. As your Business Central localization consultant, we flag any gap before you commit.

Can companies in different localizations trade with each other?

Yes. Intercompany postings can cross environments. Financial consolidation can then bring the results together in the parent's books. However, the setup takes more planning than inside one environment. That is why we design it up front, with one entity map that finance, IT and auditors can all read.

Does the on-premises product use the same localizations?

The on-premises product also comes in country versions, with the same kind of local features. Availability and delivery differ in places. So we confirm the facts for your version before you plan an install or a move to the cloud. Either way, Business Central localization stays a decision to make early.

Services that go with localization

Once you settle the country version, the work moves to entities, currencies and tax. These pages go deeper into each of those pieces, and into translating screens and documents. Read them next if your Business Central localization plan touches more than one country, so each entity gets the right setup from the start. For the product detail, see Microsoft Learn: local functionality in Business Central.