# ACH Batch Deposit Reconciliation to Customer Payments

- Author: PreciseBankFlow (https://www.precisebankflow.com)
- Published: 2026-09-25
- Updated: 2026-09-25
- Category: Payment and deposit reconciliations
- Canonical: https://www.precisebankflow.com/blog/ach-batch-deposit-reconciliation

> ACH batch deposit reconciliation: split one bank credit into the customer payments inside it using the addenda or report, and resolve unknowns.
ACH batch deposit reconciliation splits a single bank credit into the individual customer payments it contains. Get the entry detail from the bank's batch report, the payment provider's settlement report or the ACH addenda, apply each entry to its customer and invoice, and confirm the entries add up to the deposit. Entries no one can identify go to unapplied cash.

## What is an ACH batch deposit on a bank statement?

An ACH batch deposit is one credit on the bank statement that settles many separate ACH entries at once. It happens when a business collects from customers by ACH debit and the bank posts the batch total, or when a payment provider gathers customers' bank payments and settles them together. The statement shows one amount; the detail sits elsewhere.

The batching is built into how ACH files are structured. Nacha's [Third-Party Tax Payments user guide](https://www.nacha.org/system/files/2023-06/TPP-User-Guide-Revised-07-13.pdf) describes an ACH file as one or more batches, each with a batch header and control record, holding one or more entry detail records. Banks often post the batch as a single line, labelled with the company name and a batch or file reference.

### Three common sources of ACH batch deposits

- **Debits you originate**: your bank collects from customers on your instruction, then credits the batch total.
- **A payment provider's settlement**: customers pay by bank transfer through an invoicing or billing tool, which settles to you in one credit.
- **A single payer's combined payment**: one customer sends one ACH credit that pays many invoices, with the detail carried in addenda.

The first two put many payers in one deposit. The third puts many invoices from one payer in one deposit. Both need splitting before receivables are right.

## Where the detail behind an ACH batch deposit lives

The detail lives in whatever system created the batch. For debits you originate, it is the origination file or the bank's batch report in online banking. For a payment provider, it is the provider's payout or settlement report. For a single payer, it is the remittance, often inside the ACH addenda. Without it, the deposit cannot be split.

Ask for the report that lists each entry with these fields:

| Field | Use in the split |
| --- | --- |
| Batch or settlement date | Ties the report to the bank credit |
| Batch total and entry count | The control figures to check first |
| Receiver or customer name | Identifies who paid |
| Individual ID or account reference | Links the entry to the customer record |
| Amount | The receipt to apply |
| Trace number | Finds the entry later if it is returned |
| Addenda text, if any | Names the invoices being paid |

Provider settlements follow the same shape as card processor payouts. [Payment reconciliation across processor, ledger and bank](/blog/payment-reconciliation) explains the general three-way tie-out, and [Stripe payout reconciliation to the bank and ledger](/blog/stripe-payout-reconciliation) covers one provider whose settlements can include bank debits alongside cards.

## Reading ACH addenda records for remittance detail

An addenda record is an optional ACH record attached to an entry to carry payment details, such as invoice numbers. Nacha's guide describes each addenda as holding an 80-position payment related information field. It says a CCD entry can carry one addenda, commonly called CCD+, while a CTX entry can carry up to 9,999 addenda records.

In practice that means a CCD+ payment has room for a short reference, perhaps one or two invoice numbers. A CTX payment can carry a full remittance in a standard electronic format, listing dozens or hundreds of invoices with amounts and deductions. Large customers paying many invoices at once often use CTX for that reason.

### Getting the addenda from your bank

Many banks do not show addenda on the statement or in the basic transaction export. They may be available in an ACH detail report, a remittance report or a separate file service, sometimes only on request. If a large customer says they send remittance with their ACH payments and you never see it, ask the bank where that information is delivered.

Treat the addenda as the customer's remittance. Apply the payment to the invoices it names, and record any deduction it lists. If the addenda total does not equal the entry amount, the customer's remittance is wrong somewhere, and that is a question for them before you apply anything.

## Splitting an ACH batch deposit into customer payments, step by step

Splitting an ACH batch deposit means recording each entry in the batch as its own customer receipt, so each customer's balance and each invoice is updated correctly. The bank deposit in the ledger then equals the sum of those receipts. Follow the same steps every time, starting with the control totals.

1. Find the bank credit and note its date, amount and description.
2. Pull the batch report or settlement report for the same date.
3. Check the report's batch total equals the bank credit, and note the entry count.
4. For each entry, identify the customer from the name or ID.
5. Apply each amount to the invoices named in the addenda or remittance, or to the invoices the payment schedule says are due.
6. Record all receipts as one deposit in the ledger, so it matches the single bank line.
7. List any entry you could not identify and move it to unapplied cash with a note.

Step 6 depends on the software. Most accounting systems let you group several customer payments into one deposit, which keeps the bank reconciliation one line to one line. If yours does not, record a clearing account for the batch and move the total to the bank account in one entry.

## Worked example: one ACH batch deposit split into seven payments

The example below is invented. A property services company collects monthly fees by ACH debit. On April 12 its bank statement shows one credit of 18,240.00, described as the company's ACH batch. The bank's batch report for that date lists seven entries. All figures are illustrative.

| Entry (example) | Customer | Reference | Amount | Applied to |
| --- | --- | --- | --- | --- |
| 1 | Elm Street HOA | C-1104 | 2,500.00 | April fee invoice |
| 2 | North Ridge Clinic | C-1120 | 1,840.00 | April fee invoice |
| 3 | Lakeview Apartments | C-1131 | 3,200.00 | April fee invoice |
| 4 | Corner Bakery | C-1142 | 950.00 | April fee invoice |
| 5 | Westgate Offices | C-1150 | 4,100.00 | April fee invoice |
| 6 | Pine Court Condos | C-1163 | 2,650.00 | April fee invoice |
| 7 | Harbor Storage | C-1170 | 3,000.00 | March and April fees, 1,500.00 each |
| | **Batch total, 7 entries** | | **18,240.00** | |

The report's total equals the bank credit, and the count matches the seven customers scheduled for that date. Six entries pay one invoice each. Entry 7 pays two months because Harbor Storage's March debit failed and was re-presented with April's; the payment schedule shows that, so the split is documented.

In the ledger, the seven receipts are grouped into one 18,240.00 deposit dated April 12. On the bank reconciliation, that deposit clears the single bank line.

## ACH batch deposit edge case: an entry returned after the batch posts

An ACH entry can be returned after the batch has posted, for example when the customer's account has insufficient funds. The bank then debits that one entry back, days later, as a separate line. The return must be matched to the original entry in the batch, not to the batch as a whole, and the customer's invoice reopened.

In the example, suppose Corner Bakery's 950.00 is returned on April 14. The bank statement shows a 950.00 debit described as an ACH return. The trace number on the return notice points to entry 4. Record the return against Corner Bakery, reopen its April invoice, and leave the other six receipts untouched.

Return codes tell you why the entry came back and whether you may present it again. [ACH return reconciliation and return codes](/blog/ach-return-reconciliation) covers reading those codes and handling returns that arrive after month-end.

The same ACH plumbing runs in the other direction. When a company pays its credit card by ACH from the bank, the debit is one payment on the card statement; [reconciling a credit card in QuickBooks](/blog/how-to-reconcile-credit-card-in-quickbooks) shows how that payment is recorded on the card side.

## What do you do with unknown entries inside an ACH batch deposit?

Unknown entries inside an ACH batch deposit are entries whose payer cannot be tied to a customer record. Search by name variants, by the individual ID field and by amount against open invoices. If none fits, record the entry in unapplied cash with its trace number and date, and keep the rest of the batch moving.

Unknowns are more common in provider settlements and in batches of credits sent to you than in debits you originate, because you chose every customer in an originated batch. When they appear in your own originated batch, check whether a customer record was merged or renamed after the batch was set up.

### Clearing them later

- Ask the bank for the full entry detail, including any addenda.
- Contact customers whose open invoices match the amount.
- Review unapplied cash weekly and record who is chasing each item.
- Never apply an unknown entry to the customer with the oldest balance just to clear it.

## ACH batch deposit mistake: recording the batch as one receipt

The common ACH batch deposit mistake is recording the whole credit as one receipt, often against a generic customer or straight to sales. The bank reconciliation ties, so it looks fine. But every customer still shows as unpaid, the aging is wrong, and when one entry is returned there is nothing to reverse it against.

The fix is to re-split the batch from the report. If the report is lost, the bank can usually reproduce the batch detail for a date.

Before any split, it helps to know the bank statement itself is complete. PreciseBankFlow foots each statement from opening to closing balance and matches its lines to your register, so a batch credit or a return debit that has no entry behind it is listed as an exception. [Request a spot](/get-started) to run it against your own statements.