Set a 1095-B Coverage Data Cutoff and Reconciliation Plan

Inventory each carrier, eligibility administrator or internal enrollment source, with reporting entity, population, coverage year and delivery owner. Record whether the feed is a complete snapshot or only changes since the prior file. Mixing those two formats can erase members or duplicate coverage.

Capture effective-date conventions, termination-date meaning, dependent identifiers and retroactive-change handling in the feed contract. An enrollment system's end date may be inclusive or exclusive; the reporting team must establish which before converting it into coverage months. Keep the received file unchanged and store transformations separately. The cutoff plan is a data-control agreement, not authority to change the underlying coverage facts.

When a feed arrives in several parts, record the expected part count and confirm all parts belong to the same extraction. Combining a new employee file with an older dependent file can preserve plausible totals while assigning coverage to the wrong statement version.

The 1095-B instructions report months in which an individual had coverage for at least one day. Use that definition when reconciling approved eligibility dates to monthly indicators. A month-end membership snapshot alone can omit someone whose coverage ended earlier in the month.

Keep separate controls for unique covered individuals, responsible-individual statements and covered months. A family with three covered people may contribute three person-months in a month while appearing on one statement. Review duplicate enrollment rows across plans and providers under the applicable reporting rules before collapsing them. Shared names or mailing addresses do not establish that two members are the same person.

Choose an internal original-release cutoff early enough for reconciliation, form review and the selected furnishing method. Confirm each feed owner's delivery commitment and escalation contact. Leave the actual government dates in separate fields verified for the reporting year.

Require a final feed completeness attestation or equivalent factual confirmation from the source owner, but record it only when supplied. A scheduled delivery date is not proof a complete file arrived. Define how later retroactive changes are received and assessed for prefiling updates or corrections. Do not discard a valid change merely because it arrived after the internal cutoff, and do not keep rebuilding the original release without version control.

A fictional provider receives a feed with three members. One was covered January through December, one from January 20 through March 4, and one beginning December 31. The dates are assumed to be verified inclusive coverage dates, and the example applies the at-least-one-day monthly rule.

A December month-end list would not establish M12's earlier coverage. Retain full-year effective-dated evidence rather than inferring the annual population from the latest snapshot.

Use an exception queue for missing identifiers, conflicting dates, unexplained duplicate enrollment, unclear responsible-individual grouping and source files that omit expected populations. Each row should identify member key, affected month, source reference, required decision and next responsible person.

Do not let an unknown month become an unchecked coverage box by default. Determine whether no coverage was established or data is simply missing. The two conditions look similar in an output but have different evidence. For missing TIN information, follow the B-series instructions and applicable solicitation rules, including permitted date-of-birth use where appropriate, instead of inventing identifiers or applying a 1099 vendor rule without review.

Bind the approved monthly data, member counts, return counts and unresolved decisions to a specific release version. Confirm the filing provider and statement team use the same approved source. If the provider groups family members differently, reconcile the new return count without losing the covered-person controls.

Keep a late-change register with received date, effective coverage dates, affected released forms and disposition. The B-series instructions require corrections for errors in filed information; the cutoff does not create an exception. Save the original release and later revisions with their actual filing and furnishing outcomes. Reuse the cutoff process next year only after verifying the new source-year dates and changed feed contracts.