The practical answer

Reconcile line 9 to the actual Forms 1095-B accompanying that transmittal. Start with the approved statement inventory, compare generated record membership and resolve missing or repeated returns before approving the count.

Several totals can appear in a coverage reporting project: people, statement groups, generated files and printed pages. Only the relevant accompanying-return count belongs on line 9. This guide uses the final 2025 instructions and an original fictional reconciliation to show why changing a number alone may leave the batch wrong.

Define the counting unit before comparing totals

The 2025 line 9 instructions require the total number of Forms 1095-B transmitted with Form 1094-B. A 1095-B can contain several covered individuals, so a member roster cannot be used as the transmittal count without establishing the return grouping.

Continuation sheets do not create additional Forms 1095-B for this count. Neither do recipient instruction pages, duplicate print copies or internal review reports. Record these other totals separately if they help operational review.

Fix the reporting year, filer and exact packet scope. A dashboard showing every statement prepared for the year may include returns assigned to another transmittal or work not yet approved. The count must describe the accompanying batch, not an unexplained overall project total.

Build a bridge from approved statements to output

Original source-to-transmittal reconciliation fields
StageRecord to retainComparison
Approved source groupingStatement keys and associated covered people.Expected return membership for the packet.
Prepared outputGenerated 1095-B record inventory and version.Missing, extra or repeated statement keys.
Transmittal draftLine 9 and matching packet version.Count equals the corrected accompanying inventory.
Supporting pagesContinuation relationships and review material.Pages remain associated without becoming extra returns.

Use stable internal statement references in the working comparison. Keep the controlled mapping to actual recipient and filing information separately. A reviewer should be able to locate a difference without circulating full identity numbers in a general count report.

Worked example: 240 statements contain 610 covered people

Fictional example: Blue Fen Coverage approves 50 statements with one covered person, 100 with two and 90 with four. The return inventory is 50 + 100 + 90 = 240 Forms 1095-B.

The covered-person total is 50 × 1 + 100 × 2 + 90 × 4 = 610 people. The two totals are both useful but answer different questions. If all 240 returns accompany this transmittal, the intended line 9 count is 240, not 610.

The reviewer retains the statement-to-person relationship map and checks that each approved statement appears once in the generated inventory. A count report should label its units explicitly so a later operator does not replace 240 with the more prominent 610-member roster total.

Resolve output differences before fixing the transmittal

Continue the fictional case with a generated output containing 242 records. Membership review identifies three accidentally repeated statement records and one omitted approved statement. The apparent difference of two records hides four specific defects.

The correct repair is 242 - 3 duplicates + 1 omitted return = 240 generated returns. The preparer fixes the output population, regenerates the inventory and then ties line 9 to the corrected version. Merely typing 240 on a transmittal attached to the flawed 242-record output would not reconcile the packet.

Retain the exact repeated and missing keys and their dispositions. If the product deliberately split a statement or changed grouping, establish the reviewed reason rather than labelling every difference a duplicate. The intended return structure must be known before a count adjustment is approved.

Review late changes and separate packet scopes

If a return moves to another packet, record both the removal and the destination assignment. Repeat the affected counts and confirm that it is not present as an unintended original in both. A shared preparation dashboard should not obscure which transmittal owns the final return.

Keep original and correction work identifiable in the inventory. Line 9 still concerns the returns accompanying the particular transmittal, while the operation's history belongs in separate review evidence. Do not use a count of transmission attempts as the number of accompanying statements.

The instructions say not to file a corrected Form 1094-B. When a post-filing question arises, preserve the actual history and route it for the appropriate B-series review rather than inventing a corrected transmittal simply to change an internal count.

Approve the reconciled packet and preserve its version

Save the approved statement inventory, generated inventory, difference dispositions and final 1094-B draft together. Record the reviewer, date and version. Include any continuation relationships needed to explain why the page count exceeds the return count.

Have a second reader reproduce the Blue Fen arithmetic and locate one statement through the source and output inventories. They should be able to distinguish the 610-person total, the flawed 242-record output and the corrected 240-return packet without guessing what any number means.

Use the manager review packet for approval evidence and the batch structure guide for the hierarchy. The reconciled transmittal is a prepared-data result; electronic packaging and agency outcome checks remain separate operational steps.

A count reconciliation repairs the inventory before the header

A count reconciliation repairs the inventory before the header: Approved groups; Generated difference; Repair membership; Tie line 9
Fictional example. The 610 covered people and printed pages are separate units from Forms 1095-B.
Read the workflow as text
  1. Approved groups. Fifty single-person, one hundred two-person and ninety four-person statements total 240 returns.
  2. Generated difference. The output has 242 records because of three repeats and one omission.
  3. Repair membership. 242 minus 3 plus 1 restores the approved 240-return population.
  4. Tie line 9. The final transmittal count matches the corrected accompanying inventory.

Put this guide to work

1094-B source, batch and transmittal count 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 line 9 count statements or covered individuals?

It counts the accompanying Forms 1095-B. A statement may include several people, so the member total can be much larger. Label each number's unit in the reconciliation.

Can I fix a mismatch by changing only line 9?

Only after establishing that the accompanying inventory is correct. If the output contains missing or repeated returns, repair that population first and then tie the transmittal to the corrected version.

Do continuation pages count as extra returns?

No. The 2025 instructions exclude continuation sheets from the count of Forms 1095-B submitted with the transmittal.

Why compare record membership when the totals match?

Equal totals can hide substitutions, duplicates offset by omissions or returns assigned to the wrong packet. A statement-key comparison establishes which records are actually present.

What should happen after a return moves to another packet?

Update both inventories, repeat the relevant counts and confirm the final assignment. Preserve the move so a reviewer can explain the difference and avoid unintended duplicate original inclusion.

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 Instructions for Forms 1094-B and 1095-B

    Line 9 accompanying-return count, continuation exclusion and no corrected 1094-B.