Network business specification · transition

Peppol BIS Billing 3.0

The dominant Peppol invoice and credit-note profile based on EN 16931 and UBL, with Peppol and seller-country rules.

UBL Invoice XMLUBL CreditNote XML

Current version and implementation status

Version notePeppol BIS Billing 3.0.20-hotfix; mandatory from 23 February 2026
Statustransition
Reviewed2026-08-02
FamilyNetwork business specification
Open official technical source

How to recognize the profile

Do not rely on the file extension alone. Inspect the root namespace, customization/profile identifiers, version values and authority-specific envelope.

  • urn:fdc:peppol.eu:2017:poacc:billing:01
  • Peppol profile identifiers
  • EndpointID schemeID

Production validation stack

  1. 1
    UBL schema

    Confirm that the document is well formed and structurally compatible with the intended Peppol BIS Billing syntax.

  2. 2
    EN 16931 rules

    Apply semantic and business-rule checks rather than accepting a file merely because it parses.

  3. 3
    Peppol BIS rules

    Validate currencies, countries, tax categories, units, payment means and other controlled values against the correct release.

  4. 4
    Country-specific seller rules

    Apply the national, network or authority restrictions that narrow the base syntax.

  5. 5
    Code lists

    Apply the current official validation artefact and retain an auditable result.

EInvoiceLab’s browser tools provide detection, inspection and technical preflight. A profile is only production-valid after applying the correct official artefacts and obtaining the required network or authority outcome.

Common errors and corrective action

!
Invalid endpoint scheme

Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.

!
ProfileID mismatch

Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.

!
National seller rule failure

Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.

!
Invalid VATEX or EAS code

Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.

Questions people ask

What is Peppol BIS Billing?

The dominant Peppol invoice and credit-note profile based on EN 16931 and UBL, with Peppol and seller-country rules.

How is Peppol BIS Billing validated?

A production check normally applies UBL schema, EN 16931 rules, Peppol BIS rules, Country-specific seller rules, Code lists. Local browser preflight cannot replace the official validation artefacts or authority outcome.

Which version should I use?

The current research note is: Peppol BIS Billing 3.0.20-hotfix; mandatory from 23 February 2026. Confirm release notes at the official source before production deployment.

Practical tools

Inspect and prepare Peppol BIS Billing files