Finance & Billing adds a fixed set of question types, called query types, to the Query Center. Each query type gives you a ready-made starting point with a table, related records, and default columns. You choose the query type first, then add conditions and select the fields you want. Finance & Billing maintains this list, so there is nothing for you to create, rename, or remove.
What It Controls
This list controls which Finance & Billing questions appear in Select Query Type in the Query Center, grouped by category. Other Rhythm applications, such as Membership, use the same list for built-in reports and drill-downs on Finance & Billing data. They request a query type by its identifier, such as invoice line items, instead of needing to know how Finance & Billing stores the data.
Not every payment-related field is available from every query type. Payments includes payment details but not Product Name, so start from Payments > Payment Line Items with Products when a report needs both payment and product information.
Where to Find It
Go to Finance & Billing › Queries to open the Finance & Billing Query Center. Select Select Query Type to see the Finance & Billing query types below, grouped by category, along with any custom query types your account has added.
The Query Types
| Category | Query Type |
|---|---|
| Invoices | Invoices |
| Invoices | Invoice Line Items with Products |
| Invoices | Historical Invoice Snapshots |
| Invoices | A/R Aging Summary |
| Payments | Payments |
| Payments | Payment Captures |
| Payments | Payment Line Items with Products |
| Payments | External Payments |
| Credits | Credits |
| Credit Line Items | |
| Refunds | Refunds |
| Refunds | Refund Line Items |
| Batches | Batches |
| Batches | Subledger Entries |
| Batches | Subledger Entries by Batch |
| Revenue Recognition | Revenue Recognition Schedules |
| Revenue Recognition | Revenue Recognition Schedule Entries |
| Billing | Installment Schedules |
| Products | Products |
Finance & Billing provides the same built-in query type list for every Rhythm account. You can see custom query types your account has added alongside that list, but you cannot ask Finance & Billing to add a new built-in query type just for you. Rhythm sets each query type’s fields, joined records, default columns, and sort order.
Some query types include more fields than others. Payments includes payment details and, when you need it, the payer’s contact organization name, but it does not include product information. Payments > Payment Line Items with Products is the right starting point when a report needs what was purchased and payment-related details together, such as payment date, organization, totals, product name, and capture batch. A practical starting field set for that kind of report is Invoice, Organization Name, Bill to Contact, Product, Balance Due, Status, Amount Paid, and Date; Product data is expected to be available from this query type. Keep in mind that Status means different things in different queries. It may reflect the invoice’s status or the order’s status, so check which field you have before you rely on it.
That same query type has two fields for a payment line’s inline bundled products, Bundled Product 1 and Bundled Product 2. These fields map only to the first and second inline bundled products on the line, so a third bundled product is not reportable in them. The Primary Product Total field returns the line item total minus the inline bundled product amounts, which lets you report the remaining amount attributed to the primary product. These bundled-product fields were added going forward only. They populate for newly processed transactions but stay blank for payments and invoices processed before the fields existed. Two related fields also use different value formats: Product Type returns the coded type value, while Type under product returns the friendly display name. Check these fields if a criterion or output column does not look the way you expected.
Invoices, Invoice Line Items with Products, and Payments are separate query types with their own record grain. If you need invoice, line-item, and payment detail together, you may need to build separate queries instead of one combined report. The same is true across transaction types: Query Center cannot return payments, refunds, and credits together in one result, so build a separate query for each transaction type you need. When you add a field that describes what was purchased, such as product name or quantity, you usually need a line-item query type. That returns one row per line item instead of one row per invoice or payment, so choose the query type whose grain matches the report you want before you add those fields. To report who purchased event registrations or function tickets and what they paid, start from Invoice Line Items with Products and add contact and organization details, quantity, product name, amount totals, balance due, and payment status, then filter to the relevant products.
Refund processing dates are not available from every query. To report when a refund was processed, build your query from a refund-specific source such as Refunds or Refund Line Items instead of a payment-based query type. A date column on a payment query type can represent the payment line item’s date, not the refund transaction’s date. Refunds also lets you include batch-related output fields, so you can report on refunds and their batch without going through the payments area.
Batches shows a payment’s method only when the payment was made at the time the order was placed. It leaves the method blank for a payment recorded later against that order.
Warning
Adding a Product Type (Invoice Line Item) criterion set to equals to a Batches > Subledger Entries query can cause the query to fail to save, preview, or run, no matter which product type value you choose. If a subledger query behaves this way, remove that criterion and filter by product another way.
Dependencies and Precedence
- Other applications reuse this list. A built-in Membership report, for example, can use the Invoice Line Items with Products query type. When you select its Open Query button, you open this same Query Center with that question already running.
- Reaching the Query Center is what is checked, not each query type individually, in the browser. After you open the Query Center, Select Query Type shows every query type your account is entitled to use. The platform Query Center hides any query types you may not run.
Change Impact and How to Revert
There is nothing to change or revert because this list is not a setting you maintain. If Rhythm adds a new query type, it can take up to about ten minutes after release to appear because the query runner keeps a short-lived copy of the list.
Permissions
You need your account’s Finance & Billing queries permission to open the Query Center. A specific query type can also require its own permission. If a query type you expect is missing from Select Query Type, or a saved query based on one is refused when you open or run it, ask your administrator to check that permission.
If a query works for everyone else but fails intermittently for one person, start by confirming that person’s role and permissions instead of assuming a Rhythm issue. An administrator or superuser account should be able to reach every query type without restriction. If the problem still will not reproduce, ask the affected user for a screen recording that shows the browser’s inspector or console log open at the moment of failure, since that is usually what is needed to investigate further.
Related
Use Design and Run a Query to learn how the Query Center works, including choosing a query type, adding conditions, picking columns, and saving, scheduling, or exporting the result. This article only lists the Finance & Billing questions you can start from.