The short answer
To get pool service customers on autopay, bill every account on a monthly invoice that builds itself from the visits you completed, email it with a one-tap card payment link, and set a clear pay-on-receipt or prepay policy in your service agreement. Where your processor supports a saved card, the monthly charge then runs on its own.
Chasing payments is the part of the month no pool pro signed up for. You balance the water, you make the stops, and then the first week of every month turns into a round of texts asking customers where the check is. Autopay fixes that at the source: instead of asking 55 people to remember to pay you, the bill goes out on its own and the money comes in on its own. None of that is pool work, and almost all of it is avoidable.
Autopay is less a single button than a setup: automatic monthly billing, a one-tap way to pay, and a written policy that makes paying the default. Here is what autopay actually means for a pool service business, how to set it up, what to put in your service agreement, and what to do about the customer who won't put a card on file.
At a glance
Key takeaways
- Autopay for pool service is automatic monthly billing plus a one-tap payment link - not just one feature, but a setup that bills and collects without you touching it.
- Turn on recurring billing so one invoice per customer generates itself from completed visits on your billing date, usually the 1st.
- Save a card on file where your processor supports it - that is the piece that makes the monthly charge run on its own and ends the chasing.
- Make autopay the default at signup; enrolling new customers as part of onboarding keeps most of your route hands-off from the start.
- Card processing runs about 2.5-3.5% per transaction - decide whether you absorb it or build it into your rate before switching on online payment.
- Write the payment terms into your service agreement: monthly billing, due on receipt, card on file as a condition of service.
- Move the customer who won't save a card to prepay so you never float a month of work for a slow payer.
Autopay for pool service means automatic billing plus effortless payment
Pool service autopay is two things working together: billing that happens automatically and payment that takes one tap. The automatic side is recurring billing - one monthly invoice per customer rather than a charge after every stop, which assumes you have already decided on billing monthly rather than per visit. It is generated from the visits you actually completed that period, instead of you rebuilding each bill from memory. The effortless side is pool service online payment - every invoice carries a payment link, so the customer pays by card in one tap with no app to download and no account to create.
True hands-off autopay adds a third piece: a saved card. With pool service card on file, the customer enters their card once and the monthly charge runs against it on your billing date, so neither of you touches it again. Card processing runs about 2.5-3.5% per transaction, and card payments typically settle to your account within 1-2 business days. Decide up front whether you absorb that fee or build it into your rate, because pool service automatic payment only saves you time if the economics already work.
How do I set up autopay for pool service customers?
Set up autopay in four moves: make automatic monthly billing the default, attach a payment link to every invoice, save a card on file where your processor supports it, and write the terms into your agreement. The foundation is automatic monthly billing and online payment, so the bill is built from the visits you logged rather than typed into a blank form each month.
- Turn on recurring billing for every maintenance account. The software compiles that month's completed visits into one invoice on your billing date - usually the 1st - so pool service recurring billing happens without you opening a spreadsheet.
- Put a payment link on every invoice. The emailed bill carries a one-tap card link, and a confirmation marks it paid automatically, so you are not logging payments by hand.
- Offer a saved card at signup. When a customer puts a card on file, the monthly charge runs on its own - this is the part that turns invoicing into true autopay and stops the chasing.
- Default new customers to autopay. Make a card or autopay enrollment a normal part of onboarding, not an afterthought, so most of your route is hands-off from day one.
- Track who has not enrolled. Anyone still paying manually is your short follow-up list - far shorter than chasing the whole route.
How do I make a pool service invoice send itself every month?
Make the invoice automatic by setting each recurring customer to monthly billing, and the system assembles that period's completed visits into one bill on your billing date instead of you building it by hand. The mechanics of the underlying bill - the line items, the tax, the total - work the same as any other invoice, so if you already know how to send the invoice from a customer's record, recurring billing just does it for you on a schedule.
One precise note so you set expectations right: automatic monthly invoice generation and automatic charging are two different things. Generating one monthly invoice per customer from logged visits is the automatic-billing half, and it works on its own. Charging a saved card on the billing date is the autopay half. A customer without a card on file still gets the automatic monthly invoice and taps the payment link to pay each month - which already removes most of the manual work, even before a card is saved.
How do I write autopay terms into a pool service agreement?
Put the payment terms in the written service agreement so autopay is expected, not a surprise. State that recurring maintenance is billed monthly, that payment is due on receipt, and that the account is kept on autopay or a card on file as a condition of regular service. Spelling it out at signup is what makes enrollment feel routine instead of like a favor you are asking for, and it is the single cheapest step in the whole setup.
A short clause does the job. Something like: "Maintenance is billed monthly and charged to the card on file on the 1st. Accounts not on autopay are billed pay-on-receipt; service may pause on any balance more than 15 days past due." That one paragraph sets the billing date, names the saved card, and ties continued service to payment, so the customer who lapses already agreed to the consequence. Roughly 80% of billing disputes trace back to a term that was never written down - the agreement is where you prevent them.
What about customers who won't put a card on file?
For the customer who refuses a saved card, move them to prepay: they pay for the month before service, not after. Pool service prepay flips the risk - you are never floating a month of work for someone who has already shown they pay slowly. Reserve it for the chronic cases rather than the whole route; most customers will happily go on autopay once it is framed as the normal way you bill, and only a handful ever need the prepay track. For the accounts that still fall behind, it helps to have a set plan for handling late-paying customers.
The goal of all of this is to stop chasing pool service payments and get customers to pay on time without nagging anyone. Take a two-tech shop in Chandler running 120 monthly accounts that used to spend the first week of every month texting reminders. Once every customer is on automatic monthly invoicing with a card link - and most on a saved card - all 120 invoices go out on the 1st on their own, and the owner only follows up on the handful still unpaid by the 10th instead of all 120. That is the difference between autopay and a calendar reminder to go collect: the system bills, the customer pays, and your month starts with revenue already in the account instead of a list of people to text.
FAQ
Frequently asked questions
Can I require all my pool service customers to pay by autopay?
Yes, and many operators do. Making a card on file a condition of regular maintenance service is legal and common, as long as you state it clearly in the service agreement the customer signs at signup. The cleanest approach is to default every new customer to autopay and reserve manual billing for exceptions, rather than trying to convert a whole established route at once. About 9 in 10 customers accept autopay without pushback when it is presented as simply how you bill, not as an unusual request. For the rare holdout, prepay is your fallback - they pay for the month up front instead of being carried on credit.
How do I move an existing customer onto autopay?
Send a short note explaining that you are moving billing to monthly autopay and asking them to save a card on the next invoice's payment link. Frame it as a convenience - no more checks, no more remembering a due date - because for the customer it genuinely is. Time the switch to the start of a billing month so there is no half-charged period to explain. Most customers convert the first time they would otherwise have written a check; expect a few to need a second reminder. The ones who go quiet are usually your slower payers, which is exactly the signal to put those specific accounts on prepay.
What happens when an autopay card is declined?
A declined card leaves that month's invoice showing unpaid, the same as if the customer never tapped the payment link - so you see it on your outstanding list rather than discovering it later. Cards decline for ordinary reasons: an expired card, a new number, or a hold on the account. The fix is a quick message asking the customer to update their card on the invoice, which resolves most declines within a day or two. Build the habit of scanning your unpaid list a few days after your billing date so a declined card becomes a one-line follow-up, not a month of unbilled service.
Where is my customer's card stored when they go on autopay?
The card is stored by the payment processor - Stripe, in PoolBoss's case - not in a file on your computer or in the app's own database. You never see or handle the full card number; the processor keeps it in a PCI-compliant vault and exposes only a token your software uses to run the monthly charge. That matters for two reasons: your liability is far lower because you are not holding card data, and customers are more willing to enroll when they know a bank-grade processor holds the card, not their pool guy's laptop.
Is autopay worth setting up for a small pool route?
Yes, and arguably it matters more on a small route. A solo operator running 40-60 pools feels every hour of admin directly, because there is no office staff to absorb it - the week you spend chasing payments is a week you are not selling stops or doing the work. Autopay turns monthly collections from a multi-day task into invoices that send and settle on their own. The setup is a one-time afternoon: turn on recurring billing, enroll your customers as they renew, and write the terms into your agreement. After that it runs in the background no matter how small the route.
Can commercial and HOA pool accounts go on autopay?
They can, though the terms are usually firmer. Commercial and HOA accounts often run on net-30 with a purchase order or property-manager approval rather than a pay-on-receipt card charge, so autopay for these accounts may mean a saved card charged on net-30 terms instead of immediately. Put the billing date, the terms, and the card-on-file requirement in the written agreement, since these accounts hold you to what was signed. A single commercial or HOA contract can be worth a dozen residential accounts, so it is worth setting the autopay terms up carefully rather than treating it like a residential signup.
