Recorded invoice line amount
Record grain: invoiceLine
Date basis: Parent invoice issue date; line amount before tax
Rules: No sum of repeated invoice-header totals
Payments & invoices · Google Sheets sample
Inspect invoice line amounts, quantities, and customer detail at invoice-line grain. Use this when header totals are too coarse for the question.
Invented sample · Fixed as of October 13, 2026 · USD · America/Chicago
Change filters to explore the sample locally. No account connection.
| Group | Value |
|---|---|
| Service package | $2,000.00 |
| Consultation | $200.00 |
| Support agreement | $3,650.00 |
| Group | Value |
|---|---|
| Service package | 2 |
| Consultation | 1 |
| Support agreement | 1 |
| Invoice | Item | Quantity | Line amount | Customer |
|---|---|---|---|---|
| i1 | Service package | 2 | $2,000 | Ava Wilson |
| i1 | Consultation | 1 | $200 | Ava Wilson |
| i2 | Support agreement | 1 | $3,650 | Ethan Brooks |
Record grain: invoiceLine
Date basis: Parent invoice issue date; line amount before tax
Rules: No sum of repeated invoice-header totals
Record grain: invoiceLine
Date basis: Recorded date in selected period
Rules: One contributing record per typed ID
Record grain: invoiceLine
Date basis: Recorded date in selected period
Rules: One contributing record per typed ID
Record grain: invoice
Date basis: Recorded date in selected period
Rules: One contributing record per typed ID
Do not repeat the invoice header total on every line when calculating a sum. Embedded lines are bundled with the parent invoice under the planned transfer-counting rules.
Invoice items are a child grain. Partial item coverage is not a full invoiced-business total. Header balances are never repeated across item rows.
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.
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 →Explore the samples now. Join the existing waitlist to request connected early access, or discuss a predictable subscription for larger workloads.