This article is part of our Complete Guide to Royalty Management.
Google Play Books is one of the most overlooked sales channels in publishing, but it is steadily growing in importance. For publishers who already manage imports from Amazon KDP and Ingram, adding Google Play often means yet another report to download, another currency to track, and another payment cycle to reconcile. The result is more manual work piled onto an already stretched royalty process.
The good news is that importing Google Play sales data into royalty software does not have to be complicated. Here is how to get your reports out of Google and into a system that handles the rest.
Where to find your Google Play Books sales reports
Google provides sales data through the Google Play Books Partner Centre. This is the dashboard where you manage your catalog, pricing, and account settings. To download your sales reports:
- Log in to the Partner Centre at play.google.com/books/publish.
- Navigate to Payment Centre (or Reports, depending on your account type).
- Look for the Sales Transaction Reports section.
- Select the month you need and download the report.
Google generates these reports on a monthly basis. Each report contains transaction-level data for every sale across all territories where your books are available. Unlike Amazon KDP, which produces separate files per marketplace, Google Play consolidates everything into a single file — but that file includes multiple currencies, which brings its own challenges.
Understanding Google Play’s reporting structure
The transaction report includes sales from every territory where your titles were purchased during the period. Each row represents an individual transaction with details like the book title, ISBN, sale date, list price, Google’s commission, and your net earnings.
The key thing to understand is that Google reports in the buyer’s local currency. A sale in Japan appears in JPY, a sale in Germany appears in EUR, and a sale in the US appears in USD — all within the same file. This is different from distributors that group sales by marketplace into separate reports.
For publishers managing royalties across international territories, this multi-currency structure is both a blessing and a headache. You get all your data in one place, but you need software that can handle the currency complexity without forcing you to manually separate and convert each line. If currency handling is a pain point for you, our guide to managing multi-currency royalties covers the broader challenge in detail.
Google Play’s payment timeline
Google typically pays publishers on a monthly cycle, with payment arriving around the end of the month following the sales period. January sales, for example, would generally be paid out by the end of February or early March.
This is a shorter delay than many other distributors. Amazon KDP pays roughly 60 days after the sales month, and Ingram operates on approximately a 90-day lag. Google’s faster turnaround means you can often reconcile Google Play income before your other distributor payments have even landed.
That said, exact timing can vary depending on your payment threshold settings and your country. Keep an eye on the Payment Centre for the actual deposit dates each month.
Preparing your file for import
This is the part where less is more. When you download a sales transaction report from Google Play, do not open or edit it. Do not rename columns, delete rows, or try to clean up the data before uploading. The raw file, exactly as Google provides it, is what your royalty software expects.
This is a common theme across all distributor imports — and one of the most frequent mistakes publishers make. If your software natively supports the file format, the unmodified original is always the safest bet. The moment you open and re-save a file, you risk altering formatting, encoding, or cell types in ways that break validation.
Step-by-step: uploading Google Play sales into Royalties HQ
Royalties HQ natively supports Google Play Books sales reports as one of its 12 built-in file formats. The import process works the same way as any other supported distributor:
- Go to the main menu and click Add New Sales.
- Drop your Google Play sales file into the upload zone.
- Royalties HQ automatically detects the file as a Google Play report. Confirm the format in the dropdown and click Continue.
- The system validates the file contents. If everything checks out, the status changes to “Ready to import.”
- Click Import. Each transaction row becomes a sales line, grouped into one or more sales batches.
Because the Google Play file contains transactions in multiple currencies, Royalties HQ preserves each currency as-is during import. Your USD sales stay in USD, your EUR sales stay in EUR, and so on. When you later add publisher income payments, the system handles reconciliation and conversion automatically.
Multi-currency considerations
Google Play’s single-file, multi-currency approach means you do not need to worry about downloading separate reports per territory. But it does mean you need royalty software that properly tracks and converts those currencies when calculating what you owe your authors.
If your author contracts specify royalties in a single base currency — say GBP — then every sale in USD, EUR, JPY, or any other currency needs to be converted before the royalty calculation runs. Royalties HQ handles this during the royalty run process, applying exchange rates so your statements are accurate regardless of how many currencies appear in the source data.
For a deeper look at how currency conversion fits into the royalty workflow, see multi-currency royalties.
Tips for a smooth Google Play import workflow
Download reports as soon as they are available. Even if payment has not arrived yet, having the sales data in your system means you are ready to reconcile the moment the deposit clears.
Do not combine files from different months. Upload each monthly report as its own file. This keeps your sales batches cleanly separated by period and makes it much easier to spot discrepancies.
Cross-check against the Payment Centre. Google’s payment summaries in the Partner Centre should align with the totals in your transaction reports. If they do not match, investigate before importing — it is much easier to catch issues before the data is in your system than after.
Store your originals. Keep the raw files from Google in a folder organized by month and year. If you ever need to re-import or audit a period, the unmodified originals will save you a trip back to the Partner Centre.
Building a complete import routine
Google Play is just one piece of the puzzle. Most publishers import sales from multiple distributors each period — Amazon KDP, IngramSpark, and others. The goal is a repeatable monthly routine: download each report, upload it without editing, and let the software handle matching, currency conversion, and royalty calculations.
Once that routine is in place, the hours you used to spend wrangling spreadsheets shrink to minutes. For a full walkthrough of the import process and all supported file formats, see the importing sales data documentation. And if you are still evaluating whether your current setup can keep up, download our free guide for a closer look at what a modern royalty workflow looks like.