How to check a DSP weekly settlement against your work summary
Put each route line of the settlement beside the work summary for the same station, week, route type and day, and look for days where fewer routes were paid than you ran. RoutePayAudit makes that comparison, and a few checks of the settlement against your rate card, your scorecard and its own arithmetic. It does not compare hours, packages or stops, and it asks you a question wherever a difference cannot be shown from the files.
Updated . Status as of
What is known about the weekly settlement, and where it stops
Amazon pays its delivery service partners through a weekly settlement statement. A settlement is built in layers: a fixed part for vehicles, a variable part for routes, hours or packages, a bonus by scorecard tier, and deductions and adjustments. Rates and thresholds differ from one partner to the next and are not published. There is no published sample of a settlement or list of its columns. None of this comes from Amazon itself (what a settlement is, as far as is known).
Two articles by firms that serve delivery service partners say the same about the weekly statement and its parts (Steph's Books, Route Consultant). They are not documents of Amazon. Because no sample or list of columns is published, a line is matched by what your own file prints for it: its category, date, route type, unit, quantity, rate and amount. Check that your agreement lets you share a file before you upload it.
What to put beside the settlement
These are the files RoutePayAudit reads (the files you supply). You supply them yourself: it does not sign in to Amazon or fetch anything from it.
- The settlement of the week: the station code, the day the week starts and the day it ends, the day the settlement appeared, the currency, the net amount, and every line with its category, date, route type, unit, quantity, rate and amount.
- The work summary for the same station and the same week: one row per day and route type with the routes you ran. The file can also hold hours, packages and stops.
- The scorecard of the week, if the settlement has a bonus line.
- Your own rate card, in the version you have confirmed against your paperwork, if you want a rate checked or a missing route priced.
How to check the routes by hand
- Match the header. The settlement and the work summary must name the same station and the same week. A work summary of another station or another week answers nothing, and RoutePayAudit asks you for the right one.
- Add up the route lines of the settlement for each day and route type. A route line with no date pays a total for the week, so compare it with the routes run over the whole week.
- Take the routes run for the same day and route type from the work summary, on the days it lists in full. A file lists a day in full when a Day Complete column says yes on every row of that day, or when it states that it lists all work for the full week. If it says neither, RoutePayAudit does not compare the day and asks you.
- Compare. Routes paid at or above the routes run are no difference. Routes paid below are a candidate, not yet a difference.
- Look at the rest of the week before calling a route missing. It may be paid under another date, or by another positive line such as an adjustment.
- Price what is left: the missing routes times the rate the settlement pays for that route type, or else the rate in your own confirmed rate card. With no rate known there is no amount, and it is a question.
- Keep the line numbers of the settlement and the rows of the work summary beside the figures. You write and send the request yourself.
One of the articles gives similar advice to its readers: "Compare your daily dispatch log (route count, driver, station) to the route-level detail on the settlement" (Steph's Books). It is the advice of a bookkeeping firm, not a rule of Amazon.
Each kind of settlement line, and what RoutePayAudit does with it
The ten rules by the line they check. The three rows on routes are the ones that use the work summary
| Line of the settlement | Compare it with | What RoutePayAudit does | Source |
|---|---|---|---|
| Route pay: the routes of one type on one day | The routes run that day for that route type in your work summary, if it lists the day in full | Rule S1. Reports a difference when fewer routes are paid than you ran and the week is short too, and asks in the other cases. The amount is the missing routes times the rate. | Rule S1 |
| Route pay with no date: a total for the week | The routes run over the whole week, if the work summary lists every day of it | Rule S1. Compares the week as a whole. If a day is not listed in full, it asks you for a work summary that covers the week. | Rule S1 |
| A route type in your work summary that the settlement does not mention | The settlement, in case the type is paid under another name | Rule S1. Asks whether the type is paid under another name. It reports no difference. | Rule S1 |
| Pay at a rate: route, hour, package or stop | The rate for that route type and unit in your confirmed rate card, on the date of the line | Rule S2. Reports a difference when the rate paid is below the card rate. Asks when the card is not confirmed or has no such rate. | Rule S2 |
| Bonus by scorecard tier | The scorecard of the week the bonus is paid from, and your confirmed rates by tier: see DSP scorecard tier and the bonus | Rule S3. Reports a difference when that scorecard shows a higher tier than the line was paid at. Asks when the weeks back, the scorecard or a rate is not known. | Rule S3 |
| Peak or bonus premium | The premium dates and rates in your confirmed rate card, and the pay lines on those dates | Rule S4. Reports a difference when the settlement pays no premium or less. Asks when a quantity is not read. | Rule S4 |
| Chargeback or deduction | The same reference, amount and date in this settlement or in an earlier one of the same station | Rule S5. Reports a charge taken twice when all three match; a weaker match is a question. It does not check a chargeback against your delivery records. | Rule S5 |
| Fixed payment for vehicles, fuel, deduction for damage, van lease | Your own agreement, lease and incident records | Rules S6, S7, S8 and S10. Never a difference: it asks whether the amount is what you expected. | Rules S6, S7, S8 and S10 |
| Any line with a quantity, a rate and an amount | Quantity times rate | Rule S9. Reports a difference when the amount is below quantity times rate. A line paid above it is not reported. | Rule S9 |
| All the lines together | The net amount of the settlement | Rule S9. Reports a difference when the lines add up to more than the net amount. Asks when they add up to less. | Rule S9 |
An example week in our sample report
In our sample report, an invented station has a work summary that shows 10 Standard routes on each of the 7 days of the week 2026-09-12 to 2026-09-18, and a settlement that pays 10 routes at $200.00 on six of those days and 9 routes on 2026-09-14 (the sample report).
Figures in our sample report: an invented station, an invented settlement and an invented rate
| Day or line | Routes run in the work summary | Routes paid in the settlement | Result in our sample report | Source |
|---|---|---|---|---|
| 2026-09-12, 2026-09-13, 2026-09-15, 2026-09-16, 2026-09-17 and 2026-09-18 | 10 a day | 10 a day | No difference | Sample report |
| 2026-09-14, settlement line 3 | 10 | 9 | A difference of $200.00: 1 missing route at $200.00, the rate the settlement pays for these routes that week | Sample report |
| Settlement line 8, a device fee of $50.00 taken off | no row for it | not paid by route | A question: is this deduction expected? It is not a difference | Sample report |
That week ends as a discrepancy in our sample report: one difference worth $200.00 and one question for you. The same page shows the text of the request as the product writes it; you file it yourself (the sample report).
When a short day is a difference, and when it is a question
- A difference, with an amount: on a day the work summary lists in full, the settlement pays fewer routes of a type than you ran; the week counted over the days listed in full is short too; nothing else in the settlement could be paying them; and a rate is known. It is never more than the week is short, and one line never gives two amounts (the ten rules).
- A question, with no amount: the week as a whole is not short, so the route may be paid under another date; an adjustment, a step payment or another positive line may pay it; no rate is known; the work summary is missing, is for another station or week, or does not list the day in full; or a route type of the work summary has no route line in the settlement (the ten rules).
- Nothing: the settlement pays as many routes as you ran or more, or the missing routes are worth less than the smallest amount RoutePayAudit reports, which the ten rules explain as rounding (the ten rules).
What RoutePayAudit does not look for
- Hours, packages and stops. The work summary file can hold them, but in this version no rule compares them with the settlement: the work summary is compared on the routes run.
- Routes on a day the work summary does not list in full, and a bonus that is missing from the settlement altogether.
- Overpayments. A day paid above the routes run, or a line paid above quantity times rate, is not a difference.
- Whether a fixed payment for vehicles, a fuel charge, a deduction for damage, a van lease or a chargeback is right. It asks whether you expected the amount, and the proof is in your own records.
- The rates and thresholds of your agreement. It uses the rate card version you have confirmed and nothing else, and it shows no amount where none is confirmed.
After the check
A week ends as one of four verdicts (the verdicts). For each difference RoutePayAudit prepares the text of a request with the figures and the lines it rests on; you file it yourself, and it files nothing for you. We found no primary source for the time allowed to dispute a settlement, so RoutePayAudit names no deadline of its own. You can record your own number of days for a station in the cabinet (the time to dispute).
Sources
- Steph's Books, "Amazon DSP Payment Reconciliation" (April 9, 2026): An article of a bookkeeping firm, not a document of Amazon, read on 2026-10-30: DSPs are paid through a weekly settlement cycle, the settlement is the net result of base rates, per-package fees, incentive tiers, chargebacks, deductions and adjustments, and the quoted advice to compare a dispatch log with the route-level detail of the settlement.
- Route Consultant, "How Are Amazon DSPs Paid?": An article of a consultancy, not a document of Amazon, read on 2026-10-30: DSPs receive a weekly settlement statement, and a monthly base rate that offsets the cost of the vehicles.
- RoutePayAudit, what a settlement is, as far as is known: The sentences on the weekly settlement and its layers, which several independent sources agree on, and that nothing there comes from Amazon.
- RoutePayAudit, the files you supply: The four files, that they are supplied by you, that rates and thresholds are not published, and that no sample of a settlement is published.
- RoutePayAudit, the ten rules: What each rule compares, when it reports a difference and when it asks you a question.
- RoutePayAudit, the four verdicts: The four verdicts a week can end with.
- RoutePayAudit, the time to dispute: That no primary source for the time allowed to dispute a settlement was found, and what the product does about it.
- RoutePayAudit, sample report: The invented week: its work summary, its settlement lines, the one difference, the one question and the text of the request.
This guide is general information. RoutePayAudit is software, not legal or accounting advice. RoutePayAudit is not affiliated with, endorsed by, or sponsored by Amazon.
Next step
Upload the settlement and the work summary of a week and see on which days fewer routes were paid than you ran.