If there are any issues with a transaction import, AvaTax Update creates an error file that helps you troubleshoot errors.
- In AvaTax Update, 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 the troubleshooting information.
The file lists only the rows that did not import. All rows 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
When you import transactions, an error file is created that includes the rows did not import successfully and the associate error messages. Here what the error messages mean and their probable causes:
What it means
|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.|
|AddressRangeError||The address was found, but the street number was not between the low and high range of the post office database.|
|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.|
|CityError||The city name or code was not recognized. Check the spelling.|
|CompanyNotFoundError||Company used in the transaction does not exist.|
|CountryError||The country name or code was not recognized.|
|CurrencyCodeError||Currency code is either invalid or missing. Add the correct currency code.|
|DateError||A required date was not submitted or was invalid. Dates must be submitted in MM/DD/YY format.|
|DestinationJurisdictionError||No jurisdictions were found for the destination address.|
A transaction with an identical doc code already exists.
To fix this error, sign in to AvaTax Update and click Transactions. Select Filters. Under Document Code, type the doc code of the transaction you're trying to import or calculate. Click Apply.
Select the transaction with the duplicate doc code. If the existing transaction is the same as the transaction you're trying to import or calculate, don't add the new transaction. If the two transactions are different, change the doc code on the transaction you're adding.
|DuplicateLineNoError||One or more line numbers are duplicates. All line numbers must be unique within the document.|
|JurisdictionNotFoundError||Unable to determine the taxing jurisdictions. To resolve, verify the state abbreviation.|
The maximum length of a field in the GetTax request is exceeded. Verify the maximum length 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.|
The ZIP/Postal Code does not exist and could not be determined by the city/municipality and state/province.
If the ZIP/Postal Code starts with a zero, Excel may remove it, which causes an address error. To resolve this, 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 not within the required range of values.|
|RegionCodeError||The two-digit state code was not specified or was invalid. To resolve, verify the state abbreviation.|
|RequiredError||One of the required fields is missing in the GetTax request. For a list of required fields, read format the important transactions template.|
|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. To resolve, read format the important transactions template.|
Address is incomplete or invalid.
|TaxIncludedError||TaxIncluded is not supported in combination with caps, thresholds, or base rules.|
|TaxOverrideError||Invalid/Wrong Tax Override or TaxOverride is applied in an invalid way. Verify is the state has sales tax and that you have nexus in that state.|
|TaxRegionError||Invalid TaxRegion is provided in the import file. To resolve, verify the state abbreviation.|