Skip to content

Transaction Reports

Transaction Reports record the financial events TicketingHub has logged for bookings, payments, refunds, vouchers, merchandise and OTAs. Use them to trace what happened inside TicketingHub and reconcile it with your accounts.

They are not bank payout statements. Stripe, PayPal and other providers can combine transactions, deduct fees and settle them on different dates.

Download a Report

  1. Go to Reports → Transaction Reports.
  2. Select a start and end date.
  3. Find the report you need and select Download.
  4. Wait for the export to finish, then save the CSV.

Most reports allow a date range of up to one year. Use shorter periods when you are investigating a discrepancy or working with a large account.

The files use tab-separated columns and can be opened in Excel or imported into Google Sheets. If values appear in one column, choose Tab as the separator during import.

For booking, customer, payment or manifest exports—or automatic connections to another system—see How to Export TicketingHub Data and Connect Other Tools.

Understand the Dates Before Comparing Totals

The date range you select is interpreted in your account’s timezone. Timestamps inside the downloaded file are shown in UTC. Convert the timestamps before comparing a report with local daily totals.

Transaction Date

Transaction Date reports filter by when TicketingHub recorded each financial event. A booking can have events on several dates, such as creation, amendment, payment allocation, cancellation or refund.

Use Transaction Date when investigating what changed in TicketingHub during a period.

Reporting Date

Reporting Date reports filter by when revenue is recognised for reporting. This can differ from the date on which the event was recorded.

Use Reporting Date for month-end revenue and accrual accounting. The booking detail export includes both transaction_date and reporting_date, so you can see why an event falls into different periods.

Reporting Date versions are available for the Booking Summary, Booking Detail and Booking Sales reports.

Understand Currencies and Positive or Negative Values

Reports can contain two currencies:

  • Revenue and amount columns use your account’s supplier currency.
  • order_currency and order_currency_amount show the currency used on the customer order.

Booking and voucher reports use accounting signs. Booked or sold values are often negative, while payments and allocations are positive. A negative booked value does not automatically mean a refund.

In the Payment and Refund report:

  • Payments are positive.
  • Refunds are negative.
  • charge_amount contains related fees or fee reversals.
  • net_amount is the transaction amount after those charges.

Choose the Right Report

Your goalUse this report
One total row for each standard bookingBooking Transaction Summary
Audit every financial event on a bookingBooking Transaction Detail
Analyse sales by ticket type or extraBooking Transaction Sales
Track voucher sales, redemptions and cancellationsVoucher Booking Transaction Summary or Detail
Track merchandise and gift-card merchandise salesMerchandise Purchase Transaction Summary or Detail
Match payments and refunds to a payment providerPayment And Refund Transaction Detail
Find orders holding money that is not fully allocatedUnallocated Payments
Review Viator, GetYourGuide or Airbnb payment activityOTA Transaction Report

Booking Transaction Summary

This report returns one row per standard booking. It combines ticket and extra activity into booking-level totals.

Choose:

  • Transaction Date to include transaction events recorded during the selected period.
  • Reporting Date to include revenue recognised during the selected period.

Important columns include:

  • Order, booking, customer, reseller, product and variant references
  • Order status and source
  • Booking creation, experience and cancellation dates
  • pax for the guest quantity
  • booked_revenue, tax and gross
  • paid_revenue and paid_tax
  • allocated_payments
  • allocated_refunds_and_adjustments
  • net_allocations

Use net_allocations to understand how much payment remains allocated to that booking after refunds and adjustments. Use the order and booking references to investigate a row in the dashboard.

Booking Transaction Detail

This report returns one row per booking transaction event instead of one row per booking.

It includes the same order, customer, reseller, product and booking identifiers as the summary, plus:

  • transaction_date
  • reporting_date
  • transaction_type
  • quantity and pax
  • Supplier-currency amount
  • Order-currency amount

Common transaction types include creation, adjustment, cancellation, expiry, allocation and deallocation.

Use this report when an accountant or support agent needs the full audit trail behind a Booking Summary total.

Booking Transaction Sales

This report groups each booking by the ticket tier or extra that produced the value. It is the best export for questions such as:

  • Which ticket types produced the most revenue?
  • How much did an extra contribute?
  • Which channel, reseller, package or POS order produced the sale?

Important columns include:

  • Order and booking references
  • Product, variant and package
  • origin_type and origin_name for the tier or extra
  • Order creator, reseller, channel and POS indicator
  • Experience date and product timezone
  • booked_revenue, tax, gross, paid_revenue and paid_tax

Use the Reporting Date version for recognised revenue by tier. Use the Transaction Date version to investigate activity recorded during a period.

Voucher Booking Reports

Voucher Booking reports cover prepaid, open-dated voucher bookings. They do not list ordinary coupons or monetary gift-card balances.

Voucher Booking Transaction Summary

Returns one row per voucher booking with:

  • Order, voucher booking, customer, reseller and product references
  • sales_value, tax_value and gross
  • Redeemed value, tax and gross
  • Cancelled or expired value, tax and gross

Use it to understand voucher liability movement: vouchers sold, redeemed into dated bookings or cancelled.

Voucher Booking Transaction Detail

Returns one row per voucher transaction event, including creation, adjustment, redemption, expiry and cancellation.

Use it to trace the history behind a voucher summary row. To find which vouchers are still waiting for customers to choose a date, use the Orders filters described in How to Find Unallocated, Unredeemed and Returned Vouchers.

Merchandise Purchase Reports

These reports cover merchandise purchases, including merchandise configured as a gift card.

Merchandise Purchase Transaction Summary

Returns one row per merchandise purchase with:

  • Order, customer, reseller and merchandise references
  • Merchandise name and quantity
  • Purchase and cancellation dates
  • Booked revenue, tax, gross, paid values and allocations

Merchandise Purchase Transaction Detail

Returns one row per merchandise transaction event. The deferred_income_type column distinguishes ordinary merchandise from gift-card merchandise.

Use the detail report when you need to trace adjustments, cancellations, payment allocations or deallocations. Gift-card redemption balances are tracked separately from the original merchandise purchase, so do not treat the merchandise summary as a complete gift-card liability report.

Payment And Refund Transaction Detail

This report returns one row per payment or refund across bookings, vouchers and merchandise.

Important columns include:

  • Order reference, source, status, customer, reseller and channel
  • payment_type
  • payment_reference
  • gateway_transaction_id
  • Payment or refund creator
  • transaction_date and transaction_type
  • Supplier and order currencies
  • amount, charge_amount and net_amount

Reconcile a Payment Provider

  1. Download this report for the period you are checking.
  2. Filter by payment_type.
  3. Match gateway_transaction_id with the transaction identifier in Stripe, PayPal, Spreedly or your other provider.
  4. Compare amount, charge_amount and net_amount.
  5. Use the order reference to investigate differences in TicketingHub.

A blank gateway transaction ID is normal for cash, bank transfer, credit or another manually recorded payment.

This report shows when TicketingHub recorded money moving in or out. It does not show when a provider paid the money into your bank. Use the provider’s payout report for settlement dates and bank deposits.

Unallocated Payments

This report returns orders with a positive balance that has not been fully allocated to a booking or merchandise item.

Important columns include:

  • Order reference, source, status, customer and reseller
  • Order creation date
  • Order total
  • Payments total
  • Refunds total
  • unallocated_amount
  • The same totals in the order currency

Use this report at month-end to find deposits, excess payments or manual payments that still need attention.

The date filter uses the date the order was created, not the date of the latest payment. If you are looking for a recent payment on an older order, widen the range to include the order’s creation date.

An unallocated payment is not the same as an unredeemed voucher. An unallocated payment is money not fully assigned inside an order; an unredeemed voucher is a voucher booking awaiting a date.

OTA Transaction Report

This report covers payment and refund activity from Viator, GetYourGuide and Airbnb orders.

Columns include:

  • Transaction and order IDs
  • Order reference
  • Amount and currency
  • Calculated fee
  • Transaction date
  • OTA source

Use the order reference and source to compare TicketingHub rows with the OTA’s remittance statement. Direct website, dashboard and POS orders do not appear in this report.

The fee is calculated from the OTA fee settings on your account. It is not necessarily the final amount paid by the OTA after every adjustment on its statement.

Month-End Revenue

  1. Download Booking Transaction Summary (Reporting Date) for the accounting period.
  2. Use Booking Transaction Detail (Reporting Date) when you need the events behind a total.
  3. Review Voucher and Merchandise reports separately.
  4. Review Unallocated Payments and resolve outstanding balances.
  5. Record payment-provider and TicketingHub fees separately.

Bank and Card Reconciliation

  1. Download Payment And Refund Transaction Detail.
  2. Match gateway transaction IDs with the provider.
  3. Compare the provider’s payout report with your bank statement.
  4. Account for provider fees, payout batching, refunds and settlement timing.

One payment-provider payout can contain transactions from several TicketingHub orders, so an order total will not always match one bank deposit.

Voucher Liability

  1. Use Voucher Booking Transaction Summary for voucher sales, redemptions and cancellations.
  2. Use the Detail version to audit individual events.
  3. Use the Orders voucher filters for the operational list of vouchers still awaiting redemption.

OTA Reconciliation

  1. Download OTA Transaction Report.
  2. Filter by OTA source.
  3. Match order references against the OTA statement.
  4. Investigate cancellations and refunds in Payment And Refund Transaction Detail when more detail is needed.

Why Two Reports May Not Match

Check these common causes before assuming data is missing:

  1. Different date basis: Transaction Date and Reporting Date can place the same event in different periods.
  2. Timezone conversion: CSV timestamps are UTC, while your comparison may use local time.
  3. Different financial layers: Booking reports track revenue and allocation; Payment reports track money received or refunded.
  4. Voucher or merchandise activity: These are separated from standard booking reports.
  5. Unallocated balances: A payment can exist before it is fully assigned to a booking.
  6. Provider settlement timing: A gateway can pay several transactions in one later payout.
  7. Fees: Provider and service charges can make net deposits differ from gross payments.
  8. Multiple currencies: Supplier-currency and order-currency values may differ after conversion and rounding.
  9. Manual payment methods: Cash, bank transfer, credit or external card payments may not have a gateway identifier.
  10. Order status changes: A cancellation or amendment can create later transaction events for an older booking.

Frequently Asked Questions

Which report should I send to my accountant?

Use Booking Transaction Summary (Reporting Date) for recognised revenue totals. Add Booking Transaction Detail (Reporting Date) when the accountant needs a line-level audit trail. Include Voucher and Merchandise reports if you sell those items.

Which report should I use for Stripe or PayPal?

Use Payment And Refund Transaction Detail, then match its gateway transaction IDs against the provider. Use the provider’s payout report—not TicketingHub alone—to confirm what reached your bank.

Why are booked revenue values negative?

Booking and voucher reports use accounting signs. Booked or sold values can be negative while allocations and payments are positive. Use the column meaning and transaction type rather than interpreting every negative value as a refund.

Why is a payment missing from Unallocated Payments?

That report filters by the order’s creation date. Include the date on which the order was created, even if the payment was added later.

How do I list unredeemed vouchers?

Use Orders → Filter By → Voucher Booking → Is Voucher. Transaction Reports explain voucher financial activity; the Orders filter shows the current operational list.

How do I export the report to Google Sheets?

Download the file, then use File → Import → Upload in Google Sheets and select Tab as the separator. For automatic updates, see How to Export TicketingHub Data and Connect Other Tools.

For more context on provider payouts, reseller invoices and TicketingHub fees, see Your TicketingHub invoices and payouts.