Triage a Rejected 1094-B Filing Packet

Save the actual response, attempt time, environment, release version and any returned receipt. Record the exact status and error text without rewriting them into an assumed diagnosis. Retain the related manifest, form-data file reference and validation results in the protected release evidence.

Publication 5165 distinguishes portal rejections from transmissions or submissions rejected by AIR. A portal fault without a receipt is different from an acknowledgment that identifies a rejected submission. A timeout alone does not prove either outcome.

If the outcome is unknown, assign acknowledgment retrieval or support investigation before authorizing another attempt. The UI procedures in Publication 5258 explain the UI's acknowledgment workflow. Keep an unresolved response marked unresolved rather than converting it into a convenient rejected status.

The owner column is a suggested organizational assignment, not an IRS designation. A source-data question should still go to the person who can substantiate the data, even when a technical team first receives the error.

Find the original release's operation type and the actual processing result before deciding what to send next. Publication 5165's replacement procedures distinguish replacing an entirely rejected original transmission from replacing rejected original submissions in a partially accepted transmission.

For a completely rejected original transmission, the replacement follows the original rejected transmission's scope. For a partially accepted original transmission, preserve accepted submissions and target the rejected submission scope under the applicable procedure. Do not add unrelated new returns to make a repair batch more convenient.

A rejected correction remains a correction on its retry; it does not become a replacement simply because the acknowledgment says Rejected. The B-series form instructions also say not to file a corrected Form 1094-B. These distinctions prevent a generic retry button from becoming the team's entire decision process.

Copy the actual error code, text and location reference into a protected issue record, or link their source artifact. Include the receipt and submission context needed to identify the affected scope. A record number alone can be ambiguous across different submissions.

Describe what needs to be established: which generated field conflicts with the applicable rule, whether a manifest and data-file pair disagree, or which reviewed source value is missing. Ask a specific question instead of forwarding an entire payload with the instruction fix this.

Preserve the before value, approved change and regenerated version when a repair is made. Re-run the checks affected by the change. Do not assume that changing a displayed message or clearing a local warning proves the subsequent IRS outcome.

Fictional example: Pine Crossing's original transmission PC-22 contains submission A with 72 returns and submission B with 28. The actual acknowledgment is Partially Accepted. A is Accepted; B is Rejected with technical error details identifying B's generated data.

The operator creates internal issue PC-REPAIR-1 for B's 28 returns. The software owner uses the actual error artifact to identify and repair the generation problem, then supplies the revised validation report. PC-REPAIR-1 is an internal label, not an invented IRS error code.

The repair scope is 28 returns. The 72 accepted returns stay outside the replacement submission. The intended original population still totals 72 + 28 = 100, but that does not justify resending all 100.

After the properly associated replacement is sent, its receipt and acknowledgment are linked to B's issue. If the replacement also fails, the team preserves the original rejected association and follows the repeated-replacement instructions rather than treating the latest failed attempt as a fresh original filing.

Save the repair decision, changed artifact references and actual resubmission operation in the batch control log. Record the resulting acknowledgment in the submission tracker. A repaired file waiting on a workstation is not a completed agency follow-up.

If the result remains unknown, carry the evidence gap forward with an owner. If the subsequent acknowledgment identifies another problem, link a new investigation to the same history rather than overwriting the earlier result.

Use the current AIR guide for applicable replacement timing and association rules. This queue is a way to organize the investigation, not a new extension of a filing deadline or a guarantee of acceptance. Preserve the actual dates so the responsible filing team can evaluate timeliness correctly.