How much ticket revenue should you keep available for refunds?

Your ticket payout has arrived, the venue wants its next payment, and the money is finally there. How much can you spend? Before you answer, work out what you'd need if buyers started asking for their money back tomorrow.

Keep enough accessible money to fund the refunds and related costs your event could reasonably face before more dependable funding arrives. Calculate routine refunds separately from a partial disruption or full cancellation, then make a funding plan for each. A fixed percentage of sales won't tell you whether those obligations are covered.

That distinction matters. A reserve that comfortably pays for ordinary changes of mind may barely cover the first batch of refunds after a venue closes. You need to know which problem your reserve solves, where the money is, and what happens if the bigger problem arrives.

This guide walks through that decision using an invented paid-event example. You'll calculate the amounts, check whether the cash is genuinely available, and decide what has to change before you make another commitment.

Start with what you might have to repay

The first thing you want to do is establish the refund obligations. Your refund policy helps, but it doesn't answer every cancellation question.

Someone changing their mind is different from your business cancelling the event. A workshop moving rooms is different from a festival moving to another city. The relevant law, what you sold, your terms and the actual change all affect the answer. Get those distinctions checked in the places where you sell tickets.

For example, Australia's ACCC says buyers are entitled to a refund when an organizer chooses to cancel or makes a major change. Its guidance on buying event tickets also explains that other cancellations and changes depend on their circumstances, and related compensation may apply. That's Australian guidance, rather than a rule you can copy into every country's policy.

Write down what buyers could receive in each situation. Include the ticket amount and any fees or extras you may need to return. Check tax treatment with your accountant. The amount arriving in your bank after deductions may be smaller than the amount you owe a buyer.

Our event refund policy guide covers the wording and customer experience. Here, you need the financial consequence of those promises. If your team can't say what a cancelled booking would cost, you can't calculate its reserve yet.

Also separate ticket refunds from other potential claims. A cancellation could leave supplier obligations, sponsor repayments or compensation questions. Those need funding too, even when they don't belong in the ticket refund calculation. Keep them visible in the wider cancellation plan.

Define the period your money has to cover

A reserve needs a time period. You might be trying to cover the refunds expected before the next confirmed funding date, while retaining a separate plan for a major disruption.

Start today and list the dates when money could leave. Include approved refunds waiting to process, likely new requests, and any announced deadline that could bring requests together. Then identify when dependable replacement funding could actually be used.

A sponsor saying payment is coming isn't the same as the money arriving. An upcoming payout may contain less than expected after deductions. And if the event is cancelled, the future ticket sales in your forecast may disappear completely. Use the cancellation version of the forecast when you're checking cancellation funding.

You may need a daily view around an announcement. A positive month-end balance doesn't help if the refunds need funding earlier. Make the time period specific enough to expose that gap, then extend the calculation when uncertainty lasts longer.

Keep the ordinary event forecast connected to this work. Our event cash-flow forecast guide explains how to place receipts and payments on their actual dates. The reserve calculation adds a question to it: after protecting the money needed for refunds, can you still pay the event's bills?

The Australian Government's cash-flow planning guidance recommends keeping records current and reviewing statements regularly. For a paid event, that means updating the plan when sales, refund requests or payment dates change, rather than relying on the version you approved before launch.

Build the refund record before you need it

You don't need a complicated model to keep the calculation honest. You need a booking record that explains what the buyer paid, what's already been returned, and what remains exposed in each scenario. Use the ticketing and payment records you already have, then add the planning assumptions they don't contain.

For a group purchase, start with the order rather than multiplying the headline ticket price by the number of people. There may have been a discount, an extra package or an earlier partial refund. The remaining refundable amount has to follow that actual purchase. Otherwise your reserve can grow because you've counted money the buyer never paid.

Give accepted refunds a clear status. Requested, approved, funded and completed describe different points in the process. An approved request may still require cash. A completed refund should reduce both the remaining buyer amount and the money available. Keep enough detail to reconcile those movements without treating an email confirmation as proof that cash has moved.

Then record the scenario assumptions separately. You might expect ordinary requests on some bookings while a cancelled date affects every booking for that date. Keeping the assumptions separate lets you change one part of the event without rewriting the whole calculation or losing the original transaction detail.

If the event has several sales channels, bring their remaining amounts into the same plan. Check which organization holds each balance and who funds each refund. Avoid adding a ticketing total to a payment total when both describe the same purchases. Match them first, then investigate any difference.

Finish each review with a dated version and a named owner. Someone should be able to explain why the reserve changed since the previous review. More sales, completed refunds and a changed disruption assumption are different reasons, and they suggest different next decisions.

Estimate routine refunds from your own bookings

Start with requests you've already accepted. Use their remaining unpaid amounts, since a refund that has already left the account doesn't need funding again.

Then estimate additional requests during your planning period. Look at comparable events, ticket types and purchase windows. How much was refunded, when did those requests arrive, and why? Separate ordinary buyer requests from exceptional disruption so a previous cancellation doesn't quietly become your normal refund assumption.

Use the amount of money returned, alongside the number of bookings. A group booking can need much more cash than a single admission. If you sell premium tickets, catering packages or multi-day passes, a booking count alone can hide the difference.

A useful starting calculation is expected additional refunded bookings multiplied by their expected refundable amount. Add that to accepted refunds still awaiting payment. For events with very different ticket types, calculate each group separately before adding them together.

This is an estimate of your event, not an industry benchmark. There isn't a defensible universal percentage in the sources used here. Someone else's refund rate may come from a shorter sales window, a different audience or much more restrictive terms.

For your first event, build a range and explain the assumptions. You can test low and higher request volumes without pretending either is historical evidence. Choose a working amount you can justify, review it as actual requests arrive, and keep cancellation funding separate.

Pay attention when you change the offer. A more generous refund window changes how much money buyers can reclaim voluntarily. A new ticket bundle changes the amount per request. Update the forecast at the same time as the policy or package, rather than after support notices an increase.

Work through a routine refund example

Everything in this example is invented and expressed in USD. The figures demonstrate the calculation. They aren't recommended reserve percentages, typical refund rates, customer results or Loopyah payment terms.

Imagine you've collected $50,000 in ticket payments that remain outstanding to buyers. Previously completed refunds have already been removed. For simplicity, assume that total includes every ticket-related amount refundable in the cancellation scenario, with no additional tax or fee repayment beyond it.

For the next planning period, you've accepted $600 of refunds that haven't been paid. Based on your stated assumptions, you allow another $1,200 for ordinary requests. That makes $1,800 of routine refund payments to fund.

You also allow $400 for separate disputed payments and related provider charges, and $300 for additional refund administration and other refund-related cash costs. Those amounts are invented planning allowances. Check your own agreements and staffing arrangements before using either category.

The resulting ordinary funding requirement is $2,500. That's $600 plus $1,200 plus $400 plus $300. The disputed transactions are different bookings from the refunded ones, so the calculation doesn't repay the same purchase twice.

Notice what this tells you. You have a reason for each amount and a period it has to cover. You can replace an assumption when better information arrives. If you simply chose a percentage of ticket sales, you wouldn't know which part to change when a large group asked for a refund.

It also tells you what the figure leaves out. The $2,500 doesn't fund a cancelled event or the remaining production budget. Calling it your refund reserve should never make those other obligations disappear from the accounts.

Test a partial disruption and a full cancellation

Next, change the event conditions. Consider a plausible disruption that affects only some bookings. Perhaps one session can't run, one date needs moving, or a premium inclusion can't be delivered. Establish the actual rights and agreed response before assigning a refund amount.

In our invented example, the partial disruption creates $9,000 of total ticket refunds during the period. That includes the routine refunds already counted; it replaces the $1,800 figure. Add $700 for separate disputes and related charges, plus $300 of additional administration. The partial-disruption requirement is $10,000.

For the full cancellation, assume all $50,000 of the remaining buyer payments must be returned. Allow a further $1,000 for the example's remaining refund-related cash costs. The cancellation funding requirement is $51,000. Separate disputed ticket amounts aren't added again because all those buyer payments are already included in the full refund total.

The chart compares these alternative scenarios. Don't add the bars together. Source: Loopyah's invented worked example in this article, calculated from the assumptions above. The figures illustrate refund-related funding only and exclude supplier cancellation bills and other business obligations.

The difference is substantial because cancellation affects the whole outstanding buyer balance. Routine requests involve only some bookings. Taking the ordinary estimate and adding a small cushion doesn't establish that cancellation is funded.

You don't necessarily need every scenario's amount sitting unused in one bank account. You do need dependable, timely funding for the obligations your business may face. If your cancellation plan relies on borrowing or recovering supplier deposits, check the availability, timing and conditions before describing those amounts as covered.

Choose disruption scenarios from your actual event. An outdoor festival, a conference dependent on one speaker and a series of small classes won't fail in the same way. Work through the credible conditions with the people responsible for delivery, then calculate the money consequence.

Check where the refund money actually sits

Now list the funds you can use. Keep money in your bank separate from payment balances, pending payouts and amounts withheld by a provider. Each may have different rules for funding a refund.

Stripe's refund documentation provides a useful provider-specific example. Refunds use its available balance, excluding pending amounts. When that balance is insufficient, card refunds can remain pending, while refunds for other payment methods fail. Stripe also says the original processing fees aren't returned. Your ticketing arrangement may handle funding and fees differently, so verify its own rules.

Ask your provider which balance pays the refund, how to add funds if necessary, and how long that takes. Confirm whether the platform or your payment account handles the operation. A healthy bank balance helps only if the required money can reach the refund process in time.

For a provider-held reserve, get the written conditions. Is the money available to meet this event's refunds? Who authorizes its use? Could it cover another obligation instead? Until you've confirmed the answers, don't subtract the withheld amount from the cash you need to arrange yourself.

Also check who controls the bank account. Money belonging to another event, tax money you've set aside or funds committed to payroll aren't spare refund cash. Record the allocation so the same balance can't be promised to two different payments.

Keep the record practical. For each funding source, write the amount, where it sits, what it's already committed to, and the earliest reliable date it can fund the refunds. Any condition that could stop access belongs next to the amount.

Calculate the shortfall before spending the payout

Return to our invented event. Suppose you have $11,000 in bank cash specifically available for refunds. You also have $6,000 in a separate available payment balance that your provider has confirmed can fund these refunds.

Those are different funds, so together they provide $17,000. A further $4,000 comes from an existing credit facility whose terms you've checked. In this example, it remains drawable during cancellation, can arrive before the refunds need funding, and hasn't been allocated elsewhere. Total confirmed funding is $21,000.

Compare that amount with each scenario. The $2,500 routine requirement is covered. The $10,000 partial-disruption requirement is also covered. The $51,000 cancellation requirement leaves a $30,000 shortfall.

That doesn't mean you should distribute the difference between $21,000 and $2,500. Some of that funding is borrowed, the disruption scenario needs more, and the wider business still has bills. It means you've identified exactly which scenario lacks funding and how large the current gap is.

The calculation is simply the scenario requirement minus confirmed funds usable by its deadline. A negative result means that scenario has a surplus under the stated assumptions. It doesn't establish accounting profit or make the money available for any purpose.

If the credit facility can be withdrawn under conditions likely during cancellation, remove it and calculate again. If money takes longer to transfer, exclude it from the earlier deadline. A facility's headline limit and the amount you can actually use can differ.

Keep the full scenario visible even if you decide to protect a smaller amount in cash for daily operations. Write down how the rest would be funded. An unexplained difference between the exposure and the reserve is a funding problem waiting for an owner.

Be particularly careful after a successful sales push. In the invented example, another $5,000 of fully refundable buyer payments would raise the cancellation ticket amount to $55,000, assuming nothing else changed. It could also increase available funds, but only by the amount actually usable after deductions and other allocations. Update both amounts instead of celebrating the larger bank balance on its own. Assign one person to check both amounts after each large sales release.

That review doesn't require you to freeze every new receipt. It tells you whether the funding decision you made still works at the new sales level. If the cancellation gap is increasing, decide how much of the new cash must stay available and what other funding needs arranging. Make that decision before approving extra production spending. Otherwise strong sales can encourage bigger commitments while leaving the business less able to repay buyers if delivery becomes impossible.

Count insurance and supplier recoveries carefully

Insurance can reduce your eventual loss, but a possible claim isn't cash available today. Check whether the relevant cause is covered, which losses qualify, the excess and limits, and what the insurer requires before paying.

The Australian Government's business insurance guidance recommends understanding exclusions, settlement methods and policy conditions, and contacting the insurer promptly when making a claim. Apply that care to your cancellation plan. Ask your broker how refund payments would be funded while a claim is being assessed, rather than assuming the policy provides an immediate transfer.

Our event cancellation insurance guide explains the cover questions in more detail. For this calculation, keep expected insurance recovery and the cash needed before recovery as separate entries. Otherwise an insured loss can still leave you unable to return buyers' money on time.

Treat supplier repayments the same way. Read the contract, establish what can be recovered, and confirm when repayment would arrive. A refundable venue deposit may help later, but it doesn't fund tomorrow's refunds if the venue hasn't returned it.

Don't count a recovery twice. If a provider uses money it holds to refund buyers, reduce the buyer balance still payable and the remaining held money consistently. You haven't created additional cash. You've used existing cash to settle an obligation.

For uncertain recoveries, show a version without them. That lets you see whether the event depends on a quick, cooperative response from another business at exactly the moment both organizations may be dealing with disruption.

Keep disputes separate without paying twice

A chargeback is a buyer disputing a payment through their card issuer. It can affect cash while you're still deciding how to respond, so it belongs in the funding plan as well as the support process.

Stripe's explanation of disputes says it debits the disputed amount and a dispute fee from the balance. It also explains that future-event disputes can have timing linked to the event date. The precise rules vary, so don't treat your voluntary refund deadline or event day as the automatic end of all payment exposure.

For cash planning, use the provider's actual debit and remaining obligation. A disputed amount already removed from your balance shouldn't also appear as cash you still hold for that same repayment. Related charges may remain an additional cost.

When a booking appears in both your refund list and dispute list, check its status before issuing money. Your provider may require you to handle the case through the dispute process. Coordinate finance and support so one person doesn't approve an ordinary refund while another handles the same transaction elsewhere.

You can estimate future disputes separately for ordinary operations, as our example does. Under full cancellation, check how much of that estimate duplicates payments already included in the buyer refund total. Add genuine extra costs, rather than adding the same ticket value again.

Keep records by order or payment reference. A total called refund costs is difficult to reconcile when it mixes completed refunds, pending requests, disputed transactions and service charges. The calculation becomes easier when each amount has a status that explains what still needs funding.

Keep refund cash separate from the event's operating balance

There's an easy way to count the reserve twice in a cash forecast. You remove reserved cash from the opening balance, then subtract the same reserve again as though setting it aside were another event expense. That makes the forecast look worse than the underlying bank position.

The opposite error is more dangerous. You leave all the money in opening cash, let the forecast spend it on suppliers, and point to a separate reserve note as evidence that refunds remain funded. The note doesn't stop the payment leaving the account.

Choose a consistent approach with the person maintaining your accounts. If the forecast starts with cash available after the reserve allocation, track reserve receipts and refund payments separately so you can reconcile everything back to the actual balances. If you show the full cash balance, make the protected amount visible when judging how much is available for other payments.

For a business running several events, do this for each event before combining the totals. Then test a disruption that affects more than one event. Two shows using the same venue might both need refunds after one closure. A shared cash pool can support either show individually and still fail when both need it together.

Watch for shared funding too. If the same credit facility supports both events, don't give each event the full undrawn limit. Allocate the available amount once in the combined calculation. Check whether other business commitments would consume it before the refunds are due.

The same discipline applies to recovering money. Once a supplier repayment arrives, update the bank balance and remove the separate expected recovery. Leaving both in the plan counts one receipt twice. Good reserve planning follows each amount as its status changes.

Set a reserve rule your team can follow

Once you've chosen the funding plan, decide who can release reserved money. Otherwise a supplier payment can consume the reserve even while your spreadsheet says it's protected.

A separate bank account can make the allocation easier to see, provided you can transfer the money when needed. Clear records within an existing account can also work. Simply moving cash into another account doesn't create a legal trust, establish buyer protection or change your obligations. Get specialist advice if you need a formal protected arrangement.

Set your own approval rule. Before releasing money, someone checks outstanding refund requests, current scenarios, access to funding and the remaining delivery commitments. Record the amount released and why the revised reserve remains sufficient.

Use conditions you can observe. A major group booking, an announced venue change or a delay in replacement funding should trigger another calculation. So should a refund backlog growing beyond the assumption you used. Decide who receives the alert and who can pause discretionary spending.

For routine buyer refunds, make the operation match the forecast. Loopyah's ticketing tools let you set a period after purchase when buyers can refund themselves. Include bookings still within that window in your estimate. The setting handles that buyer action; deciding how to fund the resulting refunds remains a business responsibility.

Don't reduce the reserve merely because the window has closed. That may reduce voluntary requests under your policy, while cancellation rights, approved exceptions and payment disputes still need separate consideration. Update the relevant scenario instead of assuming every obligation ends at once.

Decide what changes when the cancellation plan falls short

In the example, the current problem is the $30,000 cancellation funding gap. Naming it gives you a concrete decision. You need dependable additional funding, lower exposure, different commitments or a different event plan.

Start before signing the next nonrecoverable commitment. Could you agree supplier terms that return more money sooner if cancellation occurs? Could you reduce a discretionary production cost and retain the cash? Could the owners fund the gap without depending on another event's ticket receipts?

Ask what each proposal actually changes. Negotiating a later supplier payment may improve normal cash flow without reducing the amount owed after cancellation. Insurance may reduce eventual loss without solving the immediate refund deadline. A new credit line helps only if it remains available in the circumstances you've modelled.

Avoid treating the next event's presales as an automatic solution. That event has its own customers and delivery obligations. If you allocate its cash to this cancellation, calculate what remains for the next event and whether the arrangement is lawful and financially workable.

If you can't meet obligations, involve your accountant and an appropriate local adviser promptly. The decision is bigger than choosing a reserve percentage. More sales can increase both available cash and the amount buyers may need returned, so continuing unchanged may enlarge the problem.

Make the decision in writing, with the assumptions that justify it. Revisit it when ticket sales or event conditions change. A funding plan that was adequate at launch can become inadequate as the outstanding buyer balance grows.

Review the amount after the event too

A delivered event changes the risk, but it doesn't instantly settle every booking. Before releasing the remaining reserve, reconcile completed refunds, requests still being reviewed, outstanding disputes and any other obligations you've included.

Check what actually happened against your assumptions. Did routine refunds come from a particular ticket type? Did requests arrive together after a reminder? Did the payment process need funding earlier than expected? Use those answers when estimating the next event, without turning one unusual result into a universal rule.

Keep unresolved amounts assigned to someone. A refund that failed still needs investigation. A supplier recovery that hasn't arrived is still uncertain. Write the next follow-up date so neither disappears when the event team moves to the next show.

The useful decision today is specific. Calculate the refunds you may need to fund, confirm which money can reach them before the deadline, and identify any uncovered amount before spending the payout. When that calculation supports a smaller reserve, you'll know why. When it exposes a gap, you'll still have time to change the plan.