The pool still gets cleaned. That is the particular cruelty of this problem in route work: unlike a contractor who can down tools on Tuesday, you are driving past the house every week, opening the gate, putting chemicals in the water, and the balance is still growing. Three months of unpaid service on a $150 account is $450 of chemicals, fuel and labour you have already spent, on a customer who has told you nothing.
Most owners do not have a collections problem so much as a decision problem. The ladder below is not clever. It is just written down in advance, so that the account at sixty days gets the same treatment whether it belongs to a stranger or to the man who referred you four customers. Everything here about what Pool Runs does was read on poolruns.com on 30 October 2026. None of it is legal advice, and the one place you genuinely need to check your own state and your own contract is flagged where it comes up.
An aging report flattens everything into one number per customer, which is why owners end up treating a lapsed credit card the same way they treat someone avoiding them. They are not the same situation and they do not need the same phone call. Before anything escalates, work out which of the three you are looking at, because the first one is not really a collections problem and the second one is your own paperwork more often than you would like.
| What you are looking at | How to tell | What it needs first |
|---|---|---|
| Payment failure | Auto-pay was on and stopped working. Expired card, a replaced card after fraud, a closed account, or an insufficient-funds decline on the billing date. | A card-update request, not a collections call. The customer usually has no idea. |
| Disputed or confused invoice | Payment stopped the month something changed — a rate rise, a repair line, a filter clean billed as an extra, a skipped visit billed in full. | An itemised explanation and a decision from you on whether the charge stands. Chasing before you have read the invoice yourself is how you lose the account. |
| Will not pay | Contact goes unanswered across two channels. Promises are made and missed. Often arrives with a complaint attached, raised for the first time at sixty days. | The written ladder below, run to the end, with a date on which service stops. |
Payment failure
Disputed or confused invoice
Will not pay
The practical test: a payment failure is silent, a dispute is loud, and a refusal goes quiet after being loud once.
The order matters because the cost of guessing wrong is asymmetric. Treat a failed card as a refusal and you insult a good customer over something they did not know about. Treat a refusal as a failed card and you spend another eight weeks politely resending invoices while the balance doubles.
Read the aging report on a fixed day
Once a week, at the same time, open the aging report and look at the 31–60, 61–90 and 90+ columns before you look at anything else. Collections problems are not discovered, they are noticed late. A standing fifteen minutes on a Monday catches almost all of them in the bucket where they are still collectable.
Days are measured from the invoice due date, not from the date you sent it. Pick your own numbers if these do not suit your billing cycle — what matters is that they are decided once, apply to everybody, and are written where whoever runs your office can see them. A ladder you invent per customer is not a policy, it is a mood.
Day 1–3: check the mechanism before you check the customer
Was this an auto-pay customer? Look at the decline reason first. A soft decline — insufficient funds — usually clears on a retry. A hard decline means the card is dead and the customer has to replace it. Neither is a collections event, and sending a chasing message for one is a small, avoidable insult to a paying customer.
Day 7: one short, neutral message
Text or email, with the invoice attached and a payment link in it. No tone, no late fee yet, no reference to the relationship. Assume it was missed, because at seven days it usually was. This single message collects most of what is ever going to be collected, which is why it has to go out automatically rather than when you remember.
Day 15: a second message that states the terms
Same channel, but now it names the balance, the due date it has passed, any late fee your agreement provides for, and the date service would be suspended if it stays unpaid. The suspension date is the part that does the work. A balance with no consequence attached is a request; a balance with a date on it is a decision the customer now has to make.
Day 25–30: a phone call, from you, during business hours
Call rather than message, and ask an open question: is there a problem with the service or with the invoice? This is where disputes surface, and roughly half the accounts that reach day thirty turn out to have a complaint nobody passed on. If you reach a plan — a part payment, a date — confirm it in writing the same day. An unwritten promise does not survive the next month's invoice.
Day 30–45: written notice of suspension
Email, and post it too if the balance is large. It states the amount, the period it covers, the date service stops, and what has to happen to keep it running. Keep it factual and short. This document is the one that matters if the account ever goes to a collector, to small claims, or into a chargeback dispute, and tone is what gets quoted back at you.
Day 45–60: stop servicing the pool, and mean it
Take the stop off the route for real — not a technician quietly skipping it, which reads as a missed visit and earns you a complaint. Keep invoicing turned off from the suspension date, because billing for service you did not perform is the fastest way to turn a debt you might collect into one you certainly will not.
Day 60–90: decide, and close the file
Three outcomes, and you pick one rather than letting it drift: a payment plan in writing, a formal collections or small-claims route if the balance justifies the time and the fee, or a write-off. Writing it off is a legitimate choice for a small balance. Leaving it open for a year is not a choice, it is an unmade decision that costs you a quarter of an hour every month.
Two things not to do at any rung
Do not hold the equipment, the gate key or the pool cover as leverage, and do not discuss the balance with a neighbour, a tenant or a property manager who is not on the account. The first can expose you to a claim depending on where you operate; the second is the kind of thing that ends up in a review and a complaint at the same time.
This is the only rung that cannot be automated, and it is the one most owners skip, because nobody enjoys it. It is worth making anyway: a call at thirty days is a short conversation about one invoice, and the same call at ninety days is a long conversation about a relationship. Keep it to two minutes and open with the service, not the money — is the pool coming out the way you want, and is there a problem with the invoice? That order matters, because it gives a customer with a complaint somewhere to put it other than into silence.
What comes back is almost always one of three things. The first is a dispute you had not heard about — the rate went up without warning, a green-to-clean was billed as an extra when they thought it was covered, a technician missed two weeks in August and they have been waiting for you to notice. Half the time they are right, and the correct move is to credit the line on the spot and ask for the rest. A customer who sees a charge removed the same day they raise it usually pays the remaining balance that week, and stays.
The second is hardship, stated plainly or hinted at. A job lost, a divorce, a house going on the market. These accounts are worth a written plan — a part payment now, the rest across two or three months, service continuing while the plan is honoured — because the alternative is a write-off and they will remember which one you chose. Put the plan in an email the same day with the amounts and dates in it. The point of writing it down is not legal, it is that unwritten plans quietly become nothing by the second month.
The third is avoidance: the call is not answered, or it is answered with a promise that has no date in it. That is your answer, and it is the one case where you stop spending time on conversation and go to written notice. Do not call three more times. Each unanswered call is a small decision you are making to postpone the suspension, and postponing it is what turns a $300 problem into a $900 one.
Owners tend to think of a late fee as either punishment or revenue. It is neither, at pool-service balances. On a $150 monthly account a late fee is a few dollars; it will not change anybody's behaviour on its own and it will not make you money. What it does is mark the invoice as genuinely overdue, in writing, on a document the customer has received — which is exactly the evidence you want behind you at the suspension step.
Which means the fee has to be in the agreement the customer signed, stated as a rate or a flat amount with the grace period attached, and then charged consistently. A fee that appears for the first time on the overdue invoice of a customer you are annoyed with is worse than no fee at all: it reads as retaliation, it invites a dispute, and it hands the customer the argument. Charge it on every late invoice or on none.
This is the part to check locally
What you may charge as a late fee, how much notice you must give before stopping a contracted service, and what a signed agreement has to say to be enforceable all vary by state and sometimes by city — and for an HOA or a commercial property the contract usually sets its own rules on top. Before you set a rate or a suspension period, read your own agreement and get a local answer. Everything in this article is operational guidance, not legal advice.
Everything above assumes a homeowner who can decide to pay you on the day you call. A property manager cannot. On commercial, HOA and apartment accounts the person who approves the invoice, the person who signs the cheque and the person who lets you through the gate are three different people, payment runs on the board's or the management company's cycle rather than yours, and net-thirty or net-sixty terms are normal rather than a sign of trouble. An account that is twenty days past due on a residential ladder may be exactly on time on a commercial one.
So run a second, slower ladder for them, and start it further out. Before the first invoice, get the billing contact's name and email in writing, ask whether a purchase order number has to appear on the invoice — if it does and it is missing, the invoice will not be paid and nobody will tell you why — and find out the date their accounts payable run happens. Most late commercial payments are not disputes; they are invoices that arrived two days after the cut-off and are sitting in a queue until the next one.
Two other differences are worth knowing before you suspend a commercial pool. The contract usually sets its own notice period, which overrides whatever your standard terms say, and it is often thirty days. And a public or semi-public pool has health-department obligations attached to it that a backyard pool does not — walking away from a commercial pool mid-season is a bigger decision than skipping a residential stop, and it is one to take with the contract in front of you. On the upside, these accounts rarely vanish. They are slow, not absent, and the fix is usually a phone call to a person in an office rather than a ladder.
Almost every rung below day twenty-five should happen without you. If you are personally sending day-seven reminders, you will stop doing it in a busy month, which is the month you most need it done. The checklist below is what to look for in whatever system you run — and it is worth testing in a trial rather than taking from a feature grid, because the gap between "sends invoices" and "follows up on unpaid invoices by itself" is where most of this problem lives.
What to check your system actually does
0 / 6One honest gap worth naming, since this article is about getting paid: Pool Runs does not produce customer statements — a single document listing several months of invoices and payments. For a residential route that rarely matters, because the balance is one or two invoices. For commercial and HOA accounts that pay from a statement rather than an invoice, it does, and it is worth asking about in any trial. The fastest structural fix for almost all of this is still getting customers onto automatic payment in the first place, and the terms that make it stick belong in the service agreement.
At some point the arithmetic turns. An hour of your time spent chasing a balance is an hour not spent selling a route-dense account, and a small-claims filing costs a fee plus half a day. The number worth knowing is not the balance — it is what the balance costs you to pursue, against the odds of collecting it at that age. Balances in the 90+ bucket collect far less often than balances at thirty days, which is the whole argument for running the ladder on time rather than running it hard.
The same $600 balance, handled two ways
No written ladder
Ladder run on time
One more decision that comes up and rarely gets thought about in advance: what happens when a suspended customer calls in March wanting service again, still owing for September. Decide the terms once. The usual answer is that the old balance is settled or formally planned before the stop goes back on the route, and that the account comes back on automatic payment rather than on invoice, whatever it was on before. Taking a customer back on the same terms that failed is how the same account appears in your 90+ column twice in two years.
Collections is mostly a signup problem wearing a disguise. Every item below is decided when the customer joins, costs nothing then, and is close to impossible to impose later on an account that has already gone quiet.
Set these at signup, not at sixty days
0 / 6None of this makes non-payment disappear. A route of two hundred homes will always carry a few accounts that go bad, and the goal is not zero — it is that the bad ones are caught at thirty days instead of ninety, handled the same way every time, and closed out rather than carried. The accounts worth keeping usually tell you what is wrong on the day-thirty call, which is a different conversation from the one about money, and worth having for its own sake.
Pool Runs runs invoicing, auto-pay, the aging report and the route on one plan at $45 a month for 50 properties, with your whole team included and 30 days to try it on a real month of billing. Start a free trial and see what your own 61–90 column looks like.
See how Pool Runs can streamline your pool service business.
QuoteIQ and Skimmer get compared constantly, usually by pages QuoteIQ publishes itself. They are built for different jobs: one is a horizontal contractor platform priced per user with deep estimating, the other a pool-specific route system priced per serviced pool. What each publishes, where each genuinely wins, and the one comparison row that misleads pool companies.
A data-driven breakdown of what pool pros are charging in 2026, covering pricing models, state-by-state rates, and how to set profitable base rates.
Every pool service system sells quoting. The difference is what happens after the customer says yes. What Pool Runs, Skimmer, Pool Brain and QuoteIQ each publish about approval, e-signature, deposits and whether an approved quote reaches the schedule without anyone retyping it.
