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.

5 min readTournament desk1 viewsReconcile Tournament Entry Payments and Track Authorized Refunds
— · 0 votes
Contents
  1. Set up the reconciliation worksheet
  2. Work through each entry
  3. Investigate a discrepancy before assuming nonpayment
  4. Track refunds on a separate tracker
  5. Process the refund in your platform
  6. Close refunds on evidence, not elapsed time
  7. Hand verified totals to the event budget

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:

ColumnWhat goes in it
Entry IDYour unique identifier for the registration
Charge referenceThe fee line or invoice the entry was billed under
Authorized charge or adjustmentThe amount the entry owes, plus any approved changes to it
CurrencyThe currency of the charge
Payment transaction referenceThe provider's ID for the payment
Recorded paymentThe amount on that transaction
Allocation to entryHow much of that transaction applies to this entry
DiscrepancyAuthorized charge minus allocated payments
ReviewerThe person checking the row
Next actionWhat 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:

ColumnWhat goes in it
Entry IDLinks the refund to the original entry
RequestWhat the player asked for, and when
Policy or decision referenceThe policy clause or recorded decision that justifies the refund
Authorized amountThe amount approved, which may differ from the amount requested
Approving personWho signed off
Provider referenceThe refund transaction ID from your payment provider
Submitted dateWhen the refund was issued
Recorded statusCurrent state, such as requested, authorized, submitted or confirmed
Completion evidenceWhat shows the refund went through
Follow-up ownerWho 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