How do you track refundable deposits for an event?

You've collected the exhibitor payments, ticket sales are coming in, and the bank balance looks healthy. Then your operations manager asks when the exhibitors get their deposits back. Some of the money you've been looking at was never available to pay for the show.

Track refundable deposits separately from event revenue, with a balance for each payer and a cash plan for returning it. Record what you received, what you've returned, any properly supported amount applied elsewhere, and what remains unresolved. Your team should be able to explain that remaining amount without searching through messages after the event.

The distinction matters even when the deposit lands in the same bank account as everything else. A payment can increase cash while creating an obligation to pay someone back. If you count it as sales and spend it on production, a profitable-looking event can finish with a refund bill it cannot meet.

This guide focuses on refundable security deposits you collect as an organizer, using a fictional ticketed design fair with exhibitors. We'll follow the same money through collection, settlement and return, then build a record you can adapt. Every dollar amount is an invented example in USD, with taxes excluded. None is a recommended deposit, payment-provider price or estimate of likely damage.

Start by asking what the payment is for

The first thing you want to do is stop using "deposit" as a complete description. Your team might use that word for a booking installment, a refundable security payment, a reservation or a temporary card authorization. Those arrangements create different obligations, even if the receipt gives them the same name.

An exhibitor might pay part of a stand fee now and the remainder later. That first payment contributes toward the service you're selling. Separately, you might collect security against specific damage or cleaning obligations, with the unused balance returned afterward. Record the stand payment separately from the security, with the agreed purpose and return conditions clear for each.

A card authorization is different again. If you haven't captured the payment, you haven't collected cash. Record the authorization, its conditions and expiry through the provider's supported process. Don't include an uncaptured hold in your bank reconciliation or assume it will still be available when somebody reports damage after the event.

For the design fair, suppose each exhibitor pays a $600 stand fee and a separate $200 refundable security deposit. The stand fee buys the agreed exhibition service. The deposit secures defined obligations under the exhibitor agreement. An exhibitor paying $800 has therefore paid for the stand and provided security, even if both amounts arrived in one transaction.

Keep that split visible in the offer, invoice or receipt and internal records. If the payment system combines both amounts, you still need a reliable way to identify each component. Ask whether its reports distinguish them and whether a partial refund can be tied to the security portion. A convenient checkout doesn't settle the accounting classification.

Our guide to ticket deposit presales covers a different decision: taking a conditional payment toward admission before committing to production. Here, we're dealing with security money that is separate from the price of the service. If you run both arrangements, don't combine them into one unexplained deposits total.

Separate cash received from revenue earned

Money arriving tells you that a payment happened. It doesn't, by itself, tell you what the business has earned. That's why a sales report, a bank statement and a deposit register can show different totals without any of them being wrong.

If your business reports under International Financial Reporting Standards, or IFRS, the IFRS Foundation's revenue recognition overview connects revenue to transferring promised goods or services to a customer. Collecting cash and delivering the service can happen on different dates. A stand fee received before the fair therefore needs its own timing assessment, separate from the refundable security payment.

The Foundation's IAS 32 overview also explains the importance of an obligation to deliver cash when classifying financial liabilities. A liability is an amount the business owes. Have your accountant confirm the actual classification, measurement and entries for your deposit agreement and accounting framework. These references explain the distinction; they don't classify every arrangement called a deposit.

For your operating report, keep refundable security out of earned sales while it remains repayable. Show the money held and the obligation alongside the event result. That lets the commercial team understand performance while finance can see the cash needed for returns. Neither view has to conceal the other.

Suppose the fair has 20 exhibitors on the terms above. Stand fees total $12,000 and security deposits total $4,000. The total collected from them is $16,000. After the agreed stand services are delivered, the example's stand revenue is $12,000, assuming the relevant recognition conditions are met. The $4,000 doesn't become extra revenue because the event has ended.

Before delivery, the stand fees may themselves need to remain recorded as advance payments under your accounting policy. Keep the operational split clear throughout. One part relates to services promised, while the other is refundable security. A single bucket labelled "not yet revenue" can hide those different reasons and the different actions needed to resolve them.

Tax reporting is another question. The fact that you exclude a security payment from a management sales total doesn't determine its sales tax, VAT, GST or income tax treatment. Ask for advice on the actual arrangement and location. Give the adviser the payment terms and repayment conditions, rather than asking only whether deposits are taxable.

Agree the return rules before collecting money

Your deposit register will only be useful if it tracks a clear promise. Agree what the security covers, what permits a deduction, who assesses it and how the payer can question the decision. Define the return trigger and deadline in terms the people running the fair can follow.

For exhibitors, that may involve an inspection after removal of their stand materials. Establish which area they are responsible for, what condition was recorded at arrival and who can approve the final assessment. A deposit can't solve a missing handback process. If nobody records the condition, the finance team receives an accusation rather than a supported settlement.

Be specific about ordinary service costs. If normal cleaning is included in the stand fee, don't quietly deduct it again from security. If additional cleaning may be charged in defined circumstances, explain the basis and keep the evidence. The agreement, actual facts and applicable law determine what you can recover, not the fact that you already hold the money.

In Australia, the ACCC's guidance on contracts and unfair terms explains protections applying to standard form consumer and small business contracts. A term being printed in your agreement doesn't automatically make it fair or enforceable. Get your terms checked for the markets and customers involved, including return deadlines and any proposed deductions.

Decide who communicates with the exhibitor if a charge is proposed. Operations can describe what happened, but finance needs an authorized settlement before changing the deposit balance. Tell the payer what amount is questioned, what supports it and how to respond. Return any undisputed amount as required by the agreement and law rather than inventing a blanket hold.

If you pay a venue its own bond, track that separately too. Your venue damage deposit is money another business may owe back to you. Exhibitor security is money you may owe back to exhibitors. Similar wording doesn't give you a right to use one balance against the other, or make the dates match.

Build a record for each payer and payment

You don't need to start with a complicated system. You need a record that survives a partial refund, a staff handover and a question from someone who paid months earlier. Give each deposit a unique reference and connect it to the original transaction and the relevant event.

Use a separate payment entry when the same exhibitor makes another security payment. An extra stand might increase the security required. If you overwrite the original receipt amount, you lose the history needed to match the bank. Keep the agreement's total requirement separate from the individual payments that satisfy it.

A practical deposit record includes:

• Event reference, exhibitor reference and deposit reference.

• Payer's name and the business or booking the payment relates to.

• Deposit purpose, agreed amount, currency and accepted terms version.

• Original payment reference, date received and amount collected.

• Settlement reference, fees, payout date and location of the money.

• Inspection or release trigger, expected decision date and return deadline.

• Each proposed deduction, supporting evidence, decision and approver.

• Each approved return, submission reference, amount and processing status.

• Remaining refundable or unresolved amount, case owner and next action date.

The original payment reference matters more than a familiar trading name. One company may pay for several exhibitors, or a staff member may use a personal card. Link the payer to the booking without assuming that the person running the stand is entitled to redirect the refund to any account they name.

Keep documents attached or clearly linked, including the accepted terms, payment evidence, inspection record and settlement statement. The US IRS's recordkeeping guidance explains how business transactions generate supporting documents for accounting records. Use the retention requirements appropriate to your business and jurisdiction; a summary balance doesn't replace the underlying evidence.

Limit access according to the job. The floor manager needs the exhibitor, inspection requirements and unresolved condition questions. The person issuing refunds needs the approved amount and original payment route. Store sensitive payment information in the provider's supported system, and use references in the operating record. A shared event sheet shouldn't become a collection of card or bank credentials.

Follow the $4,000 through settlement

Let's return to the fictional fair. All 20 exhibitors pay their $200 security, so you collect $4,000 of refundable deposits. For this example, the deposits are processed separately from stand fees. That makes the deposit settlement easier to follow without implying every provider supports the same setup.

Assume the processor deducts $80 in collection fees and pays $3,920 to your bank. These are invented charges, not a published price. Your refundable obligation is still $4,000 under the example's promise of returning the full unused security. Receiving a net payout doesn't reduce what each exhibitor paid or what you may owe back.

Record $4,000 collected, $80 of organizer-borne fees and $3,920 settled to the bank. Then fund the missing $80 from the business's own available money. Your deposit return funding can now cover the full $4,000. If you simply put aside the payout, you're short before the event has even begun.

This is where a neat bank total can be misleading. A report that labels the $3,920 payout "deposit income" both confuses revenue and conceals the fee gap. Keep gross collections, costs and net settlement distinct. If stand fees and deposits arrive in one payout, reconcile each component to the provider's settlement statement rather than assigning the whole deposit to sales.

The same logic applies if the provider hasn't paid out yet. A successful customer payment can appear in the deposit register before the cash becomes available to your bank or refund balance. Record the location and status of those funds. Your return plan must use the money the actual refund route requires, not whichever total looks largest.

When checking the deposits, ask two questions. How much security have we collected and not yet resolved? Where is the money available to return it? A difference needs an explanation, such as settlement still pending, fees needing replacement or a failed return coming back through the provider. "It's somewhere in the ticket account" isn't enough.

Keep deposit funding out of the spending decision

Separating a balance in a report helps people understand it. Separating the money operationally can also prevent accidental spending. Depending on your arrangements, that might mean a designated bank account or an internal cash allocation with controlled access. Find out whether any legal, contractual or provider requirement prescribes how the funds must be held.

A second account by itself doesn't create escrow, a trust or protection from business failure. Don't make those promises to payers unless the actual arrangement supports them. Explain what you really do, and have the legal position checked where you collect material sums. Operational discipline and legal protection are different questions.

Consider a snapshot immediately before the fair. After the deposit fees and the business's replacement of that $80, suppose the designated deposit account contains $4,000. A separate operating account has $8,500 of cleared money. Total bank cash across the accounts is $12,500. The business also has $6,000 of ordinary bills due before any further receipts.

Keep the $4,000 allocated to deposit returns. Paying the ordinary bills from the $8,500 operating balance leaves $2,500 for other decisions. Looking at $12,500 and subtracting only the bills would suggest $6,500 was free. That would overstate the unallocated balance by the same $4,000 the exhibitors may need back.

Now suppose you're considering a $3,000 production upgrade. On this simplified snapshot, the available operating money falls $500 short, even though total bank cash looks sufficient. The choices are to reduce or defer the upgrade, secure other funding or identify a genuine available receipt before payment. Don't assume that a proposed deduction from somebody's deposit will finance it.

These figures are a limited cash check, excluding other commitments and minimum cash requirements. Your full event cash-flow forecast needs the actual payment dates, provider balances, incoming settlements and all the bills. Keep the deposit return schedule within that forecast so finance doesn't approve spending from a figure that already belongs to another commitment.

Show the event result without deposit collections

Assume the fair has now delivered its promised services. Its earned ticket revenue is $18,000 and earned stand revenue is $12,000, before organizer-borne payment costs. Total earned revenue is $30,000. Assume all other operating costs, including ticket and stand payment costs, total $26,000. The separate $80 deposit collection fee has not yet been included.

The result is $3,920 of operating profit after that additional $80 cost, before financing and income tax. The $4,000 collected as security doesn't increase the $30,000 earned revenue. Nor does returning the full $4,000 create a new $4,000 event expense. Under the example's treatment, collecting and returning security changes cash and the amount owed, while the $80 processing cost affects profit.

If you add security collections to revenue, you'd incorrectly report $34,000 of revenue and $7,920 of profit on those same cost assumptions. Both totals would be overstated by $4,000. That is enough to change your view of whether to repeat the event, increase the production budget or pay yourself a distribution.

Our event profit and loss template explains the wider statement. Keep the deposit balance as a separate supporting record, with its movements reconciled to the accounting system. You can then explain the event's return and the remaining repayment exposure in the same review without mixing them into one result.

Later deductions may change the final result, but they need their own accounting assessment. Damage recoveries, reimbursements and amounts applied to unpaid service invoices aren't interchangeable kinds of ticket sales. Record the related costs and avoid counting the same invoice twice. The deposit register documents where the security went; it doesn't decide the financial statement presentation by itself.

For that reason, keep the $3,920 as the result before any later damage costs or recoveries in our example. When we settle the deposits below, we won't assume every dollar retained is extra profit. Finance must record the actual underlying events on the appropriate basis before approving the final P&L.

Reconcile the register to the accounting and cash records

A useful reconciliation connects the detail to a total and explains any difference. Start with the deposit balance carried forward, add new collections and subtract properly resolved amounts. Keep transfers or accounting corrections visible rather than changing the opening balance to make the total fit.

For a simple deposit balance check, use this structure:

• Opening refundable or unresolved balance.

• Plus new security payments collected.

• Less returns that have reached the verified completion stage in your process.

• Less authorized amounts validly applied to another obligation.

• Plus or minus documented corrections or transfers.

• Equals the closing refundable or unresolved balance.

Agree with finance how in-transit refunds appear. The operational register can keep a case open until completion while the accounting system records the cash movement earlier. Add an explicit in-transit category so the difference is understood. Don't force the accounting liability, payment-provider balance and open-case total to agree by deleting pending cases.

Check by currency before consolidating anything. A deposit collected in one currency and returned in another can involve conversion and timing differences. The customer promise, processor mechanics and accounting policy decide how those are handled. Preserve the original currency and amount, then record the actual conversion rather than treating a translated reporting total as the refund instruction.

Check the deposit-related cash as well. It starts with collections, then reflects fees, bank settlements, funds added by the business and payments out. Transfers between your own accounts move the money without settling what you owe the payer. If a transfer reduces the apparent deposit balance in one account, the destination needs to remain visible.

Finally, compare the total balance in the accounting records with the detailed cases. A $1,000 total with no explanation of the payers behind it is difficult to return accurately. Twenty individually plausible rows that don't match the accounting balance are also unfinished. Resolve both directions before telling the event lead how much can be released for other spending.

Settle deductions and partial returns without losing the history

Suppose the fair's inspections and settlement process produce three groups. Sixteen exhibitors qualify for full returns of $200 each, totaling $3,200. Two other exhibitors have separate, accepted deductions of $50 and $100. They receive $150 and $100 back respectively, totaling another $250. The remaining two deposits of $200 each are unresolved.

For this example, assume the $150 of deductions is permitted by the agreements, supported, approved and accepted. Don't treat those assumptions as a shortcut for your own disputes. A proposed charge remains a proposed charge while responsibility, amount or enforceability is being resolved. Keep the full questioned balance visible under the treatment agreed with finance.

After the completed returns of $3,450 and the valid application of $150, the register has $400 still unresolved. The balance check is $4,000 collected, less $3,450 returned, less $150 applied, leaving $400. Every exhibitor can be traced through that calculation, including the two who received partial returns.

Your cash record answers a related question. Starting with $4,000 funded for returns, paying $3,450 leaves $550. Of that, $400 still supports unresolved deposits and $150 corresponds to the accepted applications. Decide how to account for and transfer that $150 through your approved process. It hasn't all become freely spendable simply because the deduction was accepted.

The related cleaning or repair bill may still need paying. If the accepted $150 settles a charge already recorded elsewhere, apply it against that charge once. If finance determines a different recovery treatment, follow it and record the supporting cost. Never show the deduction as new income and also pretend the underlying damage cost disappeared.

For one partial-return record, write the complete history. Deposit DEP-017 collected $200, accepted additional-cleaning charge $50, completed return $150, closing deposit balance zero. Link the cleaning evidence and approval to the charge and the payment reference to the return. Keeping only the final zero would hide the reason that exhibitor received less.

Treat refund submission and completion as different steps

The person pressing the refund button needs a clear approval. They also need to report what happened afterward. Approved, submitted, pending, failed and completed are different states. Preserve the provider's actual status and define what your team means when it says a return is complete.

Stripe's refund documentation explains that refunds use the available Stripe balance and that insufficient funds can leave card refunds pending. It also describes failed refunds, including cases requiring an alternative return method. Those are Stripe's mechanics, not a promise about every payment provider or every Loopyah transaction. Check your actual payment route before choosing the funding and follow-up process.

In the fair example, suppose you submit the final two $200 returns. One completes and the other fails. The unresolved amount falls from $400 to $200 when the first return reaches the agreed completion stage. The failed return remains an open obligation. An instruction appearing in yesterday's activity report doesn't prove that the payer has been paid.

If the provider had already removed the failed return's money from your available balance, track it as in transit until the provider returns it or confirms what happened. Don't count that same $200 as both available funding and money already delivered. Your case record and cash record can temporarily differ, but they need a named explanation and an owner.

Contact the payer with the actual status, the amount, any reference available and the next action. Avoid promising the date their bank will display the money unless you have a sound basis. Distinguish your submission deadline from provider processing and bank posting. Someone asking where their money is needs a specific update rather than "all refunds processed."

If you arrange an alternative payment, verify the recipient through an established contact and follow your approval controls. Confirm what happened to the original attempt before paying again, especially if a payment dispute is also open. Keep both references together so another staff member doesn't issue a second replacement while trying to be helpful.

Use a short team review while balances remain open

Review frequency should follow the work. During collection, check that successful payments and settlements are coming through as expected. Around handback, concentrate on inspections and return approvals. During close-out, concentrate on pending payments, disputed deductions and missed deadlines. Give each open case an action date rather than waiting for someone to complain.

A short review can answer a few concrete questions. Which deposits have become eligible for return? Which assessments are waiting for operations? Which payments were submitted but need attention? How much money must remain available, and where must it sit for those returns to work? The answers should come from records the team already maintains.

Keep commercial pressure out of the settlement decision. If ticket sales are slower than planned, the deposit balance hasn't become more available. If you waive a supported charge for a returning exhibitor, record who approved the concession and how the business will cover the cost. Apply the agreed process consistently.

Loopyah's Event CRM financial view brings ticket, door and sponsor sales, refunds and fees into the event's financial picture, lets you add costs, and distinguishes cash paid out from money on the way. Use that connected information for the wider event result and funding review. The security deposit arrangement still needs a verified record of what each payer is owed and how it is resolved.

Before collecting security through any tool, ask for a demonstration of your exact workflow. Test a stand fee plus deposit, a partial deposit return, a fee deduction, a failed return and the resulting reports. Confirm how the security component is classified. A system that can issue a ticket refund hasn't necessarily demonstrated the separate deposit process you need.

Keep credits, transfers and old balances explicit

An exhibitor may ask to carry the deposit into next year's event. That can be convenient when both parties genuinely agree and the arrangement is permitted. Preserve the original settlement, identify the amount transferred and create a linked balance against the new booking. A transfer changes which obligation the money supports; it doesn't create fresh sales or another cash receipt.

As a separate alternative to returning a deposit, suppose the fair carries $200 forward. The old event's deposit register can show a $200 authorized transfer out and the next event a $200 transfer in. At company level, the amount still owed hasn't disappeared. Don't count both records as two separate cash collections, and don't release the funding just because the old event's balance is zero.

A credit toward a future stand fee needs a different instruction from security carried forward. Establish whether the payer has agreed to apply the amount to a specific service and how cancellation or repayment rights change. Finance can then assess the accounting. Moving a number into the next event's revenue column without agreement doesn't complete that decision.

Avoid treating silence as permission. A payer who hasn't replied to your bank-details request hasn't necessarily surrendered the money. An old balance needs continued follow-up and a legal assessment where relevant, including any rules for unclaimed property or dormant obligations. Don't copy another organizer's write-off deadline into your policy and assume it applies to your business.

Also keep deposits you paid to suppliers out of this register's repayment total. They belong in a separate record of money potentially due back to you. You can show both in a company cash forecast, with realistic dates, but don't offset unrelated counterparties to make the exposure look smaller. A venue owes you money on its own terms; your exhibitors are owed money on theirs.

Fix deposits that were already recorded as sales

You may be reading this after collection has started. Perhaps your bookkeeper received one payout total and posted it to event sales, or the team sold a combined stand-and-security package without splitting the report. Fix the records from the original payments. Don't start by subtracting an approximate deposits figure from this month's revenue and hoping the balance is right.

First, identify every relevant booking and retrieve its accepted terms. Separate actual security collected from stand installments, failed payments, uncaptured authorizations and amounts already returned. Match the total to payment and settlement evidence. If an exhibitor made two payments, preserve both. If the purpose of a payment is unclear, flag it for investigation rather than deciding from its amount alone.

Give finance that reconstructed detail and the entries already made. They can determine the correction required, including any effect on an earlier reporting period or tax return. Keep the correction reference against the register. An accounting adjustment changes the classification; it doesn't move money back into the bank if the business has already spent it.

Next, check the funding shortfall. Suppose a separate hypothetical event should be holding $2,000 for refundable security but has only $1,300 available for that purpose. It needs another $700 to fund the full balance, before considering any other obligations. That's a funding problem even after every accounting entry has been corrected. Don't conceal it by assuming some exhibitors will forget to claim.

Name who will provide the money, when it will arrive and which return deadlines it must meet. If you cannot meet an obligation, get appropriate financial and legal advice promptly and communicate through the agreed process. A new deposit sale doesn't resolve the old event's underlying shortfall. It adds new people who may also need their money back.

Once corrected, explain the change to anyone using the event result. A lower sales total after reclassification doesn't mean ticket demand suddenly fell. It means the earlier report included money that wasn't earned sales. Preserve the earlier version, record the correction and use the corrected basis for the next budget. Otherwise, next year's target will inherit the same mistake.

Test cancellation and handover before launch

A deposit process should work when the fair goes ahead and when it doesn't. Before opening collections, walk through cancellation with the person managing payments. Identify who can stop new collections, who decides what each payer is owed and which costs the business must fund separately. Don't assume the inspection-based return date still makes sense when no exhibitor ever loads in.

In the main fair example, assume cancellation before delivery requires all security to be returned under the accepted terms and applicable rights. That means funding the full $4,000 without relying on damage deductions that never arose. Stand fees have their own cancellation treatment and may create additional refunds. The security total alone is therefore only part of the cancellation cash requirement.

Use the same care for a smaller change. If an exhibitor reduces a booking, check whether the agreed security requirement changes and whether any excess becomes returnable now. Record the amendment, approved amount and payment outcome. Don't leave an overpayment unresolved until the event merely because your spreadsheet only has one final return date.

Run a staff handover test too. Ask someone outside the original conversation to open one deposit record and explain the amount held, return condition, deadline and next action. Let them find the accepted terms and original payment without help. If they can't, improve the record while the people who know the answer are still available.

Finally, test access. Someone must be able to issue an approved return if the usual finance contact is away after the event. Use named access and the provider's supported permissions, with an appropriate second check for unusual payments. Shared passwords and an informal promise to send a screenshot later leave the next person unable to establish what actually happened.

Copy a settlement record your team can actually use

Here's a compact record for the fictional DEP-017 case. Adapt the fields to your agreement and system rather than treating the sample as contract wording. Its purpose is to make a payment history understandable to someone who wasn't present at handback.

• Event: ticketed design fair, spring edition.

• Booking: exhibitor EX-017; payer matched to the original transaction.

• Security received: $200; original payment and settlement references attached.

• Basis: refundable exhibitor security under the accepted terms version.

• Assessment: $50 additional cleaning, evidence and contractual basis attached.

• Decision: accepted application of $50, with named approval and date.

• Return: $150 through the original supported payment route.

• Payment outcome: verified completed under the team's provider-status process.

• Closing security balance: zero; related charge and return references retained.

For the failed $200 return, the final lines would look different. Record the attempted payment, its failure status, the funding position, the contact made and the next action date. Keep the $200 unresolved until a valid resolution is verified. Don't copy the completed case's zero simply because both returns were submitted in the same batch.

Then prepare a short event summary from the detail. In our example after the first final return completes, total security collected remains $4,000. Completed returns are $3,650, accepted applications remain $150 and the unresolved balance is $200. Those three outcomes account for the original collection without changing its history.

Close the obligation before releasing its funding

Closing the event programme and closing the deposit process can happen on different days. Keep someone responsible until the remaining cases are resolved and the accounting agrees. Mark the event's deposit report provisional while a material refund, deduction or transfer is still uncertain.

For our final failed return, suppose the original attempt is confirmed unsuccessful and the $200 is available again. A verified replacement payment then completes. Total completed returns become $3,850. Together with the accepted $150 of applications, that resolves the $4,000 collected. The deposit register now closes at zero, with the full history preserved.

That doesn't mean the event earned $150 of additional profit. The accepted applications have to reconcile to their underlying charges or recoveries, and related bills may still be payable. It also doesn't erase the original $80 processing cost or any separately incurred replacement-payment cost. Close the deposit process and the P&L using their own complete records.

Before releasing surplus funding, have finance confirm the closing deposit balance, completed payment evidence, valid applications and remaining cash commitments. If a question remains, name it and assign the next action. For the next event, keep the same separation at collection so nobody has to reconstruct it from the bank after the money has been spent.