Peppol flows
Sending an invoice
The flow for sending an invoice via the Peppol network follows this scheme:
- The ERP sends the invoice to the Peppol access point (AP1)
- AP1 transmits the invoice via the Peppol network
- The Peppol network routes the invoice to the recipient's access point (AP2)
- AP2 notifies the customer's system (webhook or other mechanism)
- The customer's system retrieves the invoice from AP2
ERP ---> AP1 (send) ---> Peppol network ---> AP2 (receive) ---> Customer system
Customer response
The response flow follows the reverse path:
- The customer's system sends its response to access point AP2
- AP2 transmits via the Peppol network
- The network routes it to AP1
- AP1 notifies the ERP (webhook)
- The ERP retrieves the data from AP1
Customer system ---> AP2 ---> Peppol network ---> AP1 ---> ERP
Notes on access point configuration
Warning: You must use a single AP (Access Point) for both sending AND receiving. It is not possible to use two distinct APs (one to send, one to receive) with the same Peppol identifier.
Why a single AP for both sending AND receiving?
- Your Peppol identifier is registered in the directory with a single AP address
- Return messages (invoice acceptance/rejection, statuses) are sent to that address
- If you send via an AP different from the one registered for receiving, the responses cannot be processed correctly
Problematic example:
- You send an invoice via Scrada
- Your Peppol ID in the directory points to e-invoice.be
- The customer rejects the invoice
- The Peppol rejection message is sent to the AP associated with your Peppol identifier, i.e. e-invoice.be
- e-invoice.be receives a rejection for an invoice it has never seen, and your ERP may not even be connected to this AP if your initial idea was, for example, not to handle supplier invoices