Prepare a 1095-C Correction Packet

Find the employer, reporting year, original prepared output, and actual filing outcome. If a correction has already been submitted, include that history too. Ask the preparer for the identifiers that connect your internal record to the record in the filing process.

Publication 5165, section 7, distinguishes corrections from rejected-file procedures. Do not classify every problem as a correction merely because a source value needs to change.

Include the original form or prepared data, employer identity, internal person reference, reporting year, vendor batch ID, and the relevant filing identifiers provided by the transmitter. Preserve original identifying values in controlled storage if those values themselves need correction.

Attach the actual outcome and any prior correction history. A coordinator can use a readable internal ID in the cover sheet while the authorized preparer accesses the full identifying records through the agreed secure process.

The purpose is exact association. If the preparer cannot establish which record the proposed change belongs to, have it resolve that reference problem before release. Re-sending an entire original employer batch is not a substitute for identifying the affected record.

Build an original-versus-corrected table with one row for each affected field or period. Include the original value, supported new value, source record, reason, and reviewer. If the correction changes an effective date, preserve the underlying date and identify the months the preparer needs to reassess.

Distinguish a source correction from a change in reporting interpretation. An updated administrator record may establish different facts; a reviewer may instead decide that the same facts were coded incorrectly. The packet should make that distinction visible.

Provide the complete supported record for preparation. Publication 5165 directs electronic corrections to contain complete records, not only the changed data elements. Your comparison table explains the changes, while the preparer produces the complete required output.

Determine whether the issue is isolated to one person or comes from a source or mapping error that affected others. Search for the same rate source, eligibility group, date conversion, or employer mapping in the working data. Record the method used to find the potentially affected population.

Ask the responsible reviewer whether employer-summary information also needs review. Keep employee-form changes and employer-summary questions distinct in the packet; the preparer and transmitter must select the appropriate process for each.

Include employee-statement follow-up in the review. The corrected-return instructions address previously filed forms and recipient statements. State what was previously provided and have the preparer identify the required action under the applicable furnishing method. Do not assume that resolving an IRS record completes every employee-facing obligation.

Fictional Aspen Canal Services discovers that a July rate update was omitted from three prepared records. Its reviewer confirms that the relevant monthly contribution should be $110 for July through December, while the prepared forms show $125 for those months. All amounts and circumstances here are fictional; the reviewer has already confirmed the field's applicability.

The comparison shows six affected monthly entries per person and a $15 difference per entry. Across three people, the packet identifies 18 changed monthly entries: 3 × 6 = 18. The aggregate difference is $270, which is a reconciliation total only, not tax owed, a penalty, or a conclusion about whether a correction exception applies.

The preparer receives the rate document, original filing references, the three-person scope list, and complete revised records for review. The employer does not send a table of 18 changed cells as if that were itself a valid correction filing.

Have the employer reviewer confirm the supported facts, the affected population, and the proposed revised output. Record the actual approval, version, and authorized action. Ask the transmitter to confirm the process and original references it will use before release.

After submission, retain the new output and outcome with a link to the prior record. Keep unresolved errors visible. If another issue is discovered later, provide the complete correction chain to the transmitter instead of assuming the first original reference is always the correct one to reuse.

Use the downloadable packet checklist to organize the request. Start by filling in the employer, year, prior outcome, and record reference. If those four items are unknown, gathering them is the next useful action before preparing a technical correction.