One settlement, a dozen deductions
Open a settlement statement from a carrier or dispatch service and the layout is rarely simple. Gross revenue for the period sits at the top, followed by a long column of deductions — fuel advances, dispatch commission, cargo and liability insurance, escrow contributions, ELD or tech fees, base plate and permit costs, a truck lease payment where one applies — before finally arriving at the net figure that actually clears the bank. Every carrier lays this out a little differently, and no two settlement statements use quite the same column names for the same underlying deductions.
Answering the question every owner-operator eventually asks — did this settlement actually reflect what I hauled, at the rate I expected, minus only the deductions that were actually mine — means reading the statement line by line and checking it against the deposit. The bank statement alone can't answer it; the deposit is just one net number with nothing behind it.
Why a settlement statement is harder to read than it looks
A settlement statement carries more structure than most financial documents an owner-operator deals with, and that structure varies enough from carrier to carrier that a method built around one statement's layout tends to break on the next.
The net deposit is already net of everything
Fuel advances, dispatch fees, insurance and escrow are all deducted before the money ever reaches the bank — the deposit is the last step in a long chain, not a starting point.
A settlement period rarely matches a calendar period
A settlement covers whatever window the carrier defines — weekly for most, biweekly for some — which almost never lines up neatly with a calendar month pulled for tax or budgeting purposes.
Escrow and reserves get held back and released later
A carrier can hold back part of a settlement as a maintenance reserve or security deposit, releasing it weeks or months later as a separate, unrelated-looking deposit.
Multiple carriers or brokers means multiple formats
A driver running under more than one authority, or picking up occasional broker-direct loads, ends up with settlement statements that structure the same concepts — gross revenue, fuel, dispatch fee — completely differently.
None of these four are a carrier being unreasonable — they're the normal shape of how a settlement gets assembled, and they're exactly why comparing a bank deposit against a rough sense of what a week should have brought in rarely produces a confident answer, no matter how experienced the driver doing the comparing is. Reading the settlement statement itself, rather than relying on that rough sense, is the only way to know for certain — and it's a habit that gets faster every settlement cycle, not slower.
What this doesn't do, stated up front
Doesn't calculate what deductions should be
Dispatch commission rates, insurance premiums and fuel surcharges are set by the carrier or lease agreement. This confirms the deductions the statement actually charged add up to the net payout — it doesn't audit whether the rate itself was fair.
Doesn't connect to a carrier's driver portal or dispatch system
There's no API, no login, no integration. You download the settlement statement yourself, the same way you already do, and upload it.
Doesn't calculate or file IFTA fuel tax
IFTA reporting is a separate quarterly filing based on miles driven per state. This reads what the settlement and fuel card statement show — it doesn't calculate or file the return.
Doesn't dispute a deduction with the carrier
If a fee genuinely looks wrong, raising it with the carrier is a step you take — this surfaces the discrepancy clearly enough to make that conversation possible.
What's left is narrow, and it's exactly the part that eats an evening every settlement cycle: turning a statement full of deductions into a clear answer about what the payout actually represents.
What gets read
| Field | Source |
|---|---|
| Gross revenue per load or period | Settlement statement |
| Fuel advances and fuel card deductions | Settlement statement, fuel card statement |
| Dispatch fee, insurance, escrow | Settlement statement |
| Truck lease or finance payment | Settlement statement |
| Net deposit amount and date | Bank statement |
Five sources of truth, read as they actually exist — not summarized from memory, and not assumed to agree with each other until the matching step actually checks.
How a deduction gets categorized
Categorization runs on the deduction's description together with its amount and its position on the statement — not a single keyword match, because the same short label can mean different things depending on the carrier.
| Category | Typical deduction |
|---|---|
| Fuel | Fuel card advance, in-house fuel purchase |
| Dispatch and commission | Load booking fee, factoring fee |
| Insurance | Cargo, liability, occupational accident |
| Escrow and reserve | Maintenance reserve, security deposit |
| Equipment | Truck lease, trailer rental, ELD or tech fee |
A deduction that fits cleanly into one of these lands with high confidence. One that doesn't — an unlabeled adjustment, or a fee that could plausibly belong to two categories — is flagged for a quick manual confirm rather than guessed at silently.
A settlement period, reconciled
A one-week settlement covering six loads for an owner-operator leased to a mid-size carrier.
| Line | Amount |
|---|---|
| Gross revenue, 6 loads | $8,940 |
| Fuel card deductions | −$1,860 |
| Dispatch fee, 8% | −$715 |
| Insurance and escrow | −$420 |
| Net settlement deposited | $5,945 |
The $5,945 deposit on the bank statement, taken alone, tells the driver nothing about whether $8,940 of gross revenue is a plausible figure for six loads. Read alongside the settlement statement, every deduction lands in its own category, and the deposit is confirmed to equal gross revenue minus all four deduction types — a genuine reconciliation rather than an assumption that the number looked roughly right.
How it works
Upload the settlement statement and fuel card statement
Whatever the carrier and fuel card provider issue, plus the bank statement covering the payout date.
Every line item is read
Gross revenue, fuel, dispatch fee and every other deduction, kept linked to the statement it came from.
Matched against the net deposit
By total and timing together, with a confidence level per line.
Export
Excel, CSV or JSON — every deduction category kept as a separate, clearly labeled column.
Fuel card advances and deductions
Most owner-operators run fuel through a company-issued fuel card — a Comdata, EFS or similar account that advances fuel purchases at the pump and settles the total against the carrier settlement. The settlement statement usually shows only a lump fuel deduction, with the actual station-by-station detail living on a separate fuel card statement.
Reading the fuel card statement alongside the settlement closes that gap — every fuel purchase is read as its own line, and the settlement's lump fuel deduction is confirmed against the sum of the individual purchases. The detail behind that matching is covered in fuel card and deduction matching.
Escrow and maintenance reserve
Many lease-on agreements require an owner-operator to build up an escrow balance or maintenance reserve — a small percentage held back from each settlement, accumulated as a buffer against repair costs or as security under the lease, released in full or in part when the contract ends.
A held reserve is read from the settlement statement as its own line item and tracked as pending rather than treated as a missing or short deposit. Where the statement shows a running escrow balance, that balance is carried forward across settlements, so the driver has a running answer to how much is currently held without adding up every prior statement by hand.
Load-level detail inside a period settlement
A weekly or biweekly settlement almost always covers several loads at once, and a carrier's statement usually lists each load's gross revenue as its own line before rolling everything into one period total. That load-level detail is read and kept intact rather than collapsed into a single figure — useful for a driver who wants to see which loads actually paid well and which barely covered fuel.
For a driver who wants the settlement statement itself broken down purely by load, rather than as part of a broader deduction reconciliation, the same load-level reading is covered from that angle in load settlement statement to Excel.
More than one truck on the same account
A small fleet running two or three trucks under the same authority, or an owner-operator who has added a second truck with a hired driver, ends up with multiple settlement statements arriving on the same schedule — each truck's own gross revenue, fuel and deductions, sometimes summarized together on one combined statement from the carrier.
Each truck's settlements are read and kept as their own export rather than merged into one undifferentiated total, so a truck that's underperforming is visible on its own rather than hidden inside a fleet-wide average.
Who this is for
Owner-operators leased to a carrier
A settlement confirmed against the statement instead of trusted on faith every week.
Small fleets running two or more trucks
One consistent reconciliation process across every truck, not a separate manual check per driver.
Bookkeepers serving trucking clients
The same matching method applied regardless of which carrier's settlement format a client happens to use.
Owner-operators considering a new lease-on
A clear settlement history that makes comparing two carriers' actual net payout straightforward.
This isn't dispatch or ELD software
Worth being precise about the boundary. This doesn't book loads, track hours of service, or connect to an ELD. There's no login to any dispatch system. What it reads is the financial side — the settlement statement and fuel card statement, the same documents a driver already receives every settlement cycle, turned into clean, categorized numbers.
Moving from a folder of paper settlements
Most drivers who reach for this have been keeping settlement statements the way the industry always has — a folder in the cab, a shoebox of printed statements, or a spreadsheet updated in batches whenever tax season or a factoring application forces the issue. It works, in the sense that the numbers eventually get assembled, but it's slow, and it catches nothing subtle: a dispatch fee that crept up, an escrow balance that was never released, a fuel deduction that doesn't match the card statement.
The transition doesn't require reorganizing anything on day one. A reasonable first step is running one settlement period through and comparing the categorized export against whatever rough total already existed, to see where the two agree and where the automatic reading catches something the manual count missed.
How often to reconcile
Matching your reconciliation cadence to the carrier's own settlement schedule is the simplest rule that actually works — weekly for most carriers, biweekly for some. Reconciling less often than settlements arrive means several statements pile up before anyone looks at any of them.
For a driver running more than one truck or leased to more than one carrier, it's often simpler to batch the reconciliation on a fixed weekly rhythm rather than chasing each settlement individually as it lands.
What accuracy actually looks like
A useful way to think about matching accuracy isn't a single percentage — it's the shape of the confidence distribution across deductions. A driver with a stable carrier and a consistent fuel card sees most deductions land at high confidence, with only a small tail needing review. A driver switching carriers mid-quarter, or running occasional broker-direct loads with their own paperwork, sees a larger medium-confidence tail — more review time, not necessarily more errors.
In practice, most owner-operators with one steady carrier see somewhere between 85% and 95% of deductions land at high confidence on a given settlement, with the rest split between a quick medium-confidence confirm and a small number of genuine discrepancies worth investigating individually.
Privacy
Uploads go over TLS, encrypted end to end.
Processing runs on EU-hosted infrastructure.
Original documents are deleted immediately after extraction.
Settlement and pay data are never used to train AI models.
Full details are on the security page.