You never owned the app refund tax, so a refund costs you your share, not the total on the receipt

Refund an in-app purchase and the customer's receipt shows the full price plus tax flowing back to them. It is tempting to read that whole number as your loss. It is not. The tax on that sale was never your money. Apple and Google added it, collected it from the buyer, and sent it to a tax authority, and when the purchase is refunded they reverse it the same way. The app refund tax on the receipt round-trips through the store. What actually leaves your account is your share of the sale, a smaller number, plus the cost of whatever you already spent delivering the purchase.

This matters the moment you reconcile. Book the gross refund, tax included, against your revenue and every refund looks bigger than it is, and your dashboard stops matching your payout. Here is who holds the tax on an App Store or Google Play sale, what a refund actually pulls back from you, and the one setup, alternative billing, where the tax stops being the store's problem and becomes yours.

Why the app refund tax was never your money

On a normal in-app purchase, you are not the party that charges tax. The store is. That single fact decides where the tax sits when a refund reverses it.

The store is the merchant of record almost everywhere

Apple and Google act as the merchant of record for in-app purchases across almost every market they operate in. Google Play states it is responsible for determining, charging, and remitting VAT for purchases by customers in the European Union and the United Kingdom, sales tax for purchases in all fifty US states and Washington DC, and VAT or GST in a growing list of other countries. Apple runs a tax calculation service that computes tax on customer transactions in the countries and regions where taxes are administered, and it files and remits on your behalf. In every one of these markets, the tax is collected and paid by the store, not by you.

Your proceeds are net of tax to begin with

Apple's own guidance is explicit. Your proceeds are calculated based on the price of your app or in-app purchase, minus any applicable taxes, and then minus commission. Google does the same. The tax is stripped off the top before your share is ever computed. So the money you booked when the sale closed did not include the tax. It could not have. The tax went to the government through the store, and your revenue was always the after-tax, after-commission figure.

What a refund actually pulls back from you

A refund is a reversal of the sale, and it reverses each piece back to wherever that piece came from. Only one of those pieces was ever yours.

The refund reverses your share, not the receipt total

Google Play reduces your payout by the developer share of a refund, not by the price plus tax the customer sees. Apple removes refunds and chargebacks from your accrued revenue for the fiscal month, again at your share. Picture a customer in a US state with an 8 percent sales tax who buys a 10 dollar item. The store charges 10.80. You never touched the 80 cents of tax. Your revenue on that sale, at a 30 percent commission, was 7 dollars. When the purchase is refunded, the store hands the buyer back 10.80 and pulls 7 dollars from you. The 80 cents of tax is not part of your loss, because it was never part of your gain.

The tax reversal is between the store and the buyer

When the store reverses the tax it collected, that money moves between the store, the tax authority, and the buyer. It does not pass through your ledger in either direction. You did not receive the tax on the sale, and you do not refund the tax on the reversal. Treating the reversed tax as your cost is counting money that was never on your side of the transaction.

The real bill is your proceeds plus what you already spent

The tax is the part of a refund that does not cost you. The parts that do are concrete. You lose your net proceeds, the after-tax, after-commission money the sale earned you. You lose the compute, the API calls, the storage, and any payouts you already spent delivering the purchase, and that spend does not come back with the refund. On Google Play, a chargeback on an order placed after August 3, 2026 adds the bank's chargeback fee on top of all of it. That is the bill. The tax line on the receipt is not on it.

Where the tax becomes your problem, alternative billing

There is one setup where the tax stops being the store's job and becomes yours. It is alternative billing. When a customer pays through a billing system other than the store's own, the merchant-of-record arrangement changes.

Off the store's billing, you can owe the tax

Google Play is direct about this. For purchases made through an alternative billing system, you become responsible for determining and remitting the applicable taxes. In those cases Google passes the entire tax amount it collects on to you and calculates its service fee off the net price of the product. The tax is now sitting in your account, and you are the one who has to send it to the tax authority.

Now a refund does reverse tax you owe

The moment you hold the tax, a refund changes shape. Refund an alternative-billing purchase and you have to return the tax to the customer and reverse the tax you were going to remit, on top of your net proceeds and your delivery cost. This is the mirror image of the store-billed case. On store billing the tax is never your problem, on a refund or otherwise. Off it, the tax is your problem on every sale and every refund. If you run external or alternative billing, reconcile its refunds separately, because the tax math is not the same.

How to reconcile a refund without double-counting the tax

The fix is to stop anchoring on the customer receipt and start anchoring on your proceeds.

Reconcile against net proceeds, not the receipt

Book every refund at your developer share, the same figure the store pulls from your payout, not at the price plus tax the customer got back. That is the only number that matches what actually left your account. If your refund line is built from receipt totals, it will always read high, and it will never tie out to your bank.

Use the store's tax and financial reports

Both stores itemize tax so you do not have to guess. Apple publishes a transaction tax report in Payments and Financial Reports that separates sales tax, use tax, GST, and similar taxes from your proceeds. Google Play breaks out tax in its earnings and payout reports. Read your refunds out of these reports, where the tax is already split from your share, and the reversed tax never lands in your revenue by accident.

The short version

On a normal in-app purchase, Apple and Google are the merchant of record. They add the tax, collect it, and remit it, and your proceeds are computed on the price after tax and after commission. So when a refund reverses that sale, the tax it reverses was never yours. Your loss is your net proceeds plus the compute, API, storage, and payouts you already spent, and on Google Play after August 3, 2026 a chargeback adds the bank fee. The one exception is alternative billing, where the tax is passed to you and a refund makes you reverse it. Reconcile refunds at your share, read them out of the store's tax reports, and the app refund tax stops looking like a loss it never was.