Truck Ticket Verification: Catching the Load Counts, Weights, and Haul Routes That Don't Match Reality
Hauling operations on a construction site — dirt moved off, aggregate brought in, asphalt delivered, demolition debris carted away — generate a lot of invoices. On a medium excavation project, a crew might generate 200-400 truck tickets a week. Each one represents a billable transaction: load count, material type, weight, origin, destination, signed by someone on site.
Because volume is high and individual tickets are small, verification tends to be spotty. Tickets get bundled into weekly invoices with dozens or hundreds of line items. If the office doesn't have a way to cross-check the tickets against some field record, the hauling vendor's tally is effectively what gets paid. Most of the time that's fine — vendors run honest businesses, and accidental over-counting is a small percentage. But on projects with significant hauling volume, the small percentage adds up, and there are specific patterns worth catching.
A hauling truck ticket is typically a three-part form: one copy stays with the pit or quarry, one stays with the hauler or driver, and one goes to the receiving site. On delivered material (aggregate, asphalt), the ticket shows where the material came from. On hauled-off material (excavated dirt, demolition debris), the ticket shows where it was taken.
Standard fields on a truck ticket
- Ticket number
- Date and time
- Truck number and driver name
- Hauler company name
- Origin (for delivered material) or Destination (for hauled-off material)
- Material description — dirt, rock, aggregate type, asphalt mix, fill classification
- Gross weight, tare weight, net weight (if weighed)
- Volume (if volume-based — e.g., cubic yards)
- Project or job-site receiving
- Signature of receiving/sending field representative
The signed ticket is the primary document. Everything downstream — the invoice, the monthly billing summary, the pay application's line-item recovery — traces back to the signed ticket count. Missing or unsigned tickets are where most verification problems start.
Hauling can be billed by weight (ton) or by volume (cubic yard). Most aggregate and asphalt billing is by weight — the truck is weighed at the pit or batch plant, and the net weight goes on the ticket. Dirt and demolition debris are sometimes billed by volume — the truck is assumed to carry a standard load size based on its truck class.
Weight-based billing is generally more accurate because actual load weights vary by material density, moisture content, and loading technique. Volume-based billing assumes the truck is full each time, which isn't always true. A half-loaded truck makes half a haul's worth of trips but bills as if full, inflating the project's actual material volume.
Specifications sometimes require weight-based billing for specific materials to prevent this. When the contract says "All aggregate supplied under this contract shall be billed by net weight per certified scale ticket," the invoice backup should include the scale tickets. When it says volume-based, the verification process has to rely on truck counts and assumed load sizes.
Many active job sites have gate cameras or entry logs that record every truck entering and leaving. When the gate log exists, it's a powerful cross-check against the hauler's invoice count. A hauler claiming 400 loads in a week on a site where the gate log shows 350 trucks entering from that hauler has either an error or a problem.
Modern gate cameras with license plate recognition can produce logs automatically. Even a simple sign-in sheet at the gate — filled out by the gate attendant when trucks arrive — is good enough for this kind of cross-check on a smaller project. The principle is the same: an independent count of truck visits to the site that the hauler's office doesn't control.
On projects with high-volume hauling, the ROI on a gate camera system is often measurable in a single month. The cost is low — a few hundred dollars a month for a basic system — and the hauling invoice reductions from systematic cross-checking more than cover it on projects with significant hauling exposure.
For weight-based hauling, the pit or batch plant produces a scale ticket for each load. The scale ticket is a separate document from the hauler's ticket — it's generated at the pit, prints the gross/tare/net weight, and typically carries a ticket number from the pit's system.
The scale ticket is the most authoritative weight evidence. A hauler's invoice claiming 22 tons on a load should be backed by a scale ticket showing the actual weighed amount. When the hauler invoices for more than the scale ticket shows, the math is wrong and the invoice is over. When the invoice is silent on net weight and just shows a dollar amount, the AP team should request the scale tickets.
On big projects, collecting scale tickets from the pit is part of the standard process. The pit bills the hauler based on material purchased; the hauler bills the contractor based on material delivered. Both should tie back to the scale tickets. Mismatches indicate that someone in the chain has the math wrong (or is carrying inventory from a previous transaction on this ticket).
Hauling rates often include a distance component — a base rate plus per-mile charge, or different rates for different haul distance brackets. A load hauled 8 miles from the pit to the site costs less than a load hauled 22 miles. The distance is built into the quoted rate or billed as a separate line.
The distance billed should match the actual route. When a hauler bills the long-haul rate on what was actually a short haul from a closer pit, the billing is inflated. Knowing where the material is actually coming from — and matching it to the distance billed — is the check. Some contractors maintain a list of approved pits for each project with the distance to site, and invoice verification compares the ticket's origin against that list.
Get AP insights in your inbox
A short monthly roundup of construction AP + accounting posts. No spam, ever.
No spam. Unsubscribe anytime.
Material Substitution
The material description on the ticket should match what the spec calls for. When a spec requires #57 aggregate and the ticket shows #67, there's a substitution happening — either authorized by the contractor or not. When the material description is vague ("crushed rock" on a spec calling for a specific gradation), the ticket doesn't prove the right material was delivered.
AP can't always tell whether a substitution is legitimate — that's a field and engineering question. But the AP system can flag mismatches between the spec and the ticket description for field review. An invoice billing premium material that the ticket describes as a lower grade deserves scrutiny before payment.
When a hauler truck has to wait at the site to unload — because the site isn't ready, or there's a line ahead of it — the hauler may bill standby or demurrage. This is separate from the haul rate. The discipline is the same as with concrete pump standby: document the wait time on the ticket at the field, and match it against the invoice.
Demurrage rates vary widely — $50/hour to $150/hour depending on the trucks and the market. On busy sites with traffic and queuing, demurrage can accumulate quickly. Tracking demurrage-reducing improvements (better staging, shorter queues) pays off directly in reduced standby charges.
Automating truck-ticket verification at scale involves a few steps that systems can handle consistently:
Automation points for hauling invoice verification
- OCR the ticket — extract ticket number, date, time, origin/destination, material, weight/volume, driver signature presence
- Match ticket against the hauler invoice line-item by line-item — count tickets, sum weights or volumes, compare to invoice totals
- Cross-reference ticket timestamps with gate-camera or gate-log entries — flag invoices with ticket counts exceeding the gate count
- Verify material descriptions against the project specification (or an approved substitution list)
- Compare net weights against the pit's scale tickets where available
- Flag invoices with haul-distance charges inconsistent with the recorded origin
- Check for duplicate ticket numbers — a ticket billed twice because it appeared on two invoice cycles
On large earthwork, demolition, or paving projects where hauling volume dominates the cost, a few patterns are worth monitoring specifically:
Patterns worth watching closely on high-hauling-volume projects
- Trucks making round trips shorter than physically possible given the haul distance — suggests either round-tripping (double-counting) or phantom loads
- Trucks arriving or departing outside the site's active hours on the gate log
- Haulers billing more loads per day than a truck can realistically complete given shift hours and travel time
- Material descriptions changing mid-project without documented approval — the sign of either an authorized substitution that wasn't documented or unauthorized substitution
- Weight per load trending upward over a project's life — could indicate genuine density changes, or could indicate the hauler tightening up their ticket weights now that they know the AP review isn't catching it
Truck ticket verification is one of the highest-volume AP tasks on earthwork and paving projects. Scale tickets, gate logs, material specs, and approved haul-distance lists are the independent data sources that keep the hauler's billing honest. Automation reads the tickets, matches them against invoices, and flags the discrepancies — turning what would otherwise be a spot-check process into a systematic one. On projects where hauling is a significant cost component, that systematic verification is where real money gets saved.
Written by
Alex Kim
Engineering Lead, AI
Engineering lead for Covinly's AI and ML systems. Previously built fraud detection at a B2B fintech. Writes about how AI actually reads invoices — the math, the edge cases, and why OCR alone isn't enough.
View all posts