Freight Accessorial Revenue Reconciliation: A Data Method

Accessorial reconciliation links a requested charge to a documented event and its final disposition. The key distinction is between eligible, billed, accepted, disputed, and collected amounts.

Methodology

Create an event register with load ID, appointment, arrival and departure evidence, rule or contract reference, request date, amount, customer response, invoice status, and collection date. Keep the original source document and record any correction.

Findings

Stage	Example control
Eligible	event meets the stated rule
Requested	support sent to customer
Billed	invoice line created
Accepted	customer did not reject or acknowledged
Collected	cash matched to invoice

Fuel and freight indicators may explain operating pressure, but they do not prove a particular accessorial. Internal event evidence is the commercial record.

Operational interpretation

Review the exception queue weekly by customer, reason, and age. Escalate disputed terms and approval decisions to the contract or finance owner. A support team can prepare packets without changing rates or promising payment.

Limitations

Contract terms vary and some event evidence is unavailable. Customer portal statuses may lag bank settlement. Requested amounts can overstate realizable revenue.

Research design

The unit of analysis is one accessorial line attached to one shipment, invoice, or credit memo. The population should be all delivered loads in a defined geography and period, not only the loads where a charge was requested. That denominator permits three separate measures: the share of eligible loads with an accessorial event, the share of submitted lines accepted, and the dollars collected per delivered load. Keep line-haul revenue, accessorial revenue, and credits separate. A total invoice cannot show whether a charge was earned, waived, duplicated, or reversed.

For each line retain the load identifier, customer, event type, event timestamp, location, appointment version, notice timestamp, contractual trigger, supporting document, submitted amount, accepted amount, rejection reason, dispute date, collection date, and reviewer. A signed detention sheet can establish that time was recorded; it does not establish the agreed free time or rate. A lumper receipt can support a reimbursement claim; it does not prove that the customer is responsible. Evidence and entitlement are different fields.

Findings from authoritative context

FMCSA safety and registration materials describe the regulatory record around carriers, while BTS and FHWA materials describe freight flows and performance measurement. Those sources support disciplined identification of the movement and its operating context. They do not publish a universal accessorial price or a national acceptance rate. Contract language, shipper instructions, appointment records, and the carrier's own ledger remain the controlling evidence for a specific charge. This distinction prevents a public freight statistic from being misused as a billing rule.

Reconcile the population in four passes. First, match every delivered load to its invoice status. Second, compare appointment and gate events with the claimed trigger. Third, match each submitted line to a contract or rate-confirmation provision. Fourth, match accepted dollars to the remittance and general ledger. Report unresolved lines by reason rather than silently dropping them. A high rejection share may indicate weak evidence, a misunderstood trigger, a customer policy, or a legitimate dispute; the ratio alone cannot choose among those explanations.

Practical measures and limitations

Use a median days-to-resolution measure for disputed lines, plus a 90th percentile and an unresolved-over-30-days share. Segment by customer, facility, accessorial type, equipment, and appointment window only when each segment has enough observations. Preserve canceled appointments and customer-caused reschedules as explicit categories. Do not label a missing timestamp as zero time. When systems are corrected, retain the original value, corrected value, correction reason, and editor so a later review can reproduce the published result.

This method transfers to owner-operators and larger fleets, but the interpretation changes with contract complexity and system maturity. A manual spreadsheet can support a small sample; it becomes fragile when one shipment has multiple stops, currencies, or overlapping claims. Public sources can give context on freight activity, but cannot validate a carrier's commercial entitlement. The bounded conclusion is that accessorial revenue is measurable when the population includes eligible loads and each line is linked to a dated event, contract rule, evidence record, and settlement outcome.

Worked interpretation

An accessorial acceptance rate can rise because evidence improved, because the customer mix changed, or because fewer difficult lines were submitted. Compare submitted lines with all eligible loads and show the number of lines in each stage. A customer with a lower acceptance percentage may still produce more collected dollars per delivered load if its events are larger or better documented. A line that is accepted but later credited should remain visible as a reversal rather than being counted as permanent revenue.

Use a versioned contract field and a separate interpretation field. The contract field records what the document says; the interpretation field records the analyst's reading and confidence. If two documents conflict, preserve both and escalate the conflict. This protects the research from turning a clerical reconciliation into an unauthorized change to a commercial term. It also makes later sampling possible: a reviewer can select accepted, rejected, credited, and unresolved lines and inspect the same evidence.

Additional limitation

The same event can support different commercial outcomes under different customer agreements. Therefore the analysis should preserve the governing document and refrain from presenting a collected-dollar ratio as an industry entitlement. Revisions and credits belong in the period where they are recorded, with a link back to the originating line.

Reporting standard

Show the eligible-load denominator beside every accessorial ratio. Report submitted, accepted, credited, rejected, and unresolved amounts separately, with a cutoff date and document version. This prevents a successful collection queue from being confused with entitlement and lets a later reviewer trace a result back to the underlying load population.

Reproducibility note

Freeze the eligible-load file, line-item extract, contract version, remittance, and correction log at the reporting cutoff. Re-run accepted and collected measures after credits or reversals without deleting the original state. This makes the analysis useful for audit and prevents a later portal update from rewriting the historical result.

Interpretation across customers

Customer comparisons require the contract version and document rule in force during each period. A carrier may appear to recover fewer accessorials after a rule change simply because unsupported categories are no longer submitted. Conversely, a new portal may increase the recorded volume without changing the underlying events. Preserve the old and new definitions, and show a bridge when the series changes. Do not backfill a new category into historical records unless the source evidence actually exists.

Review unmatched records as a sample, not only as a total. Select records from each status and inspect whether the missing item is a document, an identifier, a customer response, or a contract interpretation. That classification distinguishes a capture problem from a commercial disagreement. Report the review method and sample size. The result is more useful when readers can see which part of the reconciliation is observable and which part remains unresolved.

The safest operational inference is narrow: linked freight records can reveal where an accessorial claim lacks support or where an invoice line does not reconcile to the claim register. They cannot turn an incomplete packet into a validated receivable. Keep the evidence trail available to the authorized finance or claims reviewer, retain revisions, and state the reporting cutoff. This preserves the difference between research about records and a decision about collection.

Sources

1. FMCSA Cargo Claims
2. 49 CFR Part 370
3. BTS Freight Facts
4. BTS FAF
5. FHWA Freight Management
6. FMCSA SAFER
7. EIA Diesel
8. BLS PPI
9. Census CFS
10. SBA finance management

Evidence matching and denominator design

An accessorial observation should be anchored to one shipment or invoice line, with a stable load identifier carried through the supporting record. The minimum evidence set normally includes the rate confirmation, appointment or gate timestamps, signed delivery record, customer rule, invoice line, and any approval or dispute note. A revenue total without those links can show that billing occurred, but it cannot show whether the charge was supported, duplicated, omitted, or later reversed. Keep approved, rejected, pending, and not-submitted claims in separate states.

Calculate rates using the population that could reasonably produce the accessorial, not all loads by default. Detention requires an appointment and arrival record; layover may require a documented release or rescheduling event; lumper reimbursement requires a receipt or customer instruction. If the denominator includes loads lacking the relevant opportunity, the apparent recovery rate becomes difficult to interpret. Publish both the eligible count and the count with complete evidence. Missing documentation is a data-quality result, not a zero-dollar outcome.

Compare like periods only after checking changes in customer mix, contract language, and document capture. A higher billed amount can result from more eligible events rather than better recovery. A lower amount can reflect fewer loads or a changed rule. The bounded conclusion is that reconciliation can establish whether recorded accessorial claims agree with their supporting freight evidence; it cannot by itself establish that a customer owes a disputed amount or that a billing practice is contractually enforceable.