تخطَّ إلى المحتوى
Peppol BIS 3.0 · T01 · T76 · T16

E-procurement, not just e-invoices

MyInvoice covers the whole post-award procurement flow on the Peppol network. Create Orders, Order Responses and Despatch Advice from a simple CSV — each one serialised to UBL 2.1 and validated against the official Peppol transaction rules.

The documents your trading partners send before the invoice

Invoicing is only the last step of a business transaction. Before an invoice is ever issued, buyers and suppliers exchange orders, confirmations and shipment notifications. On the Peppol network these "post-award" messages have their own standardised formats and business rules.

MyInvoice speaks all three of the core procurement documents, so you can digitise your full procure-to-pay process — order, confirm, ship and bill — through a single, consistent API instead of stitching together separate EDI tools.

Supported e-procurement documents

Every document is produced as Peppol BIS 3.0 UBL 2.1 and validated before it is returned.

T01

Order

The buyer's purchase order

The Order is the buyer's formal request to purchase goods or services from a supplier. It carries the order lines, quantities, delivery details and references that kick off the transaction.

  • Order header, buyer & seller parties, delivery and references
  • Multiple order lines with quantities, units and prices
  • Supports order-only and ordering profiles

Peppol BIS 3.0 Order — UBL 2.1 XML

T76

Order Response

The supplier's answer

The Order Response lets the supplier accept, reject or propose changes to an order — fully or line by line — so both sides agree before fulfilment begins.

  • Accept, reject, change or conditionally accept
  • Per-line status with revised quantities where needed
  • References the original order for a clean audit trail

Peppol BIS 3.0 Order Response — UBL 2.1 XML

T16

Despatch Advice

The shipment notification

The Despatch Advice tells the buyer what is actually being shipped: items, delivered quantities, packaging, weights, carrier and delivery address — the bridge between order and goods receipt.

  • Shipment and delivery details, carrier and weights
  • Delivered quantities per line, batch and expiry data
  • Seller and buyer item identifiers for easy matching

Peppol BIS 3.0 Despatch Advice — UBL 2.1 XML

Validated against the real Peppol rules

Every procurement document is checked twice: first against the UBL 2.1 XSD for structural correctness, then against the official Peppol transaction Schematron for the business rules that apply to that specific document type.

Crucially, procurement documents are not run through the EN 16931 invoice rules — each transaction (T01, T16, T76) is validated with its own rule set, so you get accurate, relevant feedback instead of false errors.

Fatal rule violations are rejected with machine-readable error codes (e.g. PEPPOL-T01-R001); warnings are reported without blocking the conversion.

From CSV to a Peppol document in seconds

The same simple workflow you already use for invoices.

  1. 1

    Prepare a CSV

    Lay out the document header and its lines in a simple spreadsheet — one downloadable sample per document type.

  2. 2

    POST to the endpoint

    Send the file with your API key to /v1/order, /v1/order-response or /v1/despatch-advice.

  3. 3

    We build & validate

    We serialise to Peppol BIS 3.0 UBL 2.1 and run XSD + Peppol Schematron validation.

  4. 4

    We deliver it

    Take the validated UBL 2.1 XML back, or have us transmit it over Peppol to the receiver — with delivery status and webhooks.

Why digitise your orders with MyInvoice

One platform for the entire procure-to-pay document chain.

One API for everything

Orders, responses, despatch advice and invoices share the same authentication, error model and developer experience.

No EDI headaches

Skip bespoke EDI mappings — start from a CSV and get standards-based UBL out the other side.

Built and delivered

Documents conform to Peppol BIS 3.0 and pass Peppol Schematron — and we send them over the network for you, through our certified access-point partner.

Accurate, relevant validation

Each document is checked with its own transaction rules — no misapplied invoice constraints.

E-procurement FAQ

Common questions about Peppol orders and the post-award flow.

What is Peppol post-award procurement?+

Post-award procurement covers the documents exchanged after a contract is awarded: orders, order responses, despatch advice and invoices. MyInvoice supports the order, order response and despatch advice as Peppol BIS 3.0 documents.

What do T01, T76 and T16 mean?+

They are Peppol transaction identifiers: T01 is the Order, T76 is the Order Response, and T16 is the Despatch Advice. Each has its own UBL 2.1 structure and Schematron business rules.

What input do I need to provide?+

A simple CSV with the document header and its lines. We provide a downloadable sample for each document type so you can map your data quickly.

Are the documents Peppol compliant?+

Yes. Output is Peppol BIS 3.0 UBL 2.1 and is validated against the official Peppol transaction Schematron before it is returned to you.

Do you transmit documents over the Peppol network?+

Yes. POST /v1/send transmits orders, order responses, despatch advice, catalogues, catalogue responses, MLRs and invoice responses over Peppol, with delivery status and webhooks. To be precise about how: MyInvoice is not itself a certified Peppol Access Point — the network hop runs on our white-label partner, which is a certified AP and SMP. You get send and receive under one API key without becoming an access point or contracting one separately. If you would rather deliver yourself, the endpoints still return the plain XML.

Can I use the same API key as for invoices?+

Yes. The procurement endpoints use the same API key, authentication and error model as the invoice conversion endpoints.

Digitise your whole procurement flow

From the first order to the final invoice — one API, fully Peppol compliant.