A late broker payment is not automatically a bond claim.
That distinction matters.
A carrier can lose time by escalating the wrong problem, and it can lose much more money by continuing to haul while an actual credit failure is developing.
This guide covers the period between:
“The invoice should have been paid.”
and:
“We are now pursuing the broker’s financial security.”
The objective is not to turn every overdue invoice into a legal dispute.
It is to recognize when normal accounts receivable has become a recovery problem and to preserve the evidence before the carrier needs it.
Start by identifying what kind of nonpayment you actually have
Four situations can look identical from a bank account.
The money is missing.
Operationally, they are very different.
The invoice is not due yet
A carrier may invoice on Monday while the broker-carrier agreement provides:
- net 30;
- net 45;
- payment after receipt of original POD;
- payment after completion of a billing portal workflow.
The carrier can dislike those terms.
That does not make the broker delinquent before the agreed date.
Check the contract before escalating.
The invoice is on administrative hold
Payment may be blocked because:
- POD is missing;
- invoice number does not match the load;
- rate confirmation was revised;
- lumper receipt was not submitted;
- carrier packet information is incomplete;
- factoring assignment information conflicts with the invoice.
This is a document-resolution problem until the evidence suggests otherwise.
There is a genuine commercial dispute
The broker may contest:
- the amount invoiced;
- an accessorial;
- a cargo deduction;
- service performance;
- a contractual offset;
- the identity of the party entitled to payment.
A disputed invoice is not the same as an ignored invoice.
The carrier needs to understand exactly what is being disputed.
The broker is simply not paying
This is the category that deserves rapid escalation.
Warning signs become stronger when the broker:
- misses the contractual payment date;
- ignores repeated written demands;
- promises payment dates and misses them;
- stops providing remittance information;
- accumulates several unpaid invoices;
- is reportedly delaying multiple carriers;
- develops financial-security or authority problems.
The question then changes from:
When will accounting pay us?
to:
What recovery routes are available, and how much more exposure are we willing to create?
Do not wait for a claim decision before controlling exposure
One of the most expensive mistakes happens after the first invoice becomes concerning.
The broker offers another attractive load.
Dispatch accepts it.
Then another.
A carrier can move from:
- $3,800 overdue;
to:
- $18,000 outstanding;
before the first payment problem is resolved.
A BMC-84 bond or BMC-85 trust is not an unlimited credit facility.
The federal financial-security requirement is $75,000, and that amount is not reserved for one motor carrier.
If several carriers are unpaid, the carrier should assume that other claimants may also exist.
The first risk-control decision is therefore often:
Should we keep hauling for this broker?
That question belongs to dispatch and accounting before it belongs to a surety.
Rebuild the transaction from the beginning
A recovery file should make sense to someone who has never seen the load.
Do not assume the provider knows:
- who booked it;
- which truck moved it;
- what rate was agreed;
- whether delivery occurred;
- which charges were approved;
- when payment became due.
Build the file chronologically.
Start with the commercial relationship.
Broker-carrier agreement
Identify:
- correct broker legal entity;
- correct carrier legal entity;
- payment terms;
- notice requirements;
- dispute provisions;
- assignment provisions;
- setoff language;
- governing law or forum provisions where relevant.
The agreement can matter just as much as the rate confirmation.
Rate confirmation
Preserve the final version.
If the rate changed, keep both:
- original rate confirmation;
- revised rate confirmation.
Do not send a provider three different versions without explaining which one controls.
Evidence of transportation
Preserve documents showing performance.
That can include:
- bill of lading;
- signed proof of delivery;
- delivery receipt;
- tracking record where relevant;
- load-specific communications.
The purpose is simple:
show that the transportation the broker arranged was actually performed.
Invoice
The invoice should match the commercial file.
Check:
- broker entity;
- load number;
- amount;
- accessorials;
- payment instructions;
- invoice date.
A claim file with inconsistent numbers creates avoidable questions.
Separate linehaul from accessorial disputes
Suppose the agreed linehaul is $2,900.
The carrier also invoices:
- $240 detention;
- $150 lumper reimbursement.
If the broker agrees that $2,900 is due but disputes detention, do not describe the entire $3,290 as an undisputed invoice unless the documents support that position.
Break down the claim.
A provider needs to understand what portion arises from:
- base transportation charges;
- agreed reimbursement;
- disputed accessorial compensation.
The detention, layover and TONU guide explains why documentation requirements can determine whether an operational delay becomes collectible revenue.
Confirm the broker’s current financial-security filing
Before contacting a provider, recheck the broker.
Do not rely on the information saved when the load was booked.
FMCSA requires qualifying brokers to maintain $75,000 of financial security through:
- BMC-84 surety bond; or
- BMC-85 trust fund agreement.
Use the broker’s current FMCSA records to identify the financial-responsibility filing.
Also check:
- broker legal name;
- MC number;
- authority status;
- filing status.
The 2026 broker financial-responsibility guide explains how BMC-84, BMC-85, drawdowns and authority suspension fit together.
This article addresses the next question:
What does the carrier do with an actual unpaid receivable?
BMC-84 and BMC-85 are not the same financial instrument
BMC-84 is a surety bond.
BMC-85 is a trust fund agreement.
For the carrier, both can sit behind the broker’s federal financial-responsibility requirement.
But the organization handling the claim may be different:
- surety company for a BMC-84;
- eligible financial institution or trustee for a BMC-85.
Do not send a generic “FMCSA bond claim” to an unrelated company.
Identify the actual provider associated with the broker.
Then obtain that provider’s current claim instructions.
There is no single universal carrier claim form
This point is important.
FMCSA establishes the financial-responsibility framework.
It does not provide one universal motor-carrier claim package that replaces every surety or trust provider’s process.
A provider may use:
- online portal;
- PDF proof-of-claim form;
- email submission;
- notarized statement;
- assignment documentation;
- additional verification.
Follow the provider’s current instructions.
A carrier should distinguish:
documents that prove the debt
from:
documents that a specific provider requires procedurally.
Both matter.
Build the evidence packet before submitting anything
A strong carrier file will usually contain enough information to answer six questions.
1. Who owes the money?
Show the broker entity.
Use consistent:
- legal name;
- MC number;
- load references.
2. Who is claiming the money?
Show the carrier entity.
If payment rights were assigned to a factor or another party, address that before submission.
3. What transportation was agreed?
Use:
- broker-carrier agreement;
- rate confirmation.
4. Was the transportation performed?
Use:
- BOL;
- POD;
- other appropriate delivery evidence.
5. How much is unpaid?
Use:
- invoice;
- revised rate confirmation where applicable;
- supporting accessorial documentation.
6. What collection activity already occurred?
Preserve written demands.
A clean collection timeline can show:
- payment due date;
- first follow-up;
- broker response;
- promised payment date;
- missed promise;
- final demand;
- claim submission.
Do not create this history retrospectively from memory.
Preserve the messages when they happen.
Keep one claim chronology
A simple chronology is surprisingly valuable.
For example:
May 4 — Load accepted
May 6 — Delivered
May 7 — Invoice and POD submitted
June 6 — Payment due under net-30 terms
June 10 — First written follow-up
June 14 — Broker says payment will issue Friday
June 19 — No payment received
June 20 — Final written demand
June 24 — Financial-security provider contacted
This is not a federally required format.
It is an evidence-control tool.
It allows another person to understand the dispute without reconstructing a month of email.
What the provider is actually evaluating
A surety or trust provider does not simply ask:
Is the carrier unhappy?
The underlying question is whether the asserted obligation falls within the financial-security framework and whether the claim is valid.
The provider may need to examine:
- broker identity;
- carrier identity;
- contractual relationship;
- transportation performed;
- amount claimed;
- defenses raised by the broker;
- prior payment;
- setoff;
- assignment;
- duplicate claims.
The provider can ask the broker for its position.
That is one reason a carrier should submit a coherent file rather than a folder containing 40 unexplained screenshots.
The seven-business-day rule is narrower than many summaries suggest
Current § 387.307 uses a seven-business-day period in important parts of the claim and suspension process.
One situation occurs when a surety or financial institution notifies the broker of a claim.
If the broker does not respond within seven business days to address the validity of the claim, the provider may determine the claim is valid and make payment.
That does not mean:
Every BMC-84 claim must be paid in seven business days.
FMCSA expressly explained during the rulemaking that the seven-business-day provision concerns the broker’s initial response.
It does not impose one universal deadline on the provider’s investigation of claim validity.
That distinction should affect carrier expectations.
Silence from the broker can matter
The 2026 framework is designed partly to prevent financially failing brokers from accumulating unpaid carrier claims indefinitely.
Under § 387.307, provider payments and determinations can trigger regulatory consequences when the broker’s available financial security falls below $75,000.
Relevant circumstances can include:
- broker consent to payment;
- failure to respond adequately to a claim followed by provider payment;
- payment of a judgment;
- provider determination of financial failure or insolvency under the regulatory conditions.
The carrier does not control that FMCSA process.
But a properly submitted claim can become part of the information that causes the provider to evaluate the broker’s financial condition.
A claim does not automatically suspend broker authority
Do not confuse:
claim submitted
with:
claim validated
with:
claim paid
with:
financial security below $75,000
with:
FMCSA suspension
They are separate events.
One carrier submitting one invoice does not automatically deactivate a broker’s authority.
The regulatory consequences depend on what happens to the financial security and the subsequent provider/FMCSA process.
What happens when the security problem becomes regulatory
When specified events reduce available security below the required amount, the surety or financial institution has reporting obligations to FMCSA.
The current rule uses a two-business-day notification period for specified payments or determinations.
FMCSA then provides its own notice to the broker.
The broker has a separate opportunity to show, for example, that:
- the provider notification was erroneous;
- security was restored;
- pending claims were resolved without using bond or trust assets.
This is why a carrier should continue checking current authority during a serious payment problem.
The status can change after the load has already delivered.
Financial failure creates a different claims environment
The ordinary unpaid-invoice process and regulatory financial failure are not identical.
Under § 387.307, when the surety or financial institution determines that the broker is experiencing financial failure or insolvency under the rule, additional procedures apply.
The provider initiates cancellation of the BMC-84 or BMC-85.
FMCSA publishes notice in the FMCSA Register.
The provider must then accept claims for 60 calendar days following the public notice, with the regulatory extension when the final day falls on a weekend or Federal holiday.
That is a deadline worth monitoring.
A carrier should not assume that a claim can be filed indefinitely after a broker collapses.
Bankruptcy alone is not the trigger described by this rule
The regulation specifically states that a filing under Title 11 does not, by itself, constitute financial failure or insolvency for this provision.
So avoid the shortcut:
“The broker filed bankruptcy; therefore the FMCSA 60-day window automatically started.”
Check the actual regulatory notices and provider status.
Bankruptcy can also introduce separate legal issues beyond this financial-security framework.
What if the broker disputes the claim?
A dispute does not automatically mean the carrier loses.
It means the disagreement needs evidence.
The carrier should identify the precise defense.
Possible examples:
- invoice already paid;
- wrong broker entity;
- incorrect rate;
- missing POD;
- disputed accessorial;
- cargo deduction;
- contractual setoff;
- duplicate billing;
- factoring assignment conflict.
Then respond to that issue.
Do not answer:
“You owe us. Pay immediately.”
when the actual dispute is:
“The broker says the invoice was assigned to a factor and cannot determine who owns the receivable.”
Solve the specific problem.
Factored invoices need special attention
A carrier using factoring may no longer be the only party with rights relating to the invoice.
The file may include a Notice of Assignment.
Payment instructions may direct the broker to the factor.
A bond or trust claim can therefore require clarity about:
- who owns the receivable;
- who is authorized to submit the claim;
- whether the factor has charged the invoice back;
- whether the carrier has reacquired the receivable;
- what documentation proves that status.
The recourse versus non-recourse factoring guide explains why the label on the factoring agreement does not answer every nonpayment question.
Do not submit competing claims from carrier and factor without understanding the assignment.
Accessorial claims need their own evidence
Linehaul can be straightforward.
Accessorials often are not.
A detention claim may require:
- arrival time;
- release time;
- free-time provision;
- prior notice;
- written approval;
- revised rate confirmation.
A TONU dispute may depend on whether the truck:
- accepted the load;
- dispatched;
- arrived;
- met the agreed cancellation trigger.
When a claim includes linehaul plus accessorials, separate them clearly.
That allows the provider to understand the amount even if one component is disputed.
Do not inflate the claim
An unpaid freight claim should be defensible.
Do not automatically add:
- internal administrative time;
- lost future loads;
- speculative profit;
- collection fees;
- interest;
unless there is a valid contractual or legal basis for those amounts.
The strongest claim is not necessarily the largest number.
It is the amount the carrier can explain and support.
Use a short claim summary
The supporting documents can be extensive.
The cover explanation should not be.
A useful summary can identify:
Broker: ABC Logistics LLC
MC: MC-XXXXXX
Carrier: XYZ Transport LLC
Load: 48219
Delivery date: May 6, 2026
Invoice: INV-1042
Original freight amount: $3,850
Payments received: $0
Amount claimed: $3,850
Contractual due date: June 6, 2026
Supporting evidence: Rate confirmation, BOL, signed POD, invoice and written payment demands
Then explain any complication separately.
Do not make the investigator search through email attachments to determine the amount claimed.
Keep proof of the claim submission
After submitting:
- save confirmation page;
- save confirmation email;
- record claim number;
- record provider contact;
- record submission date;
- preserve uploaded documents.
If the portal does not immediately generate confirmation, document what was submitted and when.
A recovery process should have its own audit trail.
Do not stop ordinary collection activity without a reason
Filing against financial security does not mean accounting should forget the broker.
Continue appropriate written communication unless legal advice, provider instructions, bankruptcy restrictions or another applicable circumstance changes the strategy.
Keep asking concrete questions:
- Has payment been issued?
- What is the payment reference?
- Which invoices are disputed?
- What documentation is allegedly missing?
- What is the broker’s position on the claim?
The goal is resolution, not procedural escalation for its own sake.
FMCSA is not the carrier’s collection agency
This limitation should be clear.
FMCSA regulates:
- broker authority;
- financial-responsibility filings;
- provider compliance;
- regulatory notifications;
- suspension processes.
FMCSA’s current FAQ states that the agency does not act as an intermediary in disputes involving individual surety bonds, trust funds or payment between external parties.
A carrier therefore should not send FMCSA an ordinary unpaid invoice expecting the agency to decide:
“Broker owes Carrier $4,500.”
That is not FMCSA’s role.
When a lawyer may become appropriate
Many claims are straightforward commercial receivables.
Some are not.
Legal advice becomes more relevant when the dispute involves issues such as:
- substantial dollar exposure;
- conflicting contracts;
- setoff or indemnification claims;
- cargo-loss deductions;
- disputed assignment;
- bankruptcy;
- litigation;
- multiple legal entities;
- provider denial on a legal coverage theory.
This guide is a carrier operating framework.
It is not a substitute for legal advice on a specific dispute.
A provider denial is information, not the end of the analysis
If the provider rejects the claim, obtain the reason.
Do not record only:
“Bond denied.”
Record:
- date;
- provider;
- claim number;
- amount;
- stated reason;
- documents reviewed;
- whether more evidence can be supplied;
- other recovery options being considered.
A denial because the provider believes the invoice was already paid is different from a denial based on:
- coverage;
- contractual offset;
- claimant identity;
- insufficient evidence.
The next decision depends on the reason.
Build an internal broker-credit record from every incident
Whether the carrier ultimately recovers the full amount or not, the event should change future broker vetting.
Record:
- invoice age at first problem;
- promises missed;
- claims filed;
- amounts recovered;
- time to recovery;
- provider involved;
- broker authority changes.
A broker that eventually pays after 90 days and a bond claim is not equivalent to a broker that consistently pays net 30.
Both may show:
Paid
in the accounting system.
Their credit quality is not the same.
The recovery decision should happen before the crisis
A carrier should define escalation while its receivables are healthy.
For example:
Normal Invoice within contractual terms.
Review Invoice beyond normal terms or documentation dispute unresolved.
Credit hold Material overdue balance or repeated missed payment commitments.
Recovery Formal demand, provider claim or other collection action appropriate to the circumstances.
The exact day thresholds depend on the carrier’s contracts and risk tolerance.
The important part is that dispatch does not continue extending unlimited credit while accounting is already escalating nonpayment.
The practical standard
When a broker does not pay, do not begin with:
“How do I file against the bond?”
Begin with:
Is the money actually due?
Then:
Can we prove the transaction?
Then:
Who currently holds the broker’s financial security?
Then:
What claim procedure does that provider require?
And while those questions are being answered:
Should we continue hauling for this broker?
That sequence protects more than one invoice.
It protects the carrier from turning an isolated $4,000 receivable problem into a $20,000 credit problem while waiting for someone else to resolve it.