At a Glance
The IRS IRIS Taxpayer Portal supports CSV (comma-separated value) file uploads for bulk 1099 filing. CSV upload is a middle ground between manual data entry and the full A2A API — ideal for filers with moderate volumes who want to avoid typing each form individually. This guide covers the CSV template structure, field formatting rules, common errors, and when CSV upload makes sense vs. using a service like BoomTax.
This article is part of our IRS IRIS Resource Center — your complete guide to the FIRE→IRIS migration.

What Is IRIS CSV Upload?

The IRIS Taxpayer Portal offers three ways to submit information returns: manual form entry (one at a time), CSV file upload (bulk), and the A2A (Application-to-Application) API for automated, high-volume filing. CSV upload sits in the middle — it allows you to prepare your 1099 data in a spreadsheet and upload it in bulk through the IRIS web portal.

The IRS provides downloadable CSV templates for each supported form type. You fill in the template with your payee data, save as CSV, and upload it through the portal. IRIS validates the data, flags errors, and processes accepted records for filing with the IRS.

CSV upload is fundamentally different from the old FIRE system, which required fixed-width text files formatted to Publication 1220 specifications. CSV is more forgiving and easier to generate from common tools like Excel, Google Sheets, or database exports.

CSV Template Structure

Each 1099 form type has its own CSV template with columns specific to that form. While the exact columns vary by form type, all templates share a common structure:

Common Header Columns (All Form Types)

Column Description Format
Payer TIN Your EIN or SSN (the entity filing the form) 9 digits, no dashes (e.g., 123456789)
Payer Name Legal name of the payer/filer Text, up to 40 characters
Payee TIN Recipient's SSN or EIN 9 digits, no dashes
Payee Name Recipient's legal name Text, up to 40 characters
Payee Address Street address, city, state, ZIP Separate columns for each component
Tax Year The calendar year being reported 4-digit year (e.g., 2026)

Form-Specific Amount Columns

Each form type adds amount boxes specific to that form. For example, a 1099-NEC template includes a column for Box 1 (Nonemployee Compensation), while a 1099-MISC template includes columns for Boxes 1 through 18 (rents, royalties, other income, medical payments, etc.).

Field Formatting Rules

Proper formatting is critical for CSV upload success. The most important rules:

TINs (Taxpayer Identification Numbers)

  • Enter as 9 consecutive digits with no dashes, spaces, or formatting (e.g., 123456789, not 123-45-6789)
  • Do not let Excel strip leading zeros — format the TIN column as Text before entering data
  • EINs and SSNs use the same 9-digit format in the CSV

Dollar Amounts

  • Enter as decimal numbers with two decimal places (e.g., 5000.00, not $5,000)
  • Do not include dollar signs, commas, or other currency formatting
  • Zero amounts can be left blank or entered as 0.00
  • Negative amounts are not permitted in most boxes — use corrections to reduce previously reported amounts

Dates

  • Use MM/DD/YYYY format (e.g., 01/31/2027)
  • Date fields are form-specific and not required for all form types

State Codes

  • Use standard two-letter USPS abbreviations (e.g., CA, NY, TX)
  • ZIP codes must be 5 digits or 9 digits (ZIP+4 with no dash)

Ready to discuss your enterprise compliance needs?

Our compliance experts can walk you through a customized solution for your organization.

Common CSV Upload Errors

The following errors cause the most CSV upload rejections in the IRIS portal:

Error Cause Fix
Invalid TIN Excel auto-formatted TIN as a number, stripping leading zeros Format TIN column as Text before entering data
Wrong delimiter File saved with semicolons or tabs instead of commas Ensure CSV uses commas; check regional settings in Excel
Currency symbols in amounts Dollar signs or commas in amount fields Use plain decimal numbers (e.g., 5000.00)
Missing required fields Payer or payee TIN/name left blank Ensure all required columns are populated for every row
Extra columns or rows Spreadsheet contains summary rows, totals, or extra headers Remove all rows except the header and data rows
Encoding issues File saved with UTF-8 BOM or non-ASCII characters Save as standard CSV (UTF-8 without BOM)

CSV Upload Limitations

While CSV upload is convenient for moderate volumes, it has significant limitations compared to the A2A API or using a filing service:

  • Volume caps: The IRIS portal may limit the number of records per CSV upload session. For high-volume filing (thousands of forms), the A2A API or a service like BoomTax is more appropriate.
  • Form type coverage: Not all form types supported by IRIS A2A are available via CSV upload. The portal prioritizes the most common 1099 variants.
  • No automation: CSV upload is a manual process — you must log in, upload, review errors, and confirm. There is no way to schedule or automate CSV uploads.
  • No TIN matching: The IRIS portal does not offer TIN verification against IRS records. A filing service like BoomTax can validate TINs before submission.
  • No recipient copies: CSV upload files returns with the IRS only. You must separately print and mail (or electronically deliver) recipient copies.

CSV Upload vs A2A API vs Manual Entry

Feature Manual Entry CSV Upload A2A API BoomTax
Best for volume 1–10 forms 10–500 forms 500+ forms Any volume
Technical skill None Spreadsheet skills Developer required None
Automation No No Yes Yes (API available)
TIN matching No No No Yes
FIRE file support No No No Yes
Recipient copies No No No Yes
Cost Free Free Free (dev cost) Per-form pricing

When to Use CSV vs. BoomTax

CSV upload through the IRIS portal makes sense if you file a small number of forms (under 100), don't need TIN matching or recipient copy delivery, and are comfortable with spreadsheet formatting. For anything beyond that, a dedicated filing service offers substantial advantages:

  • Existing FIRE workflows: If your systems generate Publication 1220 files, BoomTax accepts them as-is — no need to reformat into CSV
  • Volume: For hundreds or thousands of forms, BoomTax's bulk upload and API handle scale that CSV cannot
  • Error prevention: BoomTax validates TINs, addresses, and amounts before submission, catching errors that the IRIS portal would reject
  • State filing: BoomTax handles Combined Federal/State filing automatically
  • Corrections: If you need to file corrections, BoomTax manages the process end-to-end

Frequently Asked Questions

The CSV templates are available within the IRIS Taxpayer Portal. Log in to your IRIS account, select the form type you want to file, and choose the CSV upload option. The portal provides a downloadable template specific to that form type with all required columns pre-defined.

The IRIS portal supports CSV uploads for moderate volumes — typically suitable for up to several hundred forms per upload session. For high-volume filing (thousands of forms), the IRS recommends using the A2A API or an IRS-authorized filing service like BoomTax.

The IRIS portal supports CSV upload for the most common 1099 form types, including 1099-NEC, 1099-MISC, 1099-INT, 1099-DIV, and others. However, not every form type supported by the IRIS A2A API is available for CSV upload. Check the IRIS portal for the current list of CSV-supported form types.

FIRE required fixed-width text files formatted to Publication 1220 specifications, where every character position had a specific meaning. IRIS CSV upload uses comma-separated columns with headers, similar to a spreadsheet export. CSV is significantly easier to create and debug than FIRE flat files. If you have existing FIRE-format files, BoomTax can accept them directly without requiring conversion to CSV.

Next Steps

Ken Ham
Author
Ken Ham
Founder at BoomTax
View all posts

Passionate about making tax compliance simple so businesses can focus on what matters.

   Help