Skip to main content

Understand your booking statements

In this article you will find an overview of the booking statement and it's different tabs.

Updated over a week ago

Booking Statements: What They Are and How to Use Them

Booking Statements are payout summaries sent by Smeetz. They help you:

  • Reconcile payments received

  • Understand which fees were deducted

  • Track customer balances and cash flow

They act as both:

  • Proof of payout (what Smeetz paid to your account)

  • Invoice for Smeetz fees

You can receive Booking Statements daily, weekly, or monthly, depending on your payout settings.

💡 Important: Booking Statements are not for sales or accounting analysis. Use them only to verify payouts and understand the cash movements between Smeetz and your venue.

Where to find them

  • Go to your Smeetz account

  • Click on your initials (top right)

  • Account Name > Booking Statements

  • Select and download any Global Payout Statement (Excel)

How you receive them

By default, Booking Statements are sent by email every Monday. You can change this frequency by going to:

Your initials > Account details > Booking statement

  • Statements show all sales from the previous period (e.g. week or event), the fees deducted, and the transfer date.

  • The actual payment is made within 15 days of the statement being issued (bank processing times not included).

In addition, once sales for an individual product or event are completed, you’ll receive a sales summary report.

This summary does not trigger a payout; only the main Booking Statement does.

Why Booking Statements Matter

1. Simplified accounting

All sales, fees, and payouts across your products are grouped into one clear document, making reconciliation faster and easier.

2. Easier refund and fund management

With consolidated statements, your payouts go into one account. This ensures you have enough cash to process refunds when needed, without overcomplicating your setup.

3. Less admin

You don’t need to issue credit notes for each event or product. This reduces paperwork, saves time, and lowers the risk of manual errors.

What's Included in a Booking Statement?

📄 1. Cover Page

  • Statement numbern(for reference)

  • Payout dates

  • Your company and bank details

  • Total amount paid

💳 2. Account Page

  • Balance due

  • Payment issued

  • Any provisions

  • Total invoiced fees

Item

Description

Payment on booking statement

The actual payout amount that will be transferred to your bank account.

Invoice on booking statement

The Smeetz fees for this period, invoiced and visible in the "Invoice" section of your account.

🧾 3. Invoice Page

Shows detailed breakdown of all fees, including:

  • Ticketing fees (the online ticketing fees represent the amount of payments without reimbursements)

  • Payment processing fees (the payment fees represent the amounts of payments, including reimbursements)

  • Marketplace fees (Viator, GetYourGuide, etc.)

  • VAT on fees (if applicable)

🎟️ 4. Sales Page

Breaks down revenue per product:

  • Ticket name

  • Quantity sold, cancelled, scanned

  • Revenue generated

  • Validity dates

  • Deductions & customer balance

Understanding the Booking Statement Balance

Total sales during the payout period
– Customer balance (unpaid bookings)
– Sales not processed through Smeetz Pay (e.g. cash or external terminals)
= Final payout (Booking Statement Balance) including Smeetz fees

⚠️ Some rounding differences may apply, especially with fee percentages.

Item

Description

Total sales

Total value of bookings made in the period.

Customer balance

Deduction due to unsettled payments by customers. These may appear in a future statement once resolved. No fees are withheld on these amounts.

Organiser (non-Smeetz sales)

Sales made outside the Smeetz platform (e.g. cash, bank transfers). No fees are applied to these transactions.

Total deductions

Total of customer balance + external sales

Booking statement balance

This is the net amount used to calculate Smeetz fees and determine your payout.

💰 5. Accounting Page

Raw data at the transaction level:

  • Date, ticket ID, value

  • Payment method (e.g. cash, Smeetz Pay)

  • Type: sale, refund, discount

  • Status: completed, pending, cancelled

📌 6. Provision Page

[To be completed, if applicable to your setup]

Common questions and sources of errors

Why your Booking Statement may show a balance

It’s normal for your Booking Statement to display a balance due by the customer or a delayed payout. This typically happens for one of two reasons:

1. IC++ payment model

If you have the IC++ pricing structure through Adyen, this means that fees (like interchange, scheme, and processing fees) are applied after the payment is initiated. Because of this:

  • The full payment may not be confirmed at the time the Booking Statement is generated

  • Final settlement may occur a few days later, once all fees are calculated and deducted

2. Delayed payment confirmation

Some transactions, particularly those involving certain card types or external factors (e.g. weekends, holidays), take longer to process. These will appear as pending in the Booking Statement and are reflected in the customer balance.

👉 These pending amounts will be included and adjusted in your next Booking Statement, once payment has been fully processed by the provider.

Why the “accounting summary” and “booking statements” can vary

The Accounting Summary shows business performance within a set timeframe, while Booking Statements focus on financial movements when transactions are issued. As a result, amounts on Booking Statements and the Accounting Summary may differ due to payment processing times between entities.

  • When comparing the sales data in Booking Statements with the total amounts in the Turnover Report from the accounting summary, differences may arise due to factors such as:

    • Date filters,

    • Unsynchronised bookings from the POS,

    • Negative booking statements,

    • Delayed payment validation by our payment provider.

  • Any discrepancies will be corrected in future statements.

Did this answer your question?