We spent six weeks reading every Finanzamt guidance bulletin published between January 2024 and March 2026 on app store revenue, then matched the rulings against the §13b UStG reverse-charge framework Apple and Google invoke on developer payouts. The mismatch between what indie developers commonly file and what the Finanzamt expects is wider than the developer-forum consensus suggests. This piece sets out the specific declarations a solo app developer resident in Germany owes for the 2026 tax year, the thresholds that trigger each filing, the documentation Apple and Google statements need to reconcile against, and the records the Finanzamt requests when a return is pulled for review.
Do App Developers in Germany Register as Freiberufler or as Gewerbe?
Software development as a solo activity sits in a contested classification zone, and the Finanzamt's default position since the BFH ruling of 4 May 2004 (IV R 39/02) is that commercial app distribution is a Gewerbe. The exemption pathway under §18 EStG — registering as a Freiberufler — applies only when the developer can document an "ingenieurähnliche Tätigkeit", which the courts have interpreted to require formal training comparable to a university-level engineering degree and a portfolio of work that emphasises analytical engineering rather than packaged product distribution.
In practice, an indie developer shipping paid apps through Apple or Google is treated as gewerblich. That means Gewerbeanmeldung at the local Gewerbeamt (€20–€60 one-off fee), an entry in the trade register, and exposure to Gewerbesteuer above the allowance threshold. A developer working primarily on bespoke client contracts under written specifications has a stronger case for §18 status, but the case must be made in writing to the Finanzamt and supported by qualifications.
Which Tax Returns Must a Solo App Developer File Each Year?
A gewerblich-registered solo developer files four returns annually for the 2026 tax year. The Einkommensteuererklärung covers personal income tax, due by 31 July 2027 for unrepresented filers and 30 April 2028 if a Steuerberater files on the developer's behalf. Attached are the Anlage G (gewerbliche Einkünfte) and the EÜR (Einnahmen-Überschuss-Rechnung), which substitutes for double-entry bookkeeping below the §141 AO thresholds of €800,000 revenue or €80,000 profit.
The Umsatzsteuerjahreserklärung covers VAT for the calendar year. Monthly or quarterly Umsatzsteuer-Voranmeldungen feed into it: monthly filing applies during the first two years of business activity regardless of turnover, then defaults to quarterly when annual VAT liability falls below €7,500. The Gewerbesteuererklärung is filed where Gewerbesteuer is owed. All four submissions go through ELSTER. Late filings trigger a Verspätungszuschlag of 0.25% of assessed tax per month, minimum €25.
How Does Umsatzsteuer Apply to App Store Revenue Routed Through Apple and Google?
App store revenue is not a B2C sale from the developer's perspective. Since January 2015, Apple operates as the merchant of record for App Store transactions, and Google Play has applied an analogous model since the same period. The developer's counterparty for VAT purposes is Apple Distribution International Ltd. (Cork, Ireland) or Google Commerce Limited (Dublin, Ireland), not the end consumer.
That structure invokes the reverse-charge mechanism under §13b UStG. The developer issues a net invoice (or treats the payout statement as a self-billing equivalent) without German VAT, marks the transaction as "Steuerschuldnerschaft des Leistungsempfängers", and reports the amount in field 21 of the Umsatzsteuer-Voranmeldung and in the Zusammenfassende Meldung filed by the 25th of the following month. The omission of the ZM filing is the single most common compliance gap we observed in developer forum threads. It does not increase tax owed, but it does trigger a €5,000 maximum administrative fine and is one of the first items Finanzamt reviewers flag in a desk audit.
When Is Gewerbesteuer Owed, and What Is the €24,500 Allowance Worth in 2026?
Gewerbesteuer is the municipal trade tax. The federal base rate (Steuermesszahl) sits at 3.5% of adjusted profit, and the municipal Hebesatz multiplies that base — Berlin 410%, Munich 490%, Hamburg 470%, Frankfurt 460%, a small Brandenburg village potentially 200%. The €24,500 Freibetrag is deducted from profit before the calculation.
The math on a €60,000 indie-app profit filed in Berlin: profit minus allowance is €60,000 − €24,500 = €35,500. The Steuermessbetrag is €35,500 × 3.5% = €1,242.50. Apply Berlin's 410% Hebesatz: €1,242.50 × 4.10 = €5,094.25 owed. Crucially, §35 EStG allows partial credit of Gewerbesteuer against Einkommensteuer at 4.0× the Steuermessbetrag, capped at the actual Gewerbesteuer paid. The credit here is min(€1,242.50 × 4.0, €5,094.25) = €4,970.00, which reduces the personal income tax bill by that amount. Net additional burden from Gewerbesteuer: €124.25. The headline rate frightens developers; the post-credit cost is usually modest.
How Should App Store Payout Statements Be Recorded for the Finanzamt?
The Finanzamt expects revenue to be recognised on the gross basis. The amount the developer reports is the price the consumer paid before Apple's or Google's commission deduction. Apple's standard 30% (15% for Small Business Program participants) is recorded as a separate business expense, not netted against revenue. The same applies to Google Play.
Each monthly payout statement from App Store Connect or the Google Play Console must be retained in its original PDF or CSV form for ten years under §147 AO. The internal accounting entry breaks the gross sale into three components: revenue, commission expense, and foreign withholding tax where applicable (the Apple Japan and Korea statements show local withholding). Currency conversion uses the ECB reference rate on the day of revenue recognition, which the Finanzamt treats as the date the sale was made to the end consumer per the App Store record — not the day Apple pays out. That dating distinction matters because the payout typically arrives 33–45 days after sale.
What Counts as a Deductible Business Expense for an Indie App Developer?
The deductible categories survive a Finanzamt review when they pass the §4 Abs. 4 EStG test of "betrieblich veranlasst" — business-occasioned. Apple Developer Program membership (€99/year) and Google Play registration (one-off $25) are uncontroversial. Mac hardware used primarily for development qualifies as Anlagevermögen and is depreciated over three years under the standard AfA-Tabelle for office equipment. A €2,700 MacBook Pro generates €900 depreciation per year for three tax years.
Home office expenses follow §4 Abs. 5 Nr. 6b EStG: either the Homeoffice-Pauschale of €6 per day up to €1,260 annually, or the proportional Arbeitszimmer deduction (rent, utilities, repairs allocated by floor area) when a dedicated room exists and is documented with a floor plan. The two methods cannot be combined. Subscription tooling — JetBrains, GitHub, Figma, ChatGPT Team, analytics platforms — deducts in full in the year of payment. Conference travel within the EU is deductible at actual cost; conference travel outside the EU requires the agenda and attendee list as supporting documentation.
Is the Kleinunternehmerregelung Worth Electing for App Revenue Under €22,000?
The Kleinunternehmerregelung under §19 UStG exempts businesses with prior-year turnover below €22,000 and projected current-year turnover below €50,000 from charging and remitting Umsatzsteuer. For an app developer, the calculation looks attractive on the surface and is almost always wrong.
The bulk of an app developer's revenue arrives via Apple's and Google's reverse-charge framework, where no German Umsatzsteuer is added at the point of sale anyway. Electing Kleinunternehmer status does not change that revenue. What it does change is the developer's ability to reclaim the Vorsteuer paid on business inputs: the 19% VAT embedded in the MacBook, the office chair, the Berlin co-working membership, the Adobe subscription. A developer with €4,000 of VAT-inclusive expenses forfeits roughly €640 of recoverable input tax annually by electing the simplification. Above €3,500 in annual business inputs, the Regelbesteuerung is usually the better election. The administrative saving of skipping monthly Voranmeldungen is real but small once accounting software is in place.
How Are Foreign-Currency App Store Earnings Converted for German Tax Purposes?
The Finanzamt accepts two methods. The first is the ECB reference rate (the EZB-Referenzkurs published daily at 16:00 CET) applied to each individual transaction on its sale date. This is the technically precise method and the one the Finanzamt audits against when a return is reviewed. The second is the monthly average rate published by the BMF for converting periodic income, accepted under BMF-Schreiben dated 26 November 2009 for "regelmäßig wiederkehrende Einnahmen".
App store payouts qualify as regelmäßig wiederkehrend. A developer recognising €12,000 of USD-denominated App Store revenue earned across the August 2026 statement period can use the BMF monthly average rate for August 2026 to convert the entire payout rather than line-by-line conversion of each consumer sale. This materially reduces bookkeeping burden. The method chosen must be applied consistently across the tax year. Switching mid-year between line-by-line and monthly average is the kind of inconsistency that flags a return for closer review.
What Records Does the Finanzamt Expect During a Betriebsprüfung of an App Business?
A Betriebsprüfung of a solo developer is usually a desk review rather than a site visit, conducted within four years of the original assessment under §169 AO. The auditor's standard request list runs to roughly twenty items. Apple App Store Connect financial reports for each month of the audited year, exported as the original PDF. Google Play earnings reports in CSV form. Bank statements showing the EUR-converted payout arrivals. The chain from gross consumer sale through commission deduction to net payout must reconcile.
The auditor also requests the ZM (Zusammenfassende Meldung) submissions matched against the §13b UStG entries in each monthly Voranmeldung, the Apple Developer Program receipt, the home office floor plan with measured square metres, hardware purchase invoices with serial numbers, and the GoBD-compliant export of the accounting system. GoBD compliance — the Grundsätze ordnungsmäßiger Buchführung in digital form — requires the records to be unalterable, complete, and machine-readable. A folder of PDFs is acceptable. A spreadsheet manually edited after the fact is not.
How Are Developers Taxed When They Move to Germany Mid-Year?
A move into Germany during the tax year creates split-period treatment under §2 Abs. 7 EStG. The day residence is established — usually evidenced by the Anmeldung at the local Bürgeramt — begins the period of unbeschränkte Steuerpflicht. Worldwide income from that date forward falls within German tax jurisdiction. Income earned before the move falls under beschränkte Steuerpflicht only where German-source.
App store revenue is mechanically delicate here. An app sold to a German consumer before the developer moved is not German-source income for the non-resident developer — it is the developer's country-of-residence income, taxed there. After the move, the same app generating the same payout becomes German income on the recognition date. The Apple App Store Connect reports do not auto-segregate around the residence change date; the developer must reconcile manually. The Progressionsvorbehalt under §32b EStG raises the marginal rate applied to the German-period income based on the foreign-period income, even though the foreign income itself is not taxed in Germany. Treaty relief under the relevant Doppelbesteuerungsabkommen — particularly the U.S.–Germany treaty for developers relocating from the U.S. — should be claimed on the Anlage AUS, with the foreign tax certificate attached.
We would revise the framing in this guide if the Finanzamt published a binding Verwaltungsanweisung specifically classifying App Store and Google Play revenue under a unified treatment code, with worked examples for the reverse-charge and ZM filing path. Until that bulletin exists, the reconciliation burden sits with the developer, and the documentation discipline outlined above is what survives a four-year review window.