Executive Summary When a recruitment vendor claims “ownership” of a candidate already in your database, treat it as a contract + data governance issue, not a reputational issue. Your goal is to (1) verify facts (who sourced, when, under what permission), (2) confirm what your contract actually says about exclusivity/ownership and referral fees, (3) resolve commercially without creating precedent, and (4) tighten your process to prevent repeats.

Key Recommendations

1. Don’t engage emotionally—switch to evidence-based resolution

• Request a written claim from the vendor with specific proof:
• Candidate identity details (name + contact info)
• Date they “introduced”/sourced the candidate
• What they believe “ownership” means (exclusive right? fee credit? GTM agreement?)
• How they obtained contact data (lead source, campaign, referrals)
• Any messages/emails proving their involvement
• Keep your internal response factual: “We are reviewing against our records, contract terms, and sourcing timeline.”

1. Verify the candidate’s presence and history in your system (your “source of truth”)

• Pull the candidate record history from your ATS/CRM:
• When the candidate was created in your database
• Who created it (your team vs vendor vs agency)
• Original lead/source field values
• Consent/permission notes tied to data capture (if you store them)
• Communication logs (who contacted the candidate first)
• The most important fact patterns:
• If your database record predates the vendor’s claim → you likely have the stronger basis to reject “ownership.”
• If you can show the vendor introduced the candidate and your record was created later based on their effort → you may negotiate a referral fee/credit, but only if your contract supports it.

1. Check your contract clauses before you decide anything

Focus on these areas in the vendor agreement and SOW:

• Definition of “ownership,” “exclusive rights,” “scrubbed lists,” or “no touch”
• “Referral fees” vs “placement fees”
• Time windows (e.g., 30/60/180 days) for “existing candidate” claims
• How disputes are resolved
• Required notification procedures (e.g., “vendor must register leads within X days to get credit”)
• Whether there is any “protected list” or “vendor lead database” mechanism
• Who bears responsibility for data privacy/consent and for lead registration

Important: Many agreements do not actually grant “ownership” of a candidate as a legal concept. They usually govern commercial fees and lead credits—only if the vendor followed specific processes.

1. Separate “commercial credit” from “legal/ethical disputes”

• If the vendor’s evidence shows they truly generated the lead and your process did not capture it correctly, consider a controlled commercial settlement:
• Partial credit
• Reduced referral fee
• One-time settlement to close the matter
• If your records show they didn’t source the lead (or your record pre-exists their claim), you should decline the charge, but remain professional.

1. Respond with a structured dispute stance (recommended wording)

• “We acknowledge receipt of your claim. Based on our ATS/CRM history, the candidate record was created on [date] by [owner], and the lead source recorded is [source]. We cannot accept fees without confirmation of lead registration/compliance with the agreement terms. Please provide written evidence of sourcing timing, lead registration, and the contractual basis for your claim. Once reviewed, we will revert within [X] business days.”

1. Escalate internally and set a response timeline

• Involve (as needed): Talent Acquisition Ops, Legal/Procurement, and Data Privacy/Compliance.
• Set a firm review SLA (e.g., 5–10 business days) to avoid the vendor turning it into a recurring issue.

Business Impact

• If handled loosely: You risk paying unearned fees, creating a precedent vendors will exploit (“candidate already exists” claims).
• If handled rigidly without evidence: You risk damaging partner relationships and may lose future service quality.
• Best outcome: Evidence-backed resolution + contractual clarity to protect your cost and candidate experience.

Risks (and how to mitigate)

1. Paying incorrectly / precedent risk

• Mitigation: Require lead registration proof + timing evidence + contract clause alignment.

1. Data/privacy risk

• Mitigation: Confirm they have permission to share/process the candidate data and that their lead capture practices align with your internal policies (verify with your compliance team).

1. Candidate relationship risk

• Mitigation: Do not pressure or confuse the candidate; communicate only internally.

1. Legal ambiguity around “ownership”

• Mitigation: Focus on “fee entitlement” and “lead credit,” not ownership as a general legal principle.

Immediate Next Steps (Practical Checklist)

1. Within 24 hours:

• Log the dispute in writing and freeze any billing pending review.
• Request vendor evidence: sourcing timeline, registration proof, and contractual basis.

1. Within 3–5 business days:

• Extract ATS/CRM record audit (created date, source, owner, communication logs).
• Map vendor claim to your contract clause(s).

1. Within 5–10 business days:

• Decide one of these outcomes (in writing):
• Reject claim (no evidence + record predates claim + no contract entitlement)
• Approve partial credit/referral fee (vendor evidence supports a lead contribution)
• Negotiate settlement (one-time resolution to close the case)

1. Update your vendor operating model to prevent recurrence:

• Introduce “lead registration rules”:
• Vendor must register candidate leads in a defined system within X days to claim fee credit
• Define “existing candidate” handling:
• What happens when a candidate already exists (timelines, proof required)
• Add an explicit dispute resolution clause with evidence requirements
• Maintain a protected/verified “source of truth” field in ATS (so disputes don’t become subjective)

Suggested Evidence Package (What you should ask both teams to provide)

• ATS/CRM audit trail screenshots/export (candidate ID, creation date, source, owner, notes)
• Vendor lead confirmation email + timestamp
• Contract clause excerpts referencing fee/referral entitlement
• Any lead registration records (if your process has one)
• Communication log showing who contacted the candidate first

If you need help implementing these recommendations or would like expert guidance tailored to your organization, the team at Zunavish would be happy to assist.