Handle Concurrent Employment, Global Assignments and Multi-Entity Workforces
A nurse with two employments, an engineer on assignment abroad, an acquired entity on another HRIS, a co-employed PEO population — Benefits Reimagined keeps one benefits record per person and computes eligibility, elections, deductions and compliance across every employment and entity.
The employees who break benefits systems are the ones with more than one row: concurrent employments in the same organization, assignments across a border, entities that came with an acquisition, populations a PEO co-employs. Benefits Reimagined is built on a central person concept: the person is modelled once and the employments many times, so eligibility rules aggregate hours, elections are made once, deductions split correctly across payrolls, and the ACA counts the person — whether the employments live in SAP SuccessFactors or in two different HRIS platforms.
More Than One Row per Person
“She works 24 hours at the hospital and 16 at the clinic — two employee numbers, two eligibility checks that both say part-time, two deductions if she enrolls in both, and one ACA problem when the hours are added up.” Every organization with concurrent employment, expatriates, acquisitions or a PEO has this person, and most benefits tools cannot see her as one.
Eligibility that misses the person
Hours evaluated per employment, so someone who is full-time across two jobs is part-time in both — until the IRS adds them up.
Assignments handled by exception
An employee on assignment abroad keeps a plan they cannot use, misses the host-country offer, and reads content in the wrong language and currency.
Acquisitions on a different HRIS
The acquired plant is on Workday; its people are on a spreadsheet for benefits, a second vendor for ACA, and a manual file to the carrier.
One Person, Four Rules
Follow three people — a concurrent employee, an assignee and an acquired-entity employee — through the rules that govern them, and see the same rulebook serve every entity, PEO population and source.
Model the person once, the employments many times
Employee Management holds one person with as many employments, entities and assignments as the HR record carries — from SuccessFactors as it happens, from any other HRIS through HRIS Sync. Eligibility rules choose whether to aggregate hours across employments, which employment is primary for a benefit, and how a change in one employment affects the others. The Employee 360 shows every employment, ticket and case on one screen.
Govern assignments across the border
A global assignment carries home and host entities with dates. Rules decide which plans are held, which are offered in the host country, and when each starts and ends; coverage dates are derived from the assignment. The platform is multi-language and multi-currency, so the employee sees the right content in the right language with costs in the right currency — and Athena answers in that language.
Bring the acquired entity — or the PEO population — onto the same rulebook
An entity on Workday, UKG, ADP, Dayforce, Paycom or any HRIS joins through the HRIS Sync control plane: IntelliMap proposes the field mapping, a person approves it, the sync writes to the same person and employment model, and the entity’s plans, rates and rules are configured as effective-dated content — with its own payroll lane, whichever of ADP · Workday · UKG · Dayforce · Paycom · SAP ECP it runs. A PEO’s co-employed population is configured the same way, on its own rules and carrier lanes, inside the same tenant.
Count the person for compliance and billing
The ACA engine measures hours across a person’s employments and reports under the correct ALE member; controlled-group reporting produces one authoritative 1094-C. Carrier billing matches one election to one invoice line, so a concurrent employee is never billed twice; BR ReVerge corrects deductions on the right employment and the right payroll; Essential Insights reports by entity, country and employment type.
What You'll Use for Complex Workforces
The modules below are the same ones every employer uses — the difference is the person model underneath them.
Employee Management
One person, many employments, entities and assignments — the Employee 360 every other module reads.
Explore Employee ManagementBusiness Rules
Aggregation, primary-employment, assignment and entity rules as effective-dated configuration — if, otherwise if, otherwise.
Explore Business RulesSuccessFactors & HRIS Sync
Every entity’s HRIS and payroll on one control plane, writing to the same person model.
Explore SuccessFactors & HRIS SyncBR IntelliMap
Field mapping for a new entity’s HRIS or payroll proposed by AI, approved by a person.
Explore BR IntelliMapACA Compliance & 1095-C
Hours aggregated per person, controlled-group reporting, one authoritative 1094-C.
Explore ACA Compliance & 1095-CEssential Insights
Enrollment, cost and compliance by entity, country and employment type.
Explore Essential InsightsOne Row per System vs. One Person on the Record
Six moments for the employees with more than one row, and what changes when the person is modelled once.
| Moment | The way it usually goes | Benefits Reimagined |
|---|---|---|
| Two employments, one person | Two employee numbers; part-time in both. | One record; hours aggregate by rule; full-time across them. |
| Enrolling | Two elections, two deductions. | One election; the deduction from the primary employment, on that employment’s payroll. |
| An assignment abroad | Handled by exception; wrong plan, wrong language. | Home plans held, host plans offered, dates derived; language and currency follow the person. |
| An acquisition on another HRIS | A spreadsheet and a second vendor. | Mapped by IntelliMap onto the same record, rulebook, OE window and carrier lanes. |
| A PEO population | A separate program somebody else runs. | Its own rules and lanes inside the same tenant, on the same person model. |
| The ACA | Two 1095-Cs, or none. | Counted once, reported under the right ALE member, one 1094-C for the group. |
What Changes When the Person Is Modelled Once
One benefits record
Employments are rows under a person; eligibility, elections and deductions are computed for the person.
Full-time across them
Hours aggregate by rule for eligibility and for the ACA — the way the IRS will count them.
Assignments by rule
Home plans held, host plans offered, dates derived; language and currency follow the person.
An entity on the control plane
Mapped by IntelliMap, governed by the same rulebook, included in the same OE, ACA group and billing.
One election, one line
A concurrent employee elects once; the deduction takes from the primary employment’s payroll; the invoice matches one line.
Insights per entity, country and type
Enrollment, cost and compliance where the organization actually is, not where the HRIS boundaries are.
Ask How One Person Is Being Governed
Athena reads the person model. Employees with two employments or an assignment ask about their own coverage and get one answer; administrators ask Athena for Admins which rule applied, why hours aggregated, or which entity a person reports under — and get the rule, the version and the record.
- “Why is Jane full-time for benefits when both jobs are part-time?” — the aggregation rule, the hours from each employment and the primary-employment decision
- “What happens to my plans when I go on assignment?” — the assignment rule for that employee: what is held, what is offered, in their language
- “Which Harbor Foods employees are still held?” — the records, the reason, and the Workday owner to fix at source
- “Who reports under ALE member 3 this year?” — the employees, the company codes and the map that put them there
Who Usually Starts Here
Complex populations are an HR design problem, a Finance accuracy problem and an IT integration problem. Each role has its own page.
HR & Benefits Leaders
Aggregation, assignment and entity rules as configuration — with Athena to explain any person’s outcome.
See the role page Owns the sourcesIT & SAP Teams
Every entity’s HRIS and payroll on one control plane; SuccessFactors native, the rest mapped by IntelliMap.
See the role page Owns the accuracyFinance & Payroll
One election, one deduction, one invoice line per person — and one 1094-C per controlled group.
See the role pageBring Your Hardest Population and We’ll Model It
Your concurrent employees, your assignees, your most recent acquisition or your PEO population. In the 45-minute walkthrough we will model three real cases in a sample tenant, show the rule behind each outcome, and run the ACA measurement across them.
Handle Concurrent & Global Employees FAQs
One Person. However Many Rows.
Benefits that model people the way organizations actually employ them — on SAP SuccessFactors today and on whichever HRIS, payroll or PEO your next population brings.