The ACH accounts a bank or credit union balances every day
ACH reconciliation is rarely one account. An institution that originates for business clients and receives payroll and bill payments for its own customers or members runs several clearing and settlement accounts, each fed by a different report and each with its own cutover. The table below is the usual inventory.
| Account | External side | What has to agree | What usually breaks |
|---|---|---|---|
| ACH origination clearing (ODFI) | Originated file totals and ACH operator settlement | Files sent, entries accepted, settlement debited or credited, client accounts posted | A batch rejected or pulled after the client account was already debited |
| ACH receipt clearing (RDFI) | Incoming entries and settlement | Entries received, entries posted to accounts, entries rejected to exceptions | Entries to closed or frozen accounts that sit in exceptions instead of being returned |
| Federal Reserve or correspondent settlement account | Statement of account or correspondent statement | Net ACH settlement per window against the GL | Settlement posted in a different window or business day from the GL entry |
| ACH returns and reversals | Return and reversal reports | Each return against its original entry and the client or member account | Returns booked after the original was already written off, or never tied back |
| ACH exception and suspense | Core exception queue | Every item has a disposition and an owner | Items with no owner and no age, especially after a conversion |
| ACH operator fees | Monthly operator fee billing | Fees charged against the expense accrual | Fees debited to settlement with no GL entry |
Why ACH reconciliation breaks: settlement windows and return deadlines
Most ACH differences are not errors. They are timing, created by a schedule your core and your GL do not share. The FedACH processing schedule, effective September 12, 2022, settles Same Day ACH in three windows each business day and settles future-dated forward items at 8:30 a.m. ET on the settlement date. If your core posts on processing date and your GL books settlement from the statement, every window is a potential one day difference.
| FedACH window | Transmission deadline (ET) | Settlement (ET) |
|---|---|---|
| Same Day ACH, first window | 10:30 a.m. | 1:00 p.m. same day |
| Same Day ACH, second window | 2:45 p.m. | 5:00 p.m. same day |
| Same Day ACH, third window | 4:45 p.m. | 6:00 p.m. same day |
| Next day (future-dated) forward items | Several windows up to 2:15 a.m. | 8:30 a.m. on the settlement date |
Returns add a second clock. Under the Nacha Operating Rules most returns, including insufficient funds (R01) and account closed (R02), must be made within two banking days of the settlement date. Unauthorized returns on consumer accounts, such as R05, R07 and R10, can come back up to 60 calendar days after settlement. So an ACH debit that balanced last month can reopen as a return this month, and the reconciliation has to tie it to the original entry rather than treat it as new money. The master account side of the same settlement, with FIRD files and weekend FedNow cycle dates, is covered on Federal Reserve account reconciliation software.
Common ACH breaks and what the software does with them
| Break | What it looks like | Classification and suggested action |
|---|---|---|
| Window timing | Settlement in the 5:00 p.m. window, GL entry the next business day | Timing. Matched under the approved one day window and closed, with the rule recorded |
| Late return | An R01 settles two days after the debit it reverses, posted to the wrong clearing account | Missing reference. Tied to the original trace number and routed to payments operations for the correct posting |
| Duplicate posting | The same originated file posted twice to client accounts after a reprocess | Duplicate. The second posting goes to reversal under maker-checker, noted on the original item |
| Batch total difference | Settlement total differs from the sum of posted entries by one batch | Partial settlement. The settled batches match, the residual stays open against the batch that did not settle |
| Operator fee | A fee debit on the settlement account with no GL entry | Fee not accrued. Proposed posting to ACH expense, and the fee added to expected categories |
| Orphan exception | An incoming entry to a closed account sitting in exceptions for days | Missing reference. Routed with its age so it is returned inside the deadline instead of found later |
From a settlement day to worked items
Input
- Statement of account · Same Day ACH, 5:00 p.m. window · net credit 1,284,316.52 USD
- Core GL · ACH settlement account · 1,284,316.52 USD posted 2026-09-04
- Return report · R01 · trace 091000019004412 · 3,860.00 USD, settled 2026-09-03
- Core GL · returns clearing · no posting for trace 091000019004412
Output
- Matched, timing 1,284,316.52 USD. Same amount, one business day apart, inside the approved window for Same Day ACH settlement.
- Missing reference 3,860.00 USD. The R01 return settled but was never posted against the original debit.
- Suggested action: post the return to the originating client account under approval and close the original entry. Routed to Payments Ops, aged from the settlement date, with the return report attached.
Illustrative sample values. The trace number and amounts are invented for the example.
Nacha fraud monitoring rules and your reconciliation
Nacha's risk management amendments added fraud monitoring obligations in two phases. Phase 1 took effect March 20, 2026 for all ODFIs, for RDFIs with 2023 receipt volume above 10 million entries, and for originators, third-party senders and service providers above 6 million entries. Phase 2 took effect June 22, 2026 (the rule date of June 19 is a federal holiday) and removed the volume thresholds.
Reconciliation is not a fraud monitoring system, and Bankautomation does not claim to be one. What it does give the fraud and risk team is clean inputs: unauthorized returns tied back to the entries and originators they came from, entries to closed or frozen accounts with an age, and a record of who dispositioned each exception. A monitoring process that has to start from a messy clearing account is slower than one that starts from a worked queue.
ACH reconciliation software compared
Institutions shortlisting ACH reconciliation usually weigh the same options. The question that decides it is whether you need a month-end certification of the clearing account or a daily queue of differences someone works before the return deadline passes.
| Option | Good at | Weak at | Fits |
|---|---|---|---|
| Spreadsheets on core and ACH platform reports | No new vendor, fully flexible | No aging, no tie between a return and its original, and the method lives with one person | Low ACH volume with one settlement account |
| Trintech (Frontier, ReconNET, Adra) | High-volume matching and close. Frontier was built for US banks, and Trintech's credit union page lists ACH among the postings it reconciles | Several product lines, so check which one the proposal is for. Pricing is quoted | Institutions buying a broad reconciliation and close platform |
| ReconArt | Bank, card, ACH and GL reconciliation, with credit union customers such as Catalyst Corporate FCU reconciling Federal Reserve, ACH and RTP accounts | Pricing is quoted, though ReconArt states an average annual cost below $50,000 | Mid-size banks and credit unions wanting a reconciliation-focused platform |
| Bankautomation | Daily exception work: ACH, card, ATM and settlement breaks classified, routed and aged in one queue, with published pricing | A newer vendor, not a close checklist, and it does not originate ACH or replace your core | Payments and accounting teams that want a worked daily queue and a price up front |
If you are already comparing the larger platforms, the bank-specific guides to Trintech alternatives, BlackLine alternatives for banks and ReconArt alternatives set out pricing and fit side by side. If you settle ACH through a bankers' bank or corporate credit union rather than the Fed, the due from side is covered on correspondent bank reconciliation software.
What ACH reconciliation software costs
Most vendors quote per institution, so the first number arrives after a demo. Bankautomation publishes its prices. Operations is $1,200 a month for one process line, 250,000 matched items a month and three source connections, which covers ACH settlement for many community banks and credit unions. Platform is $3,900 a month and adds unlimited source connections, maker-checker approvals and SSO, which is where teams land once ACH, card, ATM and the GL feed one queue. Institution is $9,500 a month for multi-entity groups. Every limit is on the pricing page.
A rollout that starts with one settlement account
Step 01
Pick the account that hurts most
Usually the ACH settlement account or returns clearing. One account with a daily spreadsheet is a better start than every ACH ledger at once.
Step 02
Send a sample report from each side
A settlement or statement file, the ACH platform report and a GL export as CSV. Field mapping is configuration and versioned, not an integration build.
Step 03
Agree tolerances with your controller
The date window per settlement window, the fee schedule and the dollar threshold below which a difference is logged, each approved and recorded.
Step 04
Run in parallel, then retire the spreadsheet
Compare the worklist with the spreadsheet for a few cycles. When they agree, retire it for that account and add origination, receipt or card settlement next.
Try the matcher on a settlement sample
The resolver at the top of this page runs the same two pass matcher on a sample USD settlement file against core postings. It holds the kinds of differences ACH teams see every day: an entry that misses its posting by a few hundred dollars, a fee line with no GL entry, a settlement posted a day late and a batch that appears twice on the ledger side. Move the date and amount tolerances and watch which differences are absorbed and which stay as breaks. Card and ATM settlement run on the same engine, covered on ATM reconciliation software, and the three way view of instruction, settlement and posting is on payment reconciliation software.
Sample data only. The demo never receives customer, member or production data, and nothing you paste into it is stored.
Questions about ach reconciliation software
What is ACH reconciliation?
ACH reconciliation is the daily process of confirming that ACH entries originated and received, the settlement posted by the ACH operator, returns and reversals, and the postings in the core and general ledger all agree. The valuable part is the residue: every difference gets a cause, an owner and an age until it is resolved.
How do you reconcile ACH transactions?
Match the ACH platform detail to settlement by window and business day, then match settlement to the GL entry, then tie every return and reversal back to the original entry by trace number. Whatever is left becomes an exception with an owner. Software does the matching under approved tolerances, so people only work the true differences.
How long does a bank have to return an ACH?
Under the Nacha Operating Rules most returns, including R01 insufficient funds and R02 account closed, must be sent within two banking days of the settlement date. Unauthorized returns on consumer accounts, such as R05, R07 and R10, can be sent up to 60 calendar days after settlement.
When does Same Day ACH settle?
FedACH settles Same Day ACH at 1:00 p.m., 5:00 p.m. and 6:00 p.m. ET for files transmitted by 10:30 a.m., 2:45 p.m. and 4:45 p.m. ET. Future-dated forward items settle at 8:30 a.m. ET on the settlement date. A reconciliation that ignores the window creates one day timing breaks.
Does ACH reconciliation software work with our core, such as Jack Henry, Fiserv or FIS?
Sources are read as files rather than through a core integration, so what matters is that your core and ACH platform can export entry detail, settlement and the GL, for example as CSV reports. Field mapping is configuration, and the usual first step is a sample export from each source.
How much does ACH reconciliation software cost?
Most vendors quote per institution. ReconArt states an average annual cost below $50,000, and Trintech prices by quote. Bankautomation publishes its plans: Operations at $1,200 a month, Platform at $3,900 a month with unlimited sources and maker-checker, and Institution at $9,500 a month. See pricing.