A required field is missing or cannot be written
Find the exact field, its mapping, and the form or sublist that requires it.
- The tax registration value exceeds 20 characters (Customers)
- An expense currency is required (Expense reports)
- The expense-account value exceeds 61 characters (Employees and expense categories)
- A mandatory field is missing (General imports)
- A field cannot be written (General imports)
- A related item is missing its presentation type (Related items)
- An incoming email value is missing or invalid (Leads and prospects)
- A revaluation row is missing a required value (Inventory cost revaluations)
- An existing sales order requires another field (Sales orders)
The tax registration value exceeds 20 characters
Message may mention: vatregnumber, 20.
What it means
The tax registration value exceeds the field's length.
Import context: Customers.
Check this first
Check the value before editing.
Show the steps
Check the required field and mapping
- Find the exact NetSuite field named in the error. Confirm whether it belongs to the record header, a line, or a subrecord.
- Check that it is mapped to the intended CSV column, or to a valid default.
- Inspect the affected records for missing values. A populated column does not mean every record has a value.
- Expand the relevant field group in the mapping tree. A required field can be present there without being visible in the current mapping list.
- If the field belongs to a sublist, make sure the import actually supplies that sublist's data.
For a field that cannot be written, inspect its availability and the import's read-only-field setting. Ignoring a read-only field allows the rest of the import to proceed; it does not make the field editable. Read-only fields
If a custom field is required, provide the intended value first. Turning off mandatory custom-field validation changes which incomplete records the import will accept. It should be an informed configuration choice, not the default troubleshooting instruction. Mandatory custom fields
Documentation checked September 16, 2026.
An expense currency is required
Message may mention: Currency.
What it means
The expense report expects a currency.
Import context: Expense reports.
Check this first
Map the expense currency or choose a default that applies to every affected line. If the expenses genuinely use only the employee subsidiary's base currency, review the report's multicurrency setting.
Show the steps
Check the required field and mapping
- Find the exact NetSuite field named in the error. Confirm whether it belongs to the record header, a line, or a subrecord.
- Check that it is mapped to the intended CSV column, or to a valid default.
- Inspect the affected records for missing values. A populated column does not mean every record has a value.
- Expand the relevant field group in the mapping tree. A required field can be present there without being visible in the current mapping list.
- If the field belongs to a sublist, make sure the import actually supplies that sublist's data.
For a field that cannot be written, inspect its availability and the import's read-only-field setting. Ignoring a read-only field allows the rest of the import to proceed; it does not make the field editable. Read-only fields
If a custom field is required, provide the intended value first. Turning off mandatory custom-field validation changes which incomplete records the import will accept. It should be an informed configuration choice, not the default troubleshooting instruction. Mandatory custom fields
If that looks right
Documentation checked September 16, 2026.
The expense-account value exceeds 61 characters
Message may mention: 61.
What it means
The expense-account value is too long for this field.
Import context: Employees and expense categories.
Check this first
Check that the intended value belongs here before shortening it.
Show the steps
Check the required field and mapping
- Find the exact NetSuite field named in the error. Confirm whether it belongs to the record header, a line, or a subrecord.
- Check that it is mapped to the intended CSV column, or to a valid default.
- Inspect the affected records for missing values. A populated column does not mean every record has a value.
- Expand the relevant field group in the mapping tree. A required field can be present there without being visible in the current mapping list.
- If the field belongs to a sublist, make sure the import actually supplies that sublist's data.
For a field that cannot be written, inspect its availability and the import's read-only-field setting. Ignoring a read-only field allows the rest of the import to proceed; it does not make the field editable. Read-only fields
If a custom field is required, provide the intended value first. Turning off mandatory custom-field validation changes which incomplete records the import will accept. It should be an informed configuration choice, not the default troubleshooting instruction. Mandatory custom fields
Documentation checked September 16, 2026.
A mandatory field is missing
Message may mention: Mandatory field.
What it means
A required value isn't reaching NetSuite.
Import context: General imports.
Check this first
Check mapping and separators.
Show the steps
Check the required field and mapping
- Find the exact NetSuite field named in the error. Confirm whether it belongs to the record header, a line, or a subrecord.
- Check that it is mapped to the intended CSV column, or to a valid default.
- Inspect the affected records for missing values. A populated column does not mean every record has a value.
- Expand the relevant field group in the mapping tree. A required field can be present there without being visible in the current mapping list.
- If the field belongs to a sublist, make sure the import actually supplies that sublist's data.
For a field that cannot be written, inspect its availability and the import's read-only-field setting. Ignoring a read-only field allows the rest of the import to proceed; it does not make the field editable. Read-only fields
If a custom field is required, provide the intended value first. Turning off mandatory custom-field validation changes which incomplete records the import will accept. It should be an informed configuration choice, not the default troubleshooting instruction. Mandatory custom fields
Documentation checked September 16, 2026.
A field cannot be written
Message may mention: permissions.
What it means
This field may be unavailable for import.
Import context: General imports.
Check this first
Check read-only settings.
Show the steps
Check the required field and mapping
- Find the exact NetSuite field named in the error. Confirm whether it belongs to the record header, a line, or a subrecord.
- Check that it is mapped to the intended CSV column, or to a valid default.
- Inspect the affected records for missing values. A populated column does not mean every record has a value.
- Expand the relevant field group in the mapping tree. A required field can be present there without being visible in the current mapping list.
- If the field belongs to a sublist, make sure the import actually supplies that sublist's data.
For a field that cannot be written, inspect its availability and the import's read-only-field setting. Ignoring a read-only field allows the rest of the import to proceed; it does not make the field editable. Read-only fields
If a custom field is required, provide the intended value first. Turning off mandatory custom-field validation changes which incomplete records the import will accept. It should be an informed configuration choice, not the default troubleshooting instruction. Mandatory custom fields
Documentation checked September 16, 2026.
A related item is missing its presentation type
Message may mention: Type.
What it means
The related-item line needs its type as well as the referenced item.
Import context: Related items.
Check this first
Inspect the presentation-item mapping, identify the existing main item, and provide the related item's type. Oracle describes an Update import for this case. The source's example mapping labels are unclear, so check the live field labels before following them literally.
Show the steps
Check the required field and mapping
- Find the exact NetSuite field named in the error. Confirm whether it belongs to the record header, a line, or a subrecord.
- Check that it is mapped to the intended CSV column, or to a valid default.
- Inspect the affected records for missing values. A populated column does not mean every record has a value.
- Expand the relevant field group in the mapping tree. A required field can be present there without being visible in the current mapping list.
- If the field belongs to a sublist, make sure the import actually supplies that sublist's data.
For a field that cannot be written, inspect its availability and the import's read-only-field setting. Ignoring a read-only field allows the rest of the import to proceed; it does not make the field editable. Read-only fields
If a custom field is required, provide the intended value first. Turning off mandatory custom-field validation changes which incomplete records the import will accept. It should be an informed configuration choice, not the default troubleshooting instruction. Mandatory custom fields
Documentation checked September 16, 2026.
An incoming email value is missing or invalid
Message may mention: incoming, email.
What it means
An email value is missing or invalid in this import.
Import context: Leads and prospects.
Check this first
Inspect the mapped email column and the rows being processed.
Show the steps
Check the saved CSV structure
- Inspect the actual saved CSV, not just its spreadsheet display.
- Confirm the file's separator and encoding agree with the import settings.
- Parse quoted fields correctly. A comma inside a quoted description is not another column.
- Compare each parsed row with the header. Identify extra fields, unnamed columns, and duplicate headings.
- Check for totals, notes, and partially populated rows that were not meant to be imported.
- Save a corrected copy and inspect it again before importing.
Completely blank trailing lines and partially populated records are different. Report the actual parsed content rather than assuming that any blank-looking spreadsheet row causes an error. The import's documented size limits are per job, including combined files: 25,000 records or 50 MB. A transaction with several CSV rows is not necessarily several records.
File conventions, separators inside fields
Oracle documents that duplicate column headings can cause the later column's values to be used. For results files, preserve duplicate error columns by position instead of silently overwriting them in a parser. Let the visitor identify the latest error column. CSV preparation tips
Check the required field and mapping
- Find the exact NetSuite field named in the error. Confirm whether it belongs to the record header, a line, or a subrecord.
- Check that it is mapped to the intended CSV column, or to a valid default.
- Inspect the affected records for missing values. A populated column does not mean every record has a value.
- Expand the relevant field group in the mapping tree. A required field can be present there without being visible in the current mapping list.
- If the field belongs to a sublist, make sure the import actually supplies that sublist's data.
For a field that cannot be written, inspect its availability and the import's read-only-field setting. Ignoring a read-only field allows the rest of the import to proceed; it does not make the field editable. Read-only fields
If a custom field is required, provide the intended value first. Turning off mandatory custom-field validation changes which incomplete records the import will accept. It should be an informed configuration choice, not the default troubleshooting instruction. Mandatory custom fields
Documentation checked September 16, 2026.
A revaluation row is missing a required value
What it means
A required value is absent on a processed row.
Import context: Inventory cost revaluations.
Check this first
Check real records and unintended trailing content.
Show the steps
Check the saved CSV structure
- Inspect the actual saved CSV, not just its spreadsheet display.
- Confirm the file's separator and encoding agree with the import settings.
- Parse quoted fields correctly. A comma inside a quoted description is not another column.
- Compare each parsed row with the header. Identify extra fields, unnamed columns, and duplicate headings.
- Check for totals, notes, and partially populated rows that were not meant to be imported.
- Save a corrected copy and inspect it again before importing.
Completely blank trailing lines and partially populated records are different. Report the actual parsed content rather than assuming that any blank-looking spreadsheet row causes an error. The import's documented size limits are per job, including combined files: 25,000 records or 50 MB. A transaction with several CSV rows is not necessarily several records.
File conventions, separators inside fields
Oracle documents that duplicate column headings can cause the later column's values to be used. For results files, preserve duplicate error columns by position instead of silently overwriting them in a parser. Let the visitor identify the latest error column. CSV preparation tips
Check the required field and mapping
- Find the exact NetSuite field named in the error. Confirm whether it belongs to the record header, a line, or a subrecord.
- Check that it is mapped to the intended CSV column, or to a valid default.
- Inspect the affected records for missing values. A populated column does not mean every record has a value.
- Expand the relevant field group in the mapping tree. A required field can be present there without being visible in the current mapping list.
- If the field belongs to a sublist, make sure the import actually supplies that sublist's data.
For a field that cannot be written, inspect its availability and the import's read-only-field setting. Ignoring a read-only field allows the rest of the import to proceed; it does not make the field editable. Read-only fields
If a custom field is required, provide the intended value first. Turning off mandatory custom-field validation changes which incomplete records the import will accept. It should be an informed configuration choice, not the default troubleshooting instruction. Mandatory custom fields
Documentation checked September 16, 2026.
An existing sales order requires another field
What it means
The transaction's stored form may require the field.
Import context: Sales orders.
Check this first
Check that form's rules.
Show the steps
Check the required field and mapping
- Find the exact NetSuite field named in the error. Confirm whether it belongs to the record header, a line, or a subrecord.
- Check that it is mapped to the intended CSV column, or to a valid default.
- Inspect the affected records for missing values. A populated column does not mean every record has a value.
- Expand the relevant field group in the mapping tree. A required field can be present there without being visible in the current mapping list.
- If the field belongs to a sublist, make sure the import actually supplies that sublist's data.
For a field that cannot be written, inspect its availability and the import's read-only-field setting. Ignoring a read-only field allows the rest of the import to proceed; it does not make the field editable. Read-only fields
If a custom field is required, provide the intended value first. Turning off mandatory custom-field validation changes which incomplete records the import will accept. It should be an informed configuration choice, not the default troubleshooting instruction. Mandatory custom fields
For an update to an existing sales order, inspect the form saved with that transaction. The import's selected form may not explain its required fields. For the terms/payment-method conflict, ask which billing outcome is intended before removing either mapping.
Documentation checked September 16, 2026.
Related errors
- Customer type or linked contact data needs attention
- NetSuite cannot read the CSV file or its columns
- Item or custom list translations cannot be imported
- Sales order terms and payment method conflict
Still stuck?
We can help you work through the file, the mapping, and the NetSuite setup behind the error.
Talk to MySuite