Glossary Term

Nemhandel

Denmark's national e-invoicing and e-procurement infrastructure, run by the Danish Business Authority. Its registry (NHR) doubles as a Peppol SMP, and the network is migrating from the OIOUBL format to a localised Peppol BIS 4 profile branded NemHandel BIS 4.

Quick Facts

Model
Four-corner
Country
Denmark
Operator
Erhvervsstyrelsen (Danish Business Authority)
Registry
Nemhandelsregisteret (NHR) — also a Peppol SMP
Transport
Nemhandel eDelivery (Peppol AS4 + extra scheme validation)
OIOUBL 3.0
Cancelled (Jan 2026)
B2B mandate
Phased from 1 Jan 2026 (Bookkeeping Act)
Certificates
MitID (access point), OCES MOCES/FOCES (NHR PoRS2 API)
Future format
NemHandel BIS 4 (localised Peppol BIS 4)
Current formats
OIOUBL 2.1, Peppol BIS 3.0

Definition

What it is

Nemhandel ("easy trade") is Denmark's national infrastructure for exchanging structured business documents — primarily e-invoices — between businesses and with the public sector. It is developed and operated by Erhvervsstyrelsen (the Danish Business Authority), and it has been the backbone of Danish public-sector e-invoicing since 2005, long before Peppol existed. For an ERP vendor, Nemhandel is the Danish equivalent of France's Chorus Pro/PPF or Italy's SdI: the network you must connect to in order to deliver invoices to Danish counterparties.

Nemhandel is built on a four-corner model. Senders and receivers each connect through an access point; documents are routed between access points and addressed using a central registry. That registry — Nemhandelsregisteret (NHR) — is the piece ERP developers interact with most: it maps a recipient's identifier (typically a Danish CVR number, an EAN/GLN location number, or a Peppol participant ID) to the endpoint and document types that recipient can receive. Crucially, NHR is itself a Peppol Service Metadata Publisher (SMP), so Danish participants are discoverable from the wider Peppol network, and it is integrated with the CVR business registry — functionality a commercial SMP does not offer out of the box, and it is free to use.

Why it matters for e-invoicing

Denmark's 2022 Bookkeeping Act (Bogføringsloven) requires businesses to use certified digital bookkeeping systems capable of sending and receiving structured electronic invoices via Nemhandel, in either OIOUBL or Peppol BIS 3.0. The B2B obligation is phased in from 2026: financial companies of any size and personally-owned businesses with annual turnover above DKK 300,000 in both 2024 and 2025 are in the first wave from 1 January 2026. This is what turns Nemhandel from a public-sector channel (mandatory B2G since 2005) into something every Danish-facing ERP must support.

The strategic picture shifted sharply in early 2026. The long-planned OIOUBL 3.0 was formally cancelled in January 2026. Instead of evolving its national format, Denmark committed to migrating the whole network onto a localised version of Peppol BIS 4, branded NemHandel BIS 4, with Danish national extensions. The current OIOUBL 2.1 format is expected to be phased out by July 2029, ahead of the EU's ViDA (VAT in the Digital Age) Digital Reporting Requirements deadline of July 2030. For vendors, the practical takeaway is to build against Peppol BIS, not to invest further in OIOUBL-only tooling.

How ERP vendors encounter it

Three integration surfaces matter:

  • Transport. The legacy RASP/OIORASP profile has been superseded by Nemhandel eDelivery, which follows the Peppol eDelivery AS4 specification. The notable Danish deviation is an extra scheme-validation step during AS4 transmission, ensuring the payload is well-formed XML of the expected document class before it is accepted.

  • Certificates. Nemhandel eDelivery requires the access point to sign with a MitID certificate (not a Peppol certificate). The PoRS2 API used to register and query NHR requires OCES organisation certificates — MOCES (employee) or FOCES (function) certificates — as client certificates.

  • Addressing. Recipients are looked up in NHR. A Danish endpoint is commonly identified by CVR via Peppol scheme 0184 (DIGSTORG / Danish organisation) or by GLN via scheme 0088.
  • Relation to EN 16931

    Both OIOUBL and Peppol BIS Billing 3.0 are CIUS/profiles aligned with the European semantic standard EN 16931. The same business terms (BT-*) you populate for a German XRechnung or a Peppol invoice carry over; what changes for Denmark is the routing layer (NHR/Nemhandel eDelivery) and a handful of Danish-specific rules. A vendor that already emits EN 16931-conformant UBL through a Peppol access point is most of the way to Nemhandel compliance — the remaining work is registry lookup, the MitID/OCES certificate setup, and the Danish extension rules.

    XML Examples

    UBL (Peppol, XRechnung)

    <!-- Danish recipient addressed by CVR via Peppol scheme 0184 (DIGSTORG) -->
    <cac:AccountingCustomerParty>
      <cac:Party>
        <cbc:EndpointID schemeID="0184">DK12345678</cbc:EndpointID>
        <cac:PartyLegalEntity>
          <cbc:CompanyID schemeID="0184">DK12345678</cbc:CompanyID>
        </cac:PartyLegalEntity>
      </cac:Party>
    </cac:AccountingCustomerParty>

    Related Content