Multi-language setup in Business Central

For organisations operating across countries, Business Central's multi-language capability lets users work in their preferred language and lets customer-facing documents (invoices, quotes, statements) print in the customer's language. The mechanics are good for the common cases; the limits matter for international operations.

User language. Each Business Central user has a language code in their profile — English (US), English (UK), Swedish, German, French, Spanish, and many others. The user's language drives:

• UI labels — every field name, action, menu item.
• Field validation messages and errors.
• Help text and tooltips.
• Date and number formatting per locale.
• Built-in report labels.

Switching user language is one click in the profile; UI re-renders instantly.

Supported languages. Microsoft ships UI translations for ~40 languages out of the box. Many extensions add their own translations as part of the .app package. Country localisations include both functional logic and language translations relevant to that country.

Customer-facing language. Each customer carries a Language Code that drives the language of documents sent to that customer:

• Posted invoice rendered in the customer's language.
• Reminder text in the customer's language.
• Statement layout in the customer's language.
• Email body templates in the customer's language.

This is where multi-language shines. A French customer receives French invoices; a German customer receives German invoices — automatically, from the same posted transaction.

Translations. Customer-facing translations come from:

• Microsoft's translations — for standard fields, labels, and report content shipped by Microsoft.
• Extension translations — third-party AppSource apps provide their own translation files for content they introduce.
• Customer-tenant translations — the tenant administrator can add or override translations for specific fields and reports. The Field Captions and Page Captions translation features let you tune what shows on customer-facing documents.

Document layouts. Layout templates can be per-language. A sales invoice has separate Word layouts for English, Swedish, German. The customer's language code selects the layout at posting; the right design renders without manual selection. The translations of headers, labels, and boilerplate text are in the document layout itself.

Item / customer / vendor descriptions in multiple languages. A separate concept: an item description can have language-specific descriptions stored alongside the base description. When a sales invoice prints for a customer with French language code, the French item description appears in the document. Configure via the Translations page on the item card.

Limits.

• UI translations are bound to what Microsoft ships. New languages or rare languages may not have full coverage; partner localisation work fills gaps.
• Translation tables for custom text — if an extension adds new tables, those need their own translation files for multi-language support. Customer-tenant text overrides are possible but require admin work.
• Right-to-left languages (Arabic, Hebrew) — supported but the document layouts and printing logic may need extra attention.
• Character-set handling for Asian languages — generally fine but PDF generation and email rendering need verification.

Country localisations and language. Each country localisation includes both functional logic (VAT, statutory reporting) and language. Installing a country localisation typically enables the country's primary language by default for users assigned to that country.

Tenant-level vs company-level vs user-level.

• Tenant-level — installed language packs available across the tenant.
• Company-level — the company can have a default language for documents and reports.
• User-level — each user picks their preferred working language.

The three layers can differ; the user's UI language doesn't change the customer-facing document language.

Operational discipline. Pilot multi-language with one international customer per language before broad rollout. Reading a foreign-language invoice and confirming all fields make sense is the only real test. Audit translations periodically; word choice ages.

Where it stops. Sophisticated translation management (TMS) for marketing content across many languages doesn't belong in BC; use a dedicated TMS integrated with BC for the data hand-off.