Context object for rendering tax app templates

Custom fields for the Account object are supported. The Account is the invoice owner of the billing document. Below is an example of how to reference a custom field for an Account:

{{customer["Account.CompanyCode__c"]}}
(CompanyCode__c is a custom field of the Account object.)

Custom fields for the Contact object are supported. The Contact represents the sold-to contact for the billing document. Below is an example of how to reference a custom field for a Contact:

{{customer["Contact.pcode__c"]}}
(pcode__c is a custom field of the Contact object.)

The status of your customer's tax exemption. Enum values are:

• 0: No
• 1: Yes
• 2: PendingVerification

The unique code that identifies a company account in the tax vendor's system. Note:

• For the standard template (tax calculation), this field is at the document_item level: document_item["taxCompanyCode"]
• For the void template (tax void), this field is at the document level: document["taxComapnyCode"]

The same definition as Customer object.

To avoid incorrect addresses generating, set addresses at the document_item level instead of the document level. 

The document can include different addresses at the document item level when you specify a sold-to contact on subscriptions or order line items. Refer to Flexible Billing Attributes for more details. 

For example, to set addresses in the template, use the following syntax:

Document_item["customer"]["address1"]
document_item["customer"]["pcode__c"]

Where address1 is a standard field on customer (represented to Sold To Contact object) and pcode__c is a custom field.

The Liquid tax template allows tax apps to extract BillTo address information. The document_items object is useful for retrieving BillTo information to share with external app vendors.

An example of the syntax is as follows:

<StreetAddress1>{{document_item["billTo"]["address1"]}}
</StreetAddress1>
<StreetAddress2>{{document_item["billTo"]["address2"]}}
</StreetAddress2>
<City>{{document_item["billTo"]["city"]}}</City>

Custom fields of Contact object are supported. The syntax is as follows:

{{document_item["billTo"]["pcode__c"]}}

Wherepcode__c is a custom field on Contact object.

Refers to the Account object, to which the billing document belongs. This is applicable regardless of the document items being from subscription charges or non-subscription charges.

It only has the following fields as standard fields:

• crmAccountId
• currency
• id
• accountNumber

You can also reference custom fields of the Account object. For example:

document_item["invoiceOwner"]["CompanyCode__c"]

Refers to the Account object, which is the subscription owner. This is applicable when document items come from subscription charges.

It only has the following fields as standard fields:

• crmAccountId
• currency
• id
• accountNumber

You can also reference custom fields of the Account object. For example:

document_item["invoiceOwner"]["CompanyCode__c"]

Custom fields for InvoiceItem are supported. Here’s an example:

{{document_item["XXXXX__c"]}}

Where XXXXX__c is a custom field of InvoiceItem.

Note: Custom fields for CreditMemoItem and DebitMemoItem are not supported.

Custom fields for Subscription are supported. Here’s an example:

document_item["Subscription.customFieldName1__c"]

Where customFieldName1__c is a custom field of Subscription.

Custom fields for RatePlanCharge are supported. Here’s an example:

document_item["RatePlanCharge.customFieldName1__c"]


Where customFieldName1__c is a custom field of RatePlanCharge.

Custom fields for ProductRatePlanCharge are supported. Here’s an example:

document_item["ProductRatePlanCharge.customFieldName1__c"]

Where customFieldName1__c is a custom field of ProductRatePlanCharge.