What is a Batch Processing?

What Is Batch Processing in Payments?

Batch processing is a method of handling payment transactions where multiple transactions are collected over a period of time and then submitted together as a group (a "batch") for processing, rather than being submitted individually in real time. It is one of the oldest and most established patterns in payment processing, and it remains central to how many card payment systems work behind the scenes.

When a merchant accepts card payments throughout the day, each transaction is typically authorised in real time -- the customer gets an approval or decline immediately. But the actual submission of those transactions for clearing and settlement often happens in a batch at the end of the day.

How Batch Processing Works

The typical batch processing cycle for card payments follows this pattern:

• Transaction accumulation -- Throughout the business day, the merchant's payment terminal or payment gateway authorises transactions individually and stores the approved transactions
• Batch close -- At a designated time (usually the end of the business day), the system packages all the day's authorised transactions into a single batch file
• Batch submission -- The batch is transmitted to the acquiring bank or payment processor for clearing
• Processing -- The acquirer processes each transaction in the batch, routing them through the appropriate card networks to the issuing banks
• Settlement -- Once clearing is complete, the net funds are transferred to the merchant's account, typically one to two business days after batch submission

Batch Processing vs Real-Time Processing

It is important to distinguish between the authorisation of a transaction (which happens in real time) and the settlement of a transaction (which typically happens in batches):

• Real-time processing -- The transaction is authorised, cleared, and settled individually as it happens. This is common in modern digital payment systems like Faster Payments in the UK
• Batch processing -- Transactions are authorised in real time but cleared and settled in groups at scheduled intervals

Most card payment systems use a hybrid approach: real-time authorisation with batch settlement. This gives the customer an immediate confirmation while allowing the banking system to efficiently process millions of transactions in bulk.

Why Batch Processing Still Matters

Despite the trend toward real-time everything, batch processing remains important for several reasons:

• Efficiency -- Processing transactions in bulk is more efficient for banks and card networks than handling each one individually. The overhead of establishing connections, performing reconciliation, and moving funds is spread across many transactions
• Cost -- Batch processing reduces the per-transaction cost of clearing and settlement
• Error handling -- Batches allow for pre-submission validation, where issues can be caught and corrected before the entire batch is processed
• Reconciliation -- Merchants can reconcile a single batch against their own records, rather than tracking individual transactions throughout the day

Batch Processing in Telephone Payments

For businesses that take telephone payments, batch processing affects when funds arrive in the merchant account. Here is how it typically works:

• A customer calls and makes a payment. The card is authorised in real time during the call
• The transaction is stored in the payment system's pending batch
• At the end of the day (or at the configured batch close time), all the day's telephone payments are submitted along with any other card transactions
• The batch is processed overnight, and funds are typically available in the merchant account the next business day

Some payment gateways allow merchants to submit batches multiple times per day, which can improve cash flow by getting funds settled faster.

Batch Close Times and Cash Flow

The timing of batch closes has a direct impact on when merchants receive their money. Consider these scenarios:

• A merchant closes their batch at 10:00 PM each night. A telephone payment taken at 9:30 PM makes it into that night's batch and settles the next business day
• A payment taken at 10:30 PM misses the batch close and is included in the following night's batch -- meaning it settles a full day later

For this reason, some merchants adjust their batch close times to optimise cash flow. If your business takes significant telephone payments in the evening, a later batch close time ensures those transactions settle sooner.

Batch Processing and Reporting

Batch processing creates natural groupings that simplify financial reporting and reconciliation. Each batch has a unique identifier and contains a complete record of all transactions included. This makes it straightforward to:

• Match batches to bank deposits
• Identify discrepancies between processed and settled amounts
• Track daily transaction volumes and values
• Audit payment activity over specific time periods

Common Batch Processing Issues

• Missed batch close -- If the batch is not closed (due to a system error or misconfiguration), transactions will not be submitted for settlement until the next close
• Expired authorisations -- If too much time passes between authorisation and batch submission, some authorisations may expire
• Duplicate transactions -- Submitting the same transaction in multiple batches can lead to double charges
• Batch rejections -- If the batch file contains formatting errors or invalid data, the entire batch may be rejected by the processor