Skip to main content
Avalara Help Center

Set up and Use Avalara Extractor for Amazon

This article applies to:AvaTax

A warning icon

If you've opted in to the newest Avalara Extractor for Amazon experience, continue to your documentation.

Haven't opted in yet? Use the link we sent you in email to opt in and get access to the latest features.

Use Avalara Extractor for Amazon to automatically sync your Amazon transactions with Avalara.

Learn more about how online marketplaces work in Avalara. For questions about the Amazon Sales Tax Report, refer to the Fulfillment by Amazon documentation maintained by Amazon.

Set up Avalara Extractor for Amazon

Set up Avalara Extractor for Amazon and authorize our connection to your Amazon account. This lets you automatically sync your Amazon transactions with Avalara so they're included on your returns. Syncing includes both Fulfillment by Amazon (FBA) and Fulfillment by Merchant (FBM) transactions.

If you have more than one company with Amazon, add each company to your profile and set up Avalara Extractor for Amazon for each additional company.

Before you begin

Create your initial company.

Steps

  1. In Avalara, go to Settings > Integrations.
  2. Select Connect to Amazon to Sync Transactions.

    Tip icon

    Setting up Avalara Extractor for Amazon for an additional company? Select Add Extractor for Amazon for Another Company.

  3. Select the company in Avalara to which you want to add Amazon transactions.
    The company you select determines which steps automatically display during the rest of Avalara Extractor setup.
  4. Select the transaction date to use as the start date for synchronizing.
    The start date should align with your current filing period requirements and not be earlier than what needs to be included on current returns. The extractor will sync all transactions from that date through the day you set up the extractor.
  5. Continue with setup.
    • If the company you chose does not have marketplace locations and is not enrolled in a Streamlined Sales and Use Tax Agreement (SST) program, select Connect and go straight to step 8.
    • If the company you chose does have marketplace locations and is enrolled in an SST program, select Continue and go straight to step 7.
    • If the company you chose doesn't fit either of the previous descriptions, select Continue and go to step 6.
  6. Make sure we have the right information about where Amazon collects and pays tax for you.
    • If everything looks good and the company you chose is not enrolled in an SST program, select Connect and go straight to step 8.
    • If everything looks good and the company you chose is enrolled in an SST program, select Continue.
    • If you need to change which states are selected, select I Have Opted Out of Amazon Tax Collection for One or More States, make sure only the states for which Amazon collects and pays tax for you are selected, and then select Save.
  7. If the company you chose is enrolled in an SST program, read the information about handling calculation differences and select Connect to accept and finish.
  8. Using the directions that display, get and enter the information you need from Amazon and then select Submit.Your Amazon transactions sync immediately. Depending on how many transactions need to sync, this initial sync can take a while.

    Tip icon

    If you ever change your Amazon MWS Authorization Token, you'll need to pause and delete your current connection and then follow these steps to set it up again.

After the initial sync, your transactions automatically sync daily.

Pause or delete an extractor

You must be an account administrator to pause automatic syncing or delete the active connection entirely.

  1. In Avalara, go to Settings > Integrations.
  2. On the connection you want to pause, turn off the toggle. Automatic syncing of transactions is paused.

    Tip icon

    When you want to begin automatically syncing transactions again, just turn the connection back on. Transactions sync again, including those created during the pause.
  3. To delete the connection entirely, select the Trash Can icon and then select Delete.
    Extractor connections can only be deleted when they're off. 

Find and fix transactions imported by Avalara Extractor with errors

Sometimes there are errors during the daily Avalara Extractor sync. Until you repair them, they won't be shown with other transactions on the Transactions page or included in reports or returns.

Error notifications

If there are errors to be resolved, you're notified in Avalara at Settings > Integrations. A yellow outline displays on the tile for the connection that had the errors, and a Generate a New Error File button is available after you've selected Error Files.

A warning icon

The yellow outline only indicates that there are new transactions with errors since the last error file was generated. No yellow outline does not mean there are no errors.

A connection with new errors
CUP-AVE-IntPg-error.jpg

A connection without new errors

An example showing filtered transactions.png

Steps

  1. In Avalara, go to Settings > Integrations.
  2. Locate your business application or online marketplace with errors and select Error Files.
    The tile expands to show you a button to create a new file and links to download previously created files.
  3. Select Generate a New Error File to generate a .csv file of all errors that aren't in previously created files.

    Tip icon

    Refresh the page if the error file isn't available to download after 30 seconds.
  4. Download and open the spreadsheet.
  5. Fix the errors described in the final column, delete the final column from the spreadsheet, and then save the file.
  6. In Avalara, go to Transactions > Import Transactions.
  7. Drag and drop the import file into the import area.
    Transactions in Avalara are updated with the new information in the spreadsheet, and fixed transactions now appear on the Transactions page.

Errors and resolutions

Error Resolution

Tax override cannot be applied

Nexus is not configured for (State or Region name)

Review Nexus settings for where you're collecting tax.

This also happens when:

  1. An Item Code is mapped to a Tax Code that isn't taxable
  2. The target state doesn't have a state tax
JAAS address validation exception

There's a problem with the addresses involved in the transaction. Check the addresses and make any needed corrections.

Test an address in the Tax Calculator or look up the address with the United States Postal Service.

Example issue: Address Line 1 contains a company name instead of the correct street information.

Invalid or missing State/Province Make sure the address has a state or province and that it's spelled correctly
The city could not be determined Make sure the address has a city and that it's spelled correctly
The address value was incomplete

Avalara needs one of the following to properly calculate tax on an address:

  1. A zip/postal code
  2. Street address, city, and region
  3. Street address and zip/postal code

The address number is out of range

Address not geocoded

Unable to determine the taxing jurisdictions

Invalid Zip/Postal code

Tax calculation cannot be determined. Zip is not valid for the state

Make sure the address number is correct.

Look up the address with USPS and use the most accurate Zip code available.

If the address is for new construction and hasn't been added to the USPS system, use General Delivery on Address Line 2 until the address is available.

Field 'postalCode' has an invalid length

Check the field for errors and typos.

Look up the address with USPS and use the most accurate Zip code available.

 

  • Was this article helpful?