A quarter of loads, one register
Haul freight for a quarter and the settlement statements pile up — one per period, each one a self-contained PDF with its own loads, its own rates and its own deductions, and no relationship to the statement before it or after it. Answering a simple question like "what did we average per mile this quarter" means opening every single settlement and adding it up by hand, because no individual statement was ever built to answer that question on its own.
A season register solves a different problem than reading any one settlement carefully — it's about taking every settlement, regardless of which carrier issued it or how its statement is laid out, and putting every load into the same running spreadsheet.
Why a stack of settlements doesn't add itself up
Every carrier's layout is different
A large fleet's settlement and a small regional carrier's handwritten statement carry the same underlying numbers — origin, destination, rate — in completely different formats, with no shared template to copy figures from.
One statement can be one load or a dozen
Some carriers settle every load separately; others batch a full week's hauling into one summary — a register has to handle both without double-counting or losing load-level detail.
Statements arrive on no fixed schedule relative to hauling
A settlement lands whenever the carrier's own cycle closes, which can mean several loads batched together or a single load settled on its own, with no consistent rhythm to plan around.
A revised statement can arrive weeks later
A correction to an earlier settlement — a reweighed load, a rate adjustment — needs to be reconciled against the original entry, not simply added as a new, disconnected line.
What this doesn't do, stated up front
Doesn't connect to a carrier's driver portal
There's no login, no API. You download or receive each settlement statement yourself, the way you already do, and upload it here.
Doesn't calculate load pricing or lane strategy advice
The register shows what was actually hauled and paid — deciding which lanes or brokers to run stays a business decision, not something this tool makes for you.
Doesn't audit whether a rate offered was competitive
It confirms the statement's own math is internally consistent — comparing rates across carriers or against a benchmark is a separate analysis.
What gets read
| Field | Kept as |
|---|---|
| Carrier or broker name | Its own column, per load |
| Pickup and delivery date | Sortable date fields |
| Origin and destination | Text fields per load |
| Gross rate and mileage | Numeric fields per load |
| Fuel, dispatch fee and other deductions | Separate deduction columns |
How it works
Upload settlement statements as they arrive, or all at once
Any carrier, any format — PDF, scan or fax.
Every load is read
Origin, destination, rate and each deduction, kept linked to the statement it came from.
Added to the register
New loads appended, revised statements matched against and flagged next to the original entry.
Export
Excel, CSV or JSON — one row per load, sortable by carrier, date or lane.
A register, built load by load
| Date | Lane | Miles | Gross rate |
|---|---|---|---|
| Sep 3 | Dallas → Memphis | 452 | $1,240 |
| Sep 5 | Memphis → Atlanta | 384 | $1,050 |
| Sep 8 | Atlanta → Charlotte | 244 | $780 |
| Sep 8 (revised) | Atlanta → Charlotte | 244 | $820 |
Four loads, one revision — and one register that shows all of it in date order, with the revised September 8th load kept next to the original so the rate correction is visible rather than replacing the earlier row silently.
This isn't a connection to the carrier's portal
Worth being precise about the boundary. Many carriers offer their own driver portal with a settlement history — this doesn't log into that, sync with it, or replace it. You download or receive each settlement statement the way you already do, and upload it here. What this adds is a single register across every carrier you haul for, which no single carrier's own portal will ever show you.
When a settlement is later corrected
A reweighed load or a rate adjustment sometimes means a carrier issues a revised settlement weeks after the original. Uploaded alongside the original, the revision is matched to it rather than treated as an unrelated new load — the register shows both, with the difference between them visible.
How often to update the register
As statements arrive is the simplest habit during an active hauling schedule — a few minutes per settlement keeps the register current with almost no batching effort. For a quarter with only a handful of settlements, running it once at quarter end works just as well.
Hauling for more than one carrier
A driver spreading loads across two or three carriers — for rate shopping, lane availability, or relationship reasons — ends up with settlement statements in as many different formats. Every one reads into the same register regardless of source, which is where the real value shows up: a single sortable view of the whole quarter, not three separate piles that each need their own manual total.
Rate per mile, once the register exists
With gross rate and mileage read for every load, a rate-per-mile figure — overall, by carrier, or by lane — is a filter and a formula away rather than a manual calculation across dozens of settlements. That's often the first thing a driver checks once a season register exists: which lanes and which carriers actually paid the best per mile, not just which ones felt busiest.
Who this is for
Owner-operators tracking their own loads
A season register built as settlements arrive, instead of a tax-time scramble through a folder of PDFs.
Drivers hauling for more than one carrier
One consistent register regardless of which carrier's format a given settlement uses.
Bookkeepers and accountants serving trucking clients
A clean, load-by-load record that drops directly into a client's income summary.
Owner-operators comparing lanes and carriers
A full quarter's hauling history, in one sortable spreadsheet, ready for a rate-per-mile comparison.
Feeding a load register to an accountant
A register built load by load through the quarter, rather than reconstructed in a single sitting at tax time, is exactly the kind of record an accountant can work from directly — dated, load-level detail rather than a single annual revenue total with no way to verify it.
Starting with one carrier
For a driver hauling for several carriers, starting the register with the highest-volume one — and confirming the format reads cleanly — is a reasonable first step before adding the rest, the same way it's worth proving out any new record-keeping habit on the simplest case first.
Export formats
Excel, CSV or JSON. The Excel export in particular is built to be a working document, not just an archive — sortable by carrier, lane or date, with formulas for a quarter's average rate per mile a light lift to add on top.
Comparing rate and deductions across carriers
A driver hauling for more than one carrier often has a rough sense of which one pays better, or takes a smaller dispatch cut, but rarely a precise one — comparing two individual settlements side by side gives one data point, not a pattern. A register spanning a full quarter, with every load from every carrier in the same structure, is what turns that rough impression into an actual comparison: an average rate per mile by carrier, or a dispatch fee that's consistently a percentage point higher at one carrier than another.
That comparison doesn't answer the question of where to run next quarter on its own — lane availability, relationship and equipment requirements all matter too — but it does put a real number behind a decision that's otherwise often made on impression alone.
A backup record independent of any single carrier
A carrier's own driver portal is a convenient record while it's available, but it's not something a driver controls — an account could be lost when a lease ends, a portal could be discontinued, or a relationship with a given carrier could simply end. A register built and kept independently, from the statements as they were originally issued, survives any of that. It's the same reasoning behind keeping paper receipts even when a company offers digital ones: convenient while it lasts, but not something worth being solely dependent on.
Rate confirmations versus settlement statements
A rate confirmation, issued at the moment a load is booked, records the agreed rate for that specific load — it's not the same document as the settlement statement, which arrives later with deductions applied. Some drivers keep rate confirmations as their own record through the quarter and reconcile them against the eventual settlement once it arrives, which is a useful secondary check: does the rate on the settlement actually match what was confirmed at booking.
Where both documents are available, reading them together closes that loop entirely — the booked rate and the eventual settlement, confirmed to agree before any deductions are even considered.
Tracking a lane's rate over time
A single load's rate is just one number. A quarter's worth, or several quarters' worth, laid out in one register, can reveal a trend that's invisible one settlement at a time — a lane that's paying consistently better than others, or one that's been trending down. Neither is necessarily a problem, but both are the kind of pattern worth noticing and, if it seems off, worth a conversation with the carrier or dispatcher armed with the actual numbers rather than a general impression.
Registering a seasonal spike in loads
A produce hauler running double the normal volume during harvest season, or a dry van driver picking up extra holiday retail freight, ends up with far more settlements to register in a short stretch than the rest of the year combined. Uploading statements in a batch once the surge eases is just as valid as reading them one at a time — the register builds the same way either way, and there's no requirement to keep pace in real time during the busiest weeks.
What matters more than the timing is eventually getting every load into the register — a busy season's worth of loads is exactly the data that matters most for an accurate seasonal comparison a year later, when the same surge rolls around again and last year's numbers become the benchmark for whether this season is running ahead or behind expectations.
A register shared between a driver and a dispatcher
On a small fleet, the driver hauling the loads and the person managing the books are often different people, and a shared, up-to-date register is what keeps both sides working from the same picture — a dispatcher negotiating the next rate can reference actual historical numbers instead of a memory of what a similar lane paid last time.
That shared view also helps settle the occasional disagreement about whether a particular lane or carrier is worth continuing to run — a register with real numbers ends that debate faster than competing impressions of how a route has been performing, since neither side has to rely on memory alone.
It also makes onboarding a new dispatcher or office manager considerably faster, since the full history is already there to review rather than something they'd otherwise have to piece together from scattered files, saving real time during exactly the kind of transition that's already stressful enough.
Privacy
Uploads go over TLS, encrypted end to end.
Processing runs on EU-hosted infrastructure.
Original documents are deleted immediately after extraction.
Rate and load data are never used to train AI models.
Full details are on the security page.