ACH Processing for Small Business: When to Use ACH, eCheck, Card

Admin • November 9, 2026

Share this article

A client replies to your monthly invoice with one line: "Can I just pay you from my bank account?" Meanwhile, three paper checks sit in a desk drawer waiting for a bank run you have been putting off since Monday, and the card fee on last month's largest invoice still stings. Owners rarely start looking into ACH processing for small business as a research project. Usually a specific payment forces the question: which payments belong on a bank transfer, and which should stay on a card?


The answer is rarely all one or the other. Small businesses that add bank transfers often end up running both: cards at the counter and for one-time buyers, ACH for the recurring and high-ticket payments where the math favors it. Getting there takes a clear picture of what ACH and eCheck are, which payments to move, what setup involves, and how to offer it without annoying the customers who like paying by card.


What ACH and eCheck Actually Are (and Why the Terms Blur)

ACH stands for Automated Clearing House. It is the electronic network that processes bank-to-bank transfers in the United States. An eCheck is a digital version of a paper check that runs on that same ACH network. Both are bank-to-bank transfers, and in practice the terms are often used interchangeably, including on Monument's own ACH page.


That blurring is mostly harmless, but there is a useful distinction many providers draw. "eCheck" often refers to a one-time, check-like debit: the customer enters their routing and account numbers once, replacing a check they would otherwise mail. "ACH" is used more broadly for any transfer on the network, including recurring pulls where the account information is stored and the payment runs on a schedule. All eChecks run on ACH; not every ACH payment is an eCheck. If you are comparing eCheck vs ACH across processors, know that some quote longer clearing for one-off eChecks, so timing depends on the processor and it is worth asking.


Under the hood, the mechanics are straightforward. According to Nacha's explainer on how ACH payments work, Nacha governs the ACH Network and payments move under the Nacha Operating Rules. ACH debits pull money: your business, acting as the Originator, sends payment instructions through your bank, called the ODFI, to your customer's bank. ACH credits push money the other direction, initiated by the customer from their bank or accounts payable system. You do not need to memorize any of this to accept bank transfers, but the pull-versus-push distinction matters when you are the one initiating the debit, because it puts authorization rules on your plate (more on that in the setup steps below).


Why Small Businesses Add ACH to the Mix

The core reason is cost, and the gap is not subtle. Per Monument's ACH page and pricing FAQ, ACH fees typically range from $0.25 to $1.50 per transaction, or 0.5% to 1.5% of the transaction amount, compared with roughly 2.5% to 3.5% for card processing. On a $1,000 transaction, card processing costs $25 to $35; the same payment via ACH costs $0.25 to $1.50. Those are typical ranges, not quotes. Still, the shape is clear: because ACH is often priced per transaction while cards are priced as a percentage, the bigger the invoice, the bigger the gap.


Per-transaction pricing is only part of the cost, so ask any provider for the full picture before you compare: any monthly gateway or platform fee, what a returned payment costs, and what same-day ACH adds if you plan to use it. Those numbers vary by provider and account, and they are what turns a per-item rate into a real monthly cost.


ACH payments for small business tend to earn their keep on the invoices that hurt. A gym running monthly memberships on cards feels the fee drag every billing cycle. A property manager collecting rent, a bookkeeper or IT firm billing monthly retainers, an HVAC company running service plans, a contractor taking a deposit on a job: in each case, a large or predictable payment is being routed through a card fee structure built for convenience, not for size.


What ACH is not is a card replacement. Monument is direct about this: ACH is a complement for specific transaction types, not a substitute for card processing, and it is not the right fit for every transaction. The evaluation that matters happens before anything is set up: your transaction mix, your average ticket, and how your customers actually prefer to pay. A business with mostly small counter sales will see little benefit. A business sending monthly invoices in the thousands will notice quickly.


One practical concern comes up right away: settlement. Standard ACH settles in one to three business days, and cards typically settle in one to two, so the difference is minimal for most businesses. If timing ever is a problem, same-day ACH exists through some processors for an additional fee; Nacha's Same Day ACH information covers the mechanics. For most recurring and invoiced payments, a possible extra day matters less than the fee difference.


When to Move a Payment to ACH, and When to Keep It on Card

The choice is less about product names and more about how the customer pays you.


Strong fits for ACH, based on Monument's published use cases, include:


  • Recurring billing and subscriptions
  • B2B and high-ticket invoices
  • Electronic invoicing with a bank payment link
  • Membership and dues payments
  • Service businesses, contractors, and healthcare providers who invoice remotely and take eCheck through a hosted payment page or virtual terminal


A landscaper billing monthly service plans fits. So does a studio with memberships, or a consumer on an installment plan. The common thread is a predictable payment relationship, a large ticket, or both.


Now the flip side. Keep payments on card when:


  • It is a counter sale or a one-time consumer purchase, where card is typically more convenient and customers often prefer the rewards
  • The customer is international, because standard ACH only works with US bank accounts, while cards are accepted globally


The rewards point deserves a moment. Plenty of consumers actively want to pay by card because of points, cash back, or simple familiarity. Pushing them off card for a small purchase saves you little and can cost you goodwill. This is exactly why ACH works best as an option you attach to invoices and schedules, not a mandate you impose at the register.


If your payments lean B2B, there are adjacent plays worth knowing about, like Level 2 and 3 data and net terms, covered in Monument's B2B processing guide. Membership organizations can look at ACH for nonprofit dues and pledges. And if you are still sorting out card acceptance by sales channel, Monument's small business card processing overview covers that ground.


eCheck vs ACH vs Card: How They Compare for a Small Business


Side by side, the three look like this. Cost and settlement figures are the typical ranges published on Monument's ACH and pricing pages, not quotes.


Factor ACH (recurring or stored) eCheck (one-time) Card
How it is paid You pull payments on a schedule from a bank account kept on file Customer enters routing and account numbers for a single payment Card tapped, inserted, keyed, or entered online
Typical cost $0.25 to $1.50 per transaction or 0.5% to 1.5% Same typical ACH range; confirm per-item and return fees 2.5% to 3.5%
Settlement 1 to 3 business days for standard ACH 1 to 3 business days; some processors quote longer for one-off eChecks 1 to 2 business days
Authorization Standing authorization covering amount, frequency, and how to revoke Authorization for that one payment Customer presents or enters the card at the time of sale
Dispute exposure Lower than cards; returns and unauthorized claims still possible Lower than cards; returns and unauthorized claims still possible Higher chargeback risk; EMV, 3D Secure, and fraud tools help
Best small-business fit Rent, retainers, memberships, service plans Deposits and one-time invoices Counter sales and one-time consumer purchases

Three things the table cannot fully show are worth a closer look.


First, ACH returns happen. A return occurs when a payment cannot be processed: typically insufficient funds, a closed account, or incorrect account information. It is the bank-transfer equivalent of a declined payment, and it surfaces after the fact rather than at the point of sale. Monument configures account verification where it is available and helps you understand the return code and the next step when one comes through.


Second, lower dispute exposure is not zero risk. A consumer can dispute an ACH debit as unauthorized, and under Nacha's unauthorized return rules, the return timeframe for unauthorized consumer debits is 60 days. That is a long tail, and it is exactly why authorization records matter. A clear record of what the customer agreed to, and when, is what you and your processor will need if a payment is ever questioned.


Third, cash flow timing. One to three day settlement means a large scheduled pull does not land the same day it runs. For most businesses this is a scheduling detail, but if you are timing a big pull against a payroll date or a supplier payment, plan around it.


None of these are reasons to skip ACH payment processing for small business, the same way occasional card chargebacks are not a reason to stop taking cards. They are the operating realities that come with a lower-cost rail, and they are manageable with decent habits: verify accounts, keep authorizations, and have a plan for returns.


How to Set Up ACH Processing for Small Business Payments


Setting up ACH processing for a small business takes a short stack of prerequisites and a handful of decisions, roughly in this order.


1. A business bank account. The rails run bank to bank, so you need a business account to receive the funds. If you already accept cards, you have one.


2. A processor or gateway that originates ACH. Not every payment provider offers ACH origination. You are looking for a platform that lets you manage card and bank-transfer payments together rather than bolting on a second vendor.


3. Onboarding and underwriting. Because ACH debits pull money from customer accounts, providers underwrite the businesses that originate them. Expect the provider to review your business before approving ACH, the same way a card merchant account gets reviewed. Timing and paperwork vary by provider and by account, so ask for a realistic timeline, including merchant account approval, before you plan a launch date.


4. A way to collect authorization. Before you debit a customer's account, you need their authorization. This is a rule, not a courtesy. Per Nacha's guidance on online payment authorizations, an online consumer debit authorization should include express authorization language, the amount (or a range for recurring payments), the date or frequency, the account number, the routing number, and revocation language for recurring or scheduled payments. Keep proof of the consent, such as a record with a timestamp. Confirm the specific requirements with your processor.


5. Account validation. For consumer debits authorized online, Nacha's account validation rule requires validating the account number before its first use and whenever it changes. Acceptable methods include a prenotification entry, micro-entry verification (the small test amounts you may have seen when linking a bank account to another app), or a commercially available validation service. Many processors handle this behind the scenes. Confirm how yours does it, since validation also cuts down on returns for incorrect account information. As with authorization, your processor can tell you exactly what it requires.


6. Choose how customers pay you. This is the part you and your customers see day to day. Monument's online and remote payments options cover the main channels: a secure payment link embedded in an email or text invoice, a hosted payment page customers can be directed to, virtual terminal entry by your staff for phone and mail payments, or a recurring schedule you set once. The right mix depends on how your customers interact with you.


For the specifics of setup and configuration, Monument's ACH and eCheck solutions page walks through the service details.


How to Offer ACH Without Losing Customers



The businesses that get the most out of ACH treat it as an option, not a mandate. Put bank transfer on invoices and recurring schedules, where the savings are real and the payment relationship is predictable. Keep card at the counter and for one-time purchases, where customers expect speed and want their rewards.


Frame it to your customers as convenience, because for them it genuinely is: no check to write, no stamp to find, no card number to hand over or keep on file. "You can pay this invoice directly from your bank account" is a simple sentence that lands well, especially on large invoices.


For recurring payments, the mechanics matter more than the pitch. Set the schedule once, send a notice before the first pull so the debit is never a surprise, and decide in advance who handles a failed or returned payment and when you retry, within whatever retry rules your processor applies. A returned ACH payment handled with a quick, friendly phone call is a non-event. The same return handled by silence becomes a relationship problem.


The customers who prefer card keep their card. The customers who were mailing checks anyway get something faster. Your largest and most predictable payments stop paying card-sized fees. Monument's ACH page notes that routing even a portion of transactions through ACH can meaningfully lower the overall effective rate.


How Monument Sets This Up


Monument's process follows the same sequence. It starts with the same assessment described above, then use case identification, then gateway and platform selection, then setup and integration, including configuring the ACH account and recurring schedules where applicable. After launch, Monument provides ongoing support for ACH returns and failed payments.


Monument's ACH page highlights two gateways that also handle cards. iPOSpays supports ACH and eCheck through its cloud gateway alongside card transactions, with reporting in one platform, which suits integrated POS and multi-channel businesses. iPOSpays also syncs with QuickBooks Online. Accept Blue supports ACH and eCheck alongside cards via a hosted payment page, virtual terminal, or API, with recurring ACH billing fully supported, which suits recurring billing, B2B invoicing, eCommerce, and healthcare. In both cases, card and ACH are managed in one place instead of on two separate systems.


Many businesses combine programs, for example running card processing at the counter plus ACH as an option for invoiced customers, and Monument's payment programs overview lays out how those combinations work.


See Whether ACH Fits Your Payment Mix


If you are looking at a stack of checks, a recurring invoice list, or a card fee line that has grown uncomfortable, the useful next step is not a quote. It is a read on which of your payments belong on ACH and which should stay on card, based on your actual payments. Monument, founded on Colorado's Western Slope, offers a free evaluation that does exactly that, and if the benefit does not justify the change, you will hear that too.


Start a free evaluation or call (970) 239-1307.


Recent Posts

Barista making espresso while a cashier rings up a customer on a coffee shop POS system
November 16, 2026
Coffee shop POS system guide: modifiers, orders to the bar, mobile ordering, loyalty, small-ticket tips, offline mode, and hardware for a small counter.
Customer at a food truck window reaching toward a card payment terminal on the counter
By Admin • November 12, 2026
Food truck POS system guide: what matters at the window, how cellular and offline mode work, setup types compared, real costs, and what to ask before you buy.
Team reviewing charts and documents at a table while planning nonprofit finances
By Admin • November 6, 2026
Credit card processing for nonprofits: how donations and events drive fees, what to check on a statement, and how ACH and fee recovery fit.
Hand holding a card terminal while a customer holds a payment card over it in a small shop
By Admin • November 2, 2026
What an offline POS system really does in an outage: what keeps running, why offline card payments can decline later, and what to ask before you buy.
Cashier behind a busy convenience store counter with snack shelves and a lighter display behind him
By Admin • October 29, 2026
A convenience store POS system has to keep a busy counter moving: fast scans, a big catalog, tobacco age checks, and processor choice. What to test first.
Customer holding a card to a payment terminal at a small shop counter as the cashier looks on
By Admin • October 26, 2026
Small business credit card processing works best when the setup matches how you get paid: counter, mobile, invoices, online, or recurring. What to ask first.
Customer paying at a small shop counter card terminal while the clerk waits
By Admin • October 26, 2026
Cash discount credit card processing explained: how the program runs day to day, Monument's flat monthly tiers, state rules, signage, and who it fits best.
Hands holding two printed merchant processing statements over a desk with a keyboard, mouse and gree
By Admin • October 24, 2026
Merchant statement analysis made practical: read your processing statement line by line, calculate your effective rate, and spot hidden or creeping fees.
Liquor store clerk at the checkout counter with shelves of wine and spirits behind
By Admin • October 23, 2026
Choosing a liquor store POS system? Compare age verification, case-break inventory, processor choice, and Korona vs Exatouch, plus questions to ask a vendor.
Patient holding a phone to pay at a clinic reception desk with a card terminal
By Admin • October 22, 2026
Credit card processing for medical practices: where patient payments stall, which tools fit each step from check-in to payment plans, and what to ask vendors.
Show More