Review a 1095-B AIR Acknowledgment

Start with the actual acknowledgment, associated error data when present and the exact submitted record inventory. A provider summary can help navigate, but ask for the underlying agency evidence when the summary does not identify which submission or record was affected.

According to Publication 5258, a Receipt ID confirms receipt; the acknowledgment supplies the processing outcome. Record the retrieval timestamp separately from the transmission timestamp. Store the submitting account or provider reference, environment and coverage year beside both. This prevents an old response, or a successful test, from being attached to the current production batch.

Publication 5165, section 6 defines AIR outcomes. Accepted with Errors requires review of the error detail. Partially Accepted means the transmission includes both accepted and rejected submissions. Processing is unfinished; Not Found means the requested reference was not located.

Translate the response into a work decision only after reading its level. An outer transmission status cannot tell the reviewer which household needs attention. Record submission-level results under their parent transmission, then attach any return-level errors beneath the appropriate submission. Keep the agency's exact wording in one field and the team's action in another. Labels such as “under enrollment review” are internal workflow states, not AIR statuses.

Use the saved mapping between the receipt, submission, return record and internal household key. Section 3 of Publication 5165 describes the unique record reference as Receipt ID, Submission ID and Record ID joined in sequence. Preserve all components instead of matching a bare record number across several files.

Open the version actually transmitted. A current enrollment screen may already contain changes and may list household members in a different order. Where the feedback includes a location within a repeated covered-person group, resolve that location against the original output. Save the resulting internal member key in the issue register. If the join is ambiguous, investigate the mapping before requesting a change from a member.

Fictional transmission R-DEMO contains submission 1 with 80 returns and submission 2 with 20 returns. The outer result is Partially Accepted. Submission 1 is Accepted with Errors and identifies two issues on the same return. Submission 2 is Rejected. The labels below simplify an acknowledgment for training; R-DEMO is not a valid IRS receipt and no error codes are invented.

The batch contains 100 forms, not 102. Two messages do not mean two defective returns. The review must account for 80 accepted returns and 20 rejected returns while preserving the two unresolved issues inside the accepted group.

Copy the official code, text and supplied location into the restricted issue record, then add a plain-language observation. A structural problem, a member identity discrepancy and a transmission metadata issue need different owners. Do not manufacture a universal repair by searching for a similar-looking message from another form or year.

For a suspected source-data issue, compare the original field with the authorized enrollment evidence. For an output-format issue, give the software team the schema version and smallest relevant protected excerpt. Record whether the evidence is complete. If an error report indicates truncation or the provider delivered only part of it, the visible list cannot establish that every outstanding issue has been inventoried.

Reconcile every submitted return to its submission outcome. Add separate counts for unique affected returns, feedback messages and unresolved cases. Keep a link to the subsequent action rather than editing the original acknowledgment to make its status look cleaner.

Assign a reviewer to unmatched references and unexpected count differences. A review is complete when the full batch is accounted for and each unresolved item has an appropriate next action. Filing resolution can remain open after acknowledgment review finishes. For a provider handoff, request the evidence location, the records affected and the next scheduled update. Avoid closing the entire batch because the provider marked its upload task complete.