Avalara Tax Content (ATC) provides centralized, regularly updated tax data to support accurate tax calculation across systems. It delivers jurisdiction-specific tax rates, rules, and taxability logic that integrate with ERP, point-of-sale (POS), billing, and custom applications.

Core capabilities

Deliver consistent tax rates, rules, and jurisdiction mappings across systems using a standardized content source.

Centralized tax content platform

Calculate tax in offline or edge environments without real-time API calls. Receive updated tax content to reflect regulatory changes.

Offline and POS-ready tax support with automated updates

Extend tax content with user-defined fields to align with internal data models, reporting needs, or system requirements.

Flexible data model and customizations

Support multiple industry use cases through specialized content models, including retail, lodging, and car rental.

Industry-specific extensions

Access ATC APIs, configuration endpoints, and integration guidance in the developer portal.

Setup involves configuring business locations, selecting content templates, and integrating tax data delivery into downstream systems.

Getting started

Avalara Tax Content integrates with POS systems, ERP platforms, billing systems, and custom applications by delivering tax data in standardized or system-aligned formats.

Content is delivered through APIs or file-based methods (such as SFTP) and ingested into target systems to support consistent tax calculation workflows.

How it integrates

What Avalara Tax Content solves

When to use Avalara Tax Content

Avalara Tax Content

View API docs

AvaTax automates real-time sales and use tax determination across jurisdictions, enabling accurate tax calculation at the point of transaction. It removes the need to manually maintain tax rates, rules, and sourcing logic while keeping systems aligned with continuously updated tax content.

Calculate sales and use tax during checkout, invoicing, or order processing using jurisdiction-aware logic that reflects current tax rules and boundaries.

Real-time tax determination

Apply consistent tax logic across ecommerce, marketplace, POS, and ERP systems so transactions return accurate totals regardless of where they originate.

Compliance-ready transactions

Validate addresses and map transactions to the correct tax jurisdictions to reduce errors caused by incomplete or inaccurate location data.

Intelligent address and jurisdiction mapping

Support scenarios such as product taxability differences, exemption logic, shipping rules, and temporary tax changes without building custom rule engines.

Complex rule handling

Explore API endpoints, SDKs, integration guides, and MCP capabilities. A 90-day free trial is available for evaluation and sandbox testing.

AvaTax integrates through APIs and SDKs, enabling implementation within commerce platforms, billing systems, ERPs, and custom applications. It supports both direct API integration and broader compliance workflows.

AvaTax

New ECM Customer

Exemption Certificate Management (ECM), also known as CertCapture, helps you collect, validate, and store exemption certificates in one place. It reduces manual work and keeps certificate data accurate and easy to retrieve for audits.

Collect and apply exemption certificates across online, in-store, and offline sales workflows.

Capture certificates across channels

Let customers upload certificates or enter details to generate and submit new ones.

Customer-friendly upload and collection

Validate certificate data at collection so required documentation is complete and audit-ready.

Reduce non-compliance risk

Apply exemptions when valid certificates exist to reduce rebills, credits, and manual fixes.

Improve billing accuracy at scale

Start with the API documentation and integration guides. Choose the path that fits your setup, new implementation or existing ECM account, then follow the integration steps to enable certificate collection and management.

Integrate ECM into checkout, invoicing, and tax calculation workflows to capture and reference exemption data throughout the transaction lifecycle. Use APIs to submit, validate, retrieve, and manage certificate status.

Exemption Certificate Management

Get Started

Getting the duties and taxes right on cross-border sales is critical for your operations and your customers. Avalara AvaTax Cross-Border makes it easy to sell products anywhere in the world by calculating customs duties and import taxes.

Apply Avalara-maintained tax rules and rates tailored to your product category and jurisdictions.

Industry-specific logic

Support tiered pricing, bundled offerings, exemptions, and multi-jurisdiction calculations without custom engines.

Complex scenarios

Stay current with evolving requirements through regularly updated content and configuration options.

Regulatory alignment

Integrate with billing, ERP, and custom apps using REST APIs built for high-volume transaction processing.

Operational scale

Use API documentation, integration checklists, and environment setup guides linked from each product below. Provisioning and access details depend on your Avalara products and onboarding path.

Avalara APIs provide REST interfaces for billing, subscription, ERP, and custom applications. They support scalable tax determination and high-volume processing so you can embed compliance into your existing workflows.

AvaTax Cross-Border

Are you selling throughout the U.S.? If so, getting registered with the states in which you’re obligated to collect and remit sales tax should be one of your first steps.

Registrations

Avalara Managed Returns API enables partners and platforms to embed tax return preparation and filing into their workflows. It helps automate compliance by allowing businesses to manage returns without leaving their systems.

Enable return preparation, filing, and remittance within partner or platform environments without requiring separate interfaces.

Embedded returns workflows

Consolidate transaction data from ecommerce platforms, marketplaces, and business systems into a unified returns workflow.

Multi-channel data aggregation

Prepare returns and manage payments across jurisdictions through integrated, automated processes.

Automated filing and remittance

Enable partners to extend compliance capabilities to multiple customers while maintaining consistent workflows and visibility.

Scalable partner enablement

Access Avalara Managed Returns API documentation and integration guides in the developer portal.

Setup involves configuring data flows, authentication, and mapping transaction data into returns workflows.

Avalara Managed Returns API integrates through APIs with partner platforms, marketplaces, and ERP systems to ingest transaction data and manage return workflows.

It acts as an embedded layer on top of Avalara Returns capabilities, enabling automated compliance within existing systems.

Avalara Managed Returns API

Email addresses (separated by semicolon).

Product Type default should be treated as Retail

TTE type.
Values: `Default` and `Lodging`.

List of AvataxCode IDs to be included.
            
Values: AvaTax API ItemModel.avataxCodeIds.

Indicate the applicablity of the bracket tax.

Indicate the applicablity of the combined rates.

Indicate the applicablity of the combined rates amount.

TTE CombineRatesMaxTierLevel to be included.
Values : 1 or 2.

Indiacate combineRatesTierTax.
<example>false</example>

Indicate Threshold/Tier Tax for rollout.
<example>false</example>

Restrict ATC international special export (lodging, autorental, etc) to specific countries.  This is required if International is set in the TSA Options.

Filter states by country mapping.  This is used for Canada and the US.

Restrict ATC special export (lodging, autorental, etc) to specific states or provinces (Optional, default is all states if this is not provided).

Generate component files by US state, ie CA, CO, HI-ID, etc.  These will be availble for download after the run is complete.

Inject a companyId for lodging for every row in the output.

Indicate the Custom rule override.
<example>false</example>

Indicate the Custom tax override.
<example>false</example>

Indicate the Jurisdiction override.
<example>false</example>

List of ItemGroupsNames to be included.
            
Values: AvaTax API ItemModel.itemGroupsName.

NumberofPostalCodeDigits for postal code.
            
Values: 1, 3, 6.

List of physical locations to be included.
            
Values: AvaTax API LocationModel.locationCode.

Export Platform Name.
            
Values: "TTE", "Aptos", "XStore".

Rounding method to be applied.
            
Values: `RoundHalfUp`, `RoundHalfEven`, `RoundHalfDown`, `RoundUp`, `RoundDown`, `RoundEven`, `RoundCeiling`

List of jurisdictions to be included where a company has nexus without physical locations.
            
Values: AvaTax API NexusModel.jurisCode.

Taxgroupcodetype to identify selected code type.
            
Values: AvaTax API ItemModel.taxGroupCodeType.

List of TaxGroup IDs to be included.
            
Values: AvaTax API ItemModel.itemCode.

Tax on Tax indicator
<example>true</example>

TTE TaxType IDs to be included.
            
Values: `1` - Sales; `7` - Fees

List of jurisdictions where zero rate defaults should be generated.
            
Values: AvaTax API JurisdicitonModel.id.

Defines a range of dates.
            
Expressed as either a range of absolute dates or relative days from when the job is run.

Date range end as an absolute date.
            
For use only with `StartDate`.

Date range end as a relative date.
            
For use only with `RelativeStartDays`.

Date range start as a relative date.
            
For use only with `RelativeEndDays`.

Date range start as an absolute date.
            
For use only with `EndDate`.

DetailLevel type for country entitlements.

Product Type default should be treated as Retail.

Export Platform Name.
            
Values: `TTE`, `Aptos`, `XStore`.

User defined field column type, ie string, integer, decimal, etc.

User defined field label, the column header of this user defined field in the output.

Indicates whether this is the current active record.
This property is read-only and any attempts to set its value will be ignored.
The value is calculated internally based on the record's state.

UDF table name, must be the default of "lodging-all", "autorental-all", or "special-all".

Response detailing references to an entity.

Collection of referring entities by ID and name.

Authorization

Use this service to configure your ATC jobs and schedules.

Avalara Tax Content - Configuration Service

company

state

Query filter to apply to result list, ie "Accomodations".

query

Get all lodging Tax Names and Tax Jurisdiction names for a given state. Optional query filter available.

Retrieve a list of items for a specific company.

If true, checks if the tax is current and returns an extra field (isCurrent) for each record.

validate

List UserDefinedFieldDataset data by company ID.

Create a single UserDefinedFieldDatasetModel record.

UdfKey for all imports in the request, ie "Remittance", this maps to your UDF field name.

udfKey

What to set for approval flag of imported items (default true).  You may want to set this to false if importing from fuzzy match results.

approvalState

Imports multiple UserDefinedFieldDatasetModel.

Check whether you should do a TTE run based on all current Remittance data.
Throws an error if reporting the issue if not ready.

Get all udf ds data for your company by US state.

Get all approved ids to be used as udf dataset values in the lodging run.
Seperator is ',', CustomerSourceField's with commmas will have the comma stripped.

Bulk add/remove approval to multiple UDF Dataset items.

Deletes multiple UserDefinedFieldDatasetModel item by UdfDatasetId.

Include tax/juris not already in Remittance dataset for template.

includeMissing

Rather than using this api, we recommend doing your own mapping to TaxName or TaxJurisdictionName, this is a convenience api only.

There is no guarantee for accuracy, you are responsible for making sure these estimates are correct.

Example `state`: "ID", `searchTerms`: [
 "Idaho State Sales Tax",
 "Pocatello-Chubbuck Auditorium District Tax"
]

These 2 rows will be added to your data, you may need to correct them.

match item 1: "TaxName": "ID State Sales & Use Tax", "TaxJurisdictionName": "IDAHO"

match item 2: "TaxName": "ID Special Sales & Use Tax", "TaxJurisdictionName": "POCATELLO CHUBBUCK AUDITORIUM DISTRICT SP"
.

optional parameter if you know it. Accepted values: ['StateOrProvince', 'Special', 'CountyOrParish', 'PlaceOrCity'].

jurisdictionLevel

Json list of items you want to match to tax names and tax jurisdiction names.

Try to fuzzy match a list of tax names to Avalara tax and tax jurisdiction names.

identifier

Delete a single UserDefinedFieldDatasetModel item by UdfDatasetId.

Retrieve a single record for a company based the ID.

Get a single UserDefinedFieldDatasetModel.

Update a single UserDefinedFieldDatasetModel item.  You may need to DELETE then POST if the tax details are changing.

TTE configurations allow you to configure a combination of tax rates and rules to support what your business sells at each location where you collect and remit tax.
            
Communication records determine who to notifiy when new content is delivered via a job. Specify a unique name and ID for the Communication job, and associate that job with up to 5 email addresses (recipients).
            
Jobs allow you to configure company-specific TTE job settings.
            
Onboarding allows you to specify how complete your company setup is. For each onboarding ID, you can specify whether the following are complete:
* isPOSSetupDone
* isTTESetupDone
* isJobsSetupDone
* isCommunicationSetupDone

Delete a communication record for a company based on its `communicationId`.

Delete a communication record for a given company.

Update an existing TTE configuration, communication, job, or onboarding record for a company based on its `tteId`, `communicationId`, `jobId`, or `onboardingId`.

The TTE, communication, job, or onboarding ID to update.

Retrieve a list of all TTE configurations available for a specific company. This list can be narrowed further by searching based on the `parentTTEId` and/or the `TTEName`.

parentTTEId

searchTTEName

productType

Get Lodging UDF records associated with TTE.

Delete a specific configuration record for a company based on its `tteId`.

Configuration ID (TTE ID) to filter jobs.

configurationId

Create company-specific job settings for your TTE jobs.

Create company-specific configuration settings for TTE jobs.

Delete a TTE job setup for a specific company.

Configuration

Jobs

Tax Region Lookup

URI to retrieve the next set of results, if any.

Token for retrieving the next set of results, if any.

The number of records in this result set.

SampleJob

The run ID to compare against the `latest_run_id`.

The configuration name for this pipeline run.

Specify an ID for the Data Transport Toolkit (DTT) for this job.

Specify an ID for this job. This ID can be used to retrieve a run for a specific job.

Specify the job type.

Values: `Production`, `Test`

The latest run ID to compare against the `base_run_id`.

Specify the output type.

Values: 
- `Full`: Returns full runs for both the base and latest runs.
- `Differences only`: Returns the deltas between the base and latest runs.

productType used to differenciate between ATC products default(retail), lodging, managers.

Specify an ID for this TTE Job Configuration.

Details describing how the run will be executed.

Gets or sets the actual release data
<example>2023-03-06T10:22:19.431Z</example>

Gets or sets the release name
<example>March-2023</example>

Specify how the execution will run.

Values: `manual`, `scheduled`, `automatic`.
            
- `manual` runs the job when it is created.
- `scheduled` allows you to specify a time and date to run a job.
- `automatic` will run a job whenever new content is published.

Represents a configuration for a new Content Extract Pipeline run.

When running a `Differences only` job, specify the base run ID for the job you want to compare this to.

Run configurations for each company to extract data for.
            
Can either be in the form of a fully explicit run configuration
or a configuration ID representing an existing configuration.
networkDetails only needed in case of destination = exavault

Specify the output type.

Values: `Full` for a full run or `Differences only` for changes.

- `Full`: Run a full job. This downloads the all of the associated tax content for use with your point of sale (POS) system.
- `Differences only`: Retrieve just the changes in a job. This creates a file that identifies the differences in tax content between two job runs. 
   You can compare the output between a new and a previous job run or between two previous job runs. Requires `base_run_id` to be set.

Specify an ID for this prebuiltsettings. This ID can be used to retrieve a prebuiltSettings.

Date range end as a relative date.
            
For use only with RelativeStartDays.

Date range start as a relative date.
            
For use only with RelativeEndDays.

Metadata for a new Content Extract Pipeline run.

SampleName

Country codes from the TTE configuration.

DTT Preview status.
            
Values are: `enabled`, `disabled`, `warmup`.

ID for the combined TTE configuration, delivery method, and communication method.

Product type for the pipeline run, 'lodging' for lodging runs.

Status of the pipeline run.
            
Values are: `QUEUED`, `RUNNING`, `FAILURE`, `SUCCESS`.

TTE type for the pipeline run, 'lodging' for lodging runs.

Use this API to start/cancel ATC job runs. You can also use your runId to check job status, get available downloads and download the files.