Understanding Apple's financial reports

If you've ever opened App Store Connect, checked your revenue in three different places, and gotten three different numbers — congratulations, you've discovered that Apple gives you three separate reporting systems that were never designed to agree with each other.

This isn't a bug. Each system answers a different question, on a different clock, in a different currency model. Once you know what each one actually measures, the mismatches stop being alarming and start being predictable.

The three systems

App Analytics answers "how is my app doing?" It's a product metrics tool: impressions, downloads, conversion rate, and estimated proceeds. It runs on UTC and has its own opinions about what counts — more on that below.

Sales and Trends answers "what sold yesterday?" It gives you next-day data on units and proceeds. Apple is explicit that these are estimates: proceeds are shown in USD "using a rolling average of previous month's exchange rates," while the downloadable reports show amounts "in local currencies as transacted by customers."

Payments and Financial Reports answers "what will Apple actually wire me?" This is the only system with final numbers. Financial reports are generated per currency region, converted to your bank currency at the actual exchange rate Apple applies, and made available "by the first Friday of the current fiscal month" for the previous fiscal month's earnings.

The one-line summary: Analytics is for product decisions, Sales and Trends is for daily monitoring, Financial Reports is for accounting. Only the last one is money.

Why the numbers never match

Apple documents the discrepancies directly in its "Differences in reporting tools" page. The big ones:

Timing of payment collection. Per Apple: "Transactions initiated in a particular month may not appear in Sales and Trends Reports until the customer's payment is processed, collected, and invoiced, possibly in the following fiscal month." And the mirror image: "Transactions without collected payments don't appear in financial reports." A subscription renewal that fires on the last day of a fiscal month can land in next month's financial report. If you reconcile calendar months against fiscal months, you will always find orphaned transactions.

Exchange rates. Sales and Trends converts everything to USD with a rolling average of last month's rates. Financial reports use the actual rate applied when converting each currency region's proceeds to your bank currency. If the euro moved 2% this month, your "estimated proceeds" and your actual payment diverge by roughly that much on EU revenue — before anything else goes wrong.

Different inclusion rules. App Analytics and Sales and Trends don't even count the same events. From Apple's own list: App Analytics excludes restores from its redownloads metric, Sales and Trends includes them. App Analytics excludes sales from TestFlight builds; Sales and Trends includes them. App Analytics excludes watchOS sales and redownloads. App Analytics excludes in-app purchase transactions (like auto-renew renewals) from apps removed from sale; Sales and Trends includes them.

Timezones. App Analytics is UTC-only. Sales and Trends defaults to UTC but can be switched to Pacific Time. If someone on your team toggled that setting, your "daily" numbers are shifted by 7–8 hours relative to Analytics.

None of these differences is large on its own. Stacked together across thousands of transactions, they guarantee that no two surfaces ever reconcile to the cent — and they're not supposed to.

The fiscal calendar: Apple months are not human months

Apple doesn't pay you by calendar month. It pays by fiscal month, and Apple's fiscal calendar is a 52-week (364-day) construction: four 13-week quarters, each split into one 5-week month followed by two 4-week months — the 5-4-4 pattern. That means one fiscal month per quarter is 35 days long and the other two are 28 days.

Concretely, from Apple's fiscal 2026 calendar (as compiled by RevenueCat): fiscal "May 2026" ran May 3–30, and fiscal "July 2026" runs June 28–August 1. So "July revenue" in a financial report includes several days of calendar June, and none of the last days of calendar July. If your bookkeeping compares Apple's fiscal months to Stripe's calendar months, the two will drift in and out of alignment all year.

Because 364 ≠ 365, the calendar slowly slips against real dates, so Apple inserts a 53rd week roughly every five to six years to re-align — most recently in fiscal 2023.

When the money actually lands

Apple's official commitment, from the App Store Connect payments documentation: "payments are made to the bank account and the currency you provided within 45 days of the last day of the fiscal month in which the transaction was completed." That's the contractual ceiling. In practice, the observed pattern (tracked by RevenueCat across years of payouts) is that Apple pays about 33 days after fiscal month close, typically on a Thursday — e.g., fiscal May 2026 (ending May 30) paid out July 2, 2026.

Two more conditions from Apple's docs worth knowing: you must exceed "the minimum monthly payment threshold" for each country or region where you sell (below-threshold amounts roll forward), and Apple's bank "consolidates proceeds for each currency in which you have App Store sales, resulting in a single payment to your bank per fiscal month." One payment, one bank account — split or multiple accounts aren't supported.

So the realistic timeline for a subscription renewal on, say, June 1: it falls in fiscal June (May 31–June 27), the financial report appears in early July, and the money lands around July 30. A sale can easily be 60 days old before it's cash.

Practical takeaways

• Treat Sales and Trends as directionally correct, never final. Apple says so itself.
• Reconcile accounting against Payments and Financial Reports only, and reconcile by fiscal month, not calendar month.
• When Analytics and Sales and Trends disagree, check the known exclusion list (restores, TestFlight, watchOS, timezone) before assuming data loss.
• Budget cash flow on fiscal-month-close + ~33 days, with 45 days as the worst case.

Reevee ingests Apple's reports directly and normalizes fiscal months, currencies, and estimated-vs-final proceeds into one consistent timeline, so you can ask "what did I actually earn in June?" and get one answer instead of three.

Sources

• Apple — Differences in reporting tools (App Store Connect Help)
• Apple — Overview of receiving payments (App Store Connect Help)
• Apple — Download and view reports, Sales and Trends (App Store Connect Help)
• Apple — View payments and proceeds (App Store Connect Help)
• RevenueCat — Apple fiscal calendar year and payment dates