Guide · Freight

After the load books, the real work starts

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.


The lifecycle after "covered"

Every step below 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. Durations are typical for a small brokerage running email plus a spreadsheet; they are not benchmarks.

StepOwnerTypical durationFailure mode when it slips
Rate confirmation out, signed copy backBroker or ops10–30 min, same dayUnsigned rate con means the accessorial terms and free time are unagreed when you need them
Carrier vetting: authority, insurance, W-9, agreementOps or compliance12 min first time, 90 sec per load afterDispatching against expired coverage; a claim with no cargo policy behind it
Dispatch and check callsOps5–10 min per call, several per loadNo timestamps, so detention cannot be evidenced and is never billed
POD collectionOps or billingMinutes if it arrives; days to weeks if it does notThe invoice cannot be submitted at all. This is the single largest source of AR delay
Invoice generation and submissionBilling5–15 min per load, more for portal customersWrong format or missing reference, so the customer's AP system rejects it silently
Carrier settlement, direct or via factorAccountingBatch, weekly or per termsPaying the wrong party after a factoring change; double payment on a re-brokered load
AR tracking, dunning, dispute resolutionOwner or AR clerkOngoing to 30/45/60/90 daysNobody chased at 30 days, so cash arrives at 70 days instead of 45
Reconciliation and closeOwner or bookkeeperHalf a day to two days monthlyUnbilled accessorials are discovered too late to bill, or never discovered

The document matrix

Most back-office pain is a document that does not exist yet, in the hands of somebody who has no reason to hurry. Knowing who produces each one, and when it becomes blocking, is what turns chasing into a schedule instead of a panic.

DocumentWho produces itWhen it is neededWhat breaks without it
Broker-carrier agreementYou, signed by the carrierOnce, before the first loadNo anti-re-brokering clause, no insurance minimums, no indemnity
Carrier authority recordFMCSA, pulled by youAt onboarding and re-checked per loadNo evidence the carrier was authorised on the pickup date
Certificate of insuranceThe carrier's insurance agentAt onboarding, monitored to expiryNo proof cargo coverage existed on the day of loss
W-9The carrierBefore first paymentIncorrect 1099 reporting and an unverified legal entity
Notice of assignment (factoring)The carrier's factorAt onboarding and on any changePaying the carrier directly when the factor owns the receivable, and paying twice
Rate confirmation, signedYou, signed by the carrierEvery load, before dispatchThe rate, free time, and accessorial terms are all arguable later
Bill of lading, signed at pickupShipper and driverAt pickupNo record of condition or count at origin, which is the whole fight in a damage claim
Proof of delivery, signedConsignee and driverAt deliveryThe invoice usually cannot be submitted at all
Lumper receiptThe facilityAt the dock, in the momentAn unrecoverable pass-through cost, because reimbursement requires the receipt
Check-call log with timestampsYou, continuouslyThroughout the loadDetention is unbillable because arrival and departure cannot be evidenced
Customer invoice with attachmentsYouPer customer terms after deliveryNothing to age, nothing to chase, no receivable
Accessorial backupYou, from timestamps and receiptsWith the invoiceAccessorial lines get short-paid because they are unsupported

Where the money actually leaks

LeakMechanismCost
Missing PODInvoice cannot be sent, or is sent and rejectedDays to weeks of delay on every affected load
Wrong invoice formatCustomer's AP system rejects or ignores itRe-work plus a full payment-cycle delay
Unbilled accessorialsDetention and layover never make it onto the invoicePure lost margin, invisible in the P and L
Late dunningNobody chased at 30 daysCash tied up; occasionally never collected
Expired carrier insuranceNot caught before dispatchPotentially catastrophic liability
Missing lumper receiptPass-through cost cannot be substantiatedThe full lumper amount, absorbed
Duplicate carrier paymentFactoring change not trackedThe entire carrier pay, twice

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 margin arithmetic that these leaks eat into is worked through in the margin and rate-per-mile guide.

Accessorial capture, worked

Accessorials are the clearest case of money that is already earned and simply not collected. Detention is the most common, and it is lost for one reason: nobody recorded the two timestamps that prove it. Here is the arithmetic on a single illustrative load.

ILLUSTRATIVE LOAD - detention at delivery Appointment time 14:00 Driver arrival (check call) 13:48 Checked in at gate 14:05 Departed loaded/empty 19:40 Clock starts at the later of appointment and arrival = 14:00 Time on site = 19:40 - 14:00 = 5h 40m = 340 minutes Free time per rate confirmation = 2h 00m Detention time = 340 - 120 = 220 minutes Billed in completed 15-minute increments: 220 / 15 = 14.67 → 14 increments = 3.50 hours Customer detention rate $60/hr → 3.50 x 60 = $210.00 Carrier detention rate $50/hr → 3.50 x 50 = $175.00 Margin on the accessorial = $35.00 Daily cap per rate con $360 → not reached

Now the part that matters. Illustrative monthly arithmetic on a brokerage running 40 loads a month: suppose 6 of them incur detention, and 4 of the 6 go unbilled because the timestamps were never captured. That is 4 × $210 = $840 of customer billing gone, and 4 × $35 = $140 of pure margin gone, every month. Annualised, the margin alone is $140 × 12 = $1,680, and the billing is $10,080 that should have been collected and passed through.

The whole detention question is decided by two timestamps recorded at the time, not reconstructed afterwards. A check-call log is not administrative overhead — it is the evidence file for every accessorial you will ever argue about. The full mechanics of detention, demurrage, and the rest sit in the accessorials guide.

Which lines are billable, how free time is normally defined, and where demurrage differs from detention are covered in the detention and accessorials guide, and the calculators are free on the freight tools page.

AR ageing, and what to actually say in each bucket

Dunning fails for a stylistic reason more often than a commercial one. Early messages that sound like collections damage the relationship; late messages that sound apologetic get ignored. The escalation should be visible in the language, and the language should be written down once so it does not depend on whoever is having a bad week.

BucketStatusChannelOpening lineEscalation
0–15 daysCurrentNoneNo contact neededConfirm receipt only if the customer uses a portal that can silently reject
16–30 daysApproaching termsEmail, automatedQuick confirmation that invoice 10482 is in your system and scheduledNone. This is a receipt check, not a chase
31–45 daysPast termsEmail, named senderInvoice 10482 is now past the agreed 30-day terms. POD and rate confirmation are attached again for convenienceAttach the backup pre-emptively. Half of these are a missing-document problem
46–60 daysAgedEmail plus phone callFollowing up on invoice 10482, now 52 days out. Can you confirm the approval status and who it is sitting withAsk for a name and a date, not a promise. Get the AP contact
61–90 daysSeriously agedPhone first, email to confirmWe need to resolve invoice 10482, 74 days outstanding. Is there a dispute we have not been told aboutOwner-to-owner contact. New loads move to prepay or hold
90+ daysAt riskFormal written noticeFormal notice regarding invoice 10482, outstanding 96 daysCredit hold, then third-party collections or legal. Decide the threshold in advance, in writing

Two rules. Never let the first contact be a chase — a confirmation email at day 20 catches the silent-rejection cases while everyone is still friendly. And decide the credit-hold threshold before you have a customer sitting at 80 days, because in the moment the pressure is always to take one more load from someone who owes you money.

What days sales outstanding is actually worth

DSO is the average number of days between invoicing and getting paid. Every day of it is cash you have already earned, funded out of your own pocket, while you still have to pay carriers on much shorter terms. Here is the arithmetic, on illustrative numbers.

ILLUSTRATIVE BROKERAGE Customer billings $250,000 / month = $3,000,000 / year Revenue per day 3,000,000 / 365 = $8,219 / day Cash tied up in AR = revenue per day x DSO At DSO 52 days 8,219 x 52 = $427,400 At DSO 38 days 8,219 x 38 = $312,300 ------------------------------------------ Cash released by 14 days = $115,100 What those 14 days cost while you carry them: Financed on a line of credit at 12% APR 115,100 x 0.12 = $13,812 / year Or, if the same gap is bridged by factoring your own receivables at 2.5% 3,000,000 x 0.025 = $75,000 / year Fourteen days of DSO is not an accounting statistic. It is between $13.8k and $75k a year of real cost.

This is why POD chasing is the highest-value automation in a brokerage, and it is not close. It is not that the task is hard. It is that every day the document is missing is a day of DSO, and DSO has a price per day that most small operators have never calculated.

What automates cleanly

The rule of thumb: automate what is repetitive, structured, and deadline-driven; keep humans on judgement and relationships. That selection filter, generalised beyond freight, is the subject of the small-business automation guide.

  • Reading billing email and extracting load numbers, references, amounts, and attachments.
  • Matching documents to loads — POD to load number, rate confirmation to invoice, lumper receipt to accessorial line.
  • Drafting invoices in each customer's required format, with accessorials pulled from the timestamps already recorded.
  • Chasing missing documents on a schedule, with escalation, so nobody has to remember.
  • AR ageing and dunning — automatic at 30, 45, 60 days, with a human review before anything gets sharp.
  • Compliance expiry monitoring — insurance and authority dates flagged before dispatch, not after. The vetting side of that is in the carrier vetting checklist.
  • Detecting the silent rejection — an invoice submitted to a portal with no acknowledgement after N days is an exception worth raising.

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.

Build, buy, or automate: the decision

OptionUpfrontOngoingBest whenFails when
Do nothing, absorb the hours$0The hours, foreverUnder roughly 20 loads a month, one person, no growth intentVolume grows, or the person who holds it in their head leaves
Hire an AR or billing clerkRecruiting timeA salary, plus managementVolume is high and irregular, and exceptions dominateVolume is high but repetitive; you have hired a person to be a script
Buy a full TMSSetup, migration, trainingPer-user or per-load feesYou want one system of record and can standardise your process to fit itYour customers each demand a different invoice format the TMS does not produce
Buy point solutions and glue themLowSeveral subscriptionsOne specific step dominates the pain and a good tool exists for itYou end up with five logins and no place that answers cross-cutting questions
Automate the specific workflowsBuild hoursNear-zero per unit, plus maintenanceThe work is repetitive, structured, deadline-driven, and customer-specificThe task is genuinely judgement-heavy, or the volume does not justify a build

For most small brokerages the honest answer is a combination: a lightweight system of record, plus automation on the two or three workflows that actually consume the week. Buying a large platform to solve POD chasing is expensive, and doing POD chasing by hand at volume is also expensive; the middle is usually right.

A sequencing plan for a small brokerage

Do these in order. Each step pays for the next, and the order is chosen so that the first thing you fix is the thing with a price per day attached.

  1. Week 1 — measure. Pull the last 90 days: DSO, count of loads where the POD arrived more than 2 days after delivery, count of accessorials billed versus incurred. Roughly 4 hours. You cannot prioritise without these three numbers.
  2. Week 1 — make load number the primary key. Every email subject, every file name, every invoice reference. About 2 hours of policy plus discipline, and it is the precondition for every automation that follows.
  3. Week 2 — document status becomes a field, not a memory. Even a spreadsheet with one row per load and columns for rate con, BOL, POD, lumper, invoice, paid. 3–4 hours. Now the question 'which loads are missing a POD' has an answer.
  4. Week 3 — automate POD chasing. Scheduled reminders at delivery plus 1 day, plus 3 days, plus 7 days, escalating to a phone-call task. 6–10 hours to build. This is where the DSO arithmetic above pays out first.
  5. Week 4 — automate document matching. Inbound attachments read, load number extracted, filed against the load. 10–16 hours. This is what removes the daily inbox triage.
  6. Week 5–6 — automate invoice drafting per customer format. One template per customer, populated from the load record, human review before submission. 12–20 hours. Do the two highest-volume customers only.
  7. Week 7 — automate AR ageing and dunning drafts. Bucketed by the table above, drafted automatically, sent by a human until the language is proven. 6–8 hours.
  8. Week 8 — compliance expiry monitoring. Insurance and authority dates checked daily, flagged before dispatch. 4–6 hours, and it is the one that prevents the catastrophic outcome rather than the expensive one.
  9. Ongoing — review the exceptions weekly. The exception queue is the specification for the next automation. If the same exception appears five weeks running, it is not an exception.

Total build time in that plan is on the order of 45 to 70 hours spread over two months, alongside running the business. The measurement step is non-negotiable, because without it you will automate the workflow that annoys you most rather than the one that costs the most, and those are rarely the same.

Why the inbox is the wrong system of record

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 tables 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. The moment a question like "which loads are past 45 days with no dispute logged" can be answered by a query rather than by a person, the whole class of attention failures stops being possible.

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 in the HwyHaul writeup, and unfamiliar terms are defined in the glossary.

Tools referenced in this guide


FAQ

Quick answers

What does a freight broker do after a load is booked?

Issue and collect a signed rate confirmation, verify carrier authority and insurance, run check calls through pickup and delivery, collect the proof of delivery, generate an invoice in the customer's required format, settle with the carrier or their factoring company, and then track the receivable to payment with dunning at 30, 45, and 60 days.

Why do freight invoices get paid late?

Most commonly a missing proof of delivery, an invoice submitted in a format the customer's accounts-payable system rejects, or nobody chasing at 30 days. Each of these delays a full payment cycle, and none of them are visible until cash is already tight.

What is the most chased document in freight?

The proof of delivery. Without it the invoice usually cannot be submitted at all, which is why POD collection is the step most worth automating in a small brokerage.

How much is days sales outstanding actually costing a brokerage?

Multiply revenue per day by DSO to get the cash tied up in receivables. On an illustrative $3 million of annual billings, revenue per day is about $8,219, so cutting DSO from 52 days to 38 releases roughly $115,000 of cash. Financed at 12 percent that gap costs about $13,800 a year, and bridged by factoring at 2.5 percent it costs far more.

Why do brokerages lose money on detention?

Because detention is proved by two timestamps recorded at the time, and small operations reconstruct them afterwards or not at all. On an illustrative load with a 14:00 appointment, a 19:40 departure, and two hours of free time, 3.5 billable hours at $60 is $210 of customer billing that simply never appears on the invoice.

Which back-office tasks can AI handle in a brokerage?

Reading billing email and extracting load references and amounts, matching documents to loads, drafting invoices in customer-specific formats, chasing missing documents on a schedule, running accounts-receivable ageing and dunning, and flagging expiring carrier insurance or authority before dispatch.

What should stay human in a brokerage?

Rate negotiation, decisions about which customers and carriers to keep, claims handling, and any exchange where the relationship itself is the asset. Automation should handle repetition and deadlines, not judgement.

Why is email a bad system of record for freight?

Because information in an inbox is not queryable. Nobody can answer which loads are missing a POD right now without a person reading threads, so every deadline depends on someone remembering it, which is exactly where margin leaks.