Successful live collections
Record grain: transaction
Date basis: Validated payment date
Rules: Successful live transactions in selected currency; gross, refunds separate
Payments & invoices · Google Sheets sample
Bring successful collections and current overdue invoices into the same operating view while keeping their meanings separate. Use the invoice register for collection follow-up.
Invented sample · Fixed as of October 13, 2026 · USD · America/Chicago
Change filters to explore the sample locally. No account connection.
2026-10-01–2026-10-13 · Daily · Payment date
| Group | Value |
|---|---|
| 2026-10-01 | $0.00 |
| 2026-10-02 | $0.00 |
| 2026-10-03 | $0.00 |
| 2026-10-04 | $1,000.00 |
| 2026-10-05 | $0.00 |
| 2026-10-06 | $700.00 |
| 2026-10-07 | $0.00 |
| 2026-10-08 | $2,750.00 |
| 2026-10-09 | $0.00 |
| 2026-10-10 | $0.00 |
| 2026-10-11 | $0.00 |
| 2026-10-12 | $0.00 |
| 2026-10-13 | $0.00 |
| Group | Value |
|---|---|
| 1–30 days | $500.00 |
| 31–60 days | $900.00 |
| 61+ days | $0.00 |
| Invoice | Customer | Due date | Balance | Currency |
|---|---|---|---|---|
| Invoice i1 | Ava Wilson | 2026-10-05 | $500 | USD |
| Invoice i2 | Ethan Brooks | 2026-09-01 | $900 | USD |
Record grain: transaction
Date basis: Validated payment date
Rules: Successful live transactions in selected currency; gross, refunds separate
Record grain: invoice
Date basis: As of latest refresh
Rules: Eligible unpaid balance past due date in selected currency
Record grain: invoice
Date basis: As of latest refresh
Rules: Eligible unpaid invoices past due; one invoice per ID
Record grain: transaction
Date basis: Payment date
Rules: Successful live collections missing explicit opportunity relationship
Gross live collections are not recognized revenue. Current overdue balances are snapshots, and a shared contact does not allocate a payment to a deal.
CRM financial coverage only · USD. Gross collections; $200 recorded refunded separately. 1 other-currency and 1 test transactions excluded. A contact match never attributes a payment to a deal.
Early access · These public previews use invented records. Join early access to discuss connecting your own GoHighLevel account.
Use the report whose definitions match the decision you need to make.
Confirm source access, relevant mappings, history, and any configured goals.
The early-access design reuses compatible imports and creates a report worksheet.
Select source refreshes deliberately. New executions transferring records add usage.
Successful collections, transaction counts and payment types.
Explore sample →Customer collections, current balances and linked payment records.
Explore sample →Explore the samples now. Join the existing waitlist to request connected early access, or discuss a predictable subscription for larger workloads.