What it means
Imagine a company that receives 3,000 customer payments during a day. Posting each one to the ledger as it arrives would tie up the system and staff.
Instead, the payments are collected during the day and posted together overnight in a single batch. The benefit is efficiency.
Setup costs, such as opening files, validating formats and connecting to banks, are paid once per batch rather than once per item. Processing at off-peak hours also keeps systems free during the working day.
In finance, common batch jobs include payroll runs, supplier payment runs, direct debit collections, month-end depreciation postings, interest calculations and bank file uploads. Many banks process payments in batches several times a day, which is why some transfers do not arrive instantly.
Accounting teams often schedule batches so that the figures are ready when staff start work. The trade-off is delay.
Items sit waiting until the batch runs, so information is not always up to date in real time. A customer who pays at 5:30 pm may not see their account updated until the next morning, and a finance team cannot always see the latest position on demand.
Scheduling is part of the design. Teams usually set a cut-off time so everyone knows which items will join today's batch and which will wait for tomorrow's.
A late payment instruction that misses the cut-off can mean a supplier is paid a day later than planned, so the cut-off should be written into procedures and shared with the people who submit requests. Control matters too.
Good batch processing includes totals and counts, so the person running it can confirm that every item entered was processed once. If a batch fails halfway, staff need a clear way to restart it without duplicating payments.
In practice
Real-world examples
Example 1
A retailer with 200 stores uploads all daily takings to head office in one overnight batch. The finance system posts sales, taxes and card fees together by 6 am. The controller starts the day with up-to-date numbers without anyone rekeying a single figure.
Example 2
A manufacturing company pays 450 suppliers every Thursday through a single bank file. The accounts payable clerk checks that the file total equals the approved invoices before it is released. A control total of $1,385,000 confirms nothing was missed. The clerk files the signed total with the bank confirmation for the audit trail.
Example 3
A subscription software company charges customers monthly. On the first day of each month, the billing system collects all renewals into one batch and sends the card requests. Failed payments are listed separately for the collections team to chase. The team contacts those customers the same day, which recovers most failed payments within a week.
Think of it
Batch processing handles transactions in bunches at set times-not one by one as they happen.
Formula
Calculation
Cost per item = (Batch setup cost + Cost per item x Number of items) / Number of items
A payments team sends 2,500 supplier payments in one batch. The batch setup cost is $50 and each payment costs $0.02 to process. Total cost = 50 + (0.02 x 2,500) = 50 + 50 = $100. Cost per payment = 100 / 2,500 = $0.04. If each payment were sent individually with its own $0.35 handling cost, the total would be 2,500 x 0.35 = $875, so batching saves 875 - 100 = $775.Case study
Seen in the real world
Redfield Services is a fictional payroll bureau that used to process each client's salaries separately. Staff spent hours every Friday sending 120 small files to the bank, and mistakes were common. A manager proposed combining the files into one daily batch.
In this illustrative story, the bureau built a batch with control totals and an automatic report of exceptions. Processing time fell from six hours to under one, and errors dropped sharply because the totals had to match before release. The team also set a cut-off time, so clients knew when their data had to arrive.
The bureau then reviewed its error reports each month and refined the checks, adding a rule that flagged any salary that differed from the previous month by more than 20%. Clients valued the extra safeguard and the bureau used it in its sales pitch.
Watch out
Common mistakes
- Assuming batch processing is always instant. Items wait for the next scheduled run, so there is always some delay.
- Skipping control totals. Without counts and totals, missing or duplicated items can go unnoticed.
- Running the same batch twice after a failure. Teams need a documented restart process to avoid duplicate payments.
Questions
People also ask
What is the opposite of batch processing?
Real-time processing, where each transaction is handled as soon as it arrives.
Why do some bank transfers take a day?
Many payment systems process transfers in batches at set times, so a payment made after the cut-off waits for the next run.
Is batch processing outdated?
No, it is still used widely because it is efficient and reliable for large volumes, and many modern systems combine it with real-time features. Payroll, payment runs and large data updates still rely on it heavily.
Watch