> For the complete documentation index, see [llms.txt](https://help.peoplevine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.peoplevine.com/products/control-panel-overview/reports-overview/pull-revenue-reports.md). # How to Pull Revenue Reports by Category ### Before you begin (Prerequisites) * **Permissions**: Administrator, Supervisor, or Support. See: [How to Manage Users and Permissions](/products/control-panel-overview/admin-overview/manage-roles-permissions.md). ### Quick cross-category snapshot For a fast overview of transaction activity across all categories, open the snapshot view: 1. Navigate to [**REPORTS > Transaction Flash Reports**](https://control.peoplevine.com/reporting/transactions). > **Note (Pro Dash):** Navigate to **SELL > Transactions > View Transaction Report**. The same feature is renamed in Pro Dash. 2. Set the date range and click **APPLY**. To drill into a specific category, use the detailed reports outlined below. ### Membership revenue To report on **collected** membership billing revenue, use the View Transactions page — not View Subscriptions. View Subscriptions is a forecast of upcoming dues (a book-of-business view), not revenue already collected. 1. Navigate to [**SELL > View Transactions**](https://control.peoplevine.com/transactions). > **Note (Pro Dash):** Navigate to **SELL > Transactions > View Transactions**. 2. Set **Payment For** = **Membership Billing**. 3. Set **Status** to **Processed** (or "Membership Revenue Already Collected") to see only collected dues. To also include invoiced dues not yet paid, add the **Invoiced** status. Keeping all statuses selected will include declines, refunds, and errors within the same date range. 4. Apply your date range and click **APPLY**, then **SHOW DATA** to view results or **EXPORT DATA** to download a CSV. For a forecast of upcoming membership dues: 1. Navigate to [**SELL > View Subscriptions**](https://control.peoplevine.com/subscriptions). > **Note (Pro Dash):** Navigate to **SELL > Subscriptions > View Subscriptions**. 2. The page shows **Estimated Revenue** with Annual Revenue (ARR) and Monthly Revenue (MRR), plus a **To Be Collected** breakdown by subscription status. Click **EXPORT DATA** for subscription-level detail. ### Event and ticketing revenue Two ways: **Via View Transactions (recommended for event-level detail):** 1. Navigate to [**SELL > View Transactions**](https://control.peoplevine.com/transactions). 2. Set **Payment For** = **Events**. 3. Set your date range. The date range should cover when tickets went on sale — each transaction is recorded when the member purchased the ticket, not the event date. 4. Set **Status** to **Processed** for collected revenue only, or include additional statuses as needed. 5. Click **APPLY**, then **EXPORT DATA**. 6. Once filtered for a specific event, use the `transaction_amount` or `processed_amount` column to calculate that event's revenue. See: [Transaction Export Field Reference](/products/control-panel-overview/reports-overview/transaction-export-fields.md). **Via Transaction Pivot Reports (for grouped totals):** 1. Navigate to [**REPORTS > Transaction Pivot Reports**](https://control.peoplevine.com/render/report_pivot_billable_items). > **Note (Pro Dash):** Navigate to **SELL > Transactions > Transaction Pivot Reports**. 2. Select the report type that groups by billable item (Transactions by Billable Items). 3. Set the date range and click **APPLY**. 4. After results load, an **Event Ticket** section shows a breakdown by event with revenue totals. ### Dining and POS revenue Whether Peoplevine processed the payment for a POS or dining transaction depends on how the club is configured: when a member pays with a card on file (which can be the primary tender at some clubs), Peoplevine processes the payment; otherwise the payment is taken on the originating POS platform. Both kinds of transactions are recorded in View Transactions. 1. Navigate to [**SELL > View Transactions**](https://control.peoplevine.com/transactions). 2. Set **Payment For** = **Orders - F\&B**. 3. Apply your date range and click **APPLY**, then **SHOW DATA** or **EXPORT DATA**. 4. To distinguish payments by processor, use the **Payment Type** filter: `creditcard` = Stripe, `ach` = GoCardless. To filter by a specific processor (e.g., if you have multiple Stripe processors), use the **Processor** filter instead. > **Note**: [**REPORTS > Sales by Location**](https://control.peoplevine.com/render/revenue-location) also shows revenue by physical location, which includes both POS and any spa locations configured on the Peoplevine virtual POS — not dining alone. ### Spa revenue 1. Navigate to [**SELL > View Transactions**](https://control.peoplevine.com/transactions). 2. Set **Payment For** = **Orders - Spa**. 3. Set **Status** to **Processed** for collected revenue only. 4. Apply your date range and click **APPLY**, then **SHOW DATA** or **EXPORT DATA**. ### Tax, payment-type, and category breakdowns For grouped breakdowns (revenue by category, payment type, tax by category), use the Transaction Pivot Reports: 1. Navigate to [**REPORTS > Transaction Pivot Reports**](https://control.peoplevine.com/render/report_pivot_billable_items). > **Note (Pro Dash):** Navigate to **SELL > Transactions > Transaction Pivot Reports**. 2. Select a **Report type** from the dropdown — the breakdown only loads after a report type is chosen (there is no default view). The dropdown lists the available pivot dimensions (e.g., billable item, revenue category, payment type, tax by category). 3. Set the date range and click **APPLY**. ### When the standard reports don't have what you need Not every revenue cut is exposed in the reports section or the reporting dashboard. For ad hoc filters (custom combinations of date range, membership program, payment type), pull raw data from [**SELL > View Transactions**](https://control.peoplevine.com/transactions) using **EXPORT DATA**, then filter in your spreadsheet. See: [Transaction Export Field Reference](/products/control-panel-overview/reports-overview/transaction-export-fields.md). ### What Happens Next * **Drill into one transaction**: [How to Read a Transaction Details Page](/products/control-panel-overview/transactions-overview/read-transaction-details.md) * **Reconcile to bank deposits**: [How to Reconcile Transactions with Stripe](/products/control-panel-overview/reports-overview/reconcile-stripe.md) * **Field-level reference**: [Transaction Export Field Reference](/products/control-panel-overview/reports-overview/transaction-export-fields.md) *Last updated: 2026-05-29* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.peoplevine.com/products/control-panel-overview/reports-overview/pull-revenue-reports.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.