How to Accept ACH Payments: A Small Business Guide to Bank Transfers

ACH stands for Automated Clearing House, a nationwide electronic network that moves money between U.S. bank accounts in batches. It is governed by NACHA, the organization that writes and enforces the operating rules every participating bank and processor must follow. When you accept an ACH payment, you are not swiping a card or touching a card network at all. You are instructing one bank to send funds to, or pull funds from, another bank using account and routing numbers.

There are two basic directions on the network. An ACH credit pushes money out, the way an employer sends payroll into an employee's account. An ACH debit pulls money in, which is what happens when you collect a payment from a customer's bank account with their authorization. Both flow through the same clearing system, and both are processed in batches rather than one at a time.

Batch processing is the reason ACH is not instant. Instead of settling each transaction the moment it happens, the network gathers entries, sorts them, and settles them at set times through the banking system. Standard ACH typically clears in one or more business days, and same-day ACH exists for faster movement, though availability and cutoff times depend on your provider and the amounts involved. That short delay is the practical tradeoff for paying pennies on the dollar compared with card fees.

The clearest difference between ACH and cards is how you pay to accept them. Card fees are usually a percentage of each sale, so they scale up with the size of the transaction. ACH is typically a small flat fee per transfer, sometimes with a modest percentage capped at a low ceiling. On a large invoice, that gap is enormous: a percentage-based card fee on a five-figure payment can cost real money, while the ACH fee on the same amount stays roughly flat.

Speed is where cards win. A card authorization happens in seconds and funds typically settle quickly, while ACH moves in batches and clears over a business day or more. For a walk-in retail sale or anything where you need instant confirmation, cards remain the better tool. ACH is built for payments where a short wait is perfectly acceptable in exchange for a much lower cost.

That tradeoff points straight at ACH's ideal use cases. It shines for recurring billing, subscriptions and memberships, large B2B invoices, rent or tuition, and any situation where the same customer pays you repeatedly. Offering ACH alongside cards lets customers choose, and it often nudges your biggest, most predictable payments onto the cheapest rail you have.

Most small businesses accept ACH through one of three channels, and the right one depends on how you already collect money. The first is your payment processor or gateway. Many processors that handle your card transactions can also enable ACH, which means one provider, one relationship, and often one dashboard for both card and bank payments. For a business that already accepts cards, this is frequently the simplest path.

The second channel is your invoicing or billing software. A lot of accounting and invoicing tools let you turn on bank-transfer payments so a customer can pay an emailed invoice directly from their bank account. This works well if invoices are already the center of how you get paid, since the ACH option lives right where your customers are clicking to pay.

The third channel is a dedicated ACH provider. These specialize in bank transfers and can offer more control over things like verification, batch scheduling, and handling returns at volume. They tend to fit businesses with heavy recurring billing or a lot of ACH volume, where the added tooling is worth managing a separate relationship. For many merchants, though, adding ACH to an existing card processor is the fastest way to start.

Setting up ACH follows a predictable sequence, and none of the steps are exotic once you know the order. You start by choosing an ACH-capable provider and going through their underwriting. Just like a card merchant account, an ACH provider reviews your business before approving you to pull funds from customer accounts, so expect to share basic business details, ownership information, and an idea of your expected volume and average transaction size.

Next comes collecting bank details safely and getting authorization. You can gather a customer's account and routing number directly, or use a bank-linking and verification method that confirms the account electronically. However you collect it, that data must be handled securely, and you must obtain and record the customer's authorization to debit their account. That authorization is not optional under NACHA rules, and keeping proof of it is what protects you if a payment is ever questioned.

From there, the flow is operational. You submit payments to your provider, which batches and sends them into the ACH network for settlement. You then watch for the outcome: successful settlements, plus any returns or notifications of change that come back through the network. Reconciling those responses, and re-collecting on returns when appropriate, becomes a small routine rather than a one-time task.

Authorization is the heart of ACH compliance. Because you are pulling money from someone's bank account, NACHA rules require that you have the account holder's permission before you do it, and that you keep a record of that permission. The specifics of how you capture consent depend on how the payment originates, which is why the network defines several authorization types for different situations. You do not need to memorize the technical codes, but you should know that the method must match the channel.

At a high level, a few authorization types come up most often. WEB covers payments a customer authorizes online. TEL covers payments authorized over the phone. PPD is used for consumer payments such as recurring memberships where you have a signed or written authorization on file. CCD is used for business-to-business payments between company accounts. Your provider will guide you to the right type, but the underlying rule is consistent: get clear consent, and keep proof of it.

The rest of compliance is about records and data security. Retain authorizations for the period the rules require, keep clear records of each transaction, and protect stored bank account information the same way you would protect any sensitive financial data. Handling ACH data carelessly is both a compliance problem and a fraud risk, so treat account and routing numbers with the same discipline you apply to card data.

ACH payments can come back, and understanding returns is central to running the channel well. A return is the network's way of telling you a payment did not go through, and each return carries a code explaining why. The most common is insufficient funds, the ACH equivalent of a bounced check, where the customer's account did not have enough money to cover the debit. Others signal a closed account, a wrong account number, or a customer who says they never authorized the payment.

Unauthorized returns deserve special attention. If a customer disputes that they permitted a debit, that return is not just a failed payment, it is a signal the network watches. This is exactly why your recorded authorization matters, and why NACHA sets thresholds on return rates. Merchants who exceed allowable return rates, especially for unauthorized or administrative returns, can face scrutiny or lose ACH access, so keeping those rates low is part of staying in good standing.

The practical defense is verification and good process. Verifying that a bank account is valid and belongs to your customer before you debit it cuts down on returns for wrong or closed accounts. Confirming funds availability where your provider supports it reduces insufficient-funds returns. And a clean authorization record is your best protection against unauthorized-return disputes. Build a simple routine to catch returns, re-collect where appropriate, and watch your return rate the way a card merchant watches chargebacks.

Weighing ACH against your other payment options is easier once the tradeoffs are laid out plainly. On the upside, ACH is inexpensive, especially on large amounts, because it is charged as a low flat fee rather than a percentage. It is well suited to recurring and predictable billing, it reduces the friction of chasing customers for repeat payments, and it keeps big invoices off the more expensive card rails. For the right use cases, those savings add up quickly.

The downsides are mostly about speed and failure handling. ACH settles over a business day or more rather than instantly, so it is not the tool for moments that need immediate confirmation. Payments can be returned after the fact for insufficient funds or other reasons, which means you cannot always treat a submitted payment as final until it clears. And because you are handling bank account data, you take on responsibility for securing it and following NACHA authorization rules.

None of that makes ACH better or worse than cards in the abstract. It makes ACH a specialized tool that is excellent for some payments and poorly matched to others. The businesses that get the most from it are the ones that offer it alongside cards and steer their large, recurring, and B2B payments toward it, while leaving instant retail sales on cards.

ACH is the quiet workhorse of business payments. It will never replace cards for instant, in-person sales, and it is not trying to. What it does exceptionally well is move large, recurring, and business-to-business payments cheaply and reliably, turning a percentage-based card fee on a big invoice into a small flat cost that barely moves with the amount. For any business sending invoices, billing on a schedule, or collecting from other companies, that is a meaningful improvement to both margins and cash flow.

The smartest approach for most merchants is not to choose between ACH and cards, but to offer both and let each payment find the rail that fits. Cards handle speed and impulse; ACH handles size and repetition. Set it up with a capable provider, get authorization right, verify accounts to keep returns low, and it becomes a low-maintenance channel that quietly saves money month after month. SalenPay can enable ACH acceptance alongside your card processing so your largest and most predictable payments run on the most cost-effective option you have.