Finance Index
What is an ACH return and how is it different from an ACH rejection?
Reference guide to ACH returns and rejections, including payment timing, method choices, control points, reconciliation, and vendor communication.
A rejection happens before processing - the bank or network refuses the file or item (format error, limit breach), so no money ever moves. A return happens after processing - the receiving bank sends the payment back with a return code (closed account, no account, unauthorized). Returns mean money moved and came back; both reopen the question of how the vendor actually gets paid.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| An ACH return | A rejection happens before processing - the bank or network refuses the file or item (format error, limit breach), so no money ever moves. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| What do the common ACH | R01: insufficient funds (debits). | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Payment impact | The account number didn't match an open account at that routing number; verify the details directly with a known vendor contact (never by replying to an email that supplied them), correct the record, and re-pay. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| What does r02 "account closed" | The vendor's account was closed after you captured details; re-collect through a secure, authenticated channel with verification against vendor history - bank-detail changes are prime BEC territory. | Keeps vendor records and payment decisions reliable. |
| How long after sending can | Most business-to-business returns occur within two banking days of settlement; certain unauthorized-entry scenarios extend longer, so don't treat a settled payment as immovable until several days have passed. | Reduces payment errors, timing issues, and reconciliation cleanup. |
What do the common ACH return codes mean?
R01: insufficient funds (debits). R02: account closed - re-collect details through a verified channel. R03: no account / unable to locate - the account number doesn't match an open account; recheck digits and re-verify with the vendor. R04: invalid account number structure. R16: account frozen. R29: corporate customer advises not authorized - the receiver's bank returned your entry because their customer hasn't authorized it (common when corporate accounts use debit blocks/filters; for credits, usually a screening or account-restriction artifact). Each code tells you whether the fix is data, authorization, or the vendor's bank.
We got an r03 on a vendor payment - what do I do?
The account number didn't match an open account at that routing number; verify the details directly with a known vendor contact (never by replying to an email that supplied them), correct the record, and re-pay.
What does r02 "account closed" mean and how do I re-collect details safely?
The vendor's account was closed after you captured details; re-collect through a secure, authenticated channel with verification against vendor history - bank-detail changes are prime BEC territory.
How long after sending can an ACH still be returned?
Most business-to-business returns occur within two banking days of settlement; certain unauthorized-entry scenarios extend longer, so don't treat a settled payment as immovable until several days have passed.
Why would a vendor's bank return our credit as r29?
R29 reflects the receiving corporate customer's authorization controls - often ACH blocks or filters on their account that don't yet include your company ID; the vendor needs to whitelist your originator ID with their bank.
What's the correct accounting treatment when a payment is returned?
Reverse or void the payment so cash is restored and reopen the invoice (or link the return to it) - never leave a returned payment applied, or the vendor balance and bank rec both lie. Mechanics vary by ERP; the invariant is that invoice status, payment status, and cash all reflect the return.
What is an ACH noc and am I required to act on it?
A notification of change tells the originator that account details have changed (e.g., post-merger routing numbers); Nacha rules require you to update your records promptly - typically within six banking days or before the next entry.
Our entire batch was rejected before processing - usual causes?
File format errors, exceeded exposure limits, insufficient funding or prefunding, expired credentials, or duplicate-file detection; the bank's acknowledgment file states which.
What's a normal ACH return rate for AP payments and when should we worry?
Vendor-credit return rates should sit well under 1%; a rising rate is a vendor-master data quality signal - stale records, unverified onboarding - before it's a banking problem.
The vendor's bank returned the payment but the vendor insists the details are correct - how do I break the deadlock?
Give the vendor the return code and trace number and have them take both to their bank; the return code is the receiving bank's statement of fact, and the fix (wrong digit, account type mismatch, filter) gets resolved on their side.
What's the difference between a returned and rejected payment in terms of whether money moved?
Rejected: money never left. Returned: money left and came back - which matters for cash timing, vendor communication, and how you reverse it in the ledger.
Stampli perspective
Stampli's validation guardrails block payments when vendor banking details are missing or unverified - preventing the bad-data returns that account for most ACH failures - and payment status tracking surfaces failed payments with actions to resolve and resubmit, keeping invoice and payment state consistent.