version	1.1
published	27 Sep 2019
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.

...

Code Block

language	xml
title	SubmitInboxRequestsubmitInboxRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:head=”http://fsb.belgium.be/header”  xmlns:v1="http://fsb.belgium.be/einvoicing/simpleprior/v1_00">
   <soapenv:Header>
      <head:fsbHeader>
         <head:messageId>9397cbe5-174f-479f-941d-2371129acb05</head:messageId>
      </head:fsbHeader>
   </soapenv:Header>
   <soapenv:Body>
      <v1:submitInboxRequest>
         <v1:receiverId>?</v1:receiverId>
         <v1:senderId>?</v1:senderId>
      </v1:submitInboxRequest>
   </soapenv:Body>
</soapenv:Envelope>

...

Code Block

language	xml
title	SubmitInboxResponsesubmitInboxRequestResponse

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:v1="http://fsb.belgium.be/einvoicing/simpleprior/v1_00>
   <soapenv:Header>
      <wsse:Security soap:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
         <wsu:Timestamp wsu:Id="Timestamp-HvumButHp993jGDym7t89Q22" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
            <wsu:Created>2018-10-03T10:07:55Z</wsu:Created>
            <wsu:Expires>2018-10-03T10:12:55Z</wsu:Expires>
         </wsu:Timestamp>
	<!—More elements on security and signature:-->
      </wsse:Security>    </soapenv:Header>
   <soapenv:Body>
      <v1:submitInboxRequestResponse>
         <v1:documentGroup>
            <!--Zero or more repetitions:-->
            <v1:documentReference>
               <v1:documentId>?</v1:documentId>
               <v1:documentTypeCode>?</v1:documentTypeCode>
               <v1:receiverId>?</v1:receiverId>
               <v1:senderId>?</v1:senderId>
            </v1:documentReference>
         </v1:documentGroup>
      </v1:submitInboxRequestResponse>
   </soapenv:Body>
</soapenv:Envelope>

...

Code Block

language	xml
title	SubmitInboxRequestretrieveDocument

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:head=”http://fsb.belgium.be/header”  xmlns:v1="http://fsb.belgium.be/einvoicing/simpleprior/v1_00">
   <soapenv:Header>
      <head:fsbHeader>
         <head:messageId>692da97e-e4a0-4ed0-b0bd-6e3f01e1e601</head:messageId>
      </head:fsbHeader>
   </soapenv:Header>
   <soapenv:Body>
      <v1:retrieveDocument>
         <v1:receiverId>?</v1:receiverId>
         <v1:senderId>?</v1:senderId>
         <v1:documentType>?</v1:documentType>
         <v1:documentId>?</v1:documentId>
      </v1:retrieveDocument>
   </soapenv:Body>
</soapenv:Envelope>

...

Code Block

language	xml
title	RetrieveDocumentResponseretrieveDocumentResponse

<soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/  xmlns:v1="http://fsb.belgium.be/einvoicing/simpleprior/v1_00>
   <soapenv:Header>
      <wsse:Security soap:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
         <wsu:Timestamp wsu:Id="Timestamp-HvumButHp993jGDym7t89Q22" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
            <wsu:Created>2018-10-03T10:07:55Z</wsu:Created>
            <wsu:Expires>2018-10-03T10:12:55Z</wsu:Expires>
         </wsu:Timestamp>
	<!—More elements on security and signature:-->
      </wsse:Security>    </soapenv:Header>
   <soapenv:Body>
      <v1:retrieveDocumentResponse>
         <v1:receivedDate>yyyy-MM-dd</v1:receivedDate>
         <v1:document>
            <!--Valid UBL document returned-->
         </v1:document>
      </v1:retrieveDocumentResponse>
   </soapenv:Body>
</soapenv:Envelope>

...

Code Block

language	xml
title	MarkDocumentRequestmarkDocument

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:head=”http://fsb.belgium.be/header”  xmlns:v1="http://fsb.belgium.be/einvoicing/simpleprior/v1_00">
   <soapenv:Header>
      <head:fsbHeader>
         <head:messageId>692da97e-e4a0-4ed0-b0bd-6e3f01e1e601</head:messageId>
      </head:fsbHeader>
   </soapenv:Header>
   <soapenv:Body>
      <v1:markDocument>
         <v1:receiverId>?</v1:receiverId>
         <v1:senderId>?</v1:senderId>
         <v1:documentType>?</v1:documentType>
         <v1:documentId>?</v1:documentId>
      </v1:markDocument>
   </soapenv:Body>
</soapenv:Envelope>

...

Code Block

language	xml
title	SubmitDocumentRequestsubmitDocument

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:head=”http://fsb.belgium.be/header”   xmlns:v1="http://fsb.belgium.be/einvoicing/simpleprior/v1_00">
   <soapenv:Header>
      <head:fsbHeader>
         <head:messageId>692da97e-e4a0-4ed0-b0bd-6e3f01e1e601</head:messageId>
      </head:fsbHeader>
   </soapenv:Header>
   <soapenv:Body>
      <v1:submitDocument>
         <v1:document>
            <!--You may enter ANY valid UBL document at this point-->
         </v1:document>
      </v1:submitDocument>
   </soapenv:Body>
</soapenv:Envelope>

...

Code Block

language	xml
title	SubmitDocumentResponsesubmitDocumentResponse

<soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/
xmlns:v1="http://fsb.belgium.be/einvoicing/simpleprior/v1_00">
         <soapenv:Header>
            <wsse:Security soap:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
               <wsu:Timestamp wsu:Id="Timestamp-HvumButHp993jGDym7t89Q22" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
                  <wsu:Created>2018-10-03T10:07:55Z</wsu:Created>
                  <wsu:Expires>2018-10-03T10:12:55Z</wsu:Expires>
               </wsu:Timestamp>
	      <!—More elements on security and signature:-->
            </wsse:Security>          </soapenv:Header>
   <soapenv:Body>
      <v1:submitDocumentResponse>
         <!—When successful ackIndicator is true-->
         <v1:ackIndicator>true</v1:ackIndicator>
		<!—When an exception occurred ackIndicator is false-->
		<v1:ackIndicator>false</v1:ackIndicator>
		-->
      </v1:submitDocumentResponse>
   </soapenv:Body>
</soapenv:Envelope>

...

add PEPPOL BISv3 INVOICE and CREDIT NOTE document formats:
- this This capability will enable G2G exchanges of EN-conformant invoices. itIt requires configuration on teh the simpl.ePRIOR flow.
- It is a high-priority requirement. it It is planned, target date 15 May 2019 .
- for For Mercurius staff only: see page 219 - Outbound (G2B) Invoicing - BIS3 support (secured page).
add a response reception flow: this involves configuring inbound PEPPOL BIS IMR support, and may also require more configuration and more preparation.
adding a PDF plan B to the main flow:
- the current situation generates a lot of burden to the public sector entity that sends the documents: the entity must know in advance for each receiver if he is capable of receiving the PEPPOL BIS format, and find other ways to handle the sendings to other receivers
- to improve this, Mercurius will soon generalize a logic that converts the document and sends it via pdf/email if the receiver does not have suitable receiing capabilities. this way the public sector entities are freed from the cumbersome process described above, and can plan massive use of the outbound flows.

...

The following 2 tables summarize the key information about the supported document formats.

Format specifications

cf.

Document format	UBL DocumentTypeCode	syntax (XSD)	semantic	status, remarks
BIS V2 Invoice	380	UBL-Invoice-2.1.xsd	PEPPOL BIS 5A Billing	in phase out. bidirectional support (in-,outbound).
BIS V2 Credit Note	81	UBL-CreditNote-2.1.xsd	PEPPOL BIS 5A Billing	in phase out. bidirectional support (in-,outbound).	PEPPOL BIS 5A Billing	in phase out. bidirectional support (in-,outbound).
BIS V3 Invoice	http://docs.peppol.eu/poacc/billing/3.0/codelist/UNCL1001-inv/	UBL-Invoice-2.1.xsd	http://docs.peppol.eu/poacc/billing/3.0/	EN-compliant list of authorized identification schemes for party identifiers (enpointID): cf Electronic Address Scheme code list (EAS)
BIS V3 Credit Note	https://docs.peppol.eu/poacc/billing/3.0/codelist/UNCL1001-cn/	UBL-CreditNote-2.1.xsd	http://docs.peppol.eu/poacc/billing/3.0/
BIS V2 Message Level Response (MLR)	301	UBL-ApplicationResponse-2.1.xsd	PEPPOL BIS 36A Message Level Response	in phase out. [TO CHECK] bidirectional support (in-,outbound).
BISV2 Order	////	UBL-Order-2.1.xsd	PEPPOL BIS 28A Ordering	outbound support
Order Response	231	UBL-OrderResponse-2.1.xsdPEPPOL BIS 28A Ordering	PEPPOL BIS 28A Ordering	Not supported, no intake programmed yet
Invoice Response	23	UBL-ApplicationResponse-2.1.xsd	PEPPOL BIS 63A Invoice Response	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. Examples of supplier roles: seller, consignor, creditor, economic operator.
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. Examples of customer roles: buyer, consignee, debtor, contracting authority.

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)	http://fe1.babelway.net/simpleprior/simpleprior?WSDL
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	https://digital.belgium.be/e-invoicing/MercuriusLogin.html
list of PEPPOL receivers registered in smp.belgium.be	https://digital.belgium.be/e-invoicing/PEPPOLinBelgium.html
simpl.ePRIOR relevant documentation on FSB (access, proxy-service)	https://dtservices.bosa.be/fr/services/fsb/demande-dun-service-web-fsb-ou-dun-certificat-fsb/je-demande-dacceder-un-service-web http://dtservices.bosa.be/fr/services/fsb/catalogue/eprocurementservices-s294/documentation-eprocurementservices-s294#S331-MercuriusService%20(Simpl.ePRIOR)
sources of diagrams shown on the page	618233862
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)

Versions Compared

Old Version 16

New Version 17

Key

Format specifications

References

Sample Code

Page Comparison

Versions Compared

Old Version 16

New Version 17

Key

Format specifications

References

Sample Code