Event refund request administration
Three delegates have emailed asking for a refund, and each message went to a different person.
The short answer
Refund administration means one place where requests arrive, one log where they are recorded, and one named person who decides against the terms you published. The reply and the payment are then separate, recorded steps.
The terms themselves, and whether a particular refund is owed, are for your committee and, where there is doubt, your legal adviser. This page covers the handling, not the entitlement.
Start from the terms you already published
Find the cancellation and transfer wording on the registration page, the confirmation email and any contract. If the three differ, note that before you answer anyone and ask your adviser which governs.
Decisions that depend on judgement, such as illness, visa problems or a speaker change, need an owner and a rule written before the first request arrives.
A handling sequence
- Publish one address or form for requests and forward anything sent elsewhere to it the same day.
- Log each request with date received, requester, registration or invoice reference, amount paid, reason and the date of the request relative to any published cut-off.
- Acknowledge receipt with a standard message that says who will decide and by when, without promising an outcome.
- The named decision owner records approve, partly approve, decline or refer, with the clause or reason relied on.
- Finance pays only from the log entry, to the verified original payer or account, and records the payment date and reference.
- Send the outcome message and close the entry. Keep the log for the final reconciliation.
Refund, credit or transfer
| Outcome | What to record | Who needs to know |
|---|---|---|
| Refund to payer | Amount, method, date paid, reference | Requester, finance |
| Transfer to another delegate | New name, any difference in fee, confirmation sent | Registration desk, requester |
| Credit for a future event | Amount, expiry stated in writing, who holds it | Requester, finance |
| Declined | Reason and clause relied on, date told | Requester, committee if disputed |
Points to check with a finance or legal adviser
- Whether the published terms allow the refund being requested.
- Whether payment-processor fees or taxes affect the amount returned.
- How a refund is handled in your accounts, and whether any records must be kept for a set period.
- What to do with a request that arrives long after the event or from someone other than the payer.
Worked example · Fictional example
Cancellations before a one-day seminar
Fictional organisation and illustrative figures only.
A fictional professional-learning team receives 11 refund requests across two weeks. Four arrive before the published cut-off, five after it, and two ask for a transfer to a colleague.
Because every request is logged with its date, the decision owner can show that the four early requests were treated alike. The five late requests are referred to the committee with a note on the clause, and the committee decides case by case. The two transfers are completed without any payment. Finance pays from the log only.
Use this yourself
Refund request log and standard replies
Use one row per request. Copy the reply lines into your email template and adjust the bracketed parts.
- Log columns: request no. / date received / requester / registration or invoice ref / amount paid / reason / date relative to cut-off / owner / decision / clause relied on / date told / payment date and reference / closed.
- Acknowledgement: We received your request on [date]. [Name] will decide against the published terms and reply by [date].
- Approved: Your refund of [amount] will be paid to the original payer account on [date]. Please reply if the details on your registration have changed.
- Declined: We have reviewed your request against [clause or reason]. The outcome is that [decision]. Please reply if you have information we have not seen.
- Transfer: Your place is now held by [new name]. No payment is due or returned unless stated here: [detail].
Handle it in-house, or bring in help?
Your team can usually handle this when
- Few requests are expected and one person holds the terms and the mailbox.
- Terms are clear and the same on every document.
- Finance already pays against a written approval.
Outside planning help earns its fee when
- Terms differ between documents, or a large cancellation wave is likely.
- Requests arrive from delegates, suppliers and sponsors at once.
- Nobody is clearly allowed to decide exceptions.
Need refunds handled consistently?
A conference project lead can set up the request route and log, draft the standard replies for your approval, bring exceptions to your decision owner and keep finance paying only from recorded decisions. Entitlement questions go to your legal or finance adviser.
Questions organisers ask
Who should decide a refund request?
A named person or small group agreed in advance, using the published terms. Avoid deciding case by case in a chat thread.
Can we refund to a different account from the one that paid?
Treat that as an exception that needs a second check. Verify the request independently and confirm with your finance adviser before paying.
Should we answer within a set time?
Say in the acknowledgement when the requester will hear back, and meet that date. Choose a period your team can keep.
Is a credit the same as a refund?
No. A credit stays with the organiser. Put the terms in writing, including any expiry, and ask your adviser how it is recorded.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.