Dependent eligibility verification: audit documents vs HR records

A dependent eligibility audit compares the documents submitted for each spouse, child or other person on an employee's health plan (marriage license, birth certificate, tax return page, court order) with the employee's HR record and with the plan's written definition of an eligible dependent. The question is not whether a document looks genuine but whether, read field by field, it supports the relationship, age and status claimed at enrollment. A clean cross-check shows the file is consistent; it does not prove any certificate is authentic.

This article covers US employer-sponsored group health plans. Plan terms, state law and your plan document control; the sources below were checked on October 29, 2026. It is operational guidance, not legal advice.

What does a US dependent audit compare?

A US dependent audit compares three layers: the enrollment record, the supporting document and the HR or payroll file. The audit is usually run by the plan sponsor or a third-party administrator, with the plan document as the rulebook.

Synthesis: the State of Indiana's audit asks for a marriage license plus the front page of the most recent federal tax return for a spouse, a birth certificate showing the employee's name for a biological child, and a court order, adoption decree or Qualified Medical Child Support Order for guardianship, adoption or foster cases; it covers dependents enrolled in the past two years (Indiana State Personnel Department).

What does federal law say about the age limit?

Group health plans that offer dependent child coverage must make it available until the child turns 26, whether or not the child is married, and may not limit eligibility by financial dependency, residency, student status or employment for that cover (US Department of Labor, Young Adults and the Affordable Care Act).

For the reviewer the consequence is practical. A school enrollment certificate for a 24-year-old is not a control on a group health plan, only extra personal data to protect. The documents that matter are the birth certificate (relationship and date of birth) and, for stepchildren, the marriage license. Student or disability evidence matters only for plans that extend other benefits, such as some dental, vision or supplemental plans, whose definitions may differ. Read each plan document separately.

Which cross-checks matter for a spouse?

For a spouse, two comparisons carry most of the risk: the name on the marriage license against the enrollment form, and the license date against any later divorce. The usual failure is stale data. An employee keeps a former spouse on the plan because the divorce was never reported to HR. The license is genuine and matches the record; the person is no longer an eligible spouse.

A license alone cannot catch this. That is why the Indiana audit pairs it with the tax return page showing the spouse, and why plans ask employees to attest that the marriage is in force. The Indiana page also states that common-law marriages and ex-spouses are not eligible under its definition, a definition set by that plan and not a national rule. Reviewers should quote the plan document in every rejection letter.

When a spouse kept a different surname, the comparison should rest on date of birth and the names printed on the license.

What about domestic partners, stepchildren and tax status?

Domestic partners and non-tax-dependent children are defined by the plan, and their coverage can have payroll consequences. Employer-provided coverage for someone who is not the employee's tax dependent may generate imputed income, which payroll must handle (IRS Publication 15-B). The cross-check for HR is therefore a second one: the tax-dependent status recorded in payroll against the dependent type on the enrollment line. A mismatch there is not an eligibility failure but a payroll error to correct.

For stepchildren, three documents must line up: the child's birth certificate (naming the spouse), the marriage license (naming employee and parent) and the tax return page showing both names. If any link in that chain is missing, the line stays open.

What happens after a mismatch?

After a mismatch, the reviewer picks one of three outcomes: accept, request a replacement document, or reject and escalate. Write the decision tree and the deadlines in the audit notice before the campaign opens.

1. Accept: every field matches and the age and status rules are met. Log the document type, date and reviewer.
2. Request: a field is missing or differs for an explainable reason (name change, redacted SSN). Set a deadline and name the document that would settle it.
3. Reject and escalate: the relationship or status cannot be supported. Refer the case to the plan administrator or counsel; HR should not decide contested family situations alone.

Consequences for non-response are set by the sponsor. Indiana's notice warns of disciplinary action up to dismissal; most private plans instead remove unverified dependents. Put the consequence in writing in advance.

What do employees ask on forums?

Employees on benefits and HR forums most often ask why they must resend a marriage license, whether a black-marked tax return is acceptable, and what happens if the audit deadline is missed.

• "Can I black out my income on the tax return?" The Indiana audit allows financial information to be blacked out while leaving Social Security numbers visible. Check your own plan's instructions.
• "My child has a different last name." Not a mismatch if the birth certificate names you as a parent. If it names only your spouse, the file follows the stepchild route.
• "Will my partner be covered?" It depends entirely on the plan's definition of a dependent.

How should dependent files be handled?

Dependent files hold Social Security numbers, tax data and sometimes health-related information. Group health plans are covered entities under HIPAA, and the HHS privacy rules apply to health information the plan holds (HHS, HIPAA). Collect only what the plan document requires, redact what is not compared, store the audit result rather than copies where permitted, and set a retention date.

Where does automation help?

Automation helps with the repetitive part: reading the same fields on every certificate and comparing them with the HR record. A document validation tool such as the one on the HR solution page checks completeness, dates and cross-document consistency, and flags the lines a person must decide on. It does not decide eligibility and does not establish that a document is authentic. See security for data handling.

Related reading: validating employee bank details and tax ID before the first payroll and HR document verification. Sector context: the industry verification guide.

FAQ

What is dependent eligibility verification?

It is the check that each person enrolled as a dependent meets the plan's definition, by comparing supporting documents with the enrollment form and HR record. It covers relationship, age and status.

Which documents do audits usually require?

Spouse: marriage license and the front page of a recent federal tax return. Child: birth certificate showing the employee's name, plus adoption, guardianship or court documents where relevant.

How far back does an audit look?

The sponsor decides. Indiana's audit covers dependents covered in the past two years; others verify only at enrollment and at qualifying life events.

Does a matching certificate prove eligibility?

No. It shows the document is consistent with the record. Eligibility also depends on current status and the plan's terms.

What if an employee does not respond?

The sponsor's notice controls the outcome, from removal of the dependent to disciplinary action. State it in the audit communication before the campaign starts.