Why field tickets get disputed, and what each dispute actually costs

A disputed field ticket is rarely a disagreement about whether the work happened. The crew was there, the customer’s company man watched them do it, and nobody is pretending otherwise. The dispute is almost always about the paperwork describing the work. That distinction matters, because paperwork problems are detectable in advance and disagreements about reality are not.

Here are the five ways it goes wrong, in roughly the order of how often we see them raised.

1. The rate on the ticket is not the rate in the agreement

Master service agreements carry rate schedules. Those schedules get amended, renegotiated at renewal, superseded for specific projects, and occasionally overridden by a one-off letter agreement that lives in somebody’s inbox. Meanwhile the crew is billing from the rate sheet they were given, which may be the one that was current eighteen months ago.

This is the single most common cause of a short-pay, and it is completely mechanical. The customer’s AP system compares the line item to the contracted rate, finds a difference, and pays the lower number. Nobody is being dishonest. Two documents simply disagree, and the one your customer holds wins.

The reason it persists is that checking is expensive when done by hand. Verifying every line on every ticket against the governing rate schedule is precisely the kind of work that gets skipped when volume is high, which is to say, exactly when it matters most.

2. The ticket is missing an authorization the contract requires

Most MSAs specify who has to sign, and for what. A company man’s signature on the ticket. A separate approval for work outside the original scope. A purchase order number, an AFE number, or a cost center reference that must appear on the face of the document.

When one of these is missing, the ticket does not get argued about. It gets rejected, often silently, and re-enters your process as an exception. The crew that could have obtained the signature is three counties away by the time anyone notices.

3. The work was not covered by the authorization it was billed against

This is the expensive one. The job was authorized under one AFE or PO, the scope expanded in the field for perfectly good operational reasons, and nobody generated a new authorization before the work was done. Your customer’s position is straightforward: they authorized X, you billed X plus Y, and Y was never approved by anyone with the authority to approve it.

You will usually get paid something. You will rarely get paid all of it, and the argument will take months.

4. Quantities are disputed

Hours on site, standby time, equipment days, consumable counts. These are genuine disagreements more often than the others. Your ticket says eleven and a half hours, their company man remembers ten. Without a contemporaneous record that both parties saw at the time, the dispute becomes a question of whose memory is better documented, and the party holding the money has more patience than the party waiting for it.

5. The ticket was submitted after the contractual window closed

This one is underrated and it deserves its own paragraph, because it is the only item on this list where you can lose one hundred percent of the value.

Many master service agreements contain a submission window, commonly worded as a requirement to submit invoices or supporting tickets within a set number of days of the work being performed. Ninety days is typical, sixty is not unusual, and thirty appears in agreements with larger operators. Miss it, and the customer has a contractual basis to refuse payment entirely for work you actually performed.

Companies that discover this discover it in a batch. Somebody reconciles an old job, finds a stack of tickets that were never billed, and learns that the window closed a month ago. There is no negotiating position. The work is simply gone.

What a dispute costs beyond the write-off

The write-off is the number that shows up in your accounts, and it is usually the smallest part of the total.

The dispute cycle costs administrative time. Someone has to receive the short-pay notice, pull the original ticket, find the governing agreement, assemble the supporting documentation, write the rebuttal, and follow up on it, usually several times. That is hours of skilled AR time per disputed ticket, and the people capable of doing it well are not your cheapest employees.

The whole invoice ages, not just the disputed line. A dispute on one line item frequently holds the entire invoice. Ninety-five percent of the value that was never in question sits unpaid while a small argument gets resolved. If you are financing operations on a revolver, that delay carries a real interest cost on the full invoice amount.

Your credibility degrades with the customer’s AP team. A vendor whose tickets are usually clean gets the benefit of the doubt on the ambiguous ones. A vendor whose tickets routinely need correction gets scrutiny on everything, permanently, and that scrutiny is applied by people who are measured on how much they hold back.

Field crews get pulled backwards. Every dispute that requires reconstruction takes a supervisor away from the work in front of them to reconstruct work from three weeks ago, usually from memory.

Almost all of it is detectable before the invoice goes out

Look back at the five causes. Four of them (rate mismatch, missing authorization, unauthorized scope and late submission) are detectable at the moment the ticket is created, by comparing the ticket against documents you already have. Only quantity disputes require evidence you have to deliberately capture in the field.

That is a useful thing to know, because it tells you where the cheap fix is. The expensive moment to catch a billing problem is after the customer catches it. The cheap moment is before the invoice is generated, while the crew is still on location and a correction costs a phone call.

Doing that check by hand at volume is not realistic, which is why most companies do not do it. Doing it mechanically requires three things: a rate schedule that a computer can read, a ticket that arrives as structured data rather than a photograph, and a comparison step that runs before the invoice is generated rather than after the customer runs theirs.

None of that is exotic. It is document handling, and document handling is the thing this generation of software is unambiguously good at.

Where to start if you want to know your own numbers

Pull the last six months of short-pays and sort them by cause. Not by amount, by cause. Most companies find that a large share of the count comes from one or two mechanical categories, and that the mechanical categories are the ones that never get fixed because everyone is busy fighting the individual cases.

Then measure how long a ticket takes to get from the field to an invoice, and compare it to the shortest submission window in your top five agreements. If the gap makes you uncomfortable, that is the project.