Read a 1095-C AIR Acknowledgment and Create an Action Queue

Locate the actual transmission status, receipt or transmission reference, environment, and retrieval time. Then examine submission-level outcomes where applicable. A rejected submission and an accepted submission with employee errors require different follow-up context.

Publication 5165, section 6, defines the acknowledgment statuses and describes error detail. Preserve the exact status in the queue instead of replacing every unfavorable result with an internal “failed” label.

If the status is still Processing, or the lookup is Not Found, handle that retrieval state before treating a partial local display as a complete list of employee errors. The absence of visible messages at that moment does not establish that every record is accepted.

Use the generated crosswalk from the actual transmitted file. Publication 5258 describes the combination of receipt, submission, and record identifiers used to identify an employee return. Match the complete context, not just a record number that can recur in another submission.

Link that technical record to the internal employee-employer key, reporting year, approved version, and source records. If the data was regenerated later, retain both maps and use the one corresponding to the acknowledgment's original packet.

Preserve the actual message code, text, and supplied data location. A paraphrase is helpful for the assigned owner, but it should sit beside the original evidence rather than replace it.

Fictional Laurel Meridian Company receives an Accepted with Errors acknowledgment. Its internal reading table maps seven messages to five employee returns. The row labels below are internal aliases and are not valid IRS identifiers or invented error codes.

The queue has five record cases while retaining all seven messages: 2 + 2 + 1 + 1 + 1 = 7. Two repeated messages on a record do not call for two unrelated employee correction filings. The responsible reviewer determines the actual repair and filing treatment.

Each case should contain the employer, year, technical reference, internal source key, exact message, suspected data family, owner, and next action. State whether a source fact is confirmed or still under investigation.

Route employment and identity evidence to its source owner, enrollment dates to the benefits owner, and serialization or mapping problems to the technical owner. Some cases need both a source decision and a software repair; keep those dependencies visible.

Group related cases by a suspected shared cause only after preserving individual references. If a single conversion mapping affected many people, one technical fix may resolve the cause, but every affected reported record still needs its reviewed disposition.

Compare the imported message count with the source error file and inspect any truncation or incomplete-detail notice. Publication 5165 describes limits that can truncate error detail. Do not call the queue complete when the source itself says otherwise.

Keep separate counts for messages, distinct affected returns, submissions, and root causes. These measures serve different purposes. The employer may need a record-level impact count, while the technical team needs the number of shared mapping repairs.

Spot-check several mappings from the raw acknowledgment to the sent file and then to the internal employee record. A wrong join can create a persuasive-looking action list for the wrong people, especially after record ordering changed between drafts.

Record the source finding, approved changed facts if any, and the selected follow-up procedure. If a correction is required, preserve the original association and complete revised output. If another disposition applies, record the actual rule and reviewer rather than simply deleting the error.

After the authorized follow-up, link the new acknowledgment and remaining messages to the same case. Keep a distinction between “source verified,” “revision prepared,” and “agency follow-up resolved.” Those internal milestones are not interchangeable.

The downloadable queue provides columns for both original evidence and the operational decision. Use it to hand a case to someone who has not seen the transmission history and confirm that they can locate the exact record without exposing unnecessary employee details.