For decades, corporate tax departments and accounting professionals have relied on a familiar, if antiquated, year-end reporting rhythm. You extracted vendor data from your Enterprise Resource Planning (ERP) system, fed it into legacy desktop software, generated a fixed-width plain text .txt file,, and uploaded it to the IRS Filing Information Returns Electronically (FIRE) system.
That era has officially ended. The IRS is permanently retiring the legacy FIRE system and replacing it with a modernised, strictly enforced data architecture. Beginning with the upcoming filing season, the IRS mandates that all standard domestic information returns must be routed exclusively through the Information Returns Intake System (IRIS). Simultaneously, foreign entities are required to utilize the Foreign Filer Transmitter Control Code (TCC) Registration System and transmit through the International Data Exchange Service (IDES). This fundamental transition introduces new filing pathways, procedures, and technical standards for both domestic and international filers. The following sections provide a detailed roadmap, outlining the operational changes resulting from the FIRE system’s retirement, the distinctive roles of IRIS and IDES, and the practical implications for compliance in this new regulatory environment.
This is not a simple cosmetic update to an IRS web portal. It is a fundamental, structural paradigm shift in how the United States government ingests, validates, and secures financial tax data. The flat text files of the past are dead. Legacy Transmitter Control Codes are obsolete. In their place is a sophisticated framework that requires structured Extensible Markup Language (XML) schemas, enveloping digital signatures, and AES-256 cryptographic payloads.
For domestic enterprises and foreign filers alike, understanding this transition is the difference between seamless compliance and catastrophic filing failures. As an authorised software developer and transmission platform, Novus Compliance is fully credentialed and equipped to handle Form 1099-MISC and Form 1099-NEC filings under the new IRIS and IDES architectures. Here is a comprehensive breakdown of what the FIRE system retirement means for your organisation, how the new systems operate, and how our platform eliminates the friction of this mandatory transition.
The End of an Era: Why the FIRE System Was Retired
To understand the magnitude of the current transition, we need to examine why the IRS ultimately deprecated the FIRE system. Originally built to transition the IRS away from processing millions of physical paper forms and magnetic media (like floppy disks and CD-ROMs), FIRE was a product of its time. It utilised ASCII fixed-width text files—a format where data is constrained by exact character counts and spaces rather than intelligent data tags.
While FIRE served its purpose, its architecture became a severe bottleneck for modern tax administration. Fixed-width files are notoriously brittle. A single misplaced space, a missing leading zero, or an unexpected special character in a vendor's name could cause an entire batch of thousands of 1099s to fail silently or reject with cryptic error codes. Furthermore, FIRE lacked the modern application programming interfaces (APIs) needed for real-time validation, so businesses often waited days to learn their files were formatted incorrectly.
More importantly, FIRE's security protocols lagged behind modern data-protection standards. In an era of sophisticated cyber threats and global financial data syndication, federal security auditors no longer accepted transmitting plain-text files—even over secure HTTPS connections.
The IRS required a system that could dynamically validate data at ingestion, scale massively, integrate natively with modern corporate financial software, and ensure military-grade cryptography. This multi-year modernisation effort resulted in the dual-gateway approach we face today: IRIS for domestic taxpayers and IDES for foreign reporting entities.
Enter IRIS: The Modernisation of Domestic 1099 Filing
The Information Returns Intake System (IRIS) represents the future of domestic U.S. tax reporting. Unlike FIRE, IRIS is designed around structured data. It completely abandons the fixed-width text format in favour of strict XML schemas.
XML (Extensible Markup Language) uses intelligent tagging to identify data. Instead of relying on a payee's name starting at exactly character position 45 in a text file, XML wraps the data in clearly defined tags, such as <PayeeNameLine1Txt>John Doe</PayeeNameLine1Txt>. This structure allows the IRS to perform instant, automated validations on the data payload. If a required field is missing or a state abbreviation doesn't match the approved federal matrix, the IRIS schema immediately flags the discrepancy.
The IRIS TCC Requirement entails a complete overhaul of the administrative setup for electronic filing. Transitioning to IRIS means that legacy FIRE Transmitter Control Codes are no longer valid for system access. Instead, domestic businesses must submit a new IRIS TCC application. As part of this process, at least two Responsible Officials must authenticate their identities through ID.me, which requires biometric or cryptographic verification and substantiation of valid U.S. Social Security Numbers or Individual Taxpayer Identification Numbers (ITINs).
Once approved, IRIS offers two primary filing methods for domestic entities:
-
The Taxpayer Portal: Designed for smaller businesses, allowing manual data entry or the upload of small, IRS-formatted CSV templates.
-
The Application-to-Application (A2A) API: Designed for high-volume filers and enterprise software platforms, allowing direct XML transmission between corporate servers and the IRS.
However, IRIS is explicitly built around U.S. identity verification. If your organisation is based outside the United States, IRIS presents an insurmountable roadblock.
The IDES Reality: A Distinct Pathway for International Entities
If your organisation is a foreign entity making reportable U.S.-source payments (such as paying U.S.-based independent contractors, requiring a 1099-NEC), you face a unique challenge. Because your compliance officers and corporate leadership likely reside outside the U.S. and lack U.S. SSNs or ITINs, they cannot authenticate through ID.me to complete the standard IRIS TCC application. You are effectively locked out of the standard IRIS portal.
The IRS anticipated this design constraint and built a distinct, separate pathway for foreign reporting entities: The Foreign Filer TCC Registration System and the International Data Exchange Service (IDES).
IDES was originally developed to manage the substantial volumes of encrypted data mandated by the Foreign Account Tax Compliance Act (FATCA), which requires financial institutions worldwide to report information concerning U.S. account holders. For example, global banks must transmit files detailing interest income paid to U.S.-based individuals, which historically involved complex, cross-border data exchanges. The IRS has since expanded IDES to serve as the exclusive transmission gateway for foreign filers submitting standard information returns, such as the 1099-MISC, 1099-NEC, and 1042-S, thereby centralizing and strengthening the oversight of international tax reporting obligations.
Registering for IDES is a complex, multi-stage credentialing process:
-
Foreign Filer ID: The user must first create a Foreign Filer account using foreign identification credentials, generating a 6-character access ID.
-
TCC GIIN: The entity must register its business details (matching its IRS-issued Employer Identification Number) to receive a 19-character Global Intermediary Identification Number (TCC GIIN).
-
Foreign Filer TCC: Once the GIIN is approved, the entity requests a 5-character Transmitter Control Code specifically restricted to IDES.
-
IDES Enrollment: After a mandatory 3-to-6-week IRS database synchronisation period, the entity must enrol in the IDES gateway using a purchased digital certificate from an IRS-approved Certificate Authority.
This process routinely takes three to four months. Consequently, if a foreign enterprise discovers in November that its legacy software is incompatible, it won't have enough time to obtain the necessary IDES credentials before the February 1 deadline. As a result, many foreign filers may face significant compliance barriers and a higher risk of late or failed submissions.
Why Legacy Desktop Software Can No Longer Keep Up
FIRE's retirement has exposed a massive technical gap in the tax software market. For years, businesses relied on low-cost desktop applications (such as 1099Express and similar legacy tools) to handle their reporting. These programs were essentially basic data converters—they took an Excel spreadsheet, mapped the columns, and spit out the flat .txt file required by FIRE.
Because the IRS now requires secure, digitally signed XML files, these legacy tools can no longer be used. Creating a valid file for submission to IDES or through the IRIS A2A system is no longer as straightforward as saving a file in a new format. Instead, it involves more complex technical steps that go beyond basic file conversion.
To successfully transmit a 1099-NEC or 1099-MISC file through IDES, the data must undergo a rigorous packaging pipeline:
-
Schema Generation: The data must be transformed into the exact, form-specific XML schema published by the IRS. A 1099-MISC XML structure is distinctly different from a 1099-NEC XML structure.
-
Digital Signature: The XML payload must be digitally signed with an enveloping XML signature using the transmitter's authorised digital certificate. This proves the data has not been tampered with in transit.
-
Compression: The signed XML must be compressed into a specific ZIP archive format to reduce transmission payload size.
-
AES-256 Encryption: The ZIP archive must be encrypted using Advanced Encryption Standard (AES) with a 256-bit key length, utilising the most current IRS Public Key.
-
Metadata Packaging: A secondary metadata XML file, detailing the transmission parameters, sender routing information, and file sizes, must be generated and zipped together with the encrypted payload to form the final upload package.
If a single character in the XML signature is malformed, or if the AES encryption block utilises an outdated public key, the IDES gateway will immediately reject the entire archive. Legacy desktop software developers have largely refused to invest the hundreds of thousands of dollars required to build this cryptographic infrastructure, leaving their historical users stranded.
Form 1099-NEC and Form 1099-MISC: The Core Reporting Requirements
As enterprises migrate to the new IRS infrastructure, the focus remains on the two most common U.S. information returns for business-to-business disbursements.
Form 1099-NEC (Nonemployee Compensation): Reintroduced in 2020 to separate contractor pay from other miscellaneous income, the 1099-NEC is the primary vehicle for reporting payments of $600 or more made in the course of a trade or business to a person who is not an employee. This includes fees for independent contractors, attorneys, IT consultants, and freelance service providers.
-
The Urgency: The 1099-NEC carries the most aggressive deadline on the federal tax calendar. Both the recipient copy and the electronic IRS transmission are due by January 31 (or the next business day if the 31st falls on a weekend, as it does for Tax Year 2026, pushing the deadline to February 1, 2027). The IRS does not grant automatic 30-day extensions for the 1099-NEC.
Form 1099-MISC (Miscellaneous Information): While nonemployee compensation was removed, the 1099-MISC remains essential for reporting rents, royalties, prize winnings, substitute payments instead of dividends, crop insurance proceeds, and gross proceeds paid to attorneys.
-
The Urgency: Recipient copies are due by February 1, but electronic filers have until March 31 to transmit the data to the IRS via IRIS or IDES.
Missing these deadlines, or failing to file electronically when your filing volume requires it, can trigger significant financial penalties. For example, the IRS says penalties for late or incorrect filings can range from $60 to $310 per form, depending on how long the return is overdue, with a maximum penalty of over $3,783,000 per year for large businesses (IRS, 2023). Consequently, for enterprise filers submitting thousands of forms, these fines can quickly add up to tens or even hundreds of thousands of dollars, while also exposing the organisation to heightened regulatory scrutiny.
How Novus Compliance Bridges the Data Gap
The transition away from the FIRE system doesn't have to cause operational panic for your tax and accounting teams. Novus Compliance was built explicitly to solve the complex data engineering and cryptographic challenges introduced by IRIS and IDES.
As an authorised global tax compliance platform, Novus Compliance holds active, approved transmission credentials. We have already navigated the multi-month IRS vetting procedures, secured the necessary TCC GIINs, and integrated our servers with the IRS cryptographic gateways.
Seamless ERP Integration
We understand that enterprise platforms like SAP, Oracle, and NetSuite don't export data in the precise XML format the IRS requires. Our platform acts as an intelligent translation bridge between your financial system and the IRS. You do not need to alter your internal accounting workflows or hire expensive SAP ABAP developers to build custom XML extractors. We provide intelligent ingestion mapping that automatically normalises your raw SAP or Excel data extracts. Our system handles name splitting, TIN formatting, and state code validation, ensuring your data aligns perfectly with the IRS schema before transmission is ever attempted.
Automated Cryptographic Packaging
Your team does not need to learn how to generate enveloping XML signatures or manage AES-256 public key infrastructure. When you approve your data in the Novus Compliance platform, our automated engine handles the entire IDES and IRIS A2A packaging process. We generate the compliant XML, sign it with our IRS-authorized Certificate Authority credentials, encrypt the payload, and route it directly to the federal intake servers.
Audit-Ready Transparency
Every file Novus Compliance processes generates an official, timestamped IRS processing acknowledgement. When the IRS validates the XML payload and accepts the return, Novus immediately pushes that status report back to your corporate dashboard, providing an immutable audit trail for internal controls and external financial auditors.
Prepare Your Enterprise for the 2027 Tax Season
In summary, the retirement of the FIRE system marks a fundamental transformation in the U.S. tax compliance environment. Organisations can no longer depend on obsolete text-file generators or anticipate timely updates from legacy software providers without incurring considerable financial and compliance risks. Successful adaptation to the IRIS and IDES systems demands rigorous data validation processes, strict conformity to new schema requirements, and the implementation of advanced cryptographic protocols. These changes collectively redefine the operational standards for both domestic and international tax filers, making it essential for enterprises to adopt updated technologies and procedures to ensure continued compliance.
For domestic enterprises navigating the A2A API and foreign filers facing the steep learning curve of the IDES gateway, Novus Compliance provides the complete, end-to-end operational pipeline required to file securely and on time.
The February 1 deadline for Form 1099-NEC leaves no room for error. To protect your organisation from failure-to-file penalties and administrative bottlenecks, contact the Novus Compliance team by emailing contact@novuscompliance.com or visiting our website at www.novuscompliance.com. Schedule a technical walkthrough of our SAP-to-IRIS data bridge, request a live demonstration of our cryptographic packaging engine, and secure your automated filing pipeline well before the year-end compliance rush.
Related Resources
-
IRIS 1099 Filing Guide — FIRE retirement, TCC registration, schema and field reference
-
1099 Filing Software — 1099-NEC, 1099-MISC and correction filing
-
IDES 1099 Filing for Foreign Filers — Foreign Filer TCC, TCC GIIN and IDES transmission
-
A2A 1099 Filing — system-to-system XML transmission for higher volumes
Â
