← All Features
In Development

💵 Driver Pay & Settlements

Per-mile, per-load, and percentage-based driver pay with automated settlements, itemized pay stubs, deduction tracking, and accounting export. Everything needed to pay drivers accurately and on time — launching Q3 2026.

Driver Pay and Settlements
Q3 2026
Expected Launch
Per-mile
+ Per-load Pay
Pay Stubs
Itemized Statements
Export
QuickBooks & CSV
Driver Pay & Settlements is in active development. Expected availability: Q3 2026. All other VAU0 features are live and available today. Sign up now — you’ll get access to Driver Pay automatically when it launches.
🛠 Planned Features

What’s Being Built

Six core modules designed to handle every aspect of driver compensation, from mileage calculation to accounting export. Each module is being built to work together seamlessly.

💵
Q3 2026
Per-Mile Settlements
CPM (cents per mile) rate multiplied by ELD-verified miles equals automatic pay calculation. No manual odometer reading. No mileage disputes. The system pulls actual driven miles from the ERETH ELD, applies the driver’s configured rate, and generates the settlement amount. Practical route miles and hub miles can be configured as alternatives. Each settlement shows the mile source, rate applied, and total calculated — fully auditable and transparent to both the carrier and the driver.
📊
Q3 2026
Per-Load Flat Rate
Flat rate per load or percentage of gross revenue. Configured per driver or per driver type (company driver, owner-operator, team driver). The system applies the correct rate automatically when a load is delivered and marked complete. Percentage-based pay calculates from the carrier’s gross revenue on the load minus any excluded charges defined in the pay template. Multiple pay structures can exist simultaneously for different driver groups within the same carrier account.
📄
Q3 2026
Itemized Pay Stubs
Weekly or bi-weekly statements showing gross pay, each deduction itemized with description and amount, and net pay. Drivers see their pay stubs directly in the Driver Portal without needing to request them from the office. Each line item links back to the load or deduction that generated it. Pay stubs can be downloaded as PDF for personal records, tax filing, or loan applications. The format is clean, professional, and consistent across every pay period.
Q3 2026
Deduction Management
Track fuel advances, equipment damage charges, insurance contributions, escrow deposits, and any other deductions per driver per pay period. Recurring deductions can be configured to apply automatically every period until a specified end date or total amount is reached. One-time deductions are entered manually and applied to the next settlement. Every deduction includes a description visible to the driver so there are no unexplained amounts on pay stubs. Deduction history is retained indefinitely for audit purposes.
📅
Q3 2026
Pay Period Management
Weekly, bi-weekly, or custom pay periods with configurable start and end dates. Settlements lock after the cutoff date to prevent accidental changes. Administrators can unlock a period for corrections if needed, with a full audit trail of who changed what and when. Historical pay periods are accessible indefinitely, making it easy to research past settlements for dispute resolution or compliance. The system prevents duplicate payments and catches loads that fall outside the current period.
📤
Q3 2026
Accounting Export
Export settlement data to QuickBooks Online, QuickBooks Desktop, Xero, or as a standard CSV file. The export maps settlement line items to your chart of accounts so journal entries are created correctly the first time. This eliminates the manual re-entry of driver pay data into accounting software that causes errors and wastes hours every pay period. The mapping is configured once during setup and applied automatically to every subsequent export.
🔒 Our Approach

Why It’s Not Live Yet

An honest explanation of why we are taking extra time to get driver pay right.

Driver pay is the most sensitive data in a carrier’s operation. Getting it wrong creates legal liability, driver disputes, and regulatory exposure. A miscalculated settlement can mean a driver quits. A missing deduction can mean the carrier absorbs a cost they should not have. A non-compliant pay stub can trigger a Department of Labor investigation.

We are building Driver Pay & Settlements with the same care we built ELD compliance: no shortcuts. Every calculation is being validated against real carrier payroll data. The mileage integration is being tested against actual ELD records to ensure driven miles match settlement miles exactly. The deduction engine is being designed to handle complex scenarios like split-week pay periods, mid-period rate changes, and retroactive adjustments.

We are testing with our own fleet first. Our internal operations team is running parallel payrolls — one through their existing process and one through the VAU0 settlement engine — to verify that every penny matches. Only when the system produces identical results across multiple pay periods will we open it to beta carriers.

When Driver Pay launches in Q3 2026, it will be fully FLSA-compliant, integrated with ERETH ELD mileage data, and verified against real carrier payrolls. We would rather launch late and correct than launch early and cause problems for carriers and drivers who depend on accurate pay.

💪
FLSA Compliant
Fair Labor Standards Act requirements built into every calculation template from the start.
📈
ELD-Verified Miles
Settlement miles come directly from ERETH ELD records. No manual odometer readings or mileage guesses.
🔍
Full Audit Trail
Every change to a settlement is logged with who changed it, when, and what the previous value was.
✅ Available Today

What You Can Do Now

While Driver Pay is in development, here are three ways VAU0 carriers handle driver settlements today using existing features.

📄
Export Load Data to CSV
Every delivered load in the VAU0 TMS can be exported as a CSV file with all relevant fields: load number, origin, destination, miles, revenue, driver assigned, and delivery date. Import this CSV into your current payroll system or spreadsheet to calculate driver pay using your existing formulas. The export is available at any time and can be filtered by date range, driver, or load status. This gives you accurate load data from VAU0 while keeping your current pay process intact until the automated settlement engine launches.
📁
Store Settlements in Document Center
Use the VAU0 document center to upload and store settlement sheets, pay stubs, and driver agreements. Documents can be tagged by driver and date for easy retrieval. This creates a centralized, searchable archive of pay records that both the office staff and the driver can access. When the automated settlement feature launches, historical documents will remain accessible alongside the new system. This approach keeps all driver-related paperwork in one platform rather than scattered across email, filing cabinets, and external drives.
E-Sign Settlement Agreements
Use the VAU0 e-signature feature to send driver settlement agreements, pay rate confirmations, and deduction authorizations for digital signature. Drivers can review and sign documents from the Driver Portal without printing, scanning, or mailing anything. Signed documents are stored automatically in the driver’s file. This is especially useful during onboarding when drivers need to acknowledge their pay structure, sign deduction authorization forms, and confirm direct deposit information before their first load.
Smooth transition guaranteed. When Driver Pay launches, it will import your existing driver roster, pay rates, and deduction schedules from the VAU0 TMS. You will not need to re-enter driver information. The transition from manual settlements to automated settlements is designed to be seamless — run both systems in parallel until you are confident in the new one, then switch over.
📅 Roadmap

Development Timeline

Where we are in the development process and what comes next.

Q1 2026 — Architecture Design
Database schema, calculation engine design, and integration planning completed. Defined pay template structures for per-mile, per-load, and percentage-based compensation. Mapped accounting export formats for QuickBooks Online, QuickBooks Desktop, Xero, and generic CSV. Designed the deduction management data model to support recurring, one-time, and conditional deductions. Security architecture reviewed and approved for handling sensitive financial data. Complete.
Q2 2026 — Core Settlement Engine
Building the core calculation engine that takes load data, mileage records, driver pay rates, and deductions, then produces accurate settlement amounts. Currently integrating with the ERETH ELD mileage API to pull verified driven miles for per-mile calculations. Building the pay stub generation system with PDF export. Developing the deduction management interface for carrier administrators. Internal testing with parallel payroll runs against our own fleet’s existing settlement process. In progress.
3
Q3 2026 — Beta Launch with Test Carriers
Opening the settlement engine to a limited group of beta carriers for real-world testing. Beta carriers will run the VAU0 settlement system alongside their existing payroll to verify accuracy. Collecting feedback on the pay stub format, deduction management workflow, and accounting export process. Fixing issues and refining the user experience based on real carrier operations. Drivers will begin seeing pay stubs in the Driver Portal during this phase.
4
Q4 2026 — General Availability
Full release to all VAU0 carrier accounts. Driver Pay & Settlements will be available as part of the standard VAU0 platform at no additional cost. Includes per-mile settlements, per-load flat rate, percentage-based pay, itemized pay stubs, deduction management, pay period controls, and accounting export. All existing carriers will gain access automatically. New carriers signing up after launch will have Driver Pay available from day one.
📈 Under the Hood

How Pay Calculations Will Work

A closer look at the settlement engine’s approach to each pay model.

Per-Mile (CPM) Calculation
The settlement engine starts with the driver’s configured CPM rate. It then pulls the total miles for each delivered load from the ERETH ELD mileage records. The system multiplies rate by miles for each load, then sums the results for the pay period. Carriers can choose between three mileage sources:
  • ELD actual miles — The exact miles driven as recorded by the ERETH ELD hardware. Most accurate, no disputes possible.
  • Practical route miles — Calculated from origin to destination using standard routing software. Consistent and predictable.
  • Hub miles (HHG) — Standard household goods mileage guide distances. Common in certain freight sectors.
Percentage of Gross Calculation
For owner-operators or drivers paid a percentage of load revenue, the engine takes the carrier’s gross revenue on each load and applies the driver’s configured percentage. Carriers can define which charges are included in “gross” and which are excluded:
  • Included by default: Line haul revenue, fuel surcharge (configurable)
  • Excluded by default: Accessorial charges, detention pay, lumper fees (all configurable)
  • Custom rules: Per-driver overrides for specific charge types
The system shows both the gross amount and the calculated driver share on every pay stub line, so drivers can verify the math themselves.

Deduction Types Supported

Recurring Deductions
Insurance premiums, equipment lease payments, escrow contributions, and other deductions that repeat every pay period. Set a start date, optional end date, and the amount. The system applies them automatically.
One-Time Deductions
Fuel advances, damage charges, uniform costs, or any other charge that applies once. Enter the amount and description, assign it to a driver, and it appears on their next settlement. After it is applied, it does not repeat.
Installment Deductions
Large charges spread across multiple pay periods. Set the total amount and the per-period installment. The system tracks the remaining balance and stops deducting when the total is reached. Useful for equipment damage or training cost recovery.
❓ FAQ

Frequently Asked Questions

Common questions about the upcoming Driver Pay feature.

Will Driver Pay cost extra?
No. Driver Pay & Settlements will be included in the standard VAU0 platform at no additional cost. There will be no per-settlement fees, no per-driver surcharges, and no premium tier required. Every carrier on VAU0 will get full access to all settlement features when they launch.
Can I use it without the ERETH ELD?
Yes. While the per-mile calculation works best with ELD-verified miles, carriers can also use practical route miles or manually entered miles. The ELD integration is the most accurate option but is not required. Per-load flat rate and percentage-based pay models do not use mileage at all.
Will drivers see their pay stubs in the Driver Portal?
Yes. Drivers will see their itemized pay stubs directly in the Driver Portal and the VAU0 Driver App. They will be able to view current and past settlements, download PDF copies, and see a breakdown of every line item including loads, miles, rates, and deductions.
Does it handle owner-operator settlements?
Yes. Owner-operators typically receive a percentage of gross revenue. The system supports this model with configurable inclusion and exclusion rules for different charge types. Owner-operator settlements can also include deductions for insurance, escrow, trailer rent, and other common lease-on charges.
Can I join the beta?
Beta access will be offered to existing VAU0 carriers in Q3 2026. If you are a current VAU0 user and want to be among the first to test Driver Pay, contact the VAU0 support team to express interest. Beta participants will run the new system alongside their existing payroll process to validate accuracy before switching over.
What about tax withholding?
The initial release focuses on settlement calculation, not tax withholding or payroll processing. Most carriers use a separate payroll service (ADP, Gusto, Paychex) for tax withholding and direct deposit. VAU0 settlements will export cleanly to these services. Future releases may include deeper payroll integration based on carrier demand.
💡 Why VAU0

What Makes This Different

Most settlement software is a standalone product. VAU0 Driver Pay is built into the same platform where loads, miles, and documents already live.

🔗
Integrated, Not Bolted On
Because VAU0 already has the load data, ELD mileage, and driver records, the settlement engine does not need data imports or manual entry. When a driver delivers a load, the system already has the origin, destination, miles driven, revenue, and driver assignment. The settlement calculation happens automatically. No copying data between systems. No spreadsheet formulas. No reconciliation between what the TMS says and what the payroll system says.
🔐
Driver Transparency
Most settlement disputes happen because drivers cannot see how their pay was calculated. VAU0 solves this by showing drivers every line item: which loads were included, how many miles were credited, what rate was applied, and what deductions were taken. When drivers can verify the math themselves, disputes drop dramatically. This transparency builds trust between carriers and drivers, which directly impacts retention in an industry where driver turnover exceeds 90% annually.
🔗 Related Features

Works Best With

Driver Pay integrates directly with these VAU0 features for end-to-end driver management.

Start Now — Get Driver Pay When It Launches

Sign up for VAU0 today and use all live features immediately. Driver Pay & Settlements will be added to your account automatically in Q3 2026 at no extra cost.