7 FIRE Alternatives After the November 19 Cutoff 2026
FIRE system alternatives after the November 19 cutoff are the IRIS paths that replace Filing Information Returns Electronically. FIRE is the IRS’s legacy information-return e-file system. IRIS is the Information Returns Intake System. Your numeric FIRE transmitter control code (TCC) does not carry over. IRIS TCCs start with D.
A one-sentence definition: a FIRE alternative is any IRIS portal, A2A, or vendor product that can e-file 1099s and other information returns after FIRE stops.
Average month-end close cycle: 8–10 business days according to Journal of Accountancy 2025 close-cycle benchmark (2025). That is mid-market close time, not Fortune-500 3–5 day close. It is why a 1099 project that still lives in FIRE will collide with the same staff who are already in a 8–10 day close.
TL;DR: the seven paths are IRIS taxpayer portal, IRIS A2A you build, IRIS via a software vendor (Drake, Lacerte, and peers), a dedicated 1099 transmitter (Tax1099, Track1099, and peers), a payroll/1099 suite, a Big-4/managed ops provider, and a CPA firm portal. US Tech Automations does not hold an IRIS TCC for you. It can nag the calendar and hold a reject after the transmitter returns.
The IRS reminder on the FIRE-to-IRIS transition is IR-2026-99, according to the IRS newsroom (2026). FIRE last day: 19 Nov, 3 p.m. ET is the cutoff named in that reminder. Confirm the clock on the IRS page before you file; do not rely on a blog for the minute.
The November 19 cutoff, dated
EY describes IRIS as the new platform and notes the IRS plans to retire FIRE for e-filing 2026 returns in 2027, according to EY (2026). The operational cutoff you cannot miss is the FIRE last-day clock in IR-2026-99. Apply for an IRIS TCC now. Practitioner notes say TCC applications can take up to 45 days. Two responsible officials with US TINs plus ID.me are required for portal access.
Filers issuing 10 or more information returns (aggregated across W-2, 1099, 1042-S, and similar) must e-file. IRIS will not be optional for those filers.
The IRS IRIS page is the product home: e-file information returns with IRIS. The FIRE page remains up for the legacy system at the FIRE e-file providers page.
Tax pros still argue IRIS vs FIRE in public threads; one r/taxpros discussion is a sentiment check, not a filing method, according to r/taxpros (2024).
Related firm ops: deadline escalation, tax deadline reminders, Canopy alternatives, billing disputes.
IRIS TCC is not your FIRE TCC
IRIS TCC starts with D. FIRE TCC is numeric and does not carry over. You must apply again, identify responsible officials, and pass ID.me. A2A add-ons: software-developer application, API identification, and assurance testing. EY notes IRS testing and approval can take several months and that support is limited. Portal CSV uploads cap at 250 returns at a time. A2A submissions cap at 100 megabytes — those caps sit in the same EY IRIS briefing already cited above.
Sovos tracks IRS publication updates on 1099s, according to Sovos (2026). Use Sovos as a vendor-regulatory note, not as IRS text.
Who this migration is for
This page is for a CPA firm tax-ops lead, a corporate tax information-reporting owner, or a 1099 transmitter whose FIRE TCC still works today and whose 2026 calendar includes 1099-NEC, 1099-MISC, and possibly 1099-K / 1099-DA. Your stack is a tax product plus a spreadsheet of payees.
Red flags: you file three 1099s on paper and are under the e-file threshold; you already live in IRIS A2A; you are not a filer (your payroll vendor files). Skip a new vendor if IRIS portal plus 250-row CSV already covers your volume.
How we scored the seven paths
| Evaluation criterion | Weight % | Proof test | Disqualifier |
|---|---|---|---|
| IRIS TCC path | 25 | D-prefix TCC in hand | FIRE TCC reused |
| Volume fit | 20 | Portal 250 vs A2A 100MB | Portal for a 40,000-row file |
| Recipient copies | 15 | 1099s furnished, not just transmitted | A2A-only, no print |
| Calendar / rejects | 15 | 1 reject workflow | Silent fail |
| Implementation | 15 | ≤45 days TCC + testing buffer | Start Nov 1 |
| Public price | 10 | SKU or contact vendor 2026-09-06 | Surprise per-form |
Seven paths off FIRE
| Path | Best for | Volume | Published start | USTA Growth |
|---|---|---|---|---|
| IRIS taxpayer portal | Small filers | ≤250 per CSV | IRS free | $372/mo hop |
| IRIS A2A you build | Software teams | 100MB / submission | Staff time | $372/mo hop |
| Tax software (Drake et al.) | CPA firms | Vendor limits | Contact vendor | $372/mo hop |
| 1099 specialists | High 1099 volume | Vendor | Contact vendor | $372/mo hop |
| Payroll / 1099 suite | Employers | W-2 + 1099 | Vendor | $372/mo hop |
| Managed ops (EY-class) | Complex 1042/1099 | Enterprise | Contact vendor | $372/mo hop |
| CPA firm portal | Clients who will not apply | Firm | Engagement | $372/mo hop |
| 12-month planning row | TCC owner | Recipient forms | Engine of record | USTA Growth |
|---|---|---|---|---|
| Portal | You | You generate | IRS | $4,464 |
| A2A build | You (developer) | Separate | Your software | $4,464 |
| Tax software | You or vendor | Usually yes | Vendor | $4,464 |
| 1099 specialist | Often vendor | Yes | Vendor | $4,464 |
| Payroll suite | Employer | Yes | Vendor | $4,464 |
| Managed ops | Provider | Yes | Provider | $4,464 |
| CPA portal | Firm | Yes | Firm | $4,464 |
Buy vs build A2A
Build A2A only if you already have software-developer muscle, can wait through assurance testing, and will maintain a schema per tax year. EY is explicit: a separate package per year, unpublished error-code thresholds, and recipient copies are not created by A2A. Most CPA firms should buy a vendor that already passed IRIS testing.
Sovos and peer transmitters exist because publications and schemas move every year. Do not treat a one-off Python job as a 1099 product.
1099 season without a second portal
A 22-person CPA firm that issues 4,800 1099-NEC forms at a $1,200 average payment, while the close still takes 8–10 business days, will miss FIRE’s November 19 3 p.m. ET last day if the IRIS TCC is still in ID.me limbo. When QuickBooks Online updates MetaData.LastUpdatedTime on a 1099 vendor, a proposed US Tech Automations recipe could flag vendors missing a TIN, hold a packet for the tax manager, and count days remaining to the November 19 cutoff. Prerequisites: QBO API, a TCC-status field a human updates, and a reviewer who can stop a file. Configurable design, not a live customer result.
US Tech Automations would not transmit IRIS. On finance and accounting agents it would watch vendor changes, the cutoff calendar, and reject codes. Growth at $372/mo, 5 flows, 150 API calls per flow per day is nag-and-hold. Scale at $1,371/mo (10 flows, 500 API calls/flow/day, 90-day history) is the public SKU if hourly polling matters.
When NOT to use US Tech Automations: if your 1099 vendor already files IRIS and already tickets rejects, stay there. If a Zapier, Make, or n8n scenario already watches MetaData.LastUpdatedTime with retries and a run history, keep it. Those tools can support audit evidence; you own idempotency, TIN encryption, retention of 1099s, and access control. A proposed US Tech Automations design adds a human hold and “this flow does not e-file.”
Decision checklist
Is an IRIS TCC (D-prefix) approved, with two officials and ID.me?
Portal 250 vs A2A 100MB: which matches peak file size?
Who furnishes recipient copies?
45-day TCC buffer plus testing: are you already inside that window?
Parallel FIRE/IRIS plan if you are still before the last day?
A 45-day IRIS TCC calendar that fits 8-10 day close
Work backward from November 19 at 3 p.m. ET. If TCC applications can take 45 days, a firm that starts October 15 is already inside the fire. The same people are in an 8–10 business-day close. Do not schedule ID.me for the Friday the close pack is due.
Day 0: identify two responsible officials with US TINs who can pass ID.me. If you cannot name them, you cannot apply.
Day 1–7: submit the IRIS TCC application. Track it like a filing, not like a sidebar.
Day 8–45: while you wait, pick the path (portal vs vendor vs A2A). Download CSV templates. Clean TINs. Decide who furnishes recipient copies. A2A builders start assurance testing, knowing it can run months.
After TCC: one test file. One reject drill. One named person who can stop production.
Portal CSV cap: 250 returns per upload in the EY IRIS briefing. A2A cap: 100MB per submission in that same briefing. If your 1099 file is 8,000 rows, the portal is a queue, not a strategy.
E-file trigger: 10 information returns aggregated across form types. That threshold is why “we only do a few 1099s” is often wrong once you count W-2s and 1099-NEC together.
Glossary:
FIRE: legacy IRS information-return e-file.
IRIS: replacement intake system.
TCC: transmitter control code (IRIS starts with D).
A2A: application-to-application IRIS channel.
MeF: modernized e-file (1042 path is separate).
Recipient copy: the 1099 you furnish, which A2A does not create by itself.
Common mistakes: assuming the FIRE TCC ports; starting ID.me in November; building A2A as a weekend script; forgetting recipient copies; ignoring 1099-DA / 1099-K changes.
If a vendor already files IRIS and tickets rejects, you need a cutoff calendar, not a new transmitter.
Recipient copies, states, and new 1099 types
IRIS A2A transmits to the IRS. It does not print the 1099 you must furnish to the payee. If you build A2A, budget a second product for recipient copies. Portal users still have to generate forms. Vendors usually bundle both; that bundle is often the whole point of paying them.
States may still want their own layouts. A federal IRIS accept is not a state accept. If you file in states that have not moved with IRIS, you will support two outbound formats. Ask the vendor which states they transmit today, in writing.
Form churn is real. 1099-DA, 1099-K threshold changes, and 1099-NEC tweaks show up as schema updates. EY notes developers should expect IRS updates even after season start, and that each tax year needs its own package. A one-off script that “worked last January” is how you miss a new validation and blow a file at the deadline.
The 8–10 business-day close cycle is the staffing constraint. Information-return work that steals the same controllers in November will slip. Assign a 1099 owner who is not also the close owner, or accept that one of the two jobs will slip. The November 19 3 p.m. ET FIRE last day does not move because close is late.
If you are a three-form paper filer under the aggregated 10-return e-file trigger, IRIS may be optional for you. Count W-2s and 1099s together before you claim the exemption. Most firms that think they are “small” are already over ten once they aggregate.
Do not dual-run FIRE and IRIS on the same production file after the last day. Before the cutoff, a parallel test is wise. After 3 p.m. ET on November 19, FIRE is not your backup. IRIS is the path. Have the D-prefix TCC in hand, a named transmitter, and a reject drill that someone has actually performed.
Vendor due diligence is a TCC question. Does the vendor file under your TCC or theirs? Who is the transmitter of record? If they lose a file, who amends? A CPA firm portal that files under the firm’s TCC is a different liability than a corporate A2A you built. Write that down.
1042 / 1042-S and MeF are adjacent, not the same switch. EY’s briefing treats Form 1042 e-file as a separate modernized path with its own EFIN and residency rules. Do not assume IRIS solved withholding tax. If you file 1042, budget that project beside IRIS, not inside it.
The 8–10 day close and the 45-day TCC wait will collide unless you start now. Put IRIS on the same calendar as extension deadlines and 1099 vendor cleanup. If the close owner is also the 1099 owner, pick which job is allowed to slip — and know that November 19 will not slip with it.
TIN matching before transmit is still the cheapest reject prevention. A file that IRIS accepts with bad payee data still becomes a B-notice problem. Clean vendors in QBO (or your AP system) while the TCC is pending. Watch MetaData.LastUpdatedTime on 1099 vendors so new payees cannot sneak onto a file without a TIN. That watch is a hop. It is not IRIS.
Corrections and prior-year files need the year-specific schema. If you amend a 2025 1099 in 2027, you will not use the 2026 IRIS rules. Vendors that keep year packages earn their fee here. A2A builders who hoped one schema would last should read EY’s per-year warning again and budget accordingly.
State filing copies, recipient portals, and IRS rejects are three inboxes. Name an owner for each. If all three are “the tax manager who is also on close,” you have already chosen to miss one. The 3 p.m. ET clock does not care which one you miss.
Print a one-page runbook: TCC ID, transmitter, CSV vs A2A, who furnishes copies, who stops a file, and the November 19 3 p.m. ET cutoff. Tape it next to the close calendar. If the runbook does not exist, IRIS is still a slide.
Key Takeaways
FIRE’s last day is November 19 at 3 p.m. ET; IRIS TCC does not inherit FIRE.
Close cycle: 8–10 business days according to Journal of Accountancy (2025) is why this collides with year-end.
Portal, A2A, tax software, 1099 vendors, payroll suites, managed ops, and CPA portals are the seven paths.
10-or-more e-file is already the law for aggregated information returns.
Orchestrate calendar and rejects; do not become the transmitter.
FAQs
What replaces FIRE after November 19?
IRIS. Apply for a new TCC that starts with D. Read IR-2026-99 on the IRS newsroom and the IRIS page.
Can I keep using my numeric FIRE TCC?
No. It does not carry over. Budget up to 45 days for the IRIS application.
Is the IRIS portal enough?
If you can live with 250 returns per CSV and manual entry, yes. If you have tens of thousands of forms, you need A2A or a vendor.
Should I build A2A myself?
Only if you can staff developer testing that EY says can take several months, plus per-year schemas. Most firms should buy.
Does a workflow hop file 1099s?
No. It nags the cutoff and holds TIN/reject packets. The transmitter still files.
If IRIS is chosen and the remaining work is cutoff holds, see finance accounting agents. Bring the FIRE TCC (for the archive), the IRIS application status, and the person who can stop a file on November 19.
About the Author

Helping businesses leverage automation for operational efficiency.