Read this once and it will save you a lot of reconciliation. The most common question we get is why this report does not match a payments report or a bank deposit. It is not supposed to. This report and the Client transactions export answer two different questions, and the rest of this article explains how.
How to run it
Go to Client transactions, then Export, then Revenue details. Pick your trip start and end dates, and the report downloads.
The dates you choose are trip dates. The report includes every experience and add-on whose trip falls between the start and end dates you set.
Revenue vs cash: the one thing to know first
You have two financial exports, and they are built to disagree.
The Revenue details export is an accrual view. It counts revenue on the date the trip runs, whether or not the money has arrived yet. A trip that runs June 28 is June revenue, even if the balance was paid in May and the tip settled in July.
The Client transactions export is a cash view. It counts money on the date it actually moves, whatever trip it was for. A deposit collected in March for an August trip is March cash.
So the same trip can land in different months on the two reports, and that is correct. If you are trying to tie the two to the penny, stop -- they will never match, because a trip's date and its payment dates are rarely the same month. Use the Revenue details export to understand what you earned. Use the Client transactions export to understand what you collected.
What lands on the report
A revenue row shows up when all of these are true.
The booking is confirmed or settled. Draft and unconfirmed bookings are not counted.
The itinerary is active. Cancelled itineraries drop off.
The item's trip date falls inside the date range you chose.
Two kinds of things earn their own rows: the guided experiences themselves, and any add-ons attached to them. A full-day float and the streamside lunch you sold with it are separate lines, so you can see what each is worth.
The columns
Every row is one item -- an experience or an add-on -- on one trip. The export has ten columns.
Date -- the trip/experience date. This is what the report buckets on.
Booking ID -- the booking this item belongs to, so you can trace it back.
Booking client ID -- the identifier for the client on the booking.
Booking client name -- who booked the trip.
Experience / addon -- the name of the experience or add-on, as it was sold.
Item subtotal -- the after-discount, pre-tax value of the item. This is the number that sums to your revenue.
Line item discount -- a discount applied to this specific line, if any.
Booking level discount -- a discount applied across the whole booking, allocated to this item.
Total tax -- tax on the item, calculated on the discounted amount.
Tax breakdown -- how that tax splits by category (for example, Sales Tax (Experiences)).
The math, so the columns tie out
Work it in this order and the numbers reconcile every time.
Gross (list) value = item subtotal + line item discount + booking level discount.
Item subtotal = the after-discount, pre-tax figure. Sum this column to get period revenue.
Total tax is computed on the discounted amount, not the list price.
If you are checking a single row by hand, start from the list price, subtract both discount columns to reach the subtotal, then apply tax to that subtotal. That mirrors exactly how the report builds it.
Two notes on discounts. Discounts can land at the line level or the whole-booking level, so the report gives you both columns -- a booking-level discount is spread across the items on that booking. And to get your gross list value for the period, add both discount columns back onto the item subtotal.
A note on dates and time zones
The Date column is a plain calendar date -- the day the trip runs. It has no time-of-day and no time zone, so it never shifts. June 28 is June 28 on anyone's screen.
Any date on our reports that comes from a timestamp (for example, when a payment was charged) is shown in Mountain time. That is a system-wide default today, not a per-account setting. For an outfitter in the Mountain zone this is simply your local time. If you operate in another time zone and a timestamp-based date ever looks off by a few hours at a day boundary, that default is the reason -- tell us and we will sort it with you.
This only affects timestamp-based dates. Because the Revenue details export buckets on the plain trip date, time zone does not change which month a trip's revenue lands in.
Common questions
Why does this not match my payments or deposits? Because it is a revenue report, not a cash report. See the section above. Revenue is dated to the trip; payments are dated to when money moved. Different questions, different months.
Why is a booking missing? Most often the booking is not yet confirmed, the itinerary was cancelled, or the trip date sits outside your selected range. Check those three first.
Why are add-ons on their own rows? So you can see what each part of a trip earned. The experience and its add-ons are priced and sold separately, and the report keeps them separate.
Is the revenue figure before or after tax? Before tax. Sum the item subtotal column for pre-tax revenue. Add the total tax column if you need the all-in figure.
Is it before or after discounts? After. The item subtotal is already net of discounts. The two discount columns are there so you can see the list value you started from -- add them back onto the item subtotal to get gross.
If a number still does not look right after this, send us the report and the figure you expected, and we will trace it with you.