App Store tax handling: how Apple collects VAT, GST, and withholding tax across territories

A practical guide to how Apple manages VAT, GST, and withholding taxes across App Store territories as merchant of record, and what that means for your net proceeds in each market.

Apple as your tax agent: the merchant of record model

When a customer buys your app or subscription in the App Store, the purchase contract is between that customer and Apple — not between the customer and you. This structure, where Apple acts as the "merchant of record," has significant implications for how taxes work across territories.

Because Apple is the seller of record in almost every App Store territory, Apple is responsible for calculating, collecting, and remitting local consumption taxes — VAT in Europe, GST in Australia and Singapore, Consumption Tax (JCT) in Japan, and equivalent levies across dozens of other markets. You never receive that tax money, and you never need to remit it. It flows directly from the customer to Apple to the relevant government.

The practical consequence: the price customers see in the App Store already includes local tax where applicable. When you set a price tier equivalent to $4.99 USD, Apple's pricing engine converts that to local prices that typically include local tax baked in. The "proceeds" you receive are calculated from the customer price after subtracting tax.

VAT and GST: which territories charge what

Consumption taxes on digital services vary widely. Most developed markets now apply some form of digital services tax, but rates differ significantly. The table below covers the major App Store markets; it reflects the general framework as of mid-2026, but rates are subject to change and you should verify against Apple's current tax schedule before drawing conclusions.

The United States is a partial exception: sales tax on digital goods is a state-level matter, and not all states tax digital services. Apple collects and remits US sales tax where required by law, but the mechanics differ from the unified VAT model in the EU or Australia. The net effect on your proceeds in a given US state depends on whether Apple has assessed that state as requiring collection.

India deserves special attention because of that 18% rate combined with a large and growing install base. For a subscription priced at the equivalent of $9.99, a developer in the App Store Small Business Program (15% commission) would net approximately $9.99 × (1 − 0.18) × (1 − 0.15) ≈ $6.99 before any currency conversion losses. That's a meaningful gap from the nominal price. Our guide on how Apple calculates your net proceeds walks through this math in full.

Withholding tax: the layer most developers miss

Beyond consumption taxes on purchases, some countries impose withholding taxes on payments made to foreign entities. This is a distinct mechanism: rather than taxing the end customer, the local government requires that a portion of funds flowing out of the country be withheld and remitted to local tax authorities before the remainder reaches the payee.

Withholding tax affects your proceeds differently from VAT/GST. Apple typically absorbs or deducts withholding taxes depending on the territory and your tax documentation status. The deduction shows up in your financial reports as a reduced proceeds figure for affected territories — which can be confusing if you're not expecting it.

Countries where withholding taxes have historically affected App Store payouts include South Korea, India, and several Southeast Asian markets. The applicable rate depends on two things: whether a tax treaty exists between the territory in question and your country of incorporation or residence, and whether you have submitted the relevant treaty documentation to Apple through App Store Connect.

Apple's tax documentation workflow in App Store Connect prompts you to provide the forms relevant to your situation — typically a W-8BEN-E for non-US entities or a W-9 for US entities, plus any country-specific treaty documentation. Failing to submit these documents typically results in Apple applying the maximum withholding rate as a default, which is almost always higher than the treaty rate you'd qualify for.

How taxes surface in your App Store financial reports

Once you understand the mechanics, interpreting your financial reports becomes considerably less opaque. Apple provides two primary report types that expose tax-related data.

Sales Reports provide transaction-level data. The "Customer Price" column reflects what the customer paid, including any local consumption tax. The "Developer Proceeds" column is what you actually receive after Apple's commission and applicable taxes. For a German sale at €9.99, that proceeds figure has already had 19% VAT and Apple's commission removed.

Financial Reports aggregate this data into the actual bank transfer you receive. These are the numbers you'd reconcile against your bank statement. Proceeds are shown in the currency of transfer, which may involve additional conversion from the territory's local currency depending on your banking setup.

The most common developer confusion here: the proceeds figure in a Financial Report for a high-tax territory like India can look materially lower than straightforward commission math would suggest. The gap is almost always the combination of consumption tax plus withholding tax. Our guide to reading App Store Connect financial reports has a full breakdown of each column and what to look for.

For currency-volatile markets like Brazil and Turkey, tax complexity stacks on top of exchange rate uncertainty. A quarterly proceeds figure from Brazil can move substantially quarter-over-quarter for reasons entirely unrelated to your download volume — currency shifts and tax rate changes both play a role. Our piece on App Store pricing in currency-volatile markets covers the Brazil and Turkey situations in more depth.

Pricing strategy when tax rates are high

High consumption-tax markets require a deliberate approach to price-setting. Two strategies exist.

Tier-based pricing (the default): Apple's pricing grid sets your consumer price — tax included — at a round local number based on your chosen tier. If you select a tier equivalent to $9.99, Apple picks the nearest sensible local price in Indian rupees, euros, or yen and includes tax in that figure. This is the zero-effort path, and it works well for developers without the data to do better.

Manual override pricing: Apple allows you to set territory-specific prices manually rather than using the auto-converted equivalent of your base price. For high-tax markets, this matters: if your base price converts to a net proceed that compresses your margin uncomfortably after 18% GST is deducted, setting a higher manual price in that territory can recover margin — at the cost of potentially reducing conversion in a price-sensitive market. This is a deliberate trade-off, not a free lunch.

For subscription apps, the tax math compounds across the subscriber lifetime. A subscriber in France who renews annually at a price that embeds 20% VAT generates a different effective LTV than an equivalent subscriber in a low-tax US state. LTV models that treat "proceeds per subscriber" as territory-agnostic will systematically overestimate the value of subscribers in high-VAT markets. Use the AppsOps pricing tool to model net proceeds per territory before setting your price architecture.

Your actual responsibilities: a practical checklist

Given how much Apple handles, it's worth being precise about what remains your responsibility.

Apple handles:

• Calculating local VAT, GST, JCT, and equivalent taxes on each transaction
• Collecting tax from the customer as part of the App Store checkout
• Remitting collected taxes to the appropriate government authority in each territory
• Managing its own tax registrations in the territories where it operates the App Store

You are responsible for:

• Submitting accurate and current tax documentation to Apple (W-8BEN-E, W-9, and any treaty forms)
• Declaring App Store proceeds as income in your own jurisdiction
• Understanding whether your country taxes foreign-sourced income from platform sales
• Keeping your banking and tax profile in App Store Connect current — especially if your corporate structure or address has changed
• Monitoring for territory-specific tax changes that affect your effective proceed rates

The single most common developer error is conflating the taxes Apple collects on behalf of customers with the developer's own income or corporate tax obligations. Apple remitting GST to the Australian Tax Office does not discharge your own tax liabilities in your country. These are separate regimes. If you're operating through a company structure, permanent establishment rules in markets where you have employees or contractors introduce additional complexity that requires professional tax advice.

A suggested annual audit process: pull a Financial Report for a trailing 12-month period, calculate your effective proceeds rate (total proceeds ÷ total customer price) per territory, and flag any territory where the rate has shifted unexpectedly. Changes usually trace to one of three causes: a tax rate change, a missing or lapsed withholding treaty form, or a currency conversion issue. The AppsOps territories dashboard surfaces territory-level proceed rates in a single view, which makes this audit considerably faster than doing it from raw CSV exports.

Sources and further reading

• Apple Developer — Agreements, Tax, and Banking Overview (App Store Connect Help)
• Apple Developer Documentation — Sales and Finance Reports API
• Apple Developer — In-App Purchase and Subscriptions overview
• OECD — BEPS: Addressing the Tax Challenges of the Digital Economy
• RevenueCat Blog — iOS subscription operations and revenue benchmarks
• Apple Developer News — official updates on App Store policy and tax changes