| This article is part of our series on Custom Freight Brokerage TMS Development for US Freight Brokers and 3PLs: Building a Load Carrier Vetting and Settlement Platform |
Introduction — Five Surfaces With a Live Rulemaking Attached
Five compliance surfaces affect how a broker platform gets built. The first is operational authority and financial responsibility. The second is the broker transaction record every broker must maintain. The third is fraud controls and unauthorized re-brokering controls. The fourth is the documentation needed for carrier selection. The fifth is how driver location and HOS data will be handled.
There is one of these that has an actual live regulatory component to it that really dictates what the software can do. The broker transaction record requirement is one that has actually gone through rulemaking on what it means to make these records electronic, the timeliness of their availability, and whether the right to inspect the records can be waived in a contract. This takes an obligation and makes it a real product requirement, which is why compliance requirements should be defined early in custom software development for a freight brokerage platform.
There is genuine controversy around transparency in brokered transactions between the brokerage industry and carrier/owner-operator groups. This piece discusses the obligation as it currently exists, without taking a stance on whether it should be there at all, let alone in its current or proposed form.
This article is written for educational purposes and does not constitute legal advice; confirm your specific obligations with transportation regulatory counsel before treating anything here as final guidance.
See our other piece about freight brokerage TMS features to see how these obligations become product requirements, and see custom software development for freight brokerage TMS and web application development for shipper and carrier portals where this compliance layer fits in.
Broker Authority Financial Responsibility and Process Agents
Facilitating transportation for compensation is done using authority granted to property brokers under federal laws. The distinction lies in the fact that the authority provided to property brokers differs from freight forwarder authority and from motor carrier operating authority. There are two aspects in which this distinction becomes important both for the compliance position of the brokerage itself and for the determination of what a carrier calling itself a carrier is authorized to do.
The financial responsibility is established by means of surety bond (Form BMC-84) or trust fund (Form BMC-85) at the level required by the federal law and process agents should be appointed for providing services in every state the brokerage does operations. At the moment, the requirement to establish financial security is $75,000 in available financial security at all times, according to MAP-21 and 49 CFR 387.307.
This amount of money was not changed recently, yet the procedure has been modified. As per new rules that will be applied starting in 2026, the providers of surety and trust must inform FMCSA about claims reducing available financial security below the $75,000 limit, and the brokerage usually gets seven business days to replenish it to avoid suspension of the operating authority. Moreover, FMCSA has narrowed down the list of acceptable assets for BMC-85 trust, so the number of brokers who use trust funds instead of surety bonds is likely to reduce substantially. Check the current requirements, thresholds, and effective dates with FMCSA or counsel rather than relying on any summaries, because details of implementation are still changing.
As far as the platform is concerned, there are two implications. First, the compliance status of the brokerage must be monitored constantly. Second, the authorization status of the carriers must be checked periodically rather than just once when the carrier is onboarded.
The Transaction Record and the Transparency Question
It is required that the broker keeps a record of all transactions according to federal regulation. In 49 CFR 371.3, the contents that are currently required include parties to the transaction, bill of lading or freight bill number, amount of compensation received for brokerage services performed, and amounts received from the shipper and paid to the carrier. These records are kept for a certain period of time and each party to a transaction has the right to review its records.
The right of record review has been subject to a large amount of regulatory activity in recent years. In November 2024, the FMCSA issued a Notice of Proposed Rulemaking on Transparency in Property Broker Transactions following petitions that date back to 2020 from the Owner-Operator Independent Drivers Association and the Small Business in Transportation Coalition. The proposal would require electronic record keeping, would expand the scope of what the record would include, would set a 48 hour period within which the record would be provided upon request, and would clarify whether a property broker is allowed to ask a carrier to waive its rights of record review as a prerequisite to conducting business. At this time, it has been announced that FMCSA is preparing a second notice of proposed rulemaking prior to issuing the final rule. Verify current requirements and effective dates with the FMCSA before the rule is published or finalized architecture of a product.
Here’s why this matters to a software project rather than only to a compliance officer. If a brokerage must be able to produce a complete transaction record within a defined, short window on request, that’s a product requirement, not a policy statement. It shapes what the platform stores, how tightly a load links to its financial records, and whether producing the record on demand is a simple query or a week of manual assembly across systems that don’t talk to each other. Design for production on demand regardless of exactly where the rule ultimately settles. That capability is worth having whether or not the 48-hour window becomes binding.
Double-Brokering and Fraud Controls
Fraudulent entities obtain or acquire operating authority and present themselves as established carriers, often by impersonating a real, legitimately authorized carrier and using its name and identifiers with substituted contact details. A load gets accepted and is then either re-brokered without authorization or the freight is taken outright. The shipper loses the freight. The impersonated carrier, frequently a very small business with limited resources to fight back, loses its reputation and a great deal of time sorting out the damage. That’s the mechanism, stated plainly, without needing further dramatizing.
A useful set of controls belongs in the vetting workflow itself rather than bolted on afterward. Contact details should be verified against the carrier’s authority record rather than accepted at face value from whoever makes contact. Recent changes to a carrier’s registered information should be surfaced as a signal worth a second look. Identity verification should be proportionate to the load being tendered. Confirmation at pickup should establish that the driver and equipment on site match what was arranged. Continuous monitoring after onboarding means a change is noticed rather than discovered after the fact. Payment routing should never be redirected without verification through a known independently confirmed channel.
The platform should never build features that would facilitate streamline or obscure unauthorized re-brokering. Where co-brokering is legitimate it’s governed by the specific broker-carrier agreement in place and by the authority requirements attached to each party, and any capability supporting it should make those constraints explicit within the workflow rather than assume them away in the background.
Carrier Selection and the Documentation That Defends It
If a particular load leads to an accident or a loss, claims can be filed against the brokerage because the latter selected the carrier negligently. The law concerning such claims is rather unsettled; courts have reached different conclusions on various issues, including how much of the federal preemption under 49 U.S.C. § 14501(c) applies to this situation. This article does not attempt to resolve that legal question, and the product roadmap does not depend on its resolution.
However, one thing will remain stable regardless of how the legal landscape changes — the position in which the brokerage wants to be. A brokerage that could demonstrate that it had consistent written criteria to evaluate the carrier before tendering a load, performed checks and noted the findings, and made a documented decision will be in a completely different position than a company that cannot provide any of these documents.
Thus, the task that the software will perform in this case is quite clear and limited. Carrier selection criteria should be defined within the system rather than kept in one person’s head. Checks should be recorded, including their source and the time when they were done. Approval of the carrier should be recorded, as well as the rationale behind it.
It can be stored for several years, just in case, depending on the statute of limitations. Scoring and ranking by the system can facilitate the process, but decision-making is still the responsibility of a person.
Hours-of-Service Data Driver Privacy and the Coercion Rule
E-loggers have created new ways to provide hours-of-service data in ways that were impossible previously, and brokerages which receive location and availability data must be careful about the data about a driver provided by a carrier with consent from the carrier.
This approach will have implications for retention and access, as well as for the purposes of the brokerage once it has the data in hand. To treat driver location as personal data about the person as opposed to shipment telemetry is not just the right legal approach, but also better for the relationship with the carrier network a brokerage needs.
Where the platform also includes carrier document capture, consent collection, or driver-facing workflows, custom mobile app development can provide a purpose-built interface for handling those activities securely in the field.
What is frequently overlooked in broker-oriented materials must be stated clearly. Coercion provision 49 CFR 390.6 bans coercion of drivers to violate federal safety laws, including the HOS rules, and it bans this for brokers and other transportation intermediaries, and not just motor carriers. A driver who reports that a proposed schedule would violate a regulation and faces some negative consequences for declining to comply can bring a coercion case against anyone in this chain, including a broker.
The software relevance here is real, not theoretical. Appointment scheduling, detention handling, and dispatch communication are exactly where pressure gets applied in practice. A platform that surfaces timing realities clearly helps everyone make better decisions. A platform that builds urgency or pressure into the workflow itself does not, and it creates exposure. Never describe features that push a driver toward running beyond available hours, and never present compressed transit expectations as a product benefit in marketing or in the interface itself.
Cargo Claims Insurance and Specialized Freight
Cargo claims handling depends on documentation — the platform is well positioned to preserve the bill of lading, delivery receipts with any exceptions noted at the time, photographs, and the full correspondence trail. Claims often arrive months after delivery, which makes retention and retrievability the actual requirement, not speed of initial capture alone.
Insurance verification for carriers is both a vetting matter and a continuing one, since coverage can cancel well after onboarding without anyone noticing unless the system is watching for it. Contingent cargo and broker’s own liability coverage sit on the brokerage’s side of the relationship separately.
Specialized freight carries additional obligations worth flagging even briefly. Transportation of human or animal food may bring responsibilities under the FDA’s sanitary transportation requirements, and hazardous materials or temperature-controlled freight each come with their own distinct regulatory regimes. Each of these translates into specific fields, checks, and documentation the platform either captures accurately at the time or ends up reconstructing badly, and incompletely, much later. Verify what applies to your specific freight mix with counsel before finalizing scope.
Final Thoughts
Brokerages that design the transaction record for production on demand, build fraud controls into the vetting workflow itself rather than around it, document carrier selection against written criteria consistently, and treat driver data and dispatch pressure with the care the regulations actually require tend to end up with platforms that answer hard questions rather than complicate them further. Confirm your specific obligations with transportation regulatory counsel before treating anything here as final guidance.
If you’re scoping a platform that will arrange transportation and hold the transaction record, settling your record production requirement and your vetting documentation standard before architecture is fixed is the step that keeps compliance from becoming a rebuild later. More on how this fits into a full platform build is at NewAgesysIT. Learn more about digital transformation solutions from one of the leading AI software companies in the United States.
