1094-B Electronic Filing Preflight Checklist

Record the filer, reporting year, internal packet reference, current version and intended operation. Distinguish an original filing from a documented replacement or correction workflow. A filename such as final.xml does not supply that information and can be overwritten without anyone noticing.

List the submissions and individual-return inventories included in the proposed transmission. In Publication 5165, a submission combines a transmittal with its accompanying individual returns, while a transmission can contain multiple submissions. Keep an internal packet label separate from those AIR structures.

Identify held returns and their next owner explicitly. A clean release count should not conceal records that disappeared from the expected population during preparation. This is an operational reconciliation control, not a new IRS filing exception.

Check the intended test or production environment, filing channel, software release and applicable schema package. The IRS AIR resource page links the current technical materials. Use processing-year and tax-year labels separately when checking compatibility, particularly when filing a prior-year return.

For the AIR user interface, Publication 5165's UI checklist describes the manifest and form-data XML files. Verify that the pair was generated together for the intended release, rather than selecting an old manifest beside a newly generated data file.

The downloadable worksheet here is an internal review manifest. It does not replace the IRS XML manifest. Ask the transmitter or software owner to identify the applicable validation evidence, including its version, rather than assuming that a saved recipient PDF demonstrates electronic-file readiness.

Record the result and supporting artifact for each row. A checked box without an identifiable evidence version makes the review difficult to reproduce.

The 1094-B line 9 instructions count accompanying Forms 1095-B and exclude continuation sheets. For a release inventory, retain separate totals for returns and covered people when both are useful. Neither PDF page count nor enrollment-row count substitutes for the number of returns.

Compare the actual included statement references with the approved list, not only the grand total. An extra copy of one statement and an omitted different statement can offset each other numerically.

Investigate differences before generating a revised packet. After a repair, repeat the affected count and file-pair checks. Preserve the earlier results as history and associate the new review with the new version. The batch control log supports that sequence.

Fictional example: Reed Harbor's approved 2025 inventory contains 84 returns in one submission. Export version 7 also contains 84 return records. A statement-reference comparison finds RH-026 twice and RH-071 absent, so the matching total does not establish a complete population.

Preparation removes the extra RH-026 occurrence and restores RH-071. The arithmetic remains 84 - 1 + 1 = 84 returns. Version 8 now has the correct statement set, but an operator has selected the version 7 manifest beside the new data file.

The release reviewer requests a matched version 8 pair and the corresponding validation results. Only after the statement set, file pair and review evidence all refer to version 8 does the team record its actual release decision. The saved checklist explains why the original count-only check was insufficient.

These labels are fictional internal references, not real taxpayer identifiers or IRS acknowledgment values. The example illustrates a review method and does not claim that a particular AIR rule would catch every business-level duplicate.

Record the actual transmission attempt in the AIR submission tracker. The acknowledgment procedures in Publication 5165 distinguish receipt information from processing results. A successful upload is therefore a reason to retrieve and examine the outcome, not to close the filing task.

Assign someone to preserve the returned acknowledgment, identify affected submissions and coordinate any required follow-up. Keep recipient delivery and any separately applicable state work in their own completion records.

When a transmitter performs the filing, include those evidence expectations in the handoff package. Preflight is complete when the exact release is ready and its follow-through is assigned; filing completion depends on the actual subsequent outcome.