AI-Powered Document Extraction
BR IntelliVerify classifies each file and extracts names, dates, relationships, issuer, and document dates — cross-matching between documents in a composite set.
Benefits Administration · Dependent Eligibility Audit
Dependent Eligibility Audit & Verification — Automated with AI + OCR
Only the right dependents stay covered — automatically.
Cut unnecessary premium spend, reduce audit workload, and keep documentation airtight with an AI-powered dependent eligibility audit built for real-world HR operations. Benefits Reimagined collects proof, reads it with BR IntelliVerify, validates it against your plan rules and document catalogue, and routes only the exceptions to a person — while employees see a plain list of what is needed, what is done, and what happens next.
AI + OCR extractionExceptions only to HREvidence reused until it expiresAudit-ready trail
Why Dependent Eligibility Audits Save Real Money
"Managing dependent eligibility can quietly drive up benefits costs when ineligible dependents remain enrolled. Benefits Reimagined uses AI and OCR to automate audits, securely extracting key information from documents and validating eligibility against plan rules. By flagging only exceptions for human review, the platform eliminates manual effort, reduces premium leakage, and ensures compliance without disrupting employees. Automated dashboards provide real-time visibility into audit progress, verification rates, and projected savings."
Automated ReviewCollect, extract, validate by ruleAI ExtractionClassify, read, cross-matchException RoutingHigh-risk cases to HR, with contextCompliance DashboardProgress, rates, savings in real timeSecure Employee WorkflowPrompted only when necessary
1upload per relationship — verified evidence lives in the Document Center with a validity period and is reused across enrollment, life events, and audits
6document types in the catalogue out of the box — marriage certificate, birth certificate, court or adoption order, domestic partnership affidavit, proof of prior coverage, itemized receipt/EOB — each with issuer, fields, acceptance rules, and validity
3distinct outcomes, never confused — wrong document type, unreadable (review), or failed an acceptance rule (not accepted) — each with its own next step
0employees asked to pick a document type — BR classifies the file and tells them if it is the wrong one
From Proof Request to Defensible Decision
Follow one audit campaign through collection, AI extraction, exception routing, real-time tracking, and the employee experience — five controls that verify dependents without turning HR into a document desk.
Streamline dependent eligibility verification automatically
The system collects required proof, extracts key information using OCR, and validates eligibility against plan rules. Requirements are generated per dependent from the relationship and the plan — a spouse needs a marriage certificate, a stepchild needs a composite set, a domestic partner needs an affidavit — and each requirement declares which document types it accepts and whether one is enough. Only exceptions are flagged for human review.
What it delivers
- Accurate extraction — names, dates of birth, relationships, issuer, and document dates read by BR IntelliVerify
- Reduced HR workload — verified relationships close themselves; evidence on file is reused, not re-requested
- Faster cycles — decisions in minutes for clear documents, with reminders armed for missing ones
- Composite sets and cross-matches — a previous surname on a birth certificate resolved against the marriage certificate
Why it matters
Consistent compliance and cost control across every location and plan.
A dependent verified during a life event in June is not asked again in the October audit — the evidence is valid and on file.
Identify critical eligibility data efficiently
AI analyzes submitted documents, classifies document types, and pulls essential fields like names and dates of birth for verification. Classification comes first — BR decides what the file is, so a hospital record submitted as a birth certificate is a distinct outcome ("wrong document type") from an unreadable file ("please retake") or a document that fails an acceptance rule ("informational copy not accepted"). Extraction fields are engine capabilities; acceptance rules are yours.
What it delivers
- Automated anomaly identification — mismatched names, implausible dates, altered fields, duplicate submissions
- Immediate validation of extracted fields against the employee and dependent record
- Reduced errors — no manual transcription of names and dates into the system
- Three explicit outcomes with three different next steps for the employee
Why it matters
Improves accuracy and accelerates decisions while keeping the employee's next step obvious.
The catalogue is administrator-maintained: certified-copy requirement, legibility threshold, document age limit, accepted issuers, and validity per type.
Direct only high-risk cases to HR teams
Dependents that fail automated checks are routed to HR with full context, evidence, and workflow support — as a BR Resolve case carrying the requirement, the documents, the extraction, the rule that could not decide, and the employee's history. The employee sees only "Under review — no further action is required from you right now." Cases run on the Workflow Control Tower with SLAs, delegation cover, and outcomes that feed back into the dependent record and the audit trail.
What it delivers
- Targeted human review — the 1–2% the rules cannot decide, not the 100%
- Clear audit trail — who reviewed, what they saw, what they decided, and why
- Employee-friendly communication — one calm status while a person looks, then a plain outcome
- Removals handled by rule: coverage end date, notice, COBRA event where applicable, payroll and carrier updates
Why it matters
Minimizes disruption while maintaining compliance.
A removal is never a surprise: the notice, the effective date, and the appeal route are generated with the decision.
Track audit progress in real time
Dashboards provide visibility into verification rates, pending cases, and potential cost savings, enabling proactive management. Every campaign shows its funnel — in scope, prompted, submitted, verified, exception, removed — by location, plan, and relationship type, with projected premium impact calculated from the plan's actual dependent rates. Figures are as-of a date and traceable to the dependents behind them.
What it delivers
- Audit status insight — funnel by population, day by day, with reminders and escalations visible
- Performance tracking — time to decision, exception rate, reuse rate, retake rate
- Premium impact forecasting — projected and realized savings from removals, by plan and tier
- Compliance evidence — every decision with its catalogue version, exportable for auditors or carriers
Why it matters
Supports informed HR and benefits decisions and makes the audit's value visible.
Verified dependents are not re-audited; the dashboard shows reuse as a saving in employee effort, too.
Simplify document submission for employees
Employees are prompted only when necessary, and submissions are secured, validated, and logged. The experience is a Requirements Center, not a document pile: each dependent shows what is needed, why ("Why am I being asked this?" answered by Athena), what is already satisfied, and what happens next. Uploads come from the BR mobile app or portal; alternatives — by phone, on paper, or with someone helping — pause the deadline clock. Verified evidence is kept for its validity period so the same relationship is never proven twice.
What it delivers
- Reduced frustration — one list, plain statuses, one calm "under review" while a person looks
- Secure handling — encrypted upload, minimum-necessary data, retention on the notice type's class
- Simplified experience — BR classifies the document; the employee never chooses a type
- Multilingual and accessible — English, Spanish, and more, WCAG-conformant, Section 508 ready
Why it matters
Enhances engagement while ensuring data integrity.
A dependent already verified during a life event shows "Marriage certificate — not required" so employees see BR decided no document was needed.
Core Capabilities of Dependent Eligibility Audit
Extraction, verification, exception handling, workflow, dashboards, and rule enforcement — configured by administrators through the document catalogue and plan rules, not per-screen code.
OCR Verification
Legibility thresholds, certified-copy detection, issuer acceptance, and document-age limits applied per document type from the administrator-maintained catalogue.
Exception Management
Only cases the rules cannot decide reach HR — as BR Resolve cases with the evidence, the extraction, and the employee's history attached, and Athena's proposed next step.
Automated Workflows
Requirements generated per dependent, reminders that re-check before sending, deadline pauses for alternative completion, removals with notices, COBRA events, and retro premiums through ReVerge.
Real-Time HR Dashboards
Campaign funnels by location, plan, and relationship; time to decision, exception and reuse rates; projected and realized savings from each plan's real rates.
Policy-Based Rule Enforcement
Eligibility ages, student and disability provisions, domestic partner criteria, and evidence validity as effective-dated plan rules with an approval step — never hard-coded.
Athena inside Dependent Audit
"Why Am I Being Asked This?" Answered in Plain Language
Athena explains each requirement to the employee from their own dependents and plan — which document, why it is needed, and what counts — and, when a file comes back as the wrong type or not accepted, what to send instead. For HR, Athena triages exceptions with a proposed resolution, watches the campaign funnel, and assembles the evidence an auditor or carrier asks for.
- "Which document do I need?" — the accepted types for this relationship under this plan, and whether a copy on file already covers it
- "Why was mine not accepted?" — the specific rule — informational copy, expired statement, missing second proof — and the fix
- Exception proposals — name-change cross-matches, credential checks, and composite-set gaps resolved to a suggested action a person approves
- Campaign watch — locations falling behind, reminder effectiveness, and populations where a phone-based alternative would help
- Evidence on request — "show every removal this campaign with its documents and notices" returns the export
Why do I have to prove Rohan is a student? My colleague didn't.
AthenaYour colleague's children are on Plan A, which covers children to age 26 with no student requirement. Rohan is on the legacy Plan B, which requires proof of full-time enrollment for dependents aged 23 to 26 until that plan closes at the end of 2027. A current enrollment letter or a class schedule with the school's name and term works — a student ID card doesn't show the term, so it wouldn't be accepted.
Arjun · spouseNot required · verified 2026
Maya · childVerified · on file
Rohan · child, 24Enrollment letter needed by 10/02
Upload from my phoneI need more timeHave someone help me
I can't get the letter until the term starts next week.
AthenaThat's fine. I've paused your deadline — it won't count against you while you're waiting — and I'll remind you on 09/29. Rohan stays covered in the meantime.
Ask Athena about a requirement…
What Dependent Eligibility Audits Change
Reduced premium leakage
Ineligible dependents come off the plan with the right date, notice, and retro premium — and savings you can defend.
Streamlined HR effort
Automation closes the clear cases; HR sees the one or two percent the rules cannot decide.
Improved compliance
Every decision keeps its documents, its rule, and its catalogue version for auditors and carriers.
Faster audit completion
Minutes for a clear document, days for a campaign — with reminders and pauses handled by workflow.
Employee-friendly process
One list, plain statuses, alternatives that pause the clock, and no document uploaded twice.
Accurate eligibility data
Dependent records carry verification state and validity, feeding enrollment, billing, and analytics.
Governance at Scale
Benefits Reimagined standardizes dependent eligibility audits across teams and locations, ensuring consistent enforcement of plan rules. Automation reduces operational risk while providing clear audit trails and reporting, allowing organizations to scale their benefits governance efficiently — on the same platform, on SAP BTP and AWS, as enrollment itself.
- Admin: document catalogue — document types with issuer, extraction fields, acceptance rules, and validity — effective-dated, approved by someone other than the author, superseded versions retained
- Admin: campaign console — scope by plan, population, or relationship; run annually, before OE, or continuously for new dependents; funnel, reminders, and escalations in one view
- Admin: exception queue — BR Resolve cases with evidence attached, Athena proposals, delegation cover, and outcomes written back to the dependent record
- Employee: Requirements Center — per-dependent requirements, plain statuses, "Why am I being asked this?", uploads from the BR mobile app, and alternatives that pause the deadline
- Analytics: audit intelligence — verification, reuse, exception, and retake rates; projected and realized savings by plan; evidence health across the population
Stop paying for dependents who shouldn't be covered
Bring a dependent census and a handful of real documents. We'll run them through IntelliVerify, show which would close without a person, which would route and why, and the savings view built from your plan's own rates.
AI + OCR extractionCatalogue-governed rulesEvidence retained by class
Dependent Eligibility Audit FAQs
A dependent eligibility audit verifies that enrolled dependents meet plan rules and have valid proof on file. This process ensures only eligible dependents receive coverage, reducing unnecessary costs and compliance risk.
Most organizations run audits annually, before open enrollment, or continuously for new dependents. Timely verification prevents premium leakage and keeps eligibility data accurate across payroll and benefits systems. Benefits Reimagined supports all three modes from the same campaign console.
AI analyzes submitted documents, classifies types, and extracts critical information like names, dates, and relationships. This reduces manual effort and improves the accuracy of eligibility decisions — and because classification comes first, a wrong document type, an unreadable file, and a document that fails an acceptance rule are three different outcomes with three different next steps.
Only when changes occur or documents are missing or invalid. Verified dependents are not re-audited: evidence lives in the Document Center with a validity period and is reused across enrollment, life events, and audits, minimizing employee disruption.
Cases are routed to HR for review, with secure records and timestamps. Employees can respond to requests, and outcomes are logged for audit readiness and compliance. Confirmed removals get the right coverage end date, a notice with an appeal route, a COBRA qualifying event where applicable, and retro premium handling through BR ReVerge.
Administrators do, through the document catalogue and plan rules: accepted document types per relationship, certified-copy requirements, legibility thresholds, document age limits, accepted issuers, and evidence validity. Changes are effective-dated and approved by someone other than the author, and every past decision keeps the version it was judged under.
Yes. The platform is designed to scale across complex, regulated organizations — many locations, plans, and legal entities, multi-entity populations, multilingual and accessible employee experiences, and audit trails that satisfy carriers, auditors, and Section 508 obligations.
Only the Right Dependents Stay Covered — Automatically
AI extraction, catalogue-governed rules, exceptions only to HR, evidence reused until it expires, and savings you can defend — an audit that runs itself and respects your employees.