Troubleshooting Sales Tax CSV Import Errors for State Tax Code Matching in Webgility Desktop
This article helps Webgility Desktop users in troubleshooting errors encountered when importing sales tax CSV files into the platform, especially issues involving mismatches between the sales tax code and state name. It provides technical steps to diagnose file content problems and offers best practices such as avoiding unnecessary columns like “city” to ensure successful import and accurate tax configuration.
Overview
This guide provides technical troubleshooting steps for reports of errors while importing sales tax CSV files into the platform, particularly when issues concern matching the 'sales tax code' with the 'state name.' These instructions include diagnosing file content problems and recommended best practices.
Common Error Scenario
You may receive import errors related to sales tax code-state name mismatches, even when the CSV appears to be correctly formatted. Frequently, the inclusion of additional, non-required columns (such as 'city') can lead to these failures.
Typical Symptoms
- Error message indicates issues matching 'sales tax code' and 'state name.'
- The file passes initial schema/format checks but fails during content validation.
- Removing non-mandatory columns enables successful import.
Step-by-Step Troubleshooting
1. Confirm File Formatting
- Verify that the CSV uses the required column headers (sales tax code, state name).
- Ensure column headers match exactly; check for leading/trailing spaces and proper capitalization if relevant.
- Remove any unnecessary columns such as city or county.
- The CSV should include only the columns required by the import tool.
2. Test the Import
- Attempt the import using the simplified CSV file (only required columns).
- If successful, confirm the file preparation for future imports.
Key Takeaways
- Only required columns (sales tax code, state name) should appear in the imported CSV.
- Removing extraneous columns commonly resolves content validation errors.