Transportation SOX Compliance Consulting

Under ASC 606, a carrier or logistics provider recognizes freight revenue as the performance obligation — moving the shipment from origin to destination — is satisfied. For truckload and less-than-truckload carriers, industry practice generally recognizes revenue over the transit period as control of the shipment transfers to the customer in transit, rather than waiting for delivery confirmation, which means a shipment in progress at period-end has to have its revenue split between the current and next reporting period based on relative transit time or distance completed. Getting that cutoff calculation wrong — recognizing full-trip revenue at pickup, or deferring it entirely until proof-of-delivery is scanned — is one of the most common restatement triggers in the industry, because the error compounds across every shipment in transit at every period close, not just a handful of large contracts.

The control that actually prevents misstatement is a systematic, TMS-driven allocation: the dispatch and tracking system knows origin, destination, planned transit time, and current shipment status, and that data has to drive an automated in-transit revenue split rather than a manual estimate assembled from a shipment-status report pulled at month-end. Carriers running multiple service types — truckload, LTL, brokerage, intermodal — often need separate cutoff logic for each, since a brokerage load where the company is an agent rather than principal has a different revenue recognition and gross-versus-net presentation question under ASC 606 than an asset-based truckload move the carrier operates directly.

A transportation company's balance sheet is dominated by revenue equipment — tractors, trailers, railcars, or vessels depending on mode — and the recurring accounting judgment is whether a given expenditure on that equipment extends its useful life or increases its capacity (capitalize) versus simply restores it to previously expected performance (expense as repairs and maintenance). An engine overhaul, a major transmission replacement, or a trailer refurbishment sits close enough to that line that inconsistent treatment across a large fleet — thousands of units serviced by dozens of maintenance shops or third-party vendors — can misstate both the balance sheet and current-period maintenance expense in ways that are individually immaterial but cumulatively significant.

The SOX-relevant control is a documented capitalization policy with clear dollar and life-extension thresholds, applied consistently by whoever codes maintenance invoices — often a fleet maintenance system separate from the ERP — and reviewed periodically for accounts where actual practice may have drifted from policy. Depreciation methodology adds a second layer: many carriers use component depreciation for major assemblies (engine, drivetrain) with different useful lives than the chassis, and a control that verifies component-level depreciation schedules tie to the fixed-asset subledger, rather than trusting that a maintenance-system capitalization flag was applied correctly at the point of data entry, is what auditors look for in a mature fleet-capitalization control.

The transportation-management system calculates the freight rate, applies accessorial charges (detention, layover, fuel surcharge, lumper fees), and generates carrier settlement amounts before any of that data posts to the financial ERP — which makes the TMS-to-ERP interface a control point in its own right, structurally identical to the billing-to-ERP boundary in other high-transaction-volume industries. Interface failures here — a dropped settlement batch, a duplicate accessorial charge, a fuel-surcharge rate-table error that misapplies an outdated index — misstate revenue and cost of transportation even when the TMS and the ERP are each individually functioning correctly. The controls that matter are batch completeness reconciliation (settlement counts and dollar totals tied between TMS and ERP for each posting cycle), an accessorial-charge exception report reviewed against contract terms, and restricted, logged access to fuel-surcharge index configuration, since an unauthorized or erroneous rate-table change misstates cost of transportation across every affected load until caught.

Layered on top of the operational interface risk is fuel-hedge accounting: carriers with meaningful diesel exposure often use commodity swaps or collars to manage fuel-price volatility, and those derivative instruments fall under ASC 815, which requires the hedge relationship to be formally documented at inception, tested for effectiveness on an ongoing basis, and marked to fair value with the offsetting entries determined by whether hedge accounting treatment has been achieved. A SOX programme has to test that the hedge-documentation control exists at trade inception (not reconstructed after the fact), that effectiveness testing is performed on the schedule the accounting policy requires, and that a failed effectiveness test triggers the correct de-designation and income-statement treatment rather than being carried forward as if the hedge relationship were still intact.