Multi-carrier dispatch: keeping data, documents and pay separate

Why must each carrier client’s data stay separate?

Each carrier you serve is its own legal and operating entity with its own authority, insurance, customers and rates. Mixing their information causes four kinds of damage.

• Confidentiality. A rate agreed with one carrier’s customer is that carrier’s business. Showing it to another client, even by accident, can end a relationship.
• Wrong-party errors. A rate confirmation attached to the wrong load, or a driver messaged about the wrong carrier’s pickup, is a service failure that the carrier sees as yours.
• Painful exits. When a client leaves, you need to return their records and nothing else. If everything lives in one shared pile, separating it takes days.
• Weak audit trail. When a client questions a fee statement, you need to rebuild exactly what happened on their loads without wading through everyone else’s.

Records also carry regulatory weight for the carrier. A for-hire motor carrier has its own retention duties, and those duties do not move to the dispatcher by default. Agree in writing which party keeps which records, and make sure the carrier can always get its copies.

What does a “one carrier, one container” data model look like?

Whether you use spreadsheets or software, the structure is the same: every record carries a carrier identifier, and nothing is created without one. The table lists the records most dispatch operations hold and what should be shared across carriers versus owned by one.

In a spreadsheet this means one workbook or at least one tab group per carrier, with a consistent column layout so you can roll up totals for your own reporting. In software it means the system treats the carrier as the top-level boundary: a switcher to change client, a view across all clients for the owner, and the ability to restrict a user to a subset of clients. Ask any vendor to show you what happens when a restricted user searches for a load that belongs to a carrier they cannot see.

How should you organize documents for many carriers?

A document system should answer one question in under a minute: show me everything for this load. That requires consistent names and a fixed folder tree, because search stops working once volume grows.

• Folder tree. Carrier, then year, then load number. Do not nest by customer first; customers repeat across carriers.
• File names. Carrier code, load number, document type and date, in that order, for example ABC_104233_POD_2026-10-08. Sorting by name then groups every document for a load.
• Required set per load. Rate confirmation, BOL, POD, and receipts for lumper, detention or other accessorials. A load is not closed until the set is complete.
• One intake path. Documents arrive by driver scan, email or upload; decide where each lands and who files it. Personal inboxes are not a filing system.

On retention, FMCSA’s schedule in 49 CFR Part 379, Appendix A lists one year for bills of lading and for paid freight bills, and three years for several accounting records such as paid and cancelled vouchers and receivables registers. That schedule describes what regulated carriers should preserve; tax rules, contracts and insurers can require longer. Treat it as a minimum and ask the carrier’s accountant before you delete anything.

How do you separate fees, invoices and settlements?

Three different money flows run through a dispatch operation, and mixing them is the most expensive mistake in the business.

1. The carrier’s revenue. The customer or broker pays the carrier, or the carrier’s factoring company if it uses one. That money is the carrier’s.
2. Your fee. The carrier pays you under the service agreement. FMCSA’s 2023 guidance lists taking pay from a broker or factoring company, or sitting in the financial transaction between them and the carrier, as a factor pointing toward broker authority. Designing the flow so the carrier pays you keeps you on the safe side of that factor.
3. Driver pay. The carrier pays its own drivers, whether employees or owner-operators. Your involvement, if any, is preparing a draft for the carrier to approve.

Keep a separate ledger or at least a separate statement per carrier, and produce one fee statement per carrier per period. Each line should carry the load number, delivery date, the figure the fee was calculated on, the fee basis from the agreement, and the fee. A carrier that can reconcile your statement to its own load list in ten minutes will not question it.

If the carrier leases owner-operators, federal lease rules set deadlines and documentation duties on the carrier, including how quickly the owner-operator must be paid after submitting delivery documents. Those rules are covered in the trucking accounting basics guide. The point for a dispatcher is practical: late paperwork delays settlements, and settlement delays become the carrier’s legal problem.

Who should see which carrier’s information?

Apply least privilege: each person sees the carriers and screens their job requires, and no more. The matrix is an example to adapt, not a standard.

Record who changed what. When a rate or a driver assignment is edited, the history should show the person and the time. That log is what resolves a dispute quickly, and it deters casual edits.

How do you onboard and offboard a carrier cleanly?

Onboarding checklist

• Signed service agreement and the carrier’s contact for operations, billing and emergencies.
• Authority and insurance check against the FMCSA Licensing and Insurance carrier search, plus a look at the SAFER Company Snapshot for the carrier’s safety record.
• Driver and truck list with equipment types and home locations.
• The carrier’s factoring arrangement, if any, and where remittance instructions must point. Your process should work the same whether or not the carrier factors.
• Rate floors, preferred lanes, brokers to avoid, and communication rules.
• A test load run end to end before volume starts.

Offboarding checklist

• Agree the last dispatch date and a plan for loads still in transit.
• Issue the final fee statement and reconcile open items.
• Export the carrier’s complete load history and documents, and confirm they received them.
• Remove user access to that carrier and archive its container read-only.
• Record what you retain and why, in line with the agreement.

What is a sensible weekly rhythm across all carriers?

• Monday. One-page snapshot per carrier: trucks active, loads booked, open exceptions.
• Daily. Close the day with every delivered load showing its full document set, or a named owner for the gap.
• Thursday. Draft fee statements while memory is fresh and documents are in.
• Friday. Send statements, then review each carrier’s rate per loaded mile against its cost per mile.
• Monthly. Review whether any two carriers have drifted into overlapping equipment and lanes. If they have, revisit the allocation question described in the dispatch company operations guide.

What should you ask of software built for multiple carriers?

• Is the carrier a true boundary in the product, or just a tag on a load?
• Can I restrict a user to specific carriers, and can I prove it with a test login?
• Can I export one carrier’s full history, documents included, without touching the others?
• Does it produce a fee statement per carrier from the loads dispatched?
• Is there an audit trail of edits to rates and assignments?
• What is on the roadmap versus live today? Ask for the answer in writing.