A Transmitter Control Code is the credential that lets you file information returns with the IRS. FIRE had them and IRIS has them, but they are not the same code and yours does not carry over. Getting one is free and the form is not hard. What catches people is who has to sign it, how long the queue is, and how much a TCC still does not let you do.
- What it is
- Transmitter Control Code · your IRIS filing credential
- Cost
- Free
- IRS estimate
- Up to 45 business days · about 9 weeks
- Sign-in
- ID.me only · not Login.gov
- Responsible Officials
- 2 minimum · 1 for some business structures
- Carries over from FIRE
- No
Do you actually need one?
There is exactly one way to file through IRIS without a TCC of your own, and it is to file through somebody who has one. Everything else requires the application, including the free Portal.
- You file your own company's 1099s through the IRIS Portal
- Even the free Portal needs a TCC. There is no route to IRIS without one, except filing through somebody else's.
- You are a tax pro filing for clients under your own firm
- One TCC covers all the payers you file for. Your clients do not each need their own.
- You want to build or buy A2A software
- And you need a Software Developer role on top of the Transmitter role, plus a certificate and an API Client ID.
- You file through a transmitter that files under its own TCC
- The transmitter is the filer of record on the wire. This is the only way to skip the application and the wait.
Have this ready before you sign in
The IRS e-Services session times out quickly. Gather all of this first, then fill the form in one pass.
- EIN
- The employer identification number for the firm
- Legal name
- Exactly as it appears on the IRS CP 575 notice, suffix and all
- DBA
- Optional, but it is what shows as the transmitter
- Business address
- Physical, no P.O. box, plus mailing if different
- Business phone
- With country code
- Business structure
- It decides how many officials you need
- Form types
- 1099 Series for almost everyone
- CF/SF
- Whether you want the IRS to forward data to states
- Per official
- SSN or ITIN, date of birth, citizenship, title, email, phone
- e-Services PIN
- 5 digits, created in flow, cannot be all one digit
Choosing your role
This is the decision that shapes the rest of the application, and it is made on page two. Each role you take is issued its own separate TCC.
- Issuer
- You file only your own information returns. Mutually exclusive with Transmitter, so you cannot hold both.
- Transmitter
- You send returns to the IRS, including on behalf of others. This is the role a tax firm filing for clients wants.
- Software Developer
- You write the software that produces the transmission. Needed alongside Transmitter if you are building A2A yourself rather than buying it.
A tax firm filing for clients wants Transmitter. Add Software Developer only if you are writing the software that builds the XML. If you are buying software, the vendor holds that role, not you.
The application, page by page
Seven pages, in this order. The full official walkthrough is Publication 5903, and the application itself starts from the IRS IRIS Application for TCC page.
- 01
Firm Information
Business structure, EIN, legal name, DBA, addresses, phone, and the CF/SF election. The legal name is validated against IRS records with the EIN, so a mismatch here rejects the application rather than flagging a warning.
- 02
Application Details
Pick your roles and your transmission method. This is the page that decides everything downstream, so read the role section below before you touch it.
- 03
Software Packages
Only appears if you took the Software Developer role. You choose a package type here, and that choice constrains how you are allowed to distribute the software.
- 04
Authorized Users
Add your Responsible Officials, Contacts, and any Authorized Delegates. Everyone you add needs their own verified ID.me before an official can sign.
- 05
Application Comments
Optional. Most applications leave it blank.
- 06
Application Summary
Review. Worth reading properly, because some values are set by the system based on earlier answers and are not what you would have picked.
- 07
Application Submission
Every Responsible Official signs with their own 5-digit e-Services PIN. If you do not have a PIN yet, you create it here. Status then moves to Submitted Pending Review.
What actually holds people up
- 01
You may need a second human, and they need their own ID.me
The application requires a minimum of two Responsible Officials and two Contacts. Some business structures are exempt and can file with one, and Publication 5903 lists which. Every Responsible Official must pass identity verification, hold their own e-Services account, create their own PIN, and personally sign. An Authorized Delegate cannot sign the initial application. If your second official has not started identity verification, that is your real timeline, not the IRS review queue.
- 02
The Software Developer package type constrains your business model
If you take the Software Developer role you pick a package type: In-house, Online, or COTS. In-house means the software is not marketed or sold, which quietly rules out selling it as a product. You can add an Online package later by revising an approved application, which is a much smaller job than reapplying, but it is easier to pick correctly the first time.
- 03
The forms category is bundled and cannot be split
IRIS presents 1099 Series and 1042-S as a single selectable category, not two. Authorizing it does not oblige you to file 1042-S. It is permission, not a commitment, so there is no need to work around it.
- 04
The schemas are locked behind the TCC
You cannot download the IRIS XSDs or the business rules until you hold a TCC. The IRS schemas page says so directly and routes you to your e-Services mailbox. Only the figures printed in Publication 5718 are public. If your plan is to build A2A, the TCC is not the last step before development, it is the first.
- 05
e-Services logs you out faster than you can gather data
The session times out quickly enough that opening a form and then going to find a date of birth will bounce you back to sign-in. Collect every field on the checklist first, then fill the page in one pass.
How long it takes
The IRS estimate is up to 45 business days. Read that carefully. Business days, not calendar days, so it is about nine weeks rather than six. Counting back from a January 31 deadline, an application started in November has no margin at all.
Applications do come back faster, sometimes very much faster. Ours was approved in days rather than weeks. That is worth knowing and it is not worth planning around, because there is no queue to appeal to and no way to buy priority. Apply against the published estimate and treat an early approval as a bonus.
The clock you control is the one before submission. Identity verification for each official, gathering their details, and creating PINs all happen on your side, and for most firms that is the longer half.
What a TCC still does not let you do
If you plan to use the Portal, the TCC is the finish line. If you plan to transmit XML over A2A, it is roughly the halfway point. Three things remain, and the first one has the longest lead time.
- 01
A digital certificate
A2A authenticates with an X.509 certificate that you buy from a commercial authority. It cannot be self-signed. This has the longest lead time of anything in the process, because it involves identity proofing of both you and the business, so start it first.
- 02
An API Client ID
A separate application, quick once the certificate exists. You upload a JSON Web Key Set built from the certificate. The IRS is strict about its shape, including the certificate chain and thumbprint fields, and the key expires when the certificate does.
- 03
Assurance testing
TCCs are issued in Test status. Passing communication testing in the Assurance Testing System, using the package in Publication 5719, is what moves your TCC and your software package to Production. Until then you cannot file a real return.
Or skip the whole thing
Everything above is a real project. It is worth doing if you file at volume for one firm, or if filing infrastructure is your product. It is a poor use of a filing season if you are a tax professional whose actual job is the returns.
The alternative is to file through a transmitter. IRISfile holds an approved IRIS TCC and files under it on your behalf. You keep producing the FIRE, CSV, or Excel files you already produce, and there is no application, no certificate procurement, no identity verification for a second officer, and no schema work. See what that costs, or read the full FIRE-to-IRIS transition guide for how the three routes compare.
Whichever route you take, the file you feed it still has to be clean. Our free FIRE file validator checks a Publication 1220 file in your browser, with no upload and no signup.
Questions
- Does my FIRE TCC work for IRIS?
- No. IRIS requires its own Transmitter Control Code and a fresh application. Nothing carries over. This is the single most common misunderstanding about the transition, and the IRS stopped accepting new FIRE TCC applications on July 21, 2026.
- How long does an IRIS TCC really take?
- The IRS estimate is up to 45 business days, which is about nine weeks, not six. Some applications come back far faster. Plan against the published estimate rather than the best case, because you cannot appeal a queue.
- How much does a TCC cost?
- Nothing. The application is free. The costs downstream are the digital certificate for A2A, and whatever software you use.
- Do my clients each need their own TCC?
- No. One TCC covers every payer you file for. You are the transmitter and they are the issuers named in the returns.
- Can I avoid the TCC application altogether?
- Yes, by filing through a transmitter that files under its own approved TCC. That is what IRISfile does. You keep producing the files you already produce, and the transmitter handles the credential, the certificate, and the schema.
- Can I add a colleague to my TCC later?
- Yes, as an Authorized Delegate, which lets them maintain and sign revised applications without carrying an official's liability. They need their own verified ID.me first, and adding them creates a revision that a Responsible Official must re-sign.
- Is the IRIS TCC application the same as the API Client ID?
- No, they are separate applications. The TCC identifies you as a filer. The API Client ID, together with a digital certificate, is what lets software authenticate to the A2A channel. You need both to transmit XML.
- Can I sign in with Login.gov?
- Not for the IRIS application. In practice the entry point is ID.me only, even though other e-Services applications accept Login.gov.