Track a 1094-B AIR Submission and Its Evidence

Maintain an attempt record for the actual transmission and linked outcome records for its submissions. In Publication 5165, a submission consists of a transmittal and accompanying individual returns. A transmission may contain more than one submission, so a single overall status can hide different results within it.

Keep the internal packet ID, release version and attempt reference alongside the actual IRS identifiers when received. Do not manufacture an IRS receipt value by using a filename or an upload timestamp. An internal reference is useful precisely because it can exist before an agency receipt is available.

If your software presents a simplified status, preserve the original acknowledgment or an export containing the underlying result. Record which system supplied each value and when it was retrieved.

Use protected references for evidence containing personal information. A broad management view can show scope and status without copying the entire return payload into the register.

The AIR acknowledgment guidance describes statuses including Processing, Accepted, Accepted with Errors, Rejected, Partially Accepted and Not Found. Preserve the exact result instead of reducing all non-rejected outcomes to done.

Accepted with Errors requires examination of the associated errors and applicable follow-up. Partially Accepted indicates that the transmission contains both accepted submissions, which may include accepted-with-errors submissions, and rejected submissions. Identify each submission's result rather than assuming every return shares the overall label.

Processing remains a pending outcome. Not Found calls for investigation of the reference, environment and retrieval process; it is not sufficient evidence that nothing was received. The UI procedures in Publication 5258 provide the UI retrieval workflow. Keep uncertainty explicit while the responsible operator obtains the missing evidence.

Save the time of each meaningful acknowledgment retrieval and its result. Link a later completed result to the earlier pending entry so that the sequence remains understandable. You do not need a separate management alert for every unchanged poll, but the owner should have an identifiable next check.

When receipt information is missing, follow the applicable recovery procedure and confirm the environment before initiating another filing attempt. Publication 5165 describes acknowledgment retrieval and use of transmission identifiers. An application timeout and an AIR rejection are different observations.

Preserve the downloaded acknowledgment and any available error data with the release evidence. If the transmitter supplies only a screenshot, request enough underlying detail to identify the affected submission scope and the actual processing result.

Fictional example: Willow Reach transmits packet WR-12 with two original submissions. Internal submission A contains 60 returns; internal submission B contains 40. The first register event records the actual receipt as received and leaves acknowledgment review pending.

The later acknowledgment shows Partially Accepted: A is Accepted and B is Rejected. The summary therefore shows 60 returns in the accepted submission and 40 in the rejected submission. It does not label all 100 accepted, and it does not create a replacement scope containing the accepted 60.

The operator links B's error evidence to its repair task and leaves A's accepted result intact. The replacement attempt and subsequent outcome get their own records, linked to the appropriate original rejected scope under the AIR procedures.

If the replacement is later accepted, the register can show that all 100 original intended returns have reached an accepted submission outcome while still preserving the original partial result and the intervening repair. That distinction explains both the current state and the history.

Every unresolved outcome should name an owner and a question. For example, ask the transmitter to obtain the acknowledgment for a known receipt, or ask a technical owner to investigate an identified rejected submission. Avoid an unassigned note reading check later.

Use the rejected-packet triage guide when the evidence identifies a failure. Use the batch control log to follow changed file versions. Neither a new file nor an assigned repair task closes the original evidence gap until the subsequent result is reviewed.

Finally, keep federal processing evidence separate from recipient delivery and any applicable state output. The register answers what happened in AIR. Other completion claims require their own evidence and owners.