TL;DR / Key Takeaway
In an employer of record (EOR) background check arrangement, the EOR typically owns the legal screening process as the W-2 employer, but the client company controls which role requirements, risk tolerance, and adjudication standards apply. Confusion over who initiates, pays for, and makes final decisions on background checks is one of the most common compliance gaps in global and domestic EOR relationships. Your contract with the EOR must explicitly assign FCRA responsibility, data ownership, and adverse action duties before the first candidate is screened.
What HR Teams Need to Know
Employer of record arrangements have moved from a niche global expansion tool to a mainstream workforce strategy. You might use an EOR to hire in a state where you lack a legal entity, onboard international talent without establishing a foreign subsidiary, or manage contingent labor at scale without growing your internal HR headcount.
But EOR relationships create a structural ambiguity that doesn’t exist in traditional employment: two organizations share employer-like responsibilities, yet only one of them is the legal employer on paper. The EOR issues the paycheck, withholds taxes, and carries workers’ compensation coverage. The client company directs the work, sets performance expectations, and often makes the actual hire/no-hire decision.
Background screening sits uncomfortably across this split. The Fair Credit Reporting Act (FCRA) assigns specific obligations to “users” of consumer reports — disclosure, authorization, pre-adverse action notice, adverse action notice. When two entities are both functionally involved in the hiring decision, regulators and plaintiffs’ attorneys will ask: who was the user of the report, and who failed to meet their obligations?
This matters because background check compliance failures are among the most litigated areas of employment law. FCRA class actions can result in substantial settlements and statutory damages, and EEOC guidance on the use of criminal history records, along with separate state and federal restrictions on employment credit checks, adds further layers of exposure. If your organization is using an EOR and has not explicitly documented who owns each step of the screening workflow, you have an open compliance gap — regardless of how good your EOR’s screening vendor is.
Detailed Analysis
Who Actually Holds FCRA Responsibility?
The FCRA does not use the term “employer of record.” It uses “user of consumer reports” and “procurer” — concepts that predate the modern EOR industry. Courts and the FTC generally treat the entity that obtains and acts on the background check report as the responsible party, even if another entity is the legal employer for tax and benefits purposes.
In practice, this plays out in one of three models:
| Model | Who Initiates the Check | Who Adjudicates Results | Who Bears FCRA Liability |
|---|---|---|---|
| EOR-owned screening | EOR | EOR, often with client input | Primarily the EOR, as the procuring user |
| Client-owned screening | Client company | Client company | Primarily the client, even though EOR is legal employer |
| Hybrid/shared model | EOR facilitates, client specifies requirements | Joint, per contract | Potentially both — highest litigation risk |
The hybrid model is the most common in practice and the riskiest from a compliance standpoint. When both parties have a hand in obtaining and acting on the report, both can be named as co-defendants if the disclosure form was non-compliant, the adverse action timeline was missed, or the pre-adverse action notice never went out.
Why the Hybrid Model Dominates — and Why It’s Risky
Most client companies don’t fully delegate hiring judgment to their EOR. You still want to see the criminal history report, evaluate it against your own internal decision matrix, and make the final call on whether to proceed. Your EOR, meanwhile, needs to confirm the check was completed before generating an employment contract and running payroll setup.
This produces a workflow where:
- The EOR’s screening vendor runs the check and issues FCRA disclosures
- The client’s hiring manager reviews results and makes the practical decision
- Neither party is fully clear on who sends the pre-adverse action notice when a report surfaces disqualifying information
That gap — the pre-adverse action and adverse action sequence — is where most EOR-related FCRA exposure concentrates. If the client flags a disqualifying conviction and instructs the EOR not to proceed, but neither party sends the candidate the required notice and copy of the report, you have a textbook FCRA violation with two potential defendants.
Data Ownership and Retention
A second operational issue: who stores the background check report, and for how long? FCRA requires users to maintain records supporting adverse action decisions, and many state laws impose their own retention requirements for employment records. In an EOR relationship, report storage often defaults to whichever party’s screening vendor ran the check — which may not be the party best positioned to produce that record if litigation arises years later, especially after the EOR relationship has ended.
Compliance Considerations
FCRA Obligations Don’t Disappear in an EOR Structure
The FCRA’s core requirements apply regardless of which entity is contractually designated the “employer”:
- Standalone disclosure: A clear, conspicuous written disclosure that a background check will be obtained, separate from the employment application or offer letter.
- Written authorization: Signed by the candidate before the report is procured.
- Pre-adverse action notice: Sent before any final decision, including a copy of the report and the Summary of Consumer Rights.
- Adverse action notice: Sent after a reasonable waiting period following the pre-adverse action notice (the exact timeframe can vary by state and should be confirmed with counsel), confirming the final action and providing required disclosures.
If your EOR’s disclosure form bundles screening consent with other onboarding paperwork, or if neither party sends the pre-adverse action notice because each assumes the other is handling it, your organization retains exposure — even though the EOR is the W-2 employer.
EEOC Guidance and Individualized Assessment
The EEOC’s guidance on arrest and conviction records applies to whoever is making the hiring decision based on that information. If your hiring managers are the ones reviewing criminal history and deciding not to proceed, your organization — not just the EOR — needs an individualized assessment process in place: nature of the offense, time elapsed, and relevance to the job.
State and Local Fair-Chance Laws
Ban-the-box and fair-chance laws (California, New York City, Illinois, and dozens of other jurisdictions) regulate when in the hiring process criminal history can be requested and how adverse decisions must be communicated. These laws typically apply based on where the work is performed, not where the EOR or client company is headquartered. If your EOR is hiring on your behalf across multiple states, your screening timeline needs to accommodate the most restrictive applicable jurisdiction for each candidate.
Vendor Due Diligence
Not all EORs use FCRA-compliant screening vendors, and not all screening vendors used by EORs integrate properly with U.S. adverse action workflows — particularly EORs built primarily for international payroll and compliance rather than U.S. employment law. Before signing with an EOR, your legal and HR compliance teams should request:
- Sample disclosure and authorization forms
- Documentation of the EOR’s adverse action process
- Confirmation of which entity is named as the “user” on the consumer report
Action Steps for Your Team
Immediate (owned by HR and Legal):
1. Audit your current EOR contract for explicit language assigning background check responsibility — initiation, adjudication, and adverse action notices.
2. Request your EOR’s screening disclosure and authorization templates and have employment counsel confirm FCRA compliance.
3. Document your internal decision matrix for criminal history review, and confirm whether your hiring managers or the EOR applies it.
Near-term (owned by HR with Procurement/Legal support):
4. Negotiate a clear contractual designation of which party is the “user” for FCRA purposes, with indemnification language covering screening-related claims.
5. Establish a single point of accountability for adverse action timelines — ideally one party, not a shared responsibility, to eliminate the “I thought you sent it” failure mode.
6. Centralize report storage and retention so records are accessible regardless of EOR relationship status down the line.
Longer-term (owned by HR leadership and Compliance):
7. Standardize your screening requirements across all EOR partners if you use multiple vendors for different states or countries, so decision criteria don’t vary by geography.
8. Build EOR-specific screening audits into your annual compliance review cycle, alongside your standard FCRA and EEOC audit process.
FAQ
Does using an EOR eliminate our FCRA responsibility as the client company?
No. FCRA liability attaches to whoever functions as the “user” of the consumer report, which can include the client company even when the EOR is the legal employer. Your contract and actual workflow — not just your payroll structure — determine exposure.
Can our EOR run background checks on our behalf and still hold us harmless?
Only if your contract explicitly includes indemnification language covering screening-related claims, and your EOR’s process is actually FCRA-compliant. Indemnification clauses don’t prevent you from being named in a lawsuit; they only affect cost allocation afterward.
What happens if a candidate disputes a background check result in an EOR arrangement?
The entity named as the “user” on the consumer report is generally responsible for handling the dispute per FCRA reinvestigation requirements. This should be clearly assigned in your EOR contract to avoid delays that extend beyond FCRA timelines.
Should background check requirements differ by state when using an EOR for multi-state hiring?
Yes. Ban-the-box, salary history, and fair-chance timing laws vary significantly by state and apply based on where the candidate will work. Your EOR’s screening workflow should be configured per jurisdiction, not standardized nationally.
Is it better to run background checks ourselves rather than rely on the EOR?
It depends on your risk tolerance and internal compliance infrastructure. Client-owned screening gives you direct control over the FCRA process, but only if your organization has the compliance resources to manage disclosures, authorizations, and adverse action notices correctly across every jurisdiction where your EOR hires on your behalf.
Conclusion
EOR relationships don’t simplify background screening compliance — they redistribute it, often without clear documentation of where responsibility actually lands. The organizations that avoid litigation exposure are the ones that treat the EOR contract as a compliance document, not just a staffing agreement, and that assign FCRA and adverse action responsibility explicitly rather than assuming it’s “handled.”
BackgroundChecker.com works with HR teams, staffing agencies, and EOR partners to run FCRA-compliant background checks with automated adverse action workflows, dedicated account management, and integration with the ATS and HRIS platforms you already use. Whether your organization screens 10 hires a year through an EOR or manages a workforce of 10,000 across multiple employment structures, our platform is built to make ownership of the screening process clear, documented, and defensible. Request a demo or start screening today to see how a transparent, per-check pricing model and purpose-built compliance workflows can close the gaps that EOR arrangements tend to create.
—
This article is for informational purposes and does not constitute legal advice. Consult qualified legal counsel for compliance guidance specific to your organization.