A Credential Transition Register for FIRE-to-IRIS Projects

List each legal organization, form family, source-data process, and historical transmitter arrangement. Include prior-year corrections, provider dependencies, and records that must remain available after routine FIRE work ends.

For each workflow, choose the planned destination: an authorized portal team, the organization's direct A2A software, or a provider that transmits on its behalf. The destination determines which access questions the register needs to answer.

Use stable internal labels for the workflow and credential records. Keep actual codes and sensitive access details in their controlled locations. The shared transition sheet should tell a reviewer where verified evidence exists without becoming a repository of passwords or private keys.

Do not overwrite the old system label with “IRIS” or copy a FIRE code into a new-code field. A historical relationship can stay useful even when the new transmitter is a different organization.

Record the exact observed application state and its date, then use a separate internal checklist for the work still needed. A completed application can coexist with unfinished data preparation or software testing. Conversely, a reviewed source file can exist while access is pending.

For direct A2A, track the applicable TCC, API Client ID, schema package, and ATS obligations with their actual responsible party. The IRS onboarding sequence and ATS guidance establish that additional work beyond finding a code is involved.

For a provider arrangement, record the confirmed division of responsibilities rather than assuming your organization performs every integration step. Identify who transmits, which source inputs are supported, and how detailed filing outcomes will be delivered.

Keep test and production evidence distinct. Do not mark a test result as production authorization or describe an unperformed test as complete because the process is documented.

Fictional example. Example Property Group has verified its legacy FIRE application and located the prior NEC status archive. It plans to use a provider for tax year 2026 returns filed in 2027. The project spreadsheet initially says “credentials complete” because the old TCC record was found.

The two-system register reveals the missing work. The legacy side is documented, but the provider has not yet confirmed the unusual source-data cases or the method for delivering final acknowledgments. Those are operational dependencies in the new arrangement, even if no customer-owned direct A2A integration is planned.

The project changes its internal work state to “legacy record verified; new workflow confirmation pending.” It assigns a provider discussion with concrete questions and keeps the historical archive intact. This label is an internal planning description, not an IRS application status.

The IRS's August 24, 2026 notice gives November 9 as the final date for changes to IR applications and November 19 at 3 p.m. Eastern as the final FIRE submission time. Mark those separately from the new workflow's internal target dates. IRS transition notice.

The FIRE webpage also contains broader December maintenance language. Use the explicit dated milestone for planning and verify current instructions before making a change, rather than assuming that the later prose extends the cutoff.

Before local decommissioning work, identify open legacy filing questions and the records needed to answer them. Preserve controlled access to the archive and the responsible contact chain. Closing a local integration or removing an employee's access is different from deleting filing evidence.

At each project check, open a sample evidence reference and confirm that it supports the claimed state. An acceptance letter should match the correct entity; an application screen should show the intended method; a test report should describe the actual environment and scope exercised.

List uncertainty explicitly: missing original-system evidence, unconfirmed provider support, an outstanding signature, or a pending software test. Give each a next action and responsible person. Avoid a single green cell that hides a partially completed arrangement.

When the new workflow is ready, record the scope it supports and the person responsible for reviewing the first real filing outcome. Keep the old register available for historical questions. The transition record should explain both where filing is going and how the organization will still understand what happened before.