Update notices

11 Nov 2026: Status endpoint says why a delivery failed

The status of an invoice that failed at dispatch now carries the reason the access point gave, instead of only the generic message.

OAuth API

Changed

reason and reason_code on a failed status

  • GET /oauth/invoices/{invoice_id}/status adds reason (for example "Organization Doesn't Accept E-Invoices") and reason_code (for example "409") when the status category is failed and the access point gave them.
  • message is unchanged ("Failed to send invoice to Peppol"). The fields are absent when no reason was given.
  • To correct and re-send, PATCH /oauth/invoices/{invoice_id} with the corrected invoice (same entity_id and invoice_number). The same invoice is re-queued, no duplicate is created, and the answer is 202 with status PROCESSING.
  • A reason such as "Organization Doesn't Accept E-Invoices" means the buyer is not registered to receive e-invoices; correct the buyer's participant details before the PATCH.
Why we changed this
  • A client could see that a delivery failed but not why, and had to ask support to read the logs.

What to do: Read reason and reason_code on failed statuses. No change is needed for existing integrations.