The TCC lifecycle: getting, keeping and losing your transmitter code

The lifecycle

The people on the application

An IR Application for TCC needs at least two Responsible Officials and two Contacts, up to 250 contacts, with a one-and-one exception for sole proprietors, S corporations and single-member LLCs (IRM 3.42.9.7(2)). "All individuals on the application must provide a valid social security number (SSN) or an active and valid individual taxpayer identification number (ITIN). This information will be validated and monitored." Contacts cannot see or edit the application; only ROs and up to two Authorized Delegates can (IRM 3.42.9.7(11)).

Two checks run without you. Each quarter (January 8, April 8, July 8, October 8) the system matches every RO's last name and first five characters of first name against the Treasury OFAC sanctions list; a date-of-birth match is escalated (IRM 3.42.9.7.2(5)). And a date-of-death hit triggers a letter whose text is scripted in the manual: "Updates to an application must be made within 30 days after any change occurs. Remove/replace the deceased authorized user within 30 days to keep your TCC active." If the decedent was the sole RO, the application is deleted.

Applications left in "Resubmission Required" for 45 days draw a letter; at 90 days they are deleted. A saved, never-submitted application is deleted at 90 days (IRM 3.42.9.22.1).

One TCC, many companies, one login

"A TCC is issued to only one specific EIN and can transmit files for as many companies as needed" (IRM 3.42.9.8.8.2(2)). A parent or shared-services center needs one TCC, not one per subsidiary. The FIRE login, though, must use the EIN the TCC was issued to, not the EIN of the payer being filed for; logging in with a subsidiary's EIN produces the "Information does not match" error the help desk sees constantly. A second TCC of the same type is granted only if the existing one is at or near the thousand-file limit (IRM 3.42.9.7.2). IRIS TCCs are bound to one filing method (Portal or A2A) and cannot be used on FIRE; FIRE TCCs start with a digit, IRIS TCCs with a letter (IRM 3.42.9.7(4), (7), (8)).

Dormancy and deletion

A TCC unused for more than two years goes inactive and is dropped 90 days later; FIRE's annual clean-up separately deletes TCCs and accounts unused for three prior years, sparing only accounts used for the online Form 8809 (IRM 3.42.9.22.1, 3.42.9.8.2). A payer that e-files only in the years it crosses the ten-return threshold can lose its credential and face a new application with a processing clock measured in weeks, in January. A new FIRE TCC takes up to 48 hours to work after issuance; an IRIS TCC works immediately (IRM 3.42.9.7(15), 3.42.9.7.6). Do not apply on January 30.

FIRE account hygiene is also specified: passwords of 8 to 20 characters rotated every 90 days with no reuse of the last 24, a 10-digit PIN with no repeated or sequential digits, and accounts that cannot be shared between contacts (IRM 3.42.9.8.5 to 8.7). FIRE data older than seven years is archived; "FIRE is not the system of record" (IRM 3.42.9.8.9).

Files: the 10-day hold and the replacement window

A file that passes validation shows "Good" and "will automatically be released to processing after 10 calendar days unless the filer contacts TSO within this time frame" (IRM 3.42.9.16.1). Inside that window the help desk can change the status to Bad so a replacement can be sent; after it, "a corrected file is required." A replacement is not a correction and does not enter the penalty system; corrections do. A Bad file must be replaced within 60 days, and the manual expects the filer to check status within five business days; FIRE emails results only if a valid address was entered on the verification screen (IRM 3.42.9.9.4.10, 3.42.9.16.1(2)).

Duplicates are hunted rather than silently discarded: a weekly job flags files from the same TCC whose record counts are within five of each other, the help desk reviews them and contacts the transmitter, and a late "replacement" of an already-good file is watched for a late postmark (IRM 3.42.9.17.6).

The structural error codes

Pub 1220 lists record-level errors. These are the file-level codes for a file the system could not read at all (IRM 3.42.9.16.4): 14, no complete T/A/B/C record set; 15, multiple files zipped into one; 16, no payee B records; 17, cannot decompress; 22, executable; 73, PDF; 74, Word or Excel; 86, no T record first; A2, EBCDIC; A3, W-2 data sent to FIRE (W-2s go to SSA); A4, 1042-S under a TCC that does not begin with 22; AV, file too large.

FIRE retirement

"Tax Year 2026/Filing Season 2027 is the targeted date for the retirement of the FIRE System" (IRM 3.42.9.8(1)). A FIRE TCC does not carry over; an IRIS TCC is a separate application. Combined Federal/State Filing participation now requires an IRIS TCC and a first-year test file that returns "Good, Federal/State Reporting" (IRM 3.42.9.8.3). Test systems must never receive real taxpayer data (IRM 3.42.9.8.4). The FIRE to IRIS page has the migration plan.

Questions people ask