What are batch payments?
Batch payments are multiple transactions of the same type, grouped into a single file and processed together at a set interval, rather than individually. Instead of sending 200 payroll payments one by one, a business submits a single file containing all 200, and the bank or processor settles them together as one batch.
Batch payments are also called batch disbursements or batch transfers. ACH in the US and BACS in the UK are the two most widely used batch payment rails, and both process files exactly this way.
How does batch payment processing work?
The workflow follows a consistent pattern regardless of which rail carries the payments:
- The business compiles a file listing every recipient, amount, and account detail, often exported from an ERP or payroll system, or built directly in a spreadsheet
- The file is submitted to a bank, processor, or payment platform ahead of a cutoff time
- The payments are validated and processed together as a single batch
- Settlement happens at a scheduled interval, such as end of day, rather than continuously through the day
- The bank statement shows one consolidated debit rather than 200 separate line items
That single consolidated debit is one of the main reasons businesses use batch payments. Reconciling one line is far simpler than reconciling hundreds.
What is the difference between batch payments and bulk payments?
These two terms get used interchangeably, but there is a real distinction worth understanding.
Batch payments are the older, file-based model. Bulk payments are the newer, API-based model that achieves the same operational goal, consolidating many payments into one action, without the rigidity of a fixed-format file.
What is the difference between batch payments and real-time payments?
Batch payments settle on a schedule. Real-time rails like RTP and FedNow settle individually, the moment each payment is sent.
With batch payments, a business submits a file and waits for the next processing window. That window might be hours away depending on the rail's cutoff schedule. With real-time payments, each transaction clears independently within seconds. There is no batch efficiency gain, though, since every payment is its own event.
Neither approach is universally better. Batch payments make sense when timing is predictable and volume is high, such as monthly payroll. Real-time rails make sense when a single payment needs to move immediately.
Why do businesses use batch payments?
Batch payments solve a specific problem: processing high volumes of predictable, recurring payments efficiently. The main benefits are:
- Lower per-transaction cost: Processing fees are typically much lower for batch-based rails like ACH than for wire transfers or card payments
- Simplified reconciliation: One consolidated debit on a bank statement is far easier to match against internal records than hundreds of individual transactions. This connects directly to payment reconciliation workflows
- Reduced manual effort: A single file upload and approval replaces dozens or hundreds of individual payment initiations
- Predictable processing: Businesses know exactly when a batch will settle, which supports cash flow planning
What are the limitations of batch payments?
The same rigidity that makes batch payments efficient also creates friction when something needs to change.
If an error turns up in one payment within a batch, the fix often means correcting and resubmitting the entire file. It is rarely just the one affected transaction. This can delay the whole batch, including the payments that were correct from the start. Batch payments also cannot deliver same-moment settlement. A business needing to move money urgently should use Same Day ACH or a real-time rail instead.
When should a platform use batch payments instead of bulk payments?
For platforms processing payroll, vendor payments, or recurring disbursements at scale, batch efficiency is still what makes high volume manageable. The core tradeoff comes down to two questions:
- Are recipients uniform? A single payroll run each month, paid the same way to every employee, works well as a traditional batch file
- Do recipients vary? Paying suppliers, freelancers, and investors in different currencies and rails in one run benefits more from a bulk, API-driven approach
Due's Payroll Payments product is built for the first case at global scale. A single integration pays recipients across ACH, SEPA, SWIFT, mobile money, and stablecoin rails in over 80 countries, so a platform running payroll for a distributed team does not need a separate batch process for every country or rail its employees are paid through.
