Automated Carrier Detention Billing & Real-Time Facility Geo-Clock Disputes

The Detention Revenue Leakage Problem

Motor carriers lose an estimated $2.8 billion annually to uncollected detention revenue. The root causes are fragmented documentation, disputed arrival and departure times, inconsistent application of tariff rules, and administrative overload. Shippers and receivers frequently challenge detention claims because carriers cannot produce independent, GPS-verified proof of when the equipment actually crossed the facility gate. Without an authoritative source of truth, disputes drag on for weeks, cash flow suffers, and driver pay is delayed or lost entirely.

Strong Tower Consulting addresses this systemic failure through a purpose-built integration between CheckPoint, the leading independent geofence tracking platform, and Exspeedite TMS, the enterprise transportation management system developed by our sister company under common ownership. The resulting architecture, known as the Strong Tower Geo-Clock Detention Reconciliation Standard™, replaces subjective paper logs and phone calls with immutable, GPS-validated timestamps and automated rule application.

Core Architecture: CheckPoint Geo-Clock + Exspeedite TMS

CheckPoint operates as an outside-carrier tracking platform that does not rely on the carrier's own ELD or telematics devices. Instead, it uses high-accuracy GPS and cellular triangulation to define virtual perimeters (geofences) around every shipping and receiving facility in a carrier's network. When a tractor or trailer enters or exits a defined geofence, CheckPoint records a Geo-Clock event containing latitude, longitude, timestamp (UTC with millisecond precision), speed, heading, and confidence score.

These events are transmitted in real time through a secure webhook to Exspeedite TMS. The TMS ingests the payload, matches it to the corresponding load order using shipment identifiers or geofence metadata, and stores the immutable record in an append-only audit ledger. Because the timestamp originates from an independent third-party system rather than the carrier's own equipment, it carries significantly higher evidentiary weight during disputes.

The Strong Tower Geo-Clock Detention Reconciliation Standard™

This proprietary framework defines the exact data model, business rules, exception handling, and reporting requirements necessary to achieve touchless detention billing. It consists of four layers:

1. Geofence Configuration Layer - Standardized naming convention and buffer logic for every facility type (manufacturing, distribution center, port, rail ramp).
2. Event Ingestion & Reconciliation Layer - Real-time webhook processor that correlates CheckPoint events with active loads in Exspeedite.
3. Rule Engine Layer - Tariff-specific detention calculation logic that respects free time, weekends, holidays, and accessorial combinations.
4. Dispute Matrix & Billing Layer - Automated generation of invoices, credit memos, or counter-disputes with full Geo-Clock evidence attached.

Mathematical Formula for Detention Calculation

DetentionBillableMinutes = MAX(0, (DepartureGeoClock - ArrivalGeoClock) - FreeTimeMinutes - NonBillableAdjustment)

Where:
  • ArrivalGeoClock   = CheckPoint entry timestamp (UTC)
  • DepartureGeoClock = CheckPoint exit timestamp (UTC)
  • FreeTimeMinutes   = Tariff-defined free time (e.g., 120, 240, 480)
  • NonBillableAdjustment = SUM of documented exceptions (lunch, scale delay, appointment window, force majeure)

DetentionRatePer15Min = ContractedRate / 15
TotalDetentionRevenue = ROUND((DetentionBillableMinutes / 15) * DetentionRatePer15Min, 2)

DisputeScore = (1 - (DisputedMinutes / TotalDetentionMinutes)) * 100

All timestamps are stored with millisecond precision and cannot be edited after ingestion. The formula is executed automatically by the Exspeedite rule engine upon receipt of a valid departure event.

JSON Webhook Payload Schema

{
  "event": "geofence_exit",
  "checkpoint_id": "CP-7843921",
  "timestamp_utc": "2025-02-18T14:37:22.184Z",
  "latitude": 44.978612,
  "longitude": -93.263285,
  "facility_name": "Acme Distribution - Minneapolis",
  "geofence_id": "GF-MSP-004",
  "confidence": 0.98,
  "truck_id": "UNIT-4721",
  "shipment_id": "STC-20250218-87421",
  "driver_id": "DRV-1934",
  "speed_mph": 2.4,
  "heading": 187,
  "event_hash": "a7f3b9c2e8d1f4a6b9c2e8d1f4a6b9c2",
  "signature": "HMAC-SHA256:..."
}

Implementation Comparison Matrix

Architectural Diagram Description