> 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/invoices-house-account-overview/view-house-account-payments.md). # How to View House Account Payments ### 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). * House Account billing must be enabled on your tenant. See: [How to Configure House Account Billing](/products/control-panel-overview/admin-overview/configure-house-account-billing.md). > **Note**: House account payments are visible on the View Transactions page even if the automatic house sweep is not enabled. ### How house account payments work The **house account** function lets members add charges to a running balance instead of paying card-on-file at the moment of purchase. When a member chooses to add a dining, spa, or room charge to their house account, Peoplevine creates an invoice on their profile rather than charging immediately. Open invoices are held for one month, and on the 5th of the following month, the system runs all of their open invoices as one charge to close out their house account. In practice, the typical flow is: * **Member adds a charge to house account** — for example, a server closes a dining check in Micros to the member's house account at the end of the meal. * **Peoplevine creates an open invoice** on the member's profile. The transaction shows status `INVOICED` until payment is collected. * **The invoice sits open** until one of three things happens: (a) the 5th-of-month sweep runs, (b) the member pays it from the Member Portal, or (c) staff takes payment manually using **TAKE PAYMENT** on the invoice detail page. See: [How to Manage Invoices](/products/control-panel-overview/invoices-house-account-overview/manage-invoices.md). * **On the 5th of the following month**, the sweep collects all open invoices and runs them as a batch charge on each member's card on file. If a member's card on file is expired, the sweep will decline for that member — they need to add a new card on file via the Member Portal before the invoice can close. Members can also pay any open invoice or their full house account balance from the **Member Portal** at any time, without staff involvement. For a higher-level view of all members and their outstanding house account balances — including aging by 60 / 90 days — use the **Accounts Receivables** report. The View Transactions page gives you per-invoice detail; the A/R report gives you per-member roll-ups. ### Instructions **Finding house account payments:** 1. Navigate to [**SELL > View Transactions**](https://control.peoplevine.com/transactions). > **Note (Pro Dash):** Navigate to **SELL > Transactions > View Transactions**. 2. Click the **HOUSE ACCOUNT PAYMENTS** quick filter button at the top of the page. 3. Confirm the date range, then click **APPLY** and **SHOW DATA** to load results. You can also filter by payment type (CC vs ACH). Alternatively, use the Filter by Status checkboxes: check only **Payments (on Invoices)** and click **APPLY**, then **SHOW DATA**. **Identifying house account sweep payments:** House account sweep payments have these characteristics in the transaction list: | Indicator | What You See | | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Transaction status** | `payment` (displayed as "house payment" in the status badge) | | **Transaction ID column** | "PV House Account" button + "via invoice". The PV payment on file tag shows whether the payment was processed via Stripe or GoCardless, along with the payment ID. | | **Payment For column** | "House Account" | | **reference\_type** (in exports) | `invoices` | A **house payment** type transaction represents the single batch charge from the house account sweep that closes multiple outstanding invoices for one member. It is the consolidated charge that collects all open invoices in one transaction. House account payments can be processed individually or by batch. **How the sweep works:** * The automated sweep runs on the **5th of each month** at approximately 5 AM (or daily, depending on your configuration). This timing is fixed and not configurable per tenant. * The sweep charges the payment method on file for all open invoices from prior months. Only invoices generated within the last 12 months are included — invoices that have aged past 12 months are excluded from the automated sweep and must be followed up manually. * During the sweep, charges are routed by category — F\&B charges go to the F\&B processor, Spa charges to the Spa processor, and PMS charges to the PMS processor. If no category-specific processor exists, invoices route through the designated house account processor. You can set this to either the **Default Processor** or the **Membership Billing Processor** under Platform Settings. See: [How to Configure House Account Billing](/products/control-panel-overview/admin-overview/configure-house-account-billing.md). **Seeing which invoices a sweep payment covered:** 4. Click the **View** icon on a house payment-type transaction to open the transaction detail. 5. The transaction detail shows the charge amount and the member it was collected from. The individual invoices that were settled by this sweep payment are the member's previously open invoices that are now marked as **Invoice Paid**. 6. To cross-reference, open the member's CRM profile (click **GO TO PROFILE**), scroll to the **TRANSACTIONS** section, and look for transactions with an **Invoice Paid** status badge that have the same or nearby **Date Paid** as the sweep payment. ### Best Practice * **Exclude house payment type when totaling revenue.** The house payment record represents the batch charge that collects existing invoices. The individual invoices it covers are separate line items. Including both in a revenue report counts the same funds twice. * **Check for missing payment methods.** Members must have a payment method on file for the sweep to process. If a sweep payment is missing for a member with open invoices, check whether they have a valid payment method assigned. See: [How to Find Members with No Payment Method on File](/products/control-panel-overview/charging-payments-overview/find-members-no-payment.md). ### What Happens Next * **Failed sweep charges**: If the sweep payment fails (e.g., card declined), the invoices remain open and the member's subscription is not affected — house account billing and subscription billing are separate engines. * **Manual collection**: Staff can also collect on open invoices individually from the **View Open Invoices** page or the member's CRM profile. See: [How to Manage Invoices](/products/control-panel-overview/invoices-house-account-overview/manage-invoices.md). *Last updated: 2026-05-27* --- # 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/invoices-house-account-overview/view-house-account-payments.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.