> 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/identify-order-source.md).

# How to Identify Where a Transaction Originated

### Before you begin (Prerequisites)

* **Permissions**: You must be an **Administrator**, **Supervisor**, **Manager**, **Support**, or **Account Rep**. See: [How to Manage Users and Permissions](/products/control-panel-overview/admin-overview/manage-roles-permissions.md).

### Instructions

1. Open the transaction's detail page (from [**SELL > View Transactions**](https://control.peoplevine.com/transactions), click **View** on the row).
2. Locate the **Processed By** field on the transaction detail page. Common values:

| Processed By value         | What it means                                                                                                                                                                               |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `auto billing transaction` | Originated in Peoplevine — usually a membership dues run or house account sweep from the overnight billing engines.                                                                         |
| `self service`             | Paid within the member portal — the member was self-serve in that payment.                                                                                                                  |
| `Inbound from integration` | Synced from a connected platform. Look at the **Purchase** section directly above to see which platform — for example, a dining order from Micros (Symphony) or a spa order from Book4Time. |

3. For an `Inbound from integration` value, read the **Purchase** section above to identify the specific source platform.

### Alternative: filter orders by channel

If you want to scan a list of orders by source rather than read a single transaction, use [**SELL > View Orders**](https://control.peoplevine.com/orders) and filter by **Order Channel**:

> **Note (Pro Dash):** Navigate to **Sell > Ecommerce > Order History**.

Order Channel options:

* **eCommerce Orders** — orders placed through the member portal or online storefront
* **Point of Sale** — orders processed via the Peoplevine virtual POS (PV Dash)
* **Food & Beverage Flow** — orders from the F\&B ordering flow
* **3rd Party POS** — orders synced from an integrated point-of-sale system
* **Spa** — orders from a connected spa management system
* **Hotel** — orders from a connected property management system

### What Happens Next

* **Next step**: [How to View an Order's Associated Transaction](/products/control-panel-overview/transactions-overview/view-order-transaction.md)

*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/identify-order-source.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.