The practical answer

Before releasing a 1095-B batch, reconcile each return and its covered people to the approved source, validate the actual electronic output and preserve a crosswalk for later AIR feedback.

This checklist is for the operator who receives approved coverage data and prepares Form 1095-B records for electronic filing. It starts after the organization has determined what coverage to report. Its purpose is to catch damage introduced during extraction, mapping and export while making every later agency message traceable to the correct return.

The examples use tax year 2025 and current processing-year guidance checked September 5, 2026. They are fictional operating examples, not files to submit.

Pin the tax year before the export

Record the coverage year, processing environment, software release and export timestamp before reviewing individual records. A file produced in 2026 can report 2025 coverage. Calling both values “year” in a spreadsheet makes it easy to select the wrong rules or overwrite a prior-year job.

The IRS AIR program page distinguishes processing year 2026 from tax year 2025 and describes current manifest and prior-year form-data packages. Ask the transmitter to confirm the combination used by the actual export. Keep that confirmation with the batch. Use final instructions for the coverage year, then recheck current technical updates when an old return is transmitted later.

Preserve the return-to-member relationship

Build a crosswalk from the source household or policy record to the resulting Form 1095-B and every covered-person row inside it. One return can contain several covered individuals. A member count therefore cannot stand in for the number of forms being delivered.

Give each source return a stable internal key that survives sorting, splitting and regeneration. Store the member keys beneath it in export order. A household name is an unreliable join key: people can share names, change names or appear under different responsible individuals. Record the approved issuer and coverage-year association too. When two exports contain the same source key, investigate their purpose before assuming either is a duplicate.

Inspect the identity fields that actually travel

Review the electronic output, rather than relying exclusively on a PDF preview. Under the 2025 B-series instructions, covered individuals use a TIN when available and a birth date when no TIN is entered. The responsible individual has separate rules, including an exception when that person is not covered. Government-filed returns cannot use truncated TINs.

Keep full identifiers in restricted filing files and use internal keys in review tickets. Flag masked values accidentally copied from recipient statements, numbers changed by spreadsheet formatting and birth dates shifted by locale conversion. Compare questionable values with the authorized source. Never invent a number, insert a convenient birth date or replace a supplied TIN merely to clear a validation message.

Work through a fictional record preflight

Fictional batch B25-17 contains three returns and seven covered-person rows. The reviewer checks three different problems before release. These are internal observations, not IRS error codes or predictions of an AIR outcome.

Fictional record-quality findings
Source returnObservationRelease action
H-101, three peopleOne member identifier contains masking charactersRegenerate from the restricted source field
H-102, two peopleMember order differs from the saved crosswalkRefresh and verify the exported member mapping
H-103, two peopleCoverage flags differ from the approved snapshotResolve the export mapping with enrollment

The final control total remains three forms and seven people. Fixing a crosswalk does not add a form. The coverage discrepancy requires a source decision before regeneration; the filing operator should not choose new coverage months from memory.

Validate the generated record structure

Run the production candidate through the software's year-appropriate schema and business-rule checks. Save the result against the candidate's exact file version. A check performed before the last data refresh does not describe the current export. The B-series electronic filing instructions expressly direct electronic filers to XML formatting rules rather than paper-format directions.

Review both failures and changes introduced by the exporter. Check whether blank optional fields become unwanted placeholders, whether required groups are omitted and whether the member list was truncated. Test a representative long household and a record using a birth date instead of a TIN. Obtain an explanation for any transformation that changes the information approved by the source team.

Release a reproducible record package

Keep the approved source snapshot, final form/member crosswalk, validation result and export together. Identify who resolved each hold and what evidence supported that decision. If a hold remains, record whether the return is excluded from this particular batch and who owns the outstanding filing work. Exclusion from an export does not resolve the reporting obligation.

Give the transmitter the final record count and the version that passed review. Ask for the eventual AIR references mapped back to the same internal keys. Reconcile the returned filing inventory against the released inventory, including any software-driven split. Archive superseded candidates distinctly so a second operator cannot mistake an earlier file for the approved version.

The record preflight trail

The record preflight trail: Source snapshot; Member crosswalk; Output check; Release package
An internal preflight trail prepares the records for transmission; agency acceptance is verified afterward.
Read the workflow as text
  1. Source snapshot. Approved coverage year and household keys
  2. Member crosswalk. Return keys and exported person order
  3. Output check. Validate the exact candidate version
  4. Release package. Reconcile final forms and people

Put this guide to work

1095-B record-quality release worksheet

Save the editable text worksheet and use it with your own records. Keep completed copies in your secure working files.

Download the worksheet TXT

Common questions

Does passing preflight mean AIR has accepted the forms?

No. Preflight is an internal release decision. Keep the batch open until its agency processing result has been retrieved and reconciled. A successful upload or provider validation screen answers a different question.

Should I count dependents as additional Forms 1095-B?

Use the actual return count and a separate covered-person count. For the fictional batch, three forms contain seven people. Keeping both totals makes household truncation easier to detect without inflating the form inventory.

Can a missing TIN be filled with zeros?

Do not fabricate identity data. Route the record for review of the applicable TIN and birth-date rules, the information actually available and any required follow-up. Preserve the original missing-data condition in the source history.

What if an enrollment change arrives after approval?

Retire the old candidate, assess the affected return and regenerate when appropriate. Repeat checks on the changed output and update the crosswalk. Do not attach an old validation report to a newly produced file.

What should a small filing team review first?

Start with masked identifiers, year selection, missing member relationships and differences from the approved coverage snapshot. Then run the complete available validation. Risk-based review helps sequence work; it does not excuse unresolved required fields.

Official sources and scope

Sources checked September 5, 2026. Use the edition for the tax year and filing method you are working with; later instructions may change thresholds, fields, or procedures.

  1. IRS 2025 B-series instructions

    Tax year 2025 identity fields, form/member distinction, untruncated IRS identifiers and electronic-format requirements. The separate aggregate e-file rule in these instructions takes precedence over the conflicting separately-by-type sentence in Pub. 5165; no threshold calculation is taught here.

  2. IRS AIR program and tax-year updates

    Processing year 2026/tax year 2025 and prior-year schema distinctions checked September 5, 2026. Technical versions must be rechecked for later transmissions.