Vendor Pay batching
Vendor Pay uses a schedule to set when payment requests become eligible for processing. Vitesse can group eligible payment requests for the same source account and stored recipient into a fitted batch, which it processes as one payment. That payment can cover several invoices or other amounts owed to the vendor, as well as credit notes.
Scheduling payment requests
Each scheduled payment request uses a configured scheduler. Vitesse uses the scheduler’s timing rule, such as the last Friday of every month, to set the payment request’s scheduled processing time.
The request becomes eligible for processing at that time. The schedule does not specify when the vendor will receive the funds.
Processing eligible requests
Vitesse checks for eligible requests every 20 minutes and after the source account receives funds.
During each processing run, the system checks the available funds and selects the eligible requests it can include in fitted batches. It queues the payment requests it cannot process for a later run.
Example
The following payment requests use the same source account.
| Payment request | Stored recipient |
|---|---|
| PR1 | Recipient A |
| PR2 | Recipient A |
| PR3 | Recipient A |
| PR4 | Recipient B |
Vitesse can group PR1, PR2 and PR3 into one fitted batch if they are eligible and funds allow. Vitesse considers PR4 separately because it uses a different stored recipient. It can group PR4 with other eligible requests for Recipient B.
Why requests remain queued
Vitesse keeps eligible payment requests queued for the following reasons:
- Insufficient funds – The source account cannot fund all eligible requests.
- Unavailable foreign exchange rate – Vitesse cannot get the rate required for currency conversion.
- Zero or negative total – The grouped payment requests have a combined total of zero or less.
See Understanding how Vendor Pay handles credit notes below for more information.
It rechecks queued payment requests in later processing runs, without waiting for their scheduler’s next occurrence.
Understanding how Vendor Pay handles credit notes
Vitesse can create a payment only for an amount greater than zero.
Customers can submit credit notes as negative payment requests. Vitesse combines these with positive requests for the same source account and stored recipient to calculate the amount payable. Adding funds to the source account does not change the amount payable.
For example, a £70 payment request and a -£100 credit note total -£30. A further eligible £30 payment request brings the total to £0. Vitesse keeps the requests queued in both cases until further eligible positive requests bring the total above £0 and the source account has enough funds to process the payment.
References for reconciliation
Vitesse generates a unique reference for each payment it creates from a fitted batch. This reference identifies the combined payment, while references on the individual payment requests identify the invoices, claims or other records that payment covers.
The vendor may not see the individual payment request references. Customers need to communicate these references separately, for example in remittance advice, so the vendor can identify the invoices or other records the payment covers.
Use the PaymentRequestsFittedBatchSucceeded webhook to access these details. For more information, see Webhooks.
Updated about 1 month ago