Reports guide: Sales and payments

This guide covers the 14 reports for sales, payments, refunds, bundles, gift cards and vouchers. New to reports? See Run, schedule and read reports to learn how to run, schedule and read them.

In this article

• Charges: Payments
• Charges: Refunds
• Charges: Subscriptions
• Orders: Summary
• Orders: Details
• Orders: Details Split
• Collection Orders
• Bundles: Purchases
• Bundles: Purchases (Detail)
• Memberships: Purchases (Unique Clients)
• Gift Cards: Value
• Vouchers: Redeemed
• Vouchers: Usage Count
• Z-Report: Summary

Charges: Payments

What it does: Lists payments taken in your range (by payment date), with the method, location, amount, status and any amount since refunded.

Why use it: To reconcile takings by payment method or location, and to find failed payments.

Filters

What's in the file: One row per payment. Columns: ID, Order ID, Customer ID, Payment Method ID, Payment Method Name, Location ID, Location Name, Amount, Stripe ID, Status, Total Refunded, Created At.

Good to know

Total Refunded is all successful refunds on that payment to date, including refunds made after your range. Stripe ID may be blank for non-card methods.

Charges: Refunds

What it does: Lists successful refunds made in your range (by refund date), with the original payment, method, location, amount paid, amount refunded and tax refunded.

Why use it: To reconcile refunds against your payment provider or your accounts for a period.

Filters

What's in the file: One row per refund. Columns: ID, Order ID, Customer ID, Payment Method ID, Payment Method Name, Location ID, Location Name, Amount Paid, Amount Refunded, Tax Refunded, Stripe ID, Created At.

Good to know

• Failed or pending refunds are not included.
• Amount Paid is the original payment in full.
• Where tax wasn't recorded on the refund, Tax Refunded is estimated in proportion to the order's tax.

Charges: Subscriptions

What it does: Lists successful membership payments taken in your range (by payment date), with the plan and cost centre.

Why use it: To see membership revenue collected in a period by plan and cost centre, and match payments to Stripe.

Filters

What's in the file: One row per membership payment. Columns: ID, Customer ID, Stripe Price, Plan Name, Plan Handle, Cost Centre, Amount, External Reference, Created At.

Good to know

Free and trial payments are only included if you set the first filter to No.

Orders: Summary

What it does: Lists orders placed in your range, one row per order, with totals for price, tax, discount and refunds, plus a column per payment method showing how much was paid by each.

Why use it: For order-level sales and cash reconciliation, such as daily takings by payment method and location.

Filters

What's in the file: One row per order. Columns: Order #, Customer ID, Payment method IDs, Payment method names, Purchased at Location #, Location name, Total price, Tax total, Discount total, Amount refunded, External references, Status, Created at, then one "Paid using …" column for each of your payment methods.

Good to know

• The Status column shows the order's current status, which can differ from the status you filtered on.
• With Paid selected, only successful payments are counted in the payment columns.

Orders: Details

What it does: Lists every item (order line) sold in your range, with price, tax, discount, voucher, payment methods, references, location and order status.

Why use it: For item-level sales analysis or accounting, such as revenue by product type, cost centre or location.

Filters

What's in the file: One row per order line. Columns: Order #, Order Line #, Customer #, Buyable type, Buyable #, Buyable name, Cost centre, Quantity, Book price, Paid total, Tax total, Tax rate, Discount total, Payment method IDs, Payment method names, External references, Voucher, Purchased at location #, Location name, Status, Created at. Shipping method and Collection location are added when pre-ordering is enabled.

Good to know

Online orders show – as the location number and Online as the location name. Tax rate is a percentage.

Orders: Details Split

What it does: Like Orders: Details, but when an order was paid with more than one payment, each item's value is shared across those payments. An item covered by two payments becomes two rows, each with its share of quantity, price, tax and discount.

Why use it: To report revenue by payment method at item level when customers split a payment, such as part gift card and part card.

Filters

What's in the file: One row per item per payment covering it, with the same columns as Orders: Details but a single Payment method ID, Payment method name and External reference per row.

Good to know

Quantities can be fractional (for example 0.5) on split rows, and split amounts are rounded down to the penny, so split rows may differ from the original line by a penny.

Collection Orders

What it does: Lists items due for collection: booking pre-orders, walk-in pickups and over-the-counter orders. A booking pre-order's collection date is the class start time; other collections use the order date. Cancelled, already-collected and past collections are hidden by default.

Why use it: To prepare upcoming pre-order collections, such as what to have ready for each class over the next two weeks.

Filters

What's in the file: One row per item. Columns: Order #, Order Line #, Customer #, Buyable type, Product, Cost centre, Quantity, Collection type, Collection date, Collection time, Collection location #, Collection location, Event #, Event type, Instructor, Order note, Line status, Order placed at. Line status is Cancelled, Collected, Ready or Pending.

Good to know

Walk-in pickups and over-the-counter orders use the order date, which is always in the past. Set Exclude past collection dates? to No to see them.

Bundles: Purchases

What it does: Summarises credit bundle sales in your range by bundle (by the date the credits were created), excluding refunded credits. A bundle gets a row for each cost centre its sales went to.

Why use it: To compare purchases, credits, customers and revenue per bundle, and check progress against a sales cap.

Filters

What's in the file: One row per bundle per cost centre. Columns: Bundle ID, Bundle Name, Cost Centre, Total Purchases, Total Credits, Total Unique Customers, Total Paid, Total Tax, Cap Utilisation.

Good to know

• Total Purchases is worked out as credits sold divided by the bundle's credit count.
• Cap Utilisation is the bundle's current sold count against its cap ("X / Y (Z%)"), not limited to your range.
• Credits not from a bundle appear as a row with a blank bundle.

Bundles: Purchases (Detail)

What it does: Lists individual credit bundle purchases in your range, grouped per customer, bundle, order and day, excluding refunded credits.

Why use it: To see who bought which bundle and when, with credits, amount paid and tax.

Filters

What's in the file: One row per customer, bundle, order and purchase date. Columns: Order ID, Customer ID, Customer First Name, Customer Last Name, Customer Email, Customer Telephone, Bundle ID, Bundle Name, Cost Centre, Total Purchases, Total Credits, Total Paid, Total Tax, Purchased At.

Good to know

Purchased At is a date only. Order ID is blank for credits added by staff rather than bought through an order.

Memberships: Purchases (Unique Clients)

What it does: Lists each customer who started at least one membership in your range, with how many they started and the first and last start dates within the range. Renewals and re-joins count as well as first-time members.

Why use it: For a contact list of everyone who bought a membership in a period, such as for a welcome campaign.

Filters

What's in the file: One row per customer. Columns: Customer ID, First Name, Last Name, Email, Telephone, Total Memberships Purchased, First Purchased At, Last Purchased At.

Good to know

Memberships later cancelled are still counted.

Gift Cards: Value

What it does: Lists gift cards created in your range, newest first, with their original value and the balance remaining on a date you choose.

Why use it: To report outstanding gift card value for your accounts, or to check balances and expiry dates.

Filters

What's in the file: One row per gift card. Columns: Gift Card #, Last 4 digits of code, Customer #, Initial balance, Remaining balance, Created at, Expires at, Expired, Cost centre.

Good to know

• The customer is the person who bought the card.
• Cards created on the To date itself are not included.

Vouchers: Redeemed

What it does: Lists every voucher use in your range, with the code, whether it was a code or an automatic discount, the customer and the order.

Why use it: To see who used a promotion and when, for example to review a campaign or check for misuse.

Filters

What's in the file: One row per redemption. Columns: Voucher ID, Voucher Code, Type, Customer ID, Customer First Name, Customer Last Name, Customer Email, Customer Telephone, Order ID, Redeemed at.

Good to know

Order ID was recorded from July 2026, so earlier redemptions show it blank. One order can produce several rows when automatic discounts apply.

Vouchers: Usage Count

What it does: Counts how many times each voucher was used in your range.

Why use it: For a quick ranking of your most-used promotions.

Filters

What's in the file: One row per voucher used at least once. Columns: Voucher ID, Voucher Code, Type, Usage Count, Voucher Description.

Z-Report: Summary

What it does: Totals successful payments on orders placed in your range, by location and payment method, with refunds against those payments and the resulting balance.

Why use it: For end-of-day or end-of-month reconciliation of takings per location and payment method.

Filters

What's in the file: One row per location and payment method. Columns: Location, Payment Method, Number of Transactions, Sales (Gross), Refunds (Gross), Balance (Gross). Gross & Tax adds Sales Tax, Refunds Tax and Balance (Tax); All figures also adds Sales, Refunds and Balance net of tax.

Good to know

• Refunds are shown as negative numbers and placed by the date of the original order, not the refund date.
• There is no grand total row.