You open your bank statement in February, see a deposit from Apple, and it's nowhere close to the number printed on the 1099-K that just landed in your inbox. Did Apple make a mistake? Did you get shorted? Is the IRS going to think you're hiding income?
None of the above. If you sell apps, subscriptions, or in-app purchases through the App Store or Google Play, the number on your tax form and the number in your checking account are supposed to be different — and if you don't understand why, tax season turns into a guessing game instead of a five-minute reconciliation.
This is one of the most common points of confusion for solo and small-team app developers, and it's entirely solvable with a bit of structure. Here's what actually causes the gap, and how to build a bookkeeping habit that keeps you audit-ready without dreading January.
Why the 1099-K Number Looks Wrong (It Isn't)
Both Apple and Google are required to issue a Form 1099-K to U.S. developers once gross payment volume crosses IRS reporting thresholds ($5,000 in unadjusted gross sales for 2026, phasing toward the statutory $600 threshold in future years). The key word is gross.
Form 1099-K reports the unadjusted gross sales — the full customer-facing price before any of the following are subtracted:
- Apple's or Google's commission (30% standard, or 15% if you qualify for a reduced-fee program — more on that below)
- Refunds and chargebacks issued after the sale
- Currency conversion differences, if customers pay in a currency other than your payout currency
- Taxes the platform collected and remitted on your behalf (VAT, GST, and in many U.S. states, sales tax — both Apple and Google act as "marketplace facilitators" and handle this remittance directly, so it never reaches you, but it is baked into the gross sale figure reported)
- Tax withholding, if you're a foreign developer or missing tax documentation on file
So a $10,000 gross sales figure on your 1099-K might turn into $6,800–$7,000 of actual developer proceeds after commission alone, before refunds or currency effects are even factored in. That's not an error — it's the difference between top-line revenue and what a marketplace calls "developer proceeds."
The Four Numbers Every App Developer Should Track
Instead of trying to reconcile one number to another after the fact, track four distinct figures throughout the year. Each has a different purpose:
- Gross revenue — the 1099-K number. What customers paid, before any deductions. This is what the IRS sees on the form.
- Net payout — what Apple or Google actually deposits into your bank account, after commission, refunds, and currency conversion. This is your real top-line business revenue for bookkeeping purposes.
- After-tax income — net payout minus the ~25–35% you should be setting aside for federal self-employment tax, income tax, and (if applicable) state tax.
- Real take-home — after-tax income minus business expenses (developer program fees, cloud hosting, contractor payments, software subscriptions, ad spend).
Most of the "why don't these numbers match" panic comes from developers comparing figure #1 to figure #4 and assuming something's broken. They're not supposed to match. They're different stages of the same dollar.
Where to Pull the Real Numbers
You don't need to reconcile Apple's or Google's monthly reports line-by-line by hand — but you do need a routine.
Apple (App Store Connect):
- Payments and Financial Reports shows monthly proceeds by territory, already net of Apple's commission.
- Financial reports for a given month typically finish populating by the first Friday of the following fiscal month — don't reconcile too early or you'll be comparing incomplete data.
- Currency conversion happens on the day of payment, not the day of purchase, which means a sale made in December can convert at a different rate than one made in November, even at the same nominal foreign-currency price.
Google Play Console:
- The Order Management and Financial reports pages break out gross sales, Google's service fee, refunds, and chargebacks as separate line items — more granular than Apple's bundled monthly report, but delivered monthly rather than in real time.
- Starting with orders placed after August 3, 2026, Google Play began splitting chargeback costs with developers: you now absorb the purchase price (net of Google's fee) plus the card network's chargeback fee on illegitimate disputes, rather than Google absorbing the full cost. If chargebacks are a meaningful share of your revenue, that's a new cost line to track separately going forward.
The practical habit: at the end of each month, log gross revenue, commission, refunds, and net payout as four separate numbers in your books — not just the deposit amount. When the 1099-K arrives the following January, your gross-revenue total should already match it, because you tracked gross all year instead of trying to back into it later.
Don't Overlook the Reduced-Commission Programs
If you're a smaller developer, you may be paying less commission than you think you are — or you may be leaving money on the table by not enrolling.
- Apple's Small Business Program: 15% commission instead of 30%, available to any developer or company that earned $1 million or less in total proceeds (after Apple's cut) in the prior calendar year. Enrollment is simple and self-service inside App Store Connect — there's no application review.
- Google Play's parallel programs: the Apps Experience Program and Games Level Up Program offer 15% on the first $1 million in annual earnings for qualifying apps and games, and the Play Media Experience Program can bring ebook, music, and video-streaming apps down to as low as 10% if they integrate with Android TV, Wear OS, or Google Cast. Unlike Apple's program, Google's require an application and category fit — they aren't automatic.
If you crossed the $1 million proceeds threshold mid-year, or if your app category changed, revisit your enrollment status annually. A developer paying 30% who qualifies for 15% is silently losing half their platform margin.
A Simple Monthly Reconciliation Routine
You don't need accounting software built for enterprise app publishers to stay on top of this. A repeatable monthly checklist is enough:
- Pull the current month's financial report from App Store Connect and/or Google Play Console.
- Record four line items: gross sales, platform commission, refunds/chargebacks, net payout.
- Match net payout to the actual bank deposit. If Apple's payout has a delay (proceeds can take 30–45+ days to reach your account after the sale, depending on payment terms and currency), note the reporting-period lag so you're not comparing this month's deposit to this month's report.
- Set aside your tax reserve (25–35% of net payout, more if you're in a high-tax state) into a separate account the moment the deposit clears — not at tax time.
- File the expense side too. Apple's $99/year developer fee, Google's one-time $25 registration fee, any contractor or design costs, and software subscriptions used for development are all deductible business expenses that reduce your taxable income — but only if they're recorded, not just remembered.
Doing this monthly turns a once-a-year tax scramble into five minutes of admin, and it means that when your 1099-K arrives, you're checking it against numbers you already have — not reverse-engineering a year of platform reports under deadline pressure.
Keep Your App Revenue Ledger in Plain Text
Spreadsheets work for a while, but they get fragile fast once you're tracking gross revenue, commission, refunds, currency effects, and expenses across two platforms and multiple months — one broken formula and your whole reconciliation is suspect. Beancount.io gives indie developers a plain-text accounting ledger where every App Store or Google Play payout, refund, and expense is a version-controlled entry you can audit line by line — no hidden formulas, no vendor lock-in, and a format that's naturally suited to reconciling gross-vs-net revenue across platforms. Get started for free and see why developers who already think in code prefer accounting that works the same way.
