Reconcile event ticket refunds after postponement or cancellation

A postponed event can leave sold tickets, voluntary refunds, chargebacks, and transferred admissions in the same platform account. The processor balance alone does not identify the remaining obligation to ticket holders.

A workable event ticket refund liabilities schedule names the entity, period, currency, source systems, cutoff, preparer, and reviewer. It also records the report filters and extraction time. Those details let the next reviewer reproduce the work instead of trusting an unexplained total.

Export the complete in-scope population before sorting or filtering it. Save a read-only copy with its row count and control total. Compare it with the prior open-item list, then note missing locations, accounts, customers, vendors, or transactions in the exception log.

Corrections belong in the reconciliation, not in the original export. Keep the received file intact and show every mapping or classification change on a separate line.

Collect the ticket-platform export, event status log, refund policy, processor transaction, chargeback file, settlement statement, and liability ledger. Give each record a stable reference. Capture the source, date, amount, currency, status, and responsible owner. If a document is missing, say so plainly and keep the item open. An estimate or private-message screenshot does not become source evidence merely because the deadline is close.

Begin with the last reviewed position. Put additions, applications, releases, refunds, credits, reversals, and corrections on separate lines. Tie the calculated ending position to the current ledger or operating report. Investigate offsetting differences rather than allowing a net zero to clear them.

Use specific labels such as missing record, timing difference, amount mismatch, duplicate, stale item, or judgment question. Every exception needs an owner, requested action, due date, age, known financial effect, and evidence reference. Close it only when the stated record or approval arrives.

The preparer can compare observed fields, check arithmetic, and draft a focused question. The preparer should not decide refund eligibility, revenue treatment, customer remedies, and abandoned balances. Route that decision to the event finance owner, include the amount and deadline, and retain the answer with the workpaper.

Trace selected source records into the schedule and selected schedule lines back to their source. Reperform large entries, manual adjustments, old exceptions, and changes made after the first review. Record the observed mismatch before proposing its cause.

Package the untouched exports, reconciliation, evidence index, exception queue, approvals, and a short status note. State what tied, what remains open, who owns the next action, and which decisions still await review. The file should stand on its own when another person opens it next month.