2023.10.09 RFCs Post Award Community

Owned by Erwin Wulterkens
Last updated: Nov 21, 2023
2 min read

Update on the Member review:

The received comments have all been addressed. The CMB has made its decision on each comment. You can find the comments and the resolutions in this document.

The Change Management Board has approved several RFCs that are candidates for the upcoming November release. For these RFC solutions have been developed by OpenPeppol. The approval process requires that these solutions must be subject to a review by members. The following documents and artefacts are out for member review:

RFCs for BIS Billing 3.0

Changes to BIS document

  1. A recommendation has been added to the Sales Order Reference element for handling cases where there is no Purchase Order Reference. This clarifies what to do with the mandatory UBL element for Purchase Order Reference. Example file is added which illustrates this.

  2. Text in section 4.6 on negative invoices edited to remove historic comparison to BIS2 and justification for the change. No functional change.

Changes to code lists and validation artefacts

  1. The validation rule identified as PEPPOL-EN16931-R006, which ensures that only one Invoice Object is allowed at the document level in an invoice/credit note, has been removed. This is because it duplicates the European standard rule UBL-SR-04, making it redundant and unnecessary.

  2. The structure of the Peppol Schematron rule set has been improved for better quality. A function that was previously located in the Greek rules section is now correctly positioned alongside other functions.

  3. * Added invoice type codes 326 "Partial invoice" and 384 "Corrected invoice" as synonyms to code 380. 

The BIS documents and artefacts are accessible for review under the following URL:

https://test-docs.peppol.eu/poacc/2023-q4-member-review/billing/3.0/

RFCs for BISes other than Billing-3.0 (Upgrade-3 project)

BIS documentation

  1. Fixed an error in the documentation of semantic datatypes. It previously stated that a Boolean is based on the primitive datatype String, this has been corrected to Boolean. This fix is purely editorial.

Changes to syntax

  1. Order transaction (T01)

    1. Added business terms for all Order Type Codes. Renamed the element cbc:OrderTypeCode from "Consignment Order" to "Order Type" to avoid confusion, as Consignment Order is just one of several types. This change is purely editorial.

Changes to code lists and validation artefacts

  1. Added Order type codes 105 (Purchase order) and 402 "Intermediate handling cross docking order" as synonyms for 220 (Order)

  2. Example file cleanup: Removed listId from <DocumentTypeCode> and ResponseCode> in example files for Invoice Response. Deleted reference to payment in example file 7 in Invoice Response Examples

The BIS documents and artefacts are accessible for review under the following URL:

https://test-docs.peppol.eu/poacc/upgrade-3/2023-q4-member-review/

Peppol PINT Billing

Version 1.0.1

  1. Added Invoice Type codes 326 (partial invoice ) and 384 (corrected invoice) as synonyms for code 380 (commercial invoice).

  2. Various minor edits to text.

The PINT documents and artefacts are accessible for review under the following URL:

https://test-docs.peppol.eu/poacc/pint/2023-q4-dev/pint/

Any comments can be submitted by using the comment template. Please do not alter the template. Any altered template cannot be processed. This template must be mailed to reviews@peppol.eu.

The review period is 4 weeks and ends on 6 November 2023. All comments submitted in the review period will be processed and addressed by the Operating Office.