How should an event business track unredeemed gift vouchers?

You sell a batch of gift vouchers before the holidays, the money arrives, and January looks a little less uncomfortable. Then the recipients start booking. The workshop fills up, you buy materials and pay the tutor, but very little new money comes in. Those customers paid you months ago.

That's the part of gift vouchers you want to keep visible. Track the value people can still spend, link every redemption to the booking it bought, and forecast what you will need to deliver those visits. A total called "gift voucher sales" won't tell you how much of the money is still supporting a promise to a customer.

I'd keep two questions in front of the team. How much valid credit remains unused? And how much work have people booked with that credit that you haven't delivered yet? You can reduce the first number to zero while the second is growing. If you run paid workshops, performances or attractions, that difference matters when you decide whether you can afford another commitment.

This guide works through the records, a monthly reconciliation and the awkward changes that can make a voucher report misleading. The money examples are invented and use USD. They explain the decisions; they aren't figures from an event business or a recommended reserve percentage.

Start with what the voucher actually promises

A monetary gift voucher lets someone spend a stated amount under its terms. A dated ticket gives someone admission to a particular event. A promotional code reduces a price. All three might arrive as a code in an email, but putting them in one total makes the business harder to understand.

For a purchased voucher, record both what the buyer paid and what the recipient can spend. Those amounts may match, but a discount or bonus can make them different. For a complimentary voucher, record why it was issued and who approved it. Giving someone credit doesn't mean you've received money to fund their visit.

Also identify which business owes the experience. Your company might issue vouchers across its own workshop calendar, or sell admission on behalf of independent hosts. In the second arrangement, someone needs to settle with the host when a recipient books. A balance report that doesn't identify the responsible business can't explain who must fund that settlement.

Write down the permitted uses before creating your tracking categories. Can the holder make several purchases? Are there excluded events? Does the amount cover booking charges? Is it a promise of a particular experience or simply credit towards the current price? Your records need to preserve the offer that was sold, especially when you change the programme later.

Our guide to selling event tickets as gifts explains the buyer and recipient journey. Here, the job is to follow the value after purchase. Keep a dated ticket in the event's booking records and a monetary balance in the voucher records, with a link between them when credit buys admission.

You don't need to make the buyer understand your accounting. They need a clear offer and a usable balance. Your team needs enough detail behind that offer to explain every amount without trying to reconstruct a holiday campaign from old emails.

Separate the customer balance from the accounting figure

The customer balance answers a practical question: how much can this holder still spend? The accounting figure answers a different question: how should the remaining commitment appear in your accounts? Give each report a clear name so staff know which one they are using.

For businesses applying AASB 15, the Australian Accounting Standards Board's guidance on customer prepayments says a prepayment creates a contract liability until the promised goods or services are transferred. A contract liability means you've received a customer's payment while still owing the promised service. Your accountant should decide the treatment under the rules your business uses.

Operationally, you still need to know where each customer's entitlement went. When someone exchanges credit for a future workshop, their spendable voucher balance falls. The workshop is still ahead of you. Keep its booking reference and event date so the finance team can distinguish an unused balance from a paid booking awaiting delivery.

Don't ask a box-office supervisor to decide when revenue should be recognised while handling a redemption problem. Agree the reporting rules with finance first, then give staff the actions they are authorised to take. They should know how to confirm credit, make a booking and escalate a disputed balance.

Tax needs a separate decision too. A revenue report, a voucher balance and a tax return may follow different timing rules. You can make the operational records useful to all three without pretending that one number answers every question.

Keep a history of changes, not just today's total

A current balance is useful at checkout. When a customer disputes it, you need the transactions that produced it. Keep one identifiable voucher account or record and a dated history of every issue, spend, restoration, refund and correction. Use the system's existing history where it provides this information.

The history should let another team member answer a straightforward question: why does this voucher show this amount today? If the answer depends on whoever handled the last phone call, the record is incomplete. An unexplained manual adjustment is particularly difficult to investigate after seasonal staff have left.

A practical record includes:

• A unique voucher reference, the issuing business and currency.

• The original purchase or authorised issue reference, issue date, spendable value and amount paid.

• The offer and terms version, including any lawful expiry date or statement that it does not expire.

• Each dated movement, its amount, type and resulting balance.

• The booking, refund or support case that explains the movement.

• Any replacement reference, approval and record of the original code being disabled.

• The current status and the person or system responsible for the latest change.

Keep the full redeemable code out of general reports where a masked reference will do. Anyone who can read a usable code may be able to spend it. Staff investigating a balance usually need a transaction reference and controlled access to the account, rather than a copy of every customer's code in a shared file.

Keep purchaser and recipient information distinct where the offer needs both. Someone can give a voucher away without creating another sale. A change of holder should preserve the financial history while giving support enough information to verify the person making a request under your actual policy.

For each movement, distinguish when it happened from when it was entered. A booking made late on the final day of the month might appear in a later export. Both dates can be useful when you investigate the difference. Agree which date determines the reporting period, and keep that choice consistent.

Make the monthly balance explain itself

Here's a fictional month for an operator that sells monetary vouchers at their face value. There are no discounted issues, taxes or fees within this balance calculation. Nobody has approved an expiry removal or other adjustment during the month, and replacements carry value forward without adding to it.

The operator starts with $12,000 of unused valid credit. Customers buy another $8,000. Holders apply $5,500 to bookings, and approved voucher refunds remove $400. Separately, bookings made in an earlier reporting period are cancelled, returning $600 of credit to the voucher accounts that funded them.

The calculation is:

• Opening unused credit: $12,000.

• Add newly issued paid credit: $8,000.

• Add credit restored from cancelled bookings: $600.

• Subtract credit applied to bookings: $5,500.

• Subtract refunded credit removed from circulation: $400.

• Closing unused credit: $14,700.

That $14,700 should equal the sum of the individual valid balances at the same cutoff. If it doesn't, find the transactions behind the difference. Don't insert a balancing adjustment just to make the report look finished. You would lose the clue that tells you whether a customer can still spend money the business has already refunded.

Notice that the $600 restoration isn't a new sale. It reverses an earlier use of credit because the associated booking was cancelled. Record the cancellation reference so finance can check the corresponding change in the event records. Otherwise the same value may appear as both an outstanding booking and newly available voucher credit.

The $400 refund needs evidence on both sides. The payment record must show the money returned, and the voucher record must show the credit removed. If the refund is still pending, report that state accurately. A request, an approval and a completed payment are different events.

Finally, compare new voucher purchases with payment settlements. Suppose the processor deducts $200 of fees from that month's $8,000 of purchases and transfers $7,800. The customer credit issued remains $8,000. The fee explains the difference in cash received; it doesn't reduce what holders can spend.

Follow redeemed value into the event it bought

Now look inside the month's $5,500 of redemptions. Suppose $2,300 paid for events already delivered and $3,200 paid for events still to come. That split tells you something the closing voucher balance cannot. There are customers with confirmed bookings who will arrive without paying you the voucher-funded amount again.

For this limited example, the $14,700 unused balance plus $3,200 applied to future bookings represents $17,900 of customer value still awaiting use or event delivery. That is an operational view of these records, with no taxes, discounts or other accounting adjustments. It excludes any future bookings that were already outstanding at the start of the month.

Keep the scope visible when you show the number to a colleague. Calling it "everything we owe" would be wrong if older prepaid bookings, cash-paid bookings or other obligations are outside the report. A useful subtotal can become misleading when its label promises more than it contains.

When a holder spends $60 on a future class, attach the voucher reference to that booking. Show the amount paid with credit and any additional payment. The class should have one booking and one set of places, even if the funding came through several payment methods.

Avoid counting the original voucher purchase and its later use as two fresh cash receipts. A sales report may legitimately show activity at both stages, but your cash forecast needs the actual money movements. The original payment arrived when the voucher was bought; using it moves the commitment into a particular event.

Loopyah's ticketing tools provide ticket types, confirmation emails linking to QR tickets and phone-based check-in. Those help manage the admission you have sold. Before connecting any voucher service, verify how it passes the payment allocation and booking reference into your particular setup. A ticket confirmation alone doesn't establish the remaining balance of a separate voucher.

Replacements should preserve value without issuing it twice

A lost email shouldn't force your team to guess what the holder has left. Find the voucher through your verified support process, inspect the transaction history and use the replacement method your provider supports. The replacement must preserve the entitlement while preventing the original and replacement from both being spent.

Imagine voucher GV104 was issued with $100 and used for a $60 booking. Its remaining credit is $40. If a replacement is authorised, move that $40 to the replacement reference and disable the old code. Across the linked records, the holder still has $40. There is no new $40 sale.

If your export shows a $40 issue on the new reference and a $40 removal on the old one, identify them as the two sides of a replacement. They cancel in the overall balance. Counting only the new issue inflates outstanding credit, while counting only the removal makes you appear to owe less than you do.

Keep the original purchase date and applicable terms available. Changing a code is an administrative action; staff should not invent a new expiry policy while doing it. If the approved remedy includes an extension, record that decision separately so the customer and finance team can understand what changed.

Partial refunds need similar care. If the remaining $40 is refunded under the applicable policy, remove that spendable value and link the completed refund. The earlier $60 booking doesn't disappear. If that event is later cancelled, investigate the original payment allocation and the correct remedy rather than restoring credit automatically into a closed account.

The useful test is whether someone can trace the whole sequence without asking the colleague who handled it. Purchase, booking, replacement and refund should connect. They should also leave the correct number of active codes and exactly the entitlement you still owe.

Treat cancellations according to how the booking was paid

Take a separate fictional booking worth $120, funded by $80 of voucher credit and a $40 card payment. If you cancel the event, identify both amounts before processing the remedy. Don't treat the full order as a card payment simply because the booking system shows a total price.

The lawful remedy and the agreed handling of each payment method need to be established for your market and circumstances. Operationally, record what you actually return. If $80 is restored as credit and $40 is returned to the card, link both movements to the cancelled booking and remove its admission entitlement.

That is an example of recording an approved remedy, not a claim that restoring credit is always sufficient. A cancellation may give the customer rights that your ordinary voucher policy doesn't cover. Escalate those cases through the person responsible for consumer terms, rather than asking frontline staff to decide under pressure.

Also check what happens if the customer chooses another date. A straightforward exchange might move the existing payment allocation to a replacement booking without reopening the voucher balance. Another system might reverse and reapply the credit. Either route needs a complete history and only one valid resulting booking.

Set a rule for failed or interrupted changes. If credit has been deducted but the booking hasn't completed, support must be able to find the attempted transaction and restore or complete it. Tell staff how to recognise a pending change so they don't repeat it and create a duplicate booking.

Our ticket management guide covers the wider administration of ticket records. For vouchers, add the funding question to every correction: where is the credit now, and which booking or refund explains it? That keeps a customer service fix from creating another unexplained balance.

Record discounts without shrinking the holder's entitlement

Suppose you sell a $100 voucher for $90. The buyer paid $90, but the holder can spend $100 under the offer. Keep both amounts. If you record only the payment, support may wrongly tell the recipient they have less credit than they were promised.

For twenty identical vouchers, the campaign produces $1,800 of customer payments and $2,000 of spendable value before any processing deductions. The $200 difference is extra spending power promised above the payments received. It isn't a separate cash expense. To assess the offer, work out the cost of delivering the visits and whether discounted credit replaces purchases people would otherwise have made at full price.

You also need enough detail for finance to allocate the amount received under the appropriate accounting policy. Don't assume that the customer-facing total is always the balance-sheet amount. Discounts, tax and other terms can affect the relationship. Preserve the original issue data rather than asking the accountant to infer it from the remaining balances.

Here's the same distinction on one voucher. The holder uses $35 from the $100 entitlement and has $65 left. A simple proportional management illustration would associate $31.50 of the original $90 payment with the value used and $58.50 with the value remaining. Those amounts add back to $90. They aren't new cash receipts or a prescribed accounting entry.

Keep free promotional credit separate as well. A $20 goodwill voucher issued after a complaint gives someone spending power without bringing in another $20. It may help retain a customer, but its issue should not inflate the paid-voucher sales figure. Record the reason and approved offer so you can assess what it costs to fulfil.

The same applies when a purchased voucher includes a bonus. Show the paid and promotional elements clearly enough to follow their respective terms. If those terms differ, your system must apply them correctly and explain the remaining balance honestly. Avoid constructing a promotion whose everyday partial redemption needs a manager to interpret it.

Forecast the cash required when holders finally book

Your unused balance is the starting point for planning, rather than the amount of next month's bills. A holder might use it next week, next year or across several bookings. You need an estimate of timing, the events they can buy and the cash costs those visits will create.

Return to the fictional $14,700 unused balance. For a separate planning exercise, suppose holders use $6,000 during the coming period to buy 120 admissions at $50 each. Assume all those visits occur in that period and generate an additional $12 cash cost per attendee for materials and refreshments. That creates $1,440 of future payments without another $6,000 receipt.

If delivering those bookings also requires an additional staffed session costing $900, the cash needed rises to $2,340. That session cost must be genuinely additional to the costs already in your forecast. If the staff were already scheduled and paid for, adding the same $900 again would overstate the change.

Now suppose twenty of those customers also buy optional extras, producing $300 of new cash after the related deductions. If there are no additional extra costs beyond those already included, that reduces the exercise's net cash requirement to $2,040. Don't assume the extras will sell just because they make the forecast more comfortable.

This example isolates the change caused by those redemptions. Your full cash forecast still includes venue bills, other wages, taxes, refunds, ordinary sales and amounts already committed to future bookings. You also need to consider a heavier redemption period and any refund obligations. The $2,040 is neither a recommended reserve nor enough to fund the whole business.

Use your actual issue and redemption history to improve the timing estimate. Group vouchers by when they were sold and what they can buy. A Christmas gift for a short workshop series may behave differently from credit usable across a year-round attraction. Don't borrow a retailer's redemption pattern and treat it as evidence about your own audience.

Our event cash-flow forecast guide explains how to put incoming and outgoing payments on a timeline. Add voucher-funded visits to that forecast with their delivery costs and any genuine new payments. The original voucher sale belongs on the date its money actually arrives.

Check whether your calendar can absorb the outstanding value

Cash isn't the only constraint. A voucher can remain valid while the holder struggles to find a suitable date. Look at the eligible programme, the number of places still available and the restrictions you advertised. A large selection of events is less useful if almost every suitable session is sold out.

For a simple capacity exercise, suppose holders want 120 places but the relevant dates have only 80 available. You have a shortfall of 40 places within that requested set of dates. It doesn't prove all holders will book together, but it tells you what happens if the expected demand concentrates there.

Find out whether alternative dates genuinely work for the offer. A weekday morning isn't an equivalent practical option for every customer who expected an evening workshop. You may need another session, a different sales limit for future voucher campaigns or clearer eligible-date information before the next purchase.

Don't quietly change existing terms to make your calendar easier to manage. Review what was promised and what remedies are required if you can't supply it. For new sales, test the offer against realistic capacity before promoting broad flexibility. Credit that can be spent across the calendar still needs a bookable event.

Also distinguish available places from places that would otherwise sell to new cash-paying customers. A voucher holder using a peak seat can displace a later sale, even if the direct cost of admitting them is small. That's a planning tradeoff to examine, rather than another amount to deduct automatically from the cash forecast.

The useful management view shows unused credit beside future voucher-funded bookings and the remaining eligible capacity. It helps the programme lead understand what the finance report means for the coming weeks. It also gives you a reason to change the next offer before a shortage becomes a customer service problem.

Approve expiry rules before removing old balances

An old balance deserves investigation. Age alone doesn't tell you whether it can be cancelled, recognised as revenue or paid elsewhere. Keep issue dates, the original terms, later extensions and the applicable market available before anyone processes a batch of expiry changes.

In Australia, the ACCC's gift card guidance generally requires purchased gift cards supplied from 1 November 2019 to remain redeemable for at least three years. It also lists exceptions, including certain genuinely discounted or time-limited offers. An event-related label doesn't establish which rule covers your voucher. Check the actual arrangement.

For covered US gift cards, the Consumer Financial Protection Bureau's gift card regulation generally protects underlying funds for at least five years from issue or the last load, subject to its scope and conditions. State requirements may be more protective. Don't copy an Australian expiry period into a US offer and assume it works.

Keep the customer-facing date and the legal review together. Your report might show a date entered when the voucher was created, but that doesn't prove the date was valid or that no extension was granted later. A system can apply an incorrect configuration very consistently.

Ask the responsible person to approve the criteria and the specific records before a bulk change. Preserve a record of which balances were removed, why, when and under whose authority. Keep disputed cases open for investigation. A customer who has already contacted you about a booking problem shouldn't disappear inside an unexplained expiry total.

For reporting, show balances that need review separately from those that have been lawfully closed. That lets you examine the work without pretending the customer has already lost their entitlement. It also avoids a month-end incentive to clear awkward records just because they have reached an age threshold.

Don't turn quiet accounts into assumed profit

You'll sometimes hear unused voucher value called breakage. It means customer rights that aren't exercised. It doesn't mean every voucher untouched for a while, and it isn't a percentage you should copy from another business to improve your event result.

Under the AASB guidance linked earlier, recognising expected unused value depends on your right to keep it and the reliability of the estimate. Recognition follows how customers exercise their rights. Otherwise, you wait until the likelihood of further use becomes remote. Amounts you must pay to another party remain liabilities. Have finance approve the treatment.

There can also be unclaimed-property requirements. The New York State Comptroller explains that unused gift cards can form part of abandoned property turned over to the state after a period of inactivity. That example shows why a holder's silence doesn't establish that the business can keep the amount. Check the rules relevant to your issuing entity and records.

Keep the operational history even when finance makes an approved accounting adjustment. Support still needs to establish the holder's rights, and those rights must follow the applicable terms and law. A financial reporting decision should not silently rewrite what the checkout will accept.

Give tax its own classification

Before launching a voucher offer, give your accountant the exact terms, eligible products, issuing business and redemption arrangement. Include whether another operator will supply the event. These facts are more useful than asking a broad question about how gift cards are taxed.

For UK VAT, HMRC's guidance for vouchers issued from January 2019 distinguishes single-purpose and multi-purpose vouchers. Broadly, the distinction concerns whether the place of supply and VAT treatment are known at issue. VAT timing can differ between issue and redemption. It isn't decided simply by whether you sell one workshop or several.

Get the classification and reporting instructions agreed before staff build the offer. If the programme changes to include different products or suppliers, ask whether the existing treatment still applies. Preserve the terms version on older issues so a later change doesn't erase what those transactions represented.

Your records should let finance find the amount paid, the value redeemed, additional customer payments and any taxes or fees recorded separately. Keep adjustments traceable through to the source transaction. Don't deduct an estimated tax amount from the holder's visible credit unless that is actually how the lawful, advertised offer works.

The point is to make tax reporting possible without confusing it with redemption. A voucher can have a tax consequence before an event happens, while the operational team still owes a visit. Use the approved rules for each report and reconcile the differences explicitly.

Agree settlement when another operator delivers the event

If vouchers can buy events supplied by partner operators, confirm how each partner gets paid before selling that flexibility. The buyer may have paid your business months earlier, while the host needs money for the specific booking now. Someone needs to fund the gap between those transactions.

Agree which amount the host receives, when it becomes payable and who bears any discount you gave the original buyer. If a customer bought $100 of credit for $90, the host shouldn't discover the discount through an unexplained short payment. The commercial agreement needs to say how that offer is funded.

Give each redemption a host reference and a settlement status. A booking confirmation establishes the place to be delivered, but it doesn't show whether the host has been paid. Track amounts due, amounts paid and disputed adjustments so finance can distinguish the customer's entitlement from the separate supplier payment.

Work through a cancellation together. If the host cancels after receiving settlement, who returns money to whom, and how does the customer receive the remedy they are owed? Record the approved steps in both sets of records. Don't restore spendable credit and leave an unreconciled supplier payment that everyone assumes someone else will recover.

Also decide how a partner leaving the programme affects existing holders and bookings. Preserve the original offer and obtain the appropriate advice on the commitments involved. For planning, identify which future payments and eligible events remain available before selling vouchers that promise access to that partner.

Keep settlement reports limited to the information the host needs to check its bookings and payments. A partner handling one workshop doesn't need access to every voucher holder or their wider purchase history. Give both teams a named contact for differences so customer support can find an answer without making recipients negotiate the supplier arrangement themselves.

Set staff permissions around the changes that matter

Most balance problems become easier to resolve when staff can see the right history. That doesn't mean every team member should be able to issue unrestricted credit, approve refunds and change expiry dates. Match access to the person's actual job, and name an escalation contact for exceptions.

A booking agent may need to check a balance and apply it to an eligible event. A supervisor may approve a replacement after verification. Finance may approve corrections that change the total outstanding value. Decide those responsibilities in your own team and configure the available permissions accordingly.

A correction needs a reason that identifies the error. "Customer service" doesn't explain whether credit was duplicated, restored after a failed booking or issued as a goodwill gesture. Record enough for another person to check the decision, while keeping unnecessary personal details out of the finance report.

Test duplicate use before relying on the process during a busy sales period. Two staff members can be helping the same holder at once. Your redemption service needs a reliable way to prevent both bookings from spending the same available balance. A report refreshed later won't prevent an overspend that has already been accepted.

Test interrupted transactions too. A browser timeout shouldn't leave staff unable to tell whether the credit was taken. Give them a supported way to find the attempt and resolve it. Avoid telling the customer to keep trying while the status remains uncertain.

Keep a queue of unresolved cases with an owner and next action. Review it when reconciling balances, because these cases often explain the differences between a payment report and a voucher export. A neat closing total is less useful if nobody can explain which customers are still waiting for a correction.

Close the month with a short, reviewable report

The person checking the month should be able to follow the result without opening every voucher individually. Start with the opening balance and the dated movements. Show the closing balance, the sum of individual accounts and any difference still under investigation.

Then show the part of redeemed value attached to future events. Keep that separate from unused credit and identify the events involved. Add the latest cash and capacity concerns, including a concentration of bookings or an offer whose remaining eligible dates are becoming difficult to supply.

A useful monthly handover answers these questions:

• Does every issued paid voucher connect to a purchase, and does every other issue have an approved reason?

• Do redemptions connect to valid bookings, including the split between credit and new payments?

• Do refunds, replacements and restored balances have matching changes in the other affected records?

• Does the closing total agree with individual balances at the same cutoff?

• Which future events still need to be delivered, and what additional cash or capacity will they require?

• Which legal, accounting or tax decisions remain open, with whom and by when?

Keep the supporting exports and approvals under your business's retention and access rules. Save the report date and cutoff so next month's reviewer can reproduce the opening figure. If you correct a previous period, show the correction rather than quietly replacing the number people already used for a spending decision.

Connect the findings to your review of actual and forecast event costs. If voucher-funded demand needs another tutor or a larger materials order, update the event forecast. If a payment discrepancy has no effect on delivery costs, investigate it without inventing an extra expense to make the totals agree.

Use the report to make a specific decision. You might limit a new promotion, add an eligible session, fund an upcoming supplier payment or fix a repeated booking error. More voucher sales won't resolve a balance you can't explain or an event you can't afford to deliver.

Test the whole sequence before the next campaign

Choose a test voucher and follow it through purchase, partial use, a future booking, a cancellation and a replacement. Use your provider's supported test route and staff permissions. Check the customer balance and the booking records after each step, then trace the money separately.

Ask someone who didn't set up the offer to explain what happened. Can they find the original payment, identify the credit still available and tell which event remains to be delivered? Can they resolve the failed booking without issuing extra value or making the customer wait for the one person who remembers the case?

Run the same check against a discounted voucher and an offer with an extension. Those are the cases most likely to expose a report that assumes every amount paid equals the amount spendable. Fix the configuration or reporting before inviting more people to buy.

Then open the coming events and your cash forecast together. Confirm that recipients have a realistic route to book and that the costs of their visits are funded. When those checks agree with the voucher history, you can sell the next batch knowing what it adds to the business and what you still have to supply.