Event Cancellation and Ticket Refund Checks: A Practical Guide by Role

Cancelling an event or invalidating a ticket does not prove that the buyer has received a refund. Check results by payment method and assign someone to resolve failed orders.

Author: EVENTODIT Editorial Team
Published: 2026-10-23T10:09:09+09:00
Updated: 2026-10-24T13:27:14Z
Original URL: https://eventodit.com/en/stories/event-cancellation-ticket-refund-state-reconciliation.html

Practical summary

Key decision: Check ticket status and actual refund outcomes for each order, and assign failed transactions for follow-up.

Responsible roles / intended readers: Ticketing, customer service, accounting and event leads

Record / next task: Order ledger by payment route, cancellation notices, refund outcomes and failed-transaction follow-up records

Basis of information: Official operational guidance and help documents. Handover and approval procedures in the article are editorial application proposals.

Editorial review: 2026-10-23

Part 1. Event and Operations Lead

**"Check the sequence for changing status, notifying attendees and issuing refunds, and obtain approval."**

- Confirm the cancellation steps and platform-specific sequence: Once cancellation is decided, make sure sales and event status changes, attendee notices and order refunds are each completed. Eventbrite advises changing the event to cancelled, notifying attendees and refunding orders; if its email feature is used, send the notice before refunds and confirm its dispatch status. Refunding while messages are queued may prevent some from being sent. For another ticketing provider, check its current guidance and contract procedures.
- Confirm the decision and notice recipients: Record the cancellation decision time and official notice audience. Before release, compare the procedures and contact routes in the booking page, notice email and customer-service guidance.
- Reconcile and approve before bulk refunds: Whether a bulk refund can be stopped or reversed depends on the platform. Before execution, the final approver should cross-check the event name, order count, total refund, reason and permitted processing scope against the order ledger and platform conditions.
- Establish domestic contract terms and fee responsibility: Do not apply an overseas platform's rules directly to a Korean event. Review the ticketing contract and applicable consumer requirements to establish whether fees are included and who bears them for the cancellation reason.

Eventbrite's cancellation guidance says a bulk refund cannot be stopped or reversed once started. This is a platform-specific procedure; check other providers' functions and conditions separately.

Part 2. Ticketing and Booking Management

**"An invalid ticket does not mean money has been returned. Track each payment method through its final status."**

- Stop sales and preserve the order ledger: Stop ticket sales as soon as cancellation is decided and securely preserve a separate complete order ledger for each payment route.
- Separate online and offline payment orders: Distinguish the actual refund route for online cards from cash and bank-transfer receipts. For orders recorded as offline payments on Eventbrite, processing a refund in the platform invalidates the ticket but does not return funds to the buyer; place these on a separate repayment list. For separate payment routes such as PayPal and for other platforms, confirm how the actual payment and order are handled.
- Cancel complimentary invitations and revoke access: Check cancellation of free invitation orders as well as paid tickets, and update the final invitation list and venue admission permissions.
- Check every order status rather than relying on a completion notice: Do not report a system completion notice as proof that all refunds succeeded. After bulk processing, review each order's status and identify failed refunds.
- Assign failed orders and prevent duplicate returns: Record the failure reason and the person responsible for retrying. Before another attempt, check the previous request's final result to avoid a duplicate return through the card issuer or bank.

| Order type | Platform status to check | Separate record to confirm |
| --- | --- | --- |
| Online payment | Refund requested, in progress, successful or failed | Original payment method, amount and transaction reference |
| Offline receipt | Ticket invalidation and order cancellation | Actual return of funds and reconciliation with receipts |
| Complimentary invitation | Free order cancellation | Invitation list and admission entitlement updated |

Part 3. Customer Service and Accounting

**"Distinguish the platform response deadline from actual repayment, and reconcile each receipt."**

- Keep communications consistent and record dispatch: Conflicting refund procedures, timeframes or contacts on the booking page, individual emails and customer-service guidance cause confusion. Compare versions and record dispatch status and failures against each order.
- Explain processing separately from payment-provider posting: Eventbrite's organiser refund policy sets an initial response deadline of no more than five business days. That is the platform's response condition, not the date by which money reaches the attendee's account. Explain receipt, approval and execution, and card-issuer or bank posting separately, and provide the enquiry timing for the provider in use.
- Return and reconcile offline receipts: For orders paid by bank transfer or cash, confirm the applicable repayment route and contract, arrange the actual return, reconcile each return with the receipt ledger and retain evidence.
- Close the refund report and assign outstanding orders: At closeout, list successful and outstanding orders by payment method and ensure each unresolved order has a named owner so attendees are not left without a response.

The Eventbrite figures and functions discussed here are that platform's public conditions. For a Korean event, review the ticketing contract and applicable consumer requirements separately.

Practical workflow · Timeline

From cancellation to refund confirmation

Decision — Stop sales and preserve orders
  Confirm the event and lists by payment route
Notice — Explain the process to visitors
  Check messaging conditions and record notices
Execution — Process refunds and ticket status
  Separate online, offline and complimentary orders
Reconciliation — Resolve failed transactions
  Check final order results and actual fund returns

Note: Confirm the platform's current contract and procedures before issuing refunds.

**Final check before use:** Before closing the cancellation and refund process, check that actual fund returns by payment method and follow-up owners for failed transactions have been reconciled without omission.

Application conditions

For cancellations involving paid, complimentary and offline-payment orders. Distinguish overseas platform procedures from Korean requirements.

Unconfirmed information

Refund functions, fees and card-processing times at a particular Korean ticketing service have not been verified.

Sources

Eventbrite — Cancel your event: cancelled status, visitor messages, order refunds and failed transactions. Checked 2026.10.23.
https://www.eventbrite.co.uk/help/en-gb/articles/895183/how-to-cancel-an-event/

Eventbrite — Issue a full or partial refund: distinction between invalidating tickets and returning funds for offline payments. Checked 2026.10.23.
https://www.eventbrite.com/help/en-us/articles/158301/how-to-refund-an-order/

Eventbrite — Organizer Refund Policy Requirements: platform conditions for cancellation refunds and initial responses. Checked 2026.10.23.
https://www.eventbrite.com/help/en-us/articles/827759/eventbrites-organizer-refund-policy-requirements/