KDP Reports Explained: Dashboard, Royalties Estimator, Orders — and Which Numbers to Trust
The KDP dashboard, the Royalties Estimator, the Orders report and the Payments report update at different speeds and measure different things — which is why they never quite agree. Here is what each report actually contains, how fresh each number really is, and the one that finally settles what you earned.
Open your KDP reports on any given morning and you can find three different answers to "how much did I earn yesterday?" — one on the dashboard, one in the Royalties Estimator, one in Orders. None of them is wrong. They are different instruments, updating at different speeds, measuring different events. Once you know which is which, the disagreements stop being alarming and start being information.
The map: what each report is for
| Report | What it counts | How fresh |
|---|---|---|
| Dashboard ("Today") | Orders and pages read as they happen | Near-real-time (refreshes throughout the day) |
| Royalties Estimator | Estimated royalties per book and marketplace | Typically 24–48 hours behind |
| Orders | Units ordered (before returns/cancellations) | Up to ~24 hours behind |
| KENP Read | Kindle Unlimited pages read | Daily counts; the rate that prices them arrives mid-following-month |
| Payments | What was actually paid, when, to which account | Finalized monthly, on the 60-day cycle |
The single most useful thing to internalize: the dashboard is a heartbeat monitor, not an accounting system. It exists to tell you something is happening. The money is settled elsewhere, later.
Why the numbers "don't match"
Three structural reasons, each responsible for a daily forum thread:
- Orders are not sales. The Orders report counts orders when placed; a cancellation or return later reverses it. The Royalties Estimator counts royalty-bearing transactions. On any single day the two legitimately diverge.
- Estimates are estimates. The Royalties Estimator prices Kindle Unlimited pages at a provisional rate, because Amazon only announces the real per-page rate for a month around the 15th of the following month. Every KU-heavy account sees its month restated slightly, weeks later — that is the KENP fund mechanism working as designed, not a bug.
- Timezones and refresh lags. Each marketplace reports on its own clock. A late-evening US sale can land on "tomorrow" in a European author's view, and a number you screenshot at 9 a.m. may be revised by noon.
So the honest hierarchy of trust is: Payments > Royalties Estimator > Orders > Dashboard — exactly the reverse of how often most authors look at them.
The report most authors never open
The Payments report is the only page that shows money, not estimates: each payment, its marketplace, its currency, the account it went to, and whether it was actually released or held under a threshold. When the dashboard says you earned and the bank says you did not, this report holds the answer — usually a threshold, a rejected transfer, or withholding tax you forgot was being applied.
The number missing from every KDP report
Here is what no KDP report will ever show you: what those royalties cost you to earn. Your Amazon Ads spend lives in a completely separate console, with its own dashboard, its own lags, and its own currency handling. KDP can tell you royalties were $2,400 last month. It cannot tell you that you spent $1,900 in ads to get them — and that the real number for the month was $500, not $2,400.
That join — royalties from one system, spend from another, per book, per marketplace, net of tax and currency — is precisely the work most authors do in a spreadsheet, once a month, approximately. It is also where the biggest decision errors hide, as we showed in net profit per book.
Where TrueRoyalties fits
TrueRoyalties reads your real KDP data — royalties, orders, KENP reads, per marketplace — and joins it continuously to your Amazon Ads spend, so the three-dashboards problem collapses into one view with one number per book: Net Profit = Royalties − Ad Spend. The KDP reports remain your source of record; TrueRoyalties is the layer that makes them answer the question they were never designed for — is this actually making me money?