Per-stop pay is the standard compensation model for FedEx Ground drivers, but calculating it manually is a time-consuming, error-prone process. This guide walks you through automating per-stop pay calculations so you can process payroll in minutes instead of hours.
Why Per-Stop Pay Is Hard to Calculate Manually
On the surface, per-stop pay seems simple: multiply the number of stops by the per-stop rate. In practice, it's far more complex:
- Tiered rates — Many ISPs use different rates based on stop count thresholds (e.g., $1.50 for first 100 stops, $1.75 for stops 101-150, $2.00 for 150+)
- Per-package premiums — Some routes pay additional amounts based on package count
- 6th day bonuses — Drivers working a 6th day often receive premium pay
- Fuel deductions — Fuel card charges need to be deducted from gross pay
- Adjustments — Missed stops, service failures, and manual corrections complicate every payroll cycle
A fleet with 30 drivers across 3 CSAs, each with different rate structures, creates hundreds of individual calculations every pay period. Spreadsheets can handle it, but one wrong formula can cascade errors across the entire payroll.
Step 1: Document Your Pay Structures
Before automating anything, document every pay rule in use across your fleet:
- Per-stop rates for each CSA/route
- Stop count thresholds and corresponding rates
- Per-package rates (if applicable)
- 6th day bonus amounts
- Other bonuses (safety, attendance, performance)
- Deduction types (fuel, uniform, equipment)
This documentation becomes the configuration for your automated system.
Step 2: Choose Your Automation Tool
You have several options for automating per-stop pay:
Spreadsheet templates — Better than manual calculation, but still manual data entry. Formulas break. Version control is a nightmare. Not recommended for fleets over 10 drivers.
General payroll software — Tools like ADP and Gusto handle tax filing well, but they don't understand per-stop pay. You'll still calculate pay amounts manually and enter them as flat amounts.
Fleet-specific payroll tools — Purpose-built tools like FleetWage understand per-stop pay natively. You import stop counts, and the system applies your rate structures automatically.
Step 3: Set Up Per-Stop Thresholds
In FleetWage, you configure up to 3 stop thresholds per employee. Here's an example:
| Threshold | Stop Range | Rate |
|---|---|---|
| 1 | 1-100 stops | $1.50/stop |
| 2 | 101-150 stops | $1.75/stop |
| 3 | 151+ stops | $2.00/stop |
A driver who completes 170 stops would earn:
- 100 stops x $1.50 = $150.00
- 50 stops x $1.75 = $87.50
- 20 stops x $2.00 = $40.00
- Total: $277.50
This calculation happens automatically for every driver, every day, with zero manual math.
Step 4: Import Stop Count Data
Your stop count data comes from FedEx settlement reports. With automation tools, you can import this data directly rather than retyping it:
- Download your settlement report from FedEx
- Import it into your payroll tool
- Stop counts are automatically matched to drivers
- Pay is calculated based on each driver's configured rates
Step 5: Review and Export
Automation doesn't mean zero oversight. Each pay period:
- Review the calculated payroll summary
- Check for anomalies (unusually high/low amounts)
- Make manual adjustments if needed
- Export finalized payroll to your payroll provider (ADP, Gusto, Paychex, etc.)
The Time Savings Are Real
ISP owners who switch from manual spreadsheets to automated per-stop pay consistently report:
- 10-15 hours saved per week on payroll processing
- Fewer pay disputes due to transparent, consistent calculations
- Zero calculation errors — the math is always right
- Faster payroll processing — what took a weekend now takes an hour
Getting Started
If you're still using spreadsheets for per-stop pay, the switch to automation is straightforward. Most ISPs complete setup in under an hour and run their first automated payroll the same week.