← Solution examplesLogistics example · TMS ↔ Telematics ↔ AP

Accessorial & Freight Cost Intelligence

The carrier has an invoice. The TMS has the shipment. Telematics has what actually happened. We make the numbers prove themselves.

solution / accessorial-freight-cost

Engineering blueprint

LAYER 01Existing systemsIntegrated, not replaced

TMSCarrier EDI / APITelematicsYard / WMSERP / AP

LAYER 02Governed shipment dataCanonical, with lineage

TimelinesAppointmentsInvoicesRates

LAYER 03KBSIntel validation layerRules & orchestration

Contract rulesCharge validationAuto-approval

LAYER 04Decisions & intelligenceBuilt on governed data

Facility patternsCarrier disputesCost leakage

Problem

Detention, layover, and lumper charges arrive with little evidence. Checking one means pulling the TMS record, appointment, GPS data, and POD by hand, so most get paid.

Example

A carrier bills three hours of detention. Telematics shows the truck arrived 90 minutes late. The yard shows a fast turn. AP pays it anyway.

Governed object · Shipment Timeline

Tender
Appointment
Geofence arrival
Yard check-in
Dock time
Departure
POD
Invoice

Where the systems disagree

Unsupported detention
Invalid layover
Lumper mismatch
Duplicate accessorial
Contract violation
Missing POD

What we build

A validation layer between carrier billing and AP. Every charge is checked against the timeline and contract.

Shipment timelines from TMS, telematics, and yard data
Invoice and EDI ingestion
Contract and free-time rule engine
Auto-approval of clean invoices
Exception routing with dispute evidence

Controls

Validate detention, layover, and lumper charges
Detect duplicate accessorials
Enforce contract and free-time rules
Route exceptions with evidence attached

Intelligence

Detention patterns by facility
Lanes and windows that create cost
Carrier dispute evidence
Cost leakage by carrier and lane

What we'd measure

Accessorial spend by carrier and facility
Invoices auto-approved versus reviewed
Charges disputed and recovered
AP hours spent validating freight

Start with one problem. Engineer the right solution.

Manual work, systems that don't talk, data nobody trusts. We trace it to the source and ship the fix into production.