← 返回教程首页 | 视频图文笔记 第 1 / 5 期

Workday 福利模块第一课:福利事件、变更福利实操与福利组配置(ZaranTech 导师课)

Introduction and Foundation Setup on Workday HCM | ZaranTech

频道:Workday Learner Community(ZaranTech) 时长 1:22:42 发布于 2024-09-11 31 帧对照 · 全片覆盖 原视频 ↗
⏱ 每节的 时间点 对应视频画面,点开原视频拖到该时间即可对照。
视频标题写的是 Introduction and Foundation Setup on Workday HCM,但全片实际内容是福利(Benefits)模块的导师课:福利与薪酬的区别、福利事件、以福利伙伴身份代理登录做 Change Benefits、关闭开放注册、福利安全组(Benefit Partner / Benefit Administrator)、Benefit Group 的资格规则与注册事件规则及各配置字段,最后约 40 分钟是讲师带学员在共享文档 Benefits Fundamentals Lab 里逐条复盘。本页标题与小节按实际内容编写。帧图取自视频按 45 个时间点截取的候选帧(v1_frames/f_HHMMSS.png),逐张目视比对后保留 31 帧有真实新信息的画面,14 个重复帧在 dropped 中逐一说明。字幕为 YouTube 自动生成,错词很多:benit / benfit / venfit / bfish / bankit / Benford / B group 实际都是 benefit,comms 多为 changes、Ruls 为 rule、Aid 为 Age、higher 为 hired、doc 是人名乱码等;正文统一使用正确术语,quote_en 保留字幕原样不改写,请对照理解。个别看不清的字段名、菜单项和数字已标(待核对)。画面底部的 ZaranTech 电话/邮箱横幅是该频道常驻广告,与课程内容无关。
0:20

本节议程:福利模块五大块

本节议程:福利模块五大块
  • 课程主课件是一张 Google Sheet「Benefits Fundamentals Lab」,本页标题 Agenda Session I,共 5 条:Intro、Benefit Transaction Example、Orgs and Benefit Groups、Benefits Security、Foundation Setup
  • 讲师交代本集范围:介绍 Workday 福利模块是什么、走几个福利交易例子、讲组织与福利组、福利安全(Benefit Partner / Benefit Administrator 角色)
  • 还有一段 benefits 的 foundation setup 要讲——不是做实施的人平时看不到,但得知道这个模块里都建了哪些东西、怎么导航过去
  • 这些基础配置是创建福利计划之前的必做项,配置不齐后面建不了 plan

"uh basically I'm going to go over the agenda for the today I will go over the introduction of um what is the workday benefits module and then we'll go through some benefit transaction examples"— 呃,我先把今天的议程过一遍:介绍 Workday 福利模块是什么,然后走几个福利交易的例子。

7:40

代理登录:先换成有权限账号

代理登录:先换成有权限账号
  • 要给员工操作福利交易,得先用 Start Proxy 代理登录成有 benefit transactions / benefit administration 权限的账号
  • Workday 训练环境惯例是代理成 Logan McNeil
  • 页面上方 Authenticated As 显示你真实的登录身份,Act As 字段输入要化身的人
  • 本帧输入「log」时下拉还是 No Items,得输全名才出候选人
  • 代理成功后对着员工 Lucy Collins 演示 Change Benefits

"make someone who has access to do benit transactions and bfit administration so in workday training servers it's usually Logan McNeil"— 找一个有权限做福利交易和福利管理的人,在 Workday 训练服务器上通常是 Logan McNeil。

8:20

变更福利入口:Actions 菜单

变更福利入口:Actions 菜单
  • 打开员工 Lucy Collins 的档案卡(Administrative Assistant,London),Actions → Benefits,第一项就是 Change Benefits
  • 这个菜单项非常多:View Current Benefit Elections、View Benefit Election History、View Benefit Coverage History、View Benefits Eligibility(含 Rule Results)、Change Retirement Savings、Change Benefits Annual Enrollment / Rates / Credit、Medicare 系列、View Passive Alerts 等(部分项名字太小,待核对)
  • 此刻的登录身份是 Benefit Administrator / Benefit Partner,所以能「替员工」发起福利变更
  • Change Benefits 排在最上面,是伙伴做交易的主入口

"from the actions menu we're going to go to benefits and then that first choice is change benefits so I'm I'm logged in as a as a benit administrator or a Benish partner"— 从 Actions 菜单进到 Benefits,第一个选项就是 Change Benefits。我现在是以福利管理员或福利伙伴的身份登录的。

9:20

变更福利:事件类型下拉全表

变更福利:事件类型下拉全表
  • Change Benefits 页的 Benefit Event Type 下拉一屏都装不下:Address Change、Administrative Correction、Beneficiary Change、Birth / Adoption of Child、Deferred Stock Units、Fitness Benefit、International Assignment、Legal Marital Status Change、Dependent Change 等(还有两条 AM1013 开头的是训练环境自建项)
  • 页顶 Instructional Text 写明:任何 dependent / marital status change 事件,先提供家庭身份变更证明,才能做年中的福利选择变更
  • 部分 elections 变更必须在 Benefits 部门批准后特定时间窗内提交,要求见 Benefits Policy Document
  • 必填 Benefit Event Type 和 Benefit Event Date,Submit Elections By 由规则带出;Attachments 是拖拽上传区
  • 管理员/伙伴能调用全部事件类型——这是发起权限的上限

"I could select any of these benefit event types so there's a lot of them that the administrator has a lot of access to all of these event types"— 我可以选这里任何一个福利事件类型,条目很多,管理员对这些事件类型全都有权限。

10:20

员工只能看到部分福利事件

员工只能看到部分福利事件
  • 同一页面,事件类型换成 Legal Marital Status Change,正在日历里选 Benefit Event Date(画面为 2020 年 2 月,选 25 日)
  • 员工自助时只能看到事件类型的一个子集,比如孩子出生/收养、法律婚姻状态变更
  • 哪些事件开放给员工、哪些只给福利伙伴,属于 foundational setup 里定义的内容
  • 伙伴替员工发起 vs 员工自助,差别就在这一列事件清单上
  • 本例模拟「员工结婚了」,选 Legal Marital Status Change 并提交

"employee is restricted that they could only they could come to the screen but they would only be able to select or they would only see certain of these events … so in the foundational setup we Define which events employees have access to and which events uh the bfair partner has access to"— 员工是受限的:他们能进到这个界面,但只能选择或只看到其中一部分事件……在基础配置里我们会定义哪些事件员工有权发起、哪些事件福利伙伴有权发起。

10:50

婚姻变更必须附资格证明

婚姻变更必须附资格证明
  • 提交后弹 Page Error:Legal Marital Status Change 事件要求 proof of eligibility,必须以电子表格附件形式附在请求里,点 Revise 在页面最底部上传
  • 页面顶部状态是 Event saved. Awaiting submission——事件存下来了,但没附件就是过不去
  • Up Next 区显示任务回到发起人 Logan McNeil 手里,要 Revise Benefit Changes,即由伙伴替员工收证明再重交
  • Related Links 直接挂 Benefits Policy Document,什么事件要证明查它
  • Do Another 里可以再发起一单 Change Benefits

"something like a legal maral skin requires a proof of Eligibility you must provide electronic form via attachments to your request click revise and attach the form at the very bottom of the page"— 像法律婚姻状态变更这类事件需要资格证明文件:你必须把电子表格通过附件提供到请求里,点 Revise,在页面最底部把表格附上。(字幕 maral skin 即 marital status change)

14:40

关闭开放注册并定稿

关闭开放注册并定稿
  • 任务 Close Open Enrollment:Enrollment Event Type = Open Enrollment - SWZ,Benefit Group = Active Employees in UK,表单里还有 Start / End / Effective Date
  • 先关英国员工开放注册的原因:培训机是公共的,别人开着各种开放注册和福利事件,不关掉就没法演示 mid-year 变更
  • Close Open Enrollment 选择框里点中那条 01/12/2019 开的注册;页面还有 Close Employees with Enrollments Open Until(截止日)和 Number of Enrollment to Close(本帧为 0)
  • 关键两步:点 close 之后还要 finalize 才算数
  • 开放注册开着时其他变更进不来,这是刚才那单婚姻变更的前置条件

"I'm going to close open enrollment because obviously this being a training uh server other people have been using it and creating open enrollment or other Ben events … once I you know I clicked on close then I have to finalize it"— 我要去关闭开放注册。显然这是个培训服务器,别人一直在用,还开了开放注册和别的福利事件……点了 close 之后还得 finalize 才行。

16:20

收件箱:员工动手改福利

收件箱:员工动手改福利
  • 伙伴提交婚姻事件后,Lucy 的 Inbox 里出现 Change Benefit Elections 任务:Legal Marital Status Change for Lucy Collins - Step 1 of 6,事件日期 24/02/2020
  • Health Care Elections 表里只有一条 Medical - Bupa Private Health Care,Elect 默认选中,可改 Waive
  • Coverage 默认 EE - Employee Only;Employee Cost (Monthly) 一栏有 £49.17/£88.72 两个值(待核对),右上角 Total Employee Net Cost/Credit 显示 £0.00 Monthly Cost
  • 页面 Instruction:Election changes must be submitted within 30 days——Dependent Change / Legal Marital Status Change 后 30 天内必须交选择
  • 点 Continue 进入下一步选计划

"here Lucy sees that she has an item in her inbox it says change benefit elections and because she got married on these dates um this item was Trigg to inbox … elect is already selected by default she could wave it"— Lucy 在收件箱里看到这个条目,写着 Change Benefit Elections,因为她在这天结婚了,这个条目就被触发到收件箱……Elect 默认已经选中,她也可以改选 Waive。

18:00

选完医疗:消费账户与强制寿险

选完医疗:消费账户与强制寿险
  • 选完医疗计划继续,页面滚动出 Spending Account Elections 2 项:Childcare Vouchers - Computershare Voucher Services 和 Season Ticket Loan - Computershare Voucher Services,都默认 Waive
  • 画面上可见年缴上限:Childcare Vouchers Maximum Contribution (Annual) £2,916.00、Season Ticket Loan £2,400.00,每项还分本年剩余期数、全年/月度缴款等录入列
  • 这两项是英国特色福利,讲师判断 Lucy 不符合资格,保持 Waive 直接 Continue——有有没有取决于公司和国家的配置
  • 紧接着的团体寿险不一样:Basic Group Life 基本保额是强制的,员工没有 waive 选项,必须 select
  • 再往后 Retirement Savings 环节可添加受益人,能选到谁取决于基础配置开放了哪些 relationship type

"so after electing the B plan then the other plans also show up uh such as child care vouchers uh this would be obviously company dependent and also some countries have them some countries don't"— 选完福利计划之后,其他计划也会跟着冒出来,比如托育代金券;这显然取决于公司,有些国家有、有些国家没有。

19:30

第 6 步复核页与提交确认

第 6 步复核页与提交确认
  • Step 6 of 6 是 Benefit Elections Review:Elected Coverages 3 项——Medical - Bupa Private Health Care(02/05/2011 生效,EE - Employee Only)、Basic Group Life - AXA UK (Employee)(01/01/2015,3 X Salary,Calculated Coverage £120,000.00)、Pension - Standard Life Auto Enrolment (Eligible Worker)(10%)
  • Employer Contribution (Monthly) 列合计 £206.17(换算列 $270.19,数字待核对)
  • 下面还有 Waived Coverages 折叠段(本例为空)和 Beneficiary Designations,确认无误点 Submit
  • 提交后得到的是可打印的确认页,能打印出来再签字
  • 至此整条「伙伴发起事件 → 员工收件箱选计划 → 复核提交」的链路走完

"this is a review page it has the pl that she signed up for things that were waved if there was any beneficiary designations and then she will hit submit … it's kind of like a um a printable you know confirmation and they could print it and then sign"— 这是复核页,列着她报的计划、放弃的项目、受益人指定(如果有的话),然后她点 Submit……就像一张可打印的确认单,可以打印出来再签字。

24:00

当前福利与历史查看入口

当前福利与历史查看入口
  • 员工当前福利看个人档案的 Benefits 标签页:本帧 4 项——Bupa 医疗、AXA UK 基本寿险(3 X Salary)、Standard Life 养老金(10%)、Deferred Stock - Standard Life(20%,01/01/2014 起,名称待核对),合计 £206.17
  • 旁边还有 Employee Benefit Credits 和 My Benefit Election History 两个标签
  • 要看未来生效的事件或全部记录:Actions → Benefits → View My Benefit Election History
  • 历史页 5 行都标着 current;最上面那条 effective February 24th 就是刚提交的婚姻变更
  • Benefits 标签里呈现的都是已定稿的 enrollment,刚做那单要到生效才并入
  • 排查「他现在到底有什么计划、谁被覆盖、事件日期」就靠这页和历史页

"the benefits that the person currently has they're under the benit tab here … in case there were some future dated events then you need to go under actions and then benefits and then view my benit election history so here we see uh five rows and these are marked as current events"— 此人当前的福利就在 Benefits 标签下面……如果有未来生效的事件,要走 Actions → Benefits → View My Benefit Election History。这里能看到 5 行,都标着 current。

26:30

查安全组:福利伙伴挂监管组织

查安全组:福利伙伴挂监管组织
  • 任务 View Security Group 是查福利角色分配的窗口:Security Group 输入框敲 benefit partner,就能查谁持有该角色
  • 输入框下拉给三类入口:Security Groups、Workday-Delivered Security Groups、Create Segment-Based Security Group
  • Benefit Partner 几乎总是指派给 supervisory organization(监管组织)
  • 原因:Workday 组织类型很多,但员工永远雇入监管组织,所以伙伴角色也永远挂在监管组织上
  • 查询结果就是各组织各顶级组织对应的福利伙伴名单

"I'm going to type the menu name it's called view Security Group and I'm going to try to find out who has the benit partner role … benit partner is almost always assigned to a supervisory organization"— 我要输入这个任务名 View Security Group,查一下谁有 Benefit Partner 角色……福利伙伴几乎总是被指派给监管组织。

28:40

福利管理员是按用户安全组

福利管理员是按用户安全组
  • Security Group 选定 Benefits Partner 后运行,可按监管组织核对福利伙伴是谁;测试路由时在 sandbox 里代理成那个人,看任务是否真到他手上
  • 对照角色 Benefit Administrator 完全不同:它是 user-based(按用户)安全组,不挂任何具体组织
  • 管理员一个人对整个 tenant 的福利都有管理权
  • 打开具体用户还能看到其可访问的域安全区和业务流程清单
  • Benefit Partner 通常由 HR 里专管福利的人担任

"whereas benford's administrator is a user based group so it's not assigned to a particular org that person is an administrator for the whole um organization"— 而福利管理员是一个按用户建的安全组,不指派给特定组织;这个人整个组织的福利管理员。

31:40

福利组主配置页逐字段看

福利组主配置页逐字段看
  • Benefit Group「Active Employees in U.S. - Salaried」:Effective Date 25/02/2020、Inactive No、Description 空
  • 页签共 6 个:Group Rules、Benefit Plans、Cross Plan Dependencies、Benefit Defaults、Benefit Credits、Benefit Plan Mappings
  • Group Rules 页挂两条规则:Benefit Group Eligibility Rule(同名规则链接)+ Enrollment Event Rule——一个管谁能进组,一个管什么时候能改福利
  • Waiting Period Calculation Order = Coverage Begin then apply Waiting Period;Grace Period Calculation Order 为空(这两项决定等待期和宽限期与生效日的先后算法)
  • 扣缴与地区:Frequency Monthly、Currency USD、Country / Territory United States of America
  • 福利组的本质:按资格规则(典型按国家)把一批工人圈在一起做福利处理

"so usually it's a it's a way to group a population of workers uh typically by country um and it's based elgibility rule"— 福利组通常是把一批工人归成一组,一般按国家来分,背后靠的是资格规则。

33:00

资格规则四条条件与休假坑

资格规则四条条件与休假坑
  • 点开 Eligibility Rule 看条件表(Rule Conditions 4 项,全部 And 连接):Assigned Organization any in selection list(Global Modern Services, Inc. (USA) / Spectre, Inc.)、Active Employees equal to Yes、Location Hierarchy any in selection list(United States)、Hourly Compensation Plan for Worker is empty
  • Derived Logic 把四条拼成一句人话,复核时读它最省事
  • 顶部黄色 Warning:源外部字段/计算字段没有 Benefits Eligibility 用法授权,要换字段或补授权,Workday 提供了 Benefits Eligibility Rules with Non-Benefits Report Fields 报告去查
  • 大坑:Active Employees = Yes 会漏掉休假员工——一上 leave 就不再算 active,福利组就把人踢出去了
  • 修正:条件里加一条「on leave equal yes」,休假员工继续留在组里
  • 分组口径还要配合业务:salaried 和非 salaried 开放注册不同时做,就必须分开建组

"because the moment someone goes on leave um they're not going to be considered an active employee so we're going to have issues with that so ideally this criteria should also say should also include people who are on leave so you should say something like on on leave equal yes"— 因为一个人一旦开始休假,就不再被视为 active 员工,这样肯定出问题。所以这个条件理想上也应该把休假的人包含进来,应该写成「on leave 等于 yes」之类。

39:00

注册事件规则:配置中枢

注册事件规则:配置中枢
  • View Enrollment Event Rule 页:这组规则是整个福利配置的主干(backbone)
  • 六个页签划分控制域:Start or Waive Coverage、Loss of Coverage、Levels of Change - Currently Covered、Levels of Change - Currently Waiving、Levels of Change - Newly Eligible、Coverage Rules
  • 本帧 Loss of Coverage 页签 6 项:触发事件如 Employee Turns 50 by Year End、Employee Turns 65、Employment Status Change;覆盖类型列有 401(k)、Basic Group Life、Charitable Giving、Deferred Stock、Dental、Medical(More (19))
  • 每行还能配 Coverage End Date = On the Event Date、Deduction End Date = On Coverage End Date、Grace Period 0 Days
  • 扣款何时开始、覆盖何时开始同样定义在这条规则里,规则最后挂到福利组上
  • 一条规则可被多组共用:Used by Benefit Groups 列着 Australia、Canada、China/Hong Kong、Green Planet Solutions、India……More (11)

"this rule is basically it says that um these event types are allowed to start or wave coverage these event types are allowed to have lots of coverage or change in coverage … when does deductions start when does coverage start uh all of that is defined within the enrollment event rule"— 这条规则基本就是在说:哪些事件类型允许开始或放弃覆盖,哪些事件类型允许失去或变更覆盖……扣款什么时候开始、覆盖什么时候开始,全部定义在注册事件规则里。

41:00

签名行与 EOI 生效日期

签名行与 EOI 生效日期
  • Enrollment Signature Line:控制本组内注册计划结束时要不要出现电子签名行;此组设 No,讲师说通常会选 Yes——员工选完 Kaiser 之类的计划,最后会看到一段「同意以电子方式签名」的声明并打勾
  • 该字段不选 Yes,签名声明就永远不出现
  • EOI Takes Effect On Date = Effective on Approval/Denial Date(本帧讲师正选中这一行):可保证明在获批或被拒当天生效
  • EOI(Evidence of Insurability)是寿险场景术语:默认保额(比如 $50,000)不用证明;超出部分保险公司会来信要求体检,证明交给供应商或在 Workday 里上传
  • 画面底部 HSA/Spending Account Deductions 区还露出 Maximum Percent Change from Previous Deductions = 1(数值待核对)和下一节标题 Employee Age Calculation

"there's a field over here called enrollment signature line that means when you are enrolled in a plan within this benefit group um should there be a signature line that showed up and over here is selected as no uh typically it will be selected as yes … so eoi is a industry term which says evidence of insurability"— 这里有个字段叫注册签名行,意思是:你在本福利组内注册计划时要不要弹出签名行。这里选的是 No,通常会选 Yes……EOI 是行业术语,指可保证明(evidence of insurability)。

47:20

白板复盘:什么是福利事件

白板复盘:什么是福利事件
  • 复盘环节在 Benefits Fundamentals Lab 表格里现场打字,先把计划盘子摆出来:Medical Health Benefit Programs、Dental Plan、FSA、Retirement Plan、LTC、Vision
  • Processing Benefit Events 行开写「Benefit Event =」,让学员先答:员工生命周期里哪些事会需要改福利
  • 定义的落点:计划给公司建好后,得在不同时间点 rollout 给员工——那些时刻就是福利事件
  • Benefit Event Rules 行已有一句话定性:Control when someone can change or enroll in benefits
  • 讲师提醒这是新内容,放慢节奏,先确保全班对齐再往下走

"once these plans are set up these plans need to be rolled out to the employees … those times where these plans are rolled out to the employees that's called benit events"— 这些计划配置好之后,得在不同时间推开给员工……计划推开给员工的那些时间点,就叫福利事件。

48:40

福利事件的定义写进文档

福利事件的定义写进文档
  • 定义完整写在文档里:Benefit Event = Life Events that enable an employee or Benefit Partner to assign benefit plan(s) to employee and/or dependents
  • 最常见的事件是 hire——入职动作本身既是 HCM 事件也是福利注册事件
  • transfer 也可能触发:员工从印度调到美国,就得进美国计划
  • 接下来记 Having a Children or adoption、Marital Status 等 life event
  • 注意定义里的主语是 employee or Benefit Partner——事件既可能员工自助发起,也可能伙伴发起

"so bit events are life events that enable an employee or benit partner to assign benit plans to employee or their dependent so the most common one is a higher event"— 福利事件就是生命事件,它让员工或福利伙伴能把福利计划指派给员工本人或其受抚养人。最常见的是 hire(入职)事件。(字幕 higher 即 hired)

52:40

事件清单与事件规则职责

事件清单与事件规则职责
  • 文档第 6 行事件清单正在扩展:Hire, Transfer, C…(打字中),旁边已写好 Having a Children or adoption、Marital Status
  • 第 8 行 Benefit Event Rules 的职责补到第二行:configuration of Start of Coverage, Change in Coverage, Loss of Coverage
  • 讲师总结:能触发福利变更的这类事件,全部配置在 benefit event rules 之下
  • 本段口播进入离职场景:termination 触发 loss of benefits 并启动 COBRA(此时文档还没写出来,下一帧才落笔)
  • 还举了个少见但存在的例子:有些公司有高管专属计划,从 director 升 VP 也可能触发福利变更

"Cobra which is continuation of benefits after you know termination but then it will be the same insurance and the same plan except now the person who's been terminated will have to pay for it 100% out of their own pocket"— COBRA 就是离职之后的福利延续,还是同一个保险、同一个计划,只是被终止的员工此后要 100% 自己掏钱。

54:40

离职触发 COBRA 自费延续

离职触发 COBRA 自费延续
  • Termination will trigger COBRA 写进事件清单(文档 J 列)
  • COBRA 是离职后的福利延续:同样的保险、同样的计划,区别是被终止的员工要 100% 自费
  • 若员工没有义务参加 COBRA,但公司必须在其离职时提供这个选择(口播在本帧窗口内)
  • 规则职责行同步补全:start of coverage、change in coverage、loss of coverage 及其他覆盖规则都维护在 benefit event rules——它是「谁能何时改福利」的控制中心
  • 文档开始写下一节(E13 打字中),进入 Benefit Group 话题

"obligated to sign up for Cobra but they will be offered Cobra at that time … the heart of all this configuration of you know the control and when someone could change oural benefits is part of the benefit event rules"— (员工)没有义务签 COBRA,但离职那时会向他们提供这个选择……这一切配置的核心——谁能、什么时候能改福利——就是 benefit event rules 的一部分。

56:10

福利组定义与同组三条件

福利组定义与同组三条件
  • Benefit Group 的定义落进文档(第 13 行):Defines a group of employees with similar benefit plans, rates and processing
  • 下面 Considerations 清单第一条刚写出:Open Enrollment
  • 复盘重点:能不能同一个组,光开放时间一致不够——计划要相似、费率要相同、处理节奏要一致
  • 组可大可小:全美国员工一个大组行,只把美国 salaried 单拎一组也行,粒度由业务定
  • 开放注册同一时间、同一费率的人群,就该合并进同一个福利组处理

"remember over here I wrote not only similar benefit plans which same rates and processing so just because they're having open rollment at the same time is not good enough but they have to be on the similar plans and same rates"— 记得这里我写的是:不仅要有相似的福利计划、相同的费率和处理方式——只是因为大家都在同一时间开放注册还不够,他们还得计划相似、费率相同。

57:10

跨国必拆组按本地货币

跨国必拆组按本地货币
  • Considerations 第二条落文档:Country/Currency(本帧新写出)
  • 一个福利组里只能有一个国家、一种货币——配置页的字段直接锁死这个约束
  • 多国员工都在 Workday 里注册福利,就得每个国家单独建组
  • 目的很实际:让员工看到的费用是自己的本地货币

"if the employees are enrolling in benfish in multiple countries then you need like a separate Benford group for uh each country that way you will make sure that the employees seese their cost in their um in their local currency"— 如果员工在多个国家注册福利,那每个国家都得单独建一个福利组,这样员工看到的费用就是自己本地的货币。

57:40

扣款频率不同不能同组

扣款频率不同不能同组
  • Considerations 第三条落文档:Frequency of Deductions(本帧新写出)
  • 扣款频率就是员工工资被扣保额的节奏:半月薪一次(semi-monthly)还是月薪一次(monthly)
  • non-exempt(小时工)半月薪扣一次、exempt 月薪扣一次的话,两者不能放同一个福利组
  • 反过来,若大家都在美国、计划和费率都一样、扣款频率也一致,salaried 和 hourly 并一组完全合理

"so if you're treating non-exempt population on a semi monthly basis and our um an exempt on a monthly basis then they cannot be on the same benefit group"— 如果非豁免人群按半月薪频率扣款,豁免人群按月薪扣款,那他们就不能待在同一个福利组里。

59:20

截图复盘美国员工组

截图复盘美国员工组
  • 讲师切到文档里单独的 benefit groups 标签页,回看提前截好的福利组配置图——本帧是「Active US Employees」组
  • 注意此组与 Salaried 组的字段差异:Frequency 是 Semi-monthly,Waiting Period Calculation Order 是 Waiting Period then apply Coverage Begin(先套等待期再算覆盖开始,顺序与前例相反)
  • 截图里的设计意图:把美国所有人都圈进来,条件是员工类型为 regular,且「active status = Yes」或「on leave = True」
  • 其余字段:Currency USD、Country United States of America、Enrollment Signature Line No、EOI Effective on Approval/Denial Date
  • 截图底部露出 Employee Age Calculation 一节,稍后展开

"so I actually have a tab in here called benfish groups I took some screenshots … we wanted to make a elgibility rule that included everybody in the United States as long as they were a regular employee type and they were on active status as far far as benf were concerned so active status equal yes or true or there on leave equal to true"— 我在这份文档里其实有个叫 benefit groups 的标签,截了几张图……我们想做一个资格规则,把美国所有人圈进来:只要员工类型是 regular、福利上的状态是 active——也就是 active status 等于 yes,或者 on leave 等于 true。

1:05:10

员工年龄按哪一天计算

员工年龄按哪一天计算
  • 截图下滚露出 Employee Age Calculation 段:此组 Calculate As Of = Event Date,按事件发生当天算年龄
  • 年龄口径共三种可选:按当前日期、按事件日期、按年末——很多计划和资格判定都依赖年龄
  • 为保证公平、避免年中年龄跳档,很多公司统一按当年 12 月 31 日计算
  • 同一画面下方还贴了 Edit Benefit Group Eligibility Rule(Active US Employees)的编辑页截图,Condition Rule 与 Description 均写着 Active US Employees(Description 带必填星号)

"in that group there's also a field for employee age calculation because there's a lot of plans and events in which the age is important … a lot of companies say we're going to calculate employee age as of uh December 31st of that year"— 这个福利组里还有个员工年龄计算字段,因为很多计划和事件都很在意年龄……很多公司会说:我们就按当年 12 月 31 日来算员工年龄。

1:08:10

员工能不能在多个福利组?

员工能不能在多个福利组?
  • 复盘提问写进文档:employee can be in one benefit group or multiple groups?(第 23 行只打出 Employee can be in)
  • 背后的硬约束:多数计划(如医疗、牙科)要求同类只能参加一个;人在多个福利组里,就可能出现同类型重复注册,直接不成立
  • 答案下一行就要落笔:必须且只能在一个福利组(见 01:09:40 帧)
  • 上方文档此时已补上两条复盘笔记:扣款频率示例 semi-monthly/monthly,以及 Benefit Group is assigned the following(先写了 Eligibility Rules 和 Event Rule 两行)

"employee and can be in One V group or they can be in multiple V groups anybody remember … most of these plans will have a requirement that you could be only enrolled in one of them"— 员工到底在一个福利组还是可以在多个福利组?还有谁记得……大部分计划都会有要求:同类你只能注册其中一个。(字幕 V group 即 benefit group)

1:09:40

福利组被赋予的三样东西

福利组被赋予的三样东西
  • 结论定格:Employee must only be in one Benefit Group at the same time
  • Benefit Group is assigned the following 三行补齐:Benefit Plans、Benefit Eligibility Rules、Benefit Event Rule——福利组就是把这三样东西绑在一起的载体
  • 员工可以同时持有医疗、牙科、视力等多个计划,但它们都必须属于同一个福利组
  • 计划经常换:公司换供应商时会在开放注册期间做 provider mapping,把旧计划上的员工整体映射到新计划(福利组页的 Benefit Plan Mappings 标签承接,见 00:31:40 帧)
  • 若同组与异组计划相同只是拆了组(salaried/hourly),同一个计划可以挂到多个组上

"so I'm adding over here the benefit group is assigned the following so the Ben uh the benit plans are assigned to the group the alil rule uh is assigned to the group and the event rule uh is assigned to the group … in that case is called uh provider mapping"— 我这里补一句:福利组会被赋予以下三样——福利计划赋给组,资格规则赋给组,事件规则也赋给组……换供应商那种情况叫 provider mapping。

1:14:10

查看符合资格员工做审计

查看符合资格员工做审计
  • 福利组建好后要测资格规则:页面右上角三个点的 Related Actions 菜单展开,可见 Benefit Group Eligibility、Audit、Benefit Eligibility Rule、Benefits、Favorite、Instances、Integration IDs 等分组
  • Benefits 里选 View Eligible Workers,列出全部命中资格标准的员工名单——用来审计你圈的人群对不对
  • 训练环境数据被用花了,Active Employees in U.S. - Salaried 只跑出 6 个人(数字待核对)
  • 右侧已经叠出 View Benefit Eligibility Rule Results 页面:Warning、Description、Derived Logic、Rule Conditions 4 items 都在
  • 单个员工的判定另走一条路:Related Actions → Benefits → View Benefit Eligibility Rule Results(下一帧)

"there is benefit group eligibility and you go to view eligible workers so this will show you a list of employees who match the eligibility criteria that you have defined so this helps you audit that you got the right set of population … only six people are being um showing up under active employees us salary"— 这里有 Benefit Group Eligibility,进去选 View Eligible Workers,它会列出符合你定义的资格标准的员工名单,帮你审计圈到的人群对不对……在 active employees us salaried 下面只出现了六个人。

1:15:50

按单个员工测资格规则

按单个员工测资格规则
  • View Benefit Eligibility Rule Results 表单:Benefit Eligibility Rule 选 Active Employees in U.S. - Salaried,Employee 选 Lucy Collins,另有 Dependent 和 View As Of 条件
  • Lucy 实际在英国,规则限定美国,按今天的日期跑,结果就是 no / false——不命中
  • 典型用法是排错:某员工为什么没收到开放注册任务?跑一把就知道他档案里哪条不满足资格规则
  • 讲师收尾预告最后一个话题 Benefit Group Audit:理想配置下应该一个员工都不返回,结果数应为零

"we see here that the rule result it says no so doc did not meet the criteria that we defined so this helps in testing or troubleshooting like okay why is this person not you know is not being part of the Open Enrollment"— 可以看到规则结果是 no,也就是说这个人不满足我们定义的条件。这对测试和排障很有用——比如,为什么这人没被卷进开放注册。(字幕 doc 为人名乱码)

1:18:10

审计必须零结果才能上生产

审计必须零结果才能上生产
  • 任务 Benefit Group Audit:本帧 216 items,列结构为 Worker、Active、Benefit Groups(组名 + 组资格规则两列)、Severity、A Problem Exists With、Problem/Solution
  • Problem/Solution 判定都是同一句:Worker is eligible for more than one Benefit Group.,Severity 全部 Critical
  • 原因很直白:这个 tenant 里一堆福利组资格条件互相重叠(CUS - Benefits Groups HR US 和 AM1013 US TX Salaried Group 等同时命中 Logan McNeil、Betty Liu 等人)
  • 生产环境不能容忍:带着这些冲突,开放注册根本跑不对——每建完一个组就运行审计,名单里一个员工都不该出现
  • 有结果就查他为什么命中多个组,把资格标准定义得更精确,直到员工与福利组恢复一对一
  • 讲师说这个 Workday 交付的审计后台具体查了什么他也说不准,看起来是把三条资格规则各跑一遍(待核对)

"these are critical errors um we cannot have these in real life our like open enrollment will not work correctly … after you create a group you run it and make sure that you don't get any uh employees in this list … you have to figure out why they're showing up in multiple groups and then Define the criteria more precisely so that um you only have one to one relationship between the employee and the benefit group"— 这些都是严重错误,现实生产里不能有——有的话开放注册都不会跑对……每建好一个组就去跑这个审计,确保名单里不会出现任何员工……一旦有结果,就得弄清他们为什么出现在多个组里,把标准定义得更精确,直到员工和福利组只剩一对一关系。