A haul ticket may arrive without a job code. The driver's load count may not match the scale-house total, or a fuel advance may post after the settlement cutoff. Cutoff-week failures begin when the ticket, agreement, and accounting record no longer describe the same trip. When those records diverge, the team can pay the driver correctly while assigning the ticket to the wrong phase code, or it can duplicate a quantity or fuel deduction across the settlement statement, job-cost entry, broker invoice, and project quantity report.
The driver settlement workflow below starts by reconciling trip records, contract terms, and accounting entries. It then applies the contractual pay basis and verifies deductions and compliance records. Exceptions are routed with supporting evidence. The workflow generates an itemized statement and summary only after required records and material exceptions have been reviewed and approved.
Automating the routine part moves settlement managers off re-keying and onto disputed quantities, deductions, and classifications before they release pay, the same shift that document control makes possible everywhere else on a project. The sections below define a settlement, explain how it calculates net pay, and walk through five checks for resolving exceptions before payment.
What Is a Driver Settlement?
A driver settlement is the itemized payment statement that resolves those records into gross earnings, deductions, reimbursements, advances, and net pay for a driver or owner-operator.
The settlement summary is the snapshot within that statement. It typically shows the amount paid for the current period, the pay basis, and year-to-date earnings, deductions, reimbursements, and reserve balances. The underlying statement provides the load-by-load or ticket-by-ticket detail needed to verify those totals.
For built-world project teams, the calculation may depend on tons delivered, loads completed, hours worked, mileage, or a percentage of hauling revenue. It may also require paper or electronic haul tickets, project and cost codes, truck-broker records, public-project requirements, and construction ERP data. In an automated process, the system can interpret those records, compare them against configured rules, flag exceptions, and prepare a structured settlement for human approval.
A five-step workflow verifies field records and unusual deductions while automating driver settlement processing. It preserves payroll judgment and gives settlement managers a consistent review package before the team issues pay.
How a Driver Settlement Calculates Net Pay
Each settlement period must account for every dollar earned, withheld, and reimbursed. The governing calculation is gross earnings minus total deductions plus reimbursements equals net settlement pay.
Choose the Contractual Pay Basis
The gross-earnings calculation depends on the driver's agreement and the type of hauling work. The governing agreement determines which pay basis applies:
Cents per mile (CPM): Multiply paid miles by the agreed rate. The agreement must identify whether the carrier uses practical, HHG, hub, loaded, or empty miles; odometer miles are not automatically the pay basis.
Percentage of revenue: Apply the driver's percentage to gross load revenue. For leased owner-operators paid this way, the carrier must provide the rated freight bill or equivalent shipment documentation at or before settlement.
Hourly pay: Common for local work, waiting time, site work, or short-haul assignments. Match time records to the correct truck, project, and shift.
Per-load or flat-rate pay: Each accepted load earns a set amount. The settlement must reconcile the driver's submitted count with dispatch and delivery records.
Per-ton pay: Common in aggregate, paving, excavation, and heavy-civil hauling. The calculation multiplies accepted ticket quantity by the configured rate for the material, route, truck class, project, or broker agreement.
The selected basis must match the governing agreement and accepted source records.
Itemize Deductions and Reimbursements
Gross earnings may also include detention, layover, stop pay, fuel surcharge, safety bonuses, or other accessorial pay. Deductions can include fuel-card charges, cash advances, equipment payments, insurance chargebacks, escrow contributions, permits, or taxes when applicable. Reimbursements cover approved driver-paid costs such as tolls, scale tickets, permits, or unloading charges.
The final statement should identify the settlement number and period, driver classification, and each paid load or haul ticket. It should also show the pay calculation, itemized deductions, reimbursements, pending loads, carry-forward balances, and net pay. A summary can sit at the top, but it should never replace the supporting detail.
Why Settlement Accuracy Matters on Built-World Projects
Scrutinize settlement accuracy whenever opaque calculations could create disputes, because driver pay is personal even when the final total is technically correct. Pay discrepancies are a recurring complaint among drivers, and an opaque statement turns a single mismatched ticket into a dispute about trust. A settlement that shows the ticket, quantity, rate, deduction basis, and approval status gives the driver and payroll team the same record to review.
Protect Project Costing
A haul ticket assigned to the wrong phase code distorts job costs even when the driver is paid correctly. If project staff assign an aggregate ticket to the wrong phase code, they may still pay the driver correctly while the job-cost report is wrong. If they duplicate the ticket quantity, they can overstate both driver pay and material quantities. If a truck broker's roster is stale, the settlement team may issue the settlement under the wrong owner-operator agreement.
Apply Lease Controls by Classification
Driver classification determines whether lease requirements apply. For owner-operators operating under a lease subject to 49 CFR § 376.12, the lease must specify chargebacks. The carrier must provide supporting freight-rate information for percentage-based settlements and handle required payment documentation under the regulation. The Truth-in-Leasing rules also require accounting for escrow deductions or additions. Project teams should apply these provisions only to drivers and construction subcontractors whose classifications and contract terms require the controls.
Check Public-Work Records
Public work can add certified payroll and prevailing-wage requirements, plus disadvantaged-business-enterprise requirements. Truck-rental-rate or monthly trucking-report requirements may also apply. Those records must remain tied to the correct project, date, driver, truck, and hauling company. Automated checks can surface missing fields, but project teams still need qualified payroll or compliance personnel to decide whether a record satisfies the applicable contract and jurisdiction.
Preserve Cost Visibility
Accurate settlements also improve cost visibility. Labor and hauling costs feed job-cost forecasts and equipment decisions. They also feed subcontractor accruals. A settlement workflow that preserves the connection between the source ticket and the accounting entry makes it easier to explain a variance before month-end rather than reconstructing it afterward.
Where Settlement Errors Enter the Workflow
Trace the source records when project teams must reconstruct the chain of evidence after the hauling work is complete. The recurring bottlenecks are usually identifiable before automation begins.
Find Source-Record Failures
Paper and electronic haul tickets create the first problem, often carrying forward a gap that started with how the load plan itself was built. A ticket may show the material, gross and net weight, truck number, timestamp, and delivery location but omit the job or cost code the ERP requires. Handwritten truck numbers can be difficult to interpret, and a replacement truck may appear under a dispatch record created for different equipment. Paper ticket processing can organize the inputs, but unreadable or incomplete tickets still need field confirmation.
Map Pay-Rule Variation
Pay-rule variation creates the next bottleneck. One broker agreement may pay by ton, another by load, and a company driver may receive hourly pay plus waiting time. Payroll and contract managers must explicitly map rate effective dates, minimum-load provisions, overtime rules, material classes, and owner-operator percentages. An automated workflow should not infer a new pay basis merely because a historical spreadsheet used it once.
Correct the Entire Record Chain
Manual correction then compounds the workload. A missed ticket or duplicate fuel deduction affects the settlement statement, job-cost entry, broker invoice, and potentially a project quantity report. Fixing only the net-pay total leaves the underlying records inconsistent. The correction workflow needs to update or route every affected output while retaining an audit trail.
Maintain Integration Mapping
Data integration is the final recurring drain. Dispatch logs, scale-house exports, emailed tickets, spreadsheets, accounting systems, and construction platforms each hold part of the record. Even when imports exist, truck IDs, driver names, vendor numbers, project codes, and units of measure may not align. Integration mapping requires ongoing implementation work.
Five Checks Before Issuing a Construction-Hauling Settlement
The five checks below apply when teams compare and assemble records across connected project files and enterprise systems. Spreadsheets and databases may also hold those records. Search tools can query connected spreadsheets, documents, databases, and web pages to deliver quick, structured answers, while the five checks below keep human approval at the center of disputed pay and unusual deductions.
Step 1: Validate Tickets, Dispatch Records, and Project Codes
Start here when ticket quantities, dispatch records, and the driver's submitted load count disagree. Inputs may include paper or electronic haul tickets, spreadsheet exports, emailed attachments, and records in construction and accounting systems.
Assemble each trip using stable fields for the driver, truck, broker or carrier, project, and cost code. Also include the material, quantity, unit, origin, destination, and timestamp. Compare ticket numbers for duplicates, flag missing job codes, and route records with unmatched truck or driver IDs for review. Structure scanned project files for comparison rather than re-keying them into a settlement spreadsheet.
AI agents can interpret connected records, compare stable fields, detect duplicates, and route unmatched IDs without deciding that an unreadable ticket is valid.
Confidence alone cannot validate a blurred ticket, handwritten correction, or missing scale-house record. Set a review threshold and require field confirmation when the source does not establish the payable quantity.
Step 2: Apply the Configured Pay Basis
A single settlement cycle often mixes mileage, percentage, hourly, per-load, and per-ton agreements. Select the configured rule based on driver classification, agreement, project, route, material, equipment, and effective date, then show the calculation beside the source record.
For per-ton work, that means accepted tons multiplied by the applicable rate. For per-load work, it means validated loads multiplied by the flat amount. CPM requires the designated mileage basis, while percentage pay requires verified gross revenue and the contractual percentage. Hourly pay requires approved start, stop, waiting, and overtime records.
Payroll and contract managers must approve the rule table, effective dates, rounding method, minimums, and precedence when agreements overlap. Historical corrections can inform future routing, but they should not silently rewrite compensation terms.
Step 3: Verify Deductions and Compliance Records
Every fuel advance, insurance chargeback, equipment payment, escrow contribution, and damage deduction needs this check before it reaches the payable total. Compare the proposed deduction with the driver's agreement, supporting transaction, prior balance, and project or truck assignment. Move missing authorizations or duplicate charges to an exception queue instead of the payable total.
For public projects, the same workflow can check whether required project codes, driver classifications, trucking reports, or prevailing-wage records are present. Compare settlement project files against a configured audit checklist and flag gaps before the designated reviewer approves the pay package. Datagrid's Audit Agent can run that comparison against the checklist the payroll team supplies and flag compliance gaps for review.
Automated checks can enforce rules the project team supplies, but payroll, legal, or compliance personnel must determine which lease, labor rule, and public-contract requirement applies.
Step 4: Route Exceptions With the Supporting Evidence
Route the exception once the financial impact or source conflict exceeds the team's approval threshold. Route the exception with the raw ticket, dispatch record, agreement clause, prior settlement entry, proposed calculation, and affected project code shown together.
AI agents can assemble the review package and route it by exception type while the designated reviewer decides whether to approve, correct, or reject the proposed calculation.
Reviewers can approve the calculation, correct a mapped field, reject a deduction, or request missing evidence. Record the final decision, timestamp, reason, and changed values so the next audit doesn't depend on an email thread.
Thresholds set too tightly create false-positive noise; thresholds set too loosely let material exceptions pass. Review the queue regularly and adjust routing by exception type.
Step 5: Generate the Statement and Settlement Summary
Assemble the statement only after every required source record and material exception carries an approval status. Assemble the itemized statement with load or ticket detail, gross earnings, accessorials, deductions, advances, reimbursements, carry-forward items, and net settlement pay.
The summary should show the current deposit or payment amount, pay basis, and settlement period. It should also show open items and year-to-date totals. Structured outputs should preserve the project, cost code, vendor, truck, and quantity fields. Accounting and job-cost reviewers need those fields. Use dashboards to show settlement status, unresolved exceptions, and hauling-cost trends without substituting estimates for approved pay. A designated payroll or settlement manager should confirm the control totals and release the settlement through the organization's established payment workflow.
Automate Driver Settlement With Datagrid's AI Agent
Datagrid's AI agents can consolidate haul tickets, agreements, and accounting records across your connected systems and prepare a settlement package your payroll team can approve:
Trip assembly from source records: Build each trip from stable driver, truck, broker, project, and cost-code fields drawn from paper tickets, scale-house exports, emailed attachments, and project files.
Duplicate and gap detection: Compare ticket numbers for duplicates, flag missing job codes, and route unmatched truck or driver IDs before they reach the payable total.
Configured pay-basis application: Apply the approved rate table by classification, agreement, project, route, material, and effective date, and show the calculation beside the source record.
Deduction verification: Match each proposed fuel advance, chargeback, equipment payment, or escrow contribution to the agreement, supporting transaction, and prior balance.
Exception packages for review: Assemble the raw ticket, dispatch record, agreement clause, prior settlement entry, and proposed calculation into one routed review item.
Statement and summary generation: Produce the itemized statement and settlement summary with project, cost code, vendor, truck, and quantity fields preserved for job-cost review.
Payroll and settlement managers still decide disputed quantities, unusual deductions, classification questions, and when the control totals are ready to release.
Pilot the workflow with one pay group or project, and document the pay basis, required ticket fields, deduction authority, exception thresholds, and final approver before expanding it. Get started with Datagrid and run one closed settlement period through it alongside your existing process to compare what each pass caught.
Frequently Asked Questions About Driver Settlement
These are the questions payroll and settlement teams ask when a driver's pay run must reconcile against haul tickets, deductions, and compliance records before approval.
What Is a Driver Settlement Summary?
A driver settlement summary is the top-level view of the itemized statement. It shows the current payment amount, pay basis, settlement period, open items, and year-to-date totals. The underlying ticket detail remains the record used to verify those totals.
How Should Mismatched Haul Ticket Counts Be Handled?
Follow Step 1 by comparing ticket numbers and stable trip fields with dispatch and delivery records. Route unresolved or unreadable records for field confirmation before approving pay.
What Evidence Should Accompany a Disputed Deduction?
Use the Step 3 review package, including the driver's agreement, supporting transaction, prior balance, relevant agreement clause, proposed calculation, and project or truck assignment. Unverified charges belong in the exception queue.
Who Should Approve a Driver Settlement Before Payment?
A designated payroll or settlement manager should confirm the control totals and release payment. Payroll, legal, or compliance personnel should review disputed deductions and questions about the applicable lease, labor rule, or public-contract requirement.
