The ticket rode in the truck for three days
The work was done Monday. Nobody billed for it until the following week, and nothing that happened in between was your customer's fault.
The short version
4 things that decide this
- 01Enverus's own field-ticketing research names the exact pattern this piece is about: crews drive tickets to offices for approval, and lost or illegible tickets delay payment for weeks.
- 02The delay isn't the operator's payment terms. It's everything that happens before the invoice is even submitted, and almost all of that time is under your own control.
- 03A ticket that rides in a truck cab for three days is three days of working capital nobody can spend, whatever your invoice terms say.
- 04Digital capture, same-day approval and validation against dispatch remove most of the controllable delay, and they remove it before the operator ever sees the ticket.
The job finishes. The ticket doesn't move for three days
Picture a normal Monday. Your crew finishes a job at a wellsite forty minutes outside town. Someone fills out a paper ticket: hours, units, equipment, a signature from the company man if you're lucky enough to catch him before he leaves. The ticket goes on the dash, or in a folder, and the truck heads to the next job.
It doesn't reach your office that day. Maybe it doesn't reach your office that week. The crew is out on other jobs, the truck comes back to the yard on Thursday, and the ticket surfaces in a stack with a dozen others. Nobody did anything wrong here. This is just what a paper ticket does when the person carrying it has other jobs to do first.
By the time someone in your office reads the ticket, keys it in, and routes it for approval, three days have already gone by since the work happened. And that's before anyone has thought about invoicing at all.
Enverus names this pattern for a reason
You're not imagining this, and you're not the only shop it happens to. Enverus's own field-ticketing research, published under the title "7 Field Ticketing Pain Points," names the exact pattern: workers drive tickets to offices for approval, and lost or illegible tickets delay payment for weeks. That's not a competitor's marketing claim about your operation. It's the industry's own vendor describing what it sees across the accounts it serves.
Here's the part worth sitting with. None of the days your ticket loses between the wellsite and your office are the operator's fault. Your operator's payment terms don't start the clock until they receive a submitted invoice. Every day before that, the ticket riding in a cab, waiting in a stack, getting keyed in by hand, is time you're losing before the game even starts. Call it a document logistics problem, because that's what it actually is. It just happens to cost you real money every single week.
- Work finishesTuesday, at the wellsite
- Ticket rides in the truckDays, not hours, until someone passes the yard
- Waits in a pileA supervisor's desk, over a weekend
- Gets keyed inMidweek, by hand, into whatever system you run
- Invoice goes outTen days after the work, if nothing bounced
The operator's payment clock hasn't even started yet. Every station above this line is yours to fix.
Lost, illegible, and disputed: the three ways paper fails
A ticket that rides in a truck for three days is the best case. Three worse things happen to paper tickets often enough that every controller in this industry has a story about each one.
A ticket gets lost. It falls under a seat, gets left at a site, or never makes it out of a folder that ends up in the wrong truck. Lost work is unbilled work, and nobody notices until someone reconciles hours against invoices weeks later and finds the gap.
A ticket gets written badly. Hours smudge, a number gets transposed, a signature is illegible. Someone in your office has to call the field to confirm what the ticket actually says, and that phone call is another day gone.
A ticket gets disputed. The operator's coder reads the hours differently than your supervisor did, or a rate doesn't match the master service agreement, and the whole thing bounces back for a correction. Now you're not three days behind. You're restarting the clock from scratch, with a rejection attached to your record.
- 01Lost tickets: unbilled work that surfaces weeks later, if it surfaces at all.
- 02Illegible tickets: a phone call to the field, and another day gone confirming what should have been clear the first time.
- 03Disputed tickets: the whole cycle restarts, and the rejection sits on top of the original delay.
Digital capture doesn't speed up the truck. It removes the truck from the equation
Imagine the same Monday, but the ticket never leaves the wellsite as paper. Your crew fills it out on a phone, offline if the site has no signal, and the company man signs on the device before anyone leaves. The ticket exists digitally the moment the work finishes, not three days later when someone happens to pass the yard.
Your supervisor gets a notification and approves from their own phone, the same day, instead of finding the ticket in a Thursday stack. Once approved, the ticket is validated against what dispatch actually sent, so a duplicate line or a rate that doesn't match your contract gets caught in your office instead of the operator's audit. Then the invoice generates itself from the approved ticket, coded correctly, and goes out in whatever format your operator's portal requires.
None of this changes your operator's payment terms. What it changes is the part you actually control: the days between the work happening and the invoice existing at all. That's usually the larger half of your real DSO, and it's the half nobody's collections team can do anything about.
Some of the systems we have shipped
Related questions
01Is the delay usually the operator's fault, or ours?+
Almost always ours, and that's the useful part of this. Operator payment terms start once a clean invoice is submitted. Everything before submission, the ticket's journey from the wellsite to your accounting system, is inside your own control.
02Do crews actually accept digital ticketing in the field?+
Yes, once the app is faster than paper and works with no signal. Offline-first capture is the requirement that decides this. A crew asked to find bars before saving a ticket goes back to the clipboard within a week.
03How much of our DSO does this actually fix?+
More than most controllers expect, because the paper journey usually accounts for the larger share of the gap between work and invoice, not the operator's payment terms. Our audit measures your real number instead of guessing.
04What if we already use a ticketing app but still see delays?+
Then the gap has probably moved downstream, into validation against dispatch, or the format your operator's portal requires. That's worth tracing the same way: one job, dated at every hand-off.
