Navigation
14.13. Filter, Sort, Group, and Summarize Invoice Data
Use transforms to shape invoice data before it appears in tables, summaries, grouped sections, and custom totals.
Transforms shape invoice data before it appears in a layout. They are useful when the invoice has many rows or when billing staff want charges presented in a business-friendly order.
Transforms are optional. Start with a normal line-item table first. Add transforms when the invoice presentation needs filtering, sorting, grouping, aggregation, or computed summary values.
Figure 1: The Transforms tab lets advanced billing admins shape invoice data before it appears in the layout.
What transforms can do
| Transform | Use it for | MSP example |
|---|---|---|
| Filter | Include only rows that meet a condition. | Show only managed services lines in one section. |
| Sort | Order rows by a field. | Sort line items by service period, location, or amount. |
| Group | Combine rows by a shared field. | Group charges by client location or service category. |
| Aggregate | Calculate sum, count, average, minimum, or maximum. | Sum all backup storage overage lines. |
| Computed field | Create a derived value for display. | Build a custom service label from category and period. |
| Totals composition | Assemble rows for a totals display. | Create subtotal, tax, discount, and total lines in a custom order. |
When to use transforms
Use transforms when a normal table is accurate but not readable enough.
Good candidates:
- invoices with many usage rows;
- clients with multiple service locations;
- mixed project, recurring, and support charges;
- contracts that need line items grouped by service category;
- billing summaries that need subtotal rows by group.
Avoid transforms for simple invoices with only a few lines. Simpler layouts are easier to maintain.
Example: group by service category
For a client like Cascade Manufacturing, a detailed invoice may include endpoint care, security monitoring, onsite support, and backup usage. A transform can group line items by service category so the invoice reads like:
- Managed Services
- Security Services
- Backup and Disaster Recovery
- Onsite Support
This helps the client understand what each portion of the monthly bill represents.
Transform checklist
Before saving a layout that uses transforms:
- preview with a sample that includes enough rows to test the rule;
- confirm filtered rows are intentionally excluded;
- confirm sort order matches how clients expect to read the invoice;
- confirm grouped totals match the invoice total;
- document why the transform exists in the layout description or internal billing notes;
- have another billing admin review complex grouping before assignment.