This article applies to:AvaTax
If there are any issues with a transaction import, Avalara creates an error file to help you troubleshoot.
- In Avalara, download the transaction import error file.
a. Go to Transactions > Transaction Import History.
b. Click the Download icon in the Errors column for the import file you want to view.
- Open the error file and scroll to the last column to see the error messages and troubleshooting information.
The file lists only the rows that didn't import. Any transactions not listed in the error file were imported successfully.
- Make the necessary changes and then delete the last column (the one with the error messages).
- Save the file with a new name and import it again.
Transaction import error messages
This table lists the error messages you might see in an error file, as well as what they mean and what might have caused them.
What it means
|How to fix it|
|AddressNoStreetError||The ZIP or postal code exists, but there aren't any streets that begin with the same letter in that ZIP or postal code.||Find the transaction that caused the error, and check its addresses for misspellings or typos.|
|AddressRangeError||The address was found, but the street number was not between the low and high range of the post office database.||Find the transaction that caused the error, and check its addresses for misspellings or typos.|
|AddressUnknownStreetError||An exact street name match could not be found. Phonetically matching the street name resulted in either no matches or matches to more than one street name.||Find the transaction that caused the error, and check that it has a valid ZIP code.
Excel sometimes removes leading zeros from ZIP codes. In this case change the cell format to postal code or enter an apostrophe ( ' ) in front of the zero (for example, 01234 would become '01234).
|CityError||The city name or code isn't recognized.||Check for misspellings and typos.|
|CompanyNotFoundError||The company used in the transaction does not exist.||Make sure the company has been added to AvaTax.|
|CountryError||The country name or code isn't recognized.||Check for spelling and typos.|
|CurrencyCodeError||The currency code is either invalid or missing.||Add the correct currency code.|
|DateError||A date is missing or invalid.||Make sure the date follows the format mm/dd/yyyy or yyyy-mm-dd.|
|DestinationJurisdictionError||No jurisdictions were found for the destination address.||Check the destination address for misspellings and typos.|
|DocStatusInvalid||The process code for a transaction you're trying to import is invalid. This often happens because a transaction with an identical doc code already exists.||If you're trying to update the transaction, change its process code to 4. This overwrites the transaction instead of creating a duplicate.
Alternately, you could search for the transaction with the duplicate doc code in AvaTax and edit it.
|DuplicateLineNoError||One or more line numbers are duplicates.||Make sure all line numbers are unique.|
|JurisdictionNotFoundError||Unable to determine the taxing jurisdictions.||Check the state abbreviation for the invalid jurisdiction.|
|LengthError||A field in the GetTax request exceeded exceeds its character limit.||Check that the field doesn't exceed the character limit in the Type (Size) column of the import transactions template.|
|NonDeliverableAddressError||The physical location exists, but there are no homes on this street. One reason might be railroad tracks or rivers running alongside this street, as they would prevent construction of homes in this location.||Find the transaction that caused the error, and check its addresses for misspellings or typos.|
|PostalCodeError||The ZIP or postal code doesn't exist or couldn't be determined for the city/municipality and state/province. This often happens when Excel removes a leading zero from ZIP or postal codes.||Change the cell format to postal code or enter an apostrophe ( ' ) in front of the zero (for example, 01234 would be entered as '01234).|
|RangeError||A value of one field in the GetTax request was outside its required range.||For the transaction that caused the error, check columns like ProcessCode that only accept a small range of numbers. See Guidelines for the import transactions template for a list of accepted values for these fields.|
|RegionCodeError||The two-digit code was not specified or was invalid.||Make sure you're using a valid two-digit state or province code.|
|RequiredError||A required field is missing from the import template.||See Guidelines for the import transactions template for a list of required fields.|
|SSTItemError||SST requires an audit trail of the mapping of item codes (SKUs) to system tax codes. You have to put an item description if you are making it non-taxable.||See Guidelines for the import transactions template for a list of required fields for SST.|
|TaxAddressError||An address is incomplete or invalid.||Verify that both the destination and origin address have, at minimum, one of the following combinations:
|TaxIncludedError||The value of TaxIncluded—whether to include tax in the total sale amount for a line item—isn't valid due to some combination of caps, thresholds, base tax rules, or custom tax rules.||Turn off the TaxIncluded option for the transaction that caused the error. Alternately, check for any custom tax rules that might affect tax calculation for the transaction.|
|TaxOverrideError||A tax override is invalid or applied incorrectly.||Check whether the state has sales tax and that you have nexus in that state.|
|TaxRegionError||The tax region provided in the import file is incorrect.||Check the state abbreviation for the invalid tax region.|
|There were unsupported characters with-in the batch file.||There's an invalid character in the import file. AvaTax stops importing transactions at the line that contains the error.||Check the line the caused the error for the replacement character symbol (�), and delete it.|