How do finance teams reconcile ticketing transactions?
Ticketing revenue, payment transactions, settlement balances and bank payouts represent different stages of the financial process. A £100 ticket order is not necessarily a £100 bank deposit. Taxes, booking fees, payment fees, refunds, chargebacks, reserves and delayed payouts can all change timing or amounts.
Why do ticketing sales and bank deposits differ?
A ticket can also be reserved or invoiced before it is paid. Finance teams should separate the order ledger, payment-provider balance activity and bank movement rather than comparing two summary dashboards.
What is the reconciliation chain?
Use unique identifiers across systems and preserve original currency amounts as well as converted amounts. A payout may combine multiple event orders, and a refund today can adjust a payout relating to different dates.
What should teams investigate?
Look for orders marked paid without a matching captured payment, captured payments missing orders, duplicate settlement records, unknown fees, partial refunds, reversed chargebacks and unmatched bank deposits. Distinguish expected timing differences from real missing money.
For example, ten £50 orders generate £500 gross sales. If payment fees total £15 and one £50 refund is settled before payout, a simplified payout could be £435. That illustrative number excludes tax, other fees and any reserve; it is not an accounting prescription.
How should controls be designed?
Reconcile daily during active onsales and formally at event close. Assign exception owners, preserve immutable source transactions and audit manual adjustments. Document who is merchant of record and who is entitled to each fee line before choosing account mappings.
Bottom line: finance needs an order-to-payment-to-payout trail with explained differences, not a dashboard that assumes gross sales equal cash.