VATupdate
I Love The Netherlands

Share this post on

May 2026 NPa Validation Artefacts for SI-UBL 2 / NLCIUS and Peppol BIS 3 – Mandatory from 17 August 2026

Summary 

  • The Dutch Peppol Authority (NPa) published the May 2026 validation artefacts for both SI-UBL 2 (NLCIUS) and Peppol BIS 3. [peppolautoriteit.nl]
  • These artefacts incorporate updated EN 16931 validation rules (v1.3.16) and revised technical specifications. [peppolautoriteit.nl]
  • The updated versions will become mandatory for use on 17 August 2026, following the standard phased release approach. [peppolautoriteit.nl]

Article

The Dutch Peppol Authority (NPa) has released the May 2026 updates to the validation artefacts for SI-UBL 2 (implementing NLCIUS) and Peppol BIS Billing 3.0, marking an important step in the continuous evolution of e-invoicing standards within the Netherlands.

Scope and purpose of the update

The newly published artefacts define the technical validation rules that structured electronic invoices must comply with when processed via the Dutch e-invoicing ecosystem, particularly over the Peppol network. These validation artefacts are critical as they ensure that invoices:

  • comply with the European standard EN 16931,
  • adhere to Dutch-specific business rules (NLCIUS), and
  • remain interoperable within the Peppol framework.

For the May 2026 release, the NPa confirms that the underlying EN 16931 validation rules have been updated to version 1.3.16, requiring updates to validation logic and potentially to ERP and middleware configurations. [peppolautoriteit.nl]

Key changes and technical impact

The update primarily affects:

  • Validation artefacts for SI-UBL 2 (NLCIUS):
    These artefacts include schematrons, XSDs, and supporting files used to validate Dutch-compliant UBL invoices. The updated artefacts are made available via the official NPa GitHub repository, ensuring transparent versioning and traceability. [peppolautoriteit.nl]
  • Peppol BIS 3 validation artefacts:
    The NPa refers users to the official OpenPeppol documentation, where updated validation rules, code lists, and implementation guidance are provided. [peppolautoriteit.nl]

As validation artefacts directly control whether an invoice is accepted or rejected by receiving systems, even minor rule changes (e.g., code list updates, new mandatory fields, or stricter validations) can have immediate operational impact.

Mandatory implementation timeline

In line with the standard Dutch Peppol release cycle, the NPa applies a phased approach:

  1. Publication phase (May 2026) – new artefacts released and available for testing
  2. Transition phase – both current and new versions can be used
  3. Mandatory phase (from 17 August 2026) – the new artefacts become compulsory

From 17 August 2026, all invoices exchanged under the relevant formats must comply with the updated validation rules; until then, existing versions remain mandatory. [peppolautoriteit.nl]

This approach aligns with the broader Peppol governance model, where updates are introduced gradually to allow service providers and businesses sufficient time to adapt. [peppol.nl]

Regulatory and market context

Although B2B e-invoicing is not yet generally mandatory in the Netherlands, structured e-invoicing is already required for suppliers to public sector entities, and Peppol has become the dominant infrastructure for compliant exchange. [invoicedat…action.com]

Within this context:

  • SI-UBL 2 remains the Dutch national implementation of EN 16931 via NLCIUS,
  • Peppol BIS 3 ensures cross-border interoperability, and
  • the NPa enforces standardisation through mandatory validation artefacts and release cycles.

The May 2026 release therefore represents a technical compliance milestone, ensuring continued alignment between Dutch requirements and evolving European standards.

Practical implications for businesses

Companies operating in or trading with the Netherlands should:

  • Update validation engines and mapping logic to reflect EN 16931 v1.3.16
  • Test invoice flows against the new artefacts before August 2026
  • Coordinate with Peppol service providers to ensure timely implementation
  • Monitor dependencies, such as ERP integrations, middleware, and e-invoicing platforms

Failure to adopt updated artefacts by the deadline may result in invoice rejections, delayed payments, and compliance risks—particularly in public sector invoicing.

Links / Sources



Sponsors:

VAT IT
Fiscal Solutions Bottom

Advertisements:

  • advert