Candidate Document Collection Tools for Recruiters: What to Compare After the Upload

This article is for information only and is not legal advice. Regulatory references are accurate at the date of publication. Seek qualified advice for any decision about an individual file.

Candidate document collection tools are the portals, forms, upload links and mailboxes a recruiter uses to get ID, right-to-work evidence, proof of address, bank details and qualifications from applicants. Collection solves the chasing problem. It does not solve the checking problem: a perfectly organised folder can still hold a passport that expires before the start date and a bank account in someone else's name. The useful question when choosing a tool is what happens to the files after they arrive.

What collection tools do, and what they leave to you

Most collection tools stop at three jobs: ask the candidate for a list of documents, receive the files, and store them against a candidate record. Checking that the files agree with each other is a separate step, and in many teams it is still a person with two tabs open.

Collection answers "do we have the file"; validation answers "do the files agree". Both are needed before an offer becomes a start date. The rest of this article describes the second part, field by field. The wider approach is covered in our guide to verification automation.

The cross-checks, field by field

A cross-check compares one field on one document with a field on another document or an official source, and defines in advance what a mismatch looks like. Six cover most recruitment files.

Two points matter more than the table. First, a mismatch is a question, not a verdict. Most name differences are marriage, translation or a missing middle name, and rejecting on that alone is both unfair and a source of discrimination risk. Second, the reviewer's next step must be written down per mismatch type, otherwise every case is decided differently by whoever is on shift.

Example: a temporary-worker file that passes collection and fails validation

A candidate uploads a passport, a share code, a bank statement and a utility bill. The portal shows four green ticks. A validation pass then finds that the passport expires in nine days, the share-code result gives a different order of given names, the bank statement belongs to a joint account whose first holder is a partner, and the bill is five months old. None of these is proof of anything improper. Each is a question for the candidate, and each would have been found on day three of the assignment instead of day zero.

United Kingdom: the right-to-work check is a separate act

In the UK, a copy of a passport in your portal is not a right-to-work check. The employer's check must follow the Home Office method: for many non-British candidates it is the online check using the candidate's share code and date of birth, where the result page shows a photograph to compare with the person in front of you. The Home Office guidance requires employers to keep a clear copy of the evidence for the duration of employment plus two years (GOV.UK: check a job applicant's right to work).

What this proves: the individual's status on the date of the check. It does not prove the passport scan in your folder is genuine, and it does not replace comparing the person to the photo. Your collection tool should therefore store the check result with its date and the name of the person who ran it, and flag a follow-up date where the status is time-limited.

On data handling, the ICO's guidance on recruitment says to collect only what is needed at each stage (ICO: employment practices and data protection). Asking every applicant for ID at application stage, rather than at conditional offer, runs against that.

What recruiters ask on forums

Questions that come up repeatedly in recruiter and HR communities are practical rather than legal.

"Candidates send blurry phone photos or a PDF of a photo of a paper. Can I insist on a proper scan?" Yes, you can set a quality rule: all four corners visible, text legible, no cropped edges, file readable. Put it in the request message and reject on legibility only, never on the candidate's device. A tool that checks legibility on upload saves a full day of back-and-forth.

"How long can I keep documents from candidates I did not hire?" Keep them no longer than needed for the purpose. The ICO's employment guidance and the UK GDPR storage-limitation principle (UK GDPR Article 5(1)(e)) mean you should set a retention period for unsuccessful applicants, document it, and delete on schedule. Many teams pick a short fixed period and tell candidates in the privacy notice.

"The name on the bank account is different from the passport. Is that automatically a problem?" No. It is a flag. Typical causes are a joint account, a recent name change or a shortened first name. Ask for confirmation and a corrected document if the pay file needs it.

Choosing a tool: questions to ask a vendor

1. Can I define, per role, which documents and which fields are required?
2. Does it extract fields from each document (names, dates, numbers) so they can be compared, or does it only store images?
3. Can I write my own comparison rules and decide what is a warning versus a block?
4. Does it log who reviewed a mismatch and what they decided?
5. Where is data stored, for how long, and can retention be set per candidate status?
6. Does it say clearly what it does not check? Be wary of any tool that implies a field match proves authenticity.

The last question is the important one. A date and name comparison is a consistency check. It is useful because most file problems are inconsistencies and omissions, but it is not an authenticity verdict, and an official register lookup shows what the register holds, not that the paper in front of you is real.

A workable process in five steps

1. Send a role-specific request listing documents, quality rules and a deadline.
2. Validate on upload: file readable, document type correct, not expired.
3. Run the six cross-checks; classify each result as pass, query or block.
4. For a query, message the candidate with the exact field in question, not a generic "please resend".
5. Record the decision, the date and who made it; schedule expiry reminders.

For agencies handling hundreds of files a week, this is where the time saving sits. See how this plays out for high-volume hiring and for agency file checks.

Where CheckFile fits

CheckFile is a validation layer rather than a collection portal. It reads the documents a candidate has submitted and compares the extracted fields: whether the file is complete, whether dates are current, and whether names, addresses and bank details agree across documents. Results go to a reviewer with the mismatch highlighted, and the decision stays with your team. If you run a staffing or recruitment business, see the temp staffing and recruitment solution, the HR onboarding solution, or pricing.

FAQ

What is candidate document collection?

It is the process of requesting and receiving identity, right-to-work, address, bank and qualification documents from applicants, usually through a portal, form or upload link. The goal is a complete file before the start date.

Is a collection tool the same as document verification?

No. Collection gathers and stores files. Verification compares what is in them: dates, names, numbers and addresses, within and across documents, and against official sources where one exists.

When should a recruiter ask for ID?

Ask only for what each stage needs. Many employers request right-to-work and ID evidence at conditional offer rather than at application, in line with data minimisation under UK GDPR.

Does a name mismatch mean the candidate is lying?

No. Marriage, transliteration, a missing middle name and joint accounts explain most name differences. Treat it as a query and ask for the legal form.

How much does candidate document collection cost?

Prices vary widely by volume and by whether the tool only collects or also validates. Compare per-file cost against the hours spent chasing and re-checking, and ask for the pricing basis in writing.