Recruiting Integration Flow: From Candidate to Employee Record
Understand how data moves from Recruiting Management through Recruiting Marketing and into Onboarding and Employee Central, including the touchpoints, timing dependencies, and common breakpoints in that chain.
Explanation
Recruiting rarely operates as an isolated module. Once a requisition is approved and a candidate is hired, data must flow reliably into Onboarding (or Onboarding 1.0 in older landscapes) and eventually into Employee Central as a new hire or rehire record. Understanding this integration chain is essential for any intermediate consultant because most production defects in recruiting surface not inside the applicant tracking screens but at the handoff points between systems. The typical flow starts with a requisition created in Recruiting Management, which may be sourced from an Employee Central position or a standalone job requisition depending on configuration. Candidates apply through the Career Site (Recruiting Marketing), and their application data is pushed into the Applicant Tracking System (ATS) side of Recruiting Management. As the candidate progresses through statuses (Screening, Interview, Offer, Background Check), each status change can trigger downstream events. The most consequential transition is moving a candidate to a 'Hired' or equivalent final status, because this typically initiates the New Hire Data Model (NHDM) transfer to Onboarding, and subsequently to Employee Central once onboarding tasks are complete. A key architectural point: the New Hire Data Model acts as the bridge between Recruiting and Onboarding. It maps candidate profile fields, offer details, and job information into a structure Onboarding can consume to generate onboarding tasks and eventually create the Employee Central foundation and employee records. Field mapping between Recruiting candidate fields and Employee Central foundation objects (such as position, department, cost center) must be configured carefully; mismatches here are one of the most common causes of failed or incomplete new hire creation. Integration also depends heavily on the underlying provisioning settings and the specific SuccessFactors instance configuration - some customers use Onboarding 1.0, others use the newer Onboarding module, and the data flow, timing, and available touchpoints differ between them. Because product behavior and available integration center scenarios evolve and vary by customer configuration, an intermediate consultant should always verify current mapping and trigger points in the specific customer's provisioning and configuration workbook rather than assuming a universal flow. Troubleshooting this chain typically starts with confirming three things: (1) did the requisition and candidate reach the expected final status, (2) did the New Hire Data Model transfer execute without field mapping errors, and (3) did Onboarding complete its tasks and successfully trigger Employee Central record creation. Many production issues stem from incomplete or inconsistent field mapping, missing foundation object values (e.g., a cost center referenced by the requisition no longer being valid), or permission gaps that prevent the integration user from writing to Employee Central. From a production support perspective, consultants should also understand that email notifications, offer letter generation, and background check vendor integrations often sit alongside this core flow and can independently fail without blocking the core hire transaction, which can create confusing situations where the employee record exists but downstream communications did not fire.
Real project scenario
A retail client reported that hires were being created in Employee Central but with missing department and cost center values, causing payroll integration failures. Investigation traced the issue to a recent reorganization where cost center codes were updated in Employee Central foundation objects but the corresponding values in open requisitions were not refreshed, causing the New Hire Data Model transfer to pass stale or invalid references.
Common mistakes
• Assuming all hires flow through the same Onboarding version without checking whether the customer uses Onboarding 1.0 or the newer Onboarding module • Not validating that foundation object values referenced by open requisitions are still valid after organizational changes • Overlooking that offer letter and background check integrations are separate from the core hire-to-employee data flow • Failing to check field mapping configuration when new hire records are created with blank or incorrect job information • Treating a successful requisition status change as confirmation that Employee Central record creation also succeeded
Best practices
• Document the exact field mapping between Recruiting candidate data and Employee Central foundation objects for each customer instance • Establish a periodic validation process to confirm foundation object values referenced in open requisitions remain valid after org changes • Separate monitoring of the core hire transaction from monitoring of offer letters, notifications, and background check integrations • Confirm which Onboarding version (1.0 or current) is in use before assuming behavior or available configuration options • Maintain a documented escalation path distinguishing Recruiting-side issues from Onboarding-side or Employee Central-side issues
Interview angle
Interviewers use this topic to assess whether a candidate understands recruiting as part of a broader hire-to-retire chain rather than an isolated ATS. Be ready to describe the New Hire Data Model's role, name the systems involved (Recruiting Management, Recruiting Marketing, Onboarding, Employee Central), and explain a realistic troubleshooting sequence for a stuck or incomplete hire.