Money out
Running a pay week
The pay run is the object, not the individual settlement. One run covers a period, states how many drivers and what the total net is, and is approved once.
The run
- 01Generate the period. Every driver with activity gets a draft. Loads, per-mile pay, fuel and card charges, recurring deductions and advances all pull in automatically.
- 02Read the exceptions. Anything questionable is surfaced before the approve button, not after.
- 03Confirm.Two clicks, and the second one names the amount: “Confirm — approve $X.” Committing money to people should require reading the number.
Exceptions worth knowing
| Warning | What it means |
|---|---|
| Duplicate load | The same reference number appears twice in one period. Nearly always a double-entered rate con, and paying both overpays the driver. |
| Prior unpaid loads | A load from an earlier period that never got settled. It can be pulled into this run rather than disappearing. |
| Before the opening balance | The period ends on or before a driver's migration date, so that money is already counted in their opening figures. |
Negative weeks
A week where deductions exceed pay does not produce a negative payment. The shortfall carries forward and is worked off against following weeks, which is how the arrangement actually works on paper.
After approval
An issued settlement is history. Its rows are locked, and the charges behind them cannot be recategorized, reassigned or deleted.
Opening balances
A carrier moving to TruckDesk mid-year has a real year-to-date that this system knows nothing about, and YTD prints on the settlement statement as a fact.
An opening balance per driver fixes that: the figures their previous system ended on, and the date it ended. It creates no line, no payment and no books entry. Any balance a driver still owed on that date lands on their first settlement here and never again.
Related guides