Moving dental patients from cards to ACH: the fee math
A dental practice pays about 2.5 to 3.5 percent of card volume in processing fees. An ACH payment costs a flat fee under a dollar. The gap is real and the arithmetic is short. What stops most practices is not the fee but the posting: every ACH payment becomes a front-desk task unless something puts it into the ledger.
Dental practices pay about 2.5 to 3.5 percent of card volume in processing fees, and optimized practices get to 1.8 to 2.2 percent (Private Dental Alliance). An ACH payment costs $0.20 to $1.50 flat, or 0.5 to 1.5 percent capped around $5 (Ramp). Recurring payments are the candidate: membership plans, payment plans, orthodontic contracts. The work is not the fee. It is getting each cleared ACH payment matched to the right patient and posted into the practice management system without a person re-keying it.
What cards actually cost a practice
Card fees arrive in layers, and the layer a practice can see on the statement is the smallest one. Interchange, set by the card issuers, runs 1.45 to 2.65 percent plus $0.10 to $0.22 per transaction for dental practices, according to the Private Dental Alliance. Network assessments sit on top. Then the processor's markup, which is the negotiable part, and then the monthly line items: minimums, statement fees, PCI program fees, gateway charges, terminal rental.
Added up as an effective rate, total fees divided by total card volume, Dentist Merchant Services puts most dental offices at 2.5 to 3.5 percent all-in in 2025 and 2026, drifting higher for practices that key in a lot of payments or take rewards cards. The Private Dental Alliance reports the same unoptimized band, 1.8 to 2.2 percent for practices that have negotiated interchange-plus pricing, and a typical overpayment of $2,000 to $8,000 a year on the fixed fees alone.
Two things follow. First, the effective rate is the only number worth tracking, and most practices have never computed it. Second, negotiating the markup gets a practice from 3 percent to 2. Changing the payment rail gets it to a flat fee.
What ACH costs instead
An ACH payment moves money bank to bank, and the network cost is close to nothing. What a practice pays is the processor's price for the rail: $0.20 to $1.50 per transaction on flat pricing, or 0.5 to 1.5 percent on percentage pricing, usually capped around $5 (Ramp, August 2026). Ramp's comparison is the one to hold on to: a $5,000 invoice paid by card can cost $100 or more in fees, and by ACH less than a dollar.
ACH has costs cards do not. It settles in one to three business days rather than instantly. A payment can return for insufficient funds after it appeared to clear, which means the posting logic has to handle reversals. And the patient has to enroll once, with a bank account instead of a card. None of those is a reason not to do it. All three are reasons the path has to be built rather than switched on.
The math on a recurring payment
| Payment | Card at 2.85 percent plus $0.15 | ACH at $0.50 flat | Difference per payment |
|---|---|---|---|
| $150 membership plan, monthly | $4.43 | $0.50 | $3.93 |
| $250 payment plan installment | $7.28 | $0.50 | $6.78 |
| $400 orthodontic contract, monthly | $11.55 | $0.50 | $11.05 |
| $1,000 treatment balance | $28.65 | $0.50 | $28.15 |
Worked examples, not client results. Card rate uses the middle of the 2.5 to 3.5 percent band plus a $0.15 per-transaction fee inside the interchange range; ACH uses a mid-band flat fee from Ramp. Your processor's numbers replace these.
Multiply the difference by the number of recurring payments a month and by twelve, and you have the annual figure for your practice. We do not publish one for the practice we built this for, because they have not shared a measured number we can stand behind. The table gives you the method instead.
Why recurring payments are the candidate
One-time payments at the front desk are the wrong place to start. The patient is standing there with a card, the amount is unknown until the visit ends, and the enrollment friction of ACH is not worth a few dollars once. Recurring payments are the opposite on every count: the patient is already enrolled in something, the amount is fixed or scheduled, the payment happens without anyone at the desk, and it repeats every month for the life of the plan.
That is membership plans, in-house payment plans, and orthodontic contracts. A practice with two hundred patients on monthly plans has 2,400 payments a year on one rail or the other, each one carrying the fee difference in the table above, and each one needing to land on the right patient's ledger.
The posting problem
Here is why most practices that price the savings never collect them. A card autopay inside the practice management system posts itself. An ACH payment through a separate processor does not. Every cleared payment becomes a task: watch the processor, find the patient and the ledger, re-key the payment, reconcile outside the posting action. Two hundred plans is two hundred tasks a month. The fee savings turn into front-desk hours, and the front desk is already the constraint.
That was the operating question in our dental payment integration: how does a practice move recurring payments to ACH without manually reconciling every payment, and without replacing Dentrix? The fee was visible. The posting was the problem.
Compute the effective rate before you change anything.
Total card fees divided by total card volume, last three statements. If it is above 2.5 percent and you run membership or payment plans, the rest of this page is your project. If not, it is not.
What a working ACH path needs
Four parts, and the integration we shipped has all four. Anything that skips one moves the work instead of removing it.
- Matching. Each cleared payment resolves to one patient account. In our build, that happens on the clinic's own workstation, and patient identity never enters the cloud. An uncertain match stops and goes to staff instead of being guessed.
- Posting. The payment enters the practice management system through its existing interface, onto the right ledger, once. Idempotency and deduplication controls mean a retry cannot post twice.
- Exceptions. Ambiguous matches, returns, and reversals enter an exception state that stays visible and returns to a person with the detail attached.
- Read-back. After posting, the system reads the ledger back and records either confirmation or a structured failure. Nothing is assumed done.
The boundary is the part to write down first. In our build, the cloud service carries only the opaque payment information needed to retrieve work. Patient linkage, account context, posting detail, and every exception record stay inside the clinic. That boundary is what makes the path possible in a practice handling protected health information.
What it costs to set up
Three costs, with different shapes. The processor's ACH pricing is the per-payment fee above and it is negotiated like card pricing. Patient enrollment is front-desk time once per plan, and it is the part practices underestimate: a script, a form, and a month of asking. The integration is the build, and published bands put a custom workflow that reaches into a legacy practice management system at $15,000 to $25,000 (Layer3 Labs). Set against the per-payment difference in the table, that build pays back on plan volume, and a practice can compute exactly when.
The productized version of the path we built is Chomp, built to run inside Dentrix Classic. Our case study is the record behind it and states only what the record supports: the payment path, the local matching boundary, the exception handling, the posting controls, and the read-back were built, and the system is running in production.
How to compute your own number
- Pull three months of processor statements. Total fees divided by total card volume is your effective rate.
- Count the recurring payments: membership, payment plans, orthodontic contracts. Number per month and average amount.
- For each, card fee at your effective rate versus ACH at your processor's flat fee. Multiply by twelve.
- Subtract the enrollment effort and the integration cost, spread over the life of the plans.
- Then ask the only question that matters: after the switch, who posts each payment? If the answer is a person, the savings are hours, not dollars.
The fee is the easy part. The ledger is the project.
What to hold on to
- Cards cost a practice 2.5 to 3.5 percent all-in. Negotiation gets to about 2 percent. Changing the rail gets to a flat fee under a dollar.
- ACH costs a flat fee under two dollars a payment. It settles in days, can return, and needs one enrollment per patient. All three shape the build.
- Recurring payments are the candidate. Membership plans, payment plans, orthodontic contracts. Fixed amounts, no one at the desk, twelve times a year.
- The posting is the project. Without integration, every ACH payment becomes a front-desk task. The savings turn into hours.
- Four parts: match, post, stop, read back. Patient identity stays inside the clinic. Uncertain matches stop for staff. Nothing is assumed done.
Questions owners ask us
How much does a dental practice pay in credit card processing fees?
Most dental offices pay 2.5 to 3.5 percent of card volume all-in (Dentist Merchant Services), and practices on negotiated interchange-plus pricing get to 1.8 to 2.2 percent. Interchange alone runs 1.45 to 2.65 percent plus $0.10 to $0.22 per transaction (Private Dental Alliance). The number to track is the effective rate: total fees divided by total card volume.
How much does an ACH payment cost a dental practice?
Typically $0.20 to $1.50 per payment on flat pricing, or 0.5 to 1.5 percent capped around $5 on percentage pricing (Ramp). A $1,000 payment costs about $28 by card at a typical dental rate and under a dollar by ACH. Processor pricing for ACH is negotiated the same way card pricing is.
Can a dental practice move patients to ACH without replacing Dentrix?
Yes. Our dental payment integration does exactly that: a clinic-side service retrieves each cleared ACH payment, matches it to the patient account on the clinic workstation, posts it into Dentrix through the existing interface, and reads the ledger back to confirm. Uncertain matches stop for staff. It is running in production.
Which dental payments should move to ACH first?
Recurring ones: membership plans, in-house payment plans, and orthodontic contracts. The amount is fixed, the patient is already enrolled in something, nobody is at the desk when it runs, and it repeats monthly. One-time front-desk payments are the wrong place to start because the enrollment friction outweighs a single fee.
Why do practices that switch to ACH not see the savings?
Because each ACH payment through a separate processor has to be matched to a patient and posted into the ledger by hand. Two hundred plans becomes two hundred front-desk tasks a month, and the fee savings turn into hours. The savings appear only when posting is automated and exceptions stop for a person.
How much does it cost to set up ACH posting into a practice management system?
Three costs: the processor's ACH fee per payment, front-desk time to enroll each patient once, and the integration. Published bands put a custom workflow reaching into a legacy practice management system at $15,000 to $25,000 (Layer3 Labs). Chomp is the productized version of the path we built for Dentrix Classic.
Sources
Fee figures are quoted from published guides; the worked examples are ours and are labeled as such; the integration facts come from our own record. Checked September 5, 2026.
- Private Dental Alliance, "Dental Credit Card Processing: Cut Hidden Fees by 40%". December 2024. Interchange ranges, effective-rate bands, fixed fees, and typical overpayment.
- Dentist Merchant Services, "Average Credit Card Processing Fees for Dental Offices (2026)". January 25, 2026. The all-in band and the effective-rate method.
- Ramp, "ACH Processing Fees: Costs, Types and How to Save". August 14, 2026. ACH fee ranges and the card comparison.
- Layer3 Labs, "AI Consulting Rates and Pricing in 2026". Updated June 17, 2026. The legacy-integration build band.
- Dental payment integration, our implementation record, and Chomp, the product built around the same path.