Job-to-Cash: Why Finished Work Can Take 30+ Days to Become Money

Here's a question that can expose trapped cash before you consider a new tax strategy: the job finished two weeks ago, where's the money? Often the honest answer is "somewhere between the field and the bank." The tech closed the job, but it sat in a "ready to invoice" queue for a week. Then the invoice went out, and it's been aging ever since with nobody chasing it. The work is done and profitable. The cash is stuck in the seam.

This is the part people miscategorize. They think slow cash is an accounting problem, so they lean on the bookkeeper or the CPA. But the bookkeeper records what already happened. The lag was created upstream, in the operational handoff from completion to invoice to collection. Closing the job-to-cash gap is an operations discipline, and it's the kind of routine handoff an operating layer for the trades can help run.

The gap has two halves

Half one: completion to invoice

Across Level's contractor benchmark research, raw median billing speed is 1 day, per Level Index published metric (see its eligible sample and definition), but that's flattered by the ~25% of contractors who progress-bill before a job closes. Among post-completion invoicers, the adjusted median is 7 days. The published full-cohort slowest-decile threshold is 30 days, not a separately derived post-completion decile. Billing speed here means days from job completion to invoice issued, across 733 companies in Level's cross-trade research. It is not a separately measured HVAC, plumbing or electrical subset, and it covers only the first half of the gap.

That lag is float. Fictional illustration: assume a $10M contractor invoices all of its work after completion, evenly across a 365-day year. That is about $27,400 of work completed per day ($10,000,000 / 365). A steady 7-day completion-to-invoice lag keeps roughly $190K of finished work unbilled at any moment ($27,400 x 7 = about $191,800) versus same-day billing. Closing the lag releases that balance once. It is a timing gain, not $190K of new profit every year, and it is smaller if part of your revenue is already progress-billed. When the cause is operational, it usually looks like this: nobody flagged the completed job as ready to bill, so it waited for someone to "pull completed jobs on Friday."

Half two: invoice to cash

Then the invoice goes out, and the second clock starts. Median collection rate across the dataset is 85.1%, per Level Index published metric (see its eligible sample and definition). In that research, collection rate means cash collected as a share of billed revenue, across 464 contractors in all trades. A shortfall mixes timing, disputes, credits, write-offs and data gaps, so the gap to 100% is not all recoverable cash. This page has no sourced collection-by-age curve, so test the timing question on your own invoices. Compare all invoices issued in a matched period before a follow-up cadence change with all invoices issued after it, including invoices never followed up. Measure collection within 120 days of issue, then check customer mix, invoice size and seasonality. An invoice still unpaid at day 30 belongs to a slower-paying population by construction; splitting invoices by their first follow-up day cannot isolate the effect of earlier follow-up. (More in why contractors bill millions and collect thousands less.)

Put the halves together and a "profitable" contractor can be chronically cash-tight: earned margin trapped first in unbilled work, then in aging AR.

The AI reflexes that close it

This is a textbook case for running the money on reflexes instead of reports (the finance-function version is in your CFO's real job is building the AI operating system for your money). Applied specifically to job-to-cash:

• Bill the moment work is done. A job ticket flips to "complete" → the system drafts the invoice within hours → a named person reviews and approves it before it is sent. A missing PO, billing contact or approved change order raises an extra exception flag. That flag is in addition to approval, not a substitute for it. The "ready to invoice" queue stops being a place jobs go to age.
• Escalate AR before the customer goes cold. Automatic, tiered follow-up: a polite nudge at day 7, a firmer one at day 14, owner CC'd at day 30. Humans handle only the disputes and the relationships that need a personal call. Everything else runs on a schedule a person sets and can pause. Contract payment terms, lien or notice deadlines and any statutory claim dates override this cadence. Calendar them from the contract first, because a day-30 reminder does not preserve a legal right.
• Catch the change orders that never got billed. Approved scope changes that never made it onto an invoice are silent margin leaks; the reflex reconciles work performed against work billed and flags the gaps.

None of this replaces judgment. The hard collection calls and the key-account conversations stay human. It replaces the forgetting. When the handoff is the cause, the issue isn't strategy; it's that the routine steps depend on someone remembering to do them on a busy week.

What closing the gap is worth

The two effects work differently. In the fictional $10M example above, cutting a 7-day billing lag to same-day releases about $190K once. After that, cash arrives sooner, but annual revenue and margin are unchanged. Earlier follow-up can also raise the share of billed revenue you collect. Only the part of the shortfall that was genuinely collectible can be recovered, not the part that was disputed, credited or already resolved. Measure that part on your own invoices before counting it. Together, the timing release and any recovered shortfall can reduce how much you draw on the line of credit in a tight month, and unlike a line of credit, this is your own money, not borrowed money.

It also shows up in DSO, the headline number lenders and buyers look at. Faster collection lowers DSO. Faster billing shrinks unbilled work but can temporarily raise accounts receivable; those are different parts of job-to-cash. A lower DSO is a one-time reduction in the receivable balance, not recurring profit.

How to start

1. Measure both halves separately. Days from completion to invoice, and days from invoice to cash. Many shops have neither number on hand. If your FSM can't show post-completion billing speed, export completion dates and invoice dates for the last 90 days and compute it yourself.
2. Kill the "ready to invoice" queue. Make completion trigger billing, not a weekly manual pull.
3. Put AR follow-up on a fixed cadence. Day 7 / 14 / 30, automated, with humans on exceptions and disputes, and with contract and lien deadlines calendared separately.
4. Reconcile work performed vs. work billed monthly. The change orders and small jobs that never got invoiced add up fast.

Finished work is the most frustrating place to lose money, because you already did the hard part. Close the job-to-cash gap and you convert margin you've already earned into cash you can actually use, no new sales, no new crew.

FAQ

What is the job-to-cash gap?

It's the time and money lost between finishing a job and getting paid for it, across two stages: completion to invoice, and invoice to collection. It's primarily an operational handoff problem (nobody flags the job as ready to bill, nobody chases the invoice), not an accounting one, even though it shows up in your cash position.

How fast should a contractor invoice after completing a job?

As close to same-day as possible. In Level's cross-trade research (733 companies), the adjusted median among post-completion invoicers is about 7 days. The full-cohort slowest-decile threshold is 30 days; the post-completion decile is not separately published. Take a fictional $10M contractor that bills everything after completion. A 7-day lag holds about $190K in float versus billing immediately, and closing it releases that cash once, not every year.

How does AI improve contractor cash flow?

By running the routine steps on reflexes: auto-drafting the invoice for a named person to approve when a job is marked complete, escalating AR on a fixed day-7/14/30 cadence, and flagging change orders or completed jobs that never got billed. Humans handle disputes and key-account calls; the system handles the forgetting that creates the lag.

Isn't slow cash just a collections problem for my bookkeeper?

No. Your bookkeeper records what already happened. The lag was created upstream in the operational handoff. Part of the gap can be work that was finished but never invoiced, which never reaches collections at all. Measure that share by comparing completed jobs against invoices issued. Fixing it requires connecting field completion to billing to follow-up, which is an operations job.

---

If you finished a strong month and payroll is still tight, check whether the cash is stuck between the field and the bank. Book a 15-minute call and we'll scope the records needed to measure both halves of your job-to-cash gap and the float involved. The first profitability audit is free.