A First-Time 1095-C Filing Runbook

Write down the legal employer, EIN reference, reporting calendar year, reason for the first filing, and the person who has reviewed the employer's reporting scope. Reasons can include a growing workforce, a new company, a change in service provider, or previously unhandled reporting. Those situations do not all have the same legal consequences.

Have the scope reviewer address ALE status and any related-employer considerations using the IRS ALE determination guidance. Obtain a reviewed population definition rather than estimating required forms from the current headcount.

If earlier-year obligations are uncertain, separate that review from the current preparation project. The coordinator can collect records while the reviewer determines which years and employers need action.

Decide who will prepare the forms and who will handle transmission or other permitted filing arrangements. Verify the actual services, access setup, input formats, and review outputs before committing the schedule. An account registration is not a completed test of the data handoff.

The IRS AIR page provides the official resources for ACA electronic filing. Ask the designated transmitter to confirm its readiness and the applicable requirements. Keep transmission setup with that responsible party instead of treating the filing coordinator's first spreadsheet as a submission-ready file.

Choose a documented employee-statement process using the applicable year's guidance. Record the owner of employee inquiries and the evidence the team will retain. Establish that workstream early, because its preparation and follow-up needs can differ from the IRS filing work.

Give each task a named owner and internal due date. Record the source for external deadlines separately, so a copied task board cannot accidentally become an outdated deadline calendar.

Use a representative subset of authorized source records, or synthetic records when testing a layout, to confirm that the preparer understands the file. Include a stable employee and relevant change cases such as a hire, termination, or rate change. Have the preparer return a draft or mapping explanation for review.

Check identifiers, date interpretation, conditional fields, and the distinction between offer and enrollment facts. Confirm that the source periods survive the transformation. Fix the layout or definitions before asking every department to produce the full export.

This is a preparation exercise. Keep it distinct from any technical testing the transmitter must perform. Do not label a sample output as filed or approved for production simply because the preparer can display it.

Fictional North Alder Services is filing through a new preparer for the first time. The employer's scope reviewer has identified 157 person-employer records for preparation. HR supplies all 157, but the initial benefits export includes 149 because it excludes eight inactive people with relevant history.

The coordinator changes the export scope, receives the eight historical records, and reconciles 149 + 8 = 157. A small preparation check then reveals that one date column represents an extraction date, not a coverage effective date. Benefits supplies the correct dated history before the full draft is generated.

The employer reviews draft v2, resolves its remaining findings, and approves v3. The fictional example shows two different first-run risks: a missing population and a misunderstood field. Correcting only the count would not have fixed the date problem.

After approval, record the version released, the authorized action, the person handling it, and the expected return evidence. Collect the actual filing outcome and route unresolved issues to the assigned owner. A status such as “sent to preparer” belongs in the handoff column, not the completion column.

Track employee-statement work and inquiry handling under the chosen process. Keep a reference to the applicable-year instruction used. Retain the prepared output, source mapping, approvals, and outcome references together so a later question can be traced to the first run.

Use the downloadable task board to identify the earliest unresolved dependency today. If scope is reviewed but history is missing, request the history. If the facts reconcile but no reviewer is assigned, name the reviewer before releasing a draft. The runbook works best when every step produces an observable output.