People · Benefits
Route /benefits/plans Flag benefitsEnabled

Benefits Plans

Plan catalog — what can be elected — not the payroll run and not medical files in Work Graph.

Scroll to Flowcharts. Scenario: Publish a benefits plan.

Plan catalog

What people may elect

Benefits plans is the catalog. Elections happen on enrollment. Pay impact is the payroll benefits seat.

Payroll → Benefits plans Route /benefits/plans Org flag benefitsEnabled Payroll Manager · HR Admin · Admin

The job of this console

Author and publish plans so enrollment has something to point at. Keep medical detail out of graph metadata.

Seat at the table

HR and payroll admins. Employees do not edit the catalog.

The working rhythm

Create, publish, tell enrollment, confirm a test election.

Moments that bring you here

Annual renewal. New carrier. A plan retirement. Before open enrollment.

ⓘ
Catalog, not PHI store
Do not persist medical or bank values in AI/graph. Carrier files are the exchange.

Flowcharts

1 — Catalog then enroll

Publish a plan, then open enrollment.

flowchart TD
  A[Open Benefits plans] --> B[Create / edit]
  B --> C[Publish]
  C --> D[Enrollment]
  D --> E[Payroll impact / carrier]
            
  1. 1
    OpenPayroll → Benefits plans.
  2. 2
    AuthorCatalog.
  3. 3
    PublishAvailable to elect.
  4. 4
    EnrollEnrollment screen.

Overview

Plans are the catalog. Enrollment is who chose what. Carrier files send/receive. Payroll benefits is pay.

How to use

1. No PHI in names/comments
Masking.
2. Effective dates
Mid-year adds need care.
3. Not a deduction code only
Deductions may map from plans.