1095-B Resubmission Controls for Filing Teams

Open the original transmission record and its latest response. Capture the exact submitted file, receipt or fault, timestamp, environment and affected submissions. If the outcome is still unknown, obtain the missing evidence before launching a second delivery of the same records.

A provider timeout describes the provider's observation, not necessarily the agency's state. Ask whether the file reached AIR and whether a receipt or acknowledgment can be recovered. Keep this uncertainty visible in the work queue. An operator should not turn an unresolved first attempt into a second original simply because the local screen no longer shows progress.

Publication 5165, section 7.2 distinguishes portal faults from AIR rejections. Portal faults are repaired and resent using the original transmission type; AIR-rejected transmissions or submissions use the replacement process.

For accepted records that need changes, use the applicable correction process. Publication 5258, section 6 provides the electronic reference rules. A replacement restores the rejected scope; a correction changes an accepted record. Have the transmitter explain which history supports the selected action before preparing the next file.

Keep the decision in plain language beside the technical action. For example, “replace rejected submission 2” is more reviewable than “retry batch.” A mixed outcome may require separate actions for separate parts of the original transmission.

Maintain two linked chains. The source chain shows which approved data version produced each candidate. The agency chain shows which prior transmission, submission or record the next action references. Neither a file name nor a household identifier carries all that information alone.

The AIR composition guide specifies first-rejected references for replacements and references to the accepted correction when correcting again. Preserve the full chain, then let the current rules determine the reference placed in the output. Do not mechanically reuse the most recent receipt for every action. Record why the selected prior reference is the correct one for this particular replacement or correction.

Fictional batch Q25 contains 100 original returns. Submission A has 60 accepted returns; submission B has 40 rejected returns. After review, two returns in A also need corrected information. The operator plans a replacement for B and a separate correction action for the two accepted returns.

The three actions contain 142 record appearances, but the intended population remains 100 returns. Summing attempt counts would inflate the filing inventory. Track the final outcome for each of the 100 source keys and preserve the earlier attempts as history.

Compare the intended scope with the actual candidate. Every rejected return that belongs in the replacement must be accounted for, and accepted records outside that scope must stay out. For a correction, review the complete return, including covered-person rows that did not change. A repair should not become a partial household export.

Use a second check on the prior agency reference, source version and action type. Regenerate file-dependent metadata through the transmitter's supported workflow after changing the data. Renaming a file does not establish that its contents, checksum or lineage are correct. Keep the previous candidate retired and give the released candidate an internal identifier that cannot be confused with an earlier version.

Retrieve and reconcile the new acknowledgment. Link it to the action that produced it and update the current outcome for each affected source return. Preserve unresolved results rather than treating the second attempt as successful merely because it was sent.

Review the population ledger for returns with no resolved delivery, several competing original attempts or an unprocessed follow-up. Keep recipient-copy and selected state actions linked to the change, with their own evidence. If the original or later filing may be late, assess timeliness under the applicable current rules using actual timestamps. This guide's internal retry workflow does not grant an extension or guarantee relief.