SAP SuccessFactors integration
AI Screening Tool for SAP SuccessFactors Recruiting
Screened scores every resume against your Job Requisition's requirements, then runs AI voice or text screening on your strongest applicants — with results landing on the Candidate Profile and Applicant Status in SuccessFactors.
Where Screened fits in SAP SuccessFactors
SAP SuccessFactors is the recruiting module inside SAP's cloud HCM suite, used alongside modules like Employee Central, Onboarding, and Performance & Goals by large, often multinational enterprises that need standardized hiring across many countries, business units, and legal entities.
Recruiters build Job Requisitions from templates or directly off an open Position on the Employee Central org chart, move applicants through a configurable Applicant Status Set inside the Candidate Pipeline, and rely on native prescreening questions, Textkernel resume parsing, and Interview Central assessment forms as the system's own evaluation tools.
SAP is now also layering in SmartRecruiters, acquired in 2025, as a connected recruiting front end — but SuccessFactors Recruiting remains the system most long-tenured SAP customers run hiring through today, with existing contracts honored and no forced migration.
What Screened takes off your plate in SAP SuccessFactors
SuccessFactors' native prescreening questions let you assign point Weights to individual questions, mark some as a Disqualifier, and set a Required Score threshold that auto-disqualifies any candidate whose computed rating falls below it — recruiters can then sort the Candidate Pipeline by that rating to shortlist who's left. It's a genuine scoring engine, but the score only measures how a candidate answered a fixed multiple-choice, numeric, or rating-scale question set at the point of application; it never reads the resume itself.
Screened scores the parsed resume against the Job Requisition's stated requirements — years of experience, specific must-haves, red flags — and posts that score back to the candidate's record as an activity note, so a recruiter can weigh both — the native rating and Screened's read — without leaving SuccessFactors.
A distribution-center Job Requisition that draws hundreds of applicants against one Applicant Status Set doesn't get a live phone screen for everyone who clears the Required Score threshold — there isn't time. Screened runs its AI voice screening interview on that shortlist automatically, then writes the results link, per-question scores, and a hire/no-hire recommendation back to the candidate's record, so the recruiter's next action is moving qualified candidates to the next Applicant Status, not working through a hundred cold calls.
When a recruiter creates a Job Requisition straight from an open Position on the Employee Central org chart, the job code, cost center, and requirements are already inherited from that Position record. Screened reads whatever requirements land on the requisition either way, so a Position-driven req scores the same as one built manually from a template — nobody has to re-type qualifications into a second system just to turn on AI scoring.
Large SAP customers commonly run a different Applicant Status Set per country or business unit inside a single instance, each tied to its own Job Requisition Data Model. Screened's sync is mapped per requisition to whichever status set that req uses, so a corporate-office req in one region and a warehouse req in another can each keep their own status names while Screened's scores, results links, and recommendations still land on the right record in both.
How Screened works with SAP SuccessFactors
A candidate's Job Application lands in the Job Requisition's Candidate Pipeline; Screened pulls that requisition's stated requirements and scores the parsed resume 0-100 against them, flagging years of experience, key qualifications, and red flags.
For candidates worth a closer look, Screened runs an AI voice or text screening interview and produces a transcript, per-question scores, and a hire/no-hire recommendation.
Screened writes the resume score, results link, and recommendation back onto the candidate's record and advances their Applicant Status, so the recruiter reviews everything from the same Candidate Pipeline view already in use — a complement to the native prescreening rating, not a replacement for it.
Connecting SAP SuccessFactors to Screened takes a few clicks: you authorize the connection from your SAP SuccessFactors account, your open jobs and candidates flow into Screened, and every screening result flows back to SAP SuccessFactors — no engineering, no CSV exports, no custom build.
Built around how SAP SuccessFactors works
Screened fits the objects and stages your team already uses in SAP SuccessFactors.
The record for an open role — created from a template or directly from an open Position on the Employee Central org chart — that defines the prescreening questions, Applicant Status Set, and requirements candidates are evaluated against.
A candidate's standalone, searchable record in the SuccessFactors database, independent of any one requisition. Textkernel resume parsing populates it automatically from an uploaded resume, and recruiters search it to resurface someone for a different role later.
The requisition-specific submission — resume, cover letter, and prescreening question answers — a candidate creates when applying to one particular Job Requisition.
SuccessFactors' native knockout-and-scoring tool. Questions can be flagged Required, Disqualifier, or Score with a point Weight; the system computes a rating from the scored questions and, if a Required Score is set, auto-disqualifies anyone whose rating falls below that threshold.
The Pipeline is the status-based set of applicants working through a requisition; the Workbench is the screen recruiters use to filter, sort, and Move them between statuses. Many long-tenured customers still call it the 'Candidate Workbench' — SAP's legacy name for the tool, which still ships alongside the redesigned Applicant Workbench. The redesign is opt-in, and SAP hasn't announced a retirement date for the legacy view.
Where interviewers submit Interview Assessment Forms and the organization keeps a feedback dossier on a candidate — a separate feature from Interview Scheduling, which just handles calendars and logistics.
Review candidate fit and authenticity
Bring screening assessments and potential authenticity concerns into your team’s review. Use the written findings to decide where a closer look is needed.
Common questions
Its native prescreening questions do more than a plain yes/no knockout: you can assign point Weights to individual questions, set a Required Score threshold that auto-disqualifies anyone below it, and the system computes a rating recruiters can sort the Candidate Pipeline by to shortlist. But that score only reflects how a candidate answered a fixed multiple-choice, numeric, or rating-scale question set at the point of application — it never reads what's actually in the resume, and it can't hold a conversation with the candidate. Screened adds both: it scores the parsed resume against the Job Requisition's stated requirements, and for candidates worth a closer look, runs an AI voice or text screening interview and writes the results link and recommendation back to their record.
No. Screened writes its resume score, interview results link, and hire/no-hire recommendation back to the candidate's record as an activity note and advances their Applicant Status, so a recruiter working the Candidate Pipeline in the Applicant Workbench (or the Candidate Workbench, on instances still on the legacy tool) sees the updated status in the pipeline and Screened's full results on the candidate's record.
SAP acquired SmartRecruiters and shipped the first phase of native integration (user sync, configuration sync, and job sync) in March 2026, positioning SmartRecruiters as its long-term recruiting front end. But SAP has said existing SuccessFactors Recruiting contracts will be honored and customers are not required to migrate — the two can run side by side, and moving to SmartRecruiters is each customer's own decision on its own timeline, not an automatic cutover. Screened's integration is built against SuccessFactors Recruiting as it runs today; a later move to SmartRecruiters would be a separate integration conversation, not something forced on this one.
Yes. A Job Requisition created from an open Position on the Employee Central org chart inherits its job code, cost center, and requirements from that Position, but it's still a standard requisition with its own Applicant Status Set and Candidate Pipeline. Screened reads whatever requirements are on the requisition regardless of whether it started from a template or a Position, so scoring works the same either way.
You don't need to standardize first. Screened's sync is mapped per Job Requisition to whichever Applicant Status Set that requisition's Job Requisition Data Model actually uses, so a req in one country can keep its own status names while a req in another keeps its own, and Screened's scores and recommendations still land on the correct status in both.
Screened highlights potential concerns in resumes and checks interview answers against the job requirements. Your team can review the written reasons and interview transcript, then ask follow-up questions about experience that needs clarification.
Screened keeps assessments and written reasons for candidates screened through SAP SuccessFactors. Open the Screened candidate profile to review activity, or export a CSV of the latest decisions. For hiring decisions made in SAP SuccessFactors, use its own records. See the screening records guide.
More on how Screened works with your ATS, or see the ATS integrations we build natively.
Connect SAP SuccessFactors to Screened
Link your SAP SuccessFactors account in a few clicks and let Screened handle resume scoring and first-round interviews.