Start with payments actually received
Use successful payments as your basis and keep test orders separate. Take amounts from your payment and sales records. A reservation or pending payment is not money received. Check the payment route too: does the organiser collect directly in their own provider account, or does TixBeam collect and settle later? This determines who still needs to transfer what.
The calculator uses fictional figures and does not connect to payment or accounting records.
Separate refunds from charges
A refunded ticket reduces proceeds. Transaction charges may remain; check actual provider costs. In this example, TixBeam fees are reversed for fully refunded tickets. The demo uses €0.30 including VAT per remaining paid ticket as a rounded example. Actual settlements follow recorded amounts and agreements.
Ticket price here means the total received per ticket, including any service fees passed on to buyers.
Allow for reserves and earlier payouts
Keep a reserve separate for possible obligations. Subtract amounts already paid to the organiser so the same balance is not released twice. Refunds, disputes, additional costs and earlier transfers may change the amount available. A negative result is a shortfall to investigate, not an amount to pay out.
Review every release deliberately. The calculator cannot transfer funds or release a reserve.
Close with a traceable overview
Reconcile the event settlement with orders and provider records. A settlement is not a VAT invoice and the calculated balance is not profit. Account separately for other event costs and tax treatment. With direct collection, proceeds are already with the organiser; with TixBeam collection, check the remaining obligation before paying out.
Confirm the period, payment route and earlier payouts included in every settlement.