The Payment Method You Made Optional: Card-on-File
If clients have to decide how to pay every invoice, some of them will decide later. Storing a payment method turns getting paid into a default, not a task.
Most invoicing advice focuses on the send: automate the invoice, attach a pay link, set reminders. That's all worth doing. But there's a quieter reason invoices sit unpaid, and it has nothing to do with when you send them. It's that every single invoice asks the client to make the same decision again — how do I want to pay this? — and that decision is where the delay lives.
The fix is boring and effective: stop asking. Capture a payment method once, at the start of the relationship, and default to charging it. Card-on-file (or a saved direct debit) turns payment from an action the client takes into a thing that simply happens.
Why the pay link isn't enough
A pay link is a big improvement on 'here are our bank details, please include your invoice number as the reference.' But it still puts a task in front of the client every time. They have to open the email, click through, find a card, type in the numbers, and confirm. For a busy business owner, that's three minutes of admin that competes with everything else on their desk — and admin that competes usually loses.
The result is the pattern every practice knows: the invoice isn't disputed, the client isn't unhappy, the money just... hasn't arrived yet. Your debtor days creep up not because clients won't pay, but because paying keeps not being the most urgent thing they're doing.
Card-on-file removes the competition entirely. When the work is done and the invoice is raised, the payment method is already there. You're not waiting on a click.
Where card-on-file actually fits
Not every fee suits an automatic charge, and pretending otherwise is how you end up with awkward reversals. Think about where it earns its place:
- Recurring compliance work. Monthly bookkeeping, quarterly BAS, annual returns billed in instalments — predictable amounts on a predictable schedule are the ideal case. The client agreed to the package; the charge just follows the work.
- Fixed-fee engagements paid in stages. If you've priced the year as a package and split it into monthly payments, a saved method keeps those instalments landing without a chase each time.
- Deposits and upfront portions. Capturing a method at onboarding lets you take a deposit before work starts and bill the balance on completion — no second request.
For large one-off invoices or anything the client might reasonably want to review before paying, a pay link with a clear approval step is still the right call. Card-on-file is for the routine, agreed work — which for most practices is the bulk of the revenue.
Get the consent right
Storing a payment method and charging it automatically is a commitment you're asking the client to make, so it needs to be explicit — not buried. The cleanest place to establish it is the engagement letter. Spell out:
- What you'll charge (the fee or the instalment amount)
- When you'll charge it (on completion, monthly on a set date, per BAS lodgment)
- How they'll know before it happens (an invoice issued a set number of days ahead)
- How they change or remove the method
Handled this way, card-on-file isn't a surprise — it's a term the client agreed to when they signed on. It also protects you: the scope, the fee and the payment mechanism all sit in one signed document. If a charge is ever queried, you're pointing back to something explicit, not an assumption.
Notice, then charge
The one thing that turns automatic payment from a convenience into a complaint is charging a card with no warning. Don't. The sequence that keeps clients comfortable is simple: issue the invoice, give a few days' notice, then charge the saved method — and always send a receipt.
That short window does two jobs. It gives the client a chance to flag anything genuinely wrong before money moves, and it means the charge, when it lands, is expected. You get the speed of automatic payment without the friction of surprise.
Wiring it into your practice
Card-on-file only pays off if it's connected to the rest of how you run work — otherwise you've just added another system to reconcile. This is where practice management software matters more than the payment processor itself.
In Finye, invoicing runs off the same client records and work items as everything else. A payment method captured at onboarding sits against the client, engagement terms sit against the engagement, and the invoice fires when the job is marked complete or on the recurring schedule you've set. Payments go through Stripe or Square, and because Finye syncs two-way with Xero, the paid invoice and its reconciliation flow through without you re-keying anything. The point of good accounting client management software isn't a nicer invoice — it's that getting paid stops being a separate process bolted onto the work and becomes part of it.
That connection also fixes the reporting problem. When payments are automatic and tied to work items, your debtor position reflects reality rather than a pile of invoices you're mentally discounting because 'those ones always come in eventually.' You can actually see which clients are on saved methods and which aren't — and the aged-receivables list gets short enough to be worth reading.
Start with the clients you least worry about
Rolling this out to your whole client base at once creates noise. Start narrow. Take your recurring, fixed-fee clients on solid terms — the ones who already pay reliably, just slowly — and move them to card-on-file at their next engagement renewal. You're not changing whether they pay; you're removing the lag. That's the group where the change is easiest to sell and where the debtor-days improvement shows up fastest.
From there, make it your default for new clients. Fold the payment method into onboarding alongside the engagement letter, the ID checks and the document requests. If capturing how they'll pay is just one more step in a runway they're already walking through, it never feels like a special ask.
The shift underneath
Getting paid faster isn't really a chasing problem or a reminder-timing problem. Those are patches on the same underlying issue: you've left the decision to pay in the client's hands, every invoice, forever. Card-on-file moves that decision to the start of the relationship, where it belongs, and makes 'paid on time' the thing that happens automatically instead of the thing you keep having to arrange.