Purchase invoice events

Two events tell you when a purchase invoice is stored. Use the event type to decide whether to process the invoice or send it for review.

These events describe purchase documents, including supplier invoices received through Peppol, the network used to exchange electronic invoices. They also cover invoices submitted as purchases through the API.

EventFires when
purchase.invoice.storedThe invoice was stored successfully. This includes invoices stored with warnings.
purchase.invoice.validation_failedThe invoice failed validation. It is still stored, so you can see it in Documents, but it needs attention.

Read the fields below from data.data in the delivery body. Fields such as supplier name, issue date and totals may be absent if they are unavailable.

FieldMeaning
documentIdThe document’s ID in Complyance. Use it to open the document or fetch it through the Purchases API.
documentNumberThe supplier’s invoice number
documentTypeFor example tax_invoice or credit_note
countryAE, SA, MY, BE or DE
totalAmountThe invoice total including tax
currencyISO 4217 code, for example AED
sellerNameThe supplier
issueDateThe date on the invoice
submittedAtWhen the invoice entered Complyance
errorsValidation errors, when available: each has code, message and an optional path
attributionCompany, branch and source details, when available
attribution.companyIdThe company the purchase belongs to. Use it to select the company in your integration.
attribution.branchIdThe branch, when identified. Do not assume every event includes it.

What to do with them

  • stored: create the invoice in your accounts-payable system, or start your approval flow.
  • validation_failed: route the invoice to someone for review. Open it in Documents to see the errors in full.

These events are only for invoices you receive. Sales invoices you send to customers do not raise these purchase events.

To register for them, see Set up a webhook.

Last updated