Country deep dive
Denmark's Bookkeeping Act is unusual: it mandates the technical capability to e-invoice, not that every invoice actually be sent electronically — and it's already mid-transition to a new national format.
Denmark has run digital B2G invoicing for two decades — the 2022 Bookkeeping Act extends the underlying discipline to the private sector rather than inventing something new.
Establishes the modern digital bookkeeping framework, replacing the regime that had governed Danish bookkeeping since 2006.
Sets out the detailed technical criteria for both registered and non-registered digital bookkeeping systems.
Medium and large companies filing annual reports must use a certified digital bookkeeping system capable of sending and receiving structured e-invoices (OIOUBL or Peppol BIS 3.0) and generating SAF-T files on request.
Starting with privately owned companies above DKK 300,000 turnover, extending through to financial companies of any size and personally-owned companies above the same threshold by 1 January 2026.
The planned next major version of Denmark's national format is scrapped entirely — OIOUBL 2.1 remains the operative standard with no direct replacement, pending the Peppol-based migration below.
Erhvervsstyrelsen automatically enrols all entities on registered bookkeeping systems into NemHandel, prompting default e-invoice issuance with an opt-out window — a nudge toward actual usage, not just capability.
Small businesses and sole proprietorships exceeding DKK 300,000 turnover in two consecutive years, using non-registered ("custom") accounting systems, become fully subject to the Bookkeeping Act's digital requirements.
Entities on registered bookkeeping systems must be able to generate a Danish Standard Audit File for Tax on demand — SAF-T 2.0 will harmonise charts of accounts and VAT codes nationally.
A proposed version of Denmark's localised Peppol BIS 4 format (incorporating the PINT architecture) is released for stakeholder comment.
Denmark completes its migration to NemHandel BIS 4 / Peppol PINT — timed deliberately to align with the EU ViDA cross-border deadline of 1 July 2030.
Denmark is mid-migration — the format you build against today is not the format you'll be using by the end of the decade.
Both operative formats must be supported by any system seeking "registered" status — this is a non-negotiable procurement checklist item, not an either/or choice.
Once migration completes, Erhvervsstyrelsen proposes to simplify the Bookkeeping Act's format requirement down to a single supported standard — Nemhandel BIS support alone.
A globally configured ledger doesn't map natively to the Danish standardkontoplan — this is a genuine localisation task, not just a format-conversion exercise.
Test this explicitly: simulate a data request from Erhvervsstyrelsen or Skattestyrelsen before you're ever asked for real — it's one of the six principal obligations under the Act.
The single most important thing to understand about Denmark: this law mandates capability, not universal transmission — a meaningful difference from every clearance-model country in this tracker.
A business can be fully compliant while still exchanging some invoices in other ways — what it can't do is lack the capability entirely, or use a non-compliant system to record its books.
NemHandel is Denmark's national platform, but it's interconnected with the broader Peppol network — you don't need a CVR number to participate, just a different entry point.
"Custom" doesn't mean "less scrutinised" — Path B still has to meet every statutory technical requirement, it means you carry the burden of proving compliance yourself rather than relying on a pre-certified vendor.
This campaign nudges actual e-invoice issuance up without changing the underlying legal mandate — decide deliberately whether to opt out rather than let default enrolment catch you unprepared.
Compliance here is about your bookkeeping system's status, not a single "sign up" step — plan around the six statutory obligations.
Check Erhvervsstyrelsen's official register first — using an already-certified system is materially less work than declaring and proving compliance for a custom build.
Both are required for registered status today — treat this as non-negotiable when evaluating or switching systems.
Foreign companies without a CVR should set up a Peppol Access Point connection instead to receive and send OIOUBL/Peppol invoices.
Don't assume a globally configured chart of accounts satisfies this — it's a genuine localisation requirement for registered-system status.
If your system is registered, you'll be auto-enrolled — actively decide whether to stay in or opt out rather than let it happen passively.
Confirm your system can produce SAF-T 2.0 on demand, and that your kontrolspor and transaktionsspor audit trails are properly distinguished.
Don't build long-term integrations against OIOUBL 3.0 — it's cancelled. Watch for the 2027–2028 release candidate of NemHandel BIS 4 instead.
Danish fines scale dramatically with severity — and the ultimate sanction goes well beyond money.