Many 1099 CSV formatting errors are introduced after the data itself is already correct. A spreadsheet program may change a date, strip a leading zero, convert a long number to scientific notation, or save a file with a column structure that no longer matches the IRS template.

Use the IRS template for the exact form and tax year

Publication 5717 says the Taxpayer Portal CSV workflow uses IRS-provided templates and that the column count of the uploaded file must match the template. Do not add convenience columns, remove unused columns, or combine different form types into one CSV.

Save the final file as CSV UTF-8

The user guide instructs filers to save the upload as CSV UTF-8 (Comma Delimited) (*.csv). This helps preserve special characters and produces the file type expected by the portal workflow.

Protect TINs, ZIP codes, account numbers and long numeric identifiers

Spreadsheet software can strip leading zeros or convert long values into scientific notation. Publication 5717 specifically gives scientific notation as a risk to check before uploading. Identifier fields should be reviewed in the final CSV, not only in the workbook.

Use MM/DD/YYYY for dates

The IRIS user guide warns that spreadsheet software may format dates in ways the portal does not allow. Recheck date fields after the last save and make sure the final CSV contains the required MM/DD/YYYY representation where the form-specific guide calls for it.

Keep currency plain

Publication 5717 says currency values may contain no more than two digits after the decimal and should not include dollar signs or commas. A visually formatted Excel amount such as $1,250.00 may need to appear in the CSV as 1250.00.

Use the accepted coded values

The general upload guidance lists specific TIN type codes such as SSN, EIN, ATIN, ITIN, QI-EIN and UND. It also says checkboxes should use Y or N, and state or territory values should use the applicable two-letter abbreviations. Country values should follow the designated country abbreviations.

Keep every row the same width as the header

A misplaced comma or quoting problem can cause one record to have more or fewer fields than the header. That can shift every value after the bad delimiter into the wrong column. A structural validator can catch this before the file reaches the portal.

Do not rely on the spreadsheet preview alone

The worksheet view is not the file IRIS reads. The final CSV text is what matters. If you reopen a CSV in Excel, spreadsheet formatting may be reapplied, so recheck the file after every final save.

1099 CSV formatting error FAQs

What CSV format does IRIS expect?

Publication 5717 instructs filers to save the upload as CSV UTF-8 (Comma Delimited) and use the IRS-provided template for the specific form and tax year.

Can I include dollar signs and commas in currency fields?

No. Publication 5717 says currency values may have no more than two digits after the decimal and should not contain dollar signs or commas.

What date format should I use?

The user guide warns that dates should be in MM/DD/YYYY format and that spreadsheet software can convert dates to other formats.

Why is scientific notation a problem?

Spreadsheet software can convert long numbers into values such as 1.045E+5. Publication 5717 specifically warns filers to check for this behavior.

Check the file before you retry IRIS

Use the free validator and troubleshooter to isolate structural and formatting problems before you spend more time in the portal.

Troubleshoot an IRIS CSV ErrorValidate a CSV

Sources: IRS IRIS guidance, Publication 5717, and IRIS known issues and solutions. IRS procedures can change, so verify the current processing-year guidance before filing.