Log in to IRS e-Services at irs.gov and navigate to the IRIS application; ensure the responsible individual has a completed e-Services account with identity-proofed access
Submit the IRIS TCC application, specifying whether you are filing as an issuer (filing your own information returns) or a transmitter (filing on behalf of other issuers), as the TCC type affects what you are authorized to submit
Wait for IRS processing of the TCC application; the IRS communicates approval and the assigned TCC via the e-Services secure mailbox, not by email
Once the TCC is issued, test connectivity against the IRIS Assurance Testing System using the TCC and the SOAP or CSV upload interface before submitting production returns
For A2A submissions, configure your SOAP client with the production IRIS endpoint URL and include the TCC in the submission manifest; for portal submissions, use the IRIS portal CSV upload workflow instead
Retain the TCC securely; it is required for every future IRIS submission and is specific to the filing role (issuer vs. transmitter) under which it was issued
Known gotchas
IRIS TCC applications require identity proofing of the responsible individual through IRS e-Services; organizations that have not completed e-Services identity verification cannot apply
A TCC issued for the issuer role cannot be used to submit returns on behalf of other payers; a separate transmitter TCC application is required for third-party filing scenarios
IRS FIRE TCCs and IRIS TCCs are separate; an existing FIRE TCC does not grant access to the IRIS system, and the two systems have different submission formats and endpoints
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp