BN72 - Retiree Benefit Entry

Hello,

We are in the process of moving our retiree benefit information from the BN32 to the BN72. Has anyone ever noticed that ineligible dependents show up on the HR13.4 (the offshoot of the BN72) but don't show up on the HR13.3 (the offshoot of the BN32)? We don't find them in the tables, and they aren't tied to the plan, but it concerns us that this doesn't happen on the BN32, but is happening on the BN72.

We are on version 10.1

Thanks!

0712131256598360.doc

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

unknown

Hi, I am curious to know if you ever switched over to BN72 successfully? We are going to be migrating our retirees to Lawson from a legacy system, and we are trying to decide whether to use BN32 or BN72. The first hing we noticed was that if you set up the retiree benefit plans so that retirees can be administered on BN72, there doesn't seem to be a mass load job for retiree benefits, like BN101 or BN531/BN532 for employees. I am curious why you decided to start using BN72 instead, if you successfully moved your retirees, and what you like about BN72 vs BN32? Thank you!

Rachel Lake

Hello. This response is probably way too late, but it could be helpful to others. We did migrate our retirees over to the BN72. So we have our actives on the BN32 and our retirees on the BN72. One thing to note is that once you move over to the BN72, you can no longer use the BN47 to input beneficiaries. That was a frustration for us. We now have to input benes on the comments section of the BN72. You also have to use new reports to pull data for the retirees - the BN233 replaces the BN231 for retirees.

Copyright © 2025 Infor. All rights reserved.