What it means
Every transaction requires some overhead: authorisation, data entry, checking, posting, reconciling. Doing that for each transaction as it arrives is expensive and error-prone.
Grouping transactions and processing them together lets the overhead be incurred once per batch, lets the batch be checked as a whole (does the total of the invoices entered agree to the total on the control sheet?), and lets processing run at quiet times, overnight or at weekends, when systems are free. This is why payroll, billing, payment runs and ledger postings have been batched since accounting was done by hand, and why computerised systems inherited the same rhythm.
Batch control is a core accounting control. Before a batch is processed, someone counts the documents and totals the amounts (the batch header).
After processing, the system's totals are compared with the header. A difference means a document was missed, duplicated or entered wrongly, and the batch is corrected before it is posted.
Batch totals are one of the simplest and most effective defences against input error, and they give auditors a clear trail: every posting belongs to a batch, every batch has a header, every header was agreed. The limitation of batching is timing.
A customer payment received on Monday morning is not visible in the ledger until the daily batch posts that night; a supplier invoice approved on Tuesday is not paid until Friday's run. For most accounting processes that delay is acceptable and even useful, since it creates a natural point for review and approval.
For customer-facing processes it may not be: online retailers process orders and payments in real time because customers expect confirmation immediately, and many businesses now run a hybrid of real-time capture with batch posting and settlement. Batch processing also shapes the month-end close.
Standard journals for depreciation, prepayment releases, accruals and allocations are prepared as batches, reviewed together and posted in sequence, which is faster and safer than entering them individually and lets the close be scheduled and tracked.
In practice
Real-world examples.
Example
A company runs payroll as a monthly batch: timesheets are collected, the batch is calculated, totals are checked against the previous month and against headcount, the batch is approved by the finance manager and the bank file is released.
Example
A utility generates 400,000 customer bills in an overnight batch on the fifth of each month, with the total billed agreed to the meter-reading file before the bills are sent.
Example
An accounting system posts the day's bank feed as a single batch at 6 a.m., matching each transaction to open invoices and flagging unmatched items for review.
Think of it
“Batch processing handles transactions in bunches at set times-not one by one as they happen.
Formula
Calculation
Batch control: Sum of items entered = Batch header total (count and value), or the batch is rejected
Processing cost per transaction = (Fixed cost per batch run + Variable cost per item x Items in batch) / Items in batch
Worked example. A distributor processes supplier invoices in daily batches. Each batch run costs about $60 of fixed effort (preparing the header, running the posting, reviewing exceptions, filing) and $1.50 per invoice for data entry and matching. On a typical day 120 invoices are batched.
- Cost per invoice = ($60 + 120 x $1.50) / 120 = $240 / 120 = $2.00
If invoices were processed individually as they arrived, with an estimated $4 of set-up, approval and posting effort each on top of the $1.50 of entry, the cost would be $5.50 per invoice. Batching saves $3.50 per invoice, or about $105,000 a year on 30,000 invoices.
Batch control example: Tuesday's batch header records 118 invoices totalling $246,830.40. After entry, the system reports 118 invoices totalling $246,380.40. The difference of $450.00 is investigated: an invoice for $1,275.00 was entered as $825.00. Corrected, the totals agree and the batch is posted. Without the control, the supplier would have been underpaid by $450, the error found only when the supplier chased the balance.
Timing cost: invoices approved after the daily cut-off wait a day. For a supplier offering a 2% discount for payment within 10 days, a one-day batch delay is immaterial; a weekly payment run is not, and the payment run is scheduled to ensure discounted invoices are paid within the window.Case study
Seen in the real world.
A subscription business processed customer card payments in a single monthly batch on the first of the month. It was efficient: one run, one settlement, one reconciliation. The problems were in the timing.
Customers whose cards had expired or been replaced were only discovered on the first, when the whole batch ran; failed payments, about 4% of the batch, then had to be chased manually through the month, and by the time they were resolved the next batch was due. Revenue arrived in a single lump, making cash forecasting lumpy, and a processing failure on one occasion delayed the entire month's collections by three days. The company moved to daily batches based on each customer's subscription anniversary, with automatic retries for failed payments over the following week and card-update prompts sent ten days before expiry.
Failed payments fell to 1.2%, cash arrived evenly through the month, and the finance team's manual chasing fell by 80%. The batch principle survived; the batch size and frequency changed.
Watch out
Common mistakes.
- Posting batches without agreeing control totals. The control is the whole point; without it, batching merely delays the discovery of errors.
- Batching processes where the delay damages customers or loses discounts. Match batch frequency to the cost of waiting.
- Letting failed items in a batch fall through. Every batch needs an exception process that runs before the next batch.
Questions
People also ask.
What is the difference between batch and real-time processing?
Batch collects transactions and processes them together at intervals. Real-time processes each transaction as it occurs. Many systems capture in real time and post or settle in batches.
Is batch processing outdated?
No. Payroll, billing, payment runs, ledger postings and settlements are still batched in almost every organisation because the efficiency and control benefits remain. The batches have become smaller and more frequent.
What is a batch header?
A record of the number and total value of the items in a batch, prepared before processing and agreed to the system totals afterwards.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%