Choose the filing channel before requesting access
The IRIS Application for TCC requests authorization to participate in IRIS. An IRIS Taxpayer Portal TCC is required for both manual entry and CSV upload. A2A uses its own TCC assignment; a FIRE, AIR or portal TCC cannot simply be substituted for an A2A TCC.
Decide who will actually transmit: your organization, its software operator or a third-party transmitter. Record that responsibility before applying. A business using a service to transmit under the service's authorization should confirm the arrangement rather than assume every customer must obtain a separate transmitting credential.
Match the business role to the reporting entities
Publication 5903, the IRS application tutorial, distinguishes Issuer, Transmitter and Software Developer roles. Issuer applies when the business transmits only for the company on the application. Transmitter covers filing for other businesses and can include the transmitter's own business. The application does not allow both Issuer and Transmitter selections.
The Software Developer role relates to developing A2A software and is not used for the Taxpayer Portal. Identify the actual legal entities in the planned filing population; a shared owner or brand does not make several EINs one issuer.
Prepare the application and complete its signatures
Use the official application link and tutorial to collect the firm's legal name, EIN, business structure, addresses and required authorized-user information. Determine the required Responsible Officials and contacts under the business-structure rules. Give each person responsibility for completing their own access and signature steps.
A saved application is not an approved application. All required Responsible Officials must complete the initial signature process. Publication 5717, revised February 2026, says to allow up to 45 calendar days for processing and to monitor the Application Summary. Record the submission date, outstanding signatures, review status and assigned TCC rather than treating an email or tracking number as permission to file.
Example: separate access readiness from filing readiness
Fictional Beacon Accounting prepares returns for its own practice and eight client businesses. Its administrator chooses the Transmitter role for the planned portal activity and identifies the required authorized users. The business has nine issuer populations to manage, but that does not mean it needs nine separate portal applications merely because there are nine issuers.
The administrator marks access ready only after the application is completed, the portal TCC is assigned and the authorized operator can reach the correct organization. The filing manager still approves each issuer's reporting data separately. Obtaining a credential does not approve the clients' payment classifications or amounts.
Give A2A access its own readiness checklist
For an organization transmitting with A2A software, Publication 5718 for processing year 2026 describes the A2A TCC, API Client ID, consent and testing requirements. Confirm the applicable production status. A Software Developer TCC remains a test credential and does not authorize production transmissions.
The current specification uses REST APIs with XML return documents. JSON is not the specified return payload. An initial response can provide a receipt while processing continues; the operator must retrieve the later status or acknowledgment. Keep technical configuration review with the software owner and production release approval with the filing owner.
Maintain access when staff or the business changes
Review authorized users, contact details and assigned responsibilities when staff leave or a service arrangement changes. Update the application as required and complete any required signatures. Publication 5717 explains that changing the TCC application does not automatically update the organization's IRS tax-record address, or vice versa.
The current portal guidance states that a TCC unused for three consecutive years is deleted and cannot be reactivated. Do not submit an unnecessary tax return merely to keep a credential active. Investigate the actual status and follow the applicable application process if the organization needs access again.
Choose a practical guide
Use the guides below for application preparation, role selection, access maintenance and the handoff to an authorized filing operator. Browse the filing guides.
Questions from filing teams
Do manual portal entries require an IRIS TCC?
Yes. The portal requires its own assigned TCC whether the operator enters returns manually or uploads the IRS CSV template.
Will our FIRE TCC work in IRIS?
No. IRIS has a separate application and channel-specific assignments. Verify the TCC for the actual portal or A2A activity.
Does a Software Developer TCC permit live filings?
No. Publication 5718 describes it as a test credential. Establish the applicable Issuer or Transmitter production authorization and testing requirements for live A2A work.
Is TCC approval the last step before an A2A filing?
It is one dependency. The software owner must also address the applicable API Client ID, consent, software and testing requirements, then the filing team must approve the production data.
Where should the team start a new application?
Use the IRS IRIS Application for TCC page linked above and its tutorial. The application and the Taxpayer Portal are different destinations with different tasks.
Set up your organization's filing project
Create a BoomTax account to begin your organization's filing setup. Keep the reporting year, expected return volume and approved source records available as you prepare the project.
