How an invoice moves from a seller's ERP to a buyer's ERP through Peppol-style access points — with a validating tax-authority node in the middle for ZATCA-style clearance markets.
Where the invoice originates — SAP, D365, Oracle, or any connected system.
dsConnectMW, acting as the seller's certified access point to the network.
The receiving party's own access point — theirs or a partner provider's.
Where the invoice lands for matching and payment processing.
The Peppol registry (SMP/SML), or — in clearance markets like ZATCA — the tax authority as a validating node.
| Message | Direction | Purpose |
|---|---|---|
| Invoice message | Corner 1 → 4 | The invoice document itself, routed through both access points. |
| Message Level Response (MLR) | Corner 4 → 1 | Confirms technical receipt of the message. |
| Message Level Status (MLS) | Corner 2/3 → sender | Ongoing delivery status as the message moves across the network. |
| Business acknowledgement | Corner 4 → 1 | Confirms the invoice was accepted into the buyer's business process. |
| Application response | Corner 4 → 1 | Formal accept/reject decision at the business level, distinct from technical delivery. |