SAP SuccessFactors Rehire Switch Cannot Be Reversed: What Changes on November 13

31 October 2026 | SAP What's New initially published 2 October; revised 30 October | 2H 2026 production valid-as-of date: 13 November 2026 | Status: customer-configured release enhancement, not verified live in any particular production tenant.

A setting that looks like a routine onboarding improvement deserves a change-control meeting before anyone enables it. In its 30 October revision to the 2H 2026 release note, SAP added a warning about Enable Rehire on New Employment with Future Termination: once the switch is turned on, it cannot be turned off. SAP also instructs customers to finish in-flight Legal Entity Transfer cases before activation. This is a new clarification to a feature first documented on 2 October, not a feature first announced on 30 October. SAP What's New: OBX-37336, change history and configuration warning.

Why a one-way setting changes the release conversation

Consider an employee moving between legal entities while their existing employment has a scheduled termination date. Recruiting or a third-party applicant tracking system starts onboarding before that termination takes effect. In the previous flow, the candidate could be classified under the Legal Entity Transfer hire type, even when the underlying employment situation did not warrant it. SAP says this created inconsistent routing and did not align with Employee Central, which does not support Legal Entity Transfer as a hire type. The new option directs qualifying scenarios to Rehire with New Employment. That is an improvement in classification, but it also changes the workflow, data mapping and test cases the project must support. SAP's before-and-after explanation.

The irreversible switch is not a harmless cosmetic toggle. SAP explicitly says the old Legal Entity Transfer hire type is no longer available once the option is enabled. Therefore, I would treat activation as a controlled process migration, not an administrator's convenience setting. The practical question is not simply whether the switch appears in Preview. It is whether HR operations, recruiting integrations and Employee Central can handle the resulting classification for real cases. SAP implementation procedure and prerequisite permissions.

Exactly what SAP has documented

The setting lives under Admin Center > Onboarding General Settings > Rehire Settings. SAP labels the enhancement Customer configured and General Availability in the 2H 2026 release, with a valid-as-of date of 13 November 2026. General Availability is the release classification, not proof that your tenant already has the feature in production. The release note's latest revision is 30 October 2026; its change history says the additional note explains the implications of enabling the switch. Official release status and revision history.

For a prior employment with a future-dated termination, SAP describes Rehire with New Employment routing when the new start date is in the future or the day after termination. The same-day start-and-termination scenario is explicitly excluded. For a past termination, the application can route to Rehire with New Employment or Rehire with Old Employment, according to the conditions. Do not generalize this as 'all rehires automatically become new employment.' The documentation defines narrower cases. SAP's date-dependent routing rules.

Third-party ATS integrations can also initiate Rehire with New Employment for candidates with future-dated terminations, subject to SAP's API validation that a termination record exists. That makes this relevant to SmartRecruiters and other recruiting integrations, but it does not prove that every existing customer mapping works without changes. Test the actual payload and the resulting OnboardingInfo process subtype, rather than inferring success from an HTTP success code alone. Official third-party ATS support statement.

The cutover prerequisite teams must not overlook

SAP's revised documentation is explicit: complete all in-flight Legal Entity Transfer cases before enabling the setting, because those cases must continue under their existing process. The switch cannot be disabled after activation. Before a configuration owner approves the change, obtain a count and owner for open cases, determine how to close or defer them safely, and agree a cutover window with HR operations. This operational plan is my recommendation; the irreversibility and in-flight requirement are SAP's documented constraints. SAP's activation instructions.

The configuration also has authorization prerequisites. SAP lists the applicable OnboardingInfo object permission and the Rehire Inactive Employee with New Employment Manage Hires permission for coordinators. After initiating a test case, inspect the OnboardingInfo object: processSub Type should indicate Rehire With New Employment and Process Sub Type Detail should indicate Future Termination. SAP warns that Default in the latter field indicates the Legal Entity Transfer classification. Treat these fields as test evidence, not just background implementation trivia. SAP's permission and field-validation checklist.

Five acceptance tests before the November production change

1. Baseline and rollback decision: inventory active Legal Entity Transfer cases, relevant permission roles and existing routing rules. Record the setting's initial value in Preview. Since the switch cannot be turned off, use a disposable or approved test environment and do not flip it in production for exploratory testing. Configuration warning.
2. Future termination: test a candidate whose old employment ends before the new start date. Verify that the process is classified as Rehire with New Employment and that the process subtype detail is Future Termination. Include a third-party ATS initiation path if your organization uses one. Routing and ATS conditions.
3. Boundary dates: test the day-after-termination case and the explicitly excluded same-day case. Record what your tenant actually does rather than assuming a single rule covers both. Also test an already-terminated employee to distinguish old-employment and new-employment choices. SAP's date exclusions.
4. Downstream data: validate Employee Central employment records, custom fields, integration mappings, notifications and rehire data-save behavior. SAP's separate centralized service layer enhancement validates and merges rehire data; do not confuse that automatically-on save capability with this customer-configured routing switch. Centralized service layer release note.
5. Identity and communication: test welcome emails, login access and the transition period between termination and new start. SAP's login guide warns that employees with a gap may be unable to sign in using a third-party SSO provider during that period; the available login paths depend on configuration. Verify actual IAS and SSO behavior before signing off. SAP rehire login guidance.

Do not confuse this with the separate Preview rehire rollout issue

SAP KBA 3839948 documents a data-center-specific Preview rollout for centralized rehire save features. That notice concerns feature visibility and planned Preview enablement dates. It does not remove the irreversible-toggle warning, establish that your production tenant is updated, or prove that the routing change has been tested. If a control is missing in Preview, check the relevant KBA and your data center before diagnosing a configuration defect. SAP KBA 3839948.

A documentation nuance worth checking

A separate SAP Community overview published on 30 October describes several 2H rehire enhancements together, including username alignment and data merges. For precise identity behavior, rely on the specific What's New entry for each feature. For example, SAP's Correct Username Assignment for Rehire on Old Employment note describes matching the username to the selected previous employment's User ID, with a separate option to retain the onboarding username. Do not treat a broad summary's reference to email or credentials as a universal username rule across all rehire scenarios. SAP Community overview; specific SAP username release note.

What I would do now

Ask the HRIS release owner for one decision: Are we ready to retire the Legal Entity Transfer onboarding path for qualifying future-termination scenarios? If the answer is unclear, do not enable the switch in production. Complete the in-flight case inventory, test the date boundaries and ATS integration, verify the resulting Employee Central data, and document an explicit go/no-go approval. The setting is a useful simplification when the process is ready; its irreversibility is exactly why the readiness evidence matters. SAP's revised 30 October release note.