Does screening / background check software integrate with my ATS or HRIS?

Yes, and the connectors are mature. First Advantage publishes more than 100 integration options covering Workday, iCIMS, Greenhouse, Lever, SAP SuccessFactors, and UKG [12]. Greenhouse documents supported integrations with Checkr, Sterling, Accurate, and Certn [6][7][8][9]. The useful question is how much of the ordering, consent, and decision workflow a given connector carries, because a screening integration can order from the candidate record, pass identity data so nobody rekeys a date of birth, return status and a report link, and on some pairings post a summary result the hiring team acts on [7][8][12].

How the connection is usually built

Most employers get a certified connector the two vendors built together. First Advantage describes these as turn-key, needing little or no development work, and often live within days once you supply credentials and a support team enables the link [8][12].

A direct API build is the alternative. Checkr exposes candidates, packages, reports, and webhooks, pushing status changes to your endpoint rather than making you poll for them [2]. That path fits companies embedding screening in their own product, and it means you maintain the candidate-facing screens. Unified middleware sits in between, normalizing many ATS APIs behind one schema, which matters to software vendors connecting to many customer systems and far less to an employer on one ATS.

In almost every pre-built integration the screening vendor hosts the disclosure and authorization, which is a deliberate design choice rather than a software limit. The Fair Credit Reporting Act requires a clear and conspicuous written disclosure, made before the report is procured, in a document that consists solely of the disclosure, plus the consumer's written authorization, which may appear on that same document [1]. A standalone document is hard to guarantee inside an ATS screen that also shows job details and onboarding tasks, so vendors keep the form on their own domain where they control its wording and version history.

Checkr's hosted flow, created through the invitations endpoint, emails the candidate, collects the personal information the search needs, presents the disclosures and summary of rights, and captures consent by eSignature [2][3]. In Greenhouse that is all the candidate sees: an email from Checkr and a Checkr-hosted site [6]. Accurate's Greenhouse integration is equally explicit that consent is captured on the Accurate platform before the order is processed [7].

What changes when you embed the flow yourself

Embedding is possible and materially different. Checkr's partner documentation states that if you build your own flow on the Reports API, you must collect and store both the candidate's information and their consent inside your application, and you take on the obligation to provide the appropriate state and city specific disclosures [3]. The practical test is who updates the form when a city changes its notice requirements: a vendor-hosted form makes that maintenance theirs, while a self-hosted form makes it permanently yours, along with storing signed authorizations in a way you can produce years later. A self-hosted flow buys back control over the candidate experience, which is why companies selling screening inside their own product often build one.

This describes how the software behaves and is general information, not legal advice. Disclosure wording and state or local notice rules are worth reviewing with counsel before you change the flow.

Status writes back; report detail usually does not. Greenhouse's Sterling integration surfaces three values on the candidate record, new, pending, and complete, updating them as Sterling progresses [8]. Accurate's integration posts webhook updates into the Greenhouse activity feed and returns a summary adjudication of clear or review with a URL to the full report [7]. Checkr recommends that partners link out to the report in its dashboard rather than reproducing the contents [3], since a consumer report carries information most people in a hiring process do not need to see.

Role-based access is therefore part of the integration. Greenhouse restricts ordering to Site Admins and to Job Admins holding the permission to view and edit private candidate and application fields, and the Sterling controls sit on the candidate's Private tab [6][8]. Workable's default is narrower than many teams expect, since only admins, recruiters, and hiring managers can request a check and view results, though a Super Admin can extend that permission and anyone granted it also starts receiving result notifications, which is how an interview panelist ends up able to read a criminal history report [11].

What should reach the HRIS at hire

The employee record needs the fact that screening completed and cleared, the date, and the package that ran. The underlying consumer report is a different category of data, and copying it into an HRIS profile managers and generalists can open spreads it well past the people who adjudicated it [7][8]. Drug test and medical examination results are stricter: under the ADA regulations, information from post-offer medical examinations and inquiries must be collected and maintained on separate forms, in separate medical files, and treated as a confidential medical record [13]. A custom field on an HRIS profile is not a separate medical file.

Adverse action almost always runs from the screening platform rather than the ATS. The Fair Credit Reporting Act requires that before taking adverse action based in whole or in part on a consumer report, the employer gives the consumer a copy of the report and a written description of their rights under the statute, then provides an adverse action notice once the decision is taken [1]. Vendors automate both notices because they already hold the report and a current rights summary.

Checkr sends the pre-adverse notice on your behalf, waits out a configurable period, then sends the post-adverse notice if the candidate does not respond, and it publishes report.pre_adverse_action and report.post_adverse_action webhook events so a connected ATS records each step [3]. The statute names no waiting period, and Checkr's own guidance treats seven calendar days as the figure generally considered adequate while noting that some jurisdictions impose longer periods, with fair chance and ban the box ordinances adding their own timing and individualized assessment requirements [4].

Your ATS is a spectator during that waiting period, and a recruiter who does not know it will email the candidate about next steps in the middle of a legally structured pause. A candidate declined for reasons unrelated to the report belongs in an ordinary ATS rejection instead, because routing that decision through the adverse action machinery blurs the record of why it was made. None of this is legal advice.

Assessment integrations move a score instead of a consumer report, which removes the FCRA layer and changes what the connector does. In Greenhouse the assessment vendor becomes an interview stage, and a transition rule sends the test automatically when a candidate lands there. TestGorilla works this way, with the invitation email sent from TestGorilla rather than from Greenhouse, and results appear first as a status while the candidate works, then as a link to the submitted test inside the interview kit [10].

Score write-back is the detail to check per vendor pair. Some integrations return a numeric score to the candidate record and some return only a link, and that difference decides whether you can filter or sort on the result inside your ATS. Greenhouse and TestGorilla also reconcile only every 30 minutes, so a finished test does not show as complete instantly [10].

Pass and fail thresholds, along with any auto-advance or auto-reject rule, usually sit on the assessment vendor's side or in your ATS automation rules, and they deserve a written policy before you switch them on, because an automated rejection based on a score is a hiring decision applied identically to everyone reaching that stage. On a validated cognitive or personality instrument, confirm the cutoff you set is the one the instrument was validated against rather than a round number chosen during setup.

Screening integrations fail in a small number of predictable ways, and duplicate orders are usually the most expensive.

Duplicate orders

Duplicates appear when more than one path can create a check: a transition rule, a manual button, and a recruiter re-running the order after profiles are merged or a candidate reapplies. You pay for each report created, so restricting ordering to admin-level permissions, as Greenhouse does, removes most of the exposure [6].

Candidates stuck awaiting consent

Candidates stall in the vendor's hosted flow more often than anywhere else, and the ATS shows the check as pending with no explanation attached. Checkr invitations expire after seven days if the candidate has not completed them, so a reminder at day three is worth more than discovering the expiry at day eight [3].

Results that never write back

Write-back fails quietly when webhook credentials expire, when a firewall blocks the callback, or when the connector was authorized by an employee who has since left. Connectors that depend on an API key held by ATS support, as the Greenhouse links to Sterling and Certn do, break when that key is rotated [8][9].

Package mismatches by role or jurisdiction

Per-order package selection is where errors concentrate, because the person clicking is a recruiter rather than a compliance analyst. A driving role ordered on the standard package comes back without a motor vehicle record, and a check submitted with the wrong work location can generate the wrong state disclosure [6]. Mapping packages to requisition types in advance, the way Accurate's integration uses pre-configured custom fields, takes that decision out of the moment [7].

International checks that need different consent

Non-US checks need consent handling a domestic connector does not provide. Checkr notes that international checks can involve additional steps, supplementary documents, and more time, and that country rules differ, with France limiting checks to what is relevant to the position [5]. Candidates outside the United States are not covered by the FCRA flow, so the disclosure your integration serves them may be the wrong document.

Ask about ownership before features, because the expensive surprises come down to which party holds a responsibility.

• Which exact ATS edition is the connector certified against, and is it native or an API build we maintain? [12]
• Who hosts the disclosure and authorization, and if we host it, do you supply state and city specific versions? [1][3]
• What writes back: a status only, a status plus an adjudication summary, or a report link? [7][8]
• Which ATS roles can order a check and read the result by default, and can we narrow that before go-live? [6][11]
• Do you send the pre-adverse and adverse action notices, what is the default waiting period, and how do you handle jurisdictions that require longer? [3][4]
• What happens when a candidate lets an invitation expire, and are we billed for it? [3]
• Are per-check fees and passthrough court costs billed by you or by the ATS? [14]
• For assessments, does a numeric score write back to a field we can filter on, or only a link? [10]
• For hires outside the United States, which countries run through this connector, and what changes for the candidate? [5]