Credit Notes
Update credit note
Updates an existing credit note.
How updates work
- Update uses a full
PUTcontract; items are always required. invoiceIdstays required and the credit-note client is always taken from the selected invoice.- Omitted fields are not copied from the current credit note, so send the full business payload.
- For line items, you may send existing
uuidvalues so the backend can preserve warehouse inbound receipt links during synchronization. In the create flow, itemuuidis not part of the request contract; if you send it, the backend ignores it and generates its own UUID.
PUT
Update credit note
Authorizations
Bearer token created for a specific company in Integrations → API.
Path Parameters
Credit note ID.
Example:
351
Body
application/json
Payload used to update a credit note. Update uses the same fields and validation rules as the create flow. You must send the full business payload including invoiceId and items; omitted fields are not copied from the current credit note. The client is always derived from the selected source invoice.
ID of the original invoice the credit note references. The invoice must be available in the token scope.
Example:
301
Explicit credit-note number. It must be unique across invoices and credit notes. This flow requires number, so do not send numericalSeriesId together with it.
Required string length:
1 - 20Example:
"20260051"
Issue date in Y-m-d format.
Example:
"2026-03-03"
Due date in Y-m-d format. It must be greater than or equal to issueDate.
Example:
"2026-03-17"
Delivery date in Y-m-d format. It must be less than or equal to issueDate.
Example:
"2026-03-03"
Company bank account ID used on the credit note.
Example:
201
Variable symbol with 1 to 10 digits.
Required range:
0 <= x <= 9999999999Example:
20260051
Reverse-charge tax liability flag.
Example:
false
Payment method ID from the payment method reference table.
Example:
1
Currency ID from the currency reference table.
Example:
1
Currency exchange rate against EUR. If the document currency is EUR, the backend always stores and returns 1.0.
Required range:
0.00001 <= x <= 10000000Example:
1
Language ID from the language reference table.
Example:
1
Credit note line items. This field stays required on update. If you send the original uuid of an existing line item from the credit note detail response, the backend can preserve warehouse inbound receipt links. In the create flow, item uuid is not part of the request contract and the backend ignores it.
Required array length:
1 - 100 elementsPayload for a single invoice line item during update. The validation rules are the same as in create, but you may additionally send the original uuid of an existing invoice row. You can obtain that UUID from the invoice detail response. The backend uses it during warehouse allocation and outbound receipt synchronization so it can match the edited line with the original stored line. In the create flow, item uuid is not part of the request contract; if you send it, the backend ignores it.
- Option 1
- Option 2
- Option 3
- Option 4
Optional business case ID. When sent, it must be available in the token scope and to the client derived from the source invoice.
Example:
701
Numbering series ID for credit notes. In this explicit public create/update flow, do not send it together with the required number field.
Example:
12
Constant symbol with 1 to 4 digits.
Required range:
0 <= x <= 9999Example:
308
Specific symbol with 1 to 10 digits.
Required range:
0 <= x <= 9999999999Example:
55
Document-level discount type.
Available options:
percentage, fixed Example:
"percentage"
Document-level discount value.
Example:
10
Note shown on the document.
Maximum string length:
3000Example:
"Credit note for the original invoice."
Text shown above the line items.
Maximum string length:
3000Example:
"We are crediting part of the original supply."
Response
Credit note updated.
Credit note.
Example:
351
Example:
"6b1b8c9e-66e6-4fb5-b2db-6d7c7f0f8f19"
Example:
"credit-note"
Example:
"20260051"
Absolute URL of the public web document for this credit note.
Example:
"https://app.fintoro.sk/web-doklad/credit-note/4f3f8a95-5c4a-4c8b-9e6c-8a0c1a5df3a1"
Absolute URL of the Fintoro API endpoint that downloads this credit note PDF as an attachment.
Example:
"https://app.fintoro.sk/api/public/v1/credit-notes/351/pdf"
Supplier snapshot stored directly on this document.
Live ID of the client linked to the credit note.
Example:
101
Historical client snapshot stored directly on this document.
Bank account linked to the credit note as a live relation, loaded even through soft delete.
Payments linked to this credit note ordered from newest to oldest.
ID of the original invoice the credit note references.
Example:
301
Example:
20260051
Example:
308
Example:
55
Example:
"2026-03-03"
Example:
"2026-03-17"
Example:
"2026-03-03"
Optional business case ID. When sent, it must belong to the client derived from the source invoice.
Example:
701
Example:
"percentage"
Example:
10
Example:
false
Example:
12
Payment method ID from the payment method reference table.
Example:
1
Currency ID from the currency reference table.
Example:
1
Example:
1
Language ID from the language reference table.
Example:
1
Example:
"Credit note for the original invoice."
Example:
"We are crediting the original supply."
Example:
-20
Example:
-24
Example:
0
Example:
-20
Example:
-24
Example:
-24
Available options:
paid, unpaid, partially_paid, overdue, will_not_be_paid Example:
"unpaid"
Example:
true
Update credit note