IRIS CSV Template Checklist Before Upload

In the portal's Upload CSV with Form Data workflow, select the appropriate form template and obtain the associated formatting guidance. Keep the tax year and form type visible in your preparation notes. Publication 5717 describes one form type and one tax year per CSV upload. Publication 5717, section 3.5.

Preserve the entire template header, including unused columns. Do not rename columns to your accounting system's field names, remove columns that look empty, or reuse an old file without checking its layout. The source-to-template mapping belongs in a separate working sheet.

The IRS publishes tax year 2025 template formatting guidelines as a ZIP of form-specific PDFs. A guideline for a different form or year is not a substitute. If the intended year's template is unavailable, resolve the supported workflow before preparing a production upload.

Build a short mapping sheet from the source report to the required template fields. Match payer and recipient identifiers to their correct type fields. Match business-name versus individual-name data to the corresponding name-type selection. Keep optional fields and conditionally required fields distinct.

For amounts, compare the actual tax box meaning. An accounting column named “total paid” does not establish which information-return box should receive it. Resolve the reporting question using the form instructions and business records before solving CSV formatting.

Keep payer and recipient address fields separate. A mailing address copied from the wrong party can pass a basic format check. Likewise, an account number should identify the intended account or record under the applicable instructions, not be invented merely to fill a cell.

Fictional example, selected columns only. This excerpt uses labels from the TY2025 NEC guidance, omits many required columns, and must not be uploaded. It shows why inspecting saved text helps.

Form Type,Tax Year,Payer Business or Entity Name Line 1,Recipient ZIP/Postal Code,Box 1 - Nonemployee Compensation
1099-NEC,2025,Example Harbor Company,02108,1250.50

The recipient ZIP remains 02108, including its leading zero. The amount remains 1250.50, with no currency symbol or thousands separator. The record stays on one logical line. In the actual template, every column must remain present in its original position, even where the corresponding value is blank.

Publication 5717 recommends CSV UTF-8 (comma delimited) and discusses text formatting, spreadsheet conversion, extra separators, and embedded line breaks. Check the saved file after export with a text viewer or a CSV parser that does not rewrite it. Publication 5717, successful-upload tips.

Confirm that each data row has the expected number of fields. A comma inside a value must be represented according to CSV quoting rules, but valid CSV quoting cannot make a character acceptable if the IRS field guidance prohibits it. Check both the file structure and the individual field rule.

Review leading zeros, formatted identifiers, dates where applicable, blank cells, checkbox values, and amounts. Use the specific field guide for allowed characters and required values. Do not apply one blanket punctuation-removal rule across names, addresses, and numeric fields.

Reopening and resaving through spreadsheet software can change earlier formatting. If you edit, inspect the resulting saved file again and keep the final reviewed version clearly identified.

Count data rows separately from the header, and compare them with the intended batch. Sum each relevant box separately before upload. After the import, compare the number of forms created and any reported errors with the source count.

The February 2026 portal guide permits up to 250 forms in a CSV, excluding the header. Its submission/download sections still describe 100-form operations, while the general IRS overview says 100 at a time. Use the limit for the specific operation and follow the current portal instructions. Do not treat the CSV size as a universal limit for every action. Publication 5717, sections 3.5 and 3.6.

For a larger preparation set, create controlled files with distinct labels and a row-count crosswalk. Check that every intended return appears once across the files. Splitting the work should not change its payer identity, form, or year.

Keep the exact message and identify whether it concerns the file structure or specific fields. First resolve a malformed file that prevents row validation; then investigate the named field and source record. Avoid repeated uploads of unchanged data.

If the portal appears to stall, check whether forms were added before repeating the import. Record what you actually see in Unsubmitted Forms. An upload message alone does not tell you that the forms were submitted to the IRS.

After correction, save and inspect a new final version, reconcile its rows and totals, and proceed through portal review and submission. Keep the reviewed CSV as the source artifact for the receipt and processed result that follow.