To request an ACH payment from a customer, you need three things in order: a valid authorization that meets NACHA’s rules for the channel you used to collect it, the customer’s correct banking details (validated before the first debit), and a way to submit the transaction to the ACH network through your bank or a payment processor. Everything else — timing, fees, notices, returns — flows from those three. Two rulebooks govern the process: NACHA’s operating rules for the ACH network itself, and Regulation E, the federal rule that protects consumers in electronic fund transfers.
Step 1: Get the Customer’s Authorization
You cannot pull a dollar from a customer’s account without their explicit permission first. NACHA requires the authorization to spell out the terms of the debit before you initiate it: the amount, the date or frequency of the charges, the customer’s account and routing numbers, and clear language showing the customer agreed. For recurring charges or anything scheduled in advance, the authorization also has to explain how the customer can revoke it.
How the authorization has to look depends on how you collected it. NACHA sorts these into Standard Entry Class codes, and the three you will usually see for consumer debits are:
- PPD (Prearranged Payment and Deposit): the customer signs a paper or electronic form. This is the typical setup for recurring bill payments.
- WEB (Internet-Initiated Entry): the customer authorizes the debit online or on a mobile device. You have to authenticate them with commercially reasonable methods and capture evidence of the authorization, including timestamps and IP addresses.
- TEL (Telephone-Initiated Entry): the customer authorizes verbally. One-time TEL debits require either a recorded oral authorization or a written confirmation sent afterward. Recurring TEL debits require you to send the customer a copy of the authorization.
Electronic signatures are legally valid for ACH authorizations under the E-SIGN Act, which provides that a signature or contract cannot be denied legal effect solely because it is electronic.1Office of the Law Revision Counsel. 15 USC 7001 – General Rule of Validity For WEB entries, NACHA wants you to keep both the authorization itself and a record of how you verified the customer’s identity and tied them to the authorization. Screenshots of the signup page, login timestamps, and audit logs all count.2Nacha. WEB Proof of Authorization Industry Practices
Step 2: Collect and Validate the Banking Details
Every ACH debit needs four pieces of data: the name on the account, the account type (checking or savings), the nine-digit routing transit number for the bank, and the account number. One wrong digit and the transaction bounces back, and you pay the return fee.
For WEB debits, NACHA requires more. Before you use a new account number for the first time, you have to confirm it belongs to a legitimate, open account that can accept ACH entries. A general fraud detection system is not enough on its own if it skips account validation. Acceptable methods include sending a prenotification (a zero-dollar test entry), micro-deposit verification, or running the account through a third-party validation service or API.3Nacha. Supplementing Fraud Detection Standards for WEB Debits If the customer later changes their account, you have to validate the new number before debiting it.
Skipping validation is where most ACH problems begin. Invalid accounts generate returns, returns cost money, and a pattern of them flags your business inside NACHA’s enforcement system.
Step 3: Submit the Debit Through a Processor or Your Bank
Once you have the authorization and the validated banking data, the transaction goes into your processing system. Most small and mid-sized businesses use a payment processor or merchant portal that handles the technical formatting. You give the platform the routing number, account number, amount, and SEC code, and it packages everything into the standardized file format the ACH network expects.
Larger organizations sometimes work directly with an Originating Depository Financial Institution (ODFI), uploading batch files in NACHA’s fixed-width text format. The ODFI reviews the file and submits it during the next processing window. Batching multiple transactions in a single file is standard and lowers your per-item cost.
Most businesses pay somewhere between $0.20 and $1.50 per ACH transaction, sometimes with a small percentage of the amount layered on top. Volume brings those costs down. Same-Day ACH costs more than standard ACH because the Federal Reserve adds a surcharge for same-day forward items and your processor marks it up further.4Federal Reserve Banks. FedACH Services 2026 Fee Schedule
Step 4: Know When the Money Actually Moves
ACH is a batch system, not real time. Your transaction sits in a queue until the next processing window opens. The Federal Reserve’s FedACH service runs on a published schedule with specific transmission deadlines through the day.5Federal Reserve Financial Services. FedACH Processing Schedule
For standard (non-same-day) debits, the latest transmission deadline is 8:00 p.m. ET, Sunday through Thursday, and those entries settle at 8:30 a.m. ET the next business day. In practice, standard ACH debits take one to two business days to settle depending on when your file hits the network.
Same-Day ACH gives you three windows per business day:
- Window 1: submit by 10:30 a.m. ET; settle at 1:00 p.m. ET
- Window 2: submit by 2:45 p.m. ET; settle at 5:00 p.m. ET
- Window 3: submit by 4:45 p.m. ET; settle at 6:00 p.m. ET
Each Same-Day ACH payment can be up to $1 million.6Nacha. Same Day ACH Settled is not the same as available. Funds can show as settled in your account but still sit on hold for 24 to 48 hours while the receiving bank confirms no return is coming.
Recurring Debits When the Amount Changes
If you are debiting the customer on a recurring schedule and the next charge will differ from the last one or from the amount they originally authorized, Regulation E requires you to send written notice of the new amount and date at least 10 days before the transfer.7eCFR. 12 CFR 1005.10 – Preauthorized Transfers You can give the customer the option of receiving notice only when the amount falls outside an agreed range, but you have to tell them they have the right to receive notice of every variation.
Subscription businesses that change pricing trip over this constantly. Missing the 10-day notice does more than create a compliance problem. It gives the customer stronger grounds to dispute the charge as unauthorized when their bank asks.
Returns You Should Expect
Some of your debits will come back. When a customer’s bank cannot process one, it returns the entry with a reason code. The ones you will see most often:
- R01 (Insufficient Funds): not enough money in the account. The bank must return it within two banking days.
- R02 (Account Closed): the account was closed after the authorization was signed.
- R03 (No Account): the routing and account combination does not match a real account, usually a data entry error.
- R08 (Payment Stopped): the customer put a stop payment on this specific transaction.
- R10 (Unauthorized): the customer says they never authorized the debit.
- R11 (Not in Accordance with Authorization): the customer authorized a debit but says this one does not match the agreed amount, date, or frequency.
R10 and R11 are the ones that hurt. NACHA treats both as unauthorized returns, and high rates can trigger enforcement against your ODFI, which will come back to you.8Nacha. Differentiating Unauthorized Return Reasons If you get an R11 and the error was yours, you can correct the entry and resubmit within 60 days of the return settlement date. Every return costs money on top of the lost payment, which is why validating accounts before the first debit protects your margins as much as your compliance record.
What Your Authorization Does Not Override
Your customer keeps rights under Regulation E that your authorization form cannot sign away.
A customer can stop any preauthorized transfer by telling their bank at least three business days before the scheduled debit date. The stop-payment request can be oral or written. The bank may require written confirmation within 14 days of an oral request, but the oral request is binding immediately.7eCFR. 12 CFR 1005.10 – Preauthorized Transfers
For transfers a customer calls unauthorized, they have 60 days from the date their bank sends the statement showing the charge to report the problem.9eCFR. 12 CFR Part 1005 – Electronic Fund Transfers, Regulation E Inside that window the bank must investigate and provisionally credit the customer. A solid authorization record is your defense, which brings up what you have to keep and for how long.
Records You Have to Keep
You must retain authorization records for two years from the date the authorization is terminated or revoked. That is two years from the end of the relationship, not two years from the last transaction, and it is the point businesses most often misread.10Nacha. RMAG – Preventing and Recovering from Operational Errors and Accidents If a customer disputes a charge 18 months after it ran, you will need the original authorization, your identity verification evidence, and proof that the authorization was tied to that specific person.
Storing customer bank account numbers brings a security obligation too. Businesses that originate two million or more ACH payments per year must render account numbers unreadable when stored electronically. NACHA does not require a specific technology; encryption, tokenization, and truncation all qualify.11Nacha. Supplementing Data Security Requirements Below that threshold the rule does not reach you, but a breach that exposes customer account numbers will cost more than encryption ever would.
NACHA enforces its rules against financial institutions through a National System of Fines, and your ODFI passes the consequences down to you.12Nacha. Report of Alleged ACH Rules Violation If your unauthorized return rate drifts up, expect a call from your bank long before NACHA gets involved. Clean authorizations, account validation before the first debit, and the 10-day notice for varying amounts are what keep that call from coming.