Partial update AP Payments in batch
Security
The requesting user must have the following permission to approve AP payments:
- Accounts Payable → AP Payments → Approve AP Payments
Approve and create are separate permissions — this permission does not grant create rights.
Identifies the R365 tenant the request applies to. Required on every request.
The collection of AP payments to approve or reject.
Payment identifier to approve or reject.
Approval status to set on the payment. Valid values: Approved, Rejected.
Invoices to associate with this payment.
Credit memos to associate with this payment.
Multi-Status – Batch operation result containing status for each payment in the request.
The result for each payment in the request.
Zero-based index of the payment in the original request.
Payment identifier.
Result status of the operation. Valid values: Unknown, Succeeded, Failed.
Error code if the operation failed, otherwise null.
Error message if the operation failed, otherwise null.
Bad Request — a parameter value is malformed, of the wrong type, or outside its allowed range.
Unauthorized — the bearer token is missing, invalid or expired, or is not valid for the specified tenant.
Forbidden — the caller lacks the permission required for this operation.
Not Found — the requested resource does not exist, or the supplied continuation token is unknown or has expired.
Conflict — the request conflicts with the current state of the resource and cannot be applied.
Unprocessable Entity — a required parameter is missing, or a supplied parameter value is invalid.
Too Many Requests — the caller has exceeded the rate limit; retry after a short delay.
Internal Server Error — an unexpected error occurred while processing the request.