Skip to main content

Register suppliers

Supplier registration guide ›

Issue invoices

Issuing guide ›
NemHandel is Denmark’s national e-invoicing network, managed by the Danish Business Authority (Erhvervsstyrelsen). Invoicing Danish public authorities through it has been mandatory since 2005 — the first B2G mandate in Europe — and Danish businesses exchange B2B invoices over the same infrastructure, with the Digital Bookkeeping Act requiring every business system to be e-invoicing-capable.The NemHandel Denmark app converts GOBL invoices and credit notes to OIOUBL 2.1, Denmark’s UBL-based national format, and exchanges them over the network: outbound documents are delivered through Invopop’s NemHandel access point, and documents addressed to your registered suppliers are imported back into your workspace automatically.Supplier onboarding is handled end to end in a workflow: the supplier’s representative signs the authorization agreement through a hosted signing page, and once approved the party is registered as a NemHandel participant.
Danish public authorities also accept Peppol BIS Billing 3.0 over the Peppol network. If you don’t specifically need OIOUBL or NemHandel participant registration, the Peppol app is usually the simpler option.

Key features

  • Workflow automation: Convert, deliver, and import documents with no-code workflows.
  • OIOUBL 2.1: Danish CIUS of EN 16931, generated and parsed natively from GOBL.
  • Supplier onboarding: Hosted authorization agreement signing and participant registration.
  • Receiving: Documents delivered to registered suppliers are converted to GOBL and stored with their original XML and attachments.
Check out the guides below to get started:

FAQ

Invoicing questions
Documents on NemHandel are addressed by participant identifier. If the customer declares an endpoint (for example GLN:5798009883735 for a public institution’s EAN/GLN number), that identifier is used. If a Danish customer only carries a CVR number in its tax ID, the dk-oioubl-v2 GOBL addon derives the participant identifier (DK:CVR:<number>) automatically. Explicit endpoints always win over derived ones.
Issue a credit note referencing the original invoice in the preceding array. OIOUBL requires non-negative totals, so corrections in Denmark are always credit notes — a negative invoice will fail validation. There is no cancellation mechanism on the network itself: once delivered, a document can only be countered by a credit note.
OIOUBL restricts the UNTDID 4461 payment means codes to a fixed list. The most common mappings from GOBL are debit-transfer for IBAN bank transfers (code 31, requires a BIC), domestic Danish bank transfers (code 42, account number plus bank registration number), Giro (code 50), and FIK (code 93). A generic credit-transfer (code 30) is rejected by the format.
The send step submits the OIOUBL document to the network and then queues until the delivery is confirmed by Invopop’s NemHandel access point. The workflow’s state only advances to sent once the network reports the document as delivered, so a sent entry means the recipient’s access point accepted it.
Registering supplier questions
Before a company can be registered on NemHandel, its representative must sign an authorization agreement allowing Invopop and its NemHandel access point to exchange documents on the company’s behalf. The registration workflow publishes a public signing link on the party entry; the representative opens it, fills in their name, role, and contact email, signs, and the agreement is submitted for approval. The workflow waits until the agreement is approved before registering the participant.
Someone entitled to represent the company — typically a director or another person with signing authority. The signer provides their full name, their role in the company, and a contact email, and can sign by typing or drawing their signature.
Yes. The registration steps are safe to re-run: an already-signed agreement or an already-registered participant is detected and skipped, so retrying a failed or interrupted registration won’t create duplicates.
Receiving questions
Once a party is registered, documents addressed to its participant identifier are delivered to Invopop’s access point. Each delivery triggers the import workflow you selected in the NemHandel Denmark app’s configuration: the import step fetches the OIOUBL document, converts it to GOBL, creates the silo entry, and attaches the original XML along with any embedded binary attachments (such as PDFs).
Deliveries are only acknowledged to the network after the import completes, so a transient failure leaves the document ready to be retried. An hourly reconciliation loop also picks up any deliveries missed by the real-time path. Documents that can never be processed are flagged for review instead of being retried forever.
More answers in our Denmark FAQ section

Participate in our community

Ask and answer questions about the NemHandel Denmark app →