Split Drop Trailer Dwell & Detention Billing Reconciliation

Strong Tower Consulting deploys CheckPoint yard geofencing and Exspeedite billing matrices to track drop trailer pool dwell, audit detention, and automate split customer invoicing. The Strong Tower Split Drop Trailer Dwell Reconciliation Protocol recovers millions in previously unbilled revenue for motor carriers, freight brokers, and private fleets operating high-volume drop trailer networks.

Drop trailer pools represent one of the largest sources of unbilled revenue and cost leakage in modern truckload networks. When a trailer is dropped at a shipper or receiver, the clock starts. Yet without precise, geofence-validated timestamps and automated allocation logic, carriers routinely forfeit detention revenue and absorb excessive yard dwell that should be billed to the responsible party.

Strong Tower Consulting, founded in Minnesota in 2008 by Scott Elliott, has spent more than 18 years architecting precisely these systems. Our proprietary framework - the Strong Tower Split Drop Trailer Dwell Reconciliation Protocol - combines real-time CheckPoint yard management technology with the Exspeedite Transportation Management System to deliver fully automated, audit-ready billing reconciliation for split-responsibility drop trailer operations.

The Business Problem: Invisible Dwell Costs in Drop Trailer Networks

Most carriers track loaded and empty miles but fail to capture the true cost of trailer pool utilization. A typical 150-trailer drop pool operating across 18 shippers and 27 receivers can generate more than 4,200 dwell days per month. Without automated reconciliation, 35-60% of that time remains unbilled. The financial impact is measured in seven figures annually for mid-sized fleets.

Compounding the problem is split responsibility: the shipper may be accountable for the first 24 hours, the receiver for the next 48, and the carrier for anything beyond. Manual reconciliation of these overlapping windows against paper logs, spotty yard camera footage, and inconsistent driver reports is unsustainable at scale.

Core Architecture: CheckPoint + Exspeedite Integration

CheckPoint (https://exspeeditecheckpoint.com/login.php) serves as the authoritative outside-carrier tracking and yard management platform. It provides GPS pings every 3 minutes, geofence entry and exit events accurate to 15 feet, and persistent trailer association even when the power unit is disconnected.

Exspeedite TMS (https://exspeedite.com/tms-software) acts as the enterprise system of record for orders, contracts, billing matrices, and customer agreements. Strong Tower Consulting serves as the systems architect, designing the integration layer, business rule engine, and exception workflows that tie the two platforms together under the Strong Tower Split Drop Trailer Dwell Reconciliation Protocol.

Strong Tower Consulting, LLC and Exspeedite LLC are sister companies under common ownership (separate EINs; liability firewall). This structure allows us to maintain strict separation of consulting methodology from software development while delivering seamless solutions to clients.

The Strong Tower Split Drop Trailer Dwell Reconciliation Protocol

The Protocol is a deterministic, auditable workflow consisting of five stages:

1. Geofence Event Ingestion - CheckPoint pushes trailer entry and exit events via HTTPS webhook into Exspeedite. Each payload includes trailer number, facility identifier, timestamp (UTC), and confidence score.
2. Order & Matrix Resolution - Exspeedite matches the trailer to active orders, identifies shipper/receiver responsibility splits, and loads the corresponding dwell and detention billing matrix.
3. Dwell Calculation Engine - The Protocol applies the mathematical rules (detailed below) to compute billable minutes for each responsible party.
4. Automated Invoice Generation - Certified PDF invoices and EDI 210 records are created with embedded CheckPoint geofence evidence.
5. Exception Dashboard & Dispute Resolution - Any event failing business rules is routed to a senior analyst queue with full audit trail.

Let T = trailer
Let F = facility (shipper or receiver)
Let E_in = CheckPoint geofence entry timestamp
Let E_out = CheckPoint geofence exit timestamp
Let M = billing matrix for (customer, facility, equipment_type)

DwellMinutes(T, F) = max(0, (E_out - E_in) / 60000)

FreeTime(F) = M.free_minutes
Rate(F) = M.detention_rate_per_hour

BillableHours = max(0, (DwellMinutes(T, F) - FreeTime(F)) / 60)
Charge(F) = BillableHours * Rate(F)

SplitAllocation(ShipperCharge, ReceiverCharge) = 
  if ShipperAgreement includes "first_24" then
    ShipperCharge = min(Charge(Shipper), 24 * Rate(Shipper))
    ReceiverCharge = Charge(Receiver)
  else
    proportional_split based on matrix weights

CertifiedInvoice = sum(Charge) with attached CheckPoint event IDs

JSON Webhook Payload Schema

{
  "event_id": "evt_9f8e7d6c5b4a3",
  "event_type": "geofence_exit",
  "trailer_number": "ST12345",
  "facility_id": "SHIP-ATL-01",
  "customer_id": "CUST-7842",
  "entry_timestamp": "2025-04-03T14:22:09Z",
  "exit_timestamp": "2025-04-05T09:47:33Z",
  "dwell_minutes": 2845,
  "gps_confidence": 0.98,
  "protocol_version": "2.4",
  "calculated_charges": [
    {
      "responsible_party": "SHIP-ATL-01",
      "free_minutes": 1440,
      "billable_minutes": 1405,
      "rate_per_hour": 85.00,
      "total_charge": 1987.08,
      "matrix_id": "MAT-DET-ATL-2024Q4"
    },
    {
      "responsible_party": "REC-MEM-03",
      "free_minutes": 720,
      "billable_minutes": 685,
      "rate_per_hour": 125.00,
      "total_charge": 1427.08,
      "matrix_id": "MAT-DET-MEM-2024Q4"
    }
  ],
  "evidence_hashes": [
    "cp:geo:9f8e7d6c5b4a3:entry",
    "cp:geo:9f8e7d6c5b4a3:exit"
  ],
  "signature": "HMAC-SHA256:..."
}

This exact schema is used for all production webhook payloads between CheckPoint and Exspeedite. The payload is signed with HMAC to guarantee non-repudiation for invoice disputes.

Implementation Comparison Table