Successful live collections
Record grain: transaction
Date basis: Payment date
Rules: One contributing record per typed ID
Customer accounts · Google Sheets sample
GoHighLevel Customer Payments report template
Inspect customer collections beside current balances after aggregating each financial source at its own grain. Use the customer table to explain contributing records.
Customer Payments
Invented sample · Fixed as of October 13, 2026 · USD · America/Chicago
Change filters to explore the sample locally. No account connection.
Successful live collections$4,450.00Payment date
Known paying customers2Recorded date in selected period
Current amount due$1,400.00As of latest refresh
Payments without contact match0Recorded date in selected period
Collections by customer
View chart data
| Group | Value |
|---|---|
| Ethan Brooks | $2,750.00 |
| Ava Wilson | $1,700.00 |
Current balance by customer
View chart data
| Group | Value |
|---|---|
| Ava Wilson | $500.00 |
| Ethan Brooks | $900.00 |
| Customer | Payments in period | Collected in period | Current invoices due | Current balance |
|---|---|---|---|---|
| Ava Wilson | 2 | $1,700 | 1 | $500 |
| Ethan Brooks | 1 | $2,750 | 1 | $900 |
What the metrics mean
Known paying customers
Record grain: contact
Date basis: Recorded date in selected period
Rules: One contributing record per typed ID
Current amount due
Record grain: invoice
Date basis: As of latest refresh
Rules: One contributing record per typed ID
Payments without contact match
Record grain: record
Date basis: Recorded date in selected period
Rules: One contributing record per typed ID
Required data and boundaries
- Contacts
- Successful live transactions
- Invoices and current balances
A contact can have multiple payments and invoices. Joining first can multiply amounts; a customer match alone cannot allocate a payment to an opportunity.
Payment and invoice facts are aggregated independently before a customer join. One customer with two payments and two invoices never multiplies either amount. Current balances and payment-period amounts use separate date bases.
CRM coverage only · USD; other currencies excluded. Financial units and relationship namespaces are simulated, not provider-validated.
Early access · These public previews use invented records. Join early access to discuss connecting your own GoHighLevel account.
From this sample to a connected report
Choose the template
Use the report whose definitions match the decision you need to make.
Check required inputs
Confirm source access, relevant mappings, history, and any configured goals.
Create the worksheet
The early-access design reuses compatible imports and creates a report worksheet.
Choose freshness
Select source refreshes deliberately. New executions transferring records add usage.
Related report samples
Payments & invoices
Payment Collections
Successful collections, transaction counts and payment types.
Explore sample →Bring your own reporting question.
Make this your reporting workflow.
Explore the samples now. Join the existing waitlist to request connected early access, or discuss a predictable subscription for larger workloads.