Five Identity Verification Mistakes Swiss SMEs Make When Hiring
Checking that a new hire really is who their CV says is often skipped, outsourced, or left as a forgotten PDF. Here are the mistakes that cost Swiss SMEs time, compliance risk, and trust.
Verifying that a candidate is who their CV says they are sounds like a formality. In practice, it's one of the most inconsistently handled steps in Swiss SME hiring — done thoroughly for some roles, skipped entirely for others, and almost never filed anywhere useful. Below are the mistakes that show up again and again, why they happen, and what they actually cost a business.
Mistake 1: Treating identity checks as optional for "low-risk" hires
Many SMEs only run identity or background checks for finance roles, management positions, or anyone handling client money. Everyone else — warehouse staff, interns, part-time support — gets hired on the strength of a CV and a good interview.
This happens because a formal check usually means a separate KYC vendor, a per-check fee, and someone remembering to initiate it. For a CHF 22/hour role, that friction rarely feels justified.
The cost shows up later: a staff file built on an unverified name, a permit that was already expired at the start date, or — in rarer but real cases — someone who simply isn't who they claimed to be. Once that person is on payroll and has building access, unwinding it is far more expensive than checking upfront would have been.
The fix: when verification is built into the hiring flow itself rather than bolted on as an external step, the marginal cost of checking every hire drops close to zero. One link sent from the application page, five minutes on the candidate's phone, no app to install — there's no longer a reason to reserve it for "important" roles only.
Mistake 2: Relying on a human glancing at a passport photo
A common middle ground is the HR person eyeballing a passport or ID card during onboarding — checking that the photo looks roughly like the person and the name matches the contract. This feels like due diligence, but it isn't a real check. Humans are bad at matching unfamiliar faces, worse at spotting a tampered document, and have no way to validate the machine-readable zone (MRZ) check digits that confirm a document is internally consistent.
This mistake happens because nobody has given the HR team a better tool — not because they're careless. A visual glance is simply what's available.
The cost is a false sense of security: a document that looks fine to the eye but fails a structural check, discovered only if something goes wrong later.
The fix: automated document reading with ICAO MRZ check-digit validation, expiry checks, and tamper checks does what a glance can't — and it does it the same way every time, regardless of who's doing onboarding that week.
Mistake 3: Letting inconclusive results slide through
When a check does flag something — a selfie that's a borderline match, a permit expiring in three weeks, a name spelled slightly differently on the application versus the document — the easiest thing to do under time pressure is wave it through. The hire is scheduled to start Monday; nobody wants to be the reason it slips.
This is where "automated" verification tools can quietly fail: if the system only ever produces a pass, inconclusive cases get treated as passes too.
The fix: a verification flow that treats "inconclusive" as its own category, not a soft pass. Hard failures reject outright; anything uncertain — including selfie comparisons that don't clear a liveness sanity check — routes to a human reviewer with the document and selfie side by side, so a person makes the actual decision instead of an algorithm making it silently.
Mistake 4: Stopping at the document instead of asking about it
A document can be genuine and still raise a question: a residence permit expiring soon, a name on the ID that doesn't quite match the job application, a date of birth that's off by one digit between CV and passport. Most checks stop at "is this document real" and never follow up on what it actually says.
This gap exists because asking a candidate about a discrepancy means a reviewer has to notice it first, remember to raise it, and frame a question that doesn't feel like an accusation.
The fix: an AI-led interview that combines the employer's own base questions with follow-ups generated specifically from what the document raised, judging each answer for consistency rather than leaving the discrepancy buried in a file nobody reopens.
Mistake 5: Filing the result as a PDF no one can find again
Even when a KYC check is done properly, the output is often a report from an external vendor's portal — a PDF emailed once, saved somewhere, and disconnected from the staff record it was supposed to support. If a GDPR data-subject request arrives, or a fiduciary asks for proof a check happened, someone has to go hunting.
This happens because the verification step and the HR record live in two different systems that were never designed to talk to each other.
The fix: when the check is requested directly from the Recruitment application page or the HRM staff file, the result isn't a detached document — it's part of the hire. On hire, the verified passport data and document image become the staff file itself. Identity images sit on private storage with a retention purge; the extracted fields remain as the permanent record of the check, so if a data-subject request comes in, there's an actual answer.
The pattern behind all five
None of these mistakes come from negligence. They come from identity verification being treated as a separate chore — a vendor to call, a PDF to save, a judgment call to make under time pressure — rather than a native part of the hiring flow. Building the check into the application and staff-file process, with a human reviewing anything that isn't clean, turns an occasional formality into a consistent, auditable habit.