> 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/transactions-overview/use-breakout-line-items.md).

# How to Use Breakout Line Items

### Before you begin (Prerequisites)

* **Permissions**: Administrator, Supervisor, Support, or Waitstaff. See: [How to Manage Users and Permissions](/products/control-panel-overview/admin-overview/manage-roles-permissions.md).
* You must be on the [**SELL > View Transactions**](https://control.peoplevine.com/transactions) page.

### Instructions

1. Navigate to [**SELL > View Transactions**](https://control.peoplevine.com/transactions).

> **Note (Pro Dash):** Navigate to **SELL > Transactions > View Transactions**.

2. In the filter panel, check the **Break-out line items into transactions** checkbox.
3. Click **APPLY**, then click **SHOW DATA** to load results.

Each combined charge now appears as separate line items in the transaction list. Without this checkbox, combined charges appear as a single row showing the total amount.

### When to use this

Some charges in Peoplevine combine multiple items into a single transaction. This happens in two scenarios:

1. **Membership enrollment** — when a member is approved through the application flow, the auto-charge combines all fees (initiation, dues, service fee) into one charge.
2. **Automatic subscription billing** — when multiple subscriptions for the same member are due on the same day, the billing engine combines them into a single transaction.

**Example — enrollment:** A membership enrollment charge of $1,500 might appear as one transaction. With breakout enabled, it splits into:

* Initiation fee (also called joining fee) — $1,200
* Monthly dues — $200
* Service fee (when paying via credit card) — $100

**Example — subscription billing:** A member has two annual subscriptions both renewing on the same date. Autobilling produces one transaction for the combined total. With breakout enabled, each subscription appears as a separate line item.

This is useful when you need to see the individual components of a combined charge for accounting or reconciliation purposes.

> **Note**: This feature applies to non-eCommerce charges that were combined into a single transaction (such as membership enrollment charges from the application/approval flow). eCommerce orders already display individual line items by default.

### What Happens Next

* **Reporting**: When exporting data with breakout enabled, the CSV will include each line item as a separate row — one charge can produce multiple rows in the export. The Payment Intent ID is the same across all breakout rows from the same original charge, which can be used to group them back together.
* **Toggle off**: Uncheck the checkbox and click **APPLY** again to return to the default combined view.

*Last updated: 2026-05-24*


---

# 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/transactions-overview/use-breakout-line-items.md?ask=<question>&goal=<endgoal>
```

`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.