IRIS Submission Status: What to Save and Check Next

Open View Submitted Forms and locate the transmission using its receipt reference and available filters. Select the Receipt ID to see the related submissions, then the Record ID for individual form details. Publication 5717, sections 3.6.3 through 3.6.6.

Confirm payer, tax year, form, and the date associated with your internal batch. A recent receipt might relate to a different upload or a correction. Preserve the original receipt alongside any later related filing so the history remains understandable.

If you cannot find the expected transmission, examine the actual unsubmitted forms and the original confirmation evidence before submitting again. A missing screenshot, an uncompleted final action, and a filtered-out receipt are different explanations and need different next steps.

These are the definitions in Publication 5717, section 3.6.4. Keep the exact displayed label in your tracker. Do not replace it with a vague internal label such as “uploaded” or infer that an accepted file can never contain an underlying reporting error.

Save the acknowledgment and inspect the status details associated with the receipt. Record the error level, available identifier, and message. Link each issue to its payer, form, year, and source record before changing data.

Distinguish an error affecting an entire submission from one tied to an individual record. The scope determines what needs follow-up. A transmission can contain several submissions, so its summary status may not describe every return in the same way.

Compare the flagged value with authoritative source records. For example, a recipient identity issue needs investigation of the actual name and identifier, not an arbitrary spelling change to make a message disappear. Keep sensitive detail within the controlled filing work area and use masked references in general task notes.

Check whether the rejected item is itself a correction. Publication 5717 gives a special rule for that case: return to the original submission and file a correction, instead of replacing the rejected correction. The ordinary rejected-original replacement route should not be applied to every rejected artifact without reviewing its history.

Fictional example. A portal transmission contains two submissions. One contains 8 NEC returns and is accepted. The other contains 3 MISC returns and is rejected. The transmission's overall status is Partially Accepted.

The reviewer assigns the rejected group for repair and preserves the accepted group's evidence. Reuploading all 11 as new original returns would fail to distinguish work already accepted from work requiring replacement.

This is a constructed illustration of scope. Follow the live portal's supported selection and the actual acknowledgment for a real transmission.

Publication 5717 says to allow seven days for a Received by IRS transmission to process. Record the submission date and a sensible follow-up date, then consult the current IRS guidance if processing remains unresolved. Publication 5717, submitted-form status table.

The processing interval is not an extension of a filing deadline. Likewise, replacement and correction rules have their own details. Do not treat a calendar reminder to check status as a guarantee that all filing obligations are satisfied.

Before contacting support, collect the receipt, current exact status, relevant dates, and any downloaded error details. Have the authorized person use the current help route listed by the IRS IRIS page. State whether you are asking about pending processing, interpreting a message, or locating a missing result.

When follow-up produces another receipt, link it to the original issue and verify the new processed outcome. Record whether the action was a correction or replacement and which records it addressed. Retain the prior artifact as history rather than overwriting it.

Reconcile counts one last time: every intended original return should have an understood outcome, and every known error should have a documented resolution or a clearly assigned open action. A new receipt alone does not close an unresolved processing result.

Store the source version, original receipt, acknowledgment, issue log, and any subsequent receipt together. Separately track recipient statement updates and state work when required. That complete chain lets another staff member answer what was filed and what happened afterward.