Taxation component behavior
The article outlines the taxation component and best practices to ensure successful integration in Billing.
The Taxation component is available as an individual deployable component in Deployment Manager. You can access it from the Select screen under Compare > Settings. For more information, see Taxation.
Taxation deployment flow and best practices
-
The Connect Tax Engine depends on custom fields. To avoid deployment failures, deploy custom fields before deploying the taxation component.
-
Deployment Manager does not support Open Tax Connectors from the Marketplace.
-
Before deployment, ensure that the tax engine connection is tested and validated under the tax engine setup in both source and target tenants.
-
Taxation components must be deployed in a specific hierarchy. Deployment Manager treats the Tax Engine as the master component, followed by dependent child components.
Deploy the taxation components in the following order:
- Tax companies
- Tax code (dependent on tax engines and tax companies)
- Tax rate (dependent on tax codes)
The following diagram illustrates the deployment flow of the taxation components.
-
Deployment Manager deploys only the tax companies associated with tax engines that are configured in the target tenant. For example, if Source Tenant has Avalara and Connect Tax engines configured and the target tenant has only Avalara, only the tax companies of Avalara will be deployed post deployment and acts as a partial deployment.