It's Thursday afternoon, which means your operations lead has the dispatch board open in one window, the GPS tracking portal in another, and a billing spreadsheet in a third, and she's about to lose the rest of her day to making them agree. A driver ran a load on Monday that dispatch shows as completed, tracking shows arriving forty minutes after the appointment, and billing shows nothing at all because nobody keyed it in yet. Multiply that by every load this week. By Friday she'll have a clean invoice run. She'll also have spent a full day doing it, and three loads will still bill wrong because the data never lined up.
This is how most carriers and fleet operators in the $5M to $40M range actually run. Three systems that each do their job competently and refuse to acknowledge each other exist. The reconciliation between them isn't a task. It's a salary.
Three systems, three truths
A load moves through your business as a single event. Your software experiences it as three separate, disconnected records that have to be manually matched.
Dispatch is where the load is born: customer, origin, destination, rate, driver assignment. It's the planning truth. Tracking is where the load actually happens: where the truck is, when it arrived, how long it sat at the dock, whether it ran on time. It's the operational truth. Billing is where the load becomes money: the invoice, the accessorials, the fuel surcharge, the detention. It's the financial truth.
Three truths about one load, in three systems, and the only thing connecting them is a human comparing screens. Dispatch doesn't know the truck sat two hours at the receiver, so it doesn't know you earned detention. Tracking doesn't know the agreed rate, so it can't tell you a load ran unprofitably. Billing doesn't know either, so it invoices whatever someone remembers to type, which means accessorials get missed and detention you're owed goes uncharged.
The reconcile is the tax you pay for that disconnection. A day a week of skilled operational labor — call it 50 hours a month — spent matching dispatch records to tracking events to billing lines. At a loaded rate that's $40k to $60k a year. And like every reconciliation tax, the visible cost is the smaller cost. The bigger cost is the revenue that leaks through the gaps: the detention nobody billed, the accessorials nobody captured, the customer disputes you can't win because your three systems tell three slightly different stories and none of them is airtight.
The integration gaps that cost real money
Look closely at where the money actually leaks and it's always at a seam between two systems.
Detention and accessorials. The truck sat three hours at a dock. Tracking knows this precisely — it has the arrival and departure timestamps. Billing has no idea, because tracking and billing don't share data. So whether you bill the detention depends on whether a dispatcher noticed and remembered to flag it. Most don't, most of the time. That's revenue you earned, documented in one system, and never collected because it couldn't reach the other.
Disputed deliveries. A customer claims the load was late and short-pays. To defend the charge you need the arrival timestamp, the appointment window, the proof of delivery, and the rate confirmation — and those live in three different systems with no shared record tying them to the load. So the dispute takes an hour to assemble a defense for, and half the time you eat the short-pay because assembling it costs more than the charge.
Profitability per load. You'd love to know which lanes, customers, and drivers actually make money. That requires rate (dispatch), actual cost and time (tracking), and what got collected (billing) on the same record. They're never on the same record. So you run the business on lane-level gut feel and find out at year-end which customer relationships were quietly underwater the whole time.
None of this is a discipline failure. You can hire the sharpest ops manager in the region and the detention still goes uncaptured, because the timestamp that proves it lives in a system that has no wire to the invoice. The person isn't the bottleneck. The missing wire is.
Real-time visibility, one model
The fix is a platform where dispatch, tracking, and billing aren't three apps you reconcile but three views of one record. A load is a single object that carries its plan, its actuals, and its money together, and updates all three as it moves.
Here's what that changes on the ground.
A load is one record from quote to cash. Created at dispatch with its customer and rate, enriched in transit with arrival times and dwell, closed out into a billing line that already knows the base rate, the detention the system clocked, and the accessorials that triggered. Nobody re-keys anything between stages. The Friday invoice run stops being a reconstruction and becomes a review.
Detention bills itself from the timestamps. Because tracking and billing share a model, dwell time over the free window automatically generates a detention line on the invoice draft. You approve it before it goes out. But it never silently disappears, because no human had to notice it — the system did, the moment the truck pulled away.
Disputes get won from one screen. A short-pay comes in, you open the load, and the appointment window, the actual arrival, the proof of delivery, and the rate confirmation are all right there, on one record, timestamped and consistent. The dispute that used to take an hour to defend takes two minutes, and you stop eating charges you're entitled to.
Profitability is a report, not an autopsy. Margin by lane, by customer, by driver, by truck, computed from rate against actual cost and time on the shared record. The unprofitable customer shows up in March, while you can still renegotiate or walk, instead of in the year-end review when the damage is already done.
The real-time piece matters most for the thing dispatchers do all day: answering "where's my freight." When tracking, dispatch, and the customer-facing view are the same data, a customer's status question gets answered in seconds from one screen — not by tabbing between a tracking portal and a dispatch board and translating between them.
What fixed looks like
Fixed is Thursday afternoon with no reconcile, because there's nothing to reconcile. The dispatch record, the tracking events, and the billing line are the same record. Your ops lead spends the day she used to spend matching screens on the work that actually grows the business: tightening lanes, solving carrier capacity, handling the exceptions that genuinely need a human.
Fixed is an invoice run that's a review and an approval, not a daylong reconstruction. The accessorials are already on it. The detention is already on it. You're checking, not building.
Fixed is winning the short-pay dispute because the proof is one click away and internally consistent. It's knowing on a Tuesday in spring that a customer relationship is underwater, while you can still do something about it. It's a dispatcher answering "where's load 4471" in five seconds instead of two minutes of tab-switching.
This is for you if
You run a carrier, a fleet, or a logistics operation doing roughly $5M to $40M a year, with the load count to match — enough volume that a day-a-week reconcile is a real position and uncaptured detention is real money. You're running dispatch, tracking, and billing as separate systems that don't share data. You've eaten short-pays you should have won and missed accessorials you should have billed, and you suspect — but can't prove — that some of your lanes lose money.
A targeted build that closes one seam — say, automatic detention and accessorial capture from tracking into billing — starts around $25k. A platform that unifies dispatch, tracking, and billing on one model runs $50k to $100k+ depending on fleet size, EDI and customer-portal requirements, integrations with ELD and telematics providers, and multi-terminal complexity. We start with a scoping session that puts the real number and the real timeline in writing before anyone builds anything.
This is not for you if you're a single-system shop looking for a marginally nicer dispatch board, or if your volume is low enough that the reconcile is an hour, not a day. The platform earns its cost when the seams between your systems are leaking enough money to fund the build. If they aren't yet, keep the spreadsheet — and come back when they are.