Country and state values do not match
Check the country name used by the account and the state or province allowed for that country.
Country and state do not agree
Message looks like
The country and state/province are mismatched, the country is US and the state/province is XX. Please enter a state/province short name that matches the country.
What it means
The state or province value does not belong to the country on the same row, or the Country field is not exposed for the import to fill.
Import context: Customers.
Check this first
Compare the state value with the short names the country allows, and check that Country appears on the Field Mapping page.
Show the steps
Steps for this error
- Compare the state or province value with the short names the selected country allows.
- If the Country field does not appear on the Field Mapping page, open Setup > Customization > Address Form, check the Show box for the Country field, and save.
- Retry one row with an agreeing country and state pair.
Documentation checked September 16, 2026.
A country code is not the expected country name
Message looks like
Invalid country code
What it means
The file uses country codes, and the Import Assistant only accepts country names as NetSuite displays them.
Import context: General imports.
Check this first
Replace codes such as US with the full country names NetSuite displays.
Show the steps
Steps for this error
- The Import Assistant does not accept country codes; the file must use the localized country names.
- Replace codes such as US with the country name NetSuite displays.
- Retry one row.
Documentation checked September 16, 2026.
Related errors
- NetSuite cannot identify the record to import
- NetSuite says the record already exists
- NetSuite cannot match an item in a CSV import
- The item unit or record type does not match
Book a free 30-minute look at your import error
Bring the error and your file to a screen share and I will dig into it live. Thirty minutes is usually enough to find what is wrong and tell you what fixing it takes. Sometimes that settles it on the call; when it does not, you leave with a straight answer instead of a mystery. No cost and no obligation.
An import that keeps failing is often the first visible sign of a larger setup problem. Most of my client work starts exactly here: somebody mid-import, a file that will not load, and nobody on their side to email. If a migration or implementation sits behind this error, that is the work I do every week.