Update CustomerCredit record
Changed onUpdate an existing CustomerCredit record with the provided data. Validates all required fields and business rules.
Side effects
- If an approval workflow matches this request, DualEntry can set record_status back to draft.
- If this request posts a credit for an invoice that DualEntry filed, DualEntry checks the credit note with the authority and queues the filing.
Additional validations
- Fails with 422 if the credit note filing of the credit runs or the authority cleared it, or if the request changes invoice_number of a filed credit note. An archive gets the same answer. The e_invoicing key holds the reason.
- Fails with 422 if the credit names an invoice whose e-invoice the authority has not cleared. The e_invoicing key holds the reason. Post the credit after the authority clears the invoice.
- Fails with 422 if the e-invoice of the posted record has data that the authority refuses. The e_invoicing key lists the reasons.
Request
- Base URL: https://api.dualentry.com
- URL: https://api.dualentry.com/public/v2/customer-credits/{record_number}/
- Auth: none declared
Path parameters
The number attribute of the record.
Headers
Optional. A unique value (a UUID works well) identifying this operation. If the request is repeated with the same key, the original response is replayed instead of the operation running again, so a retry cannot create a duplicate record. Results are replayable for 48 hours. Reusing a key with a different request body returns 422.
Request body
Response
OK
Changes
- info
added the optional property
/////to the response with the status
- info
- warning
added the new
kintsugienum value to the/////response property for the response status - warning
added the new
kintsugienum value to the/////response property for the response status - info
added the new optional request property
- info
added the optional property
to the response with the status
- warning