What happens after booking?
Rate confirmation, carrier vetting, check calls, POD collection, invoicing, carrier settlement, then AR and dunning at 30/45/60 days.
Guide · Freight
Booking freight is the visible job. The invisible one — confirmations, documents, invoices, and chasing money — is where a small brokerage's margin quietly goes, and it is the part that automates best.
Every step is small. There are just a great many of them, each with a deadline, each attached to an email thread, and each capable of costing real money when it slips.
| Leak | Mechanism | Cost |
|---|---|---|
| Missing POD | Invoice cannot be sent, or is sent and rejected | Days to weeks of delay on every affected load |
| Wrong invoice format | Customer's AP system rejects or ignores it | Re-work plus a full payment-cycle delay |
| Unbilled accessorials | Detention and layover never make it onto the invoice | Pure lost margin, invisible in the P&L |
| Late dunning | Nobody chased at 30 days | Cash tied up; occasionally never collected |
| Expired carrier insurance | Not caught before dispatch | Potentially catastrophic liability |
None of these are strategy failures. They are all attention failures — the predictable result of a small team handling a high volume of small deadlines through an inbox.
The rule of thumb: automate what is repetitive, structured, and deadline-driven; keep humans on judgement and relationships.
What should stay human: negotiating rates, deciding whether to keep a difficult customer, handling a claim, and any conversation where the relationship is the asset.
Most small brokerages run on email plus a spreadsheet. It works until volume rises, and then it fails in a specific way: information exists but is not queryable. Nobody can answer "which loads are missing a POD right now" without a person reading threads. Every leak in the table above is a version of that same problem.
The fix is not necessarily new software with a login. It is turning the email stream into structured records — load, document, status, deadline — and letting something watch that structure instead of a human watching an inbox.
That is what FreightDesk AI does: it reads the billing inbox, drafts the invoice, chases the missing paperwork on a schedule, and hands a human the exceptions. The workflow-by-workflow case study — 18 AR and billing workflows — is here, and the arithmetic behind the numbers themselves is in the margin and rate-per-mile guide.
FAQ
Rate confirmation, carrier vetting, check calls, POD collection, invoicing, carrier settlement, then AR and dunning at 30/45/60 days.
Missing POD, wrong invoice format for the customer's AP system, or nobody chasing at 30 days. Each costs a full payment cycle.
The proof of delivery. Without it the invoice usually cannot even be submitted.
Read billing email, match documents to loads, draft invoices, chase paperwork on a schedule, run AR ageing, flag expiring insurance.
Rate negotiation, customer and carrier decisions, claims, and anything where the relationship is the asset.
Information exists but is not queryable. 'Which loads are missing a POD?' requires a human reading threads — that gap is the leak.