Review IRS announcements and the current IRS Publication 1220 to understand the current filing year status of the FIRE system and any published sunset or transition timeline communicated by the IRS
Audit all existing FIRE-based filing workflows, identifying the form types being filed, the TCC(s) in use, and the fixed-width ASCII format (as specified in Publication 1220) that FIRE requires
Apply for an IRIS TCC for each filing role (issuer or transmitter) that currently uses a FIRE TCC, completing the e-Services identity-proofing step for the responsible individual
Re-implement data extraction and formatting to produce IRIS-compatible output (CSV or SOAP XML) rather than the Publication 1220 fixed-width format; map each FIRE field position to the corresponding IRIS field name
Run parallel test submissions in the IRIS ATS environment using real-structure but masked payee data to confirm the IRIS submissions are accepted before cutting over production volume
Decommission FIRE-based code paths only after at least one production IRIS filing season has been completed successfully and acknowledgements have been verified
Known gotchas
The IRS has not announced a hard sunset date that is guaranteed to remain fixed; treat any specific date found in third-party summaries as potentially stale and verify against current IRS.gov announcements
FIRE and IRIS TCCs are not interchangeable; a FIRE TCC cannot authenticate to IRIS, so migration requires completing a new TCC application even for filers with decades of FIRE history
Some form types that were accepted by FIRE may have different or delayed availability in IRIS; verify the IRIS-supported form type list before assuming all current FIRE form types are available in IRIS
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp