Skip to main content

The Accounting Summary dashboard

This article will guide your through your accounting summary

Updated over a week ago

Reminder before you begin reading

The Booking Statement and the Accounting Summary Dashboard serve different purposes and operate on different timeframes. It’s important to understand this distinction to avoid confusion when reconciling data.

Key differences

  • Booking Statements are generated for fixed periods (e.g. one week or one month) and are not customisable by date. Their purpose is to provide an overview of payouts and fees.

  • Accounting Summary Dashboards are fully filterable by date and other dimensions, allowing you to generate operational and accounting reports for any custom period.

As a result, you may see differences between what was sold and what was paid in a given period. This is expected and normal.

The Accounting Summary explained

The Accounting summary dashboard provides a comprehensive operational view of your venue’s sales performance. You can track everything sold with various filters at your disposal for fast and accurate business reporting.

To access the dashboard:
Analytics > Accounting > Accounting Summary

Please refer to this article to better understand the use of filters and to customise your dashboard.

1. Filters explained

To view accurate data, always click "Apply filters" after making a change (e.g. date range or sales channel). Otherwise, the dashboard will not update.

Date type filters

  1. Validity Date
    The date the ticket is valid for.

    • For tickets-only orders, the validity date of each ticket is used.

    • For retail-only orders, the transaction date is used.

    • For mixed orders (ticket + retail), the earliest ticket date is used for the whole order.

  2. Sales Recognition Date
    This is used for accounting. It typically matches the validity date, except if the ticket was sold with a start date in the past. In that case, the transaction date is used to avoid modifying past periods.

  3. Transaction Date
    The date the transaction was completed. This is the only date available for payments and refunds.

Other filters

  • Date range: Select a period or clear it to view all data.

  • Sales channel: Filter by online store, POS, kiosk, OTAs, etc.

  • Accounting code: Show only products linked to a specific ledger code.

  • Product / Ticket / Option name

  • Booking statement: View data for a specific statement period.

  • Booking reference: Search for an individual booking.

2. Turnover report

This report shows the products sold during the selected period. Make sure to check which date type you're using (Transaction or Sales Recognition).

The columns are:

  • Quantity sold: The valid quantity of items sold.

  • Total excluding tax (before discount).

  • Discount amount: Any reductions or deductions applied to the original ticket price, resulting in a discounted price for the transaction.

  • Total excluding tax (after discount).

  • VAT: The amount of VAT calculated for the transaction.

  • Total price: The total price, including VAT.

3. Payment method report

This shows how payments were received during the selected period.

The payment gateway

  • Marketplace: Includes OTAs such as GetYourGuide.

  • Offline: Covers cash payments, invoices, and external card payments (not linked to Smeetz).

  • Smeetz Pay: Online and onsite card payments via Adyen (& Smeetz).

The columns are:

  • # of transactions: The total count of payments recorded during the specified period.

  • Payment value: The total amount received as payments.

  • Refund value: The total amount refunded for transactions.

  • Payment and refund value: Total of payments received minus refunds

4. Debit and credit movements

This section highlights imbalances by booking ID.

Report Value

What it means

Positive amount

Customer still owes payment (e.g. delay between purchase and settlement, partially paid booking)

Negative amount

Refund due to customer (e.g. ticket cancelled but not yet refunded)

5. Report on sales subject to VAT

This section focuses on VAT details.

The columns are:

  • Quantity: The valid quantity of tickets sold.

  • Total excluding tax

  • VAT: The amount of VAT calculated for the transaction.

  • Total price: The total price, including VAT.

6. Fee report

Here you’ll find all Smeetz-related fees for the selected period, grouped by accounting code.

The columns are:

  • Booking fee

  • Payment fee fixed

  • Payment fee variable

  • Interchange fee

  • Scheme fee

  • Commission fee

  • Total fees (excl. VAT)

  • VAT on fees

  • Other tax

  • Total fees (incl. VAT)

💬 Contact your account manager if you have questions about any of the fees listed here.

Common questions and sources of errors

1. Filters and inconsistent reporting

Be mindful when using filters across sessions. Changing filters — especially sales channels or date types — can lead to reporting discrepancies.

Example
If you filter by e-commerce only, but some bookings were later modified in the back-office, they will no longer appear under e-commerce sales. This can cause payment totals and sales totals to mismatch.

💡 To avoid confusion, limit the number of filters applied when reviewing key metrics.

2. Why the Turnover Report and Payment Method Report differ

These reports are based on different date types:

  • Turnover Report: shows revenue by sales/transaction date

  • Payment Method Report: shows payments by payment date

This means that:

  • A sale made on one day and paid a few days later will appear in different periods.

  • This time lag can cause mismatches in totals when using a specific date range.

Use the Debit and Credit Movement Report to see the difference between sales and payments, broken down by booking.

You can also view these under Orders > Orders with balance.

3. Gift card payments in the Payment Method Report

Gift cards create multiple payment entries across different stages of use. Here’s how they appear in your reports:

When gift cards are purchased:

  • Positive entry: Shows as a payment method

  • Negative entry: Listed as voucher issuance, because the value hasn’t been used yet and isn’t counted as revenue

Example

  • 3 gift cards are purchased for CHF 90

  • The Payment Method Report shows:

    • +90 under TWINT

    • –90 under Voucher Issuance

  • At this point, the gift cards are recorded as liability (deferred revenue), not sales.

When gift cards are used:

  • The redemption appears as a positive entry under voucher redemptions

  • The sale is now included in the Turnover Report and linked to the final product purchased

💡 Once redeemed, gift cards become the payment method used for the ticket purchase, and the revenue is recognized.

4. Reconciliation differences due to Smeetz Pay fee settings

If the "Charge Smeetz Pay fees to the customer?" option is enabled, part of the fee is passed on to the end user. As a result:

  • Your reported sales x price might not match the summary total, because the payment fee is deducted separately.

  • This can affect how revenue is displayed and needs to be considered when reconciling with the Booking Statement.

5. Tracking cash by accounting code

If you want to track cash received per accounting code, we recommend:

  • Creating separate accounting codes for online vs. onsite sales

  • This allows more granular reporting in both the Accounting Summary and Journal Entries

Importance of setting up accounting codes

Accounting codes are essential to:

  • Organise your income and expenses

  • Track financial data by product, department, or sales channel

  • Reconcile bookings and payouts accurately

Be sure to assign a code to each product during your Smeetz setup.

6. Booking Statements reflect the transaction date

Booking Statements are based on the transaction date (when the booking was made), not the sales recognition date. This means:

  • Payments may still be pending at the time of generation

  • These differences are reflected in the customer balance line of the Booking Statement

Use the Accounting Summary to match revenue and costs to the correct accounting period.

Did this answer your question?