| version | 1.0 |
|---|---|
| published |
...
- Mercurius: it is the centralized mailroom for reception and routing of all e-Procurement related electronic and structured documents to and from the public sector. Mercurius thereby serves the public sector in their automation projects, and ensures consistency throughout all public sector entities.
- PEPPOL: it is the "new way of posting", suited to structured electronic documents. Mercurius is fully aligned with the PEPPOL model. It is exclusively connected through a PEPPOL accesspoint
- Simpl.ePRIOR: interface with the public sector entities, suited to their context, and more specifically aligned with the technology in use on the public sector integrators.
- Mercurius portal: provides track and trace function to staff of entities using Mercurius platform. the portal reuses the Network infrastructure (proxy) and the Authentication and Authorization service
Context of this document
...
This document is about the Simpl.ePRIOR interface defined on the right side of the schema : it describes the interaction between the Mercurius platform and the Public sector, the customers. The other flows aren't part of this document.
Scope covered by this document
...
- the consumer collects incoming invoice:
- the consumer performs a submitInboxRequest on behalf of the target business entity→ in return he gets the list of new documents available in his inbox.
- we assume that an invoice is waiting to be picked up
- we also assume that it is a PEPPOL BISv3 Invoice (see later form more explanations over document formats, BISv2 and BIS v3)
- the consumer performs a retrieveRequest to pick up the invoice
- the consumer performs a mark request to notify Mercurius that it successfully retrieved the invoice, and that the invoice can be removed from the business entity's inbox
- the consumer performs a submitInboxRequest on behalf of the target business entity→ in return he gets the list of new documents available in his inbox.
- The consumer performs the appropriate business processing. This phase is out of scope of the current process. It ends up with a possible response to the original document sender
- The consumer performs a submitDocument Request to posts a response to the original document sender, notifying him of the results of the processing by the business entity. It uses the following document format: PEPPOL BIS v2 MessageLevelResponse (MLR).
Sequences of operations
Document conformance
...
the following 2 table summarize the key information about the supported document formats.
Format specifications
| Document format | UBL DocumentTypeCode | syntax (XSD) | semantic | status |
|---|---|---|---|---|
BIS V2 Invoice | 380 |
| ||
BIS V2 Credit Note | 81 |
| ||
| BIS V3 invoice/CN | cf http://docs.peppol.eu/poacc/billing/3.0/codelist/UNCL1001-inv/ | http://docs.peppol.eu/poacc/billing/3.0/ | EN-compliant | |
BIS V3 Credit Note | ||||
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 | Integrator 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.
...