Document types
The aliases accepted as type, and what each one is.
type on a submission is a short alias for a Peppol document type and the business process it belongs to. It saves you writing out two long identifiers on every call.
| Alias | Document | Process |
|---|---|---|
invoice | Invoice | Billing 3.0 |
credit-note | Credit note | Billing 3.0 |
invoice-cii | Invoice, CII syntax | Billing 3.0 |
self-billing-invoice | Self-billing invoice — issued by the buyer on the seller's behalf | Self-billing 3.0 |
self-billing-credit-note | Self-billing credit note | Self-billing 3.0 |
pint-aunz-invoice | Invoice, PINT A-NZ | PINT billing |
pint-aunz-credit-note | Credit note, PINT A-NZ | PINT billing |
invoice-response | Invoice response | Invoice response 3 |
order | Order | Ordering 3 |
order-only | Order | Order only 3 |
order-advanced | Order | Advanced ordering 3 |
order-response | Order response | Ordering 3 |
order-response-advanced | Order response | Advanced ordering 3 |
order-change | Order change | Advanced ordering 3 |
order-cancellation | Order cancellation | Advanced ordering 3 |
despatch-advice | Despatch advice | Despatch advice 3 |
catalogue | Catalogue | Catalogue only 3 |
catalogue-wo-response | Catalogue | Catalogue without response 3 |
Each process is a processId, in the cenbii-procid-ubl scheme:
| Process | processId |
|---|---|
| Billing 3.0 | cenbii-procid-ubl::urn:fdc:peppol.eu:2017:poacc:billing:01:1.0 |
| Self-billing 3.0 | cenbii-procid-ubl::urn:fdc:peppol.eu:2017:poacc:selfbilling:01:1.0 |
| PINT billing | cenbii-procid-ubl::urn:peppol:bis:billing |
| Invoice response 3 | cenbii-procid-ubl::urn:fdc:peppol.eu:poacc:bis:invoice_response:3 |
| Ordering 3 | cenbii-procid-ubl::urn:fdc:peppol.eu:poacc:bis:ordering:3 |
| Order only 3 | cenbii-procid-ubl::urn:fdc:peppol.eu:poacc:bis:order_only:3 |
| Advanced ordering 3 | cenbii-procid-ubl::urn:fdc:peppol.eu:poacc:bis:advanced_ordering:3 |
| Despatch advice 3 | cenbii-procid-ubl::urn:fdc:peppol.eu:poacc:bis:despatch_advice:3 |
| Catalogue only 3 | cenbii-procid-ubl::urn:fdc:peppol.eu:poacc:bis:catalogue_only:3 |
| Catalogue without response 3 | cenbii-procid-ubl::urn:fdc:peppol.eu:poacc:bis:catalogue_wo_response:3 |
The same document can belong to more than one process — an order sent under order and under order-only is the same XML with different expectations about what comes back. Use the alias that matches what you and your trading partner agreed.
Using full identifiers instead
Any document type we know can be named directly, with documentTypeId and processId in place of type:
{
"documentTypeId": "busdox-docid-qns::urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0::2.1",
"processId": "cenbii-procid-ubl::urn:fdc:peppol.eu:2017:poacc:billing:01:1.0"
}Passing both type and the full pair is allowed as long as they agree; if they do not, the request is refused rather than one silently winning.
Capabilities use the same names
A participant's capabilities are declared with the same aliases or identifiers. A document type you have no capability for cannot be sent, and other access points will not send it to you — the capability is what they read when deciding.
Self-billing
In self-billing the buyer issues the invoice on the seller's behalf. It is the same content as an ordinary invoice under its own customisation and process, so a receiver registers for it separately: a participant that can receive invoice cannot necessarily receive self-billing-invoice.
Australia and New Zealand
Both countries accept only PINT A-NZ for billing, not BIS Billing 3.0. Send pint-aunz-invoice and pint-aunz-credit-note to receivers there. Their documentTypeId is in the peppol-doctype-wildcard scheme rather than busdox-docid-qns. Give a participant that receives on behalf of an Australian or New Zealand business these capabilities rather than invoice and credit-note.
The document has to be what it is sent as: a BIS Billing 3.0 invoice sent as pint-aunz-invoice, or the other way round, is refused with 400 VALIDATION_FAILED before anything is stored. The same goes for a credit note sent as an invoice.
CII invoices
invoice-cii is the CII syntax rather than UBL. It has no current validation rules available, so a CII invoice cannot be checked before it goes out. Sending one requires its capability to be marked as allowing unvalidated documents — a deliberate decision, not a default, because it means the document leaves without ever having been verified against the Peppol rules.
Send UBL unless a trading partner specifically requires CII.