1099-HC Subscriber Data Checklist for Coverage Providers

Begin at DOR’s current bulk-file instruction index and save the handbook, schema and sample references used by the team. Record the download date and version. A recently updated index does not mean every linked technical document was newly revised.

Keep a mapping sheet with source field, target element, transformation, validation and responsible system. Resolve unclear requirements before export. A spreadsheet column titled “member ID” may contain a different value from the subscriber identifier required by the state.

Separate the recipient statement layout from the XML field structure. The same business facts must agree across both outputs, but a printed box and an XML element need not have the same display label or formatting.

Keep transformations reversible in the working records. If a name is normalized or an identifier is combined with a policy reference, retain the original source value and the rule applied so a later subscriber inquiry can be traced without guessing.

Confirm the reporting insurance company or administrator identity against the source record approved for 1099-HC. The DOR carrier guidance says the company name and FID supplied to the state must match what the subscriber receives; that FID is not necessarily the identifier used for other tax reporting.

The handbook field table documents CompanyName and CompanyID, subscriber name components, address, birth date and SubscriberNumber. Preserve leading characters and meaningful formatting through the source-to-output transformation, applying the current schema constraints.

Do not replace a missing subscriber number with an SSN merely because the source has one. Establish the intended state identifier and a stable mapping. Keep sensitive source data out of review exports that only need masked internal references.

The handbook documents Status values S for subscriber and D for dependent, and ParentSubscriberNumber for the dependent relationship. Confirm that the parent reference points to the intended subscriber within the reporting company’s records.

The documented SubscriberNumber length is six to twenty characters and it should be unique within CompanyID. If the source requires a composite identifier, define the rule consistently and verify it against the current schema. Do not invent a different identifier on every export.

Check duplicate identifiers, orphan dependents and households split between source systems. A dependent’s demographic record can be valid while its relationship is wrong. Include cases where a dependent later becomes the primary subscriber so the year-specific relationship is not overwritten by today’s account status.

Fictional example: A provider prepares three synthetic subscriber records. All names and dates parse, but one dependent points to a parent identifier absent from the reviewed company dataset.

The team traces DEP002 to an older enrollment feed and corrects the mapping from verified source records. It does not change the dependent to Status S just to make a local check pass. The final manifest records which source version supplied the repaired relationship.

Preserve effective and through dates for each coverage span, including reinstatements and midyear changes. The handbook documents CoverageEffectiveDate and CoverageThroughDate in YYYY-MM-DD form, with the through date bounded by the end of the reporting year.

Apply the state MCC month rules when preparing subscriber statements: at least 15 days of MCC coverage produces a covered month. Do not transform all active federal coverage into state MCC automatically. Retain the plan classification and any required sponsor evidence.

Review end-before-start spans, unexplained gaps and duplicate intervals. A syntactically valid date pair can still describe the wrong person or plan. Compare a sample of rendered statements with the underlying spans and documented business rules.

Compare the final state dataset with the recipient statement dataset by company, subscriber, covered people and coverage facts. Explain missing or additional records before release. A matching total count does not prove the same subscribers were included.

The handbook includes CorrectedFlag and DeletedFlag. Use those only through the documented correction process and current specifications; they are not generic cleanup switches for uncertain data. Preserve the original and changed facts in an internal comparison.

Keep the source snapshot, mapping version, validation results and authorized release record. DOR’s bulk-filing guidance explains that file exceptions arrive through MassTaxConnect e-messages. Assign responsibility for reviewing those results after submission; successful local preparation is only the preflight stage.