Freight Broker Bonding: BMC-84 vs BMC-85 Trust Fund, the $75,000 Rule, and TMS Bond Tracking

Where the $75,000 Requirement Comes From

Brokers of property must register with FMCSA and file evidence of financial security before their authority is granted. The statutory requirement sits in 49 U.S.C. 13906, and the implementing regulation for brokers is 49 CFR 387.307. For years the required amount was $10,000. The Moving Ahead for Progress in the 21st Century Act, known as MAP-21, raised the minimum to $75,000 and extended the security requirement to freight forwarders. FMCSA implemented that change in 2013, and every active broker authority today must carry the higher amount.

The purpose of the security is narrow and important. It exists so that motor carriers and shippers have a source of recovery when a broker fails to pay amounts owed under its contracts. It is not cargo insurance, it is not contingent auto liability, and it does not protect the broker itself. A broker who thinks of the bond as insurance for the brokerage has the relationship backwards. The bond protects the people the broker hires and serves, and every claim paid against it eventually comes back to the broker one way or another.

Brokers also carry recordkeeping duties under 49 CFR Part 371. Section 371.3 requires a broker to keep a record of each brokered transaction for three years, including the name and address of the consignor, the carrier, the bill of lading or freight bill number, the compensation received, and the amounts paid to the carrier, and each party to the transaction has the right to review that record. A broker TMS that cannot produce that record on request is a compliance gap in its own right, and it is also the first document a carrier will ask for when a payment dispute starts.

BMC-84 Surety Bond vs BMC-85 Trust Fund

FMCSA accepts two primary forms of broker security. The BMC-84 is a surety bond. A licensed surety company issues the bond, files it electronically with FMCSA, and promises to pay valid claims up to the bond amount. The broker pays an annual premium that the surety sets based on credit, financial statements, and experience, and the broker signs an indemnity agreement, which means the surety will seek repayment from the broker for any claim it pays. The BMC-85 is a trust fund agreement. A trustee holds the full $75,000 in qualifying assets, files the agreement with FMCSA, and pays valid claims out of the trust corpus.

Neither form is automatically better. A broker with strong credit may prefer the BMC-84 because it preserves working capital. A broker that wants to avoid premium and underwriting may prefer the BMC-85, but must be comfortable parking the full amount. Under the financial responsibility rule, the assets that can back a BMC-85 trust are limited to highly liquid forms such as cash, irrevocable letters of credit, and Treasury bonds, which makes the choice of trustee and asset type more consequential than it once was.

The FMCSA Financial Responsibility Rule

In November 2023 FMCSA published a final rule on broker and freight forwarder financial responsibility, implementing further MAP-21 provisions. The rule carried a delayed compliance date, which FMCSA set for January 2026. Because implementation details and dates can be adjusted by notice, brokers should confirm current status directly with FMCSA and with their surety or trustee rather than relying on any summary, including this one. The main themes of the rule are stable, and they shape how a broker should run its back office.

• Assets readily available - Security must be available to pay claims, which is why trust fund assets are limited to liquid forms rather than illiquid property.
• Drawdowns and suspension - When a claim payment or other drawdown leaves available security below $75,000, the surety or trustee notifies FMCSA. If the broker does not replenish within the short window the rule allows, FMCSA suspends the broker's operating authority until the security is restored.
• Broker failure and insolvency - The rule addresses what sureties and trustees must do when a broker fails financially or enters bankruptcy, including initiating cancellation and giving public notice so claimants can come forward within a defined claims period.
• Claims handling - The rule sets expectations for how sureties and trustees receive, evaluate, and pay claims, including how uncontested claims are treated when the broker does not respond.
• Enforcement against providers - FMCSA gained clearer authority to act against sureties and trust fund providers that do not meet their obligations.

The operational takeaway is simple. Before the rule, a broker could sometimes absorb a paid claim slowly while the authority stayed active. Under the rule, a paid claim can quickly become an authority problem. That turns carrier pay discipline from a reputation issue into a license issue, and it raises the value of good systems.

Bonds and trust agreements can also be cancelled by the provider on written notice to FMCSA, and the regulations require a notice period of 30 days before cancellation takes effect. A broker that misses a premium or fails to provide requested financials may learn about a pending cancellation from the surety letter or from the FMCSA record. Either way, someone in finance must own that notice and act before the 30 days run out.

Why Carrier Pay Timing Is a Bond Issue

Federal broker regulations do not set a universal deadline for paying a carrier. Payment terms come from the broker carrier agreement and the rate confirmation, and many brokers offer standard terms alongside quick pay options. What the regulations and the bond do create is consequence. When a carrier is not paid according to the contract, the carrier can file a claim against the broker's security. If that claim is paid and the security drops below $75,000, the authority is at risk.

Most broker bond claims do not start as fraud. They start as an aging payable that nobody owned. The proof of delivery was blurry, the invoice landed in the wrong inbox, a lumper receipt was disputed, a factoring company notice of assignment was not loaded, or the carrier was paid to the wrong remit address after a bank change request. Each of these is a data and workflow problem. Each can be caught by a TMS and accounting stack that treats carrier payables as a compliance signal and not just an accounts payable list.

Example: a broker moves 400 loads in a month on 30 day carrier terms. If 3 percent of those loads stall on missing documents, that is 12 open payables that can age past terms without anyone noticing. At an assumed average carrier rate of $2,200, those 12 loads represent $26,400 of potential claim exposure, more than a third of the $75,000 security. The numbers here are illustrative, but the arithmetic shows why a small leakage rate matters.

Use our quick pay vs factoring cost calculator to model how payment terms affect carrier economics, and pair it with an aging review so that quick pay programs and standard terms are both being met.

What the TMS and Accounting Stack Should Track

A broker should model financial security as a record in the system, not a PDF in a shared drive. The record should carry the security type, BMC-84 or BMC-85, the surety or trustee name, the bond or agreement number, the effective date, the amount, the renewal or premium due date, and any cancellation or drawdown notices received. A daily or weekly job should compare that record with the public FMCSA registration status and alert finance and the compliance owner if anything changes. Our freight broker consulting work often starts by building this single source of truth.

• Security master record - Type, provider, number, amount, effective date, and notice history.
• Authority status check - Scheduled comparison against FMCSA registration and insurance filings.
• Carrier payable aging - Open payables by days past contractual terms, not just by invoice date.
• Document readiness - Whether POD, invoice, and accessorial receipts are complete for each load.
• Dispute register - Short pays, claims offsets, and disputed accessorials with owner and next action date.
• Remit to integrity - Notices of assignment, factoring releases, and verified bank changes with approval history.
• Claim correspondence - Any letter from a carrier, attorney, surety, or trustee logged against the load and the carrier.

The integration between TMS and general ledger matters here. If the TMS shows a load as delivered and approved but the accounting system has no payable, the gap is invisible until a carrier calls. A clean transportation accounting integration creates the payable at the right status, carries the contractual due date, and writes payment confirmation back to the load so dispatch and carrier relations can answer the carrier without opening a second system.

Exception Queues That Prevent Claims

Good brokers do not wait for a monthly aging report. They work exception queues every day. Build queues for loads delivered more than a set number of days without a carrier invoice, invoices received without a POD, payables approaching their due date with an open dispute, and carriers with more than one payable past terms. Each queue should have an owner, a service level, and a clear next step. A reporting layer that shows these queues by team and by customer helps management see where documents stall.

Document capture is often the bottleneck. Carriers send PODs as photos, scans, email attachments, and portal uploads. Automated classification and field extraction can match a POD to the right load, read the delivery date and signature presence, and route anything unclear to a person. That shortens the time from delivery to approved payable, which is exactly the window where bond exposure grows. Our document AI automation practice focuses on that window with human review for low confidence matches.

Payment fraud is the other side of the problem. A bank change request that redirects carrier pay to a fraudster leaves the real carrier unpaid and free to claim against the bond. Verify every remit change by calling a known number on file, require dual approval, and log the verification. The insight on carrier ACH payment fraud controls covers that workflow in more depth.

Handling a Claim When It Arrives

When a surety or trustee forwards a claim, speed and evidence matter. Pull the full transaction record required by 49 CFR 371.3, the signed rate confirmation, the carrier packet, the POD, the invoice, any accessorial approvals, and the payment history. If the claim is valid, paying the carrier directly and documenting the release is usually cleaner than letting the surety pay and then reimbursing it. If the claim is disputed, respond to the provider within its stated deadline with specific documents, because an unanswered claim may be treated as uncontested. Log every step against the load so the next person can see what happened.

Keep claim data in the TMS, not only in email. Over time, claim records reveal patterns, a customer whose PODs routinely arrive late, a carrier group that disputes lumper charges, or a team that approves payables slowly. Those patterns are the inputs for process fixes that reduce future exposure.

A Practical 60 Day Plan

Days 1 to 20, create the security master record, confirm the current BMC-84 or BMC-85 details with the provider, and schedule an automated FMCSA status check. Days 21 to 40, build the carrier payable aging view by contractual due date, stand up the dispute register, and lock down remit change approvals. Days 41 to 60, connect document capture to payable approval, publish exception queues with owners, and run a mock claim drill that measures how long it takes to assemble the full transaction file. Each step reduces risk on its own, and together they turn the $75,000 requirement into a managed control rather than a surprise.

Related practice areas for this work include Freight Broker Consulting, Transportation Accounting Integration, Reporting, and Document AI Automation. Each practice page describes scope, deliverables, and how an engagement starts with a short discovery call.

How Strong Tower Consulting Helps

Strong Tower Consulting helps brokers turn a regulatory requirement into a working system inside the TMS and accounting stack rather than a side spreadsheet that only one person understands. The work starts with a data inventory of carrier payables, documents, and security records, moves to a controlled pilot on one team or customer group, and expands with reports that operations, finance, and leadership can all read. Strong Tower Consulting, LLC and Exspeedite LLC are separately organized sister companies under common ownership. That separation keeps consulting advice vendor neutral and focused on the brokerage operation.

To review your bond tracking, payable aging, and claim readiness, contact us or call 763-244-1373 and ask for Scott Elliott. A short call is enough to map the first pilot and the gaps to close before a carrier, a surety, or FMCSA asks for proof.

Frequently Asked Questions