Payment processor reserves: separate held funds from cash you can spend
Suppose a £7,500 supplier invoice is due next week and the Stripe Dashboard shows £10,000 of processor funds. The total looks like enough. The balance breakdown then shows £7,000 available and £3,000 held in a reserve, and even the available money has not reached the bank. Before committing processor funds, finance needs to know what is held, on what terms, and when released money will actually arrive in the bank account.
How Stripe describes reserves
Stripe's support documentation describes fixed reserves, rolling reserves, and transfers of an existing available balance into a reserve. A fixed reserve holds the specified share until a common release date; a rolling reserve releases each transaction's held share after its holding period. When either kind releases, the funds move into the available balance for the next payout. Stripe says an account with a reserve receives terms setting out the percentage and period, so the merchant's own notice is the document to work from. The figures on Stripe's help pages are illustrations.
Held funds are not automatically a fee or a loss. How to present them in the accounts depends on the agreement and the reporting policy, which the accountant should settle and apply consistently. Stripe is a named example here, and other processors set their own terms.
Sources and context, checked :
Release, payout and bank arrival are separate events
This hypothetical case assumes no pending funds and no new sales, fees or refunds. A £500 release is confirmed, then the full available balance is paid out.
The release moves money within the £10,000. It is not new revenue and adds nothing to bank cash on its own. Only the last row can pay the supplier, and the time between steps depends on the account's payout schedule and the bank.
| Event | Reserved | Available at Stripe | Paid out, not yet in bank | In bank from these funds |
|---|---|---|---|---|
| Starting position | £3,000 | £7,000 | £0 | £0 |
| £500 reserve release | £2,500 | £7,500 | £0 | £0 |
| Payout sent | £2,500 | £0 | £7,500 | £0 |
| Payout arrives | £2,500 | £0 | £0 | £7,500 |
What can change the expected release
Stripe's reserves FAQ says it reviews an account shortly before a reserve expires and may remove, reduce, increase or extend it, and that in rare cases a reserve may be needed indefinitely. When a transaction is refunded or disputed, the FAQ says the reserve held against it is released and used to cover it, which lowers the amount left to release. Terms arrive by email, reserve status appears in the Dashboard, and an appeal may be possible without any guarantee of success.
Stripe's general refunds documentation says refunds draw on the available balance, excluding pending funds. If that balance is too low, card refunds stay pending and refunds on other payment methods fail. In some regions, Stripe may also debit the linked bank account to recover a negative balance. When forecasting refunds and disputes, trace the actual reserve and available-balance movements so the same refund is not counted twice.
Sources and context, checked :
Forecast from the notice
In the cash forecast, we recommend carrying the reserve as its own line with three scenarios: the release arrives as scheduled, the review extends the reserve and nothing is released, or refunds and disputes use part of it first. Until the release is confirmed and the payout is on its way, plan supplier payments on the delayed scenario.
This week, reconcile the current reserve balance to the reserve notice and the status shown in the Dashboard, record the next review or release date with an owner, and check whether next month's payments still clear if that release slips.