Freight Broker Bond Explained — The $75K Requirement

For anyone searching for “freight broker bond explained,” the central rule is straightforward: a federally registered property broker must maintain $75,000 in financial security. That security is usually provided through a surety bond, commonly called a freight broker bond, or through an approved trust fund.

The requirement applies to brokers arranging transportation for compensation. It does not mean the broker has $75,000 sitting in a bank account, and it is not the same as cargo insurance, commercial general liability insurance, or a carrier’s insurance filing. Understanding the difference matters to brokers, carriers, shippers, and factoring companies because the bond is one of the primary protections available when a broker fails to pay a carrier or otherwise violates its obligations.

What Is a Freight Broker Bond?

A freight broker bond is a financial guarantee required for broker authority issued by the Federal Motor Carrier Safety Administration. The broker is the principal, the surety company issues the bond, and the federal government and affected parties benefit from the financial security.

The governing statute is 49 U.S.C. § 13906(b). The implementing regulation is primarily 49 CFR § 387.307, which addresses the security requirements for brokers and freight forwarders. Under these requirements, a property broker must maintain financial security of at least $75,000 to obtain and retain authority.

The bond is not a pool of money that automatically pays every disputed invoice. A claimant generally must show that the broker failed to meet a covered obligation, follow the surety’s claims process, and provide supporting documentation. If valid claims exceed the available security, the bond may not make every claimant whole.

The $75,000 figure is the required amount of financial security, not a guaranteed payment to every carrier with an unpaid invoice.

Who Must Have the $75,000 Security?

A person or company acting as a property broker for compensation generally needs broker authority and the required financial security. A broker arranges transportation by motor carrier without operating the equipment that moves the freight.

The requirement commonly applies to:

• Independent freight brokers
• Brokerage divisions of logistics companies
• Third-party logistics companies arranging regulated motor-carrier transportation
• Businesses that negotiate transportation with shippers and tender loads to carriers for compensation

A motor carrier that transports freight under its own operating authority does not obtain a broker bond merely because it occasionally uses another carrier. However, the company’s activities and contracts determine whether it is acting as a carrier, broker, or both. A carrier that brokers loads to another carrier may need separate broker authority and financial security for that activity.

Motor carriers should also be cautious when a company presents itself as a “dispatch service.” A dispatcher operating under a carrier’s direction may not be a broker, but the classification depends on the actual business relationship and conduct. Calling a company a dispatcher does not eliminate broker obligations if it independently solicits shippers, allocates freight among carriers, or arranges transportation for compensation in a manner that meets the legal definition of brokerage.

Why Was the Bond Increased to $75,000?

The $75,000 requirement was established by the Moving Ahead for Progress in the 21st Century Act, commonly known as MAP-21. Before the increase, the required broker security was substantially lower. Congress raised the amount to provide greater protection in a freight market where unpaid carrier claims can accumulate quickly.

The requirement applies to property brokers and freight forwarders under federal law. It is separate from the broker’s operating authority application, BOC-3 process-agent filing, and other registration obligations. A broker needs all required filings in place before it can lawfully operate under federal authority.

FMCSA can take action when required financial security is cancelled, revoked, or no longer available. A broker should not assume that paying the original bond premium once is enough. The broker must keep the bond or trust active and respond promptly to notices from the surety, FMCSA, or other parties.

Surety Bond Versus Trust Fund

Most brokers satisfy the requirement with a surety bond filed on FMCSA Form BMC-84. A broker pays a premium to a surety company, and the surety guarantees the required amount subject to the bond’s terms and applicable law.

An alternative is a trust fund filed on Form BMC-85. Instead of purchasing a bond, the broker deposits qualifying assets into a trust arrangement. The trust must meet FMCSA requirements and remain properly funded and maintained.

The practical differences include:

• Surety bond: Usually requires an annual premium and underwriting review. The broker generally does not deposit $75,000 with the surety.
• Trust fund: Requires qualifying financial assets to be placed into an approved trust structure. The broker carries the cost of tying up capital and managing the trust.
• Claim handling: Both structures can be used to address valid claims, but the process and documentation depend on the provider and the governing arrangement.

A broker should verify that the provider is authorized to issue the required security and that the filing has been accepted by FMCSA. An invoice for a bond premium is not proof that the federal filing is active.

What Does the Bond Cover?

The bond is intended to protect parties from certain financial failures or violations connected to the broker’s regulated operations. The most common practical issue is a carrier’s unpaid freight bill after the broker received payment from the shipper, failed to pay the carrier, or became insolvent.

Potential claimants may include motor carriers and, depending on the facts and applicable law, other parties with a valid claim against the broker’s required financial security. A claimant must connect the loss to the broker’s obligations and provide evidence. A simple disagreement over a rate, detention charge, lumper fee, or accessorial does not automatically establish a bond claim.

The bond generally does not replace:

• Cargo insurance for freight loss or damage
• Auto liability insurance for accidents
• Workers’ compensation coverage
• Errors and omissions insurance for every type of business dispute
• Payment assurance for invoices that lack proper documentation or violate the contract

Bond language, federal requirements, state law, and the facts of the transaction all affect a claim. Brokers should have written agreements that identify payment terms, documentation requirements, offsets, chargebacks, and dispute procedures.

How a Carrier Can File a Bond Claim

1. Confirm the Broker’s Identity and Authority

Before filing, verify the broker’s legal name and active authority in FMCSA records. A claimant should identify the correct principal and surety rather than sending a demand to a similarly named company or an individual employee.

2. Assemble the Transaction File

Strong documentation makes a claim easier to evaluate. Gather:

• Signed broker-carrier agreement
• Rate confirmation and any revised rate documents
• Bill of lading and proof of delivery
• Invoice and payment history
• Emails, messages, or call notes concerning the load
• Approved detention, layover, lumper, or other accessorial records
• Notice of any offset, deduction, or disputed amount

3. Demand Payment in Writing

Send a clear written demand to the broker using the payment address and method specified in the contract. State the load reference, amount due, due date, documents provided, and a reasonable deadline for response. Keep proof of delivery.

4. Submit the Claim to the Surety or Trustee

If the broker does not resolve the account, follow the claim instructions for the BMC-84 surety or BMC-85 trust. The provider may require a claim form, contract, invoice, proof of delivery, correspondence, and evidence that the amount remains unpaid.

Do not exaggerate a claim or submit duplicate claims for the same debt. If several creditors submit claims, the provider may investigate competing demands and distribute available funds according to the bond, trust terms, and applicable law.

Important Limits of the $75,000 Bond

The $75,000 amount is an aggregate financial-security limit, not a per-load limit. If a broker owes several carriers, the total claims can exceed the available security. A carrier with a valid claim may receive only part of the amount if the bond is insufficient to cover all approved claims.

The bond also does not guarantee prompt payment. Investigation can take time, particularly when the broker disputes delivery, rate terms, cargo responsibility, or the identity of the party that owes the money. Carriers should continue normal credit-control practices instead of treating the bond as a substitute for evaluating a broker before accepting freight.

Fraudulent or altered documents can create additional problems. A carrier should preserve original records, avoid accepting suspicious rate confirmations, and confirm that payment instructions have not changed through an unverified email request.

How Brokers Can Stay Compliant

Broker compliance is broader than keeping a bond active. Under 49 CFR Part 371, brokers must maintain specified records of their transactions. Section 371.3 addresses broker transaction records and access to those records. A broker should maintain organized files for each shipment, including the shipper, carrier, freight, compensation, and transaction terms required by the regulation.

Practical controls include:

• Track bond renewal dates and cancellation notices
• Confirm that BMC-84 or BMC-85 status remains active
• Use written broker-carrier agreements and consistent rate confirmations
• Separate carrier payables from disputed deductions
• Reconcile shipper receipts, carrier invoices, and accessorial approvals
• Keep transaction records in a searchable system
• Monitor cash flow so carrier payments do not depend on a single shipper’s payment cycle
• Review authority, insurance, and identity information before onboarding carriers

Technology can reduce preventable administrative errors. VAU0 LLC provides a free platform through December 2026 with TMS workflows, carrier onboarding, compliance management, document handling, and Rate Con AI tools that can help teams keep rate and payment records connected to each shipment.

How Carriers Should Evaluate a Broker

Before accepting a load, a carrier should review the broker’s authority, operating history, payment reputation, contract terms, and contact information. Confirm that the rate confirmation comes from a legitimate company domain and that payment instructions match previously verified information.

Useful questions include:

• Is the broker’s authority active?
• Is the required financial security showing as active?
• Who is the legal contracting party?
• What are the payment terms and invoice requirements?
• Are detention, layover, lumper, and truck-order-not-used terms written clearly?
• Does the broker require factoring notices or special payment procedures?

A carrier should not rely solely on the existence of a bond. Credit limits, load selection, written contracts, and timely invoicing remain essential risk controls.

Using Operations Software to Reduce Bond-Related Risk

Bond claims often begin with missing documents, unclear rate changes, or payment records that cannot be reconstructed. A TMS that links the load, rate confirmation, carrier agreement, delivery documents, invoice, and payment status creates a more defensible record for both sides.

VAU0 LLC also combines dispatching, ELD management through ERETH ELD, driver onboarding, compliance workflows, and an AI call center in one free platform through December 2026. For a broker-carrier operation, the value is not the bond itself; it is having operational and transaction records organized before a dispute occurs.

Practical Takeaway

The freight broker bond is a $75,000 federal financial-security requirement under 49 U.S.C. § 13906(b) and 49 CFR § 387.307. It protects against certain broker-related payment failures, but it is not cargo insurance or a guaranteed recovery for every unpaid invoice. Brokers should keep their BMC-84 or BMC-85 filing active, maintain Part 371 records, and manage payment controls carefully. Carriers should verify authority, document every load, and treat the bond as a last-resort protection—not a replacement for broker due diligence.

In 2022, we were running a small fleet and spending approximately $400 per truck per month on software. TMS license, ELD subscription, e-sign service, separate accounting integration. Four different logins. Four different monthly invoices. Four different support teams to call when something didn't work.

None of it talked to each other without manual data entry.

The software evaluation that changed everything

We spent three months evaluating every major TMS and fleet management system on the market. AscendTMS, McLeod, Motive, EZLogz, KeepTruckin, TruckingOffice, Axon. We signed up for demos, trials, and in two cases, paid for actual subscriptions to test them properly.

What we found was consistent across almost all of them: the software was built by people who had never dispatched a truck. You could tell immediately. The terminology was slightly wrong. The workflows assumed steps that no real dispatcher would take. The ELD and TMS were always separate systems that "integrated" — meaning they sometimes shared data, if you configured things correctly, and the configuration broke whenever either vendor pushed an update.

"The best way to evaluate trucking software is to use it under real pressure. Not in a demo. Not in a test environment. On a real load, with a real deadline, when a broker is calling every 30 minutes for an update."

The specific things that were broken

Without naming specific vendors: one major TMS required five screen transitions to update a load status. Not five clicks — five full page navigations. On a mobile browser from a truck stop, that meant 45 seconds to tell a broker the truck was loaded. Another system had beautiful analytics dashboards but couldn't tell you, in real time, how many hours of drive time your driver had remaining without navigating to a separate compliance module.

The ELD market was worse. Most ELD systems were designed to satisfy FMCSA's technical requirements — which they did — while making the user experience as painful as possible. Drivers hated them. When drivers hate their tools, they find workarounds. Workarounds create compliance risk.

The moment we decided to build

The decision was made on a Tuesday afternoon when our dispatcher spent 40 minutes re-entering data from a rate confirmation PDF that our ELD had already captured in a different system. The information existed. It was digital. It lived in three different places that didn't talk to each other, and a human was manually transferring it between systems.

That's not a technology problem. That's a lack of ambition problem. Nobody had decided to solve it because the existing systems were profitable enough without solving it.

What we decided to build instead

One platform. ELD and TMS as the same system, not integrations. AI that reads rate confirmation PDFs so dispatchers don't have to. A dispatcher — eventually an AI dispatcher — that covers nights and weekends so loads don't get missed. E-sign built in, not bolted on.

And priced at zero through 2026, because the goal was to prove the product worked before asking carriers to pay for it.

Two years in: did it work?

The Rate Con AI has a 95%+ accuracy rate on standard broker formats. ERETH ELD passed FMCSA's technical certification. Our AI dispatchers book real loads for real carriers after hours. The carrier dashboard still occasionally has a minor bug — we fix them the same day they're reported.

Would we have been better off just using an existing system and focusing on freight? Financially, in the short term, probably yes. But we would have kept paying $400 per truck per month for software that we knew was mediocre. And we would have missed the opportunity to build something that actually works the way the industry needs it to work.

We don't regret it.