Batch payment
A batch payment is a set of individual payments grouped into a single file or instruction and submitted together, so they are processed as one operation rather than one by one.
What it means. "Batch" refers to the mechanism: instead of initiating payments individually, the payer assembles many payments — each with its own recipient, amount and details — into one batch and submits it once. The provider validates and processes the whole set together. It is the standard way to handle bulk disbursement, and the term is often used alongside "bulk payment," with batch describing the *how* and bulk the *scale*. A batch might contain a handful of payments or many thousands.
How it works. A batch is typically a structured file (or an equivalent instruction via an interface) listing each payment. On submission, the system checks the file for errors — invalid account details, malformed amounts, duplicates — then releases the payments over the appropriate rail. Batching brings control and reliability: the whole run can be validated before release, scheduled for a chosen date, and reconciled as a unit afterwards. This makes it far safer than paying each recipient individually, where errors are harder to catch and the process is slow.
Where it fits. Batch payments underpin payroll, supplier settlement, marketplace payouts and any scenario involving many payments at once. They pair naturally with treasury operations (moving money at scale) and run over rails chosen for volume and cost. The alternative — paying each recipient individually — is slower, more error-prone and impractical at scale, which is why virtually every organisation that pays many parties relies on batch processing rather than manual, one-by-one payments. The batch is the quiet mechanism behind most of the money a business pays out on any given day.