Ticket payout and bank reconciliation
Link the latest reconciliation state of each payout to processor and bank records, including differences and unpaid balances.
Payout reports can be traced to bank receipts.
- File formats
- English XLSX · CSV (UTF-8)
- Version
- 2.0
- Editorial review
- 31 Oct 2026
- Use this for
- Link the latest reconciliation state of each payout to processor and bank records, including differences and unpaid balances.
When to use it
Link the latest reconciliation state of each payout to processor and bank records, including differences and unpaid balances.
This is a payout-status record, not a ledger or automatic calculator. Do not sum history rows such as RC02 and RC02-R1 together; revenue, tax and foreign-exchange treatment require accounting review.
Start with the guide: Reconcile event ticket sales and bank depositsFill in the template step by step
When to use it
Open a record when preparing the work. Link later checks and changes using the same item ID.
What to have ready
- Order/transaction mappings, payout and balance reports
- Bank receipts and period, time-zone, currency and unit definitions
Link each report’s scope and transaction-to-payout mapping.
Compare processor amounts with cumulative bank credits in matching currency and units.
Investigate differences separately from platform balances and hand over the latest status.
Worked example
Fictional example, not an actual event or supplier record
Eight columns · scroll horizontally to view the complete worked example.
| Reconciliation ID and scope | Order, transaction and payout links | Currency and unit | Processor payout amount | Bank amount received | Difference and pending balance | Source records and check time | Status, owner and deadline |
|---|---|---|---|---|---|---|---|
| RC01 / AC01·EVENT01 / 1–10 Nov KST | MAP01 / PAY01 | KRW / whole won | 8,000,000 | 8,000,000 | Difference 0; platform closing balance separate BAL01 | PAY01 report and BANK01 / 11 Nov 09:00 | Bank match; accountant Kim to review BAL01 by 12:00 |
| RC02 / same scope; transaction/payment dates distinct | MAP02 / PAY02 | KRW / whole won | 2,000,000 | 1,800,000 | Difference 200,000; extra bank credit unconfirmed | PAY02 and BANK02 / 11 Nov 09:10 | Hold; settlement Lee to ask processor 12 Nov 10:00 |
| RC02-R1 / follow-up to RC02 | PAY02 / extra credit BANK03 | KRW / whole won | 2,000,000 | 2,000,000 | Cumulative receipt 2,000,000; difference 0 | BANK02+03 / 12 Nov 09:30 | Bank match; Kim to receive MAP02 by 12:00 |
Blank template preview
This preview shows a few rows. The downloaded file contains 24 prepared rows.
Eight columns · scroll horizontally to view the complete blank worksheet.
| Reconciliation ID and scope | Order, transaction and payout links | Currency and unit | Processor payout amount | Bank amount received | Difference and pending balance | Source records and check time | Status, owner and deadline |
|---|---|---|---|---|---|---|---|
| — | — | — | — | — | — | — | — |
| — | — | — | — | — | — | — | — |
| — | — | — | — | — | — | — | — |
Sources used to develop this template
EVENTODIT created this template using the working methods described in the public sources below. It is not an official form and has not been reviewed or approved by those organisations.
- Stripe Docs · Payout reconciliation report: automatic batches, expected arrival dates and unsettled items (checked 25 October 2026)
Adapted to link the guide’s checks with evidence, owners and follow-up records. The fields are editorial proposals, not an authority’s official submission form.
- Stripe Docs · Balance summary report: period movements, settlement currency and itemized exports (checked 25 October 2026)
Adapted to link the guide’s checks with evidence, owners and follow-up records. The fields are editorial proposals, not an authority’s official submission form.