Build driver settlement statements from every load
Every Monday, WebRun opens BeyondTrucks, gathers each driver's loads completed last week, applies your per-load, per-mile, and accessorial pay rules, builds a clear settlement statement per driver in a Google Sheet, and drafts the matching payout in QuickBooks for payroll to review before anyone is paid.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I build driver settlement statements from completed loads?
Every Monday WebRun gathers each driver's loads completed last week from BeyondTrucks, applies your per-load, per-mile, and accessorial pay rules, and builds a settlement statement per driver in Google Sheets. It then drafts the matching payout in QuickBooks for payroll to review, so drivers are paid accurately and on time with a human approving every amount.
- Settlements are built from live load data, not a manual spreadsheet crawl
- Every payout stays a draft until payroll reviews and releases it
- Loads without a signed BOL are held out of pay automatically
Built for tank truck payroll teams · bulk carrier back office · fleet owners · driver pay administrators
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.beyondtrucks.comin a real browser with your saved login - no setup, no API keys. -
1
BeyondTrucks - gather each driver's loads
WebRun opens BeyondTrucks to gather each driver's loads. - Open BeyondTrucks and pull every load completed last week grouped by driver
- Capture the pay basis for each load: loaded miles, stops, volume, wait time, and any accessorials
- Note any load still missing a signed BOL so it can be held for the next cycle
- Flag any load with a pay basis that looks off for review
Done when Every driver's completed loads are gathered with a full pay basis.
-
2
Google Sheets - build the settlement statement
WebRun opens Google Sheets to build the settlement statement. - Open the Driver Settlements sheet and start this week's tab
- Apply your pay-per-load, per-mile, and accessorial rules to each load
- Add fuel, detention, and any deductions to build a settlement statement per driver
- Total gross pay, deductions, and net pay for each driver
Done when Each driver has a complete settlement statement with gross, deductions, and net.
-
3
QuickBooks - draft the payout for review
- Open QuickBooks and draft the payout for each driver matching the settlement statement
- Attach the statement reference and the load count to each draft
- Leave every payout as a draft for payroll to review. Never pay a driver on your own
Done when Each driver's payout is drafted in QuickBooks, none released.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it pay drivers automatically?
No. WebRun builds the settlement statement and drafts the payout in QuickBooks, then leaves it for payroll to review and release. No driver is paid without a human approving the amount.
How does it calculate each driver's pay?
It reads each completed load in BeyondTrucks and applies your pay-per-load, per-mile, and accessorial rules, then adds fuel, detention, and deductions to produce gross, deductions, and net for every driver.
What about loads missing a signed BOL?
It holds any load still missing a signed bill of lading out of this week's settlement and notes it, so pay is not released on an unconfirmed load and it carries into the next cycle once documented.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.