Update CustomerPrepayment record
Update an existing CustomerPrepayment record with the provided data. Validates all required fields and business rules.
Path parameters
The number attribute of the record.
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
Posting date (GL date) - the date when the transaction is recorded in the general ledger
Transaction date (inception date) - the date when the transaction actually occurred
Total transaction amount
Amount that was already applied to Invoices
Amount that can be applied to Invoices
Date and time the record was created
Date and time the record was last updated
Changes
Changed in 1 of the 14 revisions of this API.○1
- ○
added the new optional
headerrequest parameterIdempotency-Keynew-optional-request-parameter
- ○