At a Glance
Enterprise organizations with custom FIRE integrations face the most complex migration to IRIS. The shift from fixed-width text to XML, from FTP upload to SOAP API, and from FIRE TCCs to IRIS TCCs affects ERP systems, payroll platforms, custom applications, and vendor data feeds. You can build native IRIS integration (6–12 months) or use BoomTax as middleware (weeks) — keeping your existing ERP exports intact while we handle the IRIS submission.
This article is part of our IRS IRIS Resource Center
— your complete guide to the FIRE→IRIS migration.
Scope Assessment: What's Touching FIRE Today?
Before you can plan an IRIS migration, you need a complete inventory of every system, process, and vendor that currently interacts with the IRS FIRE system. In enterprise environments, FIRE integration is often embedded deeper than anyone realizes. Start with these areas:
- ERP systems: SAP, Oracle, Workday, Microsoft Dynamics — most major ERPs have built-in modules or custom extensions that generate Publication 1220-format files for FIRE submission. Document which modules produce these files, who maintains them, and what customizations have been applied.
- Payroll platforms: ADP, Paychex, or custom payroll systems that generate 1099-NEC, 1099-MISC, or 1099-R forms often output FIRE-compatible files as part of year-end processing. See our payroll provider IRIS guide for industry-specific considerations.
- Custom applications: In-house tools that pull data from data warehouses, apply business rules, and produce FIRE-format output files. These are typically the hardest to migrate because institutional knowledge may be limited.
- Vendor data feeds: Third-party data providers, custodians, or sub-contractors who send you FIRE-format files for consolidation and submission.
- Automated workflows: Scheduled jobs (cron, Task Scheduler, Azure Functions) that generate, validate, and upload files to FIRE. Map every step in the pipeline.
Architecture Changes: FIRE vs IRIS
The technical differences between FIRE and IRIS are fundamental, not cosmetic. Here's what changes at the architecture level. For a broader comparison, see our IRIS vs FIRE comparison.
| Dimension | FIRE (Legacy) | IRIS (New) |
|---|---|---|
| Data format | Fixed-width text (Pub 1220) | XML with published schemas |
| Submission method | Web portal file upload | SOAP-based A2A API or portal |
| Authentication | FIRE TCC + credentials | IRIS TCC + e-Services / ID.me |
| Validation | Post-upload batch processing | Real-time schema validation |
| Error handling | Status file download (24-48 hrs) | Immediate XML error responses |
| Status tracking | Manual portal check | API-queryable status |
| Specification | Publication 1220 | Publication 5717 |
XML Schema Implementation
The biggest engineering lift is the format change. FIRE's fixed-width format meant every field had a precise character position — your code wrote bytes at specific offsets. IRIS XML is self-describing and schema-validated, which is more forgiving but requires a completely different code path. See our IRIS XML format guide for schema details and field mappings.
API Integration
For automated filing, IRIS uses a SOAP-based Application-to-Application (A2A) interface defined in IRS Publication 5717. This replaces FIRE's browser-based file upload with programmatic submission, status checking, and error retrieval. See our IRIS API integration guide for implementation details.
Ready to discuss your enterprise compliance needs?
Our compliance experts can walk you through a customized solution for your organization.
Integration Options: Build vs Buy
Option 1: Build Native IRIS Integration (6–12 Months)
Building IRIS integration directly into your systems gives you full control but requires significant investment:
- Timeline: 6–12 months for design, development, testing, and deployment
- Team: 2–4 developers with XML/SOAP experience, plus QA and a tax SME
- Deliverables: XML generation from your data model, SOAP client implementation, error handling and retry logic, IRIS sandbox testing, TCC application and management
- Ongoing cost: Annual schema updates, IRS specification changes, TCC renewal, monitoring and support
- Risk: IRS schema changes can break your integration; IRIS API availability is not guaranteed during peak filing periods
Option 2: Use BoomTax as Middleware (Weeks, Not Months)
BoomTax functions as a translation layer between your existing systems and IRIS. This approach preserves your current architecture while gaining IRIS compliance:
- Timeline: Days to weeks, depending on integration method
- How it works: Your ERP, payroll, or custom system continues to generate the same FIRE-format output it always has. Send those files to BoomTax via upload, SFTP, or API. BoomTax converts the FIRE flat files to IRIS XML and submits to the IRS on your behalf.
- Integration methods:
- Web upload: Manual file upload through the BoomTax portal
- SFTP: Automated file drop to a secure endpoint
- REST API: Programmatic submission via the BoomTax API
- Zero code changes: No XML generation, no SOAP client, no TCC management, no schema updates
- Ongoing cost: Per-form filing fees — no development or maintenance overhead
Project Planning: Timeline and Milestones
Whether you build or buy, your project plan should account for these milestones. The FIRE shutdown date of December 31, 2026 is a hard deadline.
| Phase | Build (Native) | Buy (BoomTax) |
|---|---|---|
| Discovery & scoping | 4–6 weeks | 1–2 weeks |
| Development / setup | 12–24 weeks | 1–3 weeks |
| Testing (sandbox) | 4–8 weeks | 1–2 weeks |
| UAT & pilot filing | 4–6 weeks | 1 week |
| Production cutover | 2–4 weeks | Same day |
| Total elapsed time | 6–12 months | 2–6 weeks |
Risk Mitigation
Enterprise IRIS migration carries specific risks that should be addressed early:
- TCC approval delays: If building native, apply for your IRIS TCC immediately. The IRS suitability review takes 45+ days and approval is not guaranteed on the first attempt.
- Schema version changes: The IRS may update IRIS XML schemas between now and your go-live. Build your XML generation to be configurable, not hard-coded.
- Peak-period API availability: The IRIS A2A endpoint has experienced slowdowns during filing season. Design for retries with exponential backoff and have a manual fallback plan.
- Vendor readiness: If you depend on third-party data feeds in FIRE format, confirm whether your vendors will continue providing that format or switch to something else.
- Parallel filing: Plan to run both FIRE and IRIS in parallel for Tax Year 2025 (filing season early 2026) as a dry run before FIRE shuts down.
Change Management
The FIRE-to-IRIS migration isn't just a technology project — it impacts tax operations teams, compliance workflows, and vendor relationships:
- Tax operations: Teams accustomed to FIRE's upload-and-check workflow need training on IRIS processes, whether that's the IRIS portal, a new vendor integration, or BoomTax.
- Compliance documentation: Update SOPs, runbooks, and internal controls that reference FIRE. If you're SOC 2 or SOX audited, your controls narrative needs updating.
- Vendor contracts: Review contracts with any vendor that currently submits FIRE files on your behalf. Ensure they're IRIS-ready or transition to a provider like BoomTax.
- State filing: Don't forget state filing requirements — some states require direct filing separate from the federal IRIS submission.
Frequently Asked Questions
Building native IRIS integration typically takes 6–12 months including discovery, development, sandbox testing, and production cutover. Using BoomTax as middleware can reduce this to 2–6 weeks because your existing systems continue generating the same FIRE-format output — BoomTax handles the conversion and IRIS submission.
Yes. If your ERP (SAP, Oracle, Workday, etc.) currently generates Publication 1220-format files for FIRE, you can keep that output exactly as-is. Upload those files to BoomTax, and we convert them to IRIS XML and submit to the IRS. No changes to your ERP configuration, custom code, or data pipelines.
A native IRIS build typically requires 2–4 developers with XML/SOAP experience, a QA engineer, and a tax subject-matter expert. You'll need to implement XML generation per the IRIS XML schema, build a SOAP client per Publication 5717, handle error codes, and complete sandbox testing. Budget for ongoing maintenance as the IRS updates schemas annually.
Absolutely. BoomTax is designed to sit between your existing systems and the IRS. Your ERP, payroll platform, or custom application continues producing the same FIRE-format output. Send those files to BoomTax via web upload, SFTP, or our REST API. We convert to IRIS XML, validate, submit, and return confirmation — all without any changes to your source systems.
Next Steps
Author
Ken Ham
Founder at BoomTax
View all posts
Passionate about making tax compliance simple so businesses can focus on what matters.
BoomTax and its affiliates do not provide tax, legal, or accounting advice. This material has been prepared for informational purposes only, and is not intended to provide, and should not be relied on for, tax, legal, or accounting advice. You should consult your own tax, legal, and accounting advisors prior to engaging in any transaction.
