The main reason for this is to have a worldwide adopted standard for message exchange, but also to make sure that we are compliant with EU guidelines regarding e-invoicing, ViDA and VAT reporting.
Bunzl Continental Europe EDI will not prioritize the Peppol framework only for invoices, but will also use and promote the usage of Peppol/UBL messages for orders, order responses and despatch notes.
Nonetheless, we are not looking to replace the existing and well-functioning but not Peppol-based EDI connections with Peppol, unless (in the future) legislation compels us.
Why Peppol?
The messages supported by Peppol are considered reliable and are compliant with the latest and future EU regulations. Peppol messages encompass localized versions, implementations of the core EU standard and are compliant with VAT regulations.
More and more ERP systems support the UBL messages by Peppol, which means that development (if needed) and deployment should be much easier for both parties.
The Peppol framework, although a European initiative, is also adopted in several countries outside the EU, including the USA and Australia.
The use of the Peppol network makes not only bilateral agreements (originally to secure communication, record responsibilities etc.), but also the cumbersome setup of AS2, X.400 and sFTP connections with each EDI partner / service provider redundant.
Peppol for customers
Bunzl will accommodate sending messages and receiving messages in Peppol supported formats for all companies that are connected to our centralized eTrade solutions.
When you as a customer request a connection to send orders, receive invoices or other documents, we will ask you to send them via Peppol. Creating those connections will be without any additional cost.
Other, non-standardized connections can result in extra cost for setup and communication.
When setting up a Peppol connection for orders we will accept all Peppol BIS variants.
When setting up a Peppol connection for invoices, we will use the CIUS you have declared in your Peppol registration.
Certification of the endpoints is not necessary as long as you use a registered Peppol gateway.
You can easily request a Peppol invoice connection by entering your details in this form.
Peppol for suppliers
Bunzl has been implementing full Order2Invoice processes with suppliers for over 10 years. Those integrations aim to include orders, order responses, despatch notes and invoices.
Our suppliers need to implement all the aforementioned Peppol UBL message types and to connect via a Peppol Gateway. Semantically, the requirements will not be different from when EANCOM messages used to be the preferred syntax, except that the use of GTIN’s and GLN’s in the EANCOM messages are no longer needed in Peppol UBL, and that eliminates the need to have a contract for a paid service with your local GS1 organization.
Orders, order responses and despatch notes shall be exchanged with our suppliers according to the datamodels that you can find in the downloads. The invoice can be sent in line with your local CIUS as Bunzl accepts any CIUS that is compliant with the Peppol Core Invoice or PINT formats.
Peppol message specs
As Peppol has not declared a clear CIUS for orders, order responses and despatch notes, Bunzl has created documentation for you which states the minimum of data that you should send. You are allowed to include extra information, but that information will not be processed in our systems. Click here to go to the DOWNLOAD CENTER to download our message specifications based on Peppol BIS3 for orders, order responses and despatch advices.