How-to guides
How to run driver pay and dispatcher pay
Who this is for: owners and office staff.
Two separate things live here. Driver Pay produces a weekly settlement for each driver. Dispatcher Pay tracks what you owe (or are owed) for dispatch service on delivered loads.
Driver pay statements
1. Set each driver's pay
On the driver's page: pay method and rate.
| Method | Paid on |
|---|---|
| Per mile | Loaded miles on the load |
| Percent | A share of the load's gross rate |
| Flat | A fixed amount per load |
If a driver has no rate of their own, your company defaults from Settings → Operations are used.
2. Generate the week
Driver Pay → Generate. Pick the driver and the week. The statement is created as a Draft with a line for every load they delivered in that week.
One statement per driver per week. If a finalized or paid statement already exists for that week you will be told, rather than quietly getting a second one — void the old statement first if you need to redo it.
3. Add the rest of the lines
A settlement is more than load earnings. Add lines for:
- Bonus and detention pay
- Driver advances taken during the week
- Lease, insurance, fuel card, escrow
- Other deductions
Totals recompute as you go. Lines can only be added or removed while the statement is a Draft.
4. Finalize, then pay
| Status | Meaning |
|---|---|
| Draft | Editable. |
| Finalized | Locked. Ready to pay. |
| Paid | Recorded as paid, with the method and date. |
| Void | Cancelled. |
Finalizing, marking paid, and voiding are limited to owners and admins. Only a Finalized statement can be marked paid. A Paid statement cannot be voided — issue a correction on the next statement instead. That restriction is deliberate: a settlement a driver has already been paid on should never change underneath them.
Every statement renders as a PDF for the driver.
Letting a driver see their own statements
A Driver-role login sees only its own settlements — never another driver's, and never the fleet total. For that to work the login has to be tied to a driver record: open the driver's page and link them to the user account they sign in with.
Until that link exists, the app refuses to show pay statements to a driver login rather than falling back to showing everything. If a driver reports an error on the page, an unlinked login is the first thing to check.
Dispatcher pay
How it accrues
Settings → Operations → Dispatcher pay: choose the method (percent of revenue, per load, or flat) and the amount. Set the amount to 0 to turn dispatcher pay off entirely.
When a load reaches Delivered, a pending dispatcher payment is written for that load, once. Re-delivering or re-saving the same load does not double it. If a load never reaches Delivered, no dispatcher pay accrues on it.
Paying it out
Dispatcher Pay lists everything pending with a running summary. Marking a payment as paid is restricted to the carrier owner — the person whose money it is. A payment already marked paid cannot be marked again.
If nothing is accruing
Check, in order:
- The dispatcher pay amount in settings is greater than zero.
- The load actually reached Delivered.
- There is a dispatcher on the account for the pay to be assigned to.
Pay bookkeeping never blocks a delivery. If accrual cannot resolve who to pay, the delivery still goes through and the payment is skipped.
Related
Still stuck?
Email support@dynamanic.io with your company name, what you did, what happened — quoting any message on screen — and when, with your timezone.