Guide
E-Invoicing in Denmark
Key formats, routing options, and a practical checklist for sending compliant e-invoices in Denmark.
What matters in practice
This Denmark guide explains OIOUBL, NemHandel, PEPPOL routing, and the CVR and VAT checks that most often decide whether an invoice is delivered cleanly.
This article treats E-Invoicing in Denmark as a practical reference, not just a navigation page. It explains the term or workflow in context, shows why it matters for European e-invoicing, and connects the topic to invoice creation, validation, routing, archiving, and ERP implementation decisions.
Common e-invoice formats
Common e-invoice formats is where the general explanation of E-Invoicing in Denmark becomes operational. The section focuses on OIOUBL and PEPPOL BIS 3.0 (UBL), so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- OIOUBL
- PEPPOL BIS 3.0 (UBL)
Routing & delivery
Routing & delivery connects E-Invoicing in Denmark with the next useful reference pages and tools. These links are included to support a complete workflow, from understanding NemHandel and PEPPOL to validating or converting the invoice file.
Common identifiers
Common identifiers is where the general explanation of E-Invoicing in Denmark becomes operational. The section focuses on CVR number and VAT ID, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- CVR number
- VAT ID
Mandate & scope
Denmark combines OIOUBL and NemHandel with PEPPOL-style structured routing for many invoice flows.
Mandate & scope
Mandate & scope is where the general explanation of E-Invoicing in Denmark becomes operational. The section focuses on Public-sector delivery often depends on NemHandel-compatible structured data, CVR number and VAT ID should match the supplier record used by the recipient and Recipient-specific process/profile settings matter for successful delivery and validation, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Public-sector delivery often depends on NemHandel-compatible structured data.
- CVR number and VAT ID should match the supplier record used by the recipient.
- Recipient-specific process/profile settings matter for successful delivery and validation.
How to send (practical steps)
How to send (practical steps) is where the general explanation of E-Invoicing in Denmark becomes operational. The section focuses on Confirm whether the recipient expects NemHandel, PEPPOL, or both, Collect the routing identifiers and supplier registration data required for the target channel and Generate the invoice in OIOUBL or PEPPOL BIS 3.0 UBL as requested, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Confirm whether the recipient expects NemHandel, PEPPOL, or both.
- Collect the routing identifiers and supplier registration data required for the target channel.
- Generate the invoice in OIOUBL or PEPPOL BIS 3.0 UBL as requested.
- Validate, send, and retain the delivery receipt or acknowledgement.
Validation & compliance
Validation & compliance is where the general explanation of E-Invoicing in Denmark becomes operational. The section focuses on Check endpoint and participant schemes before routing, Validate VAT codes, totals, unit codes, and payment data and Use allowance/charge structures instead of negative invoice lines for discounts, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Check endpoint and participant schemes before routing.
- Validate VAT codes, totals, unit codes, and payment data.
- Use allowance/charge structures instead of negative invoice lines for discounts.
Common pitfalls
Common pitfalls is where the general explanation of E-Invoicing in Denmark becomes operational. The section focuses on Wrong endpoint or participant scheme for the chosen channel, Missing or inconsistent CVR data in supplier setup and Using free-text tax descriptions instead of the required codes, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Wrong endpoint or participant scheme for the chosen channel.
- Missing or inconsistent CVR data in supplier setup.
- Using free-text tax descriptions instead of the required codes.
Frequently asked questions
Frequently asked questions answers the practical questions that usually appear after reading the main explanation of E-Invoicing in Denmark. The answers focus on Which invoice route is most common in Denmark and What should I verify before sending a Danish invoice and are written to clarify implementation choices quickly.
Which invoice route is most common in Denmark?
NemHandel and PEPPOL-style structured delivery are both common, with the recipient usually deciding which syntax is accepted.
What should I verify before sending a Danish invoice?
Check the CVR number, VAT ID, endpoint or participant details, and the recipient’s profile expectations before sending.
Official links
Official links connects E-Invoicing in Denmark with the next useful reference pages and tools. These links are included to support a complete workflow, from understanding NemHandel and OpenPeppol to validating or converting the invoice file.