49 CFR 371.3 is one of the most frequently cited but least understood FMCSA regulations governing freight brokers. The rule requires every broker to maintain a complete record of each transaction for three years and to make those records available to any party to the shipment upon written request. For motor carriers, this creates a practical right to verify that the broker is accurately reporting line-haul rates, fuel surcharges, detention, and any other accessorials that affect their settlement.
Strong Tower Consulting regularly assists both carriers and brokers in designing Transportation Management Systems (TMS) that satisfy this requirement without creating operational drag. The key is to treat 49 CFR 371.3 compliance as a data-architecture decision rather than a document-storage problem.
What 49 CFR 371.3 Actually Requires
The regulation mandates that a broker keep, for a period of three years:
- Name and address of the shipper
- Name and address of the carrier
- Bill of lading or freight bill number
- Amount of compensation received by the broker for the transaction
- A description of any other charges or allowances
These records must be made available for inspection by any party to the transaction. The broker cannot charge a fee for providing the records, and the response must occur within a reasonable period after receiving a written request.
| Record Element | Typical Source Document | Recommended TMS Storage | Audit Consideration |
|---|---|---|---|
| Shipper name and address | EDI 204 or load entry screen | Normalized shipper table with immutable snapshot at time of booking | Foreign key to load header |
| Carrier name and address | EDI 204 or carrier selection | Normalized carrier table with snapshot of record at tender | Must match settlement record |
| Bill of lading or freight bill number | BOL or PRO number | Load-level reference field with index | Used as primary search key for carrier requests |
| Broker compensation | Invoice to shipper minus carrier pay | Separate broker_revenue and carrier_pay tables with line-item detail | Must reconcile to settlement file |
| Other charges and allowances | Accessorials (detention, fuel, lumper, etc.) | Accessorial ledger linked to load ID with type, amount, and party responsible | Critical for carrier disputes |
How a Carrier Should Request Records
A carrier should send a written request (email is acceptable if it clearly states it is a 49 CFR 371.3 request) that includes the specific load or loads in question. Best practice is to reference the PRO number, BOL number, or load identifier used by the broker. The request should specify the time period and the exact records sought. Carriers using Truckmate, McLeod, or TMW Systems can generate these requests directly from their settlement or accounts-payable module.
Once the broker responds, the carrier should compare the compensation and accessorial breakdown against its own settlement records. Common discrepancies involve fuel surcharges that were collected from the shipper but not passed through, or detention time that was billed but never paid to the driver.
TMS Architecture That Satisfies 49 CFR 371.3
A compliant TMS must treat every load as an immutable transaction. When a carrier is selected and the EDI 204 is transmitted, the system should create a permanent snapshot of the agreed rate, fuel surcharge formula, and accessorial rules. Later changes (EDI 214 status updates, detention claims, or rate adjustments) must be recorded as separate journal entries rather than overwriting the original agreement.
Recommended SQL schema elements include:
loadstable with load_id, bol_number, shipper_id, carrier_id, tender_datebroker_revenuetable with line-item detail for all charges billed to the shippercarrier_paytable with line-item detail for all amounts owed to the carrieraccessorialstable with type, amount, party_responsible, and approval_statusaudit_logtable that records every change with user, timestamp, and before/after values
This structure allows a broker to instantly retrieve the complete transaction file when a carrier submits a 49 CFR 371.3 request. It also supports automated generation of the response package as a PDF or secure download link.
Operational Workflow for Brokers
When a written request arrives, the brokerage operations team should:
- Search the TMS by BOL, PRO, or load number
- Export the complete transaction packet (load header, revenue detail, pay detail, accessorial ledger, and relevant EDI 210/214 transactions)
- Attach any scanned BOL or proof of delivery documents stored in the document management system
- Deliver the package to the requesting carrier within five business days
Modern systems such as those built on McLeod, TMW, or custom SQL-based platforms can automate most of this workflow through saved queries and report templates.
Common Pitfalls to Avoid
Many brokers store compensation data only in accounting exports or PDF invoices. This creates significant effort when a carrier requests records because the data must be manually reconstructed. A properly designed TMS stores the information relationally from the moment the load is booked, eliminating reconstruction and reducing audit risk.
Another frequent issue is the failure to retain the original rate confirmation details once the load is settled. Under 49 CFR 371.3 the broker must be able to produce the original agreement even if rates were later adjusted through a supplemental invoice.
FAQ
What records must a freight broker maintain under 49 CFR 371.3?
A broker must keep a written or electronic record of each transaction for three years. The record must include the name and address of the shipper, the name and address of the carrier, the bill of lading or freight bill number, the amount of compensation received by the broker, and a description of any other charges or allowances.
Who has the right to review a broker's transaction records?
The shipper, the carrier, and any other party to the transaction has the right to review the broker's records that pertain to their shipment. The broker must make these records available within a reasonable period of time upon written request.
How should a TMS store broker records to satisfy 49 CFR 371.3?
The TMS should store shipper details, carrier details, bill of lading number, load-specific charges, broker compensation (including any accessorials, fuel surcharges, or detention), and all related EDI 204/214/210 transactions in an auditable, queryable SQL schema with immutable audit logs and date-based retention policies.
How should a broker respond to a carrier record request?
Upon receipt of a written request, the broker must produce the complete transaction file within a reasonable time. This includes exporting the relevant load record, compensation breakdown, and supporting documents from the TMS in a readable format such as PDF or CSV.
Strong Tower Consulting, LLC and Exspeedite LLC are separately organized sister companies under common ownership. Strong Tower Consulting provides independent systems architecture and technology advisory. Carriers never have to buy our software. Our only product is better decisions.
Schedule a systems assessment with Strong Tower Consulting at 763-244-1373 to evaluate how your TMS handles brokerage compliance, record retention, and carrier transparency requirements.