Amazon DSP Settlements Explained: How to Read Your Weekly Statement Like a CFO
A deep-dive into every line of your Amazon DSP weekly settlement — what each section means, where the numbers come from, and what to flag before you sign off.
Your weekly settlement from Amazon isn't just a paycheck summary. It's a detailed financial report covering every dollar earned, every deduction applied, and the net amount heading to your bank account. Most DSP owners glance at the bottom line and move on. Reading it like a CFO means understanding every line — and knowing which ones to question.
The Settlement Structure
Every settlement follows the same basic format, though the specific line items vary by contract type and station. At a high level, it breaks down into three sections:
- Header: Settlement period (start and end dates), station code, DSP name, and settlement generation date.
- Revenue: Everything Amazon is paying you — variable pay, incentive pay, and any other compensation.
- Deductions: Everything Amazon is taking back — vehicle costs, insurance, technology fees, damage claims, penalties, and miscellaneous charges.
The net settlement is gross revenue minus total deductions. That's the number that (eventually) shows up in your bank account via Payee Central.
Reading the Revenue Side
Variable Pay
Variable pay is the largest revenue component for most DSPs — typically 60-75% of gross settlement. It's calculated based on your contract structure:
- Per-route contracts: Number of completed routes multiplied by the per-route rate. Each route type (standard, extended, nursery) may have a different rate.
- Per-package contracts: Total packages delivered multiplied by the per-package rate. Volume-based — more packages, more pay.
- Per-block contracts: Number of delivery blocks (time-based shifts) multiplied by the block rate. Less common but used in some markets.
What to verify: Compare the route count or package count in the settlement against the Work Summary Tool (WST) for the same period. If WST shows 172 completed routes but the settlement credits 169, three routes were dropped from the billing. Each dropped route is $180-250 unearned.
Incentive Pay
Incentive pay is tied to your scorecard performance tier. Amazon evaluates DSPs on metrics like delivery success rate, customer experience, safety (Mentor/Netradyne scores), and driver compliance. The tiers are:
| Tier | Typical Per-Package Incentive | Requirements |
|---|---|---|
| Fantastic+ | Highest rate | All metrics exceed thresholds |
| Fantastic | High rate | Most metrics at or above thresholds |
| Great | Moderate rate | Meets minimum requirements |
| Fair | Low or no incentive | Below thresholds on key metrics |
What to verify: Check your scorecard portal and confirm the tier shown matches the incentive rate applied in the settlement. Tier changes should take effect immediately, but there can be a lag of one settlement period.
Other Revenue
Some settlements include additional revenue lines: recruitment bonuses, referral payments, seasonal surge pay, or special program compensation. These are less common but should still be verified against what was communicated by your Amazon operations manager.
Reading the Deductions
Fixed Deductions
Fixed deductions should be the most predictable part of your settlement. They include:
- Vehicle lease payments: Per-vehicle monthly charge, divided across settlement periods. Should match your lease agreement.
- Insurance premiums: Group insurance deductions, typically per-vehicle. Check quarterly for rate changes.
- Technology fees: Monthly charges for Netradyne cameras, Mentor app licenses, and other required technology. Should match your active fleet count — if you have 35 vehicles, you should see charges for 35 units, not 38.
What to verify: Compare the vehicle count implied by these deductions against your actual active fleet. Changes in fleet size should be reflected within one settlement period.
Variable Deductions
These fluctuate based on operational events:
- Vehicle damage/accident charges: Should have a corresponding incident report. Cross-reference the date and vehicle against your records.
- AFS charges: Amazon Flex Substitution — premium charges for routes you couldn't fill. Verify the route code and date to confirm you actually failed to cover the route.
- Late cancellation penalties: Check whether the cancellation was within the acceptable window. If Amazon canceled the route (not you), the penalty should not apply.
- Fuel surcharges and tolls: Should correspond to your station's region and route geography. Spot-check occasionally.
What to verify: Every variable deduction should have a corresponding event in your operational records. If a charge appears without a matching event, it's a candidate for dispute.
Matching Settlement to Deposit
After reviewing the settlement itself, the next step is confirming the payment arrived correctly.
- Note the net settlement amount from the settlement report.
- Open Payee Central and find the corresponding payment. Match by date range (the deposit typically arrives 7-14 days after the settlement period ends), not by exact dollar amount.
- Compare three numbers: settlement gross, settlement deductions, and settlement net against Payee Central's gross, deductions, and net deposit.
- If the net amounts match, you're aligned. If they don't, the discrepancy is usually in the deductions — something was added or adjusted between the settlement report and the actual payment.
- Confirm the Payee Central amount matches your bank deposit. If those two don't match, it's a payment processing issue separate from the settlement.
A matching net settlement can hide offsetting errors. If one deduction was too high by $300 and another was too low by $300, the net looks correct but you're still being overcharged on one and undercharged on another. Check line items, not just totals.
Red Flags to Check Every Week
Not every line item needs deep investigation every period. But these signals should trigger a closer look:
- Route count mismatch: Settlement route count lower than WST route count for the same period. Dropped routes.
- New deduction categories: A charge appearing for the first time without prior communication. Don't accept it — investigate.
- Incentive rate change: The per-package incentive rate changed from the prior period. Verify it matches your current scorecard tier.
- Net settlement trending down: If net settlement is decreasing week-over-week without corresponding operational changes (fewer routes, more AFS, lower tier), something in the billing changed. Find what.
- Deductions exceeding 25% of gross: While normal deductions vary, if total deductions spike above your typical percentage, review each line item.
Making It a Habit
Reading your settlement thoroughly takes 20-30 minutes per week. It's the highest-ROI financial habit a DSP owner can build. The goal isn't perfection — it's catching the errors that are worth disputing before the 7-14 day window closes.
Set a calendar reminder for the day after settlements are generated. Block 30 minutes. Open the settlement, WST, and Payee Central side by side. Over time, you'll develop an intuition for what looks right and what doesn't — and the numbers will start to tell a clearer story about where your money is actually going.
Want to see what Amazon owes you?
We run free settlement audits for DSP owners. 10 minutes to set up. No cost, no catch.
Book a Free Audit