The Invoice That Sits for Three Days

The job gets done on Tuesday. The invoice goes out Friday. Nobody decided that should happen — it just does, every time, at almost every shop.

It's not that anyone's slow. It's that "done" and "billed" aren't the same moment, and everything that happens in between is where the delay lives.

Where the three days go

The tech finishes the job, maybe snaps a photo, and heads to the next stop. The details — what parts got used, how long it took, anything the customer asked for on the spot — stay in their head, or on a paper ticket in the truck.

That ticket makes it back to the office at the end of the day, or the end of the week if it's a busy one. Someone has to translate it into an actual invoice — figure out pricing, make sure nothing's missing, remember whether this was the job with the extra thermostat. Then it gets sent, and now everyone's waiting on the customer instead of the customer waiting on you.

Every one of those handoffs is small. Stacked together, they're the difference between getting paid this week and chasing an invoice next month.

Why this one's easy to miss

Scheduling problems get noticed immediately — a double-booked tech shows up as an angry phone call the same day. A slow invoice doesn't announce itself. It just quietly stretches out how long cash takes to come back in, job after job, until the owner notices the bank balance doesn't match how busy the crew's been.

It also compounds. A three-day lag on one job is a minor annoyance. The same lag across forty jobs a month is a real chunk of revenue sitting uncollected at any given time, for no reason other than the paperwork hadn't caught up yet.

What actually closes the gap

The fix isn't invoicing faster once the ticket lands on a desk — it's not having a separate ticket at all. If the job was already scheduled in one system, closing it out should happen in that same place, by the person who was already there: notes, photos, and parts get logged on-site, and the invoice is built from exactly that, not reconstructed from memory later.

That's the piece we built into TradeVan — a job closes out from the same screen it was dispatched from, so the invoice is ready the moment the truck leaves, not whenever someone gets back to a desk.

If three days doesn't sound like much

At low job volume, it isn't. The cost only shows up at scale — more jobs, more techs, more tickets stacking up somewhere between the truck and the office. Worth watching for, even if it's not painful yet: the same gap that costs nothing at 5 jobs a week costs real money at 50.

---

Part of our "Problems and Solutions" series — see also why the whiteboard breaks at 5 techs. If there's an operational problem you'd like us to cover, let us know.