App Store Revenue vs. Cash in Your Bank Account: Why There's Always a Gap
You open App Store Connect. Revenue is up — subscriptions are renewing, users are converting, everything looks healthy. Then you open your bank account and the number is considerably less exciting.
This isn't a bug in your accounting. It's the structural reality of how Apple pays developers, and it quietly shapes the growth trajectory of almost every indie app business on the platform.
Understanding the gap isn't just useful for planning — it reframes how you think about what your app is actually worth, and how fast you can afford to grow it.
Two Very Different Numbers
When you look at your app's financial picture, there are at least four different figures at play at any given time:
1. Gross revenue — The total value of all purchases and subscriptions in a given period, before Apple's commission.
2. Net proceeds — What's left after Apple's 15% or 30% commission. This is the number you actually have a claim to.
3. Reported proceeds in App Store Connect — Your net proceeds as shown in the dashboard. This number is real and accurate — but it's a receivable, not cash.
4. Cash in your bank account — The actual funds that have cleared and are available to deploy.
At any given moment, figures 3 and 4 can differ significantly. That difference is your float — money you've earned, that Apple owes you, that you simply cannot access yet.
The Float Is Bigger Than You Think
Most developers understand that Apple has a payout delay. Fewer have calculated what that delay actually means in dollar terms.
Here's the math:
If your app earns $20,000 per month consistently, Apple's 32–45 day payout cycle means you are always carrying approximately $22,000–$30,000 in earned-but-unpaid proceeds at any given moment.
That float grows linearly with your revenue:
| Monthly Revenue | Float at 32 Days | Float at 45 Days |
|---|---|---|
| $10,000 | ~$10,700 | ~$15,000 |
| $25,000 | ~$26,700 | ~$37,500 |
| $50,000 | ~$53,300 | ~$75,000 |
| $100,000 | ~$106,700 | ~$150,000 |
This is capital you've earned. It's sitting with Apple, earning Apple nothing and costing you everything you could have done with it.
Why the Gap Is Structurally Unavoidable
The App Store revenue-to-cash gap has three distinct causes, and none of them are going away:
1. Apple's Fiscal Month Cycle
Apple reconciles payments on its own fiscal calendar, not the standard calendar. The fiscal month closes, processing begins, and funds are transferred — all on Apple's timeline, not yours. There is no setting you can change, no account tier you can unlock, no relationship you can leverage to accelerate this process.
2. Refund and Dispute Processing
Apple allows users to request refunds for app purchases and subscriptions. These refunds can be processed after the fiscal month has closed, which means Apple cannot finalize your proceeds until the refund window has substantially elapsed. The delay is, in part, Apple managing its own refund liability.
3. Tax Withholding and Currency Conversion
For developers outside the U.S., or those earning revenue across multiple storefronts, Apple applies tax withholding and currency conversion before disbursing funds. This adds additional processing time and introduces a variable — exchange rates — that can cause the amount that lands in your bank to differ from what you saw in App Store Connect.
The Real-World Impact on Indie Developers
The float isn't just a number on a spreadsheet. It has real operational consequences that compound over time.
User Acquisition Timing
Paid acquisition campaigns — Apple Search Ads, Meta, Google — require capital upfront. If your strongest acquisition window is October (heading into the holiday season), you need that budget available in October. Revenue earned in August that's still sitting in Apple's payout queue can't fund your October campaigns.
Hiring and Contractor Decisions
Freelancers and contractors want to be paid monthly or upon project completion. If you're relying on Apple proceeds to fund development work, the float creates a timing mismatch that slows down every hiring decision.
Reinvestment Cycles
Healthy app businesses operate on reinvestment cycles: revenue comes in, a portion goes toward growth, the app grows, more revenue comes in. The float extends each cycle by 32–45 days. Over a year, that's potentially 3–4 lost reinvestment cycles — growth that simply didn't happen because capital wasn't available when the opportunity was.
Emergency Resilience
If something unexpected hits your business — a platform change, a competitor move, a bug that needs urgent engineering — having $50,000 of your own money tied up in Apple's queue can leave you without options at the worst possible moment.
This Is Different From Being Unprofitable
It's worth being explicit about this: the gap between your App Store revenue and your bank balance is not a sign that your business is unhealthy. It's not a cash flow problem in the traditional sense — you're not spending more than you earn.
It's a liquidity problem. Your business is profitable. Your proceeds are real. They're just not accessible on the timeline your business needs.
This distinction matters because the solutions are different. Unprofitable businesses need to cut costs or find equity. Profitable businesses with liquidity constraints need access to their own capital — faster.
How Savvy Developers Work Around the Float
There are a few common approaches, each with real trade-offs:
Maintaining large cash reserves. Keeping 60–90 days of operating expenses in a separate account ensures you're never caught short. The downside: that's capital that isn't working — it's not funding growth, not earning meaningful yield, just sitting as a buffer.
Business lines of credit. A revolving credit line can bridge the gap in a pinch. But unsecured business credit is hard to get for app companies (banks rarely understand recurring digital revenue), interest costs add up, and limits tend to be modest relative to the float for high-revenue apps.
Slowing down growth. The most common approach. Simply not running campaigns you can't fund, not making hires until the proceeds clear, not moving as fast as you could. This is a real cost — it just doesn't show up as a line item.
Early proceeds access. A newer category of solution built specifically for this problem: receiving your App Store proceeds before Apple's payout cycle completes, in exchange for a small fee.
The Key Insight
Your App Store dashboard and your bank account are both telling the truth — they're just measuring different things. Revenue is what your app has earned. Cash is what you can deploy. The gap between them is real, measurable, and worth actively managing.
AppCap helps App Store developers access their proceeds before Apple's payout cycle completes.