Days to cash is the number of days between finishing work and having the money in the bank. Most owners feel it as a mood: some months the account is comfortable, some months it is tight, and the workload looks the same either way. The mood becomes manageable the moment it becomes arithmetic, because days to cash is the sum of two stages that can each be measured and shortened separately: the days from job done to invoice sent, and the days from invoice sent to paid.
What a day is worth
Start with what one day of delay costs, because it justifies everything else in this guide.
The figures below are a worked example for illustration only. They are not a customer result, and your own numbers will differ.
A shop billing $4.8 million a year bills about $13,150 per calendar day ($4,800,000 divided by 365). If cash arrives on average 55 days after work is completed, then at any given moment roughly $723,000 of earned money is sitting outside the business (55 days times $13,150). Shorten the average by ten days and about $131,500 moves into the bank account. That release happens once, but it is permanent: the business runs from then on with $131,500 more cash, without a single new job, price increase, or cost cut.
That is the whole case. Every day removed from the cycle is roughly one day of revenue converted from a number on a report into money you can spend on payroll, material deposits, or the next hire.
Stage one: job done to invoice sent
The first stage is entirely inside your own walls, which makes it the place to start. The customer cannot pay an invoice that does not exist, and their payment clock does not start until it arrives. Every day in this stage is pure, self-inflicted delay.
Days hide here in predictable places:
- Waiting for cost information. The invoice cannot be assembled because hours or material receipts have not been turned in.
- Batch invoicing. The office invoices weekly or at month end, so a job finished the day after the batch waits most of a cycle for no reason.
- Assembly falling to one busy person, with completed jobs queuing behind whatever else that person does.
- Approval sitting in an inbox. The draft is ready, the reviewer is busy, and nobody can see how long it has been waiting.
Measure the stage before fixing it. Pull your last twenty completed jobs and write down two dates for each: when the work was done and when the invoice went out. Average the gap. Shops that have never measured it commonly find seven to twenty days; two to three is an achievable target for most service and project work.
The fixes follow the list. Tie invoicing to job completion instead of the calendar, so a finished job is a trigger, not an entry in a future batch. Capture cost during the job, so nothing waits at the end for a shoebox of receipts. Put a visible clock on approval, so a draft that has been waiting four days looks different from one that arrived this morning, and someone owns the oldest item.
Stage two: invoice sent to paid
The second stage belongs mostly to the customer, but you have more influence over it than it appears.
Measure it from real payment dates: for each customer, the days from invoice date to the date the payment actually arrived, averaged over their paid invoices. This number varies by customer far more than by month, and knowing it per customer is the point.
Days hide here too:
- Paper. Printing and mailing an invoice, and waiting for a check to travel back, adds real calendar days at both ends compared to an emailed invoice.
- Rejected or parked invoices. An invoice missing the purchase order number, the right billing contact, or a required attachment does not get disputed; it gets set aside, and you find out at day 40.
- Silence until day 30. If the first contact a customer hears is a past due notice, the invoice spent its whole term unprioritized.
- Terms creep. A customer on net 30 who quietly pays at 45, with no consequence and no conversation, has moved themselves to net 45.
The fixes: send invoices by email the day they are approved, with a way to pay attached. Get the invoice requirements right the first time by keeping each customer's purchase order and billing contact rules on file. Make one contact before the due date, framed as confirming that everything needed for payment is in hand; it is polite, and it surfaces the parked invoice at day 10 instead of day 40. Follow up within the first week past due, every time, so your invoices earn a reputation for being watched. And use the per-customer payment record in pricing and terms conversations, because a customer who reliably pays at 60 days is more expensive to serve than one who pays at 25.
The two stages together
Continuing the worked example from above, still an illustration and not a customer result: suppose stage one measures twelve days and disciplined invoicing brings it to three, saving nine days. Suppose follow-up and email delivery bring the average payment stage from 43 days to 36, saving seven more. Sixteen days at $13,150 per day is roughly $210,000 released into the bank account, from process alone.
Start by measuring both stages this week; the numbers are already in your records. Then fix stage one first, because it needs nobody's cooperation but your own.