Reconcile Tournament Entry Payments and Track Authorized Refunds
A practical workflow for tournament organizers: match entry charges to payment records, investigate discrepancies, and document refund authorization and completion.
Contents
Give every entry its own row with its authorized charge. Link each payment transaction to the entry it pays for, then subtract to find any difference. Investigate every nonzero difference before treating it as unpaid. Keep refunds on a separate tracker that records each stage: request, authorization, submission and confirmed completion. A refund is closed only when transaction evidence shows it went through.
This guide covers the organizer's bookkeeping. Whether a player is owed a refund depends on your event's published policy, any governing-body or venue terms that apply to your tournament, and your payment provider's rules. The worksheet records and applies those decisions. It does not make them.
Set up the reconciliation worksheet
A single shared worksheet with these columns lets any volunteer see what each entry owes, what has been received and what still needs attention:
| Column | What goes in it |
| Entry ID | Your unique identifier for the registration |
| Charge reference | The fee line or invoice the entry was billed under |
| Authorized charge or adjustment | The amount the entry owes, plus any approved changes to it |
| Currency | The currency of the charge |
| Payment transaction reference | The provider's ID for the payment |
| Recorded payment | The amount on that transaction |
| Allocation to entry | How much of that transaction applies to this entry |
| Discrepancy | Authorized charge minus allocated payments |
| Reviewer | The person checking the row |
| Next action | What happens next, such as "check provider status" or "contact player" |
Real payments rarely line up one-to-one with entries. One player may pay in two installments. A club captain may pay for several entries in a single transaction. Give each transaction its own row and use the allocation column to tie each portion to a specific entry. Don't merge transactions into one total, because that hides which payment covers which entry.
Work through each entry
- 1. Choose a comparison date. Your entry list and your payment export should cover the same period, so that payments arriving after the cutoff don't look like gaps.
- 2. List every entry with its authorized charge, and record any approved adjustment as its own line instead of overwriting the original amount.
- 3. Export payment records from your provider and enter each transaction on its own row, with its reference number.
- 4. Allocate each transaction to the entry or entries it pays for.
- 5. For each entry, subtract the allocated payments from the authorized charge.
- 6. Flag any entry with a nonzero result, assign a reviewer and write down the next action.
- 7. Keep each currency in its own column or group. Never add amounts in different currencies together.
Investigate a discrepancy before assuming nonpayment
Illustrative example: an entry has an authorized charge of 40 units and two allocated payments of 25 and 10 units. The calculation 40 − 25 − 10 = 5 leaves a five-unit difference. Flag the entry for review instead of marking the player as owing money, because the gap may come from a bookkeeping issue on your side.
- Check these before contacting the player:
- Adjustments: was a discount, fee change or partial waiver approved but not recorded against the entry?
- Allocations: was part of a combined payment assigned to the wrong entry, or not assigned at all?
- Transaction status: is a payment still pending, failed or reversed at the provider?
- Duplicates: does the same transaction appear twice, or does the same entry appear under two IDs?
Write what you found in the next-action column. Once the cause is resolved, record the correcting adjustment or allocation so the discrepancy reaches zero and the reason stays visible.
Track refunds on a separate tracker
Refunds pass through several stages and the amount can change along the way, so give them their own log rather than adding them to the payment worksheet:
| Column | What goes in it |
| Entry ID | Links the refund to the original entry |
| Request | What the player asked for, and when |
| Policy or decision reference | The policy clause or recorded decision that justifies the refund |
| Authorized amount | The amount approved, which may differ from the amount requested |
| Approving person | Who signed off |
| Provider reference | The refund transaction ID from your payment provider |
| Submitted date | When the refund was issued |
| Recorded status | Current state, such as requested, authorized, submitted or confirmed |
| Completion evidence | What shows the refund went through |
| Follow-up owner | Who chases it if it stalls |
Track four amounts separately: requested, authorized, submitted and confirmed. A player may request a full refund while your policy authorizes only part of it. A refund may also be submitted but not yet confirmed. Merging these amounts causes most refund confusion. Decide in advance who is allowed to approve refunds, and record that person's name on every row.
Process the refund in your platform
Tournament Software's support instructions for its Online Tournament Planner describe this sequence: select Payments, open "To be refunded", select the player and confirm the refund. Those steps assume the player is already entitled to the refund. The software carries out a refund you have decided on. It does not decide eligibility or set your event's policy. Platform interfaces change, so check your provider's current instructions before processing. Then enter the provider reference and submitted date on the tracker.
Close refunds on evidence, not elapsed time
Mark a refund confirmed only when the transaction record shows it completed. Don't assume a refund is finished because some time has passed since you submitted it. If a refund stays submitted without confirmation, the follow-up owner checks the provider record and logs the result.
Hand verified totals to the event budget
After discrepancies are resolved and refunds are confirmed, send aggregate figures to whoever maintains the event budget: total collected, total refunded and anything still open. Report each currency separately. Sending only verified totals keeps the budget from counting pending payments as income or authorized refunds as money already paid out.
Related articles
Document Tournament Division Eligibility and Entrant Assignment
A practical, rule-linked process for amateur tournament organizers to document division criteria, review entrant information, assign divisions and handle exceptions consistently.
Plan Consolation and Placement Match Eligibility and Timing
Decide whether to add placement or consolation matches, set who is eligible and what each result is worth, and schedule matches that depend on earlier results.
Assign Mixed Ability Teams and Document Exceptions
A practical method for community tournament organizers to balance mixed ability teams: collect comparable ratings, apply roster constraints, distribute players and log every exception.
Plan, Observe and Record a Tournament Draw
A practical procedure for running a transparent tournament draw: declare allocation rules in advance, have the draw observed, and keep a step-by-step record that preserves any corrections.
Plan Ladder League Challenges, Rankings and Administration
A practical guide to setting challenge eligibility, ranking movement, round schedules, match records and dated ladder revisions for an amateur ladder league.
Review and Correct Tournament Registration Records
A practical workflow for tournament organizers to flag wrong-event entries and possible duplicate teams, confirm corrections and keep a clear review trail.
Manage Tournament Withdrawals and Schedule Changes
A practical organizer workflow for handling a team or player withdrawal: record the request, protect completed results, review affected fixtures and publish an approved, versioned schedule.
Tournament Tie-Break Rules: How to Write a Clear Head-to-Head Points Policy
Write a clear standings tiebreak policy for your amateur tournament: how head-to-head points work, when to use them, worked examples and a fill-in template.
Amateur Tournament Registration Form Planner
Plan a sports registration form PDF for an amateur tournament: core entry fields, divisions, golf examples, deadlines, confirmations and what to verify.
Game Schedule Calculator: How to Turn a Match List into a Court-and-Time Plan
Calculate time slots, event length and court assignments from your match list, then check the plan for double-booked teams, courts and missing rest.