How Do Payouts and Bulk Payments Work?

A payout is a payment a business makes out to a bank account — a salary, a supplier invoice, a refund, an insurance claim, a customer withdrawal. When a business needs to make many payouts at once, they are processed as bulk payments: a single batch containing hundreds or thousands of individual credits, submitted to the bank or a payment provider in one go.

Bulk payments run on the same rails as ordinary transfers — usually batch EFT credits, with instant rails like PayShap increasingly used where individual payouts need to arrive immediately.

How does a bulk payment run work?

A typical bulk payment cycle looks like this:

1. Prepare: the business compiles beneficiary details, amounts and references — from a payroll system, accounts payable, or a platform's withdrawal queue.
2. Validate: account numbers are checked against branch codes (CDV checks), and ideally verified through an account verification service before first payment.
3. Submit: the batch is uploaded as a file to the bank, or submitted through a payout API.
4. Fund: the total value of the batch is debited from the business's account, or must be pre-funded, depending on the arrangement.
5. Process: the batch is cleared through BankservAfrica in the scheduled processing windows and settled between banks.
6. Report: the business receives results per item — paid, rejected or returned — and reconciles them against the original batch.

Because batches are cleared in windows, submission cut-off times determine when beneficiaries are paid. A payroll batch submitted after cut-off pays staff a day late.

Files or APIs — which should you use?

Businesses submit bulk payments in two main ways:

• Batch files: a formatted file uploaded to the bank's business banking channel or delivered host-to-host. Well suited to scheduled, high-volume runs like monthly payroll.
• Payout APIs: individual or batched payment instructions sent programmatically, with statuses returned via API or webhooks. Better for event-driven payouts such as marketplace withdrawals, refunds and claims.

The trade-offs between the two models are covered in batch files vs APIs. Kwik offers EFT payouts and PayShap payments through its platform, so businesses can automate disbursements without building bank file integrations themselves.

What can go wrong in a bulk run?

Individual items in a batch can fail even when the batch as a whole is accepted:

• Invalid account numbers fail CDV validation and are rejected before processing.
• Closed, frozen or unlocatable accounts cause the receiving bank to return the credit, often a day or more later.
• Duplicate submissions happen when a file is uploaded twice — idempotency controls and batch references prevent this.
• Insufficient funding can cause the whole batch to be rejected.

Returned items come back with reason codes and must be investigated, corrected and re-paid. See failed and returned transfers for the common return reasons.

How should payouts be controlled and reconciled?

Bulk payments move significant money quickly, so controls matter:

• Verify before you pay: run new beneficiaries through account verification to confirm the account exists and matches the ID or registration number.
• Dual authorisation: require a second approver to release batches above a threshold.
• Unique references: give every item a unique reference so bank statement entries match back to source records automatically.
• Reconcile every run: match submitted items against processed results and the bank statement, and chase every exception. The discipline is described in clearing, settlement and reconciliation.
• Protect the process: payout systems are prime fraud targets — restrict who can edit beneficiary details and audit changes.

Tips

• Schedule payroll submission at least one processing window before payday.
• Keep a suspense process for returned items so beneficiaries are re-paid quickly.
• Use instant rails for one-off urgent payouts rather than re-running a batch.
• Never edit beneficiary bank details based on an emailed request without independent verification.

Back to the Bank Transfers, Payouts and PayShap hub.