Every month-end, you turn into a part-time bill collector. The work wrapped up weeks ago (the books closed, the retainer hours logged, the plan payment due), but the money hasn't moved. So you send the polite nudge, then the firmer one, then you sit there deciding whether it's worth picking up the phone.
Here's the part worth noticing. By the time a bill ages to 45 or 60 days, you've already lost the round. The fix isn't a sharper reminder or a sterner tone. It's moving the whole question upstream, to the day the client signs on.
Get a card or bank account on file at engagement, authorize the recurring charges in writing, and let the predictable money run itself: retainers, monthly bookkeeping fees, payment plans. You stop being the bank.
Why the chase is a design problem, not a discipline problem
Think about what a 45-day-old invoice really represents. The service is delivered, the client's happy, and you're financing their operation out of your own cash flow. That's a loan you never agreed to make, at zero interest, with collection costs stapled on.
Professional practices are especially exposed here. Your revenue is recurring by nature: the monthly close, the quarterly retainer, the payment plan on a bigger matter. Recurring revenue that still needs a manual "please pay" every cycle isn't really recurring. It's just recurring friction.
Autopay fixes the structure instead of your willpower. You collect authorization once, at the moment the client is most motivated (they want you to start), and the money then arrives on schedule without anyone sending a thing.
Ask for the card at the start, not the end
The reason most practices skip this is social, not technical. Asking for a card up front feels pushy, like you're bracing for trouble before you've done a minute of work. So reframe it. You're not screening for deadbeats, you're setting up how billing works, the same way you'd set up a portal login or a document request.
Fold it into onboarding, where it belongs. When a client signs the engagement letter, that's the natural place for payment details too. One line carries most of the weight: "We keep a card or bank account on file so your monthly fee runs automatically and you never get a late notice. Which would you prefer?"
Notice what that sentence does. It states the practice as normal, names a benefit the client actually feels (no late notices, no interrupted work), and offers a choice instead of a demand. Lead with bank account over card when you can, because ACH fees run a fraction of card processing and account numbers rarely expire.
- Tie it to a benefit they feel. "So we never pause your work to chase a payment" beats "so we get paid on time."
- Offer ACH first. Lower fees for you, and bank details change far less often than cards.
- Make it the default path. If autopay is simply how new clients get set up, almost nobody opts out.
Put the authorization in writing, then automate the paper
A verbal "sure, charge my card" won't protect you if a client disputes a charge six months later. You need a signed authorization that spells out the amount (or how it's calculated), the frequency, and the plain fact that it recurs until they cancel. Your payment processor almost certainly has a standard recurring-authorization form sitting right there. Use it.
This is where a little automation earns its keep. The authorization can be an e-sign form the client completes during onboarding, filed automatically with their record. Each time a charge runs, the system emails a receipt. When a card is about to expire, the client gets a heads-up before the charge fails, not after.
None of that needs custom software. A mainstream payment processor paired with your practice management tool handles most of it out of the box. What you're automating is narrow and well defined, which is exactly the kind of job these tools do reliably:
- Capture a signed, dated recurring-payment authorization at engagement.
- Store it with the client record so you can produce it the moment a charge is questioned.
- Send an automatic receipt after every successful charge.
- Flag expiring cards about 30 days out and email the client a secure update link.
- Alert a human the instant a charge fails, with the reason attached.
Set that up once, and the ordinary month stops touching your desk at all.
Where a human still has to step in
Autopay handles the predictable. It doesn't, and shouldn't, handle everything, and pretending otherwise is how you end up with annoyed clients and surprise chargebacks.
Keep a real person in the loop for the cases that need judgment:
- Disputed or irregular charges. If a client questions an amount, freeze the autopay and talk to them. A chargeback costs you the fee and the goodwill. A two-minute call usually costs neither.
- Failed and expired payments. Automation can flag these, but a person should follow up, warmly, before anything lapses. "Your card on file expired, here's a link to update it" lands fine. A silent service interruption does not.
- Clients who genuinely need manual billing. Some matters are lumpy: variable hours, pass-through costs, a client whose own cash flow runs in fits and starts. Don't force those onto autopay. Bill them the old way and spend your saved energy there.
- Large or milestone invoices. A retainer replenishment or a big one-time fee deserves a human heads-up before it hits, not a withdrawal that catches the client off guard.
The goal was never to automate the client relationship. It's to automate the part that was never a relationship in the first place: the identical charge that runs every month whether you send a reminder or not.
Worth doing this week
You don't need to overhaul billing to get moving. Pick the slice with the most predictable revenue and convert just that.
- List your recurring charges: monthly retainers, bookkeeping fees, active payment plans. That's your autopay candidate list.
- Check what your current payment processor already supports for recurring charges and e-signed authorizations. Most of it is probably sitting there unused.
- Write one onboarding sentence that asks for a card or bank account as the normal setup, and add it to your engagement process.
- Move three steady clients onto autopay as a test, and confirm the receipts and expiration alerts actually fire.
- Set one rule for failures: who gets notified, and how fast they reach out.
Do that, and next month-end you'll notice the reminder emails you didn't have to write. If you'd rather not wire it together yourself, that's the kind of quiet setup we put in for Massachusetts practices at AI Agency Mass, and it tends to pay for itself the first time a retainer funds on time without a single nudge from you.