Recurring Billing for Pool Service Companies: What Your Software Has to Do

Almost everything written about billing for pool companies is written about invoices: what goes on one, how to send it, how to chase it when it is not paid. That is useful for repair work and it is close to irrelevant for a service route. A book of a hundred and eighty weekly customers does not really have an invoicing problem. It has a charge problem.

Those hundred and eighty customers owe roughly the same amount every month, on a standing instruction nobody looks at. Meanwhile the route underneath those standing amounts changes every single week: a pool gets closed for the season, a gate is locked, a fifth Tuesday appears in the month, a customer adds a second visit through July. The work of recurring billing is keeping the standing amounts true to a route that will not hold still, and it is almost entirely a question of what your system does without being asked.

Recurring billing is not the same problem as invoicing

An invoice is an event. Somebody did some work, somebody wrote it down, somebody owes money for it, and if the money does not arrive the whole thing sits in a pile marked unpaid where you can see it. A recurring charge is a standing instruction, and standing instructions fail in the opposite direction. They go out on the right day, for the wrong amount, and the customer pays them.

That is why recurring-billing errors are almost always found by the customer. The owner is not auditing a charge that was paid. The customer who was billed for four visits in a month that got three is the one doing the audit, and they do it in an email that starts "quick question". Every pool company that has been running a few years has a short list of accounts where the billing is wrong in the customer's favour and nobody has ever mentioned it, and a shorter, more expensive list where it was wrong the other way and somebody did.

The practical consequence is that the thing worth buying, or building, is not a better invoice. It is a charge that knows what happened on the route.

The three ways a pool route charges

Underneath the vendor marketing there are only three billing structures in this trade, and the choice is less about revenue than about which arguments you are willing to have. It is worth knowing which one you are actually running, because plenty of operators think they charge one way and in practice charge another.

Most residential routes end up on flat monthly, and should. It is the structure customers understand and the one that produces the least collections work per dollar. But it is also the structure that hides the most, because the charge is deliberately disconnected from the visit count, and the next two sections are about what that disconnection costs when the route moves.

Proration is where it breaks

A flat monthly fee on weekly service is not a fee for four visits. There are 52 weeks in the year and twelve monthly charges, which averages to about 4.33 visits for each one. Roughly four months a year have five service days in them, and in those months the customer gets a fifth visit the monthly fee has already paid for. That is the deal, and it works, right up until somebody has to put a number on a single visit.

Use your own figure rather than this one, but run the sum once. Take a flat charge of $140 a month on weekly service. Over a year that is $1,680 for 52 visits, so a single visit is worth $32.31. Most owners asked to credit a skipped visit will divide $140 by four and credit $35, because that is the number in their head. The difference is $2.69, given away each time. On a book where thirty visits a year are lost to closures, weather and access, that is roughly $81 a year, which is nothing.

The same error pointed the other way is not nothing. An owner who believes the monthly fee covers four visits, and therefore charges separately for the fifth in a five-week month, is billing about $35 four times a year on every weekly account that notices. On a hundred accounts that is a real number and an indefensible one, because the arithmetic says the fee already covered it. This is the most common recurring-billing dispute in the trade and it is created entirely by dividing by four.

Everything in that sequence except the second step is mechanical, and the second step is a decision you make once. If the system cannot do the third step, you do not have a billing policy. You have a monthly round of refund emails, and you are the only person in the business who can answer any of them. The service agreement is where the policy belongs, because a rule the customer agreed to in writing takes thirty seconds to explain and a rule they are hearing for the first time takes a phone call.

Failed cards, and the gap nobody watches

Once a book is on automatic payment, the failures stop being conversations and start being silence. A card expires. A bank reissues a number after a fraud flag. A customer changes bank. None of those are collections problems and none of them mean the customer has decided not to pay you. They mean a charge did not land, and the question is how long it takes anyone to find out.

Dunning

The sequence a system runs after a recurring payment fails: when it retries the card, when it emails the customer, when it tells you, and what it does if nothing changes. On a recurring book the dunning sequence, rather than the decline itself, decides how much service you give away before the problem reaches anybody.

That last point is the one worth sitting with. The cost of a declined payment is not the unpaid month, which you will usually recover. It is the service you keep delivering in the meantime. On weekly service, a decline that surfaces three weeks later is three visits of chemicals, fuel and labour already spent on an account that is not currently paying, and you spent them because an email went to a folder nobody opens.

1. 1

   Retry on a schedule, not instantly

   A decline for insufficient funds often clears within a few days, so a retry spaced out over the following week recovers a share of them with nobody involved. An immediate retry recovers almost none of those and can read to the customer as a duplicate charge attempt.

2. 2

   Tell the customer before you tell yourself

   Most declines are an expired or reissued card and the customer can fix it in under a minute. What decides whether they do is whether the message contains a link that updates the card, or an instruction to call the office during business hours while you are at a pool.

3. 3

   Put it on a list you actually look at

   A failed payment that exists only as an email is a failed payment you will miss in July, which is exactly when you will miss it. It needs to be a short queue with an age against each item, and the queue needs to be somewhere you pass every week.

4. 4

   Decide the service-stop threshold in advance

   Pick the number of missed cycles at which the route stops, write it into the agreement, and apply it identically to everyone. Deciding case by case in the moment is how a book quietly splits into customers who pay and customers who worked out that they do not have to.

5. 5

   Record what happened on the account

   An account whose payment has failed in three consecutive seasons is telling you something about that customer, and it is not only an admin fact. It belongs next to the service history, where it can inform a pricing or a retention decision later.

Pushing a price increase across a recurring book

Quoting a new customer a higher rate is a sales question. Moving an existing recurring book onto a new rate is a mechanical one, and it is the single task that most exposes how your billing is put together. The new amount has to start applying on a date, to a defined group of accounts, without anybody opening a hundred and eighty records on the right morning.

The pricing side of that exercise, as opposed to the mechanics, is a separate piece of work: which accounts to raise, by how much, and what to say. Raising rates without losing customers covers choosing the number and writing the notice. What matters here is only that the system can execute whatever you decide, on a date, in groups.

Partial months and the first bill

A customer who starts on the nineteenth is the smallest of these problems and the one most likely to be handled three different ways in the same business. There are two defensible answers. Pro-rate the first month from the first visit, which is fair and slightly fiddly. Or bill the interim visits individually and start the recurring charge on the first full cycle, which is tidier in the books and takes one extra sentence to explain on the phone.

Either is fine. Both being in use at once is not, because the first bill is the one a new customer reads most carefully, and it is where they decide whether you are organised. Pick one, write it down, and make it the default the system applies when nobody is paying attention. The same logic runs in reverse at the other end: a cancellation mid-cycle needs one rule too, and it needs to be the rule in the agreement rather than whichever feels generous on the day.

Can you run this on a spreadsheet?

For a while, genuinely yes, and anyone who tells you otherwise is selling something. A spreadsheet of accounts and the recurring-invoice feature in standard accounting software will bill a stable book correctly and cost you nothing extra. It is worth being precise about where that arrangement stops, rather than vague about it.

Read the right-hand column as a list of thresholds rather than a verdict. The arrangement stops working at the point where somebody other than you runs part of the route, because that is when the charge and the visit are recorded by different people, and the gap between them becomes invisible to both.

The short version

A recurring book is a set of standing instructions that has to stay true to a route which changes every week. Nearly every billing argument a pool company has is the gap between those two things, and none of the fixes are about collecting harder. Divide by 52 rather than by four. Decide the skip rule once and write it into the agreement. Know what your dunning sequence does, because that is what the silence after a decline costs. Make the rate change happen on a date, in cohorts.

One ordering point is worth more than the rest. Moving a book onto automatic payment is the step most owners reach for first, and it is the right step. But automatic payment of a wrong amount is worse than a manual invoice for a right one, because it gets paid and then gets discovered. Get the charge correct first, then automate the collection. What belongs on the invoice itself and why accounts actually cancel cover the two ends this piece sits between. If you want the visit record and the billing in one place, so that the charge and the route cannot quietly disagree, you can see how Pool Runs handles invoicing and AutoPay or start a trial.