Transactions
A transaction is one send or receive operation — the delivery of a document over a single channel (Peppol or email). It is created when you trigger a send or when a document is received, and lets you track that specific delivery attempt: success, failure, or in progress. One document can have multiple transactions (e.g. first send, resend, receive) — each corresponds to one such operation. See Document model and Status lifecycle.
Transaction types
The four types are the combination of direction (send / receive) and channel (email / Peppol):
| Type | When created | Channel |
|---|---|---|
| send.email | You send the document by email | |
| receive.email | Document received by email (if supported) | |
| send.peppol | You send the document via Peppol | Peppol |
| receive.peppol | Document received via Peppol | Peppol |
Transaction lifecycle
Each transaction has a status: e.g. processing → completed or failed. The document status follows that step: when you send via Peppol, the document moves to send.processing, then to send.completed or send.failed. See Status lifecycle for the full document status flow.
Relation to document status
One document can have multiple transactions (first send attempt, resend, receive, etc.). Document status reflects the latest operation in its lifecycle (create, upload, send, receive, delete). To see what happened with a specific send or receive, use the document status log and the transaction details (with optional status_log). See Document model and Status lifecycle.
Where to see transactions
- Web — In the Usage section, open Transactions. You can filter by status, type, and date. See Usage.
A transaction is one document delivery operation; types and statuses help you understand what happened with each send or receive.