Tools / CSV Error Translator

Event dates or times are missing or invalid

Check the event’s start and end values, date format, and whether it spans dates.

Browse all errors

Choose the message that matches your import.

• An event date differs from your preferred format (Events)
• An event Date or End Date is missing (Events)
• An event date and time cannot be parsed (Events)
• The event time range is invalid (Events)

An event date differs from your preferred format

Message may mention: preferred, Date.

What it means

An event date does not match the importing user's format.

Import context: Events.

Check this first

Check both date columns.

Show the steps

Check dates, periods, and address values

Dates

1. Check the importing user's date format in personal preferences.
2. Compare the actual CSV text with that format, including the year.
3. If the date is ambiguous, establish the intended date from the source. Do not guess whether 04/05 is April 5 or May 4.
4. For a period or time range, verify both ends and any accompanying year or view.
5. Recheck the saved file after editing it in a spreadsheet.

Use the first check above for this record type. Their requirements are not interchangeable.

Read Oracle's guidance

Documentation checked September 16, 2026.

An event Date or End Date is missing

Message may mention: Date, End Date.

What it means

A date is missing, or an unintended row is being processed.

Import context: Events.

Check this first

Inspect the saved CSV.

Show the steps

Check the saved CSV structure

1. Inspect the actual saved CSV, not just its spreadsheet display.
2. Confirm the file's separator and encoding agree with the import settings.
3. Parse quoted fields correctly. A comma inside a quoted description is not another column.
4. Compare each parsed row with the header. Identify extra fields, unnamed columns, and duplicate headings.
5. Check for totals, notes, and partially populated rows that were not meant to be imported.
6. 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 dates, periods, and address values

Dates

1. Check the importing user's date format in personal preferences.
2. Compare the actual CSV text with that format, including the year.
3. If the date is ambiguous, establish the intended date from the source. Do not guess whether 04/05 is April 5 or May 4.
4. For a period or time range, verify both ends and any accompanying year or view.
5. Recheck the saved file after editing it in a spreadsheet.

Use the first check above for this record type. Their requirements are not interchangeable.

Read Oracle's guidance

Documentation checked September 16, 2026.

An event date and time cannot be parsed

Message may mention: Parse, date/time.

What it means

A date and time cannot be read.

Import context: Events.

Check this first

Check the format and any absent end date.

Show the steps

Check dates, periods, and address values

Dates

1. Check the importing user's date format in personal preferences.
2. Compare the actual CSV text with that format, including the year.
3. If the date is ambiguous, establish the intended date from the source. Do not guess whether 04/05 is April 5 or May 4.
4. For a period or time range, verify both ends and any accompanying year or view.
5. Recheck the saved file after editing it in a spreadsheet.

Use the first check above for this record type. Their requirements are not interchangeable.

Read Oracle's guidance

Documentation checked September 16, 2026.

The event time range is invalid

Message may mention: Start time, end time.

What it means

The time range is invalid for this event import.

Import context: Events.

Check this first

Check both dates and times, including overnight spans.

Show the steps

Check dates, periods, and address values

Dates

1. Check the importing user's date format in personal preferences.
2. Compare the actual CSV text with that format, including the year.
3. If the date is ambiguous, establish the intended date from the source. Do not guess whether 04/05 is April 5 or May 4.
4. For a period or time range, verify both ends and any accompanying year or view.
5. Recheck the saved file after editing it in a spreadsheet.

Use the first check above for this record type. Their requirements are not interchangeable.

If that looks right

Oracle describes a restriction on events spanning dates in this event-import workflow. This does not establish a rule for every NetSuite calendar interaction.

Read Oracle's guidance

Documentation checked September 16, 2026.

Related errors

• NetSuite cannot read the date or posting period
• Numbers or identifiers changed in the CSV
• NetSuite CSV import says an amount is missing
• The vendor bill total disagrees with its lines

Browse all errors

Still stuck?

We can help you work through the file, the mapping, and the NetSuite setup behind the error.

Talk to MySuite