After the Flexible Billing Attributes feature is enabled, the following billing attributes are available on multiple objects:

• Bill To Contact: The bill-to contact ID is associated with a subscription or order line item. For example, you can specify Steve Lee as the bill-to contact of the invoice owner for a subscription, instead of using the default bill-to contact of the account. If not specified, the default bill-to contact of the invoice owner will be used.
• Sold To Contact: The sold-to contact ID is associated with a subscription or order line item. For example, you can specify Steve Lee as the sold-to contact of the subscription owner for a subscription, instead of using the default sold-to contact of the account. If not specified, the default sold-to contact of the subscription owner will be used.
• Ship To Contact : The ship-to contact ID is associated with a subscription or order line item. For example, you can specify Steve Lee as the ship-to contact of the subscription owner for a subscription, instead of using the default ship-to contact of the account. If not specified, the default ship-to contact of the subscription owner will be used. This field is available only if you have turned on the Ship To Contact feature. You can turn on the feature through the self-service interface for Feature Management.
• Currency: The currency of the subscription or order line item.
• Payment Term: The name of the payment term is associated with a subscription or order line item. For example, Net 30 indicates that payment is due 30 days from the invoice date. The payment term determines the due dates of invoices.
• Invoice Template ID: The ID of the invoice template is associated with a subscription or order line item.
• Sequence Set ID: The ID of the sequence set is associated with a subscription or order line item. For example, you can specify a sequence set ID for a subscription, instead of using the ID of the sequence set assigned to the account.
• Communication Profile ID: The ID of the communication profile is associated with a subscription or order line item.
  Note:

  • Communication Profile support was introduced later; historical invoices do not have communicationProfileId and are not backfilled.
  • When a charge has been billed on multiple invoices with different billing attributes (for example, some with communicationProfileId and some without), later cancel/remove actions can require multiple credit memos for the same charge.

During the generation of billing documents, including invoices and credit memos, the latest billing attributes at the subscription level or order line item are always used. To learn more information about a common use case, see Renew subscription early and update bill-to contact and payment term.

The Zuora UI, API, data source, AQuA, Data Query, and Object Query are enhanced to support the preceding billing attributes. The following table lists the detailed changes introduced in the Flexible Billing Attributes feature.

Bill To Contact and Sold To Contact - At the Subscription level

Bill To Contact and Sold To Contact - At the Invoice level

Bill to Contact

• Used as a grouping attribute for invoice consolidation.

• Explicitly set at invoice header level from subscription-level Bill To or invoice owner's default Bill To (when billing rule is enabled).

• Invoice.BillToContactId field is displayed by default (when subscription-level Bill To is set or billing rule is enabled).

SoldTo Contact

• It is not used for invoice grouping.

• Inherited from subscription or order line item and stored at invoice item level for tax calculation.

• Invoice.SoldToContactId field is not populated (remains null).

• Invoice UI displays the account-level Sold To and not the subscription-level Sold To field.

Ship-to and sold-to contacts in tax calculation

When using ship-to and sold-to contacts in tax calculation, keep the following notes in mind:

• You can only specify the contacts of the subscription owner as the ship-to or sold-to contact at the subscription level. If the ship-to or sold-to contact is specified at the subscription level, tax calculation for billing documents always use the subscription owner’s tax exemption information, VAT ID, and Tax Company Code.
• The ship-to contact takes precedence over the sold-to contact for tax calculation. If you specify a ship-to contact at the subscription level, that contact will be used for tax calculation. Specifying a ship-to contact at the subscription level is optional. If no ship-to contact is specified, the sold-to contact at the subscription level will be used, regardless of whether a ship-to contact is specified at the account level.
• The ship-to and sold-to contacts at the subscription level work with the billing rule called Calculate taxes using information from Customer Account of: Subscription Owner | Invoice Owner as follows:
  • If the ship-to or sold-to contact is specified at the subscription level, tax calculation depends on the ship-to or sold-to contact, regardless of the setting of this billing rule.
  • If no ship-to or sold-to contact is specified at the subscription level, tax calculation depends on the setting of this billing rule.
• During billing document generation, the latest billing attributes at the subscription level are always used. The invoice items or credit memo items generated from subscriptions always link to the latest ship-to or sold-to contacts.

Data Model Behavior

Typical scenarios