Envelope for files to and from PEPPOL
Envelope for files to and from PEPPOL
Envelope
When you send files using HubBroker to other PEPPOL Access Points you will need to wrap the payload (invoice, order, etc.) in an envelope, an SBDH - Standard Business Document Header. The same envelope is used when you receive files from PEPPOL.
The payload must be put between the tags </StandardBusinessDocumentHeader> and </StandardBusinesDocument> (line 32 and 35 in the sample SBDH below) and the contents is then transferred to the next PEPPOL Access Point.
Please find the OpenPEPPOL SBDH envelope specification at: https://github.com/OpenPEPPOL/documentation/tree/master/TransportInfrastructure.
Schemas and sample files can be found at http://www.gs1.com/standard-business-document-header-sbdh.
Specific requirement: RelayOperatorIdentifier
We have added relayoperatorid for the internal routing of HubBroker, please see line 9 in the SBDH sample below. You will be assigned a relayoperatorid by us during the implementation project. You should always use it in the files you send to PEPPOL. You also have to be able to handle it in incoming files from PEPPOL.
UUID
We suggest the use of the same UUID as InstanceIdentifier and ID to enable end-to-end Track & Trace across multiple PEPPOL Access Point hops. If you use UUID we will respect it and reuse it in the transaction to the receiving PEPPOL Access Point. In the sample below the message identifier uuid:0088-5567212047-201608231627339-161944 has been used.
Here's a regular expression that matches common UUID patterns:
\b(uuid:){0,1}\s*([a-f0-9\\-]*){1}\s*
Use of PEPPOL identifiers
PEPPOL Policy for use of Identifiers v.3.0.pdf explains the use of various identifiers in PEPPOL, such as the syntax for identifiers used for documents, senders and receivers.
SBDH Sample
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<standardbusinessdocument xmlns="http://www.unece.org/cefact/namespaces/StandardBusinessDocumentHeader">
<standardbusinessdocumentheader>
<headerversion>1.0</headerversion>
<sender>
<identifier authority="iso6523-actorid-upis">0007:5567212047</identifier>
</sender>
<sender>
<identifier authority="relayoperatorid">0000</identifier>
</sender>
<receiver>
<identifier authority="iso6523-actorid-upis">0007:5567212047</identifier>
</receiver>
<documentidentification>
<standard>urn:oasis:names:specification:ubl:schema:xsd:Invoice-2</standard>
<typeversion>2.1</typeversion>
<instanceidentifier>uuid:0088-5567212047-201608231627339-161944</instanceidentifier>
<type>Invoice</type>
<creationdateandtime>2015-10-27T15:00:55.110+02:00</creationdateandtime>
</documentidentification>
<businessscope>
<scope>
<type>DOCUMENTID</type>
<instanceidentifier>urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:www.cenbii.eu:transaction:biitrns010:ver2.0:extended:urn:www.peppol.eu:bis:peppol4a:ver2.0::2.1</instanceidentifier>
</scope>
<scope>
<type>PROCESSID</type>
<instanceidentifier>urn:www.cenbii.eu:profile:bii04:ver2.0</instanceidentifier>
</scope>
</businessscope>
</standardbusinessdocumentheader>
<invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2" xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2" xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" xmlns:ccts="urn:un:unece:uncefact:documentation:2" xmlns:qdt="urn:oasis:names:specification:ubl:schema:xsd:QualifiedDatatypes-2" xmlns:udt="urn:un:unece:uncefact:data:specification:UnqualifiedDataTypesSchemaModule:2"> <cbc:ublversionid>2.1</cbc:ublversionid> <cbc:customizationid>urn:www.cenbii.eu:transaction:biitrns010:ver2.0:extended:urn:www.peppol.eu:bis:peppol4a:ver2.0</cbc:customizationid><cbc:profileid>urn:www.cenbii.eu:profile:bii04:ver2.0</cbc:profileid>
<cbc:id>0000-integration-test-20151028-1</cbc:id>
<!-- Imagine the rest of a "PEPPOL Invoice (BIS v2 Profile 4a)" here -->
</invoice>
</standardbusinessdocument>
Category: FAQs
Last date of update: 24.09.2018
