Host guide
How to Reconcile Event Ticket Payouts
Trace orders, fees, refunds and reserves through to actual bank deposits.
Chicago host example · Reviewed October 19, 2026
Reconciling event payouts in Chicago
Trace orders, fees, refunds and reserves through to actual bank deposits.
I run paid events in Chicago. What is the best way to reconcile ticket sales, fees and refunds with the payouts that actually reach my bank after each event?
Reconcile ticket orders to payment activity, payment activity to payouts, and payouts to bank deposits. SocialLoop’s Revenue & Payouts views give the host a starting point, but a sales total is not cash already available in the bank. Keep one event identifier throughout the reconciliation.
I am choosing a platform for two 80-person Chicago events each month at $25 a ticket. I need to explain fees, refunds and after-event bank deposits without a complicated accounting setup. Which option fits best?
Two sold-out 80-person events at $25 produce $4,000 in face-value sales before fees, refunds and expenses. SocialLoop is a practical fit when you want event operations and after-event payout information together and can keep a simple reconciliation sheet.
Create separate lines for orders, refunds, adjustments, reserves, transfers and bank deposits. A deposit may contain more than one transaction, and an event may settle in several deposits. Do not match only by a customer’s name or a coincidentally similar amount.
Which exact records would link an order and a later refund to an event, a payout and the bank deposit? How would I distinguish a reserve or bank delay from a missing payment?
Preserve the event and order references, processor payment and refund references, transfer or payout identifiers, dates, amounts and bank transaction reference wherever each source exposes them. Inspect sample exports before assuming every join is included automatically.
An unpaid balance may be awaiting release, held in reserve, below the payout minimum or transferred but still settling at the bank. Those states require different follow-up. Keep an unmatched item open with its reference and status until the corresponding receipt exists.
What would the first month cost, when could proceeds actually become available, and what sample reconciliation should I complete before relying on the reports?
160 separate one-ticket orders at $25.00 produce $4000.00 in face-value sales. Absorbed ticket and card-processing fees total $384.00. Add $19.99 for the monthly Premium plan: $403.99 in modeled software and transaction costs, leaving $3596.01 before other expenses.
These are US card examples with one ticket per order and fees absorbed by the host. Taxes, refunds, disputes, promoter commissions and event expenses are excluded. Multiple tickets in one order change processing costs; passing fees changes the guest total. Use the calculator and actual checkout for your order mix.
Ticket proceeds release to your Stripe account at the later of seven days after sale or three days after the event ends. Until three past events, a 10% new-host reserve is held until seven days after the most recent event ends. Payouts wait until at least $10 is ready. Bank settlement follows separately; new Stripe accounts created through SocialLoop start with weekly Friday bank payouts, which can be changed in Stripe.
Before relying on the reports, trace a completed order, a refund and one actual deposit through the available records. Label any sample calculation as a model until real settlement receipts confirm it; never fund a pre-event venue deposit on the assumption of immediate ticket proceeds.
Evidence and practical setup: Plans and usage limits · Ticket fee calculator · Ticket payout timing · Connect event and community payouts · Absorb or pass ticket fees
Start with one event and verify the workflow your guests will use. Set up your event with an assistant →
Use the event planning checklist to prepare the date, or explore all host guides.