RoutePayAudit

How it works.

From your source documents to the text of a request. You sign in with your email address and password.

Three steps.

  1. 01

    Upload or forward your files

    Upload or forward your settlement, work summary, scorecard and rate card as supported PDF or CSV files. You decide whether your agreement permits sharing them.

  2. 02

    We recalculate the week

    We verify the figures and their meaning against your sources, then compare them using the rate version you confirmed. A missing or uncertain figure becomes a question, not a difference.

  3. 03

    You send the request

    For each difference you get a short text in your own voice, with the figures and the lines it rests on. You file it yourself.

The files you supply.

We recalculate the weekly settlement of a delivery service partner company from the settlement, work summary, scorecard and rate card files you upload or forward. We read supported PDF and CSV files. A value is used only after it is verified against the source, including what it means and which station and period it belongs to. Missing, uncertain, conflicting or incomplete data becomes a question to you, not a difference in payment. We show potential differences supported by those sources and prepare the text of a request that you can file yourself.

There is no published sample of a settlement or list of its columns. Rates and thresholds differ from one partner to the next and are not published.

What a settlement is, as far as is known.

Only what several independent sources agree on. Nothing here comes from Amazon itself.

  • Amazon pays its delivery service partners through a weekly settlement statement.
  • A scorecard is made every week, and its tier is what a performance bonus is paid on.
  • 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.

The ten rules.

A finding is always an amount in your favour, in dollars and cents, from figures that were read. Anything unread, missing or unconfirmed is a question. Differences under one dollar are not shown, because they are rounding.

RuleWhat it checksWhen it reports a difference, or only asks
S1Routes paidYour work summary lists a day in full, and the settlement pays fewer routes of that type than you ran. The amount is the missing routes times the rate: the one the settlement pays for that type that week, or else the one in your confirmed rate card. With no rate known it is a question, without an amount.
S2RateYour rate card is confirmed, the route type and unit match, and the rate paid is below the rate in your rate card for that date. If the rate card is not confirmed or lacks the type, it is a question.
S3Scorecard tierA bonus line names a tier, the rate version you confirmed says how many weeks back the bonus is paid from, the scorecard of that week is among your files, its tier is higher than the tier paid, and both rates are in your confirmed rate card. Otherwise a question.
S4Peak and bonus premiumYour confirmed rate card has a premium for dates in the week, and the settlement pays none or less. If the quantity is not read, it is a question.
S5Repeated deductionTwo chargebacks or two deductions have the same reference, the same amount and the same date, in this settlement or in an earlier settlement of the same station that you supplied. A less certain repeat is a question at most: another category or date, a credit with the same reference, or no reference.
S6Fixed payment for vehiclesNever a finding in this version. We ask whether the amount is what you expected.
S7Fuel and variable costsNever a finding in this version. We ask whether the amount is what you expected.
S8Deductions for damageNever a finding in this version. We ask whether the deduction is expected, and point you to your own incident records.
S9ArithmeticQuantity times rate comes to more than the line pays. An overpayment is not a finding. If the lines add up to more or less than the net amount, it is a question: a line may be missing from what we read.
S10Van leaseNever a finding in this version. We ask whether the amount matches your lease.

One line never gives two amounts: when two rules dispute the same line, the larger one stays.

Four verdicts for a week.

VerdictWhat it means
DiscrepancyAt least one finding. Each comes with the lines it rests on and the text of a request.
Needs dataNo finding, but a question for you, or a document that has not been supplied. A missing value is never read as an error.
No difference foundEvery rule that applies was checked and found nothing in the verified source figures.
Not a settlementThe file has no lines, or every line is of an unknown kind. No rule runs.

The time to dispute.

We found no first-hand 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. We then count from the day the settlement appeared. Without it the deadline shows as unknown, and the advice is to file right away.

Start the free check

See it on an invented week: the sample report.