FIRE Filing Records Inventory Before a System Transition

Begin with the tax operations calendar and the businesses your team served. List each tax year, legal payer, expected form family, and filing provider or internal transmitter. Include older corrections and replacements, not only the latest original filing cycle.

Compare that expected scope with the folders and records you find. An archive that contains many files can still omit a small client, a discontinued business, or a form handled by another department. Ask the source-system and filing contacts which work may live outside the central directory.

Separate records known to be filed through FIRE from IRIS, paper, SSA, or other workflows. Similar form data does not make the original filing channel interchangeable. Keep unknown channels marked for investigation rather than assigning them from a filename.

Publication 1220 recommends retaining FIRE status emails with associated files or reconstructible data. Build your inventory so the source and outcome remain connected. Publication 1220, retention and file-status guidance.

Assign an internal archive key and record the existing location of each artifact. Capture tax year, payer scope, form, original/correction/replacement category, local filename, IRS-assigned filename, transmission date, observed status, payee count, and the source of that status.

Preserve original filenames and timestamps in the register even if your storage system later needs a clearer display label. Where technically useful, a file hash can distinguish identical copies from different contents with similar names.

Use controlled references rather than copying sensitive data into the inventory itself. A masked payer key can link to the actual legal identity record. Keep personal identifiers and complete return files within the filing archive's access controls.

Mark missing artifacts explicitly. “Status email not located” is more useful than a blank cell that another reviewer may interpret as not applicable.

Fictional example. A team finds three exports for tax year 2025. All three filenames contain the word “final,” but the available filing evidence differs.

The reviewer can substantiate more than “three files exist.” The inventory reveals that ARCH-02 lacks its processed outcome and ARCH-03 needs an explicit original-record connection. Neither gap is solved by renaming the files.

Start with the submitting team or provider, controlled email archive, application records, and authorized system access while available. Ask a specific question: which IRS-assigned filename corresponds to this submitted version, or where is the status result for this transmission date?

Compare at least two identifying details when matching evidence, such as assigned reference and date, then verify the reported payee count against the source. A common payer name or a similar subject line is not enough to establish the relationship.

When a gap cannot be resolved, document what is known, what remains unknown, and who will investigate it. Do not fabricate a status or recreate an email as though it came from the IRS. A reconstructed source dataset should be labeled as reconstructed, with its basis documented.

The tax year 2025 Publication 1220 guidance calls for at least three years of reconstructible return data/status records from the reporting due date, with four-year treatment for returns reporting federal withholding and Form 1099-C. Verify the applicable instructions and your organization's other retention obligations before any disposal decision. Publication 1220, Part A, section 6.02.

A system transition is not a records-destruction event. Keep the archive readable, searchable by payer and year, and connected to the people authorized to use it. Record the software or export format needed to read older artifacts.

The IRS FIRE retirement guidance directs current-year, prior-year, and correction electronic work to IRIS after January 1, 2027. Historical FIRE evidence still matters for identifying what was originally filed. Preserve that context independently of the new system's access setup.