Smart Auto-Mapping Engine
AI predicts and aligns field mappings across carriers and HR systems, with a confidence score and the reasoning — guide passage, sample values, past templates — behind every proposal.
Smarter Mapping. Seamless Integrations. Powered by AI.
Every HR ecosystem has one challenge — connecting carriers, payroll, and benefits data without drowning in spreadsheets or file formats.
BR IntelliMap solves it with AI-powered mapping that reads, learns, and builds integrations automatically. Upload the companion guide and a sample 834; IntelliMap proposes every field, explains each choice, validates it on your real records, and saves a versioned template. You confirm the exceptions. The timeline moves from weeks to days.
EDI 834 · XML · CSV · APICompanion-guide parsingAI proposes · you confirmVersioned · rollback
The Intelligence Layer Behind Every Benefits Integration
"HR and benefits administrators know that data integration is often the hardest part of benefits management. Every new carrier, plan, or payroll update introduces new mapping logic, inconsistent formats, and complex companion guides. BR IntelliMap — the AI-powered benefits data mapping engine within BR Intelligence — brings structure, automation, and intelligence to this process: it reads the guide the way an integrator would, proposes the mapping the way a veteran would, and keeps the decision with a person."
Parsing & PreparationGuide + sample file → schema in secondsSmart Auto-MappingEvery field proposed, scored, explainedValidation & Error ResolutionReal records, exact failuresContinuous LearningYour decisions train the next feedDeployment & GovernanceVersioned templates, build vs production
80%reduction in mapping setup time — the live estimate for a new carrier feed against spreadsheet mapping
1%confidence score on every proposed field, with the guide passage, sample values and past templates that justify it
0%fields written to production without a person confirming — AI recommends, integrators approve and promote
2%environments — build and production — with full version history and one-click rollback on every template
One Carrier Feed, Five Stages
Follow a new dental carrier from companion guide to a production feed. Each stage removes a spreadsheet — and none removes the integrator's signature.
Upload. Parse. Understand — in seconds.
The integrator drops in the carrier's companion guide — a 60-page PDF — and a sample 834. Using advanced AI and NLP, IntelliMap reads complex structures like 834s, CSVs, or XMLs, extracts the loops, segments and qualifiers the guide describes, notes the carrier-specific rules buried in the footnotes, and produces a schema: every field the carrier expects, its position, its format and its allowed values.
What it reads
- Instantly parses unstructured files — PDFs, text, Excel — with OCR for scanned guides
- Supports EDI 834, XML, CSV, API payloads and custom vendor formats
- Carrier invoices too — the same parser feeds Carrier Billing
- Creates reusable templates for recurring data sources
Why it matters
Nobody retypes a companion guide into a spreadsheet again.
The guide's own page numbers stay attached to every field for the review that follows.
Intelligent field matching — minus the guesswork.
IntelliMap's Smart Auto-Mapping Engine uses LLM-powered pattern recognition to recommend field alignments automatically. For each carrier field it proposes the target in the Benefits Reimagined data model, the transformation (date formats, code tables, contribution math), and a confidence score — and it shows its reasoning: the guide passage, the sample values, and the earlier templates the choice resembles. High-confidence fields are pre-accepted; mid-range ones are suggested; the handful below threshold wait for the integrator.
What the engine does
- Reduces mapping setup time by 80% — the live estimate against manual mapping
- Handles multiple file types in one session — the 834, the plan sheet, the API spec
- Identifies conflicts and recommends corrections: two carrier codes to one plan, one field to two targets
- Applies formula-based transformation logic for date, code and contribution data
Why it matters
The integrator reviews 2 fields, not 142.
Every accept, edit or reject is stored with the proposal — the reason it was wrong is as valuable as the fix.
Automated checks that protect your data.
Once mappings are built, IntelliMap runs auto-validation to check field types, dependencies, and transformation logic against real records in the build environment. Try/catch logic detects data mismatches as they happen; the visual debugging interface shows exactly which record, which field and which rule failed — and proposes the correction with the highest historical success rate. Nothing reaches production until the run is clean or every exception has an owner.
What is checked
- Try/Catch logic detects real-time data mismatches — type, length, allowed values, required-when
- Visual debugging interface shows exactly where to fix, record by record
- Auto-corrects based on historical success rates — with the correction shown before it is applied
- Round-trip test: outbound file re-parsed and compared to the census it came from
Why it matters
Errors are found on 312 test members, not 4,812 live ones.
The same checks run on every production file afterwards, feeding 4-Way Reconciliation.
An integration engine that evolves with you
IntelliMap continuously improves through feedback loops. Every accept, edit and reject — and every production exception — is stored against the proposal that caused it. The next time a similar field appears, from the same carrier or a different one, the engine's confidence reflects what your team actually decided. When a carrier publishes a new companion guide, IntelliMap diffs it against the version the template was built from and proposes changes for only the fields that moved.
How it learns
- Self-learning improves accuracy over time — from your decisions, inside your tenant
- Adaptive logic adjusts for new vendors and plans without starting from zero
- Guide-to-guide diff: only changed fields come back for review at renewal
- Keeps human oversight at the center of automation — confidence rises, the signature stays
Why it matters
The second carrier is faster than the first; the renewal is faster than both.
Learning is per tenant. Your mapping decisions never train another customer's engine.
Secure, versioned, and enterprise-ready
Once finalized, integrations are deployed across secure, version-controlled environments. A template is promoted from build to production by a named integrator; every version keeps its guide, its proposals, its decisions and its validation run, so an auditor — or the integrator's successor — can see why field 88 maps the way it does. Rollback restores any earlier version in one step. The feed then runs on the Integration Control Plane with the same monitoring as your HRIS sync.
What governance looks like
- Separate environments for build and production; promotion by role
- Complete version history with rollback capability — and the reasoning behind each version
- Reusable integration blocks — modular workflows shared across file types and carriers
- HIPAA-aligned architecture; encryption; role-based access
Why it matters
A mapping is an auditable artifact, not tribal knowledge.
Runs, files, hashes and exceptions are kept with the version — the 4-Way Reconciliation evidence starts here.
Core Capabilities That Set BR IntelliMap Apart
Parsing, matching, transforming, reusing, validating and governing — built for benefits data, not generic ETL.
834 File + Companion Guide Parsing
Reads complex EDI and flat-file formats and the PDF, Excel or text guides that describe them, extracting the schema — loops, segments, qualifiers, footnote rules — instantly.
Transformation Logic
Applies formula-based conversions for date, code, or contribution data: format changes, code tables, many-to-one plan rules, per-pay-period math — all versioned with the template.
Reusable Integration Blocks
Modular workflows that can be reused across file types and carriers — a name block, a date block, a tier block — so the second feed starts from the first one's decisions.
Real-Time Validation & Debugging
Detects errors, mismatches, and dependencies automatically on real records, names the record and the rule for every exception, and proposes the fix with the best historical success rate.
Secure, Platform-Native Infrastructure
Runs inside the platform with encryption in transit and at rest, role-based access, separate build and production environments, and full version history.
Spreadsheet Mapping vs. IntelliMap
Most carrier connections are still built the way they were in 2010: a guide, a spreadsheet, an integrator, and a month. Here is what changes.
| Step | Spreadsheet mapping | BR IntelliMap |
|---|---|---|
| Reading the companion guide | An integrator reads 60 pages and retypes fields into a sheet. | Parsed in seconds — loops, segments, qualifiers and footnote rules, each with its page number. |
| Aligning fields | One by one, from memory and the last carrier's sheet. | Every field proposed with a confidence score and its reasoning; the integrator reviews the exceptions. |
| Transformations | Formulas in a workbook nobody else can read. | Versioned rules — code tables, date formats, contribution math — stored with the template. |
| Testing | Send a file, wait for the carrier's rejection report. | Validate on real records first; each exception names the record and the rule; round-trip check before anything is sent. |
| Renewal | Start again with the new guide. | Diff the guides; only the changed fields come back for review. |
| Knowledge | Leaves with the integrator. | Stays in the version history — who decided what, and why, for every field. |
| Timeline | Weeks per feed. | Days — and faster for every feed after the first. |
Athena inside IntelliMap
Ask the Mapping Why It Is the Way It Is
Integrators and auditors ask the same questions in different words: why does this field map there, what changed since last year, which file caused the reject. Athena on the admin side answers from the template's own history — proposals, decisions, validation runs, production files — and can prepare the next action for a person to approve.
- "Why does REF*1L map to two plans?" — the footnote, the decision, the person and the date
- "What changed between v3 and v4?" — a field-level diff in plain language
- "Which members were rejected last Thursday and why?" — records, rules, and the HRIS data-quality tasks opened
- "Draft the Vision template from Dental" — reusable blocks applied, differences flagged, nothing promoted
- "Export the mapping evidence for the auditor" — guide, proposals, decisions, runs and hashes in one package
Why does sub-group 003 map to plan D200 and not its own plan?
Athena · from the template historyBecause the 2027 companion guide, footnote 12 on page 35, states that sub-groups 002 and 003 share plan D200 while 004 is a separate plan. IntelliMap proposed the many-to-one rule at 0.41 confidence on 12/16/2026; S. Mitra confirmed it on 12/18 with the note "matches carrier account structure". The rule has run on 38 production files with zero rejects on that field.
Open the decisionShow 2028 guide diff
Draft the 2028 version but don't promote anything.
AthenaDone — DD-834-2028 v1 is in the build environment, based on 2027 v4. 137 fields carried over unchanged, 5 changed fields are queued for R. Patel's review, and validation is scheduled against the September census. Nothing has been promoted.
Open buildNotify R. Patel
Ask about this template…
Why HR and Benefits Teams Choose BR IntelliMap
Built for Benefits
Designed for HR ecosystems, not generic ETL. It understands benefits data natively — tiers, qualifying events, effective dating, sub-groups, per-pay-period contributions.
AI + Human Collaboration
AI recommends; humans approve — ensuring accuracy and control. Every proposal shows its reasoning, and every decision is recorded with a name.
Continuous Learning
Improves automatically with every mapping and update — inside your tenant, from your team's decisions, so the fourth carrier is easier than the first.
Speed and Scalability
Handles multiple carriers and vendors simultaneously, in one session — and greatly reduces the integration timeline for every new connection.
End-to-End Security
Fully encrypted and HIPAA-aligned — with test data in build, PHI only in production, and role-based promotion between the two.
Seamless Integration
Works across SAP SuccessFactors, Workday, UKG, Ceridian Dayforce, ADP, Paycom and major carrier systems — by 834, flat file, XML or API — on the same Integration Control Plane as your HRIS sync.
Where IntelliMap Fits in the Platform
IntelliMap is the front end of every connection Benefits Reimagined makes. Templates it produces run on the Integration Control Plane beside SuccessFactors Sync and every other HRIS feed; the files those templates produce are what Carrier Billing matches invoices against and what 4-Way Reconciliation proves. The same parser that reads a companion guide reads a carrier invoice, and the same validation that protects a build protects every production run.
- HRIS Sync — inbound employee and event data from SuccessFactors, Workday, UKG, ADP, Dayforce or Paycom, mapped once and monitored
- Carrier feeds — outbound 834, flat file, XML or API per carrier, with acknowledgments and rejects tracked per member
- Carrier Billing — invoice extraction uses the same parser; line items land beside the census they should match
- 4-Way Reconciliation — file hashes, run logs and exceptions from every feed are the evidence the four-source match starts from
- Payroll — deduction files mapped with the same templates and contribution math, so ReVerge retro calculations and payroll agree
Simplify Integrations. Amplify Efficiency.
The complexity of benefits integrations shouldn't slow your organization down. Bring your hardest companion guide and a de-identified sample file; we'll parse it, propose the mapping and validate it in front of you — then show you the version history an auditor would see.
Build / production separationVersion history + rollbackTest data only in buildHIPAA-alignedAI proposes · you confirm
BR IntelliMap FAQs
It's an AI-powered benefits data mapping engine that automates integrations between carriers, payroll systems, and HR platforms. It reads the carrier's companion guide and a sample file, proposes how every field lines up with the Benefits Reimagined data model, validates the result against real records, and saves the mapping as a versioned template you can reuse for the next feed or the next plan year.
834 EDI files, companion guides (PDF, Excel, text), XML, CSV, and custom vendor layouts — plus API payloads for carriers and HRIS platforms that exchange data without files. Unstructured inputs such as scanned guides are parsed with OCR and NLP before matching.
Through visual debugging, real-time validation, and rollback support. Every proposed field carries a confidence score; anything below your threshold is queued for a person. Validation runs try/catch logic on real records and shows exactly which record and which rule failed. A promoted template can be rolled back to any earlier version.
No — AI recommends; humans approve. IntelliMap proposes the alignment and the transformation, explains why (the guide passage, the sample values, the past mappings it resembles), and a benefits integrator confirms, edits or rejects each one. Those decisions train the next proposal.
The live estimate is an 80% reduction in mapping setup time. In practice a new carrier feed that took weeks of spreadsheet work becomes days: hours to parse and propose, a working session to confirm the exceptions, a validation pass on real data, then promotion. The bigger saving comes next year, when the template is reused.
Yes. It is HIPAA-aligned with encrypted data workflows, role-based access, separate build and production environments, and a complete version history of every template and every promotion.
It connects with SAP SuccessFactors, Workday, UKG, Ceridian Dayforce, ADP, Paycom and major carrier systems — by 834, flat file, XML or API. On the HRIS side it feeds the same Integration Control Plane that runs SuccessFactors Sync; on the carrier side it feeds enrollment, Carrier Billing and 4-Way Reconciliation.
You upload the new guide. IntelliMap diffs it against the version the template was built from, highlights the fields that changed, proposes the updated mapping for only those fields, and re-validates. The old template stays available for rollback and for reconciling files that still arrive in the old layout.
Mapping as a Strategic Advantage
With BR IntelliMap, mapping becomes faster, smarter, and more secure — a versioned asset your team owns, not a month your project loses.