There is a specific, expensive gap in most service businesses: the job finishes, and the money does not move for two weeks. Nothing is in dispute. Nobody is unhappy. The delay is pure process — a paper ticket riding around in a truck, then a laptop at 9pm, then a batch on Friday, then a customer who now has to remember a job from a fortnight ago.
This gap is unusual because it is entirely self-inflicted, which also makes it the easiest large cash-flow win available to a small business.
Where the days actually go
- Job → paperwork (2–5 days). The ticket travels physically. Sometimes it does not arrive.
- Paperwork → invoice (1–4 days). Someone re-keys what the quote already said into a separate billing tool.
- Invoice → customer (0–3 days). Batched on a schedule that suits the office, not the cash position.
- Customer → payment (5–15 days). The gap you have the least control over, and it starts later than it needed to.
Steps one through three are all yours. Collapsing them does not require the customer to change any behaviour at all — it just starts their clock sooner, while the work is still fresh enough that paying it feels obvious.
The re-keying tax
Watch what happens to a single line item in a fragmented stack. It is typed into a quote. It is typed again onto a work order. It is typed a third time into the invoice, often in a different system. Each retype is a chance to introduce an error, and each error is a disputed invoice — which is not a two-minute fix, it is a phone call, a credit note, and a customer who now reads the next invoice suspiciously.
When the quote becomes the order and the order becomes the invoice, that class of error stops existing. Not reduced — gone, because there is only one place the number lives.
Invoicing on site
The strongest version is invoicing at completion, from the driveway, while the customer is standing in front of you looking at finished work. Three things are true in that moment and in no other:
- The value is maximally visible — they can see the thing you fixed.
- The details are uncontested, because you are both looking at the same job.
- They have a phone in their hand, which is a payment terminal.
Every hour after that, each of those weakens. By day fourteen the customer is being asked to pay for something they last thought about two weeks ago, from a document that arrived out of context.
Job costing falls out for free
A side effect worth naming: when quote, order, and invoice share a record, you can finally see the difference between what you quoted and what the job actually consumed. Which job types quietly lose money. Which customers absorb three hours of unbilled phone calls. Which product line is carrying the business.
Most owners have strong instincts here and no data. The data usually confirms two of their three instincts and overturns the third — and that third one is where the money is.
Deposits change the whole shape of the problem
Everything above shortens the gap between finishing and being paid. A deposit removes part of the gap entirely, and on jobs with material costs it is the difference between financing your customer and being financed by them.
The objection is always that customers will refuse. In practice they refuse when the deposit is unexplained and accept when it is attached to something concrete: the materials order, the slot on the schedule, the equipment being reserved. It is the same money and a completely different conversation.
| Job type | Common structure | What it protects |
|---|---|---|
| Small repair | Payment on completion | Nothing much — the exposure is a few hours |
| Supply and install | 30-50% deposit, balance on completion | Your working capital, tied up in their materials |
| Multi-week project | Deposit, one or two milestones, balance | Cash flow across the build and your exit if it stalls |
| Recurring plan | Card on file, charged on a schedule | Everything — this is the model that never ages |
Chasing, before it becomes chasing
Most overdue invoices are not disputes and are not hardship. They are an invoice that arrived in a busy week, got mentally filed as "deal with later", and then had no further prompt attached to it.
Which means the reminder schedule matters more than the wording. A polite nudge on the due date, another at seven days, and a phone call at fourteen recovers the overwhelming majority of late payments without anyone getting uncomfortable, provided the nudges actually fire.
- Day 0 — due date. Automatic, friendly, includes the payment link.
- Day 7. Same again, slightly shorter, still automatic.
- Day 14 — a human. A call, not an email. This is where you find out whether it is inertia or a problem.
- Day 30. Formal notice, and a decision about whether this customer gets work on terms again.
The step people skip is the last one. An account that reaches thirty days twice is telling you something about how it should be structured next time, and the answer is usually a deposit rather than a difficult conversation.
The failure modes worth naming
- The invoice waits for the office. Work finishes Tuesday, gets written up Friday, sent Monday. Four days gone for no reason other than where the tools live.
- Nobody knows what was actually done. The person invoicing was not there, so they invoice conservatively, and the extras quietly go unbilled.
- Payment is hard. Bank details in an email footer is a payment method from 2004. Every step between wanting to pay and having paid costs you days.
- Nothing tracks the gap. If days-to-invoice is not a number anyone looks at, it drifts, and it always drifts upward.
A sequence that works
- Invoice at completion, on site. Even before payment collection is smooth, starting the clock earlier is most of the win.
- Take payment on the phone in the driveway for residential work. Card fees are cheaper than fourteen days of float.
- Automate the reminder cadence on anything unpaid. Nobody should be deciding daily who to chase.
- Review quoted-versus-actual monthly by job type. Fifteen minutes, and it reprices your business.
Common questions
What does quote to cash mean?
The full path from quoting a job to money in the bank: quote, acceptance, work order, completion, invoice, payment. In service businesses those steps typically live in different tools, so the same information gets retyped two or three times — which is where both the delay and the disputes come from.
How do you reduce days to invoice?
Invoice at job completion rather than in a batch later. That alone commonly takes a two-week lag to same-day, and it requires no change in customer behaviour — it just starts their payment clock while the work is fresh.
Should you take payment on site?
For residential work, yes. Card processing fees are almost always cheaper than two weeks of float plus the chasing effort, and the customer is standing in front of finished work with a phone in their hand — the single best moment to ask.
Why do invoices get disputed?
Most often because a line item was retyped between systems and no longer matches what the customer approved. When the quote becomes the order and the order becomes the invoice on one record, that entire class of dispute disappears.