BN100 – Employee Change Benefit Update

About BN100

Run Employee Change Benefit Update (BN100) to automatically add, change, and terminate employee benefits based on changes made by personnel actions. Run BN100 after implementing actions using PA52.1 (Individual Action) or PA100 (Action Update) before you run the payroll cycle in which the benefit changes take effect. **Processing Effect BN100 determines which benefits are updated using the benefit change audit records from BN35.1 (Benefit Change Audit). Benefit change audit records are changes made by personnel actions that affect an employee's benefits. BN100 does not process changes that are on hold in BN35.1. A change is on hold if the Hold field is Yes in BN35.1. The following is a list of changes that can affect an employee's benefit. - Adding or removing the employee from an employee group used for benefits. - Changing the employee's benefit postal code. - Changing the employee's salary. Changes to all of the following data items are considered a change to the employee's salary: job code, FTE (Full-Time Equivalent), rate of pay, step, grade, schedule, salary class, or benefit salaries 1 through 5. - Changing the employee's pay frequency. Some employee changes that appear in BN35.1 are listed as affecting an employee's eligibility but do not trigger BN100 to update an employee's benefits. Those changes include changes to an employee's birthdate, age, years of service or smoker status. In addition, BN100 does not update a benefit if the salary used for the benefit's coverage calculations is overridden on benefit entry forms. BN100 updates benefits in the following sequence: 1. Stop benefits for which an employee is no longer eligible. 2. Change benefits in which an employee is enrolled but now qualifies for different coverage, contributions, or general ledger overrides. To change a benefit, BN100 stops and re-adds the benefit. 3. Add the employee into plans for which the employee has become eligible. BN100 enrolls employees into default plans with the applicabledefault coverage, default contribution, and default contribution tax type defined for each plan. For defined contribution plans with a default investment account you can run BN100 to enroll employees with the default investment account. If an employee has dependents, you can run BN101 to create dependent benefit coverage for default plans that cover dependents. Benefit automation rules are used to determine when a personnel action affects employee benefits. Benefit automation rules are defined in BN16.2 (Add Rules), BN16.3 (Change Rules), and BN16.4 (Termination Rules). If no automation rules exist for a personnel action that affects benefits, BN100 lists the affected benefits but does not update the benefits. BN100 can create a COBRA record for an employee affected by a termination rule defined as a qualifying COBRA event. A termination rule is a qualifying COBRA event if the COBRA Occurrence field is Yes for the rule in BN16.4. BN100 will create a COBRA record in BN70.1 (COBRA Participant) if the employee does not have a COBRA record in effect on the date the employee's benefit isterminated. The employee's Occurrence Date is the day after the employee's benefit is terminated. If a change makes an employee ineligible for a flex plan, BN100 stops the employee's flex dollar record and all benefits under the flex planaccording to the flex plan's termination rules. You can see the results of running BN100 without updating employee benefits by selecting Report Only in the Update field and running BN100. For each benefit updated for an employee, the report lists the following applicable items: the update performed, start date, coverage option, multiple of salary, coverage amount, the annual employee contribution, whether the contribution is a percent or an amount, employee and company contributions, and deductions for the contributions.

Updated files (23)

Referenced files (68)

Program calls

Invoked programs (15)

ACAC, ACTA, API4, HRHI, HRLO, IFAC, IFCU, IFLU, IFOB, IFSG, IFUP, SLSE, SLSU, ZB31, ZB32