| version | 1.1 |
|---|---|
| published | |
| comment | This page is still the subject of additional validation cycles. Readers are welcome to send questions and/or provide comments by email to mercurius@bosa.fgov.be |
...
The following elements are used in the Simpl.ePRIOR interface. This is part of the required transmission items, on top of that the payload needs to contain a valid UBL document ( retrieve and submit document ). The Mercurius platform validates the UBL is correct based on the document type defined : this is a schematic and format validation against XSD and Schematron. The business content like PO, price, ... is not validated and must be checked by the consumer.
See UBL document definition and UBL document Validation for reference.
| soapenv:Envelope/soapenv:Header/head:fsbHeader/head:messageId | UUID, unique ID for the message |
|---|---|
| soapenv:Envelope/soapenv:Body/.../v1:receiverId | Identifier of the receiving party |
| soapenv:Envelope/soapenv:Body/.../v1:senderId | Identifier of the sender party |
| soapenv:Envelope/soapenv:Body/.../v1:documentType | Type of the document, |
| soapenv:Envelope/soapenv:Body/.../v1:docId | Id of the document as provided by the sender |
| soapenv:Envelope/soapenv:Body/.../v1:DocumentFormatIdentifier | identifier of the document format on teh PEPPOL transport infrastructure [NB: we might change by documentFormatIdentifier at a later stage] |
| soapenv:Envelope/soapenv:Body/.../v1:document | UBL Document, the binary is not inline in the message but transmitted as an attachment. See SOAP with Attachment for further information. |
| soapenv:Envelope/soapenv:Body/.../v1:receivedDate | Date at which the document has been processed by the Mercurius platform |
| soapenv:Envelope/soapenv:Body/.../v1:ackIndicator | Boolean indicating the status of the operation
|
...
The following 2 tables summarize the key information about the supported document formats.
Format specifications
| Document format | UBL DocumentTypeCode ( * ) | syntax (XSD) | semantic | status, remarks |
|---|---|---|---|---|
BIS V2 Invoice | 380 |
| ||
BIS V2 Credit Note | 81 | |||
| BIS V3 Invoice | http://docs.peppol.eu/poacc/billing/3.0/codelist/UNCL1001-inv/ |
| ||
BIS V3 Credit Note | https://docs.peppol.eu/poacc/billing/3.0/codelist/UNCL1001-cn/ | |||
BIS V2 Message Level Response (MLR) | 301 |
| ||
| BISV2 Order | //// | UBL-Order-2.1.xsd | PEPPOL BIS 28A Ordering | outbound support |
Order Response | 231 | Not supported, no intake programmed yet | ||
Invoice Response | 23 | intake programmed, but not yet started |
...
| Mercurius | Mail-room from the Belgian Public sector, for e-Procurement related structured electronic documents |
|---|---|
| PEPPOL | Pan-European Public Procurement Online, PEPPOL enables businesses across Europe and beyond to communicate electronically with public buyers in various stages of the procurement process |
| OpenPEPPOL | OpenPEPPOL is a non-profit international association under Belgian law (Association Internationale Sans But Lucratif – AISBL) and consists of both public sector and private members. The association has assumed full responsibility for the development and maintenance of the PEPPOL specifications, building blocks and its services and implementation across Europe. |
| Integrators | Integrators allow service consumers to access the simpl.ePRIOR service exposed by the Mercurius platform. The service on the Mercurius platform is only accessible to integrators : Federal ( FSB ) or regional ( Magda, ... ) |
| Portal | Also known as the Mercurius portal, it allows customers and suppliers to monitor (track and trace) the documents received and sent. It provides business information (sender, receiver, business status, date, ...) and access to technical information (messages exchanged, technical status, ...) |
| FAS | Federal Authentication Service authenticates authorises users to access the platform |
| Supplier | A supplier is an enterprise that contributes goods or services. Generally, a supply chain vendor manufactures inventory/stock items and sells them to the next link in the chain. Today, these terms refer to a supplier of any good or service. See https://en.wikipedia.org/wiki/Supplier The Peppol definition is the following : The supplier is the legal person or organization who provides a product and/or service. |
| Customer | In sales, commerce and economics, a customer (sometimes known as a client, buyer, or purchaser) is the recipient of a good, service, product or an idea - obtained from a seller, vendor, or supplier via a financial transaction or exchange for money or some other valuable consideration. See https://en.wikipedia.org/wiki/Customer The Peppol definition is the following : The customer is the legal person or organization who is in demand of a product and/or service. |
References
Sample Code
This example is provided without any guarantee or support. It's only to help you and show you how to generate code based on the WSDL definition.
...
| Description | Link |
|---|---|
| wsdl of the backend service (for info) | |
| peppol.eu page about the Belgian PEPPOL authority (PA) | http://peppol.eu/what-is-peppol/peppol-country-profiles/belgium-country-profile/?rel=tab664 |
| official webpage of the Belgian PEPPOL authority | https://openpeppol.atlassian.net/wiki/spaces/Belgium |
| Mercurius platform, portal-site homepage | |
| list of PEPPOL receivers registered in smp.belgium.be | |
| simpl.ePRIOR relevant documentation on FSB (access, proxy-service) | |
| sources of diagrams shown on the page | |
| list of authorized identification schemes for party identifiers (enpointID) | cf page: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/Code+lists, select Electronic Address Scheme code list (EAS) |