Days to Invoice: The Margin Leak Hiding in Plain Sight for Field Service Contractors

You finished the job. The crew is already on the next one. The customer is happy. And somewhere between that last signature and the invoice landing in their inbox, money quietly disappears.

Not through fraud. Not through poor pricing. Through delay. The gap between work completed and invoice sent is one of the most reliable margin leaks in a trade or field service business, and most operators have no clean way to see it.

What Is Days to Invoice, and Why Does It Matter?

Days to invoice is simple: how many calendar days pass between the moment work is complete (or a milestone is hit) and the moment a proper invoice reaches the customer?

For a business running both reactive service calls and multi phase projects, that number is rarely one number. It varies by job type, by technician, by project manager, by how well the dispatch to accounting handoff actually works. That variance is the problem.

Here is why it costs you margin, not just cash flow:

Labour costs accrue the day the work happens. If a technician completes a service call on Tuesday and the invoice goes out the following Monday, you have already paid wages, fuel, and burden on work that has not been billed. The longer that gap, the more your realized margin shrinks relative to the margin you estimated in the quote.

Change orders are the worst offender. On project work, a change order approved in the field rarely makes it to the invoice automatically. It gets jotted down, sometimes photographed, occasionally emailed, and then it sits until someone with accounting access has time to process it. By then, the customer may dispute it because the work feels like ancient history. Unbilled change orders are not a billing problem, they are a process problem that shows up as margin erosion at month end.

Delayed invoicing distorts your margin view. If you look at job cost in the middle of a billing cycle, you see costs but not matching revenue. Decisions made on incomplete margin data, staffing, equipment purchases, bidding strategy, are made on fiction.

Where the Gap Actually Comes From

Understanding why invoices are late is more useful than just trying to invoice faster. The root causes tend to cluster around three handoffs.

1. Field to Office Information Transfer

The technician completes the work. The information needed to bill, actual hours, materials used, any extras agreed on site, lives in their head, on a paper form, or in a photo on their phone. Getting that information into a format the office can invoice from takes time and re keying. Every re key is a delay and a potential error.

2. Project Milestone Ambiguity

On longer projects, "work complete" is not always obvious. If your project milestones are not defined clearly enough to trigger a billing event automatically, someone has to make a judgment call, track down the project manager, and decide when to invoice. That judgment call often happens late.

3. The Approval Queue

Even when the field data makes it to the office cleanly, invoices often wait in a queue for review, approval, or batch processing. Batching is efficient for the accounting team but it means a job completed Monday might not invoice until Friday's batch run.

None of these are character flaws. They are process gaps, places where operational truth lives in one spot but billing happens somewhere else.

A Practical Framework: Map, Measure, and Shrink the Gap

You do not need new software to start diagnosing this. You need to measure it first.

Step 1: Define your billing trigger for each job type.

For reactive service work: the billing trigger is typically when the technician marks the work order complete and the customer signs off. Write that down explicitly.

For project work: the billing trigger is milestone completion, as defined in the contract. If your milestones are vague ("Phase 2 complete"), tighten them to observable events ("rooftop unit commissioning signed off by site supervisor").

Step 2: Pull your last 60 days of completed jobs.

For each closed job or completed milestone, find two dates: the completion date and the invoice sent date. Calculate the gap. Do this by job type and by who managed the job. You are looking for patterns, not outliers.

Step 3: Identify where the longest gaps cluster.

Is it service calls handled by one dispatcher? Change orders on projects over a certain size? Jobs where the technician submits paper timesheets? The pattern tells you which handoff to fix first.

Step 4: Set a target cadence, and make it visible.

Rather than prescribing industry benchmarks (which vary widely by trade, contract type, and customer), the goal is simply to establish your baseline and track movement against it. The number that matters is yours, trending in the right direction.

Step 5: Treat unbilled change orders as a separate metric.

Unbilled change orders deserve their own tracking. At any point, your ops lead should be able to answer: how many approved change orders have not yet been invoiced, and what is the total dollar value? If that answer requires digging through emails and spreadsheets, the leak is actively running.

What Operational Continuity Actually Fixes

The root cause of a high days to invoice number is almost always the same thing: operational truth (what happened in the field) and billing capability (what can be invoiced) live in different systems, owned by different people, with a human handoff between them.

The technician finishes the job. Someone has to relay that to dispatch. Dispatch has to close the work order. Someone has to move the data to an invoice. If those are four separate tools with four separate logins, the delay is baked in.

When field execution, work orders, and invoicing share a single operational layer, the gap closes because there is no handoff to drop. The completion event in the field is the same system event that queues the invoice. Change orders added on site flow to project billing without re keying. Timesheets feed actual labour costs into job margin in real time.

This is specifically what PolarPath was built around, one continuous workflow from customer intake through quote, dispatch, field execution, and invoicing, sitting alongside QuickBooks (which stays as the accounting system of record) rather than trying to replace it. The operational execution layer is where the days to invoice gap either gets created or prevented. PolarPath owns that layer so that what happens in the field and what gets billed are never two separate conversations.

The Takeaway

Days to invoice is not a finance metric. It is an operations metric. The gap is created in the field, in the project handoff, in the approval queue, not in accounting. That means fixing it requires looking at your operational workflow, not just your billing process.

Start by measuring it. Segment it by job type. Find where the longest gaps cluster. Tighten the definition of your billing triggers so completion and invoicing are causally connected, not just vaguely related.

If you find that your biggest gaps come from handoffs between systems and people, that is worth a harder look at whether your operational stack is actually connected, or just adjacent.