1095-C Electronic Batch Preflight Checklist

Record the employer, reporting year, internal batch ID, approved version, source cutoff, and intended operation. Confirm that the generated file corresponds to the latest approved output. If the preparer regenerated it after approval, inspect the differences and obtain any required refreshed review.

Keep the exact release file in controlled storage and prevent silent replacement while the operator is sending it. An export with the same filename can still contain different records.

Check the transmission ledger for overlapping active work. A second operator or provider should not start a new original release for the same approved population merely because the first result has not yet appeared on a dashboard.

Maintain a crosswalk from the internal employee-employer key to the generated submission and record identifiers. Publication 5165 explains how receipt, submission, and record references identify records in feedback and follow-up.

Do not treat a record number alone as globally unique. The same number can occur in a different submission. Keep the complete context in the crosswalk.

Compare the generated person-employer records with the approved batch. Investigate missing records, unexpected additions, and duplicate original assignments. Reconcile the actual accompanying count to the transmittal's reported count, as required by Publication 5165.

For conditional covered-person reporting, compare the generated related-person rows with the approved prepared data. A transformation can preserve the employee while dropping a family member or a coverage period. This is an export-integrity check against approved facts, not a new eligibility decision.

Review records with special characters, multiple employment periods, and other source features that exercise distinct transformation paths. Preserve source IDs in the crosswalk so a later error can be investigated without guessing from a name.

Fictional Maple Meridian Services approves 240 employee-employer records. The release export contains 241 records. The preflight crosswalk shows that one employee was included twice after two division files were combined for the same employer.

The operator confirms that the extra row is an accidental duplicate of the same approved record, not a separate employer relationship. The preparer repairs the export and regenerates 240 records: 241 - 1 = 240. The team rechecks the affected mapping and verifies that no other duplicate original assignments remain.

The generated record ordering changes, so the operator saves a new crosswalk for the final file. Retaining the old map would make a later acknowledgment point to the wrong internal employee. All counts and circumstances are fictional and illustrate the integrity check.

Confirm the tax year, processing-year requirements, environment, channel, and schema references with the technical owner. The IRS AIR page supplies current operational resources. Prior-year form data may require a different package than the current manifest.

Run the applicable technical checks against the exact final file and preserve the results. Use the composition rules in Publication 5258 rather than assuming the printed form's formatting is an electronic schema specification.

Record checks that were not performed or exceptions that remain. A generic “validated” label is not enough to distinguish a file-read check from schema validation or a substantive employer review. Give the operator a concrete disposition for any unresolved issue.

Record the actual operator, time, final file reference, and approval. Capture the returned receipt or available transmission reference and attach it to the generated-record map. That association is what turns later acknowledgment detail into an actionable employee-level queue.

Assign the person who will retrieve and review the acknowledgment. Preserve employee-record errors and follow-up actions separately from file-level status. A receipt event is not a finding that every employee record is accepted and accurate.

The downloadable worksheet is useful when a team changes software or providers because it tests the handoff between approved content and transmitted records. Complete it with evidence from the real final file, and retain the crosswalk through the full correction or replacement history.