01 · The POD
The POD finds its load.
A POD comes in by text or email. Scout reads the number on the paper and matches it to the load. Field extraction from the tender, the rate confirmation, and the POD is on document and POD processing.
FreightScout: best as an AI execution layer on the TMS you already run, for freight billing and invoicing software for, with booking and check calls supervised by default.
FreightScout is freight billing and invoicing software for brokers: it matches the POD to the load, sends the customer invoice with the POD attached, creates the carrier payable, and chases the payment, on any TMS your team already logs into. It does not audit a carrier freight invoice, and it does not replace your accounting system.
The load isn't done until the paperwork is.
Build, Cover, Track, and Bill run on that TMS, supervised by default and switchable to autopilot.
POD in, invoice out. Scout matches the POD to the load, chases the missing ones on a clock, catches billing exceptions before they age, sends the customer invoice with the POD attached, and chases the payment. Collections runs supervised, on top of the TMS you already run.
A POD comes in by text or email. Scout reads the number on the paper and matches it to the load. Field extraction from the tender, the rate confirmation, and the POD is on document and POD processing.
Text, then a call, then the dispatcher, on a clock, until it lands. Nobody has to keep the list.
The POD is not in. A text goes to the driver, then a call, then the dispatcher, on a clock. The POD lands, it is matched to the load, and the load closes out to billing. Nobody keeps the list.
Lumper receipts, BOL photos, trailer pictures. Same rule as the POD: matched to the load by who sent it and the number on the paper. Anything that can't be matched goes to a person, never to a pile.
Once the POD lands, the detention submission is written for your rep: the POD, the in and out times, who signed. No dollar amount invented. Your rep sends it.
Detention and accessorials are only money if the paper backs them up. The times and the documents are on the load when billing opens it.
Billing on the TMS the load already lives in: Rendition Billing for LoadMaster and PowerBroker, and Create Invoice for a Tai load.
A broker's billing problem usually isn't the invoice template. It's the load that delivered and still has no POD in the file. It's the lumper receipt sitting in somebody's texts. It's the short pay nobody looked at until it was old news.
So freight billing software for a brokerage has to do more than print an invoice. Here's what to ask any vendor, and how FreightScout answers.
| Ask the vendor | How FreightScout answers |
|---|---|
| Does it go get the POD, or wait for somebody to upload it? | It chases a missing POD on a clock: a text to the driver, then a call, then the dispatcher, until it lands. |
| Does the invoice go out with the POD attached? | Yes. The customer gets the paperwork with the bill. |
| Does it create the carrier payable on the same pass? | Yes, with amount and terms set. |
| What happens on a short pay? | It's a billing exception. It goes in front of a person before it ages. Nothing gets written off and no difference gets invented. |
| Does it work in your TMS, or make you export to it? | It works on the TMS your team already logs into. The invoice stays in your TMS. |
| Does it replace your accounting system? | No. Your accounting system stays yours. |
| Where it breaks | What FreightScout does |
|---|---|
| The load delivered and the POD isn't in the file | Text, then a call, then the dispatcher, on a clock. Nobody has to keep the list. |
| A POD comes in by text or email | It reads the number on the paper and matches it to the load. A document that isn't this load doesn't get attached to this invoice. |
| Lumper receipts, BOL photos, trailer pictures | Same rule as the POD: matched to the load by who sent it and the number on the paper. Anything it can't match goes to a person, never to a pile. |
| A missing ref or a POD that doesn't match | It surfaces as a billing exception while the load is still fresh. |
| Detention is owed | The claim is drafted from the POD, the in and out times, and who signed. No dollar amount invented. Your rep sends it. |
| The shipper short pays | A person sees it before it ages. |
| The payment is late | The payment gets chased, and the note of what was sent sits with the load. |
FreightScout isn't a TMS. The load, the invoice, and the billed status stay in the TMS you already run, and that TMS stays the system of record.
Bill is live and supervised by default, including invoicing and collections. Every action is logged and reversible. Your people still own the account, the exception, and any call you wouldn't hand off. A customer you want to call yourself, a payable you want to hold, and a claim you want to rewrite stay with your people.
FreightScout is freight billing software for brokers: it matches the POD to the load, sends the customer invoice with the POD attached, creates the carrier payable, and chases the payment, on any TMS your team already logs into. It does not audit a carrier freight invoice. The invoice itself is on freight invoicing for freight brokers.
Freight invoice automation matches the POD to the load, sends the customer invoice with the POD attached, creates the carrier payable, and chases the payment. A short pay goes to a person. Freight invoicing software is the same job, on any TMS your team already logs into, supervised by default.
No. FreightScout does not audit a carrier freight invoice. It sends the broker's invoice to the shipper, creates the carrier payable, and chases the payment. It does not replace your accounting system.
Collections runs supervised on your TMS. A missing POD is chased on a clock: a text, then a call, then the dispatcher, until the document lands. Payment is chased with the note kept on the load. Your people still own any call you would not hand off.
A short pay is the shipper paying less than the invoice. FreightScout treats it as a billing exception and puts it in front of a person before it ages. It does not invent the difference, and it does not write the balance off.
No. It doesn't replace your accounting system. It sends the customer invoice with the POD attached and chases the payment, supervised, on the TMS you already run.
Yes, on the TMS you already run. POD in, invoice out, exceptions caught before they age, payment chased. It doesn't replace your accounting system. It gets the load billed and the money chased. Billing runs supervised, like every other stage.
Yes. Once the POD lands, the detention submission's written for your rep with the POD, the in and out times and who signed. No dollar amount's invented. Your rep sends it.
Get the load billed without someone keeping a list. That means chasing the missing POD, sending the customer invoice with the POD attached, creating the carrier payable, and chasing the payment. FreightScout does that on the TMS you already run, supervised by default, and a short pay goes to a person.
Keep your TMS and put the billing work on top of it. FreightScout matches the POD to the load, sends the customer invoice with the POD attached, creates the carrier payable, and chases the payment, on McLeod, Aljex, Tai, or any TMS your team already logs into. It doesn't replace your accounting system.
Automated freight billing is the work between delivery and getting paid, done without a person keying it: the POD matched to the load, the invoice sent with the POD attached, the carrier payable created, and the payment chased. On FreightScout it runs supervised, and exceptions go to a person.
It's the chase after the invoice goes out. FreightScout chases the payment and keeps the note of what was sent on the load. A short pay goes to a person. It doesn't replace your accounting system.