At a glance
Days Since Last Payout is a simple cash-flow watchdog: how many days have passed since JD last settled money into your account. JD pays POP marketplace sellers on a settlement cycle, and a healthy store sees that clock reset regularly. When the counter climbs past the normal cycle, it is an early warning of a held settlement, an account-standing flag, a banking or compliance hold, or simply a cycle that has stalled. For finance it is the difference between assuming cash is on the way and discovering a freeze a week too late. It sits in the Economics family and reads best beside the pending-payouts, oldest-pending-payout, and net-revenue cards below.
| What it counts | The number of days elapsed since the merchant last received a JD settlement payout, counted to the present. |
| Sample type | Backend API data from JD.com, refreshed on the standard data refresh. |
| Why it matters | A payout clock that runs longer than the normal settlement cycle is the earliest sign of a held or stalled settlement, an account-standing issue, or a banking hold. Catching it early protects cash flow and gives time to resolve the cause before it compounds. |
| Reading the value | Read it against your normal settlement cycle. A value at or below the cycle length is healthy; a value climbing past it, especially past the 7-day alert, signals a payout that has not landed when expected. |
| Currency | count |
| Time window | RT |
| Alert trigger | >7d |
| Sentiment key | jd_payout_age |
| Roles | owner, finance |
Calculation
The date of the most recent settled JD payout subtracted from the current date, in whole days. The clock resets to zero each time a new payout settles. Pending or scheduled payouts that have not yet landed do not reset the counter, so the value reflects actual cash received, not promised cash. It is a real-time read, recomputed on every refresh.Worked example
A representative reading of Days Since Last Payout for a typical merchant on JD.com. Suppose your settlements normally land every 5 to 7 days, so the counter usually sits between 0 and 6. This week it reads 9 and the alert has tripped. Cross-referencing the pending-payouts card shows a sizeable balance accrued and ready, which rules out “no sales to settle” and points to a held or delayed settlement. The likely causes narrow to an account-standing flag, a bank-detail mismatch, or a compliance review. The action is to check JD Seller Centre’s settlement and account-health pages immediately, confirm bank details, and open a ticket if the hold is not self-explanatory, rather than waiting for the next cycle and losing another week. For deeper investigation, use Vortex Mind to correlate the payout gap with account-standing events; for natural-language exploration, ask Ask Viq “has my JD payout cycle slipped past its normal cadence”.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
jdc_payouts_pending | Economics sibling: the balance waiting to settle, which the payout clock should be clearing. |
jdc_payout_age_days | Economics sibling: how long the oldest specific payout has been pending. |
jdc_net_revenue | Revenue sibling: the net revenue that ultimately feeds settlements. |
jdc_fee_total | Economics sibling: fees deducted before settlement. |
jdc_revenue_at_risk | Economics sibling: revenue exposure that a held payout can compound. |
Reconciling against the vendor’s own dashboard
Where to look in JD.com’s own dashboard: JD’s Seller Centre settlement and bill views list each payout with its settlement date. The most recent settled date there should match the reset point this card counts from. The account-health page is where a hold or standing flag would explain a stalled counter. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Settled vs scheduled. Vortex IQ counts from the last settled payout; a scheduled-but-unpaid payout does not reset the clock. | Variable | Confirm the payout has actually settled, not just scheduled. |
| Time zone. The day count uses China Standard Time; confirm your reporting profile aligns. | Marginal | Confirm time zone match. |
| Refresh lag. A payout that settled minutes ago may not have synced; the counter resets on the next refresh. | Marginal | Force a manual refresh after an expected settlement. |
| Banking transit. JD may mark a payout settled before it clears your bank; the clock follows JD’s settled date. | Marginal | Allow for bank transit time separately. |