Last month, a 20-route DSP owner found $6,400 in settlement errors by actually reading the line items instead of just checking the deposit amount. Duplicate chargebacks on three routes, an incentive tier miscalculation for one week, and a missing peak-day surcharge that Amazon never applied. That’s $76,800 annualized — found by spending 30 minutes per week on Amazon DSP payment reconciliation instead of assuming Amazon’s math is always correct.
Amazon’s settlement system is complex, opaque, and occasionally wrong. Your weekly settlement is not a single payment — it’s the net result of dozens of calculations involving base rates, per-package fees, incentive tiers, chargebacks, deductions, and adjustments. If you’re booking the bank deposit as one revenue line and moving on, you’re missing errors that cost thousands per year.
This guide covers how Amazon pays DSPs, how to read and reconcile settlement statements, how chargebacks work (and how to dispute them), and the system for catching payment errors before they compound. For the full financial picture, see our Amazon DSP bookkeeping guide.
Amazon pays DSPs through a weekly settlement cycle. Each settlement covers a defined service week (typically Saturday through Friday) and is deposited to your business bank account 5-10 business days after the service week ends.
Every weekly settlement includes these line items:
| Component | Description | Typical Range (25 routes, 6 days) |
|---|---|---|
| Base route pay | Fixed per-route-per-day payment | $27,000 – $42,000/week |
| Per-package / per-stop fees | Variable pay based on volume | $2,250 – $6,000/week |
| Scorecard incentive | Performance-based bonus tied to quality metrics | $0 – $8,000/week |
| Peak/surge pay | Additional pay during high-volume periods | $0 – $4,000/week (seasonal) |
| Step plan payments | Growth incentives for expanding route count | $0 – $2,000/week |
| Chargebacks | Deductions for delivery failures, damage, concessions | -$400 – -$2,500/week |
| Equipment / program deductions | Phone charges, uniform deductions, technology fees | -$200 – -$800/week |
| Adjustments / corrections | Prior-period corrections (positive or negative) | Varies |
| Net settlement deposit | $28,000 – $55,000/week |
The net deposit that hits your bank is the sum of all positive components minus all deductions. Without breaking these apart in your books, you have zero visibility into revenue trends, chargeback patterns, or incentive capture rates.
Amazon provides settlement details through the DSP Console (formerly Relay Console). Each week’s settlement includes:
Download these reports weekly. Don’t rely on the summary alone — the route-level and chargeback detail is where errors hide.
Amazon pays a fixed rate per route per day dispatched. This rate varies by:
Typical base route rates: $180-$280 per route per day. A 25-route DSP dispatching 6 days/week at $220/route generates $33,000/week ($1,716,000/year) in base route pay alone.
On top of the base rate, Amazon pays variable fees based on:
These variable fees typically add $15-$40 per route per day during normal volume and can spike significantly during peak season. Track variable revenue separately from base route pay so you can see how volume fluctuations affect total revenue.
Amazon’s incentive structure is the most significant variable in DSP revenue. Your scorecard rating determines your incentive tier:
| Scorecard Rating | Incentive Range | Weekly Impact (25 routes) | Annual Impact |
|---|---|---|---|
| Fantastic | Full incentive + bonus multiplier | +$4,000 – $8,000 | +$208,000 – $416,000 |
| Great | Partial incentive (60-80% of max) | +$2,400 – $6,400 | +$124,800 – $332,800 |
| Fair | Minimal incentive (0-30% of max) | +$0 – $2,400 | +$0 – $124,800 |
| Poor | No incentive; route reduction risk | $0 | $0 + lost routes |
The annual swing between “Fantastic” and “Fair” can exceed $200,000 for a mid-size DSP. This makes scorecard management a financial function, not just an operations function. Your bookkeeper should track incentive revenue weekly and flag any week where the incentive drops below expected levels.
Critical: Amazon recalculates your scorecard rating weekly. A single bad week can drop you from Fantastic to Great, which reduces incentive pay for that week and potentially the following weeks until metrics recover. Track the specific metrics — delivery completion rate, DPMO, customer feedback, safety score — alongside your financial data to understand exactly which operational metric is costing you money.
Chargebacks are the most contentious part of the DSP settlement. Amazon deducts from your payment for delivery failures attributed to your drivers, and the definitions are broad.
| Chargeback Type | Description | Typical Amount |
|---|---|---|
| Damaged package | Package delivered with visible damage | $15 – $75+ (based on item value) |
| Missing package | Package marked delivered but customer claims not received | $20 – $100+ |
| Concession | Refund Amazon issues to customer attributed to delivery issue | $10 – $200+ |
| Late delivery | Package delivered outside the promised window | $5 – $20 per package |
| DNR (Did Not Receive) | Customer claims non-delivery with investigation | $25 – $150 |
| Safety incident | Accident, property damage, or safety violation | $100 – $5,000+ (varies widely) |
For a 25-route DSP, chargebacks typically total $400-$2,500/week during normal operations and can spike to $4,000-$6,000/week during peak season (higher volume = more opportunities for errors). Annualized:
The difference between best and average is $41,600/year — more than many DSP owners’ take-home pay. Chargeback management is directly connected to profitability.
Not every chargeback is legitimate. Amazon’s automated chargeback system generates false positives, and drivers who provide photo-on-delivery (POD) evidence can often overturn disputed charges.
Not every chargeback is worth the time to dispute. Focus on:
Average dispute success rate for DSPs with good documentation: 30-50%. On $62,400/year in chargebacks, a 35% recovery rate on disputes covering half the total = $10,920/year recovered. That’s meaningful money for 30 minutes of weekly work.
Pro Tip: Create a chargeback tracking spreadsheet (or better, a QuickBooks memo on each chargeback journal entry) that logs: tracking ID, chargeback type, amount, dispute status, and outcome. After 3 months of data, you’ll see patterns — specific drivers, routes, or package types that generate disproportionate chargebacks. Address the root cause and the chargebacks decline.
Here’s how to reconcile a weekly settlement against your books:
Cross-reference Amazon’s reported routes dispatched against your own dispatch log. Ensure:
Compare Amazon’s per-package and per-stop counts against your own delivery data:
Check that Amazon applied the correct scorecard rating for the settlement week:
For each chargeback line item:
The final check: settlement net amount should exactly match the bank deposit. If there’s a discrepancy:
After reconciling hundreds of DSP settlements, these are the errors we encounter most:
Amazon’s scorecard updates weekly, but the incentive tier applied to your settlement sometimes lags by a week. If your scorecard showed “Fantastic” during the service week but the settlement applied “Great” rates, you’re owed the difference.
How to catch it: Maintain your own weekly scorecard log with screenshots. Compare your logged tier to the tier shown on the settlement.
The same tracking number charged in two consecutive settlement weeks. This happens when Amazon’s chargeback system processes a complaint in one week and re-processes it the following week due to a system error or secondary claim.
How to catch it: Sort your chargeback detail report by tracking number and look for duplicates across 4-week rolling periods.
During designated peak days (Prime Day, Black Friday, Christmas rush), Amazon pays elevated per-route or per-package rates. Sometimes these surcharges don’t apply correctly to all routes or all days.
How to catch it: Maintain a calendar of Amazon’s announced peak rate dates and verify that every route dispatched on those dates received the elevated rate.
You dispatched a route, your driver completed deliveries, but the route doesn’t appear on the settlement — or appears as zero-pay. This can happen during station transitions, route reassignments, or system glitches.
How to catch it: Compare your daily dispatch log (route count, driver, station) to the route-level detail on the settlement. Any dispatched route missing from the settlement is money you’re owed.
Contract amendments, rate adjustments, or station changes can cause the wrong base rate to be applied. If you recently negotiated a rate increase or changed stations, verify the new rate is reflected starting from the correct date.
How to catch it: Know your contracted base rate per route by station and route type. Verify the settlement math: routes dispatched x base rate = base route pay.
Weekly reconciliation catches individual errors. Monthly analysis reveals trends that affect strategy:
Track these metrics every month:
| Metric | How to Calculate | What It Tells You |
|---|---|---|
| Gross revenue | Sum all positive settlement components | Total earning power before deductions |
| Chargeback rate | Total chargebacks / gross revenue | Delivery quality cost (target: under 3%) |
| Incentive capture rate | Actual incentive / max possible incentive | Scorecard management effectiveness |
| Revenue per route per day | Gross revenue / (routes x days) | Per-unit economics (trend over time) |
| Revenue per package | Gross revenue / total packages | Volume efficiency (compare to cost/package) |
| Net revenue (after all deductions) | Bank deposits for the month | Actual cash received |
| Settlement-to-deposit lag | Days between service week and deposit | Cash flow planning input |
Pro Tip: Build a 12-month rolling trend for each metric. Seasonal patterns become obvious — and deviations from the pattern become actionable. A chargeback rate that jumps from 2.1% to 4.3% in a single month without a corresponding volume spike signals an operational problem, not a volume problem.
Amazon settlements don’t always match bank deposits one-to-one. Common timing differences:
Use a settlement reconciliation log in your accounting system: for each settlement, record the settlement ID, service week, gross amount, net amount, expected deposit date, and actual deposit date. When all settlements for a month are reconciled to bank deposits with zero variance, you can close the month with confidence.
The best DSP owners spend 30 minutes per week on settlement reconciliation. Here’s the system:
This system catches errors within days instead of months and ensures dispute deadlines are never missed. The time investment: 2.5 hours/month. The typical annual recovery from caught errors: $5,000-$15,000. That’s a $2,000-$6,000/hour return on your reconciliation time.
Want professional settlement reconciliation? Steph’s Books provides weekly Amazon DSP settlement reconciliation as part of our bookkeeping service. We break out every revenue component, track chargebacks, and flag errors before they compound. Get an instant quote for your DSP.
Get a free quote and see how Steph's Books can save you 40-60% vs hiring in-house.
