Statistics export: download raw bookings and payments as CSV

It contains two different exports that answer two different questions:

• Export bookings: “What bookings took place in this period?” (operational activity)
• Export transactions: “What payments were completed in this period?” (financial reconciliation)

Because they use different date logic, they will not always match day-by-day—and that’s expected.

Where to find it

• Exports are always scoped to the selected location
• All dates are interpreted in the location’s timezone

1) First step: select a period

2) Export bookings (activity-based)

What it’s for

Use Export bookings when you want to analyze:

• bookings volume and cancellations
• who booked, when they played, what they paid
• bay usage (including multi-bay bookings)
• operational reporting (“what happened during this week/month?”)

What’s included (how filtering works)

• Filtered by startTime (in the location timezone)
• Includes bookings with status CONFIRMED and CANCELLED
• Excludes incomplete/aborted/pending flows

What a row represents

• 1 row = 1 booking
• Slot/bay data is combined into the row, including:
• Number of bays
• Bay names (comma-separated)

Choose your columns (field selection)

Before downloading, you pick exactly which columns to include using checkboxes. You can also use shortcuts:

• Select all
• Select none
• Reset to defaults

Common fields include:

• Timing: date, start/end time, created at
• Customer: name, email, phone
• Booking details: status, booking type (drop-in / pre-order), duration
• Capacity: number of bays, bay names
• Money: total amount, discount amount, member booking flag, payment status

3) Export transactions (payment-based)

What it’s for

Use Export transactions when you want to:

• reconcile revenue for a period
• cross-check totals against settlements/payout reports
• understand fees and net amounts
• export to your accountant or bookkeeping system

What’s included (how filtering works)

• Filtered by callBackTime (in the location timezone)
• Includes only payments where isCompleted = true
• Can include refunds (see below)

What a row represents

• 1 row = 1 payment
• Transactions can be tied to different types of purchases, such as:
• bookings
• membership purchases/renewals
• value cards
• gift cards
• event participation

Fees: how to read them

• Alba fee: combined fees (processing + service fees)

• Net to venue: 

  Amount−Alba fee

  Amount−Alba fee

Refunds

Refunds may appear in the export. A refund can show up as:

• a negative amount, and/or
• a row marked as a refund

Choose your columns (field selection)

Common fields include:

• Identifiers: payment ID, reference
• Classification: category + description
• Amounts: amount, currency, Alba fee, net to venue
• Customer: name, email
• Status + refund flag
• Payment method: derived from the payment reference (e.g. Card/Vipps/Other)

4) The most important concept: these exports are not the same dataset

Bookings export ≠ Transactions export

• Bookings export: filtered by booking start time → best for operational reporting
• Transactions export: filtered by payment callback time → best for accounting/reconciliation

Example (why dates won’t line up)

• The payment can appear in transactions today
• The booking appears in bookings next week (because that’s when the visit happens)

A simple “which export should I use?” rule

• Use Export bookings when your question is about playtime and activity

• Use Export transactions when your question is about money and reconciliation

Quick checklist before you download

• Selected the correct location
• Selected the correct period
• Remembered timezone behavior (venue timezone)
• Picked the columns you actually need
• Included refunds (for reconciliation)