To accept ACH payments on an invoice, add a clearly labeled payment instructions block that lists your bank’s nine-digit routing number, your account number, the account type (checking or savings), and the legal name on the account. That’s the minimum the payer’s bank needs to push money to you. Everything else on this page is about getting those details right, helping the payment match the right invoice, and knowing what to expect after the payer hits send.
The Banking Fields the Payer Needs
Four data points route an ACH transfer to the correct account:
- Routing number — the nine-digit code identifying your bank or credit union, sometimes called the ABA routing number.
- Account number — the number for the specific checking or savings account where funds should land.
- Account type — checking or savings. The network processes these differently, and picking the wrong one triggers a return.
- Account holder name — the legal name on the account, which the receiving bank uses to confirm the transaction matches its records.
A transposed digit or a mismatched account type doesn’t just slow things down. It produces an ACH return that can carry fees for both sides. Verify every field against a bank statement or a voided check before the details go on any invoice.
How to Format the Invoice
Put the banking details in their own section, labeled “Payment Instructions” or “ACH Payment Information,” and keep them separate from the line items. Burying routing and account numbers inside a service description is a reliable way to stall an accounts payable clerk. Most accounting software has a dedicated field for payment instructions; a basic spreadsheet template works too, as long as the information is easy to find.
Alongside the banking fields, the invoice should carry your legal business name (matching the bank account), a unique invoice number, the amount due, and the due date. Some payees also add an Employer Identification Number so the payer’s bookkeeper can reconcile at tax time. If the customer is a larger company, ask whether they need a purchase order number on the invoice. A missing PO reference is one of the most common reasons corporate AP departments hold payment.
Electronic invoicing platforms often embed a secure payment link or QR code that pre-fills the banking fields when the payer scans or clicks. That removes the transcription errors that come with manually typing long strings of digits. If your tool offers it, use it.
Helping the Payer Attach Remittance Details
A frequent headache with ACH is matching an incoming deposit to an open invoice. A lump sum lands with minimal identifying information and you’re left guessing what it covers. The ACH file format handles this through addenda records that travel with the payment and carry invoice numbers, PO references, discount adjustments, and similar detail.
Two standard entry class codes handle remittance differently. CCD+ allows one addenda record per payment, which is enough for a single-invoice payment. CTX (Corporate Trade Exchange) supports up to 9,999 addenda records per transaction, formatted using the X12 820 standard, and is built for a single payment that covers dozens of invoices.
Delivery of that data is not automatic. Not every bank passes addenda records through to the account holder. If you take ACH payments regularly from business clients, ask your bank whether it delivers addenda information and in what format. Without that, the remittance detail your payer carefully attached may never reach you.
Credit or Debit: Which Way the Money Moves
An ACH credit is a “push.” The payer logs into their bank or payment platform, enters the banking details from your invoice, keys the amount, and sends the money. This is the usual setup for invoice payments: you send the invoice, the payer pushes funds on their own timeline.1Nacha. How ACH Payments Work
An ACH debit is a “pull.” You initiate the transaction and pull funds from the payer’s account. This works for recurring charges like subscriptions or monthly retainers. ACH debits require explicit authorization from the payer before the first transaction, and the authorization rules are stricter than for credits.1Nacha. How ACH Payments Work
When You’ll See the Money
The old three-to-five-business-day rule of thumb is outdated. Nacha estimates that about 80% of ACH payments settle in one business day or less.2Nacha. The Significant Majority of ACH Payments Settle in One Business Day or Less ACH debits, by rule, cannot settle more than one banking day in the future. Credits settle same day, next day, or within two banking days, with most landing within one.1Nacha. How ACH Payments Work
Same Day ACH handles faster settlement for transactions that meet intraday cutoff times, with a per-transaction limit of $1,000,000.3Nacha. ACH Payments Fact Sheet Most banks charge a small premium for it. Late-day submissions and weekend transfers won’t process until the next federal business day, since the ACH network doesn’t run on weekends or bank holidays.
You’ll often see a pending credit before the funds are actually available for withdrawal. The gap between “pending” and “available” is set by the receiving bank’s hold policies, not the ACH network. If you’re relying on an incoming ACH payment to cover something the same day it posts, build in a buffer.
When Payments Come Back
Returns happen, and they aren’t always the sender’s fault. The receiving bank has two business days to return a transaction for most common issues, and the return arrives with a reason code. The ones you’ll see most often:
- R01 – Insufficient funds. The payer’s account didn’t have enough to cover the debit.
- R02 – Account closed.
- R03 – No account. The account number doesn’t match any open account at that bank.
- R04 – Invalid account number. The structure is wrong (too few digits, bad format).
- R07 – Authorization revoked.
- R08 – Payment stopped. The payer placed a stop-payment order with their bank.
- R10 – Not authorized. The receiver says they never gave permission. This code has a 60-calendar-day return window and is the one most tied to disputes.
R03 and R04 usually mean someone typed the banking details wrong on the invoice. Validate the account information before sending your first invoice with new payment details. For ACH debits initiated online, Nacha rules require originators to validate first-use account numbers to confirm the account is real and open.4Nacha. Account Validation Resource Center Micro-deposit verification, prenotification entries, and third-party verification services all qualify.5Nacha. Supplementing Fraud Detection Standards for WEB Debits
Authorization Rules if You Plan to Pull Payments
If you intend to debit a client’s account instead of waiting for them to push funds, get proper authorization before initiating anything. Under the Nacha Operating Rules, a debit authorization to a consumer account must include the amount, timing, and terms of the debits, along with instructions for how the payer can revoke authorization. The originator has to give the consumer a copy and be able to produce proof of authorization if the bank asks.6Nacha. The Importance of Compliant ACH Authorizations
Consumer debit authorizations must be in writing and signed or similarly authenticated. An electronic signature or online checkbox during checkout qualifies.7Nacha. Meaningful Modernization Becomes Effective Sept. 17, 2021 ACH credit transactions also require authorization, but the format rules are less prescriptive.6Nacha. The Importance of Compliant ACH Authorizations Skipping the authorization step for debits exposes you to R10 returns, potential fines, and the risk of losing your ability to originate ACH transactions at all.
The payer keeps their own protections. Federal law lets a consumer stop any preauthorized ACH debit by notifying their bank at least three business days before the scheduled transfer date. The notice can be oral or written, though the bank may require written confirmation within 14 days of an oral stop-payment order.8eCFR. 12 CFR 1005.10 – Preauthorized Transfers A disputed debit can also be clawed back from your account well after you thought it settled, so keep clean authorization records. If you can’t produce documentation that the payer agreed, the dispute will go against you.
Protecting the Account Data You Collect
Collecting a customer’s routing and account number creates a data security obligation. Under Nacha’s Operating Rules, businesses that originate or transmit more than 2 million ACH entries a year must render account numbers unreadable when stored electronically. The rule is technology-neutral: encryption, truncation, tokenization, or letting your bank store and tokenize the numbers all qualify.9Nacha. Supplementing Data Security Requirements
Even well below that 2-million threshold, keeping bank account numbers in a plain-text spreadsheet or an email thread invites trouble. A breach that exposes customer banking data can generate fraud losses, regulatory attention, and reputational costs that dwarf the price of a proper encryption tool. If you’re a small operation collecting ACH details from invoices, store that information in an encrypted file or a payment platform with built-in security rather than a shared drive. The Nacha threshold sets a mandatory floor. Common sense sets a lower one.