Peppol International (PINT) Specifications for the European Union
Release notes for European PINT-EU Billing

Version 1.1.1

Maintained by PoAC

Applies to

PINT EU (Peppol International Invoice – European Specialization)

Release Date

June 2026

Status

Final

What’s new in this release?

This release updates the PINT EU specification to align with:

  • PINT base specification version 1.1.3.

  • Latest Peppol and EN 16931 validation artefacts.

  • Key changes:

    • Code lists updates (EAS, ICD, ISO 4217), including new identifier schemes and currency code changes.

    • Upgrade of base alignment from PINT 1.1.2 to 1.1.3.

    • Documentation and compliance clarifications propagated from PINT base.

    • Improvements to Schematron rule visibility and consistency.

    • Targeted updates to EN 16931 Schematron rules to improve accuracy, robustness, and alignment with business terms.

    • Continued alignment with Peppol BIS Billing 3.0 without semantic deviations.

  • Key inherited updates from PINT Base (1.1.3):

    • Data Model:

      • Correction of IBT-003 description to Credit note type code in Credit Note context.

    • Documentation:

      • Updates to the PINT Specialisation Guide (clarifications on shared content and cardinality restrictions).

      • Compliance section updated, including removal of negative invoice guidance.

      • Text corrections in Credit Note semantic and syntax documentation.

    • Schematron:

      • Improved visibility and linkage of existing rules (e.g. IBR-127, IBR-082).

      • Removal of redundant rule IBR-SR-45 (covered by UBL schema constraints).

      • Minor correction to code list validation formatting (IBR-CL-26).

    • Additional EN16931 Schematron Updates:

      • Extension of rule BR-B-02 to include BT-118 for complete VAT category coverage.

      • Refinement of rule BR-CO-26 to exclude identifiers with schemeID SEPA.

      • Correction of element reference in UBL-CR-674 to PrimaryAccountNumberID.

      • Simplification of XPath in UBL-SR-23 for consistent validation behaviour.

      • Update of BR-CL-01 to reflect latest UNTDID 1001 code list allocations.

      • Introduction of new rule UBL-SR-56 enforcing cardinality of Originator document reference (BT-17).

    • Impact:

      • No fundamental semantic changes to the EN16931 model.

      • Validation behaviour may change due to rule corrections, XPath simplifications, and extended rule coverage.

      • Improved accuracy in supplier identification and VAT category validation.

      • Reduced risk of false positives/negatives due to alignment with UBL structure and code lists.

      • Validation of invoice type codes now also considers profile 02 (billing with response).

      • Implementers SHOULD review validation setups, especially:

        • VAT category handling (Split payment vs Standard rated scenarios)

        • Seller identification logic (exclusion of SEPA scheme)

        • Invoice/CreditNote type code validation rules

        • Originator document reference cardinality (BT-17)

        • Credit Note handling and validation setups.

Version Information

PINT General 1.1.3

PINT EU

1.1.1

Applies to

PINT EU Billing.

Reviewed

Yes

Changes (inherited from PINT General 1.1.3, including Peppol and EN16931 updates)

Data Model

  • In the Credit Note Semantic and Syntax documentation, IBT-003 was previously described as Invoice type code. This has been corrected to Credit note type code.

Documentation

  • PINT Specialisation Guide:

    • Updated the Shared Content section to clarify restrictive cardinality on optional elements when required by local implementations.

    • Improved the definition of Shared Content in the Glossary and terminology section.

    • Added clarification under Data Model → Specialisations → Allowed cardinality restrictions.

    • Removed references to GitHub issue links.

  • Compliance:

    • The entire section “Reversing invoices (credit notes or negative invoices)” has been removed to align with UAE requirements.

Code Lists Updates

Electronic Address Scheme (EAS)

New Additions

Code Description Justification

0242

OpenPeppol Service Provider Identification Scheme (SPIS)

Part of regular code list updates

0245

Tax identification number (DIČ, Slovakia)

New scheme introduced

0246

German Electronic Business Address

New scheme introduced

0248

Oman VAT Identification Number (VATIN)

New scheme introduced
ICD (ISO 6523 Identifier Schemes)

New Additions

Code Description Justification

0245

Tax identification number (DIČ, Slovakia)

Standard addition

0246

German Electronic Business Address

Standard addition

0247

Name unknown

No public documentation available

0248

Oman VAT Identification Number (VATIN)

Standard addition
ISO 4217 Currency Codes

Changes Overview

Code Status Description Justification

XCG

Added

East Caribbean Guilder

New currency introduced

ANG

Removed

Netherlands Antillean Guilder

Deprecated

BGN

Removed

Bulgarian Lev

Removed per update

Schematron Rules

Rule Visibility and Documentation Improvements
Rule ID Syntax (XML location) Change Business Rule Reason

IBR-127

cbc:EndpointID[@schemeID = '0007'], cac:PartyIdentification/cbc:ID[@schemeID = '0007'], cbc:CompanyID[@schemeID = '0007']

Added (Rules tab)

[ibr-127] – Swedish organization number MUST be stated in the correct format for endpoints (ibt-034), (ibt-049), party identification (ibt-029), (ibt-046), (ibt-060), and legal entities (ibt-030), (ibt-047), (ibt-061).

The rule was previously not displayed under the Rules tab.

IBR-082

cbc:ChargeIndicator

Added (Rules tab)

[ibr-082] – Allowance/charge indicator value MUST be either 'true' or 'false'.

The rule was previously not visible under the Rules tab and is now correctly linked at both document and line level.
Removed Rules
Rule ID Syntax (XML location) Change Business Rule Reason

IBR-SR-45

cbc:PaymentDueDate

Removed

[ibr-sr-45] – Due Date (ibt-009) MUST occur at most once.

The UBL 2.1 schema already restricts this to zero or one occurrence, making the Schematron rule redundant.
Code List Alignment
Rule ID Syntax (XML location) Change Business Rule Reason

IBR-CL-03, IBR-CL-04, IBR-CL-05

Currency code elements (ISO 4217)

Change

Currency code MUST belong to the ISO 4217 code list.

Updated to reflect latest ISO 4217 changes (addition of XCG, removal of ANG and BGN).

IBR-CL-10, IBR-CL-11, IBR-CL-21, IBR-CL-26

Identifier scheme (ICD)

Change

Scheme identifier MUST belong to the ISO 6523 ICD code list.

Updated to include new scheme identifiers (0245, 0246, 0247, 0248) and correct formatting for 0244.

IBR-CL-25

Electronic Address Scheme (EAS)

Change

Electronic address scheme identifier MUST belong to the EAS code list.

Updated to include new scheme identifiers (0242, 0245, 0246, 0248).

EN16931 Schematron Updates

Updated Rules
Rule ID Syntax (XML location) Change Business Rule Reason

BR-B-02

VAT Category (cac:TaxCategory/cbc:ID, cac:ClassifiedTaxCategory/cbc:ID)

Change

[br-b-02] – An invoice that contains an Invoice line (BG-25), a Document level allowance (BG-20) or a Document level charge (BG-21) where the VAT category code (BT-151, BT-95, BT-118 or BT-102) is “Split payment" shall not contain an invoice line (BG-25), a Document level allowance (BG-20) or a Document level charge (BG-21) where the VAT category code (BT-151, BT-95, BT-118 or BT-102) is “Standard rated”.

Extended to include BT-118, ensuring consistency across all applicable VAT category occurrences.

BR-CO-26

cac:Party

Change

[br-co-26] – In order for the buyer to automatically identify a supplier, the Seller identifier (BT-29), the Seller legal registration identifier (BT-30) and/or the Seller VAT identifier (BT-31) shall be present.

Excludes identifiers with schemeID SEPA from satisfying the rule, improving accuracy of seller identification.

UBL-CR-674

cbc:PrimaryAccountNumberID

Change

[ubl-cr-674] – A UBL invoice should not include the PrimaryAccountNumber schemeID.

Corrected element reference from PrimaryAccountNumber to PrimaryAccountNumberID to align with UBL 2.1.

UBL-SR-23

cac:PartyTaxScheme/cbc:CompanyID

Change

[ubl-sr-23] – Seller tax representative VAT identifier shall occur maximum once, if the Seller has a tax representative.

Simplified XPath context to improve consistency and robustness of validation.

BR-CL-01

cbc:InvoiceTypeCode, cbc:CreditNoteTypeCode

Change

[br-cl-01] – The document type code MUST be coded by the invoice and credit note related code lists of UNTDID 1001.

Updated code lists: removed 502 and 503 from InvoiceTypeCode; added 502 and 503 to CreditNoteTypeCode.
Added Rules
Rule ID Syntax (XML location) Change Business Rule Reason

UBL-SR-56

cac:OriginatorDocumentReference/cbc:ID

Added

[ubl-sr-56] – An Invoice shall contain maximum one Originator document reference identifier (BT-17).

Introduced to enforce cardinality constraint not covered by schema validation.

IBR-127:

Previous Behavior: The rule validating Swedish organization numbers existed but was not visible under the Rules tab and was not clearly linked to all applicable elements.

New Behavior: The rule is now correctly displayed under the Rules tab and linked to endpoints, party identification, and legal entity identifiers using schemeID 0007.

Justification: This change improves rule visibility and ensures consistent validation across all applicable business terms without altering the validation logic itself.

IBR-SR-45:

Previous Behavior: Schematron validation enforced that cbc:PaymentDueDate (ibt-009) MUST occur at most once in the document.

New Behavior: The Schematron rule enforcing the maximum occurrence of cbc:PaymentDueDate has been removed.

Justification: The UBL 2.1 schema already restricts cbc:PaymentDueDate to zero or one occurrence. Maintaining this rule in Schematron duplicated schema-level validation and added no additional implementation value.

IBR-082:

Previous Behavior: The allowance/charge indicator rule existed but was not visible under the Rules tab and was not consistently linked at document and line level.

New Behavior: The rule validating cbc:ChargeIndicator is now correctly displayed under the Rules tab and linked to Allowance/Charge Amount at both document and line level.

Justification: This ensures consistent validation of boolean values and improves transparency for implementers without changing the underlying business requirement.

IBR-CL-26:

Previous Behavior: The ISO 6523 ICD code list value 0244 was defined without a required trailing space in the validation artefact. As a result, instances containing the value `0244 ` (with the correct trailing space as defined in the maintained code list) could incorrectly fail validation.

New Behavior: A trailing space has been added to the ISO 6523 ICD code list value `0244 ` in the validation artefact. Validation now correctly aligns with the maintained ISO 6523 ICD code list representation.

Justification: The omission of the trailing space was a formatting inconsistency in the validation artefact. Adding the space ensures full consistency with the maintained ISO 6523 ICD code list and prevents unintended validation failures due to whitespace mismatches.

Code List Alignment (Schematron):

Previous Behavior: Schematron validation enforced code list values based on the previous versions of ISO 4217, ICD, and EAS code lists.

New Behavior: Validation artefacts have been updated to reflect the latest code list versions:

  • ISO 4217: Added XCG; removed ANG and BGN

  • ICD: Added 0245, 0246, 0247, 0248

  • EAS: Added 0242, 0245, 0246, 0248

Justification: Ensures full alignment between maintained code lists and Schematron validation artefacts, preventing validation inconsistencies and supporting newly introduced identifiers and currency codes.

BR-B-02:

Previous Behavior: The rule validated that invoices containing “Split payment” VAT category (BT-151, BT-95, BT-102) must not include “Standard rated” VAT categories.

New Behavior: The validation now includes BT-118, ensuring the rule applies consistently across all VAT category occurrences.

Justification: Improves completeness and consistency of validation across all relevant EN16931 business terms.

BR-CO-26:

Previous Behavior: Any Seller identifier (BT-29), including those with schemeID SEPA, could satisfy the rule.

New Behavior: Identifiers with schemeID SEPA are excluded from validation.

Justification: Prevents misuse of non-identification schemes and ensures only valid business identifiers are considered.

UBL-CR-674:

Previous Behavior: The rule referenced a non-standard element PrimaryAccountNumber.

New Behavior: The rule now correctly references PrimaryAccountNumberID.

Justification: Aligns validation with the UBL 2.1 data model and prevents incorrect validation behavior.

UBL-SR-23:

Previous Behavior: The rule had invalid XPath (cac:Party/cac:PartyTaxScheme/…​) which could lead to inconsistent evaluation.

New Behavior: The XPath has been corrected to cac:PartyTaxScheme/cbc:CompanyID.

Justification: Improves robustness and ensures consistent validation across different document contexts.

BR-CL-01:

Previous Behavior: UNTDID 1001 code lists included outdated allocations for codes 502 and 503.

New Behavior: - Codes 502 and 503 removed from InvoiceTypeCode - Codes 502 and 503 added to CreditNoteTypeCode

Justification: Ensures alignment with the latest UNTDID 1001 code list and correct document classification.

UBL-SR-56:

Previous Behavior: No explicit Schematron rule enforced the maximum occurrence of Originator document reference identifier (BT-17).

New Behavior: A new rule ensures that at most one cac:OriginatorDocumentReference/cbc:ID is present.

Justification: Adds explicit validation for a business constraint not enforced by schema alone, improving interoperability and consistency.

Action Items for Implementers

  • Review the updated visibility and linkage of Schematron rules in your validation environment.

  • Schematron validation artefacts have been updated to align with the latest Code Lists (EAS, ICD, ISO 4217). Ensure your validation environment reflects these updates.

  • Verify support for newly added identifier schemes (EAS and ICD) and currency codes (ISO 4217), and ensure deprecated values are no longer used.

  • Review EN16931 Schematron rule updates and assess impact on validation logic, in particular:

    • VAT category validation (BR-B-02), now including BT-118.

    • Seller identification logic (BR-CO-26), excluding identifiers with schemeID SEPA.

    • Document type code validation (BR-CL-01) aligned with latest UNTDID 1001 code lists.

    • XPath simplifications and corrections (e.g. UBL-SR-23, UBL-CR-674).

    • New cardinality constraint for Originator document reference (UBL-SR-56).

  • Verify Credit Note implementations reference IBT-003 as Credit note type code.

  • Re-test validation scenarios to identify potential changes in behaviour (e.g. reduced false positives/negatives due to rule corrections).

  • No new fundamental business constraints have been introduced; however, validation behaviour may change due to rule corrections, extended coverage, and alignment with code lists and UBL structure.

Support

For support and clarification:

https://peppol.org/tools-support/service-desk/

Version 1.1.0

Maintained by PoAC

Applies to

PINT EU (Peppol International Invoice – European Specialization)

Release Date

November 2025

Status

Final

What’s new in this release?

This release updates the PINT EU specification to align with:

  • PINT base specification version 1.1.2.

  • Peppol BIS Billing 3.0 requirements.

  • Latest Peppol and EN 16931 validation artefacts.

  • Changes in this version:

    • Alignment with PINT base specification version 1.1.2.

    • Adoption of Peppol BIS Billing 3.0 without semantic deviations.

    • Inclusion of relevant updates inherited from PINT base (see below).

    • Consolidation of Schematron layers:

      • EN 16931-specific PINT rules.

      • Peppol-specific PINT rules.

      • Shared PINT rules.

  • Changes inherited from PINT Base (Version 1.1.2) *

The PINT EU specification is based on PINT general version 1.1.2 and therefore inherits the following updates.

  • Code List Updates:

    • Updates to ICD code list:

      • Added codes:

        • 0241

        • 0242 (OpenPeppol Service Provider Identification Scheme (SPIS))

        • 0243

        • 0244 (Tax Identification (Tax ID), Nigeria)

    • Updates to EAS:

      • Added code:

        • 0244 (Tax Identification (Tax ID), Nigeria)

    • Updates to ISO3166-1:Alpha2:

      • Updated country name for code:

        • BS

    • Updates to ISO4217:

      • Added:

        • CNH (Renminbi offshore)

      • Removed:

        • CUC (Deprecated)

  • Schematron Updates:

    • New rule introduced:

      • IBR-SR-63

        • Context: cbc:CustomizationID

        • Rule: Specification identifier must not contain the wildcard character '*'

  • Impact: Implementers must ensure that cbc:CustomizationID values are exact and do not include wildcard characters.

Version Information

PINT General 1.1.2

PINT EU

1.1.0

Applies to

PINT EU Billing.

Reviewed

-

Overview

This release defines the European specialization of the Peppol International Invoice (PINT EU).

The specification provides:

  • A Semantic Model aligned with EN 16931.

  • A Syntax Binding based on Peppol BIS Billing 3.0.

  • BIS-aligned implementation guidance.

  • Normative codelists required for compliant implementations.

  • Validation artefacts structured across multiple Schematron layers.

The objective is to ensure semantic interoperability, regulatory alignment, and consistent implementation across the European Peppol network.

Data Model

No Change.

Documentation

No Change.

Code Lists

Changes inherited from PINT General 1.1.2 version.

Schematron

Changes inherited from PINT General 1.1.2 version.

Action Items for Implementers

Implementers SHALL:

  • Align implementations with PINT base version 1.1.2.

  • Ensure full compliance with Peppol BIS Billing 3.0.

  • Validate documents using all applicable Schematron layers:

    • EN 16931-specific rules.

    • Peppol-specific rules.

    • Shared PINT rules.

  • Use only values from the defined normative codelists.

  • Ensure semantic and technical consistency across all document instances.

Support

For support and clarification:

https://peppol.org/tools-support/service-desk/

Version 1.0.0

Maintained by PoAC

Applies to

PINT EU (Peppol International Invoice – European Specialization)

Release Date

October 2025

Status

Final

What’s new in this release?

This release updates the PINT EU specification to align with:

  • PINT base specification version 1.1.2.

  • Peppol BIS Billing 3.0 requirements.

  • Latest Peppol and EN 16931 validation artefacts.

  • Changes in this version:

    • Alignment with PINT base specification version 1.1.2.

    • Adoption of Peppol BIS Billing 3.0 without semantic deviations.

    • Inclusion of relevant updates inherited from PINT base.

    • Consolidation of Schematron layers:

      • EN 16931-specific PINT rules.

      • Peppol-specific PINT rules.

      • Shared PINT rules.

  • Key inherited updates from PINT Base (1.1.2):

    • Code Lists:

      • ICD: Added 0241, 0242, 0243, 0244

      • EAS: Added 0244

      • ISO3166-1:Alpha2: Updated country name for BS

      • ISO4217: Added CNH, removed CUC

    • Schematron:

      • New rule IBR-SR-63 restricting wildcard '*' usage in cbc:CustomizationID

    • Impact:

      • cbc:CustomizationID MUST NOT contain wildcard characters.

      • Implementers SHALL review and update validation logic accordingly.

Version Information

PINT General 1.1.1

PINT EU

1.0.0

Applies to

PINT EU Billing

Reviewed

-

Overview

This release defines the European specialization of the Peppol International Invoice (PINT EU).

The specification provides:

  • A Semantic Model aligned with EN 16931.

  • A Syntax Binding based on Peppol BIS Billing 3.0.

  • BIS-aligned implementation guidance.

  • Normative codelists required for compliant implementations.

  • Validation artefacts structured across multiple Schematron layers.

The objective is to ensure semantic interoperability, regulatory alignment, and consistent implementation across the European Peppol network.

Data Model

  • Semantic Model:

    • Defines the business information requirements aligned with EN 16931.

    • Includes:

      • Business terms.

      • Cardinality constraints.

      • Data types and formats.

      • Business rules and conditions.

      • Relationships between elements.

  • Syntax Binding:

    • Provides the technical representation based on Peppol BIS Billing 3.0.

    • Ensures:

      • Deterministic mapping from semantic model to XML.

      • Compliance with Peppol technical constraints.

      • Interoperable document structure across implementations.

Documentation

  • BIS Documentation:

    • Introduction and scope.

    • Business processes and usage.

    • Implementation guidance.

  • Technical Documentation:

    • BIS identifiers.

    • XML schemas and namespaces.

    • Data types and structure definitions.

  • Compliance:

    • Sending compliance requirements.

    • Receiving compliance requirements.

    • Network interoperability constraints.

Code Lists

The following normative codelists are used within the PINT EU specification:

  • AlignedTaxCat (Aligned tax category codes).

  • UNCL5189 (Allowance or charge identification code – Peppol subset).

  • UNCL7161 (Charge reason code).

  • ISO3166-1:Alpha2 (Country codes).

  • ISO4217 (Currency codes).

  • UNCL2005 (Date/time/period function code – Peppol subset).

  • UNCL1001 (Document name code – invoice type).

  • EAS (Electronic Address Scheme).

  • UNCL1153 (Invoiced object identifier scheme).

  • ICD (ISO 6523 ICD list).

  • UNCL7143 (Item type identification code).

  • IANAMT (Media types – PINT subset).

  • UNCL4461 (Payment means code).

  • UNECERec20 (Unit codes).

  • SEPA (SEPA indicator).

  • VATEX (VAT exemption reason codes).

Schematron

Validation artefacts are structured into three distinct Schematron layers:

  • EN 16931-specific PINT rules:

    • Align with the European semantic standard for e-invoicing.

    • Ensure:

      • Mandatory business term compliance.

      • Cardinality validation.

      • VAT and totals calculation consistency.

      • Code list validation.

  • Peppol-specific PINT rules:

    • Extend EN 16931 rules with Peppol network constraints.

    • Enforce:

      • Peppol usage restrictions.

      • Network-specific business rules.

      • Interoperability requirements.

  • Shared PINT rules:

    • Provide reusable validation logic across PINT specifications.

    • Ensure:

      • Consistent rule definitions.

      • Reusability across jurisdictions.

      • Harmonized validation behaviour.

These layers together ensure full semantic and technical conformance.

Action Items for Implementers

Implementers SHALL:

  • Align implementations with PINT base version 1.1.1.

  • Ensure full compliance with Peppol BIS Billing 3.0.

  • Validate documents using all applicable Schematron layers:

    • EN 16931-specific rules.

    • Peppol-specific rules.

    • Shared PINT rules.

  • Use only values from the defined normative codelists.

  • Ensure semantic and technical consistency across all document instances.

Support

For support and clarification:

https://peppol.org/tools-support/service-desk/