AvaTax helps businesses of all sizes achieve compliance with sales, excise, VAT, GST, and other transactional taxes for millions of products and services across thousands of tax jurisdictions. AvaTax for VAT supports connectivity to custom applications with a well-documented and robust developer toolkit.

Core capabilities

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.

Getting started

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.

How it integrates

What AvaTax for VAT solves

When to use AvaTax for VAT

AvaTax for VAT

Get Started

VAT Reporting helps businesses manage the preparation and submission of value-added tax (VAT) obligations across jurisdictions. It simplifies aggregating transaction data, generating reports, and meeting regulatory filing requirements.

Consolidate transaction data from multiple systems into a unified dataset for reporting.

VAT data aggregation

Generate VAT reports in formats required by local tax authorities.

Report generation

Support preparation and submission to meet jurisdiction-specific reporting requirements.

Compliance workflow support

Manage VAT reporting across multiple countries with consistent workflows.

Multi-jurisdiction coverage

Access API documentation and integration guidance in the developer portal.

Setup involves connecting data sources, configuring reporting workflows, and aligning outputs with jurisdiction requirements.

VAT Reporting integrates with ERP, accounting, and transaction systems to extract and process data for reporting.

APIs enable structured data exchange and support end-to-end reporting workflows.

VAT Reporting

The Amount Threshold To Ignore Transaction

The Amount Threshold To Mark Transaction For Manual Review

The Ap Config Tolerance Type
BATCH or REALTIME

ApConfigToleranceType

RealTime

Batch

Ignore threshold when Vendor Charged Tax is zero

Represents one configuration setting for this account

MaxLines

The unique ID number of the account to which this setting applies

The User ID of the user who created this record.

The date/time when this record was last modified.

The user ID of the user who last modified this record.

The current value of the configuration setting

An account user who is permitted to use AvaTax.

ABCDEFGHIJK

The user id for the user who created this record.

The user id of user who last modified this record.

The unique name for license key per account

The unique ID number assigned to this account.

Test Account

AccountStatusId

Inactive

Active

Test

This account is flagged as a test account and may be temporary.

The account is new and is currently in the onboarding process.
            
             An account is considered new until the account administrator has reviewed and accepted
             [Avalara's terms and conditions](https://www.avalara.com/us/en/legal/terms.html).

AccountTypeId

Regular

Firm

FirmClient

The earliest date on which this account may be used.

If this account has been closed, this is the last date the account was open.

A boolean flag to identify if the account is deleted

Is Saml based authentication used by this account for user to login via AI.

Optional: A list of subscriptions granted to this account.  To fetch this list, add the query string "?$include=Subscriptions" to your URL.

Optional: A list of all the users belonging to this account.  To fetch this list, add the query string "?$include=Users" to your URL.

Specifies a duration for which to grant TSA accounts write access.
See AVT-25316

Descibes a record of an account granting TSA accounts write access.
See AVT-25316

The id of the account to which the TSA access entry belongs to.

The date/time when this TSA access record expires.

Represents a request to activate an account by reading and accepting its terms and conditions.

Set this to true if and only if you accept Avalara's terms and conditions for your account.

Set this to true if and only if you have fully read Avalara's terms and conditions for your account.

Certificate with exemption reason and exposure zone. This is exposed in the URL's `$includes`.

EXPOSURE

Dr. Bob Example

RESALE

Washington

The actual tax code for this certificate.

The actual tax number for this certificate.

The date/time when this certificate was created.

The expected tax code for this certificate.

The expected tax number for this certificate.

The exposure zone where this certificate is valid.

The unique ID number of this certificate.

The date/time when this certificate was last modified.

Model to add specific lines to exising transaction

DocumentType

Represents the different types of transactions that AvaTax can process.

SalesOrder

Represents an estimate, or a sales order, or a quote.
            
             This document type is used before a sale has occurred to estimate the final amount of tax to be paid when the
             sale is completed.
            
             For a sales order, the `companyCode` of the transaction refers to the seller and the `customerVendorCode` refers to the buyer.
            
             This is a temporary document type and is not saved in tax history.

SalesInvoice

Represents a sale that has been finalized.
            
             This document type is used to record a final transaction and calculate the final tax amount with all necessary information.
            
             For a sales invoice, the `companyCode` of the transaction refers to the seller and the `customerVendorCode` refers to the buyer.
            
             This is a permanent document and is recorded in AvaTax.

PurchaseOrder

Represents an estimate, or a purchase order, or a quote.
            
             This document type is used before a sale has occurred to estimate the final amount of tax to be paid when the
             sale is completed.
            
             For a purchase order, the `companyCode` of the transaction refers to the buyer and the `customerVendorCode` refers to the seller.
            
             This is a temporary document type and is not saved in tax history.

PurchaseInvoice

Represents a sale that has been finalized.
            
             This document type is used to record a final transaction and calculate the final tax amount with all necessary information.
            
             For a purchase invoice, the `companyCode` of the transaction refers to the buyer and the `customerVendorCode` refers to the seller.
            
             This is a permanent document and is recorded in AvaTax.

ReturnOrder

Represents an estimate of tax to be refunded if a refund or return is processed.
            
             This document type is used before a customer chooses to request a refund for a previous sale, and it
             estimates the final amount of tax to be refunded when the refund is completed.
            
             For a return order, the `companyCode` of the transaction refers to the seller who is giving the refund
             and the `customerVendorCode` refers to the buyer who is requesting the refund.
            
             This is a temporary document type and is not saved in tax history.

ReturnInvoice

Represents an refund that has been finalized.
            
             This document type is used when a customer chooses to request a refund for a previous sale, and it
             records the final amount of tax that has been refunded when the refund is completed.
            
             For a return invoice, the `companyCode` of the transaction refers to the seller who is giving the refund
             and the `customerVendorCode` refers to the buyer who is requesting the refund.
            
             This is a permanent document and is recorded in AvaTax.
            
             Please note that many jurisdictions around the United States have special rules about how to report refunds
             on a sales tax filing, and some refund transactions may be unable to file immediately due to credit netting
             rules.

InventoryTransferOrder

Represents a proposed movement of inventory from one jurisdiction to another.
            
             This document type is used when physical goods are shipped from one jurisdiction to another, and it
             may cause updates in the tax liability for various jurisdictions.
            
             For an inventory transfer invoice, the `companyCode` of the transaction refers to the owner of the inventory
             that will be moved from one location to another.
            
             This is a temporary document type and is not saved in tax history.

InventoryTransferInvoice

Represents a movement of inventory from one jurisdiction to another that has been finalized.
            
             This document type is used when physical goods are shipped from one jurisdiction to another, and it
             may cause updates in the tax liability for various jurisdictions.
            
             For an inventory transfer invoice, the `companyCode` of the transaction refers to the owner of the inventory
             that will be moved from one location to another.
            
             This is a permanent document and is recorded in AvaTax.

ReverseChargeOrder

Represents a VAT "Reverse Charge" mechanism transaction as defined in the European Union.
            
             A Reverse Charge transaction moves the responsibility for VAT reporting from the seller to the buyer, and
             is intended to allow simplification of commerce and reduce the reporting requirements for sellers that deliver
             goods and services into the single market.
            
             This is a temporary document type and is not saved in tax history.

ReverseChargeInvoice

Represents a VAT "Reverse Charge" mechanism transaction as defined in the European Union.
            
             A Reverse Charge transaction moves the responsibility for VAT reporting from the seller to the buyer, and
             is intended to allow simplification of commerce and reduce the reporting requirements for sellers that deliver
             goods and services into the single market.
            
             This is a permanent document and is recorded in AvaTax.

CustomsInvoice

Represents a VAT "Customs Invoice". 
            
             The user will enter this DocType with a TaxOverride when the VAT and ImportDuty are calculated by Customs at the border, 
             and then these documents are entered later into AvaTax in order to create the balancing entries for VAT and Import Duty.
             
             This is a permanent document and is recorded in AvaTax.

CustomsOrder

Represents a VAT "Customs Order".
            
             The user will enter this DocType with a TaxOverride when the VAT and ImportDuty are calculated by Customs at the border, 
             and then these documents are entered later into AvaTax in order to create the balancing entries for VAT and Import Duty.
             
             This is a temporary document type and is not saved in tax history.

InventoryTransferOutboundInvoice

Represents a proposed movement of inventory from one jurisdiction to another.
            
             This document type is used when physical goods are shipped from one jurisdiction to another, and it
             may cause updates in the tax liability for various jurisdictions.
            
             For an inventory transfer invoice, the `companyCode` of the transaction refers to the owner of the inventory
             that will be moved from one location to another.
            
             This is a permanent document and is recorded in AvaTax.

InventoryTransferOutboundOrder

Not a real document type.
            
             This value is used when querying for documents.  You can specify the type `Any` in some cases to permit the
             system to find any document matching other criteria.

Option to renumber lines after add. After renumber, the line number becomes: "1", "2", "3", ...

document code for the transaction to add lines

Name or ISO 3166 code identifying the country.
            
This field supports many different country identifiers:
 * Two character ISO 3166 codes
 * Three character ISO 3166 codes
 * Fully spelled out names of the country in ISO supported languages
 * Common alternative spellings for many countries
            
For a full list of all supported codes and names, please see the Definitions API `ListCountries`.

Geospatial latitude measurement, in Decimal Degrees floating point format.

Geospatial longitude measurement, in Decimal Degrees floating point format.

Postal Code / Zip Code component of the address.

Name or ISO 3166 code identifying the region within the country.
            
This field supports many different region identifiers:
 * Two and three character ISO 3166 region codes
 * Fully spelled out names of the region in ISO supported languages
 * Common alternative spellings for many regions
            
For a full list of all supported codes and names, please see the Definitions API `ListRegions`.

If you wish to use the address of an existing location for this company, specify the address here.
Otherwise, leave this value empty.
            
The `locationCode` field on this object allows you to quickly use the address of an existing `locationModel` object instead
of having to retype the address completely.
            
This field does not affect the behavior of transactions that must be filed on location-based tax returns.  To specify how a
transaction will be reported on location-based tax returns, please see the `reportingLocationCode` field
on the [CreateTransactionModel](https://developer.avalara.com/api-reference/avatax/rest/v2/models/CreateTransactionModel/) element.

The geospatial coordinates of this address

List of informational and warning messages regarding this address

The resolution quality of the geospatial coordinates

ResolutionQuality

The address resolution quality of an address validation result

NotCoded

External

Location was already geocoded on the request

CountryCentroid

RegionCentroid

Avalara-defined state / province centroid

PartialCentroid

Geocoded at a level more coarse than a PostalCentroid1

PostalCentroidGood

Largest postal code (zip5 in US, left three in CA, etc

PostalCentroidBetter

PostalCentroidBest

Best postal code (zip9 in US, complete postal code elsewhere)

Intersection

Interpolated

Rooftop

Assumed to be rooftop level, non-interpolated

Constant

Pulled from a static list of geocodes for specific jurisdictions

Specify the text case for the validated address result.  If not specified, will return uppercase.

TextCase

Default

Default (casing determined by address standardization setting in Avalara)

Upper

Mixed

Information about all the addresses involved in this transaction.
            
For a physical in-person transaction at a retail point-of-sale location, please specify only one address using
the `singleLocation` field.
            
For a transaction that was shipped, delivered, or provided from an origin location such as a warehouse to
a destination location such as a customer, please specify the `shipFrom` and `shipTo` addresses.
            
In the United States, some jurisdictions recognize the address types `pointOfOrderOrigin` and `pointOfOrderAcceptance`.
These address types affect the sourcing models of some transactions.

VAT transactions support a `goodsPlaceOrServiceRendered` address, which indicates where goods are located or where services 
are rendered. VAT transactions also support an `import` address, which specifies the address of the buyer importing a good 
from another country.

India GST transactions support a `billTo` address, which specifies where invoices and other billing-related information are sent to the buyer.
            
If latitude and longitude information is provided for any of these addresses along with line, city, region, country and postal code information,
we will be using only latitude and longitude and will discard line, city, region, country and postal code information for the transaction.
Please ensure that you have the correct latitude/longitude information for the addresses prior to using the API.
If you provide either latitude or longitude information but not both, we will be using the line, city, region, country and postal code information for the addresses.

The address where invoices and other billing-related information are sent to the buyer. This address type is only for India GST transactions.

The address where the goods are located or where services are rendered. This address type is valid only for VAT transactions.

The address of the buyer importing a good from another country. This address type is valid only for VAT transactions.

The place of business where you accept/approve the customer’s order,
thereby becoming contractually obligated to make the sale.  This address type is valid in the United States only
and only applies to tangible personal property.

The place of business where you receive the customer's order.  This address type is valid in the United States only
and only applies to tangible personal property.

The origination address where the products were shipped from, or from where the services originated.

The destination address where the products were shipped to, or where the services were delivered.

If this transaction occurred at a retail point-of-sale location, provide that single address here and leave
all other address types null.

Replace an existing MultiDocument transaction recorded in AvaTax with a new one.

If the AdjustmentReason is "Other", specify the reason here.
            
This is required when the AdjustmentReason is 8 (Other).

A reason code indicating why this adjustment was made

AdjustmentReason

Indicates the type of adjustment that was performed on a transaction

NotAdjusted

SourcingIssue

A sourcing issue existed which caused the transaction to be adjusted

ReconciledWithGeneralLedger

Transaction was adjusted to reconcile it with a general ledger

ExemptCertApplied

Transaction was adjusted after an exemption certificate was applied

PriceAdjusted

Transaction was adjusted when the price of an item changed

ProductReturned

Transaction was adjusted due to a product return

ProductExchanged

Transaction was adjusted due to a product exchange

BadDebt

Transaction was adjusted due to bad or uncollectable debt

Other

Transaction was adjusted for another reason not specified

Offline

Replace the current MultiDocument transaction with tax data calculated for this new MultiDocument transaction

Replace an existing transaction recorded in AvaTax with a new one.

Replace the current transaction with tax data calculated for this new transaction

Input model for the Advanced Rules bulk import API

Replaces a target value on the transaction with a replacement value

Generic replace rule

Flag to forbid reordering of the rules when all existing rules are updated

Flag to try updating existing rules instead of just append

Output model for the Advanced Rules bulk import API

Rule Execution

Import results for individual rule executions

AvaTax for VAT

FilingAdjustmentModel