ACH Payment

Your company moved from paper checks to ACH payments 18 months ago, and AP costs went down. Then a vendor called to say they hadn't received a payment your system showed as processed. The ACH file had gone to the bank, but the payment was returned for an invalid routing number, and the return notice landed in an email inbox nobody had checked in three days. By then the vendor had escalated, the relationship was strained, and your team had to reissue the payment by hand. ACH (Automated Clearing House) payments are electronic fund transfers processed through a US banking network that moves money between accounts in batches. They carry most business payments for payroll, vendor payments, and recurring transactions. The appeal is lower cost and less handling than checks or wires. The catch is that the process doesn't end when your bank confirms the batch was sent. It ends when the funds settle in the recipient's account and no return code arrives. Most AP teams handle the first half well. The second half (monitoring for returns, reconciling settlement, and handling exceptions) is where payments that look complete turn into problems.

How ACH payments work

An ACH payment starts when your company, as the originator, creates a payment file and submits it to your bank, the Originating Depository Financial Institution (ODFI). The ODFI passes the file to an ACH operator, either the Federal Reserve or The Clearing House, which routes the transactions to the Receiving Depository Financial Institution (RDFI), the bank that holds the vendor's account. Standard ACH settlement takes one to two business days. Same-day ACH, available since 2016, settles within the same business day if submitted before the cutoff windows. The point most AP teams miss is that bank confirmation that a file was received and processed does not confirm that each payment settled. ACH works on a return window. If a payment is rejected for an invalid account number, closed account, incorrect routing number, or insufficient funds, the RDFI has up to two business days for standard returns to send back a return entry with a reason code. Unauthorized transaction returns can take up to 60 days. Without active monitoring for those return codes, your system can show a payment as processed while the vendor never received the funds. Prenote verification, a zero-dollar test transaction sent before the first live payment to validate the bank account, exists to catch invalid banking details before money moves. Most AP platforms support it. Many teams skip it.

ACH as a payment rail

To send ACH payments, your company has to be set up as an ACH originator, either directly with your bank or through a payment processor that originates on your behalf. That setup includes daily origination limits, which matter when a large payment run could exceed the threshold and need bank approval. Timing needs attention. ACH batches have cutoff windows, typically mid-afternoon, and anything submitted after the cutoff processes the next business day. For companies managing cash closely, that one-day gap between intended payment date and actual settlement affects both the cash forecast and vendor relationships. Same-day ACH narrows it but carries per-transaction fees that standard ACH doesn't. Returns create a reconciliation problem. A returned payment may post as a debit back to your bank account one to two days after the original credit appeared to clear. If your AP system reconciles against bank statement data, the return may not match to the original payment automatically. Teams that rely on AP system balances instead of bank statement reconciliation can carry payments as complete when the funds have already come back. The return reason code tells you what to do next: R01 for insufficient funds, R02 for account closed, R03 for no account found, R04 for invalid account number. Depending on the code, you reissue, contact the vendor for updated banking details, or escalate.

How platforms handle it

When you evaluate an AP automation platform for ACH, most demos focus on payment creation: uploading bank details, scheduling batches, receiving confirmation. The more revealing test is what happens when a return comes in. A well-built platform ingests return files from the bank, flags the affected payment as returned instead of completed, creates an exception record with the return reason code, and routes it to the right AP team member. Weaker implementations need someone to check the bank portal for returns and then update the AP system by hand. Some platforms show returns as alerts in the payment dashboard. Others bury them in a raw bank file import that has to be parsed manually. The question to ask during evaluation: how does the system tell the AP team a payment was returned, and what does the exception workflow look like from the return notice through reissuance and reconciliation? Platforms that connect bank return data directly to vendor records, so the vendor's banking details can be flagged as invalid and updated before the next payment run, close a gap that manual processes leave open.

Questions to ask before selecting an ACH payment solution

• Does the platform support prenote verification before the first live ACH payment to a new vendor bank account?
• How does the system handle ACH return notifications: automated ingestion and flagging, or manual bank portal review?
• What return reason codes does the platform surface, and does it link them to vendor records for banking detail updates?
• Does the platform support same-day ACH, and how does it manage cutoff windows across time zones?
• How are ACH origination limits managed, and what happens if a batch exceeds the daily limit mid-run?
• What does the reconciliation workflow look like when a returned payment must be matched against the original bank transaction?

Common mistakes

The most common ACH mistake is treating bank batch confirmation as payment confirmation. A file the bank has acknowledged has entered the clearing network; it has not necessarily settled in the vendor's account. AP teams that close out payment records at batch confirmation, instead of after the return window has passed, carry a false picture of payables status. The second mistake is not actively monitoring return notifications. ACH returns arrive on a predictable timeline, but only if someone is looking for them. A bank notification inbox that goes unchecked for days turns a return window into a collection problem. Automating return file ingestion into the AP system and routing exception alerts to named team members, not a shared inbox, closes the gap. The third mistake is skipping prenote verification for new vendors. A zero-dollar test transaction costs almost nothing next to reissuing a live payment, handling a vendor escalation, and untangling the reconciliation entry when the return arrives days after the original payment run.

ACH against wire transfer

ACH is batch-processed, low cost, and reversible in defined circumstances under the Nacha rules. A wire is processed individually, settles the same day, costs more, and is effectively final once sent. That difference drives the fraud exposure: wires are the preferred target for payment redirection because they cannot be pulled back, which is why payment runs usually route high-value and new-supplier payments through extra verification.

Comparing AP automation

AP tools separate on what happens to the exceptions: the invoices that do not match a PO, arrive without one, or need a second approver. Once ACH Payment is settled as a requirement, read the Accounts Payable Automation Software category guide for how the market splits, then weigh the Stampli profile against the Tipalti profile on that requirement rather than on the feature list. Our Tipalti pricing breakdown records what the vendor publishes and what is quote-based. The BILL against Stampli comparison sets two of them side by side on the same criteria. Before you book demos, put your own numbers through the AP automation savings calculator so the business case is written down before a vendor writes it for you.

Frequently asked questions

Related terms

AP Aging Report, Approval Workflow, and Duplicate Invoice Detection come up in the same workflow as ACH Payment, and the rest of the AP automation cluster is indexed in the finance operations glossary.