The fastest way to spot double brokering at the invoice stage is to compare three identities that should all name the same company: the carrier on the rate confirmation, the carrier whose name appears on the invoice and remit-to, and the carrier identified on the signed delivery receipt. When a load has been re-brokered without your consent, at least one of those three stops matching, and the mismatch is usually visible days before an unpaid carrier calls you.
Most double brokering advice lives at the onboarding stage: verify authority, check the MC number, watch for new entities with fresh phone numbers. That work matters and it is well covered. It is also the wrong place to catch the loads that slipped through, because a carrier that passes vetting on Monday can re-broker a load on Thursday. Payables is the last checkpoint before money leaves, and it is the one place where the delivery documents and the payment instructions sit side by side.
One thing to say plainly up front: a name mismatch is not proof of fraud. Interlining, co-brokering with written consent, partner-carrier arrangements, and agent-based carriers all produce legitimate paperwork where more than one company touches a load. The signals below are reasons to ask a question, not reasons to accuse anyone.
What double brokering is, and what makes it a payables problem
Double brokering is when a party you tendered a load to, usually a carrier, hands it to a different carrier without your knowledge or consent, then bills you as though it hauled the freight. The carrier that actually moved the truck has a relationship with the middleman, not with you, and often never gets paid.
Your exposure is straightforward: you pay the entity you contracted with, that entity fails to pay the carrier that actually hauled, and the unpaid carrier comes to you, and sometimes to your shipper customer, for the money. Whether that carrier can successfully collect from you after you have already paid in good faith depends on the contracts involved, the facts, and the jurisdiction. Outcomes vary and there is no single federal rule that resolves it. Treat the risk as real and unsettled rather than assuming either side of it.
The practical consequence is that the cost of catching this at payables is small and the cost of missing it is not capped at the invoice amount.
The three-identity check
Run this on every invoice, not just suspicious ones. It takes seconds once the fields are in front of you.
Identity 1: who you contracted with. The rate confirmation names a carrier, an MC or DOT number, and a contact. That is the counterparty.
Identity 2: who is billing you. The invoice letterhead, the entity name, the MC number if shown, and critically the remit-to. Remit-to is the field that gets substituted, because it is the field that actually moves the money.
Identity 3: who delivered. The signed POD or delivery receipt. Look at the carrier name printed or stamped on it, the driver name, the truck or trailer number, and any receiving-facility log entry that names the carrier that checked in.
When all three match, you have a normal load. When identity 3 differs from identities 1 and 2, a different company physically hauled the freight, and you need to know why before you pay. When identity 2 differs from identity 1, the money is being routed somewhere the contract did not specify, which is either a legitimate assignment or a problem.
The signals, and the document that reveals each
| Signal | Where it shows up | What it may mean | What to do first |
|---|---|---|---|
| Carrier name on POD differs from the rate con | Signed delivery receipt, receiving log | Load was re-brokered, or an interline partner ran it | Ask the contracted carrier, in writing, who hauled and under what arrangement |
| Truck or trailer number not in the contracted carrier’s fleet | POD, check-in log, tracking notes | Different carrier’s equipment | Compare against equipment listed on the rate con or setup packet |
| Remit-to is an entity you have never paid before | Invoice, notice of assignment | New factor, or a substituted payee | Verify through a phone number already on file, never one printed on the request |
| Notice of assignment from a factor with no prior relationship | Emailed NOA | Legitimate new factor, or a fraudulent redirect | Call the carrier’s known number and confirm the assignment |
| Invoice amount differs from the rate con with no approved accessorial | Invoice versus rate con | Standard billing error, or a different party billing its own rate | Run the mismatch check before assuming anything worse |
| Rate accepted well below the market for the lane | Rate con, load board history | Load taken to be re-brokered at a spread | Flag at booking; at payables, treat as corroborating, not conclusive |
| Dispatcher contact details differ from the setup packet | Emails, tracking calls | Agent arrangement, or an impostor using a real carrier’s authority | Match domain and phone against the signed carrier agreement |
| A second invoice arrives for the same load from a different entity | AP inbox | The actual carrier is billing you directly | Stop payment on both and reconcile before releasing either |
| A carrier calls asking about non-payment on a load you already paid | Phone | The clearest confirmation, and the latest | Freeze the payment file for that load and pull every document |
The last row is how most double brokering gets discovered, and by then the money is gone. Everything above it is available earlier.
Reading the freight bill for participating carriers
There is a federal requirement that is genuinely useful here and it is underused.
Under 49 CFR 373.103, a freight or expense bill must show the names of the consignor and consignee, the shipment date, origin and destination, package count, freight description, weight or volume, the exact rates assessed, the total charges due with the nature and amount of each charge, the route and each participating carrier, transfer points, and the remittance address. The same part requires the receipt or bill of lading to identify the shipment’s basics under 49 CFR 373.101.
“Each participating carrier” is the phrase to use. When you ask a carrier to produce a compliant freight bill naming the route and every participating carrier, you are asking a routine question with a rule behind it, not making an accusation. A carrier that hauled its own load answers in one line. A carrier that re-brokered has to either name the other party or send you a bill that does not comply.
Be accurate about the limits. Part 373 sets what a bill must contain. It does not prohibit re-brokering, it does not decide who is liable when a downstream carrier goes unpaid, and it is not a fraud statute. Use it for what it is: a documentation requirement that makes the question legitimate.
Two other provisions are worth knowing because they shape who is on the hook for freight charges when the chain gets complicated. Under 49 U.S.C. 13706, an agent-consignee that gives the carrier written notice of its agency status before delivery is liable only for the rates billed at delivery, with the beneficial owner liable for additional rates, and a consignee that misidentifies the beneficial owner stays liable. And under 49 CFR 378.2, two or more payments for transporting the same shipment is a duplicate payment. If you pay both the middleman and the actual carrier, that is the category you are in, and the recovery mechanics are the same ones used for any duplicate freight invoice.
Building the check into the payables workflow
The goal is a control that runs on every load without adding an approval step to every load.
At intake. Capture carrier name, MC number, and remit-to from the rate confirmation into the payable record at booking, not at invoicing. If the values are only entered when the invoice arrives, there is nothing to compare against.
At document receipt. Read the POD for carrier identity, driver name and equipment numbers. If your process treats the POD as a proof-of-delivery checkbox rather than a document, this is the step that is missing. The same discipline that makes a POD useful for detention evidence makes it useful here: what matters is the fields on it, not that it exists.
At invoice match. Compare the invoice against the rate con. Most exceptions this surfaces are ordinary billing errors, and the rate confirmation versus carrier invoice comparison is the standard version of the check. Add two fields to it: billing entity and remit-to. A load where the money is going somewhere new deserves thirty seconds of attention.
At payment release. Hard-stop any load where remit-to changed since booking, where the POD names a different carrier, or where two entities have billed the same load. Route those to a human. Everything else releases.
On change-of-remit requests. Treat every one as unverified until confirmed by outbound call to a number you already had. Inbound verification, where you call the number printed on the request, verifies nothing. This is worth a written policy because it is the control most often bypassed under time pressure, especially by anyone running a quick pay program where the point of the program is speed.
The questions to ask, in order
When a load trips the check, ask in this sequence. Neutral, written, specific.
- “Who physically hauled this load, and under what arrangement?” Give them room to say it was an interline or a partner carrier with consent.
- “Please send a freight bill showing the route and each participating carrier, per 49 CFR 373.103.”
- “Confirm the remit-to on file. We have [entity] on the carrier agreement dated [date].” Then verify any change by outbound call.
- If a second carrier has contacted you: “We have received a billing inquiry from [carrier] on this load. Please explain the relationship.”
- If the answers do not reconcile, hold the payment, notify your shipper customer if their freight is exposed, and get counsel involved before paying anyone. Do not pay both parties to make the problem go away, and do not pay the second claimant without advice, because who is owed what is a legal question and paying twice is a real outcome.
Keep the tone plain throughout. Most of the time the answer is boring, and a carrier that gets accused over a paperwork mismatch remembers it.
What this does not solve
Two limits worth stating.
Invoice-stage detection is a last line, not a first one. Catching a re-brokered load at payables protects the money you have not yet released. It does not protect the freight, and if there is a cargo claim on that load, the coverage question follows the carrier that actually hauled, which is exactly the party you did not vet.
And the check finds mismatches, not intent. It flags legitimate interlines alongside genuine double brokering, and it will miss a re-brokering where the middleman produces clean matching documents. It is a filter that raises the cost of the fraud and lowers your exposure. Combined with the timing rules that constrain everyone in the chain, collected in the freight billing deadlines reference, it turns a category of loss that arrives as a surprise phone call into an exception you handle before the wire goes out.
The checklist
- Record carrier name, MC number and remit-to at booking, from the rate confirmation.
- On every POD, read the carrier name, driver name and equipment numbers, not just the signature.
- Compare the three identities: contracted carrier, billing entity and remit-to, delivering carrier.
- Hard-stop any change to remit-to, and verify only by outbound call to a number already on file.
- Ask for a freight bill naming the route and each participating carrier when identities do not match.
- Cross-check the AP inbox for a second invoice on the same load before releasing either.
- Do not treat a mismatch as fraud. Ask the question, in writing, and record the answer.
- If two parties claim the same load, freeze payment and get advice. Who is owed is a legal question, and paying twice is a real risk.
Sources
- 49 CFR 373.103, What a freight or expense bill must contain, including route and each participating carrier (Cornell LII)
- 49 CFR 373.101, Motor carrier receipts and bills of lading (Cornell LII)
- 49 U.S.C. 13706, Liability for payment of rates (Cornell LII)
- 49 CFR 378.2, Definition of duplicate payment (Cornell LII)