Peppol Invoice Validator for Dutch Companies
The Netherlands mandates Peppol BIS Billing 3.0 for central government since 2019, with NLCIUS as the Dutch extension. Validate your UBL invoices before submitting to Digipoort - free, no file uploaded.
Open Peppol ValidatorDutch e-invoicing obligations: Digipoort & NLCIUS
The Netherlands has been a Peppol pioneer: mandatory e-invoicing for central government (rijksoverheid) has been in force since January 2019. All suppliers to Dutch central government must submit Peppol BIS Billing 3.0 invoices via Digipoort, the national data exchange hub managed by Logius.
The Dutch extension NLCIUS (NL3.0 / Simplerinvoicing) adds Dutch-specific rules on top of Peppol BIS Billing 3.0, including mandatory OIN (Organisatie-identificatienummer) for public sector buyers and specific VAT code requirements. For B2B, the Netherlands is preparing for the ViDA mandate expected in 2027.
Compliance timeline
B2G (central government): Peppol BIS Billing 3.0 + NLCIUS mandatory for all suppliers to Dutch rijksoverheid via Digipoort.
Voluntary Peppol adoption expands to municipalities, provinces, and semi-public entities via Simplerinvoicing network.
Preparation for ViDA: Dutch FPS Finance (Belastingdienst) and Logius prepare infrastructure for B2B e-invoicing mandate.
B2B (planned under ViDA): mandatory e-invoicing for all Dutch VAT-registered companies. Peppol network as primary exchange channel.
What ValidateFin checks in your Dutch Peppol invoice
Before submitting to Digipoort or a Dutch Peppol access point, verify your invoice passes these checks:
- UBL 2.1 schema validation against Peppol BIS Billing 3.0 and NLCIUS extension rules
- Dutch VAT number format: NL + 9 digits + B + 2 digits (BTW-nummer)
- OIN (Organisatie-identificatienummer) for public sector buyers: required in cac:AccountingCustomerParty
- EN 16931 mandatory fields: seller/buyer identification, VAT breakdown, payment terms
- NLCIUS-specific rules: NL-R-001 to NL-R-009 business rules for Dutch public procurement
Common errors causing Digipoort / Peppol rejection
Missing or invalid OIN for government buyers
Dutch public entities are identified by their OIN (Organisatie-identificatienummer, 20 digits). It must appear in cac:AccountingCustomerParty/cac:PartyIdentification. Its absence causes Digipoort routing failure.
Invalid Dutch VAT number format
Dutch BTW numbers follow the format NLxxxxxxxxx (NL + 9 digits + B + 2 digits, e.g. NL123456789B01). The 'B' separator and 2-digit suffix are mandatory and frequently omitted.
NLCIUS rule NL-R-001: missing EndpointID
The Peppol EndpointID (electronic address) of both seller and buyer must be present in cac:EndpointID with the correct scheme (e.g. 0106 for KvK, 0190 for OIN). Missing endpoints break Peppol routing.
Frequently asked questions
What is NLCIUS and how does it differ from Peppol BIS 3.0?
NLCIUS (NL Customer Invoice Standard) is a Dutch extension of Peppol BIS Billing 3.0. It adds Dutch-specific mandatory fields (OIN for public buyers, specific endpoint schemes) and restricts some optional fields. All NLCIUS invoices are valid Peppol BIS 3.0 invoices, but not all Peppol BIS 3.0 invoices are NLCIUS-compliant.
Does ValidateFin support NLCIUS validation?
ValidateFin validates your UBL 2.1 invoice against Peppol BIS Billing 3.0 and EN 16931 rules. For NLCIUS-specific rules (NL-R-001 to NL-R-009), the core structural and business rule validation is included. Full NLCIUS rule set support is being extended progressively.
My company sells to Dutch municipalities - do I need Peppol?
Yes. Dutch municipalities (gemeenten) have broadly adopted Peppol following the central government mandate. Most require Peppol BIS Billing 3.0 invoices via a registered Peppol access point. ValidateFin helps you verify your invoice structure before sending it through your access point provider.
E-invoicing guides by country
Validate your Dutch Peppol invoice before submission
Check UBL 2.1, Peppol BIS 3.0, and NLCIUS rules instantly. No file uploaded, no registration.