Inside the Time-to-Invoice Problem: Where Revenue Gets Stuck

Picture two work orders at a mid-sized service company.

The first job is completed on August 15. The work is done and the equipment is running again, but somewhere between the job site and the back office, the order slips through the cracks. Six weeks later, it's still sitting as "open" in the system, fully billable and completely invisible.

The second job wraps up on August 25. The technician finishes the repair, the customer is satisfied, and the order is marked complete. This one does get invoiced, on September 10, 16 days later. The delay happened because it took over 2 weeks for the billing department to find the evidence pictures to attach to the invoice and reconcile the parts consumed for accurate billing.

Neither scenario is unusual, but both are costly. In our conversations with service leaders, we ask how many days it really takes to go from job complete to invoice out. Most answer in weeks rather than days, and a majority guess low.

We dug into this problem during our webinar, Time-to-Invoice: Closing the Gap Between Job Complete and Invoice (watch the recording here), with Shannon Ruffing and Tarrell Graham, co-founders of Solhver. Shannon has spent 10 years in the trades across operations and finance. Tarrell has spent 30, working his way from technician to CEO of a private equity-backed company.

That delay between job completion and issuing the invoice represents your time-to-invoice. Though seldom highlighted on performance dashboards, it directly impacts cash flow, revenue generation, and team efficiency. To evaluate your organization’s current time-to-invoice, consider three key questions:

• How many days, really, does it take from a job being complete to invoice going out?
• Where do those days go?
• Which jobs are aging past 30, 60, or 90 days right now, and how much revenue is sitting in them?

If you can answer all three with confidence, you're already ahead of the field. 

Why Time-to-Invoice Matters to the Bottom Line

The Payment Clock Starts When the Invoice Goes Out

Your customer’s payment terms don’t begin when the work is finished. They begin when the invoice arrives, so each day of invoicing delay pushes the whole payment cycle back. Take the August 25 job from our example. On net-30 terms, an invoice sent 16 days after the work was done won’t be due until roughly 46 days after completion, and that assumes the customer pays on time.

Imagine a restaurant waiting 16 days after serving a meal to give the customer their check. The food has been prepared, the service delivered, and the bill is ready to be paid. But until that check goes out, the restaurant can't collect.

That's exactly what happens in field service, often on a much larger scale.

For a service business generating $100 million in annual revenue, approximately $274,000 in work gets completed every day ($100M divided by 365 days). If it takes 10 days to send an invoice after a job is completed, the business has roughly $2.7 million in completed work waiting to be billed.

Meanwhile, payroll, equipment, fuel, and operating expenses don't wait. The business continues spending money to deliver new work while millions of dollars from completed jobs remain unbilled.

Reducing that delay by just one day means approximately $274,000 less tied up in unbilled work. Even for a smaller $10 million operation, that same improvement represents about $27,400.

And these are just illustrative estimates. For organizations with longer delays or significant invoicing bottlenecks, the financial exposure can be substantially higher.

Tarrell framed the cost of that delay in terms any finance leader will recognize. Slower invoicing means slower collections. AR builds, and the cash gap has to be covered somewhere, often with a line of credit and the interest expense that comes with it.

"You're essentially acting as a bank at that point."
Tarrell Graham, Co-Founder, Solhver

Revenue Leaks From Work That Gets Stuck

Slow invoicing delays revenue, and some of it never comes back. The longer an order sits, the more likely it is to leak:

• Parts get used on the job but never make it onto the invoice. Lost parts eventually surface as inventory or COGS adjustments, often when month-end reports come due.
• Smaller projects frequently get completed but are forgotten when it comes time-to-invoice. Michael Gonzalez, CEO of MSI Data, highlighted how jobs valued at $500, $1,000, or $1,500 often result in satisfied clients but zero billed revenue.
• Some losses get pushed through as $0 invoices instead of formal write-offs, so they never show up clearly on the P&L.
• Warranty claims stall when serial numbers or photos are missing. Service leaders we spoke with during our 2026 Roadshow estimated a return trip to capture that information costs $200 to $250 in wages, fuel, and lost billing hours.

Tarrell called these "micro-cuts": small losses that add up and stay hidden in your finances. Delays reach your customers too. As Tarrell pointed out, satisfaction drops as communication slows, and that affects relationships well before it shows up in a report.

The August 15 order from our example is the worst version of this problem. The revenue is fully earned, and without an invoice, the payment clock hasn't even started.

Billing Teams Spend Their Time Chasing

Invoicing staff frequently spend more time gathering data than actually preparing bills. Shannon highlighted the tasks that consume their days: tracking down part sources across vans, warehouses, or local supply runs, translating technical terminology and shorthand into customer-friendly wording, and reviewing technician labor hours that are routinely delayed by 12 to 24 hours.

The information itself is scattered. Tarrell said one admin they met described herself as an investigator, and the Sherlock Holmes comparison resonates with nearly every biller he meets. Details live in group texts, spreadsheets, photos of handwritten tickets, and technician notes as brief as "finished job, all working," which Tarrell admits was his own style early in his career.

One site visit made the cost concrete. Tarrell and Shannon sat with a biller who had built her own workaround: a Word document of saved prompts she used with Copilot and ChatGPT. For each invoice, she copied notes out of the sales order, pasted them into an AI tool with the right prompt, and copied the result back, with four or five copy-paste steps per invoice.

She created a manual workflow that performs the exact function of our Invoice Ready Notes feature, which handles this process automatically. The automated agent analyzes technician field report notes and generates a concise, standardized Complaint, Cause, and Correction summary directly within the invoice notes field. It preserves crucial technical readings while filtering out internal chatter, names, and time punches, all without overwriting existing manual entries.

"She essentially made an Invoice Ready Notes agent, it's just that she was the API. She was moving the data."
Tarrell Graham, Co-Founder, Solhver

Time lost to manual work like that seldom appears in standard KPIs. According to Tarrell, reclaiming those hours allows staff to focus on high-value tasks requiring human judgment, such as AR collections, an area where many trade companies remain understaffed

Where Time-to-Invoice Breaks Down

We've been measuring time-to-invoice alongside our customers, and a consistent picture is starting to form. These are working hypotheses, and we want to test them against what you're seeing in your own operation.

Nobody Owns the Gap

Most service businesses run two strong systems. The field service management (FSM) platform owns the job, and the ERP owns the invoice. Both can work well on their own. The handoff between them, where notes, parts, reviews, and approvals come together, often belongs to no one.

A typical path from job complete to invoice looks something like this:

• Work is completed on site
• Notes, photos, and parts are captured that night or days later
• The office reviews the notes and often rewrites them by hand
• Someone manually checks labor, parts, and warranty or contract coverage
• Approvals sit on a desk
• The ERP finally sends the invoice

Integrations often take the blame, but the bigger issue is usually the processes around them. Each handoff depends on people executing a documented process the same way, across thousands of work orders a month.

"You almost have to pitch a perfect game every single time."
Michael Gonzalez, CEO, MSI Data

Field Lag vs. Back-Office Lag

We believe time-to-invoice is really two separate measurements:

• Field lag: the time from job done to paperwork complete
• Back-office lag: the time from paperwork complete to invoice out

On the field side, the best technicians tend to complete their paperwork at the end of the day, rarely at the end of the job, and many don't get to it until the end of the week or later. Your overall time-to-invoice tells you there's a problem. Splitting it into field lag and back-office lag tells you where to start fixing it.

Four Patterns We See Repeatedly

When we baseline time-to-invoice with customers, the same four patterns keep showing up:

• Notes arrive late. They're written that night or days later, then rewritten in the office before they're usable on an invoice.
• Parts used don't match parts billed. Parts get mentioned in the notes but never recorded, or they're waiting on a purchase order nobody is watching.
• "Tweaky" jobs stall. The orders that age are often the ones that need a judgment call and end up sitting on an approver's desk.
• Small jobs get skipped. Below a certain dollar threshold, work gets written off because the effort to chase it doesn't seem worth it.

Why Hiring Another Biller Won't Fix It

When invoices back up, the natural instinct is to add headcount. Customers have told us up to 90% of invoicing time is spent waiting on information from the field, rather than processing or typing the invoice. If most of the delay comes from waiting, adding people to type invoices won't move the number much.

Hiring is also harder than it used to be. According to Robert Half's 2026 Salary Guide, 62% of finance and accounting leaders say they struggle to hire and retain accountants. With talent this tight, the more durable fix is getting complete information at the source, while the job is still fresh.

Why Now

Tarrell pointed to two timing factors. Many trades businesses head into a slower season at year-end, which leaves more room to rethink a process than the middle of summer does. October and November are also budgeting season for many organizations, a natural window to scope the work for next year.

He also raised a less obvious risk. Employees are already using AI tools on their own, like the biller with her prompt document. Without a deliberate approach, those habits can fragment your data and processes, and they're hard to undo once they spread.

What Changes When You Can See the Gap

We believe three principles make time-to-invoice manageable:

• Measure one number, daily. Track median days from job complete to invoice out, split into field lag and back-office lag. A number you see daily is easier to act on than one you discover at month-end.
• Fix information at the source. Missing notes, parts, and photos are easiest to capture while the technician is still on site.
• Work between the systems you already run. Closing the gap doesn't require replacing your FSM or your ERP.

For teams that start measuring, Tarrell suggested watching for time-to-invoice to drop within the first 30 days, with the larger financial impact showing up at 60 to 90 days as cash flow catches up. The goal is to move time-to-invoice from weeks to days.

See Your Time-to-Invoice

"It's cash you've earned, so go get it."
Michael Gonzalez, CEO, MSI Data

If you want to get a better handle on your time-to-invoice, the three questions from the top of this post are a good place to start. We'd like to help you answer them using your own data: your average time-to-invoice, where invoicing delays happen, and the dollars tied up in aging orders.

Let us help you find your time-to-invoice: click here.

Missed the live session on the time-to-invoice problem? Get the recording here.

Frequently Asked Questions

What is time-to-invoice?

Time-to-invoice is the number of days between when a job is completed and when the invoice is sent to the customer. It's measured before payment terms begin, so any delay here pushes back the entire payment cycle.

What's the difference between field lag and back-office lag?

Field lag is the time from job completion to complete paperwork, including notes, photos, and parts. Back-office lag is the time from complete paperwork to invoice out, including review, coverage checks, and approvals. Measuring both shows you which part of the process to fix first.

How is time-to-invoice different from DSO?

Days sales outstanding (DSO) measures how long it takes to collect payment after an invoice is issued. Time-to-invoice measures the delay before the invoice exists. Because unbilled work hasn't become a receivable yet, time-to-invoice delays don't show up in DSO, which makes them easy for finance teams to miss.

Why doesn't adding billing staff fix slow invoicing?

Customers have told us that up to 90% of invoicing time is spent waiting on information such as technician notes, purchase orders, and warranty documents. More billers can process complete information faster, but they can't create information that was never captured.

How do I start measuring time-to-invoice?

Pull the completion date and invoice date for a recent set of orders and calculate the median number of days between them. If your status fields allow it, split that number into field lag and back-office lag. Then check how many open orders have aged past 30, 60, and 90 days, and how much revenue is sitting in them.