Money is where small mistakes become big ones. StatVault checks the charge and the pay on every order before they leave your hands, and gives you a fair view of what your drivers earn.
The verify queue
Every order passes through a verify queue before billing. StatVault compares each order with that account's own history and flags what looks wrong: a missing reference, an unusual price, a route stop that seems billed twice, an order that coincides with a route already covering the stop. Each flag shows why it was raised and how confident it is. A verifier clears the queue, fixes what needs fixing, and moves on. References can be filled in from history, with the confidence shown, so nobody hunts for a cost center from last month.
Charge and pay lines
Each order carries its charge lines and pay lines. A verifier can add a line from your own catalogue, edit it, or remove it, and the change is recorded. Charges and pay are kept separate on purpose: what the client is billed and what the driver is paid are different questions, and the system never lets one silently overwrite the other.
Pay equity
Pay equity shows each driver's earnings per mile and per hour across lanes, with stacked work counted properly so a driver carrying three orders on one trip is not paid as if they drove three trips. It surfaces underpaid lanes, long empty miles, missing route pay and the drivers carrying the hardest work. Drivers in this industry are usually independent contractors in their own vehicles, and their pay has to cover the car. Pay equity makes that visible before it becomes turnover.
Coverage pay
When a driver covers someone else's route, the coverage is recorded against that route and day, with what was planned, what ran and what was paid. A dispatcher approves or edits the coverage pay, and the record is append-only, so a correction never erases what came before.
Where the numbers go
The billing engine is StatVault's own. Prices come from your lanes, zones and per-client rules; the verify queue checks every charge and pay line before it counts; pay equity and coverage pay settle what drivers are owed; invoices and driver settlements are produced from that verified record. Operations that also run CXT get every verified change mirrored there automatically, so nothing has to be typed twice.
Related
Questions couriers ask
- Does StatVault send invoices to my clients?
- StatVault owns the numbers: it prices orders from your lanes and rules, verifies every charge and pay line, and can produce invoices and driver settlements from the verified record. If you also run CXT, every verified change is kept in step there automatically.
- What does the verify queue catch?
- Orders whose charges or references look wrong against that account's history, such as a missing reference, an unusual price or a route stop billed twice.
- What is pay equity?
- A view of what each driver earns per mile and per hour across lanes, so underpaid work and long empty miles are visible.
- Does it handle coverage pay?
- Yes. When a driver covers someone else's route, the coverage pay is recorded against that route and day, and approved by a dispatcher.
- Where do verified changes go?
- Into StatVault's own record first: the verify queue, the pay equity pages and the settlement run read the same verified numbers. Operations that also run CXT get each change mirrored there automatically.