The work is finished. Where's the money?

The most expensive day in field service isn't the day you do the work — it's every day after, while the invoice sits unsent. A tech wraps a job, drives off, and the billing detail lives in their head, on a crumpled work order, or in a text to the office. By the time someone reconstructs what happened, attaches the right parts, and emails an invoice, a week is gone. Multiply that across every job and you've built a business that does the work for free and lends the customer the money interest-free until you get around to asking for it.

The fix isn't "invoice faster" as a willpower problem. It's closing the job-to-invoice loop so the billing builds itself as the work happens, and the invoice goes out the moment the job is marked complete.

Why the gap exists

  • The billing data is scattered. Labor hours are in one place, parts used in another, the photos and notes somewhere else. Assembling an invoice means a treasure hunt.
  • Re-keying introduces delay and error. Someone in the office retypes what the tech already recorded — slowly, and with mistakes that trigger disputes.
  • Nobody owns the handoff. The tech assumes the office will bill it; the office is waiting on the tech for details. The job falls into the gap.

Capture the invoice while the job runs

The invoice should be a byproduct of doing the work, not a separate project that starts after. That means the line items accumulate in real time:

  1. Labor logs itself from job status. When the tech moves the job through enroute → on-site → complete, the time on site is already recorded. No timesheet reconstruction.
  2. Parts get added at the truck. A part installed is a line item entered on the spot, at the price it should bill — not remembered three days later.
  3. The scope is documented as it's done. Photo evidence and notes attached to the job make the invoice defensible before anyone asks "what did I pay for?"

In Hosting Field, jobs carry line items for labor, parts, and expenses with live totals, so by the time a tech marks the job complete the billable detail is already there. The 7-state job FSM means "complete" is a real, recorded transition — and that transition is the natural trigger to turn an accumulated job into an invoice. There's no re-keying step where the money leaks out.

Make "complete" the billing trigger

The single highest-leverage discipline is connecting job completion to invoicing so they're not two disconnected events. When a job hits its completed state with line items attached, the invoice is one action away — review, send, done. The customer gets it while the work is fresh in their mind, which is exactly when they're most willing to pay.

This is also where an accurate estimate pays off twice: if the customer already agreed to a line-item quote, the final invoice is the estimate plus any documented changes. No surprises, no haggling, no "let me check with my spouse."

Kill the disputes before they start

Slow invoices and disputed invoices are the same disease. Both come from a gap between what was done and what the customer can see. Close it:

What to measure

  • Job-to-invoice time — hours from job completion to invoice sent. Drive it toward same-day; it's one of the KPIs that actually move cash.
  • Days sales outstanding (DSO) — average days from invoice to payment. Fast, clean invoices shrink it.
  • Invoice dispute rate — share of invoices questioned or adjusted. Rising disputes mean your documentation isn't keeping up with your billing.

The work being done and the work being paid for are two different finish lines. The operations that win are the ones where crossing the first one automatically starts the second — same day, same job, no gap for the money to fall into.