This article is part of our Complete Guide to Royalty Management.
Apple Books is one of the largest ebook retailers in the world, but its sales reporting can be surprisingly confusing for publishers. Between multiple territory breakdowns, different currencies, and a reporting interface that has changed names several times over the years, getting your Apple sales data into a usable format takes more effort than it should. If you are still copying numbers out of Apple’s dashboard and pasting them into a spreadsheet, there is a much better way.
Here is how to get your Apple Books sales data out of Apple and into royalty software that handles the complexity for you.
Where to find your Apple Books sales reports
Apple provides sales data through two main channels, depending on how your account is set up:
Apple Books for Authors is the simpler dashboard. If you distribute directly through Apple, you can log in at authors.apple.com to view sales summaries and download reports. The interface gives you a high-level view of units sold, earnings, and trends across territories.
App Store Connect (formerly iTunes Connect) is the more comprehensive option. Most publishers who distribute through Apple — whether directly or via an aggregator — will find their detailed sales and financial reports here. Log in at appstoreconnect.apple.com, navigate to Sales and Trends, and download reports for the period you need.
When downloading, select the report type (Sales), the date range, and the territory or territories you want. Apple lets you pull reports by individual territory or across all territories in a single file. For royalty processing, downloading a consolidated report is usually the most efficient approach.
Understanding Apple’s reporting structure
Apple’s reports can feel overwhelming at first glance because of how they break down data. A single report may include rows for multiple territories, multiple currencies, and multiple transaction types — purchases, pre-orders, refunds, and free downloads all appear in the same file.
Each row contains a territory code and a currency code, so your US sales appear in USD, your UK sales in GBP, your Australian sales in AUD, and so on. Apple sells ebooks in over 50 countries, so if you have wide distribution, your report could contain a long list of currencies.
The transaction types matter too. Apple distinguishes between new purchases, returns, and updates. When you import this data into royalty software, the system needs to handle returns as negative quantities so your net sales figures are accurate.
Apple’s payment timeline
Apple pays publishers monthly, typically within 45 days of the end of the fiscal month. So sales from January would normally be paid by mid-March. This is faster than some distributors — Ingram’s 90-day cycle, for example — but slower than others.
The timing matters because you need to match sales data to the correct royalty period. When you import your January Apple Books sales, the corresponding income payment will not arrive for about six weeks. If you are also importing from Amazon KDP with its 60-day delay, and Ingram with its 90-day delay, keeping track of which payment belongs to which sales period becomes a real challenge without proper software.
Preparing your file for import
This is the part where publishers most often go wrong. Do not edit the sales file before uploading it. Do not open it in Excel and adjust columns, do not delete rows you think are unnecessary, and do not try to merge multiple territory files into one.
When your royalty software natively supports Apple’s file format, the raw file is the correct file. Any modifications — even something as minor as re-saving in a different format — can break the column structure or encoding that the import process relies on.
Download the file, leave it untouched, and upload it directly. If you want to rename the file for your own organization (something like “Apple-Books-Sales-2026-01”), that is fine as long as you do not open and re-save the contents.
Step-by-step: uploading Apple Books sales in Royalties HQ
Royalties HQ natively supports Apple Books sales reports as one of its 12 built-in file formats. The import process takes about a minute:
- Go to the main menu and click Add New Sales
- Drop your Apple Books sales file into the upload zone (or click to browse)
- Royalties HQ automatically detects the file as an Apple Books report. Confirm the file type in the dropdown and click Continue
- The system validates the file contents. If everything checks out, the status shows “Ready to import”
- Click Import to bring in the data
- Each row from the Apple report becomes a sales line, grouped into one or more sales batches
After importing, you will need to record a publisher income payment for each sales batch. This links the sales data to the actual money Apple deposited in your account, which is what drives the royalty calculations downstream.
Multi-currency and territory considerations
Apple’s multi-territory reporting is one of the areas where dedicated royalty software really earns its keep. A single Apple Books report might contain sales in USD, GBP, EUR, AUD, CAD, JPY, and a dozen other currencies. Handling all of those conversions manually — and applying the correct exchange rate for each payment — is exactly the kind of tedious, error-prone work that burns hours every royalty period.
When you import an Apple Books file into Royalties HQ, the system preserves each territory and currency as-is. Your Australian sales stay in AUD, your Japanese sales stay in JPY. When you later record the publisher income payment and run royalties, the platform handles currency conversion automatically based on the rates at the time of payment.
If multi-currency complexity is a recurring headache in your workflow, our deep dive on managing multi-currency royalties covers the strategies that work best for publishers selling across international markets.
Tips for a smooth Apple Books import workflow
Download reports as soon as they are available. Apple finalizes sales data after the fiscal month closes. Pulling reports promptly keeps your royalty data current and avoids a backlog when it is time to run statements.
Use a consistent folder structure. Organize your downloaded files by distributor, year, and month. When you need to re-import or audit a past period, knowing exactly where the original file lives saves a surprising amount of time.
Do not confuse sales reports with financial reports. Apple provides several report types in App Store Connect. For royalty processing, you want the Sales report, not the Financial report. The financial report is useful for reconciling payments but does not contain the line-level detail you need for per-title royalty calculations.
Import regularly, not in bulk. Processing one month at a time is far easier to verify than importing six months at once. Build a monthly routine — download from Apple, upload to Royalties HQ, record the payment when it arrives — and the whole process stays manageable.
Building a complete distributor import workflow
Apple Books is just one piece of the puzzle. Most publishers also distribute through Amazon KDP, Ingram, and other channels, each with its own file format and payment schedule. The goal is to build a repeatable monthly routine where you download from each distributor, upload without reformatting, and let the software handle matching, currency conversion, and royalty calculations.
For a full walkthrough of every supported format and the upload process, see our importing sales data documentation. And if you are evaluating whether your current setup can handle the complexity of multi-distributor royalty management, download our free guide for a closer look at what a modern royalty workflow looks like.