Tracking an IRIS TCC Application and Resolving Missing Steps

Use the official IRIS application entry point and sign in as an authorized participant. Confirm the organization, application type, and any displayed application reference. Similar company names or multiple business relationships can lead a person to inspect the wrong request.

Publication 5903 describes using the Individual selection for ROs before the application reaches Completed status. Once reviewing an existing organization application, verify that its summary matches the entity you are tracking. Publication 5903, access and existing-application instructions.

If the application is not visible, first confirm that the person has the appropriate role and that their information was entered correctly. Do not assume invisibility means there is no existing request, and do not immediately create another application.

Copy the exact application status and the date you observed it. Keep an internal next-action column beside it. “Waiting on payroll” may be useful project language, but it is not an IRS status.

These labels come from Publication 5903, Application Submission and Summary. If your screen shows different wording, retain that wording and follow its current instructions. Do not map an unfamiliar label to an invented approval state.

For each required signer, record access readiness, whether the signature has been completed, and the next available time for that person to act. Ask the individual to confirm completion without sharing a PIN or password.

A coordinator may have filled every data field while the application still awaits another person's signature. Check the actual submission page and roster rather than treating the original data-entry date as the start of IRS review.

If a signer cannot access the application, separate the identity/sign-in issue from the application issue. Capture the point at which access stops and the exact message shown. If someone has left the business, route the authorization problem to an appropriate RO and the IRS as needed instead of attempting to use the departed person's account.

Fictional example. An internal project tracker says that Aspen Example Corporation applied three weeks ago. On review, the IRS application still shows Signature Required. One RO completed their step; the other thought that the coordinator's submission covered everyone.

The team resolves the missing action and then records the new status. It does not characterize all three weeks as IRS processing time. The important distinction is the evidence of submission, not how long the project has existed.

This example uses tutorial status labels for illustration. It is not a view into a real organization's application and does not promise that the same sequence will resolve every delay.

When the next step is unclear, collect the application reference, legal entity label, current status, relevant dates, and a concise description of what has already been tried. Include the precise question: for example, “Which required action remains?” rather than “Why does IRIS not work?”

Separate general guidance from account-specific questions. The IRS application page provides a chatbot route and explains that account-specific questions require authenticated access. Use the current contact information on the IRS IRIS help page when phone support is needed.

Have an appropriately authorized person make the inquiry. Preserve the response and any reference number in the tracking log, then assign the stated next action. Avoid sending duplicate requests with conflicting entity details or promising an approval date based on another organization's experience.

Official publications use different planning timeframes: the December 2024 application tutorial describes typical processing within 45 business days, while the January 2026 A2A specifications say to allow up to 45 calendar days. Neither establishes the outcome of your individual application. Use the current guidance for your filing channel and follow up on the actual recorded submission. Publication 5903 and Publication 5718, section 1.3.2.

When the application reaches the appropriate completed state, have an authorized administrator review the assigned TCC details, intended organization role, and transmission method. Record where the controlled account record is maintained. Do not place full access details into a broadly shared project comment.

Then hand off to the relevant filing or integration workstream. Portal preparation and A2A onboarding involve additional work. Marking the application complete should not automatically mark software testing, return preparation, or IRS return acceptance complete.