Meet Dex Live
Freight document processing that files paperwork on the right load
Dex is the Document agent. Drop a file on a load and Dex works out what it is, a BOL, a POD, freight photos, a packing list, a signed rate con, and files it where it belongs. The checkpoints read it from there.
Every FreightVero agent drafts. A person on your team approves anything that changes a load or reaches a customer or carrier.
Short answer
Dex is the Document agent in the FreightVero TMS. Drop a document on a load and Dex reads it and works out what it is: a carrier rate confirmation, a signed rate confirmation, a BOL, a proof of delivery, freight photos, a packing list, an invoice, a W9, a certificate of insurance. Supporting documents attach to the load they belong to. They never create a load. Only a rate confirmation or a delivery order does that, and only after a person confirms the draft. The documents Dex files are what the checkpoints run on.
The job today
Paperwork shows up from every direction. Drivers text phone photos of the signed bill of lading. Carriers email PODs a day late with the load number missing. Forwarders send packing lists that belong to a shipment already on the board.
Someone has to open each file, work out which load it belongs to, rename it, upload it and check that it’s the right document. When it’s wrong, billing finds out days later. The POD has no signer name, or the BOL belongs to a different load.
Bill of lading OCR tools turn a scan into text. The harder part on a brokerage desk is deciding what the document is, which load it belongs to, and whether it gives that load what it needs next. That’s the part Dex does.
How Dex works on a load
Read it and name it
Dex reads the file you dropped and works out what it is. A carrier rate confirmation, a signed rate confirmation, a BOL, a proof of delivery, freight photos, a packing list, an invoice, a W9, a certificate of insurance.
File it on the load it belongs to
A supporting document attaches to its load and nothing else happens. It never creates a load. Only a rate confirmation or a delivery order creates one, and only after a person confirms what was read.
Open Freight On Board
The checkpoints run on documents, and this is the part worth spelling out. A load can’t move to Freight On Board without a BOL and freight photos on it. Not a note, not a promise from the driver. The documents.
Close out Delivered
A load can’t be marked Delivered without a POD and the signer’s first and last name. A blank signer field stops the load where it is, while the carrier can still fix it.
Clear billing under the booked terms
A load can’t be invoiced until that customer’s own paperwork rules are satisfied. Those rules are copied onto the load when it’s booked, so a load is billed under the terms it was booked under, not under whatever the rules changed to last month.
What Dex holds, and where a person stays in control
A signed rate con marks itself
Upload a signed carrier rate confirmation and that version is marked signed. There’s no button to click. The system records which version was signed and when, which is what you want the first time a carrier argues about a rate.
Rate con versions don't move
A rate confirmation version can’t be edited or deleted. If the rate changes, the new version needs its own signature, because the carrier agreed to the old numbers.
Your own BOL doesn't count
A BOL your brokerage generates itself can’t satisfy the Freight On Board checkpoint. The carrier’s signed BOL is what counts.
Phone photos go up as they are
Photos from an iPhone upload as they are, HEIC included. Nobody converts a file or emails it to themselves first.
Private storage, links that expire
Every document sits in private storage and opens through a short-lived signed link. Carrier paperwork stays off customer-facing email automatically, so a rate con doesn’t ride along on an update to the shipper.
The audit log holds
Every document event lands in the audit log with who did it and when. The log is append-only, so it holds against the app, against an admin, and against anyone with a database connection.
What week one looks like
Book a load in the FreightVero TMS and that customer’s paperwork rules ride along with it. Your carrier signs the rate con, somebody uploads it, and that version is marked signed with a timestamp nobody had to enter.
At the dock the freight photos and the carrier’s signed BOL land on the load, and Freight On Board opens. At delivery the POD goes up with the signer’s first and last name, and the load moves to Delivered. The billing queue then shows it ready to bill, or names the document it’s short. Your team confirms the matches. The checkpoints are enforced in the database, so a load doesn’t skip one because someone was in a hurry.
Run it on your own freight
Send a load’s worth of paperwork. The rate con, the BOL, the phone photos, the POD. We’ll run it through and show you where each one lands and what your billing queue would have caught.
Frequently asked questions
Is this bill of lading OCR?
Reading the text is one step. Dex also works out what the document is, files it on the load it belongs to, and puts it where the checkpoints can read it. A plain OCR tool hands your team text and leaves the filing to them.
Which documents does it handle?
Carrier rate confirmations and signed rate confirmations, delivery orders, BOLs, PODs, freight photos, packing lists, invoices, W9s and certificates of insurance. Supporting documents attach to a load. Only a rate confirmation or a delivery order creates one, and only after a person confirms.
Can it check a POD before billing?
The Delivered checkpoint needs a POD and the signer's first and last name, so a load with a blank signer stops there while the carrier can still fix it. Billing then checks that customer's own paperwork rules, the ones copied onto the load when it was booked.
Can someone change a rate con after the carrier signs it?
No. Versions can't be edited or deleted. A rate change gets a new version, and that version needs its own signature. The load keeps a record of which version was signed and when, and every document event is in the append-only audit log.
Does it send invoices?
No. Dex files paperwork, it doesn't bill. The billing queue shows which delivered loads are ready to invoice and which are short a document. QuickBooks Online is a planned integration.
