Once you've generated a Guide Payment Report, the exported file will contain three tabs that break down guide compensation in different ways — giving you the flexibility to view, analyze, and share payment data as needed.
Payment by Guide — a summarized view of total compensation per guide.
All Payment Data — the full payment dataset across all guides in a single consolidated view. The columns included here depend on how the report was generated — if you used Export current view, only your selected columns will appear. If you used Export all or Export by year, all available columns will be included.
Pay Stub — a detailed, trip-by-trip breakdown per guide, including Trip Date, Experience Name, Client Count, Gross Pay, Base Payout, Adjustments, and Payment Notes, with a total calculated per guide.
For steps on how to generate a Guide Payment Report, see How to Export Guide Payments
The columns
These are the system columns every outfitter has. Your guide report may add more — see Why your columns differ from another outfitter's below.
Trip and guide
Trip date — the date the trip occurred.
Guide — the guide assigned to the trip, and the payee on this payment.
Booking client — the client the booking belongs to.
Experience name — the experience that was sold.
Trip type — the trip type the guide reported, such as float or wade.
Permit — the permit selected on the guide report.
Location — where the trip took place. This is the Area the guide selected on their report.
Put-in and Take-out — where the boat was put in and taken out, as reported.
Trip duration — the trip's scheduled time slot, shown as a start-to-end window. Despite the name, this is not a count of hours or days.
Client counts
These three columns are separate facts and will not always match. Each answers a different question.
Submitted client # — the clients on this unit's submitted guide report. If no report has been submitted, or it is still a draft, the cell shows a dash rather than 0.
Unit client # — the clients on this trip unit, taken from the booking unit it was created from. Known as soon as the booking exists, so it never waits on a guide report.
Booking client # — the total for the experience-day: every unit of the same experience, on the same day, under the same booking, added together. Every row for that experience day shows the same total, and a morning and an afternoon unit of the same experience count into one figure. On a booking with more than one experience or more than one day, this is not the booking's overall client count.
Client names — the clients listed on the guide report.
Pay
Trip gross price — what the trip sold for.
Base payout — the guide's base pay before adjustments.
Adjustment — adjustments applied to this payment.
Total payout — base payout plus adjustments. This is what the guide is paid.
Payment status and timing
Payment status — where the payment sits: Draft, Pending, or Paid.
Payment method — Automatic for a direct deposit sent by Brindlechute, or Manual for a payment made outside Brindlechute and logged for the record.
Payment cycle — the payment batch the record belongs to.
Created date — when the payment record was created.
Est. arrival date — the estimated arrival date for an automatic payment, or the final arrival date once the payment is marked Paid.
Booking payment status — where the client is in paying for the booking.
Notes — the payment note your team writes on this guide payment. This is the same field that appears as Payment Notes on the Pay Stub tab.
Cancellation — Yes if the trip unit has been cancelled, No if it has not. This is separate from the Show cancellation days checkbox on the filter bar, which controls whether cancelled rows appear in the table at all. With that checkbox on, this column tells you which of the rows are the cancelled ones.
Guide report
Guide report status — whether the guide has submitted their report for the trip.
Guide report comments — what the guide wrote in the report's Any Comments? field. See the section below.
Three different "notes" fields. Notes is written by your team on the payment. Guide report comments is what the guide wrote in their report's Any Comments? field. Guide Notes on a booking is what you send to the guide about the trip, and it does not appear in Guide Payments or its export. If you are looking for what a guide wrote about a trip, and you want it in the table or the payroll export, you want Guide report comments.
Seeing what your guides wrote on a trip
The Guide report comments column carries the free-text Any Comments? field from a submitted guide report into the Guide Payments table and the All Payment Data tab of your export — so you can read what your guides recorded without opening each report. This is the column to use if you want guide notes, guide comments, or guide feedback in your payroll export.
This column carries the built-in Any Comments? field only. Text your guides enter in custom report fields appears in those fields' own columns instead.
The column is off by default. To turn it on:
In the left sidebar, under Payments, click Guide Payments.
Click the columns button (it shows the current count) in the top right.
In the Edit columns panel, check Guide report comments.
Click Update.
Export all and Export by year include every available column, so guide report comments appear in those files whether or not the column is showing on screen.
Why your columns differ from another outfitter's
Guide Payments columns come from two places. The columns listed above are system columns that every outfitter has.
On top of those, every custom field on your guide report becomes its own column, named exactly as you named the field. If your guide report has a Fuel reimbursement field, you have a Fuel reimbursement column. An outfitter whose report doesn't include that field won't have that column at all.
This is why two outfitters comparing their exports won't see the same set of columns, and why a column another operation mentions may not exist in yours. To add or change these fields, see Customizing the Guide Report.
Related
How to Export Guide Payments — generating the file
How to Customize Columns in Guide Payments — choosing which columns are included and in what order
Customizing the Guide Report — adding custom fields that become columns here
How to prepare 1099s using the Brindlechute guide payments export — using the export for tax reporting
Use these tabs together to streamline your guide payment process — from high-level summaries to detailed pay records ready to share with your guides.