Solutions / Logistics and freight

AI automation for freight brokerages and carriers

The same seven facts about a load get typed into the system, then onto the bill of lading, then onto the invoice.

Volume freight moves on electronic data interchange rather than on modern interfaces. A tender goes out, a response comes back accepting or rejecting it, status messages flow during transit, and an invoice closes it. That much is standardised. Almost everything around it is not.

A rate confirmation arrives by email as a PDF, and every broker lays theirs out differently, with different labels for the same reference number and sometimes as a scan rather than as text. Extraction built against one layout breaks the day a new customer is added, which is why this is a per-partner problem rather than a general one.

The document that starts the payment clock is a signed delivery receipt photographed at a dock, frequently with glare, at an angle, with a thumb across the signature line. Reading the signature date off that image is the weakest link in the billing cycle, and a system that reports low confidence there is more useful than one that guesses.


Figure 01 / the ground

What this work runs through

Systems / commonly in place Yours may differ, and that is the point of week one
  • McLeod PowerBroker
  • MercuryGate
  • the DAT load board
  • Descartes MacroPoint
  • Samsara
  • EDI over a VAN
  • Outlook

Artefacts that move through the business

  • Load tender and the acceptance or rejection that answers it
  • Status messages, carrying event codes and timestamps
  • Rate confirmation, laid out differently by every broker
  • Bill of lading and the signed delivery receipt
  • Carrier packet carrying authority and insurance, plus any payment assignment
intake
Intake and triage
documents
Documents and records
billing
Billing and collections
follow up
Follow up and status
reporting
Recurring reporting

Figure 02 / where it breaks

The specific things that go wrong here

Status codes do not mean the same thing across carriers

One carrier sends arrival when the driver reaches the gate, another when checking in at the guard shack, another skips it and only reports completion, and some send events hours late in a nightly batch. Arrival estimates built on assumed code semantics misreport quietly.

A functional acknowledgement is not an acceptance

One message confirms the file parsed. A different message confirms the load was accepted. Treating the first as the second produces loads everybody believes are covered and nobody is hauling.

Tracking coverage has holes nobody sees until the call

The visibility provider connects to the telematics, but the driver never accepted the request, or the account is not linked, or that device vendor is unsupported. The dispatcher falls back to a phone call and types the location in by hand.

Load boards forbid what the impatient project wants

Access is gated behind subscription tiers and setup fees, and automated querying is restricted contractually as well as technically. Polling harder is not an available strategy.


Figure 03 / candidates

What we would automate, and when we would not

rate confirmation intake

Reading a rate confirmation once instead of three times

Extracting the load reference, the stops, the appointment windows and the agreed charges from a PDF that looks different per broker, and writing them once so the bill of lading and the invoice inherit rather than re-key.

Runs against McLeod PowerBroker / Outlook / EDI over a VAN

delivery proof

Getting the delivery receipt to the invoice

Chasing the missing receipt, reading what arrives, and attaching it to the right load so billing can go out.

Runs against McLeod PowerBroker / Twilio / Outlook

carrier vetting

Checking a carrier before the load is tendered

Pulling authority status, reading the insurance certificate for limits and expiry, and checking for a payment assignment, then assembling the result for a person.

Runs against McLeod PowerBroker / Outlook

detention evidence pack

Building the detention file before the charge is billed

Detention on domestic truckload is contractual, not rated by rule, so what is owed comes from the rate confirmation and nothing else.

Runs against McLeod PowerBroker / Descartes MacroPoint / EDI over a VAN

payee of record check

Confirming who the carrier payment is actually owed to

A notice of assignment on file redirects the receivable to a factoring company, and once it is properly served, paying the carrier direct does not discharge the debt.

Runs against QuickBooks Online / Outlook / McLeod PowerBroker


Constraint / why a person stays in the loop Checked against your own jurisdiction

Driving time is federally limited, recorded electronically, and structured as a daily driving limit inside a longer on-duty window after a required rest period, with a weekly ceiling on top. That is why waiting at a dock costs money and not only patience: the clock runs regardless. Brokers operate under authority that requires a surety bond on file before they may broker at all. Cargo claims carry statutory acknowledgement and resolution windows, and detention is contractual rather than rate-regulated for domestic truckload, so what is owed comes from the agreement rather than from a rule. Carrier identity verification matters more here than in most sectors, because fraudulent re-brokering under a hijacked authority leaves the broker exposed.

Related: Manufacturing Construction and contracting. Or start from the four shapes of work instead of from an industry.