When you import transactions:
- Try a trial import of a few records to increase your familiarity of the import process before importing larger numbers of records
- Adhere to size limits for each data field. Find the size limit for each field in the Type (Size) column of the transaction import formatting table.
- If an import contains errors, an error file lists the rows that didn't successfully import. All rows not listed in the error file were imported
Troubleshoot file imports
To troubleshoot an unsuccessfulimport, examine the resulting error file from the import status screen.
- Go to Transactions > Transaction Import History.
- On the Transaction Import History screen, in the Errors column of the import that you want to troubleshoot, click the Download icon. The Error.csv file downloads.
- Open Error.csv and view the error message in the last column for each record that failed to import.
- Make the necessary corrections to the records, and then delete the last column (the one with error messages).
- Save the file with a new name and import it.
Transaction import error messages
After importing, some records may cause error messages that you need to troubleshoot. import error messages and their probable causes are listed below:
|AddressNoStreetError||The ZIP/Postal Code exists but no streets begin with the same letter in that ZIP/Postal Code.|
|AddressRangeError||The address was found but the street number in the input address was not between the low and high range of the post office database.|
|AddressUnknownStreetError||An exact street name match could not be found and 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 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.|