Document Payments
List document payments
Returns all payments for one public document. The list is not filtered or paginated; it always returns the full payment history of the selected document ordered from newest to oldest.
GET
List document payments
Authorizations
Bearer token created for a specific company in Integrations → API.
Query Parameters
Document type whose payments you want to load. Only invoice, proforma, and credit-note are supported.
Available options:
invoice, proforma, credit-note ID of a document.
Response
Document payment list.
Payments of the selected document.
Previous
Create document paymentCreates a new payment for a public document.
### Supported document types
Only `invoice`, `proforma`, and `credit-note` are supported.
### Business behavior
- The payment is always linked to one document via `documentType` + `documentId`.
- The minimal create payload is only `documentType` + `documentId`; all other fields can be omitted and are derived server-side.
- If `paymentDate` is omitted, today's date is used.
- If `paymentMethodId` is omitted, the payment method from the source document is used.
- If `currencyId` is omitted, the currency from the source document is used.
- If `amount` is omitted, the current remaining `toBePaid` amount from the source document is used. This shortcut only works when the document still has a non-zero `toBePaid`; otherwise the endpoint returns `422`.
- If `amount` is sent explicitly, it can have at most 2 decimal places.
- If `amount` is sent explicitly, its magnitude must not exceed the current `toBePaid` and it must keep the same sign, so the payment cannot over-settle the document or move in the opposite direction.
- If `currencyRate` is omitted, the system derives it from the final `paymentDate` using the previous day's rate.
- If you send `currencyRate` for a currency other than `EUR`, that override value is used as-is.
- If the final payment currency is `EUR`, the backend always stores and returns `currencyRate = 1.0`, even when you send a different value.
- Creating a payment recalculates the document payment status exactly like the web and mobile flows.
- If you later issue a payment receipt invoice for a proforma payment, the payment response may expose it in `receiptInvoice`.
If you send an `Idempotency-Key`, the same key with the same payload returns the original response without creating the payment again.
Next
List document payments

