1094-C Replacement or Correction: Gather the Routing Facts

First identify the previous operation: original, correction, or replacement. Second obtain the actual response or acknowledgment. Third identify whether the issue affects a whole transmission, one submission, or an accepted record. Fourth preserve the references connecting that history to the current packet.

Include the reporting year, environment, employer, original output, and any intervening attempts. A screenshot saying “failed” without these details is not enough to choose a valid follow-up process.

If the outcome is unknown, use the supported receipt or UTID lookup process before proceeding. A missing browser confirmation does not prove the original filing never reached AIR. Treat uncertainty as a retrieval task, not an automatic reason to send new originals.

The publication distinguishes portal rejections from AIR replacements and keeps rejected correction transmissions on the correction path. Read the full procedure rather than applying a blanket “all rejected files become replacements” rule.

Keep the chain of transmission and submission identifiers, including unsuccessful replacement attempts and accepted corrections. Publication 5165 has specific association rules for each path. Repeated replacement failures can require reference to the earliest rejected original, while later corrections have their own record-history requirements.

The operator worksheet should store a readable internal case ID that points to the actual identifiers, not replace those identifiers. Label aliases clearly so nobody copies a fictional or internal reference into a technical element.

Have a second reviewer compare the proposed reference with the prior outcome evidence. An otherwise correct file associated with the wrong original can create another rejection or a confusing record history.

Fictional Cedar Harbor Group sends a packet with submission A containing 150 returns and submission B containing 50. The acknowledgment is Partially Accepted: A is accepted and B is rejected. All figures and labels here are fictional internal examples.

The operator opens a follow-up case for B's 50 records. The technical owner fixes the confirmed problem and prepares the applicable rejected-submission replacement, using the required original association. The accepted 150 are outside that replacement scope.

Across the original and follow-up attempts, 250 record instances were sent: 200 originally plus 50 in the replacement. The intended population remains 200 unique original return records. This distinction helps prevent the replacement from being counted as 50 additional annual employee forms.

When the accepted authoritative employer record needs correction, collect the complete revised employer information and the evidence for changed fields. The 2025 corrected-return instructions require a standalone corrected authoritative 1094-C without accompanying 1095-Cs.

Assess any employee-form corrections separately. Publication 5165 describes separate handling when both employer and employee records need changes. Do not attach all employee records to an authoritative correction simply because they were in the original filing packet.

Likewise, establish whether the questioned 1094-C was authoritative. A nonauthoritative transmittal does not use the same correction treatment. Send the original designation and issue details to the preparer before generating a revised summary.

Record the selected procedure, source section, scope, original references, prepared version, and actual approval. Have the transmitter confirm the relevant timing requirements using the actual dates. Publication 5165 includes replacement timing provisions; an internal target date should be based on that review rather than guessed from the day an employee reported an issue.

After the next attempt, retrieve the acknowledgment and link it to the case. If another failure occurs, add it to the existing chain and reassess the current process instead of resetting the case to “new original.”

The downloadable routing worksheet is complete when another qualified operator can reconstruct why this particular action was selected. It should preserve the facts and the documented reasoning, not merely a checkbox labeled “resubmit.”