Create AP Payments in batch
Security
The requesting user must have the following permission to create AP payments:
- Accounts Payable → AP Payments → Create Manual AP Payments
Create and approve are separate permissions — this permission does not grant approval rights.
Identifies the R365 tenant the request applies to. Required on every request.
The list of AP payments to create.
The identifier of the location for the payment. Required.
The identifier of the vendor being paid. Required.
The identifier of the bank GL account used for the payment. Required.
The date of the payment. Required.
The amount of the payment. Required.
Optional comment for the payment.
Optional check number associated with the payment.
Multi-Status – batch operation result containing per-payment success or failure.
Per-payment results for the batch operation.
Zero-based index of the payment in the original request array.
The vendor identifier from the original request.
Result status of this payment. Valid values: Unknown, Succeeded, Failed.
Error code if the payment failed, otherwise null.
Human-readable error message if the payment failed, otherwise null.
The identifier of the created payment if succeeded, 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.