Driver Detention Recovery and Automated Invoicing

Separate facility dwell from billable detention

A tractor inside a facility polygon is an observation. Billable detention depends on the agreed terms, relevant timestamps, qualifying conditions, and supporting evidence. Store total dwell separately from the charge calculation. A system that labels every minute beyond a fixed threshold as collectible revenue overstates what the data proves.

FMCSA's research overview explains measurement limitations in separating normal loading and unloading from delay. Its research context does not establish a universal customer tariff or payment entitlement. Use the actual applicable agreement and have unresolved terms reviewed by the responsible commercial team.

This reference workflow supports consistent evidence and billing controls. It does not promise recovery or replace contract interpretation. The aim is to identify eligible charges accurately, retain the reasons, and prevent both missed billing and unsupported invoices.

Build a versioned detention rule record

Keep customer, facility scope, service type, effective dates, free-time duration, clock-start rule, clock-end rule, billing increment, rounding policy, rate, cap, authorization requirement, document requirement, and submission deadline. Record precedence between the negotiated rate confirmation, customer contract, and other applicable terms through an approved policy.

Do not make the calculation depend on whichever rate table happens to be current when the clerk opens the invoice. Attach the effective rule version to the stop. Preserve the prior result when a rule is corrected and explain whether affected charges require review.

Collect timestamps with provenance

Store appointment window, arrival observation, accepted check-in, loading or unloading events when available, release, and departure. Preserve source time, timezone or offset, receipt time, actor, source device, and evidence reference. Distinguish a driver's confirmation from a telematics estimate and a signed facility record.

Geofence data can identify candidates for review, but a queue outside a gate, adjacent facility, equipment drop, or device reassignment can change the interpretation. Use effective-dated load-to-vehicle assignments. A missing departure should create an incomplete record rather than an invoice that continues accruing forever.

Keep EDI 214 status messages linked to the underlying event ledger. An outbound status message can document what was communicated, but it does not independently establish the agreement's billable start time. Source evidence and billing eligibility remain separate records.

Calculate a candidate charge transparently

First resolve the contractual eligible start and end. Calculate elapsed time on a continuous timeline, apply allowed exclusions, subtract free time as specified, and floor a negative result at zero. Apply the agreed increment and rounding rule before multiplying by the rate, then apply any cap or approval condition. Order matters and belongs in tests.

For an illustrative test only, suppose approved terms allow 120 free minutes after accepted check-in, exact-minute billing, and a hypothetical rate of $60 per hour. If eligible time is 195 minutes with no exclusions, billable time is 75 minutes and the candidate charge is $75. These inputs are an invented test fixture, not a market rate or client result.

Show the calculation trace to the reviewer: source timestamps, duration, exclusions, free time, rounding, rate, and final amount. Use integer minor currency units or appropriate decimal arithmetic rather than uncontrolled binary floating-point rounding for invoice money.

Generate one controlled invoice effect

Use a unique key based on shipment, stop, charge type, and rule or approved charge revision. Re-running the workflow must not insert a second charge. Put approved charges in an outbox that the supported TMS or accounting integration consumes, and store the resulting invoice identifier.

Separate candidate, awaiting evidence, awaiting authorization, approved, invoiced, disputed, adjusted, and closed states. A failed accounting API request should stay retryable without returning the charge to an untracked manual spreadsheet. Match outbound EDI 210 or other invoice delivery to the approved invoice record.

A later timestamp correction should create an auditable revision. If an invoice is already sent, follow the organization's controlled adjustment or credit process rather than quietly rewriting the historical receivable. Keep the relationship between the original calculation and the adjustment visible.

Test exceptions and reconcile actual collections

Build tests for early and late arrivals, overnight stops, daylight-saving transitions, missing offsets, duplicate events, partial free time, minimum charges, caps, negative durations, missing approval, and a customer rule change. Have billing staff compare results against approved manual calculations before enabling automatic posting.

Begin in review-only mode. Track eligible candidates, evidence completeness, approved charges, invoice submission, disputes, adjustments, and collected amounts separately. An invoice generated is not cash recovered. Evaluate missed candidates as well as rejected charges so the program does not optimize only the easy cases.

Assign an operations owner for event disputes, a billing owner for calculations, and a commercial owner for customer-term questions. Preserve customer-specific access controls and a retention policy for documents. Review rejection reasons to fix evidence collection rather than increasing the assumed charge.

Frequently asked questions

Does geofence dwell automatically become billable detention?

No. Billing depends on the applicable terms, accepted timestamps, qualifying conditions, authorization, and required evidence.

Should missing departure time produce an estimated invoice?

Keep the record incomplete and route it for review unless an approved process and the applicable terms support a documented resolution.

How do you prevent duplicate detention charges?

Use a stable charge key, explicit approval states, and a controlled posting process that records the resulting invoice and any later adjustment.

Primary technical references

Reference documentation consulted October 24, 2026. Confirm current product versions and partner requirements before implementation. The architecture and test plans above are proposed design guidance rather than vendor certification or measured client results.

• FMCSA detention measurement research

Company foundation

The Strong Tower name comes from Proverbs 18:10. Our independent consulting practice helps transportation businesses align operations, systems, and data; consulting does not require purchasing affiliated software.

Related consulting practices and solutions

• Transportation accounting integration
• Event and EDI integration
• Truckload operational systems

Discuss the scope of an assessment: 763-244-1373 or [email protected].

Strong Tower Consulting, LLC and Exspeedite LLC are separately organized sister companies under common ownership.