Home Integration guide Business document messages Changelog

Peppol and EN16931 November 2024 release

All changes in this release are mandatory from Monday, 17th Feburary 2025.

Peppol BIS Billing 3.0 - November 2024 release:
https://docs.peppol.eu/poacc/billing/3.0/2024-Q4/

Peppol BIS version 3 (other profiles) - November 2024 release:
https://docs.peppol.eu/poacc/upgrade-3/2024-Q4/

EN16931 Validation artefacts v.1.3.13:
https://github.com/ConnectingEurope/eInvoicing-EN16931/releases/tag/validation-1.3.13

EN16931 v1.3.13 UBL changes

EN16931 Validation Artefacts v.1.3.13 is a maintenance release that contains updates to code lists.
No new rules have been added, and there are no severity changes to existing validation rules.

All profiles

Code list changes

  • Update validation artafacts with Nov 24 codes #390
    • ISO 4217 (Currency codes)
      • Removed HRK and VEF
      • Added VES, VED and ZWG
    • ISO 6523 ICD
      • Added 0231, 0232, 0233, 0234, 0235, 0236, 0237 and 0238
    • CEF EAS
      • Added 0177 and 0235
    • CEF VATEX
      • Added VATEX-EU-144, VATEX-EU-146-1E and VATEX-EU-159

Peppol changes

Peppol BIS Billing 3.0 - November 2024 release introduces key updates to Peppol BIS Billing documents, including new country-specific validation rules for Germany, updates to Swedish organization number rules, and code list changes.

Changes to “BIS compliance” document

  • Added new compliance rules on how to use sender/receiver identifiers when enveloping a BIS3 message in Peppol Business Message Envelope (SBDH)

Billing

Changes to existing validation rules for Swedish organization numbers

In this release, all existing rules that verify the format and correctness of Swedish organization numbers will be updated to a severity level of FATAL.

New German country-specific validation rules

This release introduces new validation rules for German documents within PeppolBIS, aimed at enhancing alignment with Germany’s XRechnung standard and ensuring greater consistency and compliance.

Please note that most of the new rules have a severity level of FATAL.

New rules

  • German country-specific validation rules have been added, applicable only when both the supplier and customer party country codes are DE.
    • [DE-R-001]-An invoice shall contain information on “PAYMENT INSTRUCTIONS” (BG-16).
      • Severity FATAL
    • [DE-R-015]-The element “Buyer reference” (BT-10) shall be provided.
      • Severity FATAL
    • [DE-R-016]-If one of the VAT codes S, Z, E, AE, K, G, L, or M is used, an invoice shall contain at least one of the following elements: “Seller VAT identifier” (BT-31) or “Seller tax registration identifier” (BT-32) or “SELLER TAX REPRESENTATIVE PARTY” (BG-11).
      • Severity FATAL
    • [DE-R-017]-The element “Invoice type code” (BT-3) should only contain the following values from code list UNTDID 1001: 326 (Partial invoice), 380 (Commercial invoice), 384 (Corrected invoice), 389 (Self-billed invoice), 381 (Credit note), 875 (Partial construction invoice), 876 (Partial final construction invoice), 877 (Final construction invoice).
      • Severity WARNING
    • [DE-R-018]-Information on cash discounts for prompt payment (Skonto) shall be provided within the element “Payment terms” BT-20 in the following way: First segment “SKONTO”, second segment amount of days (“TAGE=N”), third segment percentage (“PROZENT=N”). Percentage must be separated by dot with two decimal places. In case the base value of the invoiced amount is not provided in BT-115 but as a partial amount, the base value shall be provided as fourth segment “BASISBETRAG=N” as semantic data type amount. Each entry shall start with a #, the segments must be separated by # and a row shall end with a #. A complete statement on cash discount for prompt payment shall end with a XML-conformant line break. All statements on cash discount for prompt payment shall be given in capital letters. Additional whitespaces (blanks, tabulators or line breaks) are not allowed. Other characters or texts than defined above are not allowed.
      • Severity FATAL
    • [DE-R-022]-Attached documents provided with an invoice in “ADDITIONAL SUPPORTING DOCUMENTS” (BG-24) shall have a unique filename (non case-sensitive) within the element ″Attached document″ (BT-125).
      • Severity FATAL
    • [DE-R-026]-If “Invoice type code” (BT-3) contains the code 384 (Corrected invoice), “PRECEDING INVOICE REFERENCE” (BG-3) should be provided at least once.
      • Severity WARNING
    • [DE-R-030]-If the group “DIRECT DEBIT” (BG-19) is delivered, the element “Bank assigned creditor identifier” (BT-90) shall be provided.
      • Severity FATAL
    • [DE-R-031]-If the group “DIRECT DEBIT” (BG-19) is delivered, the element “Debited account identifier” (BT-91) shall be provided.
      • Severity FATAL
    • [DE-R-002]-The group “SELLER CONTACT” (BG-6) shall be provided.
      • Severity FATAL
    • [DE-R-003]-The element “Seller city” (BT-37) shall be provided.
      • Severity FATAL
    • [DE-R-004]-The element “Seller post code” (BT-38) shall be provided.
      • Severity FATAL
    • [DE-R-005]-The element “Seller contact point” (BT-41) shall be provided.
      • Severity FATAL
    • [DE-R-006]-The element “Seller contact telephone number” (BT-42) shall be provided.
      • Severity FATAL
    • [DE-R-007]-The element “Seller contact email address” (BT-43) shall be provided.
      • Severity FATAL
    • [DE-R-027]-“Seller contact telephone number” (BT-42) should contain a valid telephone number. A valid telephone should consist of 3 digits minimum.
      • Severity WARNING
    • [DE-R-028]-“Seller contact email address” (BT-43) should contain exactly one @-sign, which should not be framed by a whitespace or a dot but by at least two characters on each side. A dot should not be the first or last character.
      • Severity WARNING
    • [DE-R-008]-The element “Buyer city” (BT-52) shall be provided.
      • Severity FATAL
    • [DE-R-009]-The element “Buyer post code” (BT-53) shall be provided.
      • Severity FATAL
    • [DE-R-010]-The element “Deliver to city” (BT-77) shall be provided if the group “DELIVER TO ADDRESS” (BG-15) is delivered.
      • Severity FATAL
    • [DE-R-011]-The element “Deliver to post code” (BT-78) shall be provided if the group “DELIVER TO ADDRESS” (BG-15) is delivered.
      • Severity FATAL
    • [DE-R-019]-The element “Payment account identifier” (BT-84) should contain a valid IBAN if code 58 SEPA is provided in “Payment means type code” (BT-81).
      • Severity WARNING
    • [DE-R-023-1]-If “Payment means type code” (BT-81) contains a code for credit transfer (30, 58), “CREDIT TRANSFER” (BG-17) shall be provided.
      • Severity FATAL
    • [DE-R-023-2]-If “Payment means type code” (BT-81) contains a code for credit transfer (30, 58), BG-18 and BG-19 shall not be provided.
      • Severity FATAL
    • [DE-R-024-1]-If “Payment means type code” (BT-81) contains a code for payment card (48, 54, 55), “PAYMENT CARD INFORMATION” (BG-18) shall be provided.
      • Severity FATAL
    • [DE-R-024-2]-If “Payment means type code” (BT-81) contains a code for payment card (48, 54, 55), BG-17 and BG-19 shall not be provided.
      • Severity FATAL
    • [DE-R-020]-The element “Debited account identifier” (BT-91) should contain a valid IBAN if code 59 SEPA is provided in “Payment means type code” (BT-81).
      • Severity WARNING
    • [DE-R-025-1]-If “Payment means type code” (BT-81) contains a code for direct debit (59), “DIRECT DEBIT” (BG-19) shall be provided.
      • Severity FATAL
    • [DE-R-025-2]-If “Payment means type code” (BT-81) contains a code for direct debit (59), BG-17 and BG-18 shall not be provided.
      • Severity FATAL
    • [DE-R-014]-The element “VAT category rate” (BT-119) shall be provided.
      • Severity FATAL

Changes in existing rules

  • Changed country-specific rule NL-R-008 to be domestic-only.
    • [NL-R-008] For suppliers in the Netherlands, if the customer is in the Netherlands, the payment means code (cac:PaymentMeans/cbc:PaymentMeansCode) MUST be one of 30, 48, 49, 57, 58 or 59
  • Allow more than one cbc:Note (BT-22) when both the supplier and customer party country codes are DE.
    • [PEPPOL-EN16931-R002]-No more than one note is allowed on document level, unless both the buyer and seller are German organizations.
  • Severity of Swedish country-specific rules SE-R-003, SE-R-004 and SE-R-013, which verify the format of Swedish organization numbers, has been changed from WARNING to FATAL.
    • [SE-R-003]-Swedish organisation numbers should be numeric.
    • [SE-R-004]-Swedish organisation numbers consist of 10 characters.
    • [SE-R-013]-The last digit of a Swedish organization number must be valid according to the Luhn algorithm.

Other profiles

BIS documentation

  • BIS Ordering and Order Only
    • Added sample file and use case which describes consignment orders and vendor-managed inventory

Code list changes

  • Added new codelist with code values SSCC (Serial Shipping Container Code) to the optional attribute that indicates the type/scheme for Transport handling unit identifier (in Despatch Advice)
  • Changes to codelists
    • UNCL7143
      • Added GMN
    • UNCL8273
      • Added ADY, ADZ, AEA, and AEB
    • UNECERec20-11e
      • Added HWE

Changes to syntax

Order transaction (T01)
  • Added optional element ID to AdditionalItemProperty with corresponding update in Use Case 4.
Order Change(T114)
  • Added optional element ID to AdditionalItemProperty.
Order Agreement(T110)
  • Added optional element ID to AdditionalItemProperty with corresponding update in Use Case in Appendix A.
Despatch Advice (T16)
  • Optional attribute added to indicate the scheme of the Transport Handling Unit identifier.
  • Optional Delivery Party added to align with Order.
  • Added optional element ID to AdditionalItemProperty.
Catalogue transaction (T19)
  • Added optional element ID to AdditionalItemProperty with corresponding update in Use Case 5.
Punchout transaction (T77)
  • Added optional element ID to AdditionalItemProperty with corresponding update in Use Case in Appendix A.
  • Added cac:DocumentReference to Certificate.
    • This may contain vital information regarding the label and has a similar function as in Catalogue.