Sales order terms and payment method conflict
Choose the intended billing outcome before changing either the terms or payment-method mapping.
Terms and payment method conflict
Message may mention: terms, paymentmethod.
What it means
Conflicting billing instructions were mapped.
Import context: Sales orders.
Check this first
Choose the intended billing path.
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
- A required field is missing or cannot be written
- NetSuite cannot read the CSV file or its columns
- Item or custom list translations cannot be imported
Still stuck?
We can help you work through the file, the mapping, and the NetSuite setup behind the error.
Talk to MySuite