The Best Way to File on IRIS in 2026: An Honest Comparison

You Are Choosing a Path, Not a Brand

Before comparing logos, get the shape of the decision right. Every filer who reaches IRIS does it through one of three doors, and most of the cost, effort, and risk in your filing year is decided the moment you pick the door — not the software badge on it.

The first door is the IRS Taxpayer Portal, the free web application the IRS describes in Publication 5717. You log in, key returns in by hand or upload one of the IRS CSV templates, and the portal builds the submission for you. It costs nothing and needs no code, but it was designed for modest volumes and manual review, not for tens of thousands of records or for a team filing across many clients.

The second door is direct A2A, the Application-to-Application channel specified in Publication 5718. Here your own systems generate compliant IRIS XML, sign a JWT, and POST the transmission straight to the IRS endpoint, then poll for an acknowledgement. It scales to very large filings — the IRS accepts up to 100 MB per submission — but it is a software project, complete with schema validation, the business-rule catalog, and a mandatory testing phase before you may touch production.

The third door is commercial filing software, the category this post is really about. A vendor like BoomTax or e1099f has already built the A2A integration, already passed the IRS Assurance Testing System (ATS), and already holds a Transmitter Control Code. You hand them data; they hand back a Receipt ID. The fee buys you everything the second door makes you build yourself — which is why the real comparison is less “which brand” and more “build it, do it by hand, or buy it.”

Portal vs Direct A2A vs Software, Side by Side

The table below lines up the three paths on the dimensions that actually decide a filing season — cost, the volume each can realistically carry, who has to write and maintain code, how corrections and Combined Federal/State Filing are handled, and how long it takes to be ready to file. The highlighted row is the one filers most often underestimate, because it governs your earliest possible filing date no matter which path you choose.

Notice what the table is really saying: the portal and direct A2A are free in dollars but expensive in time and engineering, while software is the reverse. The deciding factor in the highlighted row — time to first filing — is not the software at all. It is the IRS authorization process that stands behind every self-managed path, and it is the single biggest reason a January filer ends up choosing a vendor.

The Hidden Cost Everyone Forgets: The TCC Clock

Whether you file through the portal or build your own A2A integration, you cannot transmit a single live return until the IRS has issued you a Transmitter Control Code — and that code does not arrive on demand.

Getting a TCC means applying through the IRS IR Application for TCC, naming Responsible Officials who have completed identity verification, and then waiting out the IRS suitability review, which can run roughly 45 business days. That review is invisible on every pricing page, but it is the part of the calendar that actually determines whether you make the deadline. A filer who decides in early January to “just do it directly” can discover that their own TCC will not clear until well after the returns were due.

This is also where commercial software changes the math rather than just the price. Because a vendor like e1099f already holds an approved TCC and has already passed ATS, the wait disappears for you: the transmission goes out under the vendor’s authorization while you simply supply the data. If you have months of runway, the wait is a one-time annoyance; if you have days, it is the whole decision. For the deeper mechanics of obtaining your own code, the full TCC application walkthrough covers each step and the suitability review in detail.

BoomTax vs Filing Direct: Where the Trade Actually Bites

The most common head-to-head readers ask about is a hosted filing tool such as BoomTax against rolling your own IRIS submission. On paper the direct route looks cheaper, because the IRS charges nothing for A2A. In practice the comparison is not vendor-fee versus zero — it is vendor-fee versus the salary, schedule, and risk of building and maintaining a compliant transmitter yourself, every tax year, against a schema and rule catalog the IRS revises annually.

Building direct means owning the IRIS XML generation end to end. You serialize the three-level transmission hierarchy — the manifest, then submission groups, then the forms inside them — in UTF-8 without a byte-order mark, because IRIS rejects UTF-16 and UTF-32 outright. You strip characters the schema forbids, such as the double dash in an address line, and you respect the strict person-name fields that accept only letters and hyphens. None of that is conceptually hard, but all of it has to be exactly right on every record, or the transmission comes back rejected.

Hosted software absorbs that surface area for you. The trade you are really making is autonomy and per-form cost on one side against engineering time, maintenance, and rejection risk on the other. A team with developers, a stable form mix, and time before the deadline can justify building. A team without spare engineering capacity — or one staring down a deadline — almost always comes out ahead buying, because the vendor has already paid the build cost once and amortized it across every customer.

The Best FIRE-to-IRIS Migration Software Is the One That Converts Your Files

A separate question hides inside the software choice for anyone leaving the legacy FIRE system: what converts the files you already have? FIRE produces fixed-width flat files, where each value lives at a memorized column position, while IRIS expects self-describing XML, where every value is wrapped in a named element. The two formats are not interchangeable, and a FIRE file will not upload to IRIS as-is. So a real migration tool is one that maps your old flat-file layout into the IRIS schema without forcing you to re-key a season’s worth of data.

This is where the “best migration software” question separates from the “best filing software” question. Some tools assume you will hand them clean XML; the more useful ones accept the formats you already produce — including FIRE-style flat files and CSV — and generate the compliant IRIS XML for you. If you are moving off FIRE this year, weigh conversion support as heavily as price, and read the side-by-side IRIS-versus-FIRE comparison first so you know exactly which format differences your tool has to bridge.

The State-Filing Feature That Separates Real Tools From Toys

If any of your recipients live in a participating state, Combined Federal/State Filing (CF/SF) is the feature that decides whether your state obligation is handled in one transmission or becomes a second project. CF/SF lets the IRS forward your eligible returns to participating states on your behalf, but it only works if your submission elects it correctly — and the rules are unforgiving in a way that quietly trips up filers who hand-build their XML.

Under the IRIS business rules, the state election is gated on the submission header. Rule SHAREDIRFORM020 requires that whenever a return carries a CFSFElectionStateCd, the CFSFElectionInd in the submission header must equal 1, and rule SHAREDIRFORM022 requires that at least one TotalByStateGrp be present when a state code is set. On top of that, rule S1H002 requires that your TCC actually participates in the CF/SF program before the election is honored, and S1H003_001 limits the election to the specific form types CF/SF accepts. Miss any of these and the state portion is silently dropped or the return reports an error.

When you evaluate software, this is a concrete test rather than a marketing claim: does the tool set the CF/SF election on the submission — correctly, on the very first transmission of each return — and does it validate the participating-state list for you? Good tools do; weaker ones leave you to discover the rule the hard way. The companion guide to Combined Federal/State Filing on IRIS walks through the eligible states and the first-submission requirement in full.

Common Rejection Reasons (and How to Avoid Them)

However you reach IRIS, the same handful of mistakes account for most rejected transmissions — and whether a tool prevents them is the most useful thing you can know about it. Each item below names the failure, its cause, and the fix; a tool that catches these before submission is doing the job you are paying it for.

Which Path Fits Your Filer Profile

There is no universal winner, so match the door to who you are. A small business filing a handful of 1099-NEC forms once a year is well served by the free IRS portal, provided it allows for the TCC wait — the volume is low and the manual entry is bearable. A high-volume transmitter with developers and a stable schedule can justify building direct A2A, because the engineering cost amortizes across millions of records and the 100 MB submission cap leaves plenty of headroom; the high-volume bulk filing guide covers that ceiling in depth.

Everyone in between — the firm filing for many clients, the business with real volume but no spare engineers, and anyone migrating off FIRE under deadline pressure — tends to land on commercial software, because it converts the messy parts of the job into a fee. The honest framing is not “which tool is best” but “which constraint is binding”: if money is tight and time is plentiful, file direct; if time is tight and the work is risky, buy the tool that already holds the authorization and validates the rules for you.

Skip the Build Entirely: The e1099f Advantage

A Receipt ID, not a rejection — across the full 1099, 1098, 5498, and W-2G series.

Frequently Asked Questions

Not tax advice. This is general information about IRS procedures and filing options, which may change as the IRS updates IRIS; the published IRS publications are authoritative, and you should consult a tax professional for your situation.