Nested table configuration

To configure nested tables in invoice templates, use the following merge fields:

• NestedTable:GroupColumn : Groups information by a merge field, such as Charge Date, UOM (unit of measure) or a custom field.

• NestedTable:ValueColumn : Calculates a subtotal based on a merge field, such as Amount, Quantity, or any other numbered merge field where summing makes sense. For example, you can calculate different subtotals based on all of the following merge fields: {MERGEFIELD "NestedTable:ValueColumn InvoiceItem.Quantity,InvoiceItem.ExtendedPrice,InvoiceItem.TaxAmount,InvoiceItem.AmountWithoutTax" \* MERGEFORMAT} Note that you cannot add any spaces between the merge fields.

  • InvoiceItem.ExtendedPrice

  • InvoiceItem.TaxAmount

  • InvoiceItem.AmountWithoutTax

  • InvoiceItem.Quantity

Sample nested table templates

Download the following sample templates, which you can use to customize your nested table.

• Usage sample nested table template (one level of nesting)

• Invoice Item sample nested table template (three level of nesting)

See Examples: Using Nested Tables in Invoices for detailed explanations about the sample templates.

Notes and considerations

• When the TableFilter:GroupBy merge field is used for grouping invoice items, the invoice item custom fields are populated from the corresponding subscription rate plan charge custom fields. The first invoice item custom field you created corresponds to the first subscription rate plan charge custom field you created, and so on; the names of custom fields are not relevant. Therefore, you must have created invoice item custom fields in exactly the same order as the corresponding subscription rate plan charge custom fields. Additionally, if a subscription rate plan charge custom field is non-indexed, the corresponding invoice item custom field must be also non-indexed.

• Using the TableFilter:GroupBy merge field for the invoice items, credit memo items, and debit memo items in the nested tables is not supported.

• Using the TableFilter:GroupBy merge field for the credit memo items and debit memo items in regular tables are not supported. Therefore, it is recommended to use nested tables for credit memo items and debit memo items.

• Only the following fields are currently supported with nested tables:

  • Usage merge fields and custom merge fields

  • Invoice item merge fields and custom merge fields

  • Tax item merge fields

  • Credit memo item merge fields

  • Debit memo item merge fields