google play estimated sales vs earnings
Google Play Estimated Sales vs Earnings Reports
Estimated sales are useful for fast trend analysis. Earnings reports are designed for finalized financial reporting. Mixing them creates bad numbers.
Google Play developers often see different totals across Play Console reports and assume something is broken.
Usually, the reports are answering different questions.
Estimated Sales Report
Google describes estimated sales as low-latency information about app, in-app product and subscription sales.
It can contain the amounts paid by buyers without deducting taxes or Google fees. Google explicitly says it should not be relied on for accounting.
Use it for:
- recent sales monitoring
- product trends
- short-term analytics
Earnings Report
The Earnings Report is generated around the beginning of the month and is the more appropriate source for accounting workflows.
Use it for:
- monthly financial close
- fee and tax analysis
- revenue normalization
- payout reconciliation
Store the report state
The underlying lesson applies beyond Google Play.
Every revenue record should know whether it is estimated, finalized or paid. Otherwise a dashboard may combine numbers that belong to different stages of the revenue lifecycle.
Faturatik's revenue model is built around keeping those stages distinguishable rather than presenting one unexplained total.
Frequently Asked Questions
Does Google Play Estimated Sales deduct Google fees?
Google says the Estimated Sales Report does not deduct taxes or Google fees from its totals.
Which Google Play report is better for accounting?
Google recommends using the Earnings Report rather than Estimated Sales for accounting.
Why should estimated and finalized revenue be stored separately?
Because they represent different stages of the financial lifecycle and can legitimately contain different totals.