3732060 - Pre-onboarding and onboarding rehire verification occurs twice for rehires

• During onboarding of a candidate who matches an active record (for example, converting a non-paid worker to paid), the system identifies the candidate as a rehire.
• Two separate rehire verification tasks occur: a pre-onboarding rehire verification (homepage to-do) and an onboarding rehire verification (after data collection).
• Steps are repetitive and time-consuming; only one rehire check is desired.
• No error messages reported.

SAP SuccessFactors Onboarding

1. Initiate Onboarding from Recruitment for a candidate whose first name, last name, date of birth, and National ID match an active person in the system.
2. Observe that a pre-onboarding rehire verification task appears on the homepage to-do list.
3. After New Hire Data Review (if used) and completion of Personal Data Collection by the candidate, observe that an onboarding rehire verification task is created for onboarding participants.

Standard behavior: When rehire functionality is in use and a candidate matches an existing active person, the system can create both a pre-onboarding rehire verification and a subsequent onboarding rehire verification based on eligibility criteria and process configuration.

The scenario of converting a non-paid worker to a paid worker fits these matching conditions, so both checks appear.

1. Verify the rehire features are configured per product guidance (rehire with new and rehire on old employments) so the process intent is clear.
2. Identify where each check appears and when it is created:
3. 1. Pre-Onboarding Rehire Verification: homepage to-do.
4. 2. Onboarding Rehire Verification: Onboarding Dashboard (New) under Data Collection after candidate data collection and any New Hire Data Review.
5. To reduce redundancy, review and adjust the eligibility rules and configuration for the pre-onboarding and/or onboarding rehire verification so only one check runs for the intended business scenario.
6. Align process rules with how legacy profiles are handled (for example, whether a legacy profile remains active during conversion) so the matching logic supports a single required verification.
7. Validate configuration changes in a test environment to confirm that only the intended single rehire verification is created for the scenario.

• Refer to: 3325324: Pre-Onboarding and Onboarding Rehire Verification

pre-onboarding rehire verification, onboarding rehire verification, duplicate rehire check, rehire detection, contractor to employee, non-paid to paid, new hire data review, data collection, onboarding dashboard, rehire configuration, eligibility criteria, duplicate task, rehire with existing profile, ec integration, obx integration , KBA , LOD-SF-OBX-EC , Integration EC - MPH, Hire , Problem