App refunds come out of your payout, not just your dashboard revenue, and a bad month can pull money from your bank

Most developers read a refund as a line that went the wrong way, a sale that turned into a smaller number somewhere in a report. It is worse than that. App refunds come out of your payout, the actual money the store wires to your bank, and because a refund almost never lands in the same period as the sale, it comes out of a payout you may have already spent. On Google Play, a bad enough run of refunds does not even wait for the next payout. Google reaches into the bank account that receives your money and takes the shortfall back.

This is the part of refunds that never shows up in the churn charts. The money moves on the store's schedule, not yours, and the store's schedule is built to net your refunds out before it pays you. Here is exactly when refund money leaves, on the App Store and Google Play, and why the number that hits your bank never matches the number on your live dashboard.

Why an app refund comes out of your payout, not your sales

A refund is two reversals at once, and both of them are your money. Understanding that is the difference between treating a refund as an accounting footnote and treating it as cash leaving the building.

A refund reverses the customer's charge and your proceeds

When a customer is refunded, the store returns the full price they paid. It then reverses its own commission, so you are not paying the store's cut on a sale that no longer exists. What is left, the proceeds you actually earned on that sale, is clawed back from you. That is the number that matters for cash flow. It is not the commission and it is not the tax, both of which the store handles. It is the share you were going to keep, and on a refund it goes back out.

The money can leave after you have already been paid

The catch is timing. Stores pay on a monthly cycle, and a customer can request a refund days or weeks after they bought. If the refund arrives before the sale has been paid out, it simply lowers that payout. If it arrives after you have already been paid for the sale, the store takes it out of a later payout instead. Either way the refund is settled against whatever period it happens in, not the period of the sale, so refund money and sale money almost never move together.

When refund money actually leaves, store by store

The two stores land in the same place, your refunds are netted out of your payouts, but they get there on different calendars and with different consequences when the math goes negative.

Google Play nets refunds into a monthly payout

Google Play settles on a calendar month. Any order processed, refunded, or charged back from the first of a month to the end of that month is paid out around the 15th of the following month, once your balance clears the payout threshold, which is one US dollar for local-currency payouts and one hundred US dollars for USD wire transfers. Refunds are inside that settlement, not outside it. If you refund an order before Google has paid you for it, you never receive that amount. If you refund it after the payout already went out, Google deducts the amount from a future payout.

Apple books the refund against the fiscal month it happens

Apple runs on a fiscal calendar, not a calendar month, and it removes refunds and chargebacks from your accrued revenue in the fiscal month they occur. In the financial report a refund is marked as a Return, with negative units and a negative partner share, which is Apple's way of saying it directly reduces the proceeds for that period. Apple then pays you roughly a month after the fiscal month closes, and only once your balance clears the payment threshold for your region, so a refund can reduce money you have not been paid yet or offset a month where you were already paid for the original sale.

What it costs you in cash flow

The dollar amount of a refund is easy to see. The cash-flow cost is the part that catches teams out, because it is about when the money moves, not just how much.

The lag is the trap

Picture a normal month. You sell in January and get paid for it later. In February, some of those January buyers refund, and February is also when you make new sales. Google and Apple both net the old refunds against the new period, so your February deposit is lighter than your February sales alone would suggest. Nothing is wrong. The refunds just landed on a different payout than the sales they reverse.

On a consumable purchase the lag stings twice. You already spent real money delivering the coins, the credits, or the generated output when the customer bought, so the compute and API cost is gone. Then, weeks later, the proceeds you booked get pulled back out of a payout. You are out the fulfillment cost and the revenue, and they leave on two different days.

Chargebacks are the expensive version

A chargeback is a refund that went to the bank instead of the store, and it is final. You can respond to a Google Play chargeback review through orders.reviewrefund within 24 hours and Apple can request consumption information within 12 hours, but neither one turns a lost dispute back into cash. From August 3, 2026, a Google Play chargeback moves the purchase price, less Play's service fee, plus the bank's chargeback fee, onto the developer, and Google keeps covering only its own service fee. That combined amount comes out of your payout the same way a refund does, except a chargeback also carries a bank fee you never see on an ordinary refund.

Why your payout never matches your dashboard

If your revenue dashboard and your bank deposit have never agreed, refunds are most of the reason. The dashboard is counting one thing and the payout is counting another.

The dashboard is gross, the payout is net and late

A live sales dashboard shows gross sales as they happen. The payout shows those sales minus every refund and chargeback that settled during the payout period, including refunds against sales from earlier months. The two numbers describe different windows of time, so they cannot match. The payout is the smaller, later, and more honest figure, because it has already absorbed the reversals the dashboard has not caught up to yet.

How to stop refunds from surprising your cash flow

You cannot change when a customer asks for a refund, and on most refund paths you cannot stop the refund at all. What you can control is whether the timing catches you off guard and whether you are carrying enough slack to absorb it.

Reconcile to the payout, not the dashboard

Treat the store's financial report and payout as the source of truth for revenue, and reconcile your own numbers to it every period. On the App Store that means the financial report, where a refund is a Return with negative units. On Google Play it means the earnings report that feeds the monthly payout. Match to those and the refund lag stops being a mystery, because you are reading the same nets the store is paying on.

Hold a reserve against refund lag

Because a refund can hit a payout weeks after you booked the sale, do not treat a full month of gross sales as spendable the day it lands. Keep a reserve sized to your refund rate so a heavier refund month, or a cluster of chargebacks, reduces a payout you planned for instead of one you already committed. This matters most for teams that pay ad spend or contractors out of store revenue, where a lighter payout lands on a bill that does not shrink.

Kill the refunds you can, and keep customers out of the chargeback lane

The cheapest refund is the one that never happens, and the second cheapest is the one that stays a refund instead of becoming a chargeback. A customer who gets a clean, fast refund rarely calls the bank, and the bank version now carries a fee on Google Play that the store version does not. Prevent what you can before the request lands, honor the legitimate ones without friction, and you keep both the volume and the fees off your payout.

The short version

A refund is not a smaller sale, it is money leaving your account on the store's schedule. Google Play nets your refunds and chargebacks into a monthly payout around the 15th, and if your balance goes negative for 48 hours it debits your bank directly. Apple books refunds against the fiscal month they happen in and pays about a month later, net of those returns. Because refunds rarely settle in the same period as the sales they reverse, your payout is always lighter and later than your dashboard, and from August 3, 2026, a Google Play chargeback pulls the price and a bank fee out of that payout with no way to recover it. Reconcile to the payout, hold a reserve for the lag, and stop the refunds you can before they ever reach the bank.