1095-C Data Collection Checklist for a Filing Batch

Put the reporting year, legal employer, internal batch ID, preparer, and source cutoff on the cover sheet. Attach the approved population list and identify any open scope decisions. If the batch contains only one department or one portion of an employer's population, say so explicitly.

Request historical data, including relevant inactive people and midyear events, rather than relying on a current employee list. Have the scope reviewer determine who belongs in the filing population; the collector's role is to ensure the supporting records are available.

Keep a person-employer key in the working packet. That makes it possible to connect the same person across HR, payroll, and benefits while preserving the employer assignment approved for this batch.

“Required” below means a core item for the 2025 form. “Conditional” means the preparer must apply the relevant instructions; it does not mean the data can be ignored during intake. The official 2025 Form 1095-C shows the field groups.

For each row, record the source file, owner, effective period, and unresolved questions. Keep collection markers out of the final form unless the preparer's layout explicitly asks for them.

Gather dated employment events, offer records, eligibility history, applicable rate information, and enrollment changes. Preserve the original dates even if the preparer eventually summarizes them by calendar month. A monthly summary without its source dates can be difficult to review when a person starts or ends coverage midmonth.

Do not substitute the employee's chosen deduction amount for supported offer-cost information. The preparer needs to know which plan and rate records the employer reviewed. A payroll adjustment can change a deduction without changing the underlying offer.

For conditional entries, distinguish “fact collected and not applicable” from “fact missing.” The reviewer should be able to see why a blank is intentional. Refer unresolved code selection to the reporting reviewer with the source history attached; this collection checklist does not replace the code-specific instructions.

The 2025 form separates offer information in Part II from covered-individual information in Part III. The recipient explanation on the official form describes Part III in the context of self-insured coverage. Confirm the reporting arrangement with benefits before requesting or omitting this data family.

When the packet requires covered-person information, request a dated history rather than a current family roster. Include additions, removals, and retroactive changes with a source reference. Preserve the relationship to the employee so similarly named people are not merged.

Handle missing identifying information as an explicit exception under the applicable instructions. Do not extend an alternative allowed for one covered-person field to a different employee-identification field. Record what is missing and route the issue to the preparer rather than inventing an identifier or placeholder date.

Fictional Brook Lantern Company has a reviewed batch of 186 people. HR supplies identity and employment history for all 186. Benefits supplies monthly offer history for 174 and flags 12 people who moved between eligibility groups during the year.

The collector creates 12 exceptions instead of marking the file complete because it contains 186 names. Eight histories are recovered from the benefits archive. Four require the benefits lead to confirm the effective dates against original offer records. Once resolved, 174 + 8 + 4 = 186 people have documented offer histories.

The preparer then applies the form rules and identifies any intentional conditional blanks. The fictional arithmetic checks source completeness; it does not establish that all 186 forms are correctly coded or ready to transmit.

Attach the data dictionary, row counts, unique person-employer count, date range, and exception log. Label whether a later file replaces the full batch or updates particular records. Ask the preparer to confirm the counts it received and identify any fields it could not interpret.

Keep untransformed source files in controlled storage and point to them from the packet manifest. If the collection team changes a value, preserve the supporting record and the reason. This lets a reviewer distinguish a genuine source correction from a formatting change.

Use the downloadable worksheet once per batch. Before marking collection complete, inspect a stable employee, a midyear change, and a conditional-data case. A template that handles only the simplest record can look complete while leaving the hardest records unreviewable.