How to collect recurring maintenance payments automatically
Use Trade Books recurring invoices with autopay and card on file to charge customers automatically, reduce manual collections, and handle failed charges.
If you run maintenance agreements, use recurring invoices with autopay and a customer card on file to stop chasing monthly payments. A recurring invoice generates each scheduled occurrence, and with autopay on the customer’s card on file is charged when the occurrence is created so you get a receipt on success instead of a please-pay email. Failed charges enter a dunning flow.
Key takeaways
- Set each maintenance plan as a recurring invoice template so charges generate on schedule without manual invoicing.
- Turn on autopay to charge the customer’s card on file when the occurrence is generated and send a receipt on success.
- If a charge fails, Trade Books opens a dunning cycle: the office gets a push, the customer gets a payment-failed email, and retries follow your shop’s schedule.
- Pausing a series and resuming it later will not catch up missed occurrences, so schedule pauses intentionally.
- Saved cards are stored with the payment processor, not in Trade Books, and the same card on file is used by the customer portal and the office.
How do I set up recurring maintenance payments that actually get paid?
Make a recurring invoice template for each plan, add the customer’s card on file, and enable autopay so the charge runs when each occurrence is generated. Confirm the first scheduled charge succeeds and that the customer sees the receipt.
Do not treat a recurring invoice as a one-off invoice copy; it’s a template that produces each occurrence automatically on the schedule you set. With autopay on, the system charges the card on file at generation time so you won’t send a please-pay email for that occurrence when the charge succeeds. That means the office does not have to create, send, and follow up on the same invoice month after month.
How do I convert existing maintenance customers to autopay?
Follow an ordered checklist so nothing is missed and customers understand what will be charged and when.
- Tell the customer what you’ll charge and on what schedule; get their verbal or written agreement to autopay.
- Collect a card on file and confirm the customer portal can access the same card; saved cards are stored with the payment processor, not in Trade Books.
- Create a recurring invoice template that matches the plan’s schedule and price; confirm taxes and line items match the contract.
- Enable autopay for that recurring invoice so the card on file is charged when each occurrence is generated.
- Trigger or wait for the first occurrence; verify the first charge posts and that the customer receives a receipt instead of a please-pay email.
- Monitor for any payment-failed notifications and act on them: call the customer, or resend instructions to update their card via the payment-failed email link.
What happens if a customer's card is declined?
A failed charge starts a dunning cycle: the office receives a push notification and the customer receives a payment-failed email with links to pay online or update the card. Retries occur on your shop’s schedule until the retries run out or the charge succeeds.
This prevents the typical manual chase because the system alerts you and gives the customer direct ways to fix the problem. Your office still needs a small follow-up routine: reach out quickly when you get the push so the customer updates their card or you re-book the payment before the retries stop.
How do I pause a recurring invoice without billing for missed months?
Pause the recurring invoice series when a customer asks you to stop billing; when you resume later, Trade Books will not generate occurrences for the time it was paused, so you will not be charged for missed cycles.
Use pause intentionally: if the customer expects catch-up billing you must create a new invoice or change the template before resuming. Because pausing and resuming never catch-up missed occurrences, the office no longer needs to manually void or reconcile back charges created while the customer was inactive.
How does Trade Books handle recurring invoices and card on file so my office does less work?
Trade Books treats a recurring invoice as a template that generates a series of occurrences on the schedule you set. When autopay is enabled, the customer’s card on file is charged automatically at occurrence generation and a successful charge sends a receipt instead of a please-pay email.
Saved cards are stored with the payment processor, not in Trade Books, and the same card on file is used by both the customer portal and your office. If a charge fails, Trade Books opens a dunning cycle: the office gets a push notification, the customer gets a payment-failed email with links to pay or update the card, and retries run on the shop’s schedule until the series pays or retries end. That removes the repetitive manual invoicing and most of the initial collection work while keeping the office in the loop for unresolved failures.
What bookkeeping and operational mistakes does this prevent?
Using recurring invoices with autopay prevents three common errors: forgetting to issue the invoice, sending duplicate invoices for the same cycle, and letting small unpaid balances grow into bad debt because no one chased them. It also prevents accidental billing when a customer paused service because pausing stops generation rather than queuing unpaid occurrences.
Frequently asked questions
Do customers get notified when autopay charges their card?
Yes. When autopay successfully charges the card on file at occurrence generation, Trade Books sends a receipt instead of a please-pay email. If a charge fails, the customer receives a payment-failed email with links to pay online or update their card.
Where are saved cards kept, and can I see card numbers in Trade Books?
Saved cards are stored with the payment processor and not stored in Trade Books itself, so your office does not see full card numbers. The same card on file is available to the customer portal and to the office for charging via the recurring invoice autopay flow.
Will pausing a recurring invoice bill the customer for the missed cycles later?
No. Pausing a series stops generation; resuming it later will not produce the missed occurrences or retroactive bills. If you need catch-up charges, create a separate invoice or adjust the template before resuming.
What does the dunning cycle do for me after a failed charge?
Dunning triggers a push notification to the office and sends the customer a payment-failed email with links to pay or update their card. Retries then follow your shop’s schedule until the retries run out or the payment succeeds, reducing the need for manual follow-up on every failed charge.
Can I turn autopay off for a customer later?
Yes. You can disable autopay for a recurring invoice so future occurrences are generated but not charged automatically, and the system will send a please-pay email when they generate. That gives you control if a customer refuses autopay or wants to be invoiced instead.
How do I try this in my business before rolling it out to all customers?
Start with a few volunteer customers or your internal test account: create a recurring invoice, add a card on file, enable autopay, and verify the first occurrence and receipt. Trade Books offers a thirty-day free trial with no credit card required so you can test real charges before committing.
The one thing to do this week
Create one recurring invoice template for your most common maintenance plan, collect a customer card on file, enable autopay, and verify the first scheduled occurrence charges and sends a receipt. If you want to test the setup without switching systems, sign up for the Trade Books free trial at /signup and run the template against a volunteer customer or test account.