Get a personalized demo of Stuut and see how it can help with AR automation.
The low transaction fees of ACH payments often hide a massive hidden cost for AR teams: the manual labor required to parse remittance data. A single bulk ACH deposit from a distributor can represent dozens of separate invoices, and without automation, matching each payment to the right open item in your ERP creates a recurring manual burden for AR specialists at every close cycle.
This guide breaks down exactly how the ACH network operates in 2026, from settlement timelines and NACHA rules to the specific return codes that drag down your DSO. It also covers how modern AR teams use AI agents to eliminate manual cash application and resolve exceptions autonomously.
ACH is the electronic network that moves most B2B payments in the United States. Understanding how it works matters, but understanding where it creates bottlenecks for your AR team matters more. The cost advantage is obvious. The hidden operational cost is what happens after the payment arrives.
ACH stands for Automated Clearing House, the U.S. electronic payment network that moves funds between bank accounts in batches. Nacha governs the ACH network and sets the rules that every participating financial institution must follow.
For B2B AR teams, ACH is the dominant payment rail for recurring invoices because it's inexpensive, direct, and highly automatable. Unlike checks, ACH payments arrive digitally and can be matched against open invoices in your ERP. Unlike credit cards, ACH fees are flat and low.
ACH is a batch processing network, not a real-time rail. Payments accumulate throughout the day and move in files between banks and ACH operators. The two ACH operators are the Federal Reserve and The Clearing House. This batch structure directly affects when cash lands in your account and when you can match it against invoices. A payment initiated Monday afternoon may not appear in your bank file until Wednesday, depending on the processing window it hit.
Every ACH transaction follows the same path through the banking system, regardless of whether it's a $500 invoice or a $500,000 equipment payment. The sequence involves your customer's bank (the ODFI), the central ACH operator, and your bank (the RDFI). Understanding this flow clarifies why settlement takes one to three days and where delays or return codes typically occur.
The ODFI (your customer's bank, for incoming AR payments) validates the originator's authorization and formats the file correctly. The RDFI (your bank) posts funds and issues return codes when something goes wrong. This distinction matters for AR teams because Nacha's rules place warranty obligations on the ODFI. When a return code reflects incorrect account details provided by the originator, the ODFI bears responsibility for resolving that error, so knowing which institution originated the transaction tells you where to direct your follow-up.
Nacha sets the compliance standards for everyone in the ACH network. Two 2026 rule changes directly affect B2B AR teams:
For AR teams, this means your ACH payment setup needs documented authorization records, fraud controls, and audit trails. Keep customer authorization records for at least two years after a customer's final payment.
An ACH credit is a "push" payment. The payer initiates the transfer and sends funds from their account to yours. In a typical ACH credit flow, your customer initiates payment through their bank's ODFI interface using your routing number and account number as the destination. You receive the funds without taking any action.
ACH credits are the most common B2B invoice payment mechanism for established customers. Because the payer controls the timing and amount, your AR team must then match each payment to open invoices. When a customer sends one ACH credit covering 15 invoices, that single deposit hits your bank account and your team must identify which invoices it satisfies, often with incomplete remittance detail.
An ACH debit is a "pull" payment. With the customer's authorization, you initiate the transfer and pull funds from their account into yours. This is how subscription billing, utility payments, and installment plans typically work.
For B2B AR, ACH debits work well for customers on contracted payment schedules. Before pulling funds, you must obtain written authorization from the customer identifying the payment amount, frequency, and the account to be debited. Nacha requires at least 7-10 days advance notice before any change in timing or amount for recurring debits, and you must retain those authorization records for two years after the final payment.
Whether your AR team receives ACH credits or initiates ACH debits depends on your customer agreements and payment terms. If your customers prefer to pay on their own schedule, the credit model fits best. If you have customers on contracted payment terms where predictability matters, ACH debits give you more control over timing. Either way, the cash application challenge is the same: match what arrives in your bank to specific open invoices in your ERP.
Standard ACH transfers settle in one to three business days from initiation. A payment initiated Monday before the cut-off window typically settles by Wednesday. Payments submitted Friday afternoon may not settle until Tuesday the following week because the network only processes on business days. For AR teams, this delay creates a reconciliation gap where funds are in transit but not yet posted to your AR subledger, creating a timing difference that must be accounted for during close.
Same Day ACH settles within hours on the same business day the payment is initiated. The per-transaction limit is $1 million, which covers most mid-market B2B invoices. For a manufacturer collecting on a $400,000 equipment invoice, Same Day ACH eliminates a two-day float without the $25 to $50 cost of a wire transfer. AR teams can offer Same Day ACH when customers are past due and need to close an aging item fast, or at month-end when a two-day delay would push a payment into the next reporting period and affect DSO calculations.
Banks submit Same Day ACH files through three transmission windows each business day:
Missing a cut-off adds a full business day to settlement. Know your bank's ODFI deadline before promising customers same-day posting.
Most businesses pay between $0.20 and $1.50 per ACH transaction, depending on volume and processor. The cost advantage over alternatives is significant at scale.
A $10,000 invoice paid by card at 2.5% costs $250 in processing fees. The same invoice paid by ACH costs under $1.50. Wires cost $25 to $50 per outgoing transfer and are justified when same-day settlement matters more than cost. For routine B2B receivables, ACH is the cost-effective default, and the per-transaction savings compound quickly across a portfolio of several hundred monthly invoices.
When customers refer to an "ACH number," they typically mean the routing number designated for electronic ACH transactions at their institution. For many banks this is the same 9-digit number used for all transaction types, but some larger institutions assign a separate routing number specifically for ACH. Confirm which number applies before initiating the first payment.
Confirm both fields are complete before attempting payment. Either one missing or incorrect will generate an R03 return.
Before initiating ACH debits, collect signed or electronically authenticated authorization from each customer and store it for a minimum of two years after the final transaction. Use bank account verification tools before the first payment to confirm routing and account numbers are valid and prevent R03 returns from the start.
The practical AR challenge isn't receiving ACH payments. It's matching them to invoices. Your customer initiates payment, funds hit your bank, your bank generates a remittance file, and your AR team must match deposits to open invoices in the ERP. Bulk deposits covering multiple invoices are hardest to match because remittance details are often incomplete or unstructured. This is where manual work piles up and where collections teams lose hours to tasks that AI agents now handle autonomously.
R01 means the receiver's account didn't have enough funds to cover the debit at the time of processing. You can retry up to twice within 30 calendar days of the original authorization date. Contact the customer before retrying to confirm payment readiness. If R01 returns repeat on the same account, suggest an alternative payment method such as a credit or debit card, wire transfer, or a manually paid invoice rather than retrying the ACH debit.
R02 means the account has been closed. Don't retry. Contact the customer immediately for updated banking details. A common cause of R02 returns is a customer switching banks without providing updated ACH details, so when an R02 appears on an active account, confirm whether the customer has recently changed banking institutions before re-initiating any future payments.
R03 means no account matching the provided details was found at the receiving bank. The routing number may be correct while the account number is wrong, or both fields may be invalid. Verify both with the customer directly. R03 is preventable through upfront bank account verification before the first ACH transaction.
Validate bank account details before initiating the first transaction using a verification service. Send prenote ACH entries to confirm account validity before live payments. Proactively request updated banking information from customers who have had prior returns, rather than waiting for the next failed transaction.
Real-Time Payments (RTP) via The Clearing House and FedNow from the Federal Reserve offer instant settlement, 24/7/365. Unlike ACH batch processing, these networks process each payment individually and funds are available within seconds. Use these rails for urgent end-of-period collections or emergency supplier payments where a two-day ACH window creates a business problem. The trade-off is lower adoption among mid-market payers compared to ACH, with RTP showing higher adoption rates than FedNow currently.
Some large buyers, particularly in retail and CPG, pay invoices via virtual card to capture extended float and card rewards. For AR teams, virtual card acceptance means paying 2.5% to 3.5% in processing fees unless you negotiate a rebate.
Use this framework to choose the right rail:
Stuut serves mid-market manufacturing, distribution, and industrial services companies, including organizations with 5,000+ employees, that need autonomous AR execution rather than workflow tools that still require manual intervention.
ACH is cost-effective, but matching bulk deposits and resolving return codes still drains AR resources at most mid-market companies. The bottleneck isn't collecting the payment. It's everything that happens after the funds land in your account.
Stuut's cash application engine parses remittance data from bank files and applies a proprietary matching algorithm that draws on customer history, payment patterns, and terms to identify the correct invoices. We achieve a 95%+ automated match rate by handling exact matches, partial payments, short-pays, overpayments, and multi-invoice wires without manual intervention.
When a bulk ACH deposit covers dozens of invoices, Stuut breaks the deposit into sub-payments and matches each one separately. All matched entries are typically posted to SAP, Oracle, NetSuite, or Dynamics immediately upon matching, eliminating the payment matching backlog that delays month-end close.
PerkinElmer reduced overdue invoices from 50% to 15% in one year using Stuut's autonomous collections and cash application, collecting $300M while automating 80% of their tail customer portfolio.
Stuut connects to your ERP via API credentials without modifying chart of accounts, workflows, or GL configuration. Standard SAP, Oracle, NetSuite, and Dynamics environments with straightforward configurations typically go live in 3 to 4 days. Organizations with heavily customized ERP environments, multi-entity structures, or higher data complexity typically complete within the full 6 to 10 day go-live window. Timing depends on configuration complexity rather than company size alone, so mid-market organizations with non-standard setups should plan for the longer window. Once connected, matched ACH payments are posted to the AR subledger with no batch uploads or manual journal entries.
Bishop Lifting deployed Stuut across 45 branches in six weeks and reduced overdue receivables by 35%, unlocking $3M in working capital. The AR team shifted from processing routine payments to managing complex disputes and customer relationships that require human judgment.
When Stuut can't match a payment to an open invoice because remittance details are missing or incomplete, it proactively contacts the customer by email, SMS, or voice to request the information needed to complete the match. This outreach happens automatically using the customer's preferred communication channel and full account context from prior interactions, without involving your AR Analyst.
Exceptions requiring human judgment, complex deductions, payment plan negotiations, or legal disputes get escalated to your team. Most other exceptions are designed to resolve autonomously.
Initiation and settlement are not the same moment. Standard ACH: your customer initiates on Day 1, funds settle in your account on Day 2 or Day 3. Same Day ACH: initiation and settlement occur the same business day if submitted before the 4:45 p.m. Eastern cut-off. Funds become available once your RDFI posts the credit, which may be same-day or next-morning depending on your bank's posting schedule.
ACH reversals are strictly limited by Nacha's rules. According to Nacha guidelines, you can reverse an ACH entry only under specific conditions: the wrong amount was sent, the wrong account was credited, a duplicate payment was initiated, or the entry was sent on the wrong date. You cannot reverse an ACH payment because a customer disputes an invoice, and the reversal must occur within five banking days of the settlement date with written notice to the receiving bank.
Same Day ACH has a per-transaction limit of $1 million as of 2026, though Nacha has approved an increase to $10 million effective September 17, 2027. Standard ACH has no hard Nacha-imposed per-transaction cap, though your ODFI may set internal limits. Entries submitted above the $1 million threshold are not rejected by the ACH operator but are automatically processed for next-day settlement in the next available processing window. For immediate same-day settlement of payments over $1 million before the 2027 limit increase, a wire transfer is the appropriate rail.
The 2026 Nacha fraud monitoring requirements, effective June 22, 2026 for all non-consumer participants, make documented fraud controls a compliance requirement. Combine bank account verification at onboarding, authorization record retention, and automated exception monitoring to meet these requirements without adding headcount.
Stuut maintains SOC 2 certification and GDPR compliance, and all customer communications generate an audit trail that posts directly to your ERP, giving your Controller the documentation needed for close and compliance reviews. AR teams that automate ACH cash application and exception handling don't just save hours. They reduce DSO, improve cash flow predictability, and give AR Analysts time to work on disputes and relationships that actually require their expertise. Book a demo to see how Stuut automates ACH payment matching and exception handling across your customer portfolio.
Both ACH and ABA routing numbers are 9-digit codes that identify financial institutions, but they serve different purposes. ACH routing numbers are designated exclusively for electronic transactions such as direct deposits and bill payments, while ABA routing numbers cover both electronic and paper transactions including checks. The two also differ structurally: ACH routing numbers typically begin with 61 to 72, while ABA routing numbers typically begin with 00 to 12. When your customer provides an "ACH number," confirm it is the routing number designated for electronic transactions at their institution rather than the ABA number printed on a check. If a payment is returned with an R03 code, verify the correct ACH routing number directly with your customer's bank.
A 15-digit identifier assigned to each ACH entry by the originating bank, used to locate and investigate specific transactions within a limited context. Because different banks apply the same numbering logic independently, trace numbers can repeat across institutions or over time and are not globally unique. Use the trace number when contacting your RDFI or ODFI to track a delayed, missing, or returned payment.
The per-transaction limit for Same Day ACH is $1 million as of early 2026, though Nacha has approved an increase to $10 million effective September 17, 2027. Transactions above the current threshold are automatically processed for next-day settlement in the next available processing window rather than being rejected. For immediate same-day settlement of payments over $1 million, a wire transfer is the appropriate rail.
You can retry an R01 (insufficient funds) return up to two times as a new transaction within 30 calendar days of the original authorization date. After two retries, contact the customer to arrange alternative payment.
ODFI (Originating Depository Financial Institution): The bank that initiates an ACH transaction on behalf of the originator. The ODFI is responsible for validating the originator's authorization and formatting the ACH file correctly.
RDFI (Receiving Depository Financial Institution): The bank that receives the ACH file and credits or debits the recipient's account. The RDFI issues return codes (R01, R02, R03) when a transaction cannot be completed as instructed.
Nacha: The governing body that sets the rules, standards, and compliance requirements for the U.S. ACH network. Nacha represents more than 9,000 financial institutions and publishes the official ACH Operating Rules.
Remittance data: The payment detail information a payer provides alongside an ACH transfer, typically including invoice numbers, PO references, or payment breakdowns. Incomplete remittance data is the primary cause of unmatched bulk deposits and cash application delays.
Cash application: The process of matching incoming payments to open invoices in the AR subledger and posting GL entries in the ERP. Manual cash application for bulk ACH deposits is a time-consuming recurring task for AR Analysts and a primary bottleneck Stuut eliminates.
DSO (Days Sales Outstanding): A measure of how long, on average, it takes a company to collect payment after a sale is made. Faster cash application and lower return rates directly reduce DSO by converting AR balances to cash more quickly.
