The free driver payout template for delivery fleets
A payout template is only useful if it survives contact with a real platform export. These are the columns and checks that hold up.
What a good payout template needs
Most payout spreadsheets fail for one of two reasons: they do not distinguish gross pay from deductions, or they do not keep a stable driver identifier. A usable template fixes both before the first row is entered.
Keep one row per driver per payout period. If your source is a task log, aggregate it first; if it is a weekly summary, enter it directly. Do not mix the two in the same sheet.
The columns
These columns cover the numbers a payroll provider needs and the audit trail your team will want later.
| Column | Required | Notes |
|---|---|---|
| driver_name | Yes | Legal or payroll name; keep it stable |
| driver_id | Strongly recommended | Platform ID or employee ID; the safest grouping key |
| period_start / period_end | Yes | The week or pay period the file covers |
| orders | Yes | Completed deliveries; zero is valid but should be explained |
| base_pay | Yes | Per-order, hourly, or fixed commission |
| tips | If applicable | Customer tips passed through |
| incentives | If applicable | Surge, peak pay, quests, distance bonuses |
| deductions | If applicable | Cash collected, deposits, penalties |
| total_payout | Yes | The amount to transfer |
| currency | Yes | ISO code, so a file cannot be paid in the wrong currency |
| status | Yes | ready, hold, or excluded |
| note | Optional | A short reason for any adjustment |
Formulas that keep totals honest
In Excel or Google Sheets, put the components in separate columns and calculate the expected total in a new column. Then add a difference column: expected total minus the reported total. Any non-zero difference is a row to inspect.
The difference column is the single most useful audit tool in the sheet. It turns a silent mismatch into a visible exception.
| Cell | Formula | Meaning |
|---|---|---|
| Expected total | =base_pay + tips + incentives − deductions | What the components say |
| Difference | =expected_total − reported_total | Zero means the row reconciles |
| Fleet total | =SUM(total_payout) | The amount leaving the bank |
| Driver count | =COUNTA(driver_id) | Sanity check against the ledger |
How to use the DeliverPayout sample
DeliverPayout's sample file uses the same shape: driver ID, driver name, orders, total earnings, distance, active hours, tips, rating, completion rate, and vehicle. Download it from the start screen, replace the rows with your own data, and import it to see how the dashboard reads it.
The sample is deliberately small. A real file can be thousands of task rows; DeliverPayout aggregates them by driver and applies the same reconciliation rule.
A note on rounding
Round to cents at the row level and let the totals sum the rounded values. If you calculate full-precision numbers and round only at the end, the exported rows can add up to a different total than the review screen. That one-cent difference is enough to fail a payroll validation.
Questions
Can I use Google Sheets instead of Excel?
Yes. The template uses plain CSV, so it opens in Google Sheets, Excel, Numbers, and most payroll systems. Keep the header row unchanged when you export.
What is the minimum data needed for a payout?
A driver name, a unique driver identifier, the amount to pay, and the currency. Orders, tips, incentives, and deductions make the run auditable but are not strictly required to move money.
Should the template include bank details?
No. Keep bank details in your payroll provider, not in a CSV that gets emailed around. DeliverPayout's export intentionally excludes bank account information.