If your finance team goes quiet and slightly grey every time an event wraps, event ticket sales reconciliation is almost certainly the reason. Reconciliation is the unglamorous job of matching what you sold against what actually landed in your bank account, and for most organisers it is a manual, spreadsheet-heavy slog that eats days. The short version of the fix: the fewer hands your money passes through before it reaches you, the easier reconciliation becomes. This guide explains why event money is so painful to reconcile and how to make the numbers agree without a fortnight of detective work.
Quick answer first. Event reconciliation is hard because ticket platforms that hold your money pay you a single net lump sum days after the event, with fees, refunds, chargebacks and reserves already blended in and invisible. To fix it, you want each sale to arrive in your own account as its own line, with fees itemised, so your bank statement reads like your sales report instead of arguing with it.
Why event ticket sales reconciliation is a special kind of misery
Reconciliation in theory is simple: money out of the customer should equal money into your account, minus known fees. In practice, payouts rarely arrive as clean one-to-one matches. They are batched across many buyers, split across payment methods, adjusted for fees and currency, and sometimes delayed or clawed back (Rexi). So the tidy figure your ticketing dashboard shows on the night is not the figure that turns up in your bank, and the gap between them is what your finance team has to explain.
The fees are the worst offender. Processor fees, platform fees and bank charges are each deducted at different points in the payout chain, and every one has to be matched against the right line in your ledger. If the fee the processor actually charged differs by even a few pence from the fee you recorded, the net payout will not match and the difference surfaces as an unmatched break that somebody has to chase (Rexi). Multiply that by a few hundred tickets and a handful of refunds and you have a very long afternoon.
The number on your ticketing dashboard and the number in your bank account are rarely the same number, and reconciliation is the tax you pay for that gap.
The real villain: the merchant-of-record model
Here is the structural problem. Many big ticketing platforms act as the merchant of record. They collect the buyer's money into their account, hold it, deduct their fees, and pay you a net amount days after the event. That means the cash never touches your bank until the platform decides to release it, and when it does, it arrives as one blended lump with the detail stripped out.
Take Eventbrite as the familiar example. Organiser fees run at 3.7% plus $1.79 service per paid ticket, plus 2.9% payment processing (Eventbrite), and the final payout typically lands around three business days after your event, with a reserve sometimes held back against refunds and chargebacks. So your finance team is not reconciling one sale at a time. They are reconciling a single net deposit against hundreds of gross sales, then reverse-engineering which fees, refunds and holds account for the difference. That is the manual export nightmare in a nutshell.
Reconciliation should be a glance at two matching numbers, not a forensic audit of one blended payout. Credit: Lukas Blazek / Unsplash
Two models, two very different month-ends
The alternative is the own-processor model, where payments run through your own Stripe (or equivalent) account. The buyer pays, and the money lands directly in your account at the moment of purchase, each transaction visible as its own line with its own fee attached. Nobody holds it, nobody blends it, and nobody decides when you get it. The table below shows what that difference does to reconciliation.
| What happens | Merchant-of-record platform | Own payment account |
|---|---|---|
| Where the money first lands | The platform's account | Your account, at purchase |
| When you get paid | Days after the event, often with a reserve held | As sales happen |
| How it arrives | One net lump sum for the whole event | Line by line, per transaction |
| Fee visibility | Blended into the payout, itemised separately at best | Attached to each transaction |
| Reconciliation job | Reverse-engineer one deposit against hundreds of sales | Match your sales report to your bank feed |
When payments hit your own account, your bank feed and your sales report describe the same events in the same order. Reconciliation stops being an investigation and becomes a tick-and-flick. That is the whole game: you are not eliminating fees, you are making them legible.
How to fix event reconciliation (without changing your accountant)
Whether or not you can move off a held-money platform tomorrow, these steps cut the pain considerably.
Pull the settlement report, not just the sales report. Every marketplace, cart and processor can produce a settlement file showing payout date, gross sales, fees, reserves, refunds, chargebacks and net. That file, not your dashboard, is what reconciles to your bank.
Reconcile to the payout, then within the payout. First match each bank deposit to a payout batch, then break that batch down into its gross, fees and adjustments. Doing it in that order stops you hunting a single missing pound across the whole event.
Record fees as their own ledger line. If platform fees, processing fees and refunds each have a dedicated account, an unmatched break tells you exactly which category is off instead of just that something is.
Track refunds and chargebacks separately. These are the classic reason a payout undershoots your sales figure. Log them as they happen so month-end is not the first time you see them.
Shorten the chain. The single biggest lever is how many parties touch your money before you do. Payments into your own account remove the held-lump-sum step entirely, which is why own-processor platforms are so much easier to reconcile.
The hidden hours nobody puts on the invoice
There is a cost to reconciliation that never shows up on any platform's pricing page: the days your finance team spends doing it. A held-money payout that blends hundreds of sales, dozens of fees and a handful of refunds into one deposit does not reconcile itself. Someone exports the settlement file, someone cross-checks it against the sales report, someone hunts the stray few pounds that will not tie out, and someone signs it off. On a busy event calendar that is not an afternoon a month, it is a recurring drain on your most expensive people.
It also carries a risk cost. The longer and more manual the process, the easier it is for an error to slip through unnoticed, whether that is a refund counted twice, a chargeback missed, or a fee misfiled to the wrong account. Errors in reconciliation are not just annoying, they quietly distort the numbers you use to decide whether an event made money at all. Shrinking the process from a forensic reconstruction to a straightforward match does not only save hours, it makes the figures you report more trustworthy, which is the entire point of doing reconciliation in the first place.
What a reconciliation-friendly platform looks like
Judge a ticketing platform on a simple test: after an event, can your finance team match the money without a spreadsheet full of manual adjustments? That points to a few concrete features. Payments should flow through your own account so cash arrives per transaction, not as a delayed lump. Fees should be itemised, not blended. Refunds and chargebacks should be visible against the original sale. And the export should reconcile cleanly to your bank feed rather than needing a translation layer.
eventcloud is built this way: payments run through your own Stripe account, so the money lands as each ticket sells and every transaction reconciles line by line, on a flat $125 per user per month with no per-ticket cut to unpick afterwards. To be fair about trade-offs, if you run one tiny free event a year, reconciliation is barely a chore and the held-money model also quietly outsources your refund and chargeback risk, which has real value for the occasional organiser. But if you run events regularly and your finance team keeps losing days to it, the fix is structural, not a better spreadsheet.
For more on the cash-flow side of the same problem, see why your event platform should never be holding your money. Reconciliation gets easy the moment your bank statement and your sales report finally start telling the same story.
