May 6th, 2020
We must notify you to be aware that Peppol Bis 3.0 Schematron updates were released on May 1st, 2020. This means that the updated Schematron rules set will be valid from May 15th, 2020. If you are generating PEPPOL BIS 3.0 documents yourself, then you must follow the new Schematron rule set from May 15th, 2020. For an overview of which PEPPOL BIS 3.0 documents are affected, see here.
At mySupply we will of course update Schematrons and standard conversions for you, who are using our VAX 360 solution. That means you don’t have to do anything. For those of you who have costomised adjustments in your VAX 360 solution, there may be changes. We will investigate what consequences it might have for your VAX 360 solution, and then we will contact you. For those using our VAX 360 solution, the Schematron update will take effect with the next VAX release on May 14th, 2020 and go into production on May 27th, 2020.
Phase out of BIS 2.0 documents
We must also notify you that invoicing of BIS 2.0 documents has expired on May 15th. Thus, the BIS 3.0 specifications are the mandatory specification for all document types. For more information see here and here.
Attachment error – updated May 6th
In connection with the Peppol Schematron release, which is valid from May 15th 2020, a validation has been made, which means that more Peppol BIS 3.0 invoices and credit notes will fail from May 15th 2020.
The error is related to attached documents and the use of “AdditionalDocumentReference” and will refer to the use of “Invoice Object Identifier”. The error must be corrected if you generate Peppol BIS Billing 3.0 documents yourself. As the recipient of the documents, you can see the error if the sender does not update his invoices in accordance with the new validation rules.
More precisely, the error occurs if you specify DocumentTypeCode = ”130” in the case of attachments, as that code is reserved for the “Object Identifier”.
An “Object Identifier” is a way to specify at the invoice or invoice line level, the “object” an invoice(line) relates to. If the invoice is a calculation for a particular reading location, then the meter number can be stated as in the example below, where “AEV” is the code for “Reading location”.
<cbc: ID schemeID = “AEV”> Meter-1234 </cbc: ID>
<Cbc: Document Type Code> 130 </ CBC: Document Type Code>
</ Cac: AdditionalDocumentReference>
Thus, DocumentTypeCode = ”130” may only appear as in the example above, and not with other elements of the “AdditionalDocumentRefernce” class.
See section 5.9 in “Guidance on Core Invoice Usage Specification”.
For questions, contact us
Please contact us if you have any questions.