Skip ahead to the main page
Partner Huddle
Pages

FIRE to IRIS: 3 numbers for your 1099 transition

Partner Huddle Editorial Team · Published · 12 min read

Move your firm's 1099 filing from FIRE to IRIS by planning the TCC application, clearing open FIRE work, and checking intake fields.

Key takeaways

  • Give the application processing time a separate calendar buffer.
  • Assign an owner and a backup to transition tasks.
  • Separate paper-filed returns from electronically filed returns when planning corrections.

If your firm files 1099s for clients, the deadline is the easy part to remember. The harder part is changing the system you file through while the old one is still running. For many small firms, the move will happen during one busy season, with a stack of client forms, a few staff members who only know FIRE, and a partner who wants to know what happens if something goes wrong.

The IRS has been direct about where things are heading. The general instructions for certain information returns for 2026 say you are "strongly encouraged to complete your IRIS application for Transmitter Control Code (TCC) and begin transitioning to IRIS to ensure you are ready for the 2027 filing season." That sentence is the reason to start planning now instead of in January.

This post builds the plan around three numbers. The first is a processing time, 45 business days, which tells you how early the application has to go in. The second is 2026, the year FIRE stops taking submissions at year end. The third is 2027, the filing season you are preparing for. None of these numbers replaces the IRS publication, and each one links to its source so you can check the wording yourself.

Number one: 45 business days for the TCC application

The IRS publication says: "The typical TCC application will be processed within 45 business days, however, processing times may vary." The application is for a Transmitter Control Code, and the IRS ties that application to the move to IRIS. So the processing time is the first number to plan around.

Business days exclude weekends and holidays, which means the calendar runs longer than the number suggests. As a rough guide, 45 business days is about nine working weeks before holidays are counted. Start the count on Monday, November 2, 2026, and the typical timeline runs into the early part of January 2027. Holidays in late November, December, and early January push it later still.

The word "typical" matters. The same sentence warns that processing times may vary, so a firm that plans around the best case will be caught short. A sensible plan works backward from the date you want to be submitting through IRIS, then adds a buffer of several weeks on top of the 45 business days. Put the buffer on the calendar as its own line so that other work does not quietly use it up.

Two practical points follow. First, decide who at your firm owns the application and who checks its status, so the clock does not run while the file sits in someone's inbox. Second, do not wait for a client deadline to force the question. An application submitted late in the year leaves little room if the process takes longer than typical, and the buffer exists for exactly that case.

It helps to write the math down once and share it. A two-column list in your planning document, with the target submission date on one line and the latest safe application date on the next, is enough. Revisit it every week until the application is in. Most of the risk in this plan is not the 45 days themselves. It is the week nobody noticed the application had not gone in yet.

Illustrative example: sort the open work

It assigns an owner to each group, then checks how each correction was originally filed. The counts show the workload, but each correction still needs its own method checked. That firm then adds several weeks of buffer when planning its application, leaving room if processing runs long. Its target will depend on how many clients it files for and when its busy weeks fall.

Number two: 2026, the year FIRE closes

The second number is a year. The publication states: "FIRE will not be available for submissions (current, prior year, or corrections) once the system shuts down in 2026 for end of year."

Read that sentence slowly. It covers three kinds of work: current-year submissions, prior-year submissions, and corrections. A firm that assumes FIRE will still accept its late corrections after the shutdown is planning around a system the publication says will not be available. That is the mistake to avoid, and it is easy to make when the year-end rush already has everyone busy.

Check the exact shutdown date before setting your internal deadline. Get the date from the IRS publication or the official FIRE pages before you set your internal deadline, and put it on the shared calendar. Do not rely on memory or on a colleague's guess, because the cost of being one day late is that a filing you planned to make through FIRE can no longer be made there.

For planning, the practical rule is to finish everything that must go through FIRE before the shutdown. That includes any current-year work you can complete, any prior-year filings still open, and any corrections you already know about. Anything left after that becomes a question for the new process, and you want to know which items those are while there is still time to ask.

Before the shutdown, also save copies of anything you will need later from FIRE, such as submission confirmations, acknowledgments, and the record of what you sent for each client. Store them in the same shared folder as your planning files. A copy you control is easier to find in a hurry than a record you have to track down in a system you can no longer use for submissions.

Think of the shutdown as a hard wall rather than a soft target. Work that is not done by the wall moves into a different workflow, with different steps and possibly different people. The earlier you sort your open items into "done," "must finish first," and "needs the new process," the less of a scramble you will have in the final weeks of the year.

Number three: 2027, the season you are building for

The third number is the 2027 filing season. The IRS wants firms ready for it, and the publication also describes updated forms. It says: "Forms 1099-MISC and 1099-NEC have been updated to allow reporting of cash tips, Treasury Tipped Occupation Code, and overtime compensation."

For an operations lead, that sentence matters in two ways. The new fields have to appear in your client intake and data mapping, and your staff need to know where that information comes from and who confirms it. If your firm collects client data in a spreadsheet and imports it into a filing tool, check that the worksheet covers the new fields before the season starts. Do not assume the old worksheet still works just because the form number looks familiar. Use the client intake checklist to organize the handoff.

Ask your clients for the information they have, check the form instructions directly, and ask your software vendor how it handles the new fields. Write down the answers so that the next person who handles a file does not have to ask again.

Client communication is part of this too. Clients who have never been asked for tip or overtime information may not know what you need, so send a short, specific request well before the season. Name the fields, say which of their forms they affect, and ask for a reply by a date you choose. Make the request once, clearly, and file the reply with the client record so the answer does not get lost in an email thread.

Here is how the two systems compare for the questions this post raises:

Planning questionFIREIRIS
Submissions after the 2026 year-end shutdown Not available for current, prior-year, or correctionsThe IRS strongly encourages a move to IRIS for the 2027 filing season
Date that matters most The 2026 year-end shutdownReadiness for the 2027 filing season
What to do nowFinish required work before the shutdown Submit the TCC application early enough to cover the buffer

Read across the rows and the picture is clear. FIRE has an end point, and IRIS has a processing clock that starts when the application goes in. The earlier you start the clock, the more room you have for the work that comes after it.

Corrections need their own plan

Corrections are where small firms tend to get stuck, so they deserve a section of their own. The Tax1099 guidance on corrections says: "A return that was originally paper-filed doesn't follow this path." Tax1099 is a third-party provider, not the IRS, so its page is not the rule. But the point it makes is useful for your planning: how a return was first filed can change how it gets corrected.

The same page describes Tax1099's own method for correcting a return: "The original form is first zeroed out, then the correct form type is filed as a new original return with the accurate figures." That is how Tax1099 describes its own service, so the steps may differ in the filing system your firm uses. Check what your IRS filing system requires before you copy any method from a vendor page, and confirm the steps with the IRS publication.

A practical way to start is to pull a list of every return filed in the last cycle. For each one, note whether it was paper-filed or electronically filed, whether a correction is open, and whether that correction must be finished before the FIRE shutdown. Sort the list into three piles: done, must finish before the shutdown, and needs a different method. The third pile should be small, and you want to know its size early so you can plan staff time around it. The guide to client correction checks can help organize that review.

Paper-filed returns deserve separate attention. If you have only a few paper-filed returns, handle them one at a time and record each step. If you have many, check the IRS publication and your filing system's instructions for the route that applies before you start.

Corrections also create the most client conversations, so set expectations early. Tell clients which corrections you are making, why, and whether they need to do anything on their side. A short written note is usually enough, and it protects both the client relationship and your firm when someone asks about the change months later.

Penalties and records

Keep the penalty discussion measured and specific. The publication lists a section on civil damages for fraudulent filing of information returns: "Civil Damages for Fraudulent Filing of Information Returns (Section 7434)". That heading signals that the accuracy of what you file carries legal weight. This post does not summarize the penalty rules, so read the relevant sections of the publication yourself before you set your review process.

For your operations plan, the lesson is about records. Keep a clean trail of what was filed, when, under which system, and who approved the figures. If a client, a partner, or the IRS asks about a particular return later, you want to show the work rather than reconstruct it from memory. A shared folder with a consistent naming pattern and a one-line log for each filing is enough for most small firms.

Build an internal review step before anything is submitted. The reviewer should check names, taxpayer identification numbers, amounts, and form types against the client's own records, not against last year's file, since last year's file is where old errors get copied forward. A second review can catch errors before submission.

Records also protect your staff. When one person handles every correction and nobody else knows the steps, the firm is exposed the moment that person is out sick or leaves. Write the steps down, name a backup for each one, and walk the backup through a real example before the busy season arrives.

A timeline for the next several months

Use the three numbers to build a simple schedule. The steps below are in rough order, and each one can be assigned to a named person with a date beside it.

  1. Confirm the 2026 year-end shutdown date with the official FIRE pages or the IRS publication and put it on the shared calendar.
  2. Inventory every open FIRE item: current-year work, prior-year filings, and corrections. Mark which ones must be completed before the shutdown.
  3. Decide who submits the TCC application and who tracks its status. Submit it with a buffer of several weeks beyond the typical 45 business days.
  4. Update client intake forms and data mapping for the 1099-MISC and 1099-NEC changes, including cash tips, the Treasury Tipped Occupation Code, and overtime compensation.
  5. Sort past returns into the paper and electronic groups, and write down the correction method your firm will use for each group.
  6. Walk one low-risk client through the new process before the season starts, so the first real file is not also the first test.
  7. Review the open list every week until the shutdown and again once the application is approved.

Each step is small on its own. The risk comes from letting several of them slip at once, usually in the weeks when the year-end workload is heaviest. Assign owners early, keep the list visible, and check it on a fixed day each week.

Keep the schedule in one place that everyone can see. Each owner updates their line when a task moves, and the operations lead reviews the whole list at the same time every week. A schedule that lives across five email threads tends to fail quietly, and nobody notices until a deadline has already passed.

The partner's question is usually simple: will we be ready? The honest answer depends on whether the application has gone in, whether the open FIRE items are sorted, and whether the new fields are mapped. If those three things are true by the time the 2027 season starts, your firm is in a strong position. If one of them is still open, the three numbers in this post show you how much time you have left to close it.

Today, open your shared planning document and assign an owner to the TCC application and its status checks.

Questions before the season

Is the application processing time guaranteed?

No, the quoted processing time is typical and may vary. Keep that uncertainty visible when setting your target submission date.

Can a vendor's correction method apply to every return?

No, a vendor's method needs checking against your filing system's requirements. Start with the original filing method, then confirm the correction route before changing a return.

Sources