Guide
Markdown exportE-Invoicing in Netherlands
Key formats, routing options, and a practical checklist for sending compliant e-invoices in Netherlands.
What matters in practice
This Netherlands guide explains PEPPOL delivery, UBL mapping, KVK and VAT validation, and the common routing questions that decide whether an invoice is accepted.
Common e-invoice formats
Use these points as the practical checks for this section.
- PEPPOL BIS 3.0 (UBL)
- EN 16931 mappings
Routing & delivery
Common identifiers
Use these points as the practical checks for this section.
- KVK number
- VAT ID
Mandate & scope
The Netherlands frequently uses PEPPOL-based delivery models and EN 16931-aligned invoice mappings, especially for structured B2B/B2G exchange.
Country-specific operating notes for Netherlands
Use these points as the practical checks for this section.
- Dutch implementations often start with PEPPOL BIS 3.0 UBL; keep local KVK and VAT checks close to onboarding, not only at invoice export.
- Recipient discovery matters: a valid VAT ID does not prove that the buyer is reachable for the process/profile you plan to send.
- Many rejections are operational rather than semantic: wrong endpoint scheme, missing order reference, or supplier data that differs from buyer records.
- Many Dutch buyers expect the KvK number (Chamber of Commerce) in BT-30 (legal registration identifier).
- Peppol participation in NL is widespread; OVT-tunnus is for Finland (do not confuse with Dutch identifiers).
Quick checklist
Use these points as the practical checks for this section.
- Delivery: PEPPOL is commonly used via a certified access point.
- Identifiers: KVK (Chamber of Commerce) and VAT ID are frequently used identifiers.
- Profiles: ensure PEPPOL BIS settings match the recipient expectations.
- B2G mandatory since November 2017 — all central-government recipients must accept EN 16931-conformant invoices.
- NLCIUS: Dutch CIUS overlay on EN 16931, governed by the NPA (NEN/Peppol Authority).
- Simplerinvoicing: Dutch Peppol Authority brand for the Peppol routing network.
- Digipoort: government secure-messaging gateway for B2G invoice and tax filings.
- Logius: Dutch government IT-service provider operating Digipoort and the central PEPPOL access point.
How to send (practical steps)
Follow this sequence as the practical checklist for this section.
- Choose a PEPPOL access point/provider and register the correct participant identifiers.
- Confirm recipient participant ID and supported process/profile.
- Generate a PEPPOL BIS 3.0 invoice (UBL) with valid code lists and identifiers.
- Validate and send; store delivery acknowledgements.
Validation & compliance
Use these points as the practical checks for this section.
- Use correct participant ID schemes (endpoint IDs) for routing.
- Validate UBL structure and business rules (including VAT, totals, and line items).
- Ensure unit/currency/tax category codes match the expected lists.
Common pitfalls
Use these points as the practical checks for this section.
- Wrong participant ID scheme causing PEPPOL routing failures.
- Missing mandatory endpoint IDs for buyer/seller in PEPPOL workflows.
- Invalid unit or VAT codes leading to rejection.
- Sending generic EN 16931 UBL without applying the NLCIUS overlay — may pass syntax validation but fail business rules expected by Dutch buyers.
Frequently asked questions
Which invoice channel is most common in the Netherlands?
PEPPOL is the most common structured delivery model, especially for B2G and many B2B exchanges.
What should I verify before sending a Dutch invoice?
Check the participant ID, KVK or VAT details, UBL structure, and recipient profile settings before sending.