Denmark: NemHandel Peppol Schematron Packages 1.17.0 and 1.2.14 Become Mandatory at 12:00 CET on August 17, 2026

Country Update — Denmark  |  17 August 2026  |  Topic: E-Invoicing / Peppol Validation Artifacts

On August 3, 2026, Nemhandel, the Danish e-business infrastructure operated under the Danish Business Authority (Erhvervsstyrelsen), published new versions of its Peppol Schematron validation packages: the Danish CIUS package version 1.17.0 and the Danish Peppol BIS3-Other package version 1.2.14. Both become mandatory at 12:00 CET on August 17, 2026.

From that moment, the previous packages are withdrawn from use, and documents validated only against the superseded rule set are liable to be rejected rather than accepted with a warning. The release aligns the Danish customization with the OpenPeppol May 2026 post-award release, which becomes mandatory across the network on the same day.

Background

Denmark has one of Europe's longest-running mandatory e-invoicing regimes. Electronic invoicing to the public sector has been compulsory since 2005, originally through OIOXML and then through OIOUBL, and is operated through NemHandel, the national e-business infrastructure.

Since Denmark became a Peppol authority, the two worlds have converged: NemHandel now carries Peppol traffic, and the Danish requirements are expressed as a Peppol customization — a CIUS, or Core Invoice Usage Specification — layered on top of Peppol BIS Billing 3.0, together with a companion package for the other Peppol BIS 3.0 document types.

The regime has since been extended well beyond public procurement. The Danish Bookkeeping Act (bogføringsloven) requires businesses to use digital bookkeeping systems that can send and receive e-invoices, phased in across 2024 to 2026 by entity type and turnover, and makes registration in NemHandel the default for businesses using a registered bookkeeping system. Denmark has also announced a consolidation onto a single Peppol-based e-invoice specification by 2028 to 2029, aligned with Peppol BIS 4 and PINT, and a national SAF-T version 2.0 applying from January 2027. KGT reported on the specification consolidation on July 9, 2026.

Within that architecture, the Schematron packages are the operative layer. They are not law, and they are not a specification in the descriptive sense; they are the executable rules against which a document either validates or fails. Nemhandel publishes them with a version number and a hard date on which the previous version ceases to be valid, and it is that date, not the publication date, that determines whether an invoice can be delivered.

The Legislative Change

This is a technical release, not a legislative change. The Danish VAT Act, the Bookkeeping Act and the public-procurement e-invoicing obligation are untouched. The release operates within the existing legal framework and changes only the validation artifacts applied to documents in transit.

It is nevertheless binding in practice, and binding with a precision that statutory instruments rarely achieve. The obligation is enforced at 12:00 CET on a named day, by software, on every document presented after that moment. There is no assessment, no correspondence, and no reasonable-care defense: a document that fails the current Schematron is not delivered. For a supplier to Danish public-sector bodies, a document that is not delivered has not been invoiced, and payment terms do not begin to run.

The mid-day cutover deserves particular attention. Most enforcement dates in indirect tax start at the beginning of a day or period, which allows an overnight change window. A 12:00 CET cutover falls within the Danish working day, which means outbound traffic produced in the morning and afternoon of August 17, 2026 may be validated against different rule sets. Any organization batching invoice output across that boundary should assume that the second batch is subject to the new rules.

Scope

• Danish CIUS Schematron package, version 1.17.0 — the Danish customization of Peppol BIS Billing 3.0, governing invoices and credit notes exchanged through NemHandel and Peppol in Denmark.
• Danish Peppol BIS3-Other Schematron package, version 1.2.14 — the companion package covering the other Peppol BIS 3.0 document types in Danish use.
• Both packages apply to documents exchanged through NemHandel and to Danish traffic on the Peppol network, in the production environment.
• The release is aligned with, but formally separate from, the OpenPeppol May 2026 post-award release. Organizations transmitting in Denmark are therefore subject to two changes taking effect on the same day, published by two different bodies.
• The release does not alter the Danish SAF-T requirement, the Bookkeeping Act digital bookkeeping obligations, or the planned move to a single Peppol-based specification by 2028 to 2029.

Timeline

• May 20, 2026 — OpenPeppol publishes the May 2026 post-award release on which the Danish packages are based.
• August 3, 2026 — Nemhandel publishes Danish CIUS 1.17.0 and Danish Peppol BIS3-Other 1.2.14.
• August 3 to August 17, 2026 — transition period. Two weeks, which is materially shorter than the three-month network transition and falls across the Danish summer holiday period.
• August 17, 2026, 12:00 CET — the new packages become mandatory. The previous versions cease to be valid for use.
• August 17, 2026 — the OpenPeppol May 2026 billing release becomes mandatory network-wide on the same day; Peppol BIS Logistics 1.3 follows on August 24, 2026.
• January 1, 2027 — Danish SAF-T version 2.0 applies.
• 2028 to 2029 — planned consolidation onto a single Peppol-based e-invoice specification.

Businesses Affected

Every business that issues or receives electronic invoices in Denmark is in scope, but exposure is concentrated in three places.

• First, suppliers to Danish public-sector bodies, for whom electronic invoicing through NemHandel is the only permitted channel and for whom a validation failure is a payment failure.
• Second, businesses that operate their own NemHandel or Peppol connectivity, including those running Peppol from within SAP, because they hold the upgrade obligation directly rather than through a provider.
• Third, foreign groups with a Danish company code or a Danish VAT registration issuing invoices into Denmark, which are frequently the last to learn of a Danish-specific artifact release because the release is published in Danish, on a Danish infrastructure site, and does not appear in the tax authority news channels those groups monitor.

Businesses that exchange exclusively through a Danish service provider or access point under a managed service are largely protected on the sending side, but not on the content side: if the new package tightens a rule that the sending system currently breaches, the provider will begin rejecting that content on August 17.

Receiving parties should not assume they are unaffected. A Danish accounts payable process that validates inbound documents against the old package, or that rejects unfamiliar values, will fail on documents that are entirely valid under version 1.17.0.

Required Actions

• Read the Nemhandel release note for version 1.17.0 and 1.2.14 and extract the rule-level change list. This is the single most important step and it cannot be substituted with a summary.
• Confirm with your access point or service provider, in writing and before August 17, which package version is in force in production and at what time on August 17 the switch is applied.
• For self-operated connectivity, deploy and test the new packages in a test environment, then in production, and verify that the production deployment is complete before 12:00 CET on August 17, 2026.
• Validate a representative sample of Danish outbound documents against version 1.17.0, deliberately including credit notes, invoices with allowances and charges, reverse-charge and exempt lines, foreign-currency documents and any document carrying a Danish-specific reference such as an EAN or a contract identifier.
• Plan invoice output around the mid-day cutover. Where possible, run the August 17 outbound batch either well before or well after 12:00 CET rather than across it.
• Confirm that inbound validation in accounts payable accepts documents built to the new packages, and that any rejection is surfaced to a monitored queue rather than silently dropped.
• Reconcile documents released from SAP on August 17 and 18 against documents acknowledged by the access point, and clear any difference the same week.

Practical Implications

The most consequential feature of this release is the length of the transition window. Two weeks is short for any validation change; two weeks in the first half of August, across the Danish summer holiday, is short enough that many organizations will not have read the release note before it becomes binding. Where a group has already begun its August financial close, the change lands in the middle of it.

The second implication concerns ownership. National CIUS releases sit in an organizational gap. They are technical enough that the tax function does not monitor them, and specific enough to one country that a shared services or IT function running a multi-country Peppol landscape does not naturally see them. The result is a recurring pattern in which the change is discovered from a rejection rather than from a publication. The remedy is not more diligence, but a named owner per country and a version register reviewed on a schedule.

The third is that Denmark now generates two categories of change at once — Peppol artifact releases in the short term, and a structural specification consolidation toward Peppol BIS 4 and PINT by 2028 to 2029, together with SAF-T 2.0 from January 2027. An organization that treats each release as an isolated fix will repeat the same effort. Building the Danish validation layer as a configurable, version-controlled component pays for itself well before 2029.

Expected Next Steps

Nemhandel maintains the Danish packages on a rolling basis and has historically issued several releases a year, so another version should be expected before the end of 2026, likely aligned with the autumn 2026 OpenPeppol release. Organizations should also expect the Danish Business Authority to continue the legislative track around default NemHandel registration by bookkeeping-system providers, on which a draft order was put out for consultation in July 2026 with a consultation deadline in August 2026, and to publish further guidance on SAF-T version 2.0 ahead of its application on January 1, 2027.

How Can KGT Support You?

KGT specializes in making statutory e-invoicing and digital reporting work inside SAP, not alongside it. Our SAP-integrated e-invoicing add-ons cover clearance, network and reporting models, including Peppol-based exchange, and are designed so that a change in a validation artifact is absorbed as a configuration and mapping change rather than a project. Where a client runs SAP Document and Reporting Compliance (SAP DRC), KGT delivers implementation, extension and support services, including mapping to national customizations, eDocument and Statutory Reporting configuration, and the monitoring processes that turn a rejection into a resolved exception rather than an unbooked invoice.

For the readiness questions raised by this update, KGT can perform an impact assessment across the affected company codes, confirm which validation artifact version your access point or platform is running, test representative document flows against the current rules ahead of the enforcement date, and put a version-watch process in place so that the next release is picked up before it becomes mandatory rather than after the first rejection.

Official sources

• Nemhandel — release of Peppol Schematron packages 1.17.0 and 1.2.14: View source
• Nemhandel — home and news: View source
• Danish Business Authority (Erhvervsstyrelsen) — SAF-T version 2 and corrections to the standard chart of accounts: View source
• Danish public consultation portal (Høringsportalen) — draft order on NemHandel registration: View source
• OpenPeppol — post-award specifications and mandatory-use dates: View source

This publication is provided for general informational purposes only and does not constitute tax, legal, or professional advice. Please consult your advisor before acting on any information contained in this update.