Skip to content

Answers · Freight Brokerages

Freight Broker Invoicing: How Many Days From Delivery to an Invoice the Shipper Accepts?

Freight broker invoicing comes down to one number that no invoice template shows: the days between a load’s delivery and an invoice the shipper has accepted. That number is built from four timestamps (delivered, carrier POD received, shipper invoice sent, invoice accepted), and each gap between them has its own cause and its own owner. This guide shows how to measure all four on every load from the brokerage’s own TMS, the reasons the clock stops, what the federal broker records rule already requires on each load, and how to give delivered-to-invoiced one owner so the shipper’s payment terms start sooner.

By , founder of Lumina Business Advisory · Updated · Sources checked · Editorial standards

Freight broker invoicing runs on four timestamps

Free self-check · two taps · no email

Hand-off 4 of 6 · Delivery → Invoice

How many days pass, typically, between finishing work and sending the invoice?

Choose the answer that sounds like your business.

Answer it in the Self-Audit

A shipper’s payment terms do not start at delivery. Depending on the contract, they start at the invoice date or at the date the shipper receives an invoice it can process. Every day between delivery and that point is a day the freight is finished, the carrier is owed, and nobody has yet asked the shipper for the money. So the useful question is not which invoice template to use. It is how many days pass, load by load, before the shipper holds an invoice it will pay.

Four timestamps answer it. The TMS already stores some of them as statuses; the rest sit in email and portal confirmations.

  • Delivered. The time the load was delivered, from tracking, the check call or the carrier’s message, recorded as a status on the load.
  • POD received. The time a readable, signed proof of delivery reached the brokerage and was attached to the load.
  • Invoice sent. The time the shipper invoice left the brokerage, by email, EDI or the shipper’s portal.
  • Invoice accepted. The time the shipper’s system or AP team accepted it, or the date it came back rejected, with the reason.

Each gap has a different cause. Delivered to POD received is a carrier and paperwork question. POD received to invoice sent is a billing-desk question. Invoice sent to invoice accepted is a question about the shipper’s requirements. A single total hides which of the three is long, so measure all three. Public brokers carry this quantity in their books: C.H. Robinson’s 10-K for 2025 reports $156.4 million of revenue recorded at year-end for shipments still in transit, or completed but not yet invoiced, carried on its balance sheet as contract assets. A small brokerage has no such line, but it has the same list in its TMS: loads delivered and not yet billed.

Where the clock stops between delivery and the shipper invoice

The reasons a delivered load has no invoice can be coded, and once they are coded they can be counted. A starting list follows; the brokerage’s own loads will add codes and drop others.

  • No POD yet. The carrier has not sent it, or sent it to one person’s inbox, and nobody asked again.
  • POD unreadable or incomplete. A photo of a crumpled page, a missing signature or page, or exceptions written on the receipt that nobody read.
  • Missing shipper reference. The shipper’s load number, PO or BOL number is not on the load record, so the shipper cannot match the invoice.
  • Accessorial pending. Detention, a lumper receipt, a layover or a truck-ordered-not-used charge is waiting on the shipper’s approval, and the whole invoice waits with it.
  • Rate mismatch. The rate on the load does not match the shipper’s tender or rate agreement, so billing holds it for the salesperson to explain.
  • Portal requirements. The shipper’s portal or EDI setup asks for a different document set, format or reference than the one on file.
  • Batch timing. Invoices go out on fixed days, so a load delivered after the last batch waits for the next one.
  • No reason. The load was delivered and nobody noticed it had not been billed.

The last code is the cheapest to fix and the hardest to see. It leaves no email thread behind and shows up only when someone lists the delivered loads without an invoice and asks about each one by name.

What the broker records rule already asks for on every load

Federal rules already require much of what a shipper’s billing team checks. Under 49 CFR 371.3, a broker keeps a record of each transaction showing the name and address of the consignor; the name, address and registration number of the originating motor carrier; the bill of lading or freight bill number; the compensation received for the brokerage service and the name of the payer; any non-brokerage service and its compensation; and the amount of any freight charges collected and the date of payment to the carrier. The records are kept for three years, and each party to a brokered transaction has the right to review the record of that transaction.

On the carrier’s side, 49 CFR 373.101 lists what a motor carrier’s receipt or bill of lading must show: consignor and consignee, origin and destination, number of packages, description of the freight, and weight, volume or measurement where it applies to the rating. Read together, the two rules suggest a practical design. Build the shipper invoice from the load record, which the brokerage keeps anyway, and treat the POD as the evidence attached to it, not as the page the invoice is typed from.

Late charges run on their own clock. Under 49 U.S.C. 13710(a)(3)(A), a carrier must issue any bill for charges in addition to those originally billed within 180 days of the receipt of the original bill to keep the right to collect them, and under (a)(3)(B) a shipper must contest an original or later bill within 180 days of receipt. The statute is written about motor carriers and shippers. How it applies to a broker’s own invoices, and whether a shipper contract allows a line-haul invoice now and a separate invoice for an approved accessorial later, are questions for the brokerage’s transportation attorney and its contracts. Where both allow it, a pending detention approval no longer has to hold the line-haul invoice. Not legal advice.

Measure last week’s loads, one by one

The count needs one export from the TMS: every load delivered last week, with its delivered time, the time the POD was attached, the invoice date, the shipper, the invoice amount and, where the shipper uses a portal, the date it was accepted or rejected. Then add three columns by hand.

  • Days from delivered to invoice sent, for every load, split into the three gaps above where the timestamps exist.
  • For every load not yet invoiced: its age in days, its amount and one reason code from the list above.
  • For every rejected invoice: the shipper, the rejection reason in the shipper’s own words, and the date the invoice went back.

Illustrative example: a brokerage delivers 200 loads in a week at an average shipper invoice of $2,500. Of those, 150 are invoiced the next business day and 30 within four days. Twenty are still open after five days: eight wait on a POD, five on a detention approval, three on a missing PO number, two on a portal rejection and two on nothing at all. Those 20 loads are $50,000 of finished freight with no payment term running yet. Sorted by reason, the list shows which fix comes first. Read aloud once a week, by name, it has a reason to get shorter.

One owner for delivered-to-invoiced

The fix is ownership first and software second. One person, by name, owns the step from delivered to invoiced. On a cradle-to-grave desk that person can still be the rep, but the check happens at a fixed time each afternoon, not whenever live loads allow it. With a pod or a billing desk, it is the billing lead, with a written rule for what the carrier side must hand over and by when. The daily check is short: every load delivered since yesterday with no invoice, each with a reason and a next action.

A handful of standing rules keeps the list short.

  • Ask for the POD at delivery, not days later. The request goes to the carrier with the delivery confirmation, and the carrier’s payment, standard or quick pay, is released against a readable POD. C.H. Robinson’s 10-K describes its own faster final payment to carriers as made upon proof of delivery.
  • Keep each shipper’s billing requirements in the customer record: the references it needs, the document set, portal or EDI, and the contact who fixes rejections.
  • Put the shipper’s reference on the load at booking, so billing never has to look for it after delivery.
  • Decide in writing which items hold an invoice. A missing POD may. An accessorial waiting on approval need not hold the line-haul, if the shipper’s contract allows a separate invoice.
  • Read rejections the same day. A rejected invoice is an invoice not yet sent.

When to fix it in-house, and when not to hire anyone

Everything above is in-house work: one export, an afternoon of counting, a daily list and a named owner. A brokerage that already invoices nearly every load the next business day, and whose open list carries a reason on every line, does not need outside help with this hand-off.

It is worth a second look when the open list keeps growing, when “no reason” is the most frequent code, or when late invoices sit next to other leaks: accessorials paid to carriers and never billed to shippers, short-pays nobody disputes, shippers paying well past terms. The page on freight brokerage consulting lays out where a brokerage’s cash waits, hand-off by hand-off. The Revenue Review is a read-only engagement that takes two weeks. We read the brokerage’s own load, invoice and payment records, measure the days from delivery to accepted invoice on every load, and put a monthly dollar figure on each leak, with a written report and a 90-day plan. It does not cover legal questions about billing rules; those stay with the brokerage’s attorney. A free 20-minute call is enough to tell whether a Review fits.

Before any next step

What should you do next?

Fix it yourselves.
If the cause is clear, it lives inside one process, and one person can own it — take the play from this page and run it. That outcome is fine with us; it is why the play is published in full.
Order one bounded build.
If the fix is known but needs configuration or integration inside your stack — a cadence wired into your own system, an alert, a handoff — scope that one build, with us or with anyone you trust. The six systems we build show what bounded looks like.
Start with the Review.
If the causes are debatable, the problem crosses departments or systems, or the economics are unclear — diagnose before anyone builds. The Revenue Review: $4,500 fixed, two weeks, computed from your own records. Read a sample finding before you decide — free, no email.

Asked right after

How fast should a freight broker invoice the shipper?
As soon as the brokerage holds what the shipper’s contract requires, which may include a readable POD and the shipper’s own references. The broker records rule in 49 CFR 371.3 sets what must be recorded, not when the shipper is billed, so the target is the brokerage’s to set. A workable one is the next business day after the POD arrives, with every load that misses it listed with a reason. Shipper terms start at the invoice or receipt date in the contract, so each day before the invoice adds a day to the cash gap.
Does a freight broker need the POD before invoicing the shipper?
It depends on the shipper’s contract and billing requirements. Some shippers require the signed POD with the invoice; others accept the invoice and ask for the POD only when a charge is questioned. Read each customer’s terms, record the answer in the customer file, and do not hold invoices for documents a shipper never asked for.
What records does a freight broker have to keep for each load?
Under 49 CFR 371.3: the consignor’s name and address; the originating motor carrier’s name, address and registration number; the bill of lading or freight bill number; the brokerage compensation and who paid it; any non-brokerage service and its compensation; and the freight charges collected and the date of payment to the carrier. The records are kept for three years, and each party to the transaction may review its record.
Can a broker invoice an accessorial after the original invoice?
For motor carriers, 49 U.S.C. 13710(a)(3)(A) sets 180 days from receipt of the original bill to issue a bill for additional charges, and (a)(3)(B) gives the shipper 180 days to contest a bill. Whether and how that applies to a broker’s invoice to a shipper, and what the shipper contract allows, is a question for the brokerage’s transportation attorney. Operationally, a separate invoice for an approved accessorial lets the line-haul invoice go out without waiting.
Why do shipper portals reject freight invoices?
The brokerage’s own rejection log is the reliable answer. Code each rejection in the shipper’s own words for one quarter. Codes to start with: a missing or wrong reference number, a rate that does not match the tender, a missing document, and an accessorial with no approval on file. The counts show which shipper and which code to fix first.
What goes on a freight broker invoice to the shipper?
Everything the shipper needs to match the invoice to the load and pay it: the brokerage’s name as registered with FMCSA and its remit-to details, the shipper’s own load, PO or BOL reference, origin, destination and delivery date, the agreed line-haul rate, each approved accessorial on its own line, and the payment terms from the contract, with the POD attached when the shipper requires it. The federal broker rules in 49 CFR part 371 set no invoice format, so each shipper’s contract and billing requirements decide the rest. Two of those rules still bear on the invoice. Under 49 CFR 371.7(a), a broker may not perform or offer brokerage services in any name other than the one its registration is issued in, so the invoice carries the name on the registration. Under 49 CFR 371.10, where the brokerage acts on behalf of someone bound by law or FMCSA rules on sending bills or payments, it must also follow the rules that apply to that party.
Does my brokerage have to share load records when a carrier asks?
Yes, under the current federal rule: 49 CFR 371.3(c) gives each party to a brokered transaction, the carrier included, the right to review the brokerage’s record of that transaction, which is the per-load record 371.3(a) requires. The current text sets no deadline. FMCSA’s November 2024 proposal (89 FR 91648) says that, written as a private right to review, the rule did not prohibit a broker from requiring a waiver of that right as a condition of brokering a load, and gave the agency no mechanism to enforce it. The proposal would require brokers to provide a copy of the record electronically within 48 hours of receiving a request. As of October 23, 2026 it has not been made final, and the Fall 2025 federal regulatory agenda lists a supplemental proposal as the next step. Keep the record complete in the TMS on every load so a request is one export, and read the carrier agreement with the brokerage’s transportation attorney before refusing one.

Sources

The next step

Bring us the process that keeps getting stuck.

A 20-minute conversation about the workflow, the teams and the systems involved — and a straight answer on whether The Revenue Review is the right next step. If it is not, we say that on the call.

A real person answers or calls you back the same business day.

Free self-check · 2 taps