> 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/transaction-export-fields.md). # Transaction Export Field Reference ### 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). * You have exported a CSV from [**SELL > View Transactions**](https://control.peoplevine.com/transactions) using the **EXPORT DATA** button. See: [How to Navigate the View Transactions Dashboard](/products/control-panel-overview/transactions-overview/navigate-transactions-dashboard.md). ### How to export 1. Navigate to [**SELL > View Transactions**](https://control.peoplevine.com/transactions). > **Note (Pro Dash):** Navigate to **SELL > Transactions > View Transactions**. 2. Apply any filters (date range, status, etc.). 3. Click **EXPORT DATA**. In the modal, choose: * **EXPORT DATA** — downloads a CSV using the current filters. * **ADVANCED EXPORT** — lets you select additional fields and filters before downloading. ### Key fields in the export CSV The transaction export contains 44 columns. Below are the fields operators most commonly need to understand. **Native Peoplevine identifiers:** | Field | Description | Example | | ----------------------- | ---------------------------------------------------------------------------------------------------- | -------- | | `transaction_no` | Peoplevine's unique identifier for the transaction | 18731123 | | `customer_no` | Member/customer ID | 2697771 | | `card_no` | Payment method ID in Peoplevine — `0` = no payment method on file | 717665 | | `linked_transaction_no` | Related transaction ID — links a refund to its original charge, or an invoice payment to its invoice | — | > **Note**: Processor identifiers (Stripe Payment Intent, GoCardless reference) are listed under **Payment details** below. **What was charged:** | Field | Description | Example values | | ----------------- | ------------------------------------------------------- | -------------------------------------------------------------------------------------- | | `reference_type` | Type of entity charged | `order`, `membership`, `invoices`, `application`, `service`, `transaction`, `giftcard` | | `reference_no` | ID of the referenced entity (order\_no, card\_no, etc.) | — | | `reference_title` | Human-readable charge description | "Gold Membership", "Order - ecommerce", "Order - pos", "Gift Card/Stipend", "invoices" | **`reference_type` values explained:** | Value | Meaning | | ------------- | ------------------------------ | | `order` | Ecommerce or POS order | | `membership` | Subscription billing (dues) | | `invoices` | Monthly invoice sweep | | `application` | Application fee | | `service` | Service or add-on charge | | `transaction` | Peoplevine general transaction | | `giftcard` | Gift card or stipend issuance | **Amounts:** | Field | Description | | -------------------- | --------------------------------------------------------------------------------------------------------------------------- | | `transaction_amount` | Total amount charged. **Use this field for Sales Reporting** — it is the sale amount. | | `refunded_amount` | Amount refunded (0 if none) | | `processed_amount` | Net amount after refunds (`transaction_amount` − `refunded_amount`). For Sales Reporting, use `transaction_amount` instead. | | `tax_amount` | Tax portion of the charge | | `discount_total` | Discount applied | **Dates:** | Field | Description | | ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `charged_on` | Date the payment was processed. **Use this field for Sales Reporting** — `charged_on` is the invoice date. The value is set once and does not change afterward; it can be back-dated at the moment an admin manually processes a charge, but it is not updated later. | | `paid_on` | Date the transaction reaches `processed` status. For card payments this matches `charged_on`. For ACH it is later — GoCardless takes days to confirm bank processing, and `paid_on` only stamps when the transaction flips to `processed`. (`1/1/1900` = unpaid.) | | `matched_on` | Date the transaction was reconciled to a Stripe or GoCardless bank payout (`1/1/1900` = not matched). | **Payment details:** | Field | Description | Example values | | ------------------- | --------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- | | `payment_type` | Payment method used. Also reflects the source system when payment was taken outside Peoplevine. | `creditcard`, `invoice`, `cash`, `entry`, `ach`, `giftcard`, `papercheck`, `pos`, `spa` | | `t_card_type` | Card brand or tender type | `amex`, `visa`, `mastercard`, `Invoice`, `Cash`, `ach` | | `t_card_four` | Last 4 digits of card | 4242 | | `payment_processor` | Processor used | `stripev2`, `gocardless` | | `transaction_id` | Processor transaction reference — Stripe Payment Intent (`pi_*`) or GoCardless payment ID (`PM*`). Used for reconciliation. | `pi_3T9ryF...`, `PM12AB34CD...` | | `batch_id` | Stripe or GoCardless payout batch ID — groups all transactions in a single bank deposit. | — | | `matched` | Whether the transaction has been matched to a processor payout (Y/N) | N | | `check_number` | Order number from the originating system (e.g., Micros check number, Book4Time order number) | — | | `order_source` | Source system the order came from | `Micros Simphony`, `Toast`, `Book4Time` | **Status:** | Field | Description | | -------------------- | -------------------- | | `transaction_status` | Internal status code | Status code mapping: | Code | UI label | | ----------- | ---------------------------------------------------------- | | `invoiced` | Invoiced | | `processed` | Processed | | `refunded` | Refunded | | `declined` | Declined | | `payment` | House Account Payment (applied toward an existing invoice) | **Other fields:** | Field | Description | | -------------------------- | --------------------------------------------------------------------------------- | | `first_name` / `last_name` | Customer first name and last name (the CRM record on the transaction) | | `wasInvoice` | True if this was originally invoiced before payment was collected (invoice sweep) | | `transaction_response` | Processor response message | | `transaction_attempts` | Number of charge attempts | > **Note**: To identify deposits in the export, look at the `reference_title` column. Admin-entered reference titles (e.g., "Issued Deposit") appear here. System-generated transactions show "Processed by Peoplevine" as the default. ### Initiation fees and combined charges When an enrollment combines an **initiation fee** and the first dues charge, both are taken in a **single transaction** that posts as **two line items**. The export shows them as one charge by default — toggle **break out transaction items** (or include `transaction_data` on the export) to see the separate line items. ### Invoices When an invoice is paid, its transaction turns to `transaction_status = processed` with `wasInvoice = Y`. A **partial** payment creates a **new** transaction linked back to the original invoice via `linked_transaction_no`. ### What Happens Next * **Related**: [How to View a Member's Transactions](/products/control-panel-overview/transactions-overview/view-member-transactions.md) for date filter explanations (Charged On vs Paid On). * **Related**: [How to View Financial Reports](/products/control-panel-overview/reports-overview/view-financial-reports.md) for pivot reports and revenue summaries. *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/reports-overview/transaction-export-fields.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.