コンテンツへスキップ
ブログに戻る
E-procurement公開日 2026年6月2日7 分で読めます

E-procurement with Peppol: orders, responses and despatch advice

Peppol is more than invoicing. Learn how Orders (T01), Order Responses (T76) and Despatch Advice (T16) digitise the whole procure-to-pay flow.

When people hear "Peppol" they usually think of e-invoices. But the network also standardises the documents exchanged earlier in a transaction — the post-award procurement messages. Digitising these is where a lot of real efficiency lives.

The order (T01)

The Order is the buyer's formal request to purchase. It carries the order lines, quantities, prices, delivery information and references. As a Peppol BIS 3.0 document in UBL 2.1, it replaces paper POs and ad-hoc EDI with a standard both sides understand.

The order response (T76)

The supplier replies with an Order Response: accept, reject, or propose changes — at document level or line by line. This confirmation step removes ambiguity before goods are shipped and creates a clean, referenced audit trail.

The despatch advice (T16)

When the goods ship, the Despatch Advice tells the buyer exactly what is on the way: items, delivered quantities, packaging, weights, carrier and delivery address. It is the link between the order and goods receipt, enabling smooth three-way matching against the later invoice.

Why digitise the whole flow

  • Fewer manual errors — structured data instead of PDFs and emails.
  • Faster cycles — automatic confirmation and shipment notifications.
  • Clean matching — order, despatch and invoice reference each other.

Doing it with MyInvoice

MyInvoice generates all three documents from a simple CSV — /v1/order, /v1/order-response and /v1/despatch-advice — each serialised to Peppol BIS 3.0 UBL 2.1 and validated against the official Peppol transaction Schematron. Importantly, procurement documents are validated with their own rules, not the EN 16931 invoice rules, so the feedback is always relevant.