Alleged Freight Revenue Hiding Exposes the Owner-Operator Settlement Data Gap

Percentage-of-revenue compensation sounds simple: collect the freight charge, apply the contracted percentage, subtract authorized expenses, and pay the owner-operator. Yet every handoff between customer billing, dispatch, document storage, and contractor settlement creates an opportunity for the numbers to diverge.

A newly filed lawsuit shows how serious that gap can become. According to FreightWaves, a proposed class of approximately 50 or more owner-operators alleges that a Michigan transportation provider understated load values before calculating contractor compensation. The complaint seeks more than $1 million in damages. The allegations have not been proven, and the defendants had not responded in the publicly accessible docket when the article was published.

The operational lesson does not depend on the outcome of that case. If customer revenue and driver pay are held in separate systems without a shared audit trail, neither management nor contractors can readily verify the settlement formula.

The settlement must begin with one shipment record

The complaint describes an agreement under which an owner-operator would receive 80% of a load's value while the provider retained 20%. It alleges that one system held actual load values while a driver-facing system showed reduced values. A hypothetical in the filing describes a $10,000 customer rate presented to the owner-operator as $7,500, with compensation then calculated from the lower figure.

That example exposes the weakness of treating settlement as an isolated accounting output. A defensible process starts with a shipment identifier that connects five records:

• The customer's accepted rate confirmation, including every revision
• The final invoice and cash received for linehaul, fuel surcharge, and accessorials
• The dispatch offer and rate information shown to the owner-operator
• Supporting documents such as proof of delivery, detention approval, and lumper receipts
• The settlement statement, formula, deductions, adjustments, and payment status

Each document should refer to the same load and version. When an invoice changes after delivery, the contractor settlement should either recalculate automatically or enter a visible exception queue. A spreadsheet export or emailed PDF should not become the only evidence of what the parties agreed.

Reconcile revenue components, not just the total

A load total can match while its components remain wrong. Linehaul may be subject to the contractual percentage while a fuel surcharge is passed through under a different formula. Detention, truck ordered not used, layover, stop-off, or handling charges may be included, excluded, or shared according to the agreement. Deductions may cover insurance, permits, advances, equipment, escrow, or chargebacks.

Build the settlement calculation at the component level. For every amount, store the payer, payee, category, source document, effective timestamp, contractual rule, and approving user. That structure makes questions answerable: Was the fuel surcharge included? Did a late customer accessorial flow through to the driver? Was a deduction authorized by the current agreement? Did an adjustment replace a prior value or merely add another line?

The risk is not theoretical. In a separate case reported by FreightWaves, 22 independent drivers reached a settlement with a carrier after alleging altered rate sheets and hidden revenue. The financial terms were not disclosed, and the case was dismissed with prejudice. One disputed load allegedly showed drivers an $8,000 rate when the carrier received $15,000. Under the drivers' claimed 88% formula, that $7,000 difference represented $6,160 in disputed compensation.

Preserve immutable rate and settlement versions

Operational rates legitimately change. A shipper may add a stop, approve detention, cancel a service, or correct a billing error. The control objective is not to prevent changes; it is to make every change attributable and reviewable.

For each rate version, preserve the old value, new value, timestamp, user or integration, reason code, and source evidence. Never overwrite the original rate confirmation. Apply the same discipline to settlements: issue version 1, then create a linked adjustment rather than silently editing history.

Access should also be deliberate. Dispatch can propose a rate change, but finance or a designated approver should authorize any post-delivery reduction. Owner-operators should be able to see the commercial basis relevant to their pay, the formula used, and all settlement revisions without gaining access to unrelated customer information.

Audit the exceptions that reveal data gaps

A settlement audit should run continuously, not only after a dispute. Flag loads when:

• Customer revenue differs between the accepted confirmation, invoice, and receipt
• The driver-facing rate does not reconcile to the contractual percentage
• A rate decreases after tender, pickup, or delivery without documented approval
• An accessorial appears on the customer invoice but not in the settlement calculation
• A deduction lacks a contract rule, receipt, or authorization
• A shipment has multiple rate confirmations but no designated final version
• A settlement is issued while proof of delivery or customer billing remains incomplete
• A manual adjustment exceeds a defined dollar or percentage threshold

Prioritize exceptions by financial exposure and age. Assign an owner, due date, resolution code, and supporting evidence. Report recurring discrepancies by dispatcher, customer, branch, contractor agreement, and integration—not to presume wrongdoing, but to find broken mappings and weak controls before they scale.

Management should monitor settlement accuracy, percentage of loads requiring manual edits, post-delivery rate-change frequency, unresolved variance value, document completeness, and time from customer adjustment to contractor adjustment. Sampling only clean settlements will miss the very records that deserve scrutiny.

Transparency is an operating control

The current allegations involve thousands of electronic communications and years of transactions, according to the complaint. Reconstructing that history from two TMS platforms, email, text messages, and settlement statements is expensive even when every participant acted properly. A unified, shipment-linked record reduces that burden and gives contractors a practical way to question a discrepancy early.

Revenue transparency is therefore more than a contractor-relations issue. It protects finance, operations, leadership, and the business itself. The best settlement process can reproduce any payment from source documents, contract logic, and preserved versions—without relying on a person's memory or an editable spreadsheet.

CXTMS connects customer rates, shipment execution, documents, accessorials, invoices, contractor pay, and exception history in one governed record. Request a CXTMS demo to see how auditable freight settlements can reduce disputes and protect owner-operator trust.