From Field Ticket to Invoice: Where Industrial Contractors Lose Cash

A signed field ticket is a promise that money is owed, and it is worth everything it will ever be worth at the moment the customer’s representative signs it. What happens next only subtracts: the ride back in a truck, the folder on a desk, the phone photo in a text thread, the retyping on Friday by somebody who was not there.

That subtraction is not a billing problem. It is cycle time, and cycle time is working capital. A contractor whose signed tickets take three weeks to become sent invoices carries three weeks of payroll, fuel, rentals, and subcontractor cost on the customer’s behalf, continuously, for free. It never appears on a profit and loss statement. It appears as a line of credit that never quite gets paid down.

Nothing here is specific to a refinery gate. It applies to any contractor whose customer decides what the paperwork looks like.

What actually happens between a signed ticket and a sent invoice?

Usually nothing. The ticket waits.

Laid out honestly, the sequence runs: work completed, ticket written, ticket signed, ticket transported, ticket batched with the week, ticket re-keyed by somebody who was not on site, invoice assembled, invoice submitted, invoice rejected over a missing reference or a cost code that changed last quarter, invoice corrected, clock restarted.

Two of those steps create value. The rest are queue and rework, and almost none of it is measured. Ask how long it takes to get paid and you will hear days sales outstanding, which describes the customer’s behavior. The interval between work finished and invoice sent describes yours.

What should be captured at the moment of signature?

Everything the customer’s accounts payable department will ask for later, recorded once, on site, by the people who did the work.

That means the job and purchase order number, the cost code, date and shift, crew hours split by labor classification and by straight, overtime, and premium time, equipment by unit number, materials and consumables, any third-party rental or pass-through incurred, photographs before and after, and the rate sheet line each entry bills under. An entry that cannot be tied to a billable line when written gets tied to one by guesswork three weeks later, or never billed.

The signature matters as much as the fields. A representative signing on a device at the site produces a timestamp, a named signer with a title, and the exact contents of the ticket at the moment of signing. Carbon paper photographed two days later produces a conversation instead. When a ticket is questioned six weeks on, whoever can show what was signed, when, and by whom ends that conversation early.

Why match the ticket to the purchase order and rate sheet before invoicing?

Because those three documents are the only place a dispute originates, and two are knowable before the invoice exists.

The purchase order carries scope and a ceiling. The rate sheet carries the prices both sides agreed, by classification and equipment class. The ticket carries what happened. Checking at entry that the order is open, that value remains against it, that every classification appears on the rate sheet, and that the rates are current rather than last year’s is cheap, and it is the only moment anyone can still act on the answer.

A crew told on Tuesday that the purchase order runs out Thursday is having a commercial conversation. The same fact surfaced during invoicing is performed work nobody authorized, which is not a collections issue — it is margin already spent.

Not every ticket bills the same way

Time and materials, unit rate, and lump sum are three different documents wearing one cover sheet, and treating them identically is how quantities get lost.

A time and materials ticket records resources consumed, so hours and units are the billable facts. A unit rate ticket bills measured quantities against a schedule of values, so the measurement — feet, joints, square footage, tons handled — is what bills, and hours are internal cost only. Lump sum work bills against milestones, where the field record proves a milestone was reached rather than what it took. A contractor running all three, normal on plant and marine work, needs the ticket form to know which kind of job it belongs to before anyone writes on it. Otherwise crews record hours on measured work and the office reconstructs quantities from photographs.

When does a change order have to be recorded?

At the moment it is agreed, by the people who agreed it, standing where they agreed it.

Scope changes get settled verbally between a foreman and a customer representative standing next to the problem, and both are being reasonable. The failure is never the decision; it is that the decision lives in two memories until an invoice forces it into writing, by which point one memory has moved on and the other is negotiating. A change captured in the field — what was directed, who authorized it, and the signature of the same representative who signs the ticket — turns an argument into an attachment.

What does the customer require before it will pay?

An invoice on its own is rarely enough. Large industrial and public customers pay against a billing pack.

Depending on the contract that pack can include signed tickets, the order reference, cost coding in the customer’s own structure, daily reports, certified payroll, lien waivers, insurance certificates, current training records for everyone on site, and submission through a portal inside a defined window. Miss the window and the money waits a full cycle for a reason nobody can defend.

Collecting those documents, checking that none is missing or expired, formatting them per customer, and submitting them on time is work software handles well. The limit is worth stating plainly: automation assembles and routes paperwork, and makes no health, safety, or environmental judgments. Whether an analysis is adequate, whether a person is qualified for a task, and whether work proceeds are decisions for qualified people, and CMA is not a safety, environmental, or compliance firm. The system’s only job is to keep the qualified person’s decision recorded, current, and attached to the right job.

Where retainage quietly lives

Retainage is your margin, held by somebody else, on terms you agreed to and probably do not track by job.

Hold it as a receivable in its own right, with the release condition and expected date attached per job, rather than as one aggregate figure on the balance sheet. Release is normally tied to a milestone and a document — final completion, a punch list, a closeout package — the same documents the job should have produced anyway. Chasing retainage once a year instead of at closeout means reconstructing paperwork that was complete at the time and has since scattered.

What number belongs in front of an owner every day?

Work performed and not yet billed, aged by day.

That single view — every ticket where the work is done and no invoice has gone out, grouped by how long it has sat and what is holding it — is the closest thing this business has to a cash gauge. It exposes which crews are slow to turn tickets in, which customers reject most often and why, and which jobs are running past their orders.

To size it before spending anything, pull last quarter and record, for every invoice, the date the work finished and the date it went out. Average that gap and multiply by average daily billings. The result sits permanently inside the paperwork, and it spends the same as borrowed money.

Does this mean buying something?

Frequently not. Exhaust what you own first, and total what that stack costs with the stack cost calculator before adding to it. Buying stops helping once the systems holding the job disagree with one another, since settings inside any one of them cannot reconcile the rest. Then the choice is renting that disagreement forever or owning the layer underneath it, which is the argument in what you keep. A $500 Workflow Map, credited against the $3,500 Operations Audit, is the cheapest way to learn which situation you are in; process automation builds start at $10,000. One caution: a process living only in one person’s judgment cannot be automated, only transcribed badly, so if ticket quality depends on who holds the pad, start with SOPs.

CMA is based in Dallas with no office and no staff in Corpus Christi; travel for the on-site portion is scoped and priced up front rather than discovered later. Whether any of this survives contact with a crew depends on somebody watching a ticket get filled out at the end of a shift, then sitting with whoever does the billing. Scope and published prices for this market are on the Corpus Christi process automation page, and the underlying case is made in cash flow problems are operations problems.

Bring last month’s unbilled tickets to a 30-minute call. That is a more useful conversation than any demo.