Customizing Avalara AvaTax Tax Calculation Mappings

If you have specified that you want to use the FDN Mappings component to define mappings for Avalara tax calculation, you can view or update the mappings from the Manage External Tax Calculation Mappings link on the Billing Central Task Launcher.

Default Mappings

The following mappings are provided by default.

Default Mappings in Avalara Tax Calculation

Source Object	Source	Target (Avalara)
Billing Document	Company > Code	Company Code
	Document Number	Document Code
	Document Date	Document Date
	Account > Account Extension (first related record) > Tax Exemption Reason	Customer Usage Type
	Account > Exemption Certificate	Exemption Number
	Billing Account or Shipping Account Billing account is used unless a shipping address is specified, when shipping account is used.	Customer Code
	Currency ISO Code	Currency ISO Code
	Company > City, Country, State/Province, Street, Zip/Postal Code	Ship From Address
	Billing Address or Shipping Address (City, Country, State/Province, Street, Zip/Postal Code) Billing address is used unless a shipping address is specified.	Ship To Address
Billing Document Line Items	Document Line	Line Number
	Product or Service > Product Code	Item Code
	Product or Service > Product Extension (first related record) > External Tax Code	Tax Code
	Shipping Account > Account Extension (first related record) > Tax Exemption Reason	Customer Usage Type
	Quantity	Quantity
	Net Value	Amount
	Description or Product Name Product name is used unless line description is provided	Description
	Company Site > City, Country, State/Province, Street, Zip/Postal Code	Ship From Address
	Shipping Address (City, Country, State/Province, Street, Zip/Postal Code)	Ship To Address

Customizing Mappings

If required, you can customize mappings by adding additional mappings or updating the information sources. For example, you can map the Account Name field to the Description field in Avalara, so that account names longer than 50 characters in length are included on the Avalara documents.

Tip:

If you map the Account Name to the Description, you must retain the default Billing Account to Customer Code field mapping, because the Customer Code field is mandatory in Avalara AvaTax.

Additional Properties

An additional Create Transaction property is available for custom mappings.

Overriding Properties

You can override managed mappings or add mappings for additional supported properties.

You can add a custom mapping that contains a unique target field, or for child relationship mappings, a unique target field and target child type. If a managed mapping exists with the same information, the custom mapping overrides it.

If an overridden managed mapping contains child mappings, these are rendered obsolete. If the overriding custom mapping is subsequently removed, the managed mapping and its children are automatically reinstated.

Overridden mappings are displayed in the mappings table with the following information appended to the target:

• (Overridden) indicates that the managed mapping has been overridden by a custom mapping.
• (Parent Overridden) indicates that a parent of the mapping has been overridden by a custom mapping.

For more information about how to add or customize mappings, see Adding Custom Mappings from the FDN Mappings Component.