Update VendorPayment record
Changed onUpdate an existing VendorPayment 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 record already has an active bank match, and an approval workflow holds the record, DualEntry returns those matches to draft.
- If the customer or vendor is intercompany, DualEntry also writes a transaction in the elimination company.
- If the record has a bank account and a payment method that prints checks, DualEntry creates a not_printed paper check, even if the record is draft.
- If a printed or not-printed paper check already exists, DualEntry skips paper-check creation.
- If you clear payment_method_id, or set it to a payment method that does not print checks, DualEntry sets the associated unprinted paper check to archived.
Additional validations
- Fails with 422 if the request changes check_number while a paper check is not_printed.
Request
- Base URL: https://api.dualentry.com
- URL: https://api.dualentry.com/public/v1/vendor-payments/{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
- warning