PreSearch + UKG Pro Recruiting
Set up UKG Pro Recruiting for background screening
Built around your workflows.
PreSearch builds custom UKG integrations around how your organization hires and manages workforce compliance. We configure the connection to support requirements across positions, locations, and stages of employment, from pre-hire screening to ongoing compliance. Your workflows define the integration.
Integration details
| Property | Value |
|---|---|
| Integration type | Client-specific UKG Pro Recruiting integration | Bidirectional workflow |
| Connection | Supported UKG integration method confirmed during implementation |
| Authentication | Confirmed with UKG during technical enablement |
| Data from UKG to PreSearch | Candidate/application identifiers; candidate name and contact information; position or requisition context; selected or mapped screening package |
| Data from PreSearch to UKG | Background-screening status; other agreed workflow information supported by the client's configuration |
Who needs to be involved?
Your team
Start with your UKG Pro Recruiting administrator and someone who knows your recruiting workflow. Provide the right contacts, confirm your requirements, and participate in testing.
PreSearch
We lead and coordinate the implementation from workflow definition through launch, including configuration, mappings, and testing.
UKG support
We involve UKG when tenant access, connection setup, or technical support is needed.
Timeline and your time
Implementation typically takes 3–6 weeks once UKG technical access is available. Plan for approximately 3–4 hours from your team for requirements, coordination, and testing.
Timing depends on UKG access, workflow complexity, and testing availability.
Before you begin
- A UKG Pro Recruiting administrator who can open a UKG support case and maintain Recruiting Gateway stages
- Your UKG Pro tenant ID and a named PreSearch implementation contact
- An approved screening package for the initial pilot and the roles or requisitions that should use it
- One test job and one non-production test candidate or application
Implementation steps
Choose the screening trigger stage
- In UKG Pro Recruiting, identify the point at which a recruiter is ready to request a background check—not merely begin interviewing or make a verbal offer.
- Create or use a dedicated Recruiting Gateway stage with a plain name such as Background Check or Background Check Requested. Keep the post-screening decision stage separate.
- Decide which job types, locations, or requisitions belong in the initial pilot and which PreSearch package they should use.
- Document the intended recruiter action: open the job in Recruiting Gateway, select the candidate under the opportunity, then use Request Background Check from the right-side menu.
Enable PreSearch as your background-check vendor
- Open a UKG support case to request Background Check API/vendor access for your UKG Pro tenant. UKG controls this enablement.
- Complete UKG’s Background Check API Registration Questionnaire with PreSearch and your implementation contact; do not reuse another vendor’s redirect URLs or credentials.
- Provide your UKG Pro tenant ID to PreSearch. Coordinate separate test and production enablement if UKG provides both.
- Confirm the vendor registration is complete before attempting recruiter-side configuration or testing.
Map the stage, package, and status behavior
- Set the agreed Background Check recruiting stage as the screening trigger for the initial workflow. Keep its name and intended use documented for recruiters.
- Confirm whether recruiters select the package at request time or whether PreSearch maps the package from the job, requisition, location, or another approved UKG attribute.
- Confirm the candidate/application identifiers and core contact data that UKG sends with the request. PreSearch uses that context to associate the screening record and invite the candidate.
- Agree the screening statuses that should appear in UKG and the users who may initiate a request or follow its status. Completed report contents and adverse-action records stay in PreSearch.
Test the exact recruiter path
- In Recruiting Gateway, choose the test job, select the test candidate under the opportunity, and use Request Background Check from the right-side menu.
- In the new request tab, select the expected package, review the pre-populated candidate information, add a billing code only if your configuration uses one, and continue the request.
- Confirm one PreSearch request is associated with the intended UKG candidate/application, the candidate receives the invitation, and the package is correct.
- Confirm the agreed pending and completed statuses return to UKG and that the report link takes authorized users to the corresponding PreSearch record.
Pilot the stage before broad launch
- Run the selected Background Check stage with the agreed pilot jobs or locations first.
- Have recruiters confirm the trigger appears only where expected, package selection or mapping is correct, invitations arrive, and statuses update as agreed.
- After the pilot is accepted, document the recruiter instruction and expand the configured stage to the remaining approved recruiting population.
Validation
InitiationOne recruiter action creates one intended screening request.
CandidateThe correct candidate/application is connected to the PreSearch record.
PackageThe expected screening package or requirements are applied.
InvitationThe candidate receives the invitation and can complete their information.
ProcessingThe order moves through the normal PreSearch workflow.
WritebackThe agreed screening status returns to UKG.
AccessOnly intended users can access detailed screening information in PreSearch.
Data flow
| When | Direction | What moves |
|---|---|---|
| Recruiter initiates screening | UKG → PreSearch | Candidate/application context and screening selection or mapping information |
| Screening request is created | PreSearch | PreSearch associates UKG context with the screening record and invites the candidate |
| Candidate completes intake | Candidate → PreSearch | Consent and screening-specific identity information |
| Screening progresses | PreSearch → UKG | Agreed screening status |
| Screening completes | PreSearch → UKG | Final agreed screening status |
Troubleshooting
Screening was initiated but no PreSearch request appeared.
Do not initiate a second request. Provide the candidate/application identifier, approximate time, and expected workflow so PreSearch can trace the connection.
The wrong screening package was selected.
Pause before further processing if possible. Provide the candidate/application identifier, position or requisition, expected package, and selected package so PreSearch can review the mapping.
The candidate did not receive the invitation.
Confirm contact information and ask the candidate to check spam. Do not create a duplicate request. Provide the candidate/application identifier and approximate invitation time.
Screening status is not updating in UKG.
Provide the candidate/application identifier, expected status, visible status, and approximate time. PreSearch will review the agreed status behavior for your configuration.
A user cannot access the associated PreSearch record.
Provide the user role, candidate/application identifier, and expected access. Do not send sensitive screening details by email.
A duplicate request may have been created.
Do not continue retrying. Provide the candidate/application identifier, approximate times, and available references so PreSearch can review the requests together.
Need a hand?
Contact your PreSearch implementation lead with:
- Candidate/application identifier
- Position or requisition
- Expected behavior and what actually occurred
- Approximate time of the action
Do not email sensitive screening information or report contents.