Posted margin and actual margin are two different numbers
Every freight broker knows the difference between the number in the TMS at load cover and the number on the P&L at month-close. That gap has a name inside every broker's office and it is usually some variant of margin leak. Accessorials that were not billed to the shipper. Detention that the driver invoiced and the shipper disputed. Layover charges the dispatcher forgot to log. Lumper fees paid out but never reimbursed. Claims deductions off the carrier invoice that hit the wrong load. Factoring fees applied at 3.5 percent instead of the negotiated 3.0 percent. Every one of these is a small hit. Aggregated across 400 to 2,000 loads per month, they compound into 0.8 to 2.4 points of gross margin that quietly disappears between cover and close.
The reason it works this way is not that brokerage TMS platforms are bad. It is that per-load margin reconciliation is a labor-intensive human workflow that most brokerages cannot afford to run in real time. Reconciling every accessorial, every claim, every fee, every dispute against every carrier invoice and every shipper billing requires either a person or an AI. Most brokerages have neither and settle for the batch reconciliation that accounting runs at month-close, by which point the margin leak is a report, not a lever.
MiOpsAI's Finance chair runs this reconciliation continuously. Every carrier invoice, every accessorial charge, every claim deduction, every factoring statement, every shipper billing gets ingested, matched to the correct load, reconciled against the expected values, and reflected in real-time per-load margin within hours of arrival. Margin drift on the current week's loads is visible on Monday, not month-end.
What the Finance chair reconciles per load
Every load has a set of expected financial events at cover: shipper billing at the agreed rate, carrier payment at the agreed rate, factoring fee at the agreed factor rate if the carrier is factored, and standard accessorial expectations (fuel surcharge, detention if applicable). The Finance chair matches every actual financial event to these expectations. Shipper billing gets compared to agreed rate plus any documented rate changes. Carrier invoice gets compared to agreed pay plus any documented accessorial approvals. Factoring statement gets compared to agreed factor terms. Any deviation (shipper short-pay, carrier over-invoice, accessorial dispute, factor fee variance) is flagged for dispatcher or accounting review the same day it appears.
The reconciled per-load margin updates continuously. A broker or lane manager can pull up any load and see the true margin as-of the last reconciliation, with the source detail on any variance. Aggregation rolls up cleanly: by lane, by shipper, by carrier, by dispatcher, by equipment type, by any dimension the brokerage tracks. See how the Command Center handles this.
The accessorial capture problem that eats the most margin
Accessorials are the single largest source of margin leak in most freight brokerages. Detention, layover, driver assist, lumper, dry-run, TONU (truck ordered not used), reconsignment, and other accessorial events happen constantly and get logged inconsistently. A dispatcher tells the driver yeah I will get you 4 hours of detention paid, the load moves on, the dispatcher forgets to log the accessorial, the carrier invoices for it, the brokerage pays the carrier, the shipper is never billed, and the brokerage eats the accessorial as a margin hit.
LizziAI catches this at the operational level. Every driver text or dispatcher note that mentions detention time, layover, or any other accessorial event triggers a draft accessorial log entry for dispatcher confirmation within 30 minutes. Once confirmed, the accessorial is queued for shipper billing on the load close-out cycle. If the shipper disputes, the dispute goes into the Finance chair's queue with the source documentation (driver text, dispatcher note, timestamps) attached. This is one of the fastest ROI wins on a brokerage MiOpsAI deployment because most brokerages know they are leaking accessorial revenue and cannot quantify it until the reconciliation layer runs.
The claim reconciliation that stops silently deducting
Claims deductions on carrier invoices are the second largest silent margin leak. A carrier delivers with concealed damage, the shipper claims $850 against the carrier, the carrier's factor deducts the $850 from the next batch of invoices, the brokerage receives a factor statement with the deduction embedded, and the deduction gets absorbed against unrelated loads if nobody reconciles it back to the specific claim load. Multiply by dozens of claims a month and the margin impact is real.
The Finance chair matches every claim deduction to the source claim record and the specific load it applies to. Discrepancies (deduction amount does not match claim amount, deduction applied to wrong load, deduction applied after claim was resolved) are flagged for accounting review. Unresolved claims older than the brokerage's aging thresholds are surfaced for dispatcher or claims manager follow-up. Nothing gets silently absorbed. The reconciliation history is preserved so audit or dispute conversations have documented data.
The dispatcher scorecard that follows real margin
Most brokerage dispatcher scorecards run on gross margin at cover, which is the wrong number to score on. A dispatcher who covers loads at 18 percent gross margin at cover and consistently leaks 3 points to unrecovered accessorials, unresolved claims, and factor variances is delivering 15 percent actual margin, which is worse than a dispatcher covering at 16 percent with clean reconciliation. Scoring on the wrong number rewards the wrong behaviors and reinforces the leaks.
The Finance chair produces true per-dispatcher scorecards on actual margin, with the specific leak categories called out per dispatcher. Dispatchers who consistently miss accessorial capture get coaching on that specific pattern. Dispatchers with high claims incidence get support on the claims-prevention side. Dispatchers who cover at lower posted margin but hold clean actual margin get recognized for the work they do that would otherwise be invisible. This is the compensation-and-coaching data that a brokerage needs to actually improve, and it only becomes available once margin is reconciled in real time.
What this costs and what it recovers
MiOpsAI Growth plan is $299 per month. Finance chair is $250 per month. Most brokerages add the Operations chair for another $250 per month to handle the associated documentation and dispatch workflow that feeds the margin picture. Total ongoing cost around $800 per month for real-time per-load margin reconciliation.
Take a mid-sized brokerage doing $40 million per year at 15 percent posted gross margin. That is $6 million gross margin. A 1.5-point margin leak (which is on the lower end of what we typically see) is $600,000 per year of quietly absorbed margin. Recovering even a third of that leak in year one is $200,000. Recovering half is $300,000. Against a $9,600 per year platform cost, the ROI math is not close. See the pricing page for full plan details. Cancellation requires 60-day written notice.
How this plays with your TMS
MiOpsAI does not replace McLeod, Aljex, Tailwind, Turvo, or whatever brokerage TMS you run. The TMS stays as your load lifecycle and financial system of record. MiOpsAI's Finance chair operates on the reconciliation layer that sits between the TMS's transaction records and the accounting system's ledger, producing reconciled per-load records that hand off cleanly. Integration is at the read-write level for load status, invoice, and payment data. Your controller keeps the accounting system they know.
Frequently asked questions
Does this replace our TMS or our accounting system?
Neither. TMS stays as load lifecycle system of record. Accounting stays as general ledger. MiOpsAI's Finance chair runs the reconciliation layer between them, producing per-load margin data in real time that the TMS does not compute and the accounting system does not surface until batch close.
How does this handle factoring companies?
Factor statements are ingested and reconciled against expected factor terms for each carrier. Variances (rate changes, chargebacks, disputed advances) are flagged for accounting review. NOA changes, ACH routing updates, and factor-related communications are drafted by LizziAI.
Can we run this on contract lanes and spot lanes together?Yes. Contract lanes have expected rates and lane-level performance targets that feed the reconciliation. Spot lanes reconcile against the specific negotiated rate per load. Both types roll into the same per-load margin picture with lane-type filters available on all reports.What about international loads and cross-border freight?Cross-border reconciliation supports currency conversion, customs fees, and border-specific accessorials. The workflow is essentially the same; setup includes the additional line-item categories that cross-border freight requires.How does this handle claims that take months to resolve?Long-running claims stay in the Finance chair's aging queue with expected resolution timeline tracked. Deductions applied against the load are held in a reserve status until claim resolution, then either absorbed permanently or reversed based on the resolution outcome. Nothing gets silently absorbed just because a claim ran long.How do I get started?
How does this handle claims that take months to resolve?Long-running claims stay in the Finance chair's aging queue with expected resolution timeline tracked. Deductions applied against the load are held in a reserve status until claim resolution, then either absorbed permanently or reversed based on the resolution outcome. Nothing gets silently absorbed just because a claim ran long.How do I get started?
Growth plan is $299 per month. Finance chair is $250 per month. Most brokerages run Finance and Operations chairs together for $800 per month total. Request access. See the brokerage CRM page or the driver recruiting page for adjacent logistics workflows.