Localisation

AL runtime chosen in app.json affects DK locale packages, Peppol/OIOUBL, NemHandel gateways, SAF‑T exporters and Danish bank connectors. Inventory extensions, coordinate with ISVs, pin tenants and validate in a sandbox.

19 November 2026

Choosing an AL runtime is no longer only a developer concern — it's an operational decision that can change how Danish localisation and connected services behave in production. The runtime declared in an extension's app.json controls which platform and language features the extension can use, and a mismatch between extension runtime and server runtime can block deployment or change runtime behaviour.

Why the AL runtime matters

The AL runtime is specified in app.json, for example "runtime": "18.0". An extension requires a Business Central server that supports the same or a later runtime version; the compiler itself does not detect the target server runtime. If you don't set runtime explicitly, the AL compiler defaults to the first runtime version of its current major release. Microsoft documents recent runtimes: 16.0 (shipped with Business Central 2025 release wave 2 / platform 27.0), 17.0 (2026 wave 1 / 28.0) and 18.0 (2026 wave 2 / 29.0). The guidance is to set the runtime to the minimum version that supports the features you need and to ensure all target servers support that runtime.

The practical implications: if an ISV or localisation package raises its runtime requirement, your production tenant must run a server that meets that runtime. Conversely, if you raise your extension runtime, you may inadvertently rely on features not present on some tenants.

How runtime choices affect Danish localisation and connectors

Danish-specific functionality commonly lives in localisation extensions, DK locale packages, and third-party ISV add-ons: Peppol/OIOUBL mapping and senders, NemHandel gateways, SAF‑T exporters and bank/payment connectors that produce Danish bank file formats. These components are implemented as AL extensions or depend on platform APIs that can be affected by runtime changes. Examples of how runtime choice can break or change behaviour:

  • A DK locale package requiring a newer runtime will not install on an older server, preventing Peppol/OIOUBL mapping or NemHandel flows from running.
  • Bank connector extensions that produce Danish payment file formats may depend on platform APIs that change between runtime versions.
  • SAF‑T exporter extensions that rely on table schema or platform serialization can expose runtime-gated diagnostics when compiled for newer runtimes.

Microsoft recommends compiling for the latest runtime and also for the minimum targeted runtime; running frequent builds helps surface runtime-gated diagnostics and platform behaviour changes early.

What this means for companies in Denmark

If you run Business Central in Denmark, the runtime decision directly impacts: DK locale packages, OIOUBL/Peppol mapping and sending, NemHandel gateway connectivity, SAF‑T exporters used for digital bookkeeping, and Danish bank/payment connectors. Concretely, you should:

  • Inventory all installed localisation and third-party extensions that affect Peppol/OIOUBL, NemHandel, SAF‑T or bank formats and note each extension's app.json runtime and platform/application minimums.
  • Contact ISVs (for example Continia for document handling, and your bank connector vendors) to confirm which AL runtimes they support and when they will certify compatibility with newer runtimes.
  • Avoid moving production tenants to a newer platform runtime until key ISVs certify compatibility; pinning the production tenant prevents unexpected downtime for e‑invoicing, NemHandel, SAF‑T exports and payment files.

How we would approach it

1. Inventory: produce a list of all DK localisation and payment/e‑invoicing extensions and capture their app.json "runtime", "platform" and "application" settings.

2. ISV coordination: ask ISVs to confirm supported runtimes and any planned runtime bumps. Get written compatibility statements and timelines.

3. Build strategy: adopt a dual-build approach — compile daily/weekly for the latest runtime to surface issues, but set your production-target runtime to the minimum that all servers and ISVs support.

4. Sandbox validation: before any runtime change, validate in a sandbox end‑to‑end: send Peppol/OIOUBL messages, verify NemHandel gateway connectivity, run SAF‑T exports, and generate Danish bank files.

5. Pin production: keep production tenants on a certified runtime until ISVs and your tests are green.

Choosing an AL runtime is an operational decision with direct consequences for Danish bookkeeping, e‑invoicing and payments. Follow a measured, ISV‑coordinated path: inventory, verify, test, and only then change production runtimes.

Source: Microsoft Learn

Do you have questions about this?

We are happy to help you assess what this news means in practice for your Business Central setup.