App Store payout schedule explained: when Apple pays out and how to forecast your cash flow

Apple doesn't pay you the day after a sale. Understanding the fiscal calendar, minimum thresholds, and tax prerequisites lets you forecast cash flow accurately and avoid the surprises that catch many indie developers off-guard.

If you've ever wondered why your January revenue doesn't arrive in your bank account in February, you're not alone. Apple's payment cycle operates on its own fiscal calendar—one that rarely aligns with the calendar months you use to manage expenses, contractor payments, and SaaS subscriptions. Getting this wrong causes cash flow surprises that are entirely avoidable with a little upfront planning.

This post walks through how Apple calculates the timing of your payout, what can delay your first payment, how minimum thresholds work across currencies, and how to build a practical cash flow forecast from the data already available in App Store Connect.

How Apple's fiscal calendar shapes your payment timing

Apple does not use calendar months for financial reporting. Apple operates on a fiscal calendar where each fiscal year runs roughly from late September to mid-September of the following year. Each fiscal month starts on a Sunday and ends on a Saturday, which means fiscal month start and end dates shift relative to the Gregorian calendar each year.

Why does this matter for your cash flow? Because your earnings are grouped by Apple's fiscal month, not the calendar month in which the sale occurred. A subscription renewal processed on January 31 might fall into Apple's Fiscal January, or it might be counted in Fiscal February, depending on exactly where that date falls in Apple's fiscal week structure for that year.

App Store Connect's Payments and Financial Reports section makes the grouping explicit: you can see which fiscal month each payment covers and the precise dates on which Apple committed to issue funds. Apple also publishes its fiscal period dates in its investor relations materials each year, which you can cross-reference to understand exactly how transactions will be bucketed.

The payout cycle: from sale to bank account

Once a fiscal month closes, Apple processes your earnings and typically issues payment within approximately 30 days after the fiscal month end date. The funds then take additional time to clear your bank account depending on your banking institution, your country of residence, and the wire transfer routing involved.

In practice, a sale made in early January may not clear your bank account until mid-to-late March—a rough cycle of 45–75 days from transaction to cleared funds. This is significantly longer than settlement windows offered by payment platforms commonly used for web subscriptions, and it catches many indie developers off-guard during their first year on the App Store.

Apple does not offer accelerated settlement options. The timeline is consistent and non-negotiable. This means your financial planning must account for a rolling 45–75 day lag: revenue that looks strong in a given fiscal month cannot be counted on for expenses in the same calendar period.

The table below illustrates a simplified payout timeline for 2026, showing the mismatch between when users are billed and when funds clear:

The specific dates shift slightly year to year due to Apple's fiscal calendar structure. Always verify against the current year's published fiscal dates rather than assuming the previous year's schedule repeats exactly.

Minimum payment thresholds and multi-currency considerations

Apple does not automatically pay out earnings every fiscal month. Payments are only issued when your accumulated earnings in a given currency meet or exceed Apple's minimum payment threshold for that currency. If your earnings fall below the threshold, they roll forward to the next fiscal month and continue accumulating until the threshold is crossed.

This matters most for apps with revenue spread thinly across many territories. An app with users in Australia, Canada, New Zealand, Singapore, and the UK accumulates earnings in AUD, CAD, NZD, SGD, and GBP as separate pools. If each pool sits below its respective threshold, you may see no payment for several months even while aggregate revenue in App Store Connect looks healthy.

For the major currencies—USD, EUR, GBP, JPY, and AUD—the thresholds are modest and typically cleared by any app with even a few dozen paying subscribers. For smaller market currencies, however, minimum thresholds can leave earnings sitting dormant for extended periods. Apple lists the current thresholds in the Agreements, Tax, and Banking section of App Store Connect.

Currency conversion is a second variable. Apple pays you in the local currency of each territory, not in your home currency. Your bank converts the inbound wire at the prevailing rate on the day of receipt—a rate you have no control over. For currencies subject to significant short-term volatility, this can mean a meaningful gap between the proceeds figure shown in App Store Connect and the amount that actually clears your account. Industry practice is to apply a 2–3% conservative buffer to exchange rate assumptions when planning. If you're actively managing per-territory prices to reduce this exposure, see our guide on pricing across territories.

Tax setup, holds, and why your first payment takes longer

Before Apple issues any payment, you must complete several prerequisites in App Store Connect under Agreements, Tax, and Banking. Skipping or incompletely filling any of these blocks payment entirely:

1. Paid Applications Agreement: You must have a current, executed Paid Applications Agreement with Apple. Apple periodically updates its terms, and if the agreement lapses or a new version requires your acceptance, payments pause until you re-sign. App Store Connect displays a banner when action is required, but it is easy to miss during busy release periods.
2. Banking information: Your bank account details must be entered and verified. Apple requires the account to be held by the same legal entity as your developer account. Mismatches cause payment holds that can take weeks to resolve through Apple's support channels.
3. Tax forms: Non-U.S. developers must typically complete U.S. tax forms such as the W-8BEN (for individuals) or W-8BEN-E (for entities). Incomplete tax information results in backup withholding on U.S.-sourced income—Apple withholds a percentage of applicable earnings and remits it to the U.S. IRS. You may be able to reclaim withheld amounts through your home country's tax authority under an applicable tax treaty, but this is a time-consuming process. Complete your tax forms before your first release.

For brand-new accounts, even after completing all paperwork correctly, developer community accounts suggest Apple applies an additional hold period before releasing the first payment. This initial hold can add 30–45 days on top of the normal cycle, meaning your first payment from a new account may not arrive for three to four months after your first qualifying sale. Plan your launch-quarter budget with this in mind—do not count on App Store proceeds to cover expenses in the same quarter as your launch.

Reading Financial Reports to build a 90-day cash flow forecast

App Store Connect's Financial Reports are the most reliable source of truth for upcoming cash flow. Unlike the Sales and Trends section—which shows unit counts and proceeds estimates that can be revised by refunds and other adjustments—Financial Reports reflect the amounts Apple has committed to pay, broken down by currency and fiscal period.

Here is a practical approach for building a rolling 90-day forecast:

1. Download the two most recent Financial Reports from App Store Connect. Each report corresponds to a closed fiscal month and contains line items showing proceeds by currency, the applicable territory group, and the payment date Apple has committed to.
2. Identify committed vs. pending amounts. Line items where the payment date is in the past are cleared—verify against your bank statement. Line items where the payment date is in the future are committed receivables you can treat as near-certain cash.
3. Use Sales and Trends for the weeks 31–90 of your forecast window. Sales and Trends shows real-time subscription data that isn't yet closed into a Financial Report. Apply your historical refund rate and conversion rates to convert these figures into estimated proceeds. Treat these as directional, not committed.
4. Apply conservative FX rates. For each non-home-currency pool, apply a rate 2–3% below the current spot rate to buffer for movement between report date and receipt date.
5. Layer in known deductions. If you have outstanding refunds or adjustments flagged in App Store Connect, these reduce the next payment. Account for them explicitly rather than discovering a smaller payment than expected.

This approach gives you a reasonably accurate 90-day view without requiring third-party tools. RevenueCat's platform provides a complementary layer—it surfaces MRR, churn, and LTV metrics alongside payment data in a single dashboard, which simplifies forecasting for subscription-heavy apps. See our post on iOS subscription analytics: MRR, churn rate, and LTV for an explanation of how those metrics connect to the Financial Report figures.

Common payout mistakes and how to avoid them

These errors appear consistently in developer communities when App Store payments are discussed:

For context on how Apple calculates the net proceeds figure that flows into these reports—factoring in its commission, local VAT collection, and territory-specific adjustments—see our breakdown of how Apple calculates your App Store net proceeds.

Sources and further reading

• Apple Developer: View Financial Reports – App Store Connect Help
• Apple Developer: Set up your banking information – App Store Connect Help
• Apple Developer: Complete tax forms – App Store Connect Help
• RevenueCat Blog: iOS subscription monetization and revenue analysis
• AppFollow Blog: App Store analytics and subscription insights