Can You Upload a FIRE File to IRIS? CSV, XML and the Next Step

No. You cannot upload an unchanged FIRE file directly to IRIS. The Taxpayer Portal accepts manual entry or the relevant IRS CSV format. IRIS Application to Application (A2A) uses XML sent through connected software. Choose the filing channel before converting your data.

See the IRS overview of both channels and A2A specifications.

This guide was checked in September 2026 for the transition to tax year 2026 filing in 2027. The Publication 5718 edition currently consulted covers processing year 2026; software teams must verify the edition and releases applicable to their actual transmission.

A file extension is a label. The format determines where each value belongs and how a receiving system reads it. Renaming returns.txt to returns.csv or returns.xml leaves the original contents unchanged.

Ask your payroll or accounts-payable software vendor for the exact export specification, not just “a 1099 file.” A spreadsheet, a PDF recipient copy, and a FIRE export can contain related information while requiring different preparation.

Format references: FIRE guidance, portal templates, and Publication 5718, XML overview.

Start with who will submit the returns. If your team plans to work inside the IRS portal, prepare for that workflow. If a provider or your own software will transmit, agree on its input requirements first.

Check the current portal guide and onscreen limit for the specific CSV upload, submission, or download step. For larger or repeated batches, compare the work involved in portal preparation with a software-based process. Volume alone does not establish whether your specific form and tax year are supported. IRS Taxpayer Portal User Guide.

Building your own A2A connection is a separate project. The IRS lists an A2A TCC, API Client ID, schema package, and successful ATS transmissions in its onboarding steps. If you use a transmitter, establish which responsibilities belong to that provider. IRS A2A setup steps.

1. Preserve the original export

   Keep an unchanged source copy and record its export date, tax year, form types, and payer count. Work on a separate copy. This makes it possible to trace a questionable converted value back to the source.

2. Write down the receiving requirements

   Record the chosen channel, who will submit, and which input that person or service accepts. For the portal, use the matching IRS template. For A2A, confirm the applicable schema version and environment with your software owner.

3. Map and reconcile a representative batch

   Check payer and recipient identities, form types, box amounts, withholding, and any state information. Compare counts and totals before and after conversion. Include unusual records in the review, such as foreign addresses or multiple payers, when they exist in your source.

4. Assign the final submission check

   Name the person who will review the filing outcome, investigate rejected records, and save the final acknowledgment. Keep “converted,” “submitted,” and “accepted” as separate statuses in your tracking sheet.

This workflow is our suggested operational checklist. Check technical versions against the IRS schema and business-rule release table; publication dates, testing dates, and production dates can differ.

Imagine a team exports 80 recipient returns across two payers. The file includes 1099-NEC and 1099-MISC records. Checking only that the output contains “80 returns” can hide a misplaced payer or form type.

Then spot-check individual records and document any conversion exceptions. Matching counts are one useful check; they do not prove that names, identifiers, or amounts are correct. These are invented counts for illustrating a review method, not an IRS acceptance test.

Use these seven questions to make the next step explicit. A “no” should become an assigned follow-up item.

• Have we identified the tax year, form types, and payer groups?
• Do we know who will transmit and which input they accept?
• Have we kept the original source export unchanged?
• Do counts and relevant box totals reconcile by payer and form?
• Have unusual records and conversion exceptions been reviewed?
• Has the software owner confirmed the applicable production requirements?
• Is someone responsible for checking and retaining the IRS outcome?

For software testing, follow the IRS ATS guidance. A local conversion check is separate from IRS testing and production filing.