19 November 2026
Microsoft publishes cumulative updates for Business Central 2026 release wave 1 (version 24) as distinct on‑premises packages. These updates bundle hotfixes and regulatory features, and they include local versions for Denmark. For organisations running Business Central on‑premises in Denmark, applying updates is an operational task — not an automatic push — and it directly affects Danish e‑invoicing, SAF‑T, and bank integrations when any local regulatory fixes are included.
Available updates and builds
The on‑premises update table for 2026 wave 1 lists incremental updates with release months and build numbers. Examples from the published list include:
- Update 28.1 — May 2026 — Application Build 28.1.49838, Platform Build 28.0.49873
- Update 28.2 — June 2026 — Application Build 28.2.51034, Platform Build 28.0.50938
- Update 28.3 — July 2026 — Application Build 26.15.52222, Platform Build 26.0.52201
- Update 28.4 — August 2026 — Application Build 28.4.53241, Platform Build 28.0.53152
- Update 28.5 — September 2026 — Application Build 28.4.53241, Platform Build 28.0.53152
- Update 28.6 — October 2026 — Application Build 28.6.55443, Platform Build 28.0.55350
- Update 28.7 — November 2026 — Application Build 28.7.57329, Platform Build 28.0.57236
Microsoft's documentation also reminds administrators to always install the latest update because it contains cumulative hotfixes and regulatory features from previous updates. The documentation was last updated on 11/06/2026.
Why the on‑prem model matters for Denmark
On‑premises updates must be applied by the customer or their partner. That means any hotfix or regulatory change that touches Danish localisation — the Peppol/NemHandel OIOUBL e‑invoicing paths, SAF‑T export formats used for Danish bookkeeping, or file layouts for Danish bank integrations — will only become active once you install the update. Unlike cloud tenants (where you can check tenant status in the Business Central Admin center), on‑prem customers control the timing of when those fixes reach production.
If an update includes changes to local code or mappings for DK, postponing the update could delay critical regulatory fixes. Conversely, applying an update without verification could alter SAF‑T or bank export behaviour mid‑month and disrupt monthly bookkeeping or VAT reporting to SKAT.
What this means for companies in Denmark
- Confirm that updates list Denmark (DK) among included local versions — Microsoft’s update pages publish the supported local versions and build numbers. The 2026 wave‑1 updates explicitly include DK.
- Schedule update windows outside of VAT filing cycles and other critical SKAT reporting dates to avoid interrupting month‑end and VAT submissions.
- After installing an update, validate end‑to‑end Danish scenarios: Peppol/NemHandel e‑invoices (OIOUBL payloads), SAF‑T exports for digital bookkeeping, and bank file exports/imports using Danish bank formats.
- Keep a rollback plan and backups so you can restore the system if an update changes export layouts or integration behaviour that your reconciliation or VAT processes depend on.
How we would approach it (Invice recommendations)
1. Inventory and schedule: Record your current Application and Platform build numbers. Map all processes that rely on DK localisation — Peppol/NemHandel routes, OIOUBL mappings, SAF‑T generation, and bank format exports. Book update windows that avoid VAT/SKAT deadlines.
2. Prepare a copy of production: Apply the update first on a sandbox or a full restored copy of production. Use the exact database and integration endpoints for Peppol and banks to validate real‑world behaviour without touching live reporting.
3. Run concrete tests: Export a SAF‑T file and compare it to your expected structure. Send and receive test Peppol/NemHandel messages and validate OIOUBL payloads. Generate bank files and run reconciliation test cases.
4. Record and communicate changes: If the update changes any document layouts or fields, document the impact and communicate to accounting and payment teams before going live.
5. Rollback readiness: Take a full database backup and snapshot of extension/app files before installing. Have a rollback checklist and timing plan so you can revert within your SLA if month‑end processing is affected.
Applying 2026 wave‑1 updates on‑prem is an administrative step with regulatory consequences in Denmark. Plan the window, validate the Danish e‑invoicing and SAF‑T paths, and keep a tested rollback route so VAT reporting and monthly bookkeeping remain uninterrupted.
Source: Microsoft Learn

