Skip to main content
AvaTax 26.3.1.0

AvaTax 26.3.1.0 — Enhancements

Material-specific Section 232 support for Cross-Border customers Section 232 processing for Cross-Border customers now supports reporting metal composition by individual material.

Previously, Avalara applied the same metal percentage and country of origin (COO), to all applicable metals, such as steel and aluminum.

With this enhancement, you can submit separate metal percentages using the Section232MetalPercent parameter for each material. Specify the material name in the unit field, for example, steel, aluminum, copper, timber, or lumber.

Each material-specific percentage must include a corresponding MetalCoo parameter with the same unit value.

For example: { “item”: { “parameters”: [ { “name”: “Section232MetalPercent”, “value”: “0.20”, “unit”: “steel” }, { “name”: “MetalCoo”, “value”: “CN”, “unit”: “steel” }, { “name”: “Section232MetalPercent”, “value”: “0.30”, “unit”: “aluminum” }, { “name”: “MetalCoo”, “value”: “CN”, “unit”: “aluminum” } ] } } Avalara calculates Section 232 duty separately for each material percentage. This supports more accurate customs duty assessment for products that contain multiple materials. Parent-child AvaTax code support AvaTax now supports creating child tax codes under existing parent codes. This enables jurisdiction-specific taxability treatment and keeps a scalable, structured tax code framework.

With this enhancement:

  • You can create child tax codes under existing parent tax codes.
  • Child codes can have jurisdiction-specific tax rules.
  • When processing a transaction:

AvaTax first evaluates the rules for the provided TaxCode.

If no rule is found for the sourcing country, AvaTax checks for a mapped parent TaxCode.

If a parent rule exists, AvaTax applies it. If no parent rule exists, Avalara falls back to the default tax code (P0000000).

Child tax codes are restricted to the jurisdictions where they’re defined. They aren’t applied globally.

To ensure backward compatibility, a configurable ParentChildResolutionEffectiveDate parameter determines when hierarchical resolution becomes active. The effective date control ensures that the new enhancement applies only to transactions on or after the activation date. This keeps the historical behavior unchanged. Enhanced parent-child hierarchy for AvaTax code for VAT/GST tax determination We’ve introduced an enhanced parent-child hierarchical structure within AvaTax to improve VAT/GST tax determination across global jurisdictions.

Products and services are often treated differently across countries. VAT/GST legislation can define tax applicability at different levels of specificity. To support these country-specific nuances, AvaTax now applies a back end hierarchical logic that enables more granular tax determination while maintaining consistent product mapping.

This enhancement applies to all supported countries except the United States and Canada.

As a user, this means:

  • No changes are required to your existing AvaTax codes.
  • Your current product mappings remain valid.
  • You’ll see more granular classifications supported over time.
  • Tax determination accuracy is improved at the country level.
  • If there’s no specific content defined for a child tax code in a given jurisdiction, the mapping automatically rolls up to the parent code.

This update operates entirely through back end logic and is designed to enhance VAT/GST applicability without disrupting existing configurations. For example:

  • In France, multigrain bread can be taxable at a reduced rate, while other bread types are exempt.
  • In Belgium, all bread can be exempt.

Under the new hierarchical structure, a customer mapping a product to the relevant AvaTax code automatically receives the correct tax treatment based on the country’s specific legislation.

This enhancement strengthens AvaTax’s global VAT/GST coverage and improves alignment with jurisdiction-specific tax rules. Manage multiple license keys in AvaTax AvaTax now supports multiple license keys, giving you greater control and flexibility when managing your integrations. Previously, all integrations used a single shared license key. Resetting that key could disrupt every connected system. With this update, you can create and assign separate license keys to individual integrations, so changes to one key won’t affect others. You can:

  • Create a default license key for your account
  • Generate multiple secondary license keys for specific integrations
  • Reset the default key without impacting integrations that use secondary keys
  • Revoke individual keys when they’re no longer needed This enhancement helps reduce downtime and simplifies key management across your connected systems. Also, the Avalara Portal now offers a unified integrations experience, making it easier to view and manage integrations relevant to your products and ERP systems. For more information, see Get your license key.