What it means
An ACH file is a hierarchy: one file header, one or more batches, and within each batch a list of individual payment entries. The batch header record is the line that starts each batch and tells the system what the entries inside it are, who sent them, and how they should be handled.
The record carries the batch's identity card: it names the company originating the payments, describes the purpose with a standard entry class code, states the effective entry date, and sets whether the entries are debits or credits. Every entry that follows inherits those properties, which is what makes batching efficient, since common facts are stated once, not repeated per payment.
Batching is also control, because each batch closes with a control record that counts the entries and sums their amounts, so the receiving system can prove the batch arrived complete. The header starts that chain of accountability, and a malformed header orphans every entry beneath it.
Nacha, the body that governs the ACH network, publishes the file format in detail, and its developer guidance describes the batch header as the point where the standard entry class and company identification are declared. The format is rigid by design, with fixed positions, fixed lengths, and codes that mean exactly one thing.
For a business, the batch usually maps to a business event: one payroll run is a batch, one night's supplier payments is a batch, and one sweep of customer direct debits is a batch. The header's description and date are how the receiving bank and the recipients recognise what the money is for.
For a finance manager, the batch header matters at three moments. When a file is rejected, the header is the first suspect; when a recipient queries a payment, the header's reference is the trailhead; and when auditors test whether payments were properly authorised, the batch is the unit they sample.
Errors in the header propagate, which is both the risk and the lesson, since a wrong effective date in one header delays hundreds of salaries at once, and payables teams therefore validate headers before transmission with the same care they give the payment amounts themselves. The concept generalises beyond ACH.
Any bulk payment file, in any national clearing system, solves the same problem the same way: group the entries, stamp the group with its shared facts, and reconcile the group as a unit, so learning the batch header is learning the grammar of bulk payments.
In practice
Real-world examples.
Example
A company's payroll run appears in its ACH file as one batch with a header naming the company and the salary entry class. Every employee credit beneath it inherits the same originator, purpose and effective date. The payroll team reviews the header before the file is released to the bank.
Example
A bank rejects a batch because the header's effective entry date falls on a non-settlement day. The entries beneath it were all correct, but the single wrong date makes the whole group unprocessable. The originator corrects the header and resubmits, losing a day.
Example
An auditor traces a supplier payment from the ledger back to the batch header that carried it into the clearing system. The header shows who originated the batch, what it was for and when it was due to settle. That trail lets the auditor confirm the payment was part of an authorised run.
Formula
Calculation
There is no formula; the control logic is: batch entry count and value hash = sum of the entries between the batch header and its control record, and a file balances when every batch's stated totals match its contents.
Worked example: a payroll provider sends one file of four batches with 1,000, 700, 800 and 500 salary credits, each averaging $2,000. The batch totals are $2,000,000, $1,400,000, $1,600,000 and $1,000,000, so the file control record should show 1,000 + 700 + 800 + 500 = 3,000 entries and $2,000,000 + $1,400,000 + $1,600,000 + $1,000,000 = $6,000,000. If the 700-entry batch arrives with only 699 entries, or a total of $1,398,000, its control figures no longer match its contents and the receiving system can reject that batch alone.Case study
Seen in the real world.
This is a fictional, illustrative example. A payroll provider transmits 3,000 salary credits in one ACH file split into four batches by pay group. One batch header carries the wrong effective date, the receiving bank rejects that batch alone, 700 salaries land a day late, and the post-mortem moves header validation into the pre-transmission checklist. The provider's finance director compares the cost of the fix with the cost of the failure. A two-minute header check, signed off by a second person, replaces a day of complaint calls from employees and the goodwill lost with the client's payroll team.
Watch out
Common mistakes.
- Treating the header as boilerplate. The header's dates, codes, and identifiers govern every entry in the batch, and a single wrong field can delay or misroute hundreds of payments at once.
- Mixing unlike entries in one batch. Entries that share a header inherit its class and timing, so combining different payment types under one header breaks format rules and confuses reconciliation at both ends.
- Skipping control totals. A batch whose stated counts and sums are not checked against its contents can arrive incomplete without anyone noticing until recipients complain, and the control record exists precisely to catch that.
Questions
People also ask.
What is a batch header record?
It is the record that opens a batch of entries in an ACH file, declaring the originating company, the transaction type, and the settlement details that apply to every entry in that batch.
Why does the ACH system use batches?
Because common facts such as the originator, entry class, and effective date can be stated once for a group of payments, and the batch can be counted, totalled, and reconciled as a single unit.
What happens if the batch header is wrong?
Every entry in the batch inherits the error: the receiving bank may reject the whole batch, or the payments may settle with the wrong date or description, so header validation is a standard pre-transmission control.
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%Related