Update CustomerPrepayment record (partial)
Partially update an existing CustomerPrepayment record. Send only the fields you want to change — anything you don't send stays as it is. Updates are subject to the same constraints as the full update endpoint: period locks, payment-applied restrictions, and approval-workflow rules apply.
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