At a glance
The average number of days between a sale and the cash landing in your bank, across the settlement periods in the window. Amazon does not pay you per order, it pays on a recurring disbursement cycle, holds a reserve, and can extend holds for newer or at-risk accounts. This card is the cash-flow truth behind your revenue: high sales mean little if the money is stuck in a long settlement queue. It is the metric a finance lead checks when planning working capital.
| What it counts | The average elapsed days from order / sale to funds disbursed, measured across the settlement statements in the period. It captures the real lag your cash experiences, not the headline disbursement frequency. |
| Why it is not just “14 days” | Amazon’s standard disbursement cycle is roughly every two weeks, but reserves, account-level holds, and delivery-date-based release rules can stretch the effective settlement time well beyond the nominal cycle. |
| What drives it | Account age and standing (newer / at-risk accounts face longer holds), the reserve policy applied to your account, dispute and chargeback holds, and the gap between order date and the delivery-confirmation that releases funds. |
| Why it matters | It is the working-capital constraint. A seller funding inventory from Amazon payouts needs to know whether cash takes 7 days or 20 to come back. A rising settlement time can quietly starve cash flow even as sales grow. |
| Relationship to other cash cards | This is the average lag. The standing balances and oldest stuck payout live on the settlement / payout sibling cards. |
| Fulfilment scope | Account-wide. FBA and FBM funds both flow through the same disbursement engine, though delivery-confirmation timing can differ. |
| Time window | 90D (averaged across the settlement periods in the trailing 90 days for a stable read) |
| Alert trigger | >15 days. An average settlement lag above 15 days flips the card and notifies owner and finance. |
| Roles | owner, finance |
Calculation
Calculated automatically from your Amazon Seller Central data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A US seller, under a year old, mostly FBM on amazon.com. Settlement statements across the trailing 90 days, ending 20 Mar 26.| Settlement statement | Sales in period | Avg days sale-to-disbursement |
|---|---|---|
| Statement 1 | $42,000 | 16 days |
| Statement 2 | $38,500 | 18 days |
| Statement 3 | $45,200 | 17 days |
| Avg Days to Settlement (this card) | ~17 days |
- 17 days is past the 15-day alert. The nominal Amazon cycle is around two weeks, but this seller’s effective lag is longer because a reserve and delivery-based release rules are holding funds. The card surfaces the real lag, not the advertised cycle.
- Account age is the most likely driver. Newer accounts face longer holds and larger reserves while Amazon builds trust. As the account matures and standing stays healthy, the reserve typically eases and the lag shortens.
- This is a cash-flow constraint, not a revenue problem. Sales are healthy at over $40k per statement. The issue is timing, the seller cannot recycle that cash into inventory as fast as the sales suggest. Finance needs to plan working capital around 17 days, not 14.
- Delivery-confirmation timing matters. Funds tied to delivery-date release rules sit longer when transit times are long. Faster, tracked delivery can shorten the effective lag on the affected orders.
Sibling cards merchants should reference together
Settlement lag is one piece of the cash-flow picture. Read it with the balance and payout cards:| Card | Why pair it with Avg Days to Settlement |
|---|---|
| Pending Settlement | The £/$ currently waiting to be disbursed. The lag tells you how long; this tells you how much is in the queue. |
| Oldest Pending Payout (days) | The worst-case single payout. Average lag can look fine while one payout is badly stuck; check both. |
| Net Revenue (after fees + refunds) | What you actually bank. Settlement lag is the timing of that net cash arriving. |
| Total Revenue | The top line. A long settlement lag means revenue and available cash diverge, which matters for inventory funding. |
| FBA Fees | Fees are netted at settlement. Understanding what is deducted helps reconcile the disbursed amount against sales. |
| Referral Fees | Another deduction taken at settlement, part of the gap between gross sales and disbursed cash. |
Reconciling against Amazon Seller Central
Where to look in Seller Central:Payments → Payments dashboard (Statement View and Transaction View). Each settlement statement shows the period, the opening / closing balance, the reserve, and the disbursement date. Compare the sale dates within a statement to its disbursement date to see the lag this card averages.The Reserve section explains why funds are held; a delivery-date-based reserve is a common reason the effective lag exceeds the nominal cycle. Timing and reporting-lag table:
| Topic | Detail |
|---|---|
| Timezone | Settlement statements use the marketplace’s local timezone for period boundaries; Vortex IQ averages across statements consistently. Edge orders can shift slightly between views. |
| Reserve policy | Account-level reserves (including delivery-date-based reserves) extend the effective settlement time beyond the nominal cycle. The card reflects the real lag including reserves. |
| Account standing | A drop in account health can trigger longer holds or a larger reserve, lengthening the lag. Recovery shortens it over time, not instantly. |
| Disbursement cadence | The nominal cycle is roughly every two weeks; some accounts can request more frequent disbursement, which changes the lag. The card measures the actual cadence your account experiences. |
| Reason | Direction | Why |
|---|---|---|
| Sale-date vs available-date basis | Either direction | The lag depends on whether you measure from order date, ship date, or delivery date. The card uses a consistent basis; a manual calculation from a different date will differ. |
| Reserve handling | Ours reflects real lag | If you compute lag ignoring the reserve, you will get the nominal cycle (~14 days). The card includes reserve-driven delay, so it can read longer. |
| Statement averaging | Smoothing | Averaging across 90 days of statements smooths a single unusual statement; a one-statement spot check can read higher or lower. |
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
stripe.avg-days-to-payout | Payment-processor peer. A seller’s own-site Stripe payouts are usually far faster (often a couple of days) than Amazon settlement. Useful to compare channel cash velocity. | Entirely different payout engines and schedules; faster Stripe payouts are expected. |
ebay.oldest-pending-payout | Marketplace peer. eBay’s managed-payments cadence differs from Amazon’s. Used for cross-marketplace cash-flow comparison. | Independent payout systems; eBay’s hold rules and cadence are not Amazon’s. |