Skip to main content
Avalara Help Center

AvaTax for Communications SaaS Pro testing options

Testing in the SOAP API

Using Test Transactions in Production Account

AvaTax for Communications (AFC) SaaS Pro provides a mechanism for distinguishing test transactions from live transactions. When the account is setup, a 3 byte client code or company identifier is provided to the client.

Please make note of the following:

  • If using Company Identifier, the CompanyIdentifer field in the tax calculation request, identifies a transaction as a live transaction. All other transactions are considered test transactions.
  • If using Commit, set the Commit field to False.

Test Transaction Details

  • Only applies to tax calculations.
  • Request results are returned in response. Will produce the exact same taxes as an equivalent live transaction.
  • Uses the same credentials as a live transaction.
  • Transaction details and results are stored in database.
  • Taxes are not included in compliance reports.
  • Transactions are not included in monthly detailed log report.
  • AFC Customer Portal site can be used to view reports with test transaction results.

Test transactions in the production account can be used for testing:

  • What the taxes would be for a transaction without having the transaction included in compliance filing and other reports.
  • Request/response for tax calculations.

Test transactions in the production account cannot be used for testing any change that impacts the account as a whole. This includes:

  • Testing Compliance Reports
  • Testing Detailed Log Reports
  • Testing Configuration changes
  • Testing Override files, exclusion files, nexus files or bundle files

Using Test Accounts

Clients of AFC SaaS Pro can optionally add one or more test accounts. The test account is identical to a production account in all aspects, but can be managed and configured independently. The URL for test accounts matches the URL used for production accounts.

Test Account Details

  • Has its own unique credentials (username, password, 3 byte Company Identifier).
  • Transactions are tracked and billed separately from the production account.

Test accounts can be used for testing:

  • Any API call / request (tax calculation, lookups or other)
  • Compliance Reports
  • Detailed Log Reports
  • Configuration changes
  • Override files, exclusion files, nexus files or bundle files

Test accounts cannot be used for:

  • Making API calls from a production application. The production application should only make calls to the designated production account.

Testing in the REST Web API

Using Test Transactions in Production Account

This is not recommended. Please reference Using Test Transactions in Sandbox Environment for instructions on setting up an account in the Sandbox environment.

Using Test Transactions in Sandbox Environment

Enter the same Client ID as in the production account.

Test Account Details

Test accounts can be used for testing:

  • Any API call / request (tax calculation, lookups or other)
  • Compliance Reports
  • Detailed Log Reports
  • Configuration changes
  • Override files, exclusion files, or bundle files
  • Can set up and use different Profile IDs.
  • Can test for commit/uncommit.

Test accounts cannot be used for:

  • Making API calls from a production application. The production application should only make calls to the designated production account.

Using Test Server(s)

In some cases, one or more test servers may be needed for clients performing large scale testing. In this case a unique URL will be provided for sending through requests. Contact your Avalara Communications Business Unit sales representative for more information on this option.