Recruit-to-Hire Data Mapping for nonrecurring pay components

[atlchan]

Hello,

I am seeking recommendations and best practices on the following issue. We are seeing nonrecurring pay components with a value of $0 coming over from the RCM Offer Approval into Onboarding as they are mapped in Recruit-to-Hire Data Mapping. The business would have to manually delete the $0 pay components in Onboarding before submitting.

RCM Offer Approval:

Recruit-to-Hire Data Mapping:

Onboarding:

Is there a way to prevent $0 nonrecurring pay components from coming over into Onboarding so we can prevent the manual work involved in deleting those pay components before submitting?

The behavior I’m observing in the system is all-or-nothing: when they are mapped, everything, including the $0 pay components, is transferred over. If they are not mapped, then the business would have to manually add those pay components.

[CameliaL]

Hi @atlchan - was this issue resolved? If not @Gopinath_Murugaiyan - could you please confirm if its expected behavior at this time? Thanks!

[CaitlinBlanche]

Hi @atlchan - how were you able to get these to pull through? Also mapped via Recruit to Hire mapping (similar to yours); however, in RNHD in Onboarding, the portlet remains closed and no values display for Non Recurring / Variable Pay. It is working as expected for Recurring Pay Component portlet. Any advise would be appreciated. Many thanks