Every advance, deduction, paystub, settlement, and QuickBooks entry derived from a single system. Zero manual entry. Zero variance.
Built for driveaway and owner-operator carriers. Fuel card and QuickBooks on day one. Deeper with your TMS.
Driver pay lives in pieces. Each system knows its piece and nothing else. Every pay period, somebody re-keys money that already happened.
Issues the advance. Knows a driver got $200 on Tuesday. Tells no one.
Holds a statement shell: an empty container waiting for a person to type the money lines into it.
Records whatever it's told. If the entry never matches the cash, it's the last to find out.
Each of those tools is fine at its piece. None of them runs the whole chain, and none of them moves the money. That gap is this product.
The engine behind this runs live weekly payroll at a 90-driver driveaway carrier.
“We spent way too much time every month checking, double-checking, and triple-checking to make sure everything matched. Now it’s a quick review.”
Hand-keying costs you twice: hours out of every pay period, and the errors that ride in with them. The chain removes both at once, because nothing is ever entered twice. The advance records itself the moment it hits the card. The deductions derive themselves from the loads. The stub builds itself. The check books itself.
What a clerk re-keys, the system already knows. What a clerk mistypes, it can't.
One advance, one pay period, the same dollars at every step. Every figure below is derived by the system. None of it is typed by a person.
A driver takes an advance at dispatch or mid-load. We push it to their fuel card and record it as money out the door, because it is. No sticky note, no “remember to deduct this later.”
Escrow builds toward its target. Insurance follows the driver who took the load, charged per day, not a flat monthly hit. A short week from last month is recovered on schedule. Referrals go to the driver who earned them.
The stub isn't a form a clerk fills in. It's the output of everything above. If a number is on it, the system can show you exactly where it came from, down to the load and the day.
Friday morning, $2,059.00 goes to the driver. Not a report of what somebody should pay. The payment itself, for exactly what the stub says.
One check per driver per period, split by what actually happened on the trip. The settlement goes to driver pay, and every advanced dollar books to the account it was spent from: fuel, the motel, meals, the wash bay, tied to the load it belongs to. Your P&L sees the trip, not a lump.
The check is $200.00 bigger than what the driver got? That's correct, and it's the part most software gets wrong. Here's why ↓
The advance left your bank on Tuesday, the moment it hit the driver's card, days before any paystub existed, with no entry to match it.
So the check booked on Friday is intentionally larger than what reached the driver, by exactly the advances it recovered: $2,059.00 settled, plus the $200.00 that already went out Tuesday. And that $200.00 doesn't book as a blob. It splits to the accounts it was actually spent from: fuel, lodging, meals, the wash. A $2,259.00 check, and the bank statement, the P&L, and the trip all say the same thing.
Book the net instead, or book the gross without recovering the advance, and your bank account quietly stops reconciling. It won't show up this week. It shows up at tax time, as a number nobody can explain.
Most software gets this wrong because most software has never funded an advance. Moving the money is our product, so the books have to be right.
The chain doesn't just process the pay period. It audits it. These are the things a spreadsheet can't see and a tired clerk misses.
We reconcile against the fuel card itself and catch the hand-run advance someone pushed from the card portal, the bonus paid by card, the card charge with no load behind it at all. If the card moved money, the chain accounts for it.
The load delivered. The driver did the work. The stub says nothing. That's a driver who finds out on payday, or a clerk who finds out when the driver calls. We flag it before the settlement runs.
Somebody pays a driver outside the system once, and every future settlement for that driver silently stops matching. It surfaces months later as a mystery balance. We catch it the week it happens.
The same week as the example above. Flip to the version where somebody hand-runs a $150.00 advance from the card portal on Wednesday and never tells the ledger.
One advance, derived deductions, a check that ties to the penny. The same week as the chain above.
No new hardware, no rip-and-replace. The chain connects to the accounts your money already moves through, on day one.
He has spent the last year inside a driveaway carrier's settlement office, automating the pay cycle this page describes. If you get a walkthrough, he's the one who runs it.
Bring one real pay period. We'll walk it end to end: advances, deductions, stubs, checks. Then we'll show you where the chain picks it up.
Connects to your fuel card and QuickBooks on day one. Deeper with your TMS. No TMS at all? The chain runs anyway.