The Swiss SME Hiring Checklist: Are You Actually Verifying Who You Hire?
A practical self-assessment for Swiss SMEs: how many of these identity-verification boxes can you honestly tick before a new hire starts work?
Ask any Swiss office manager or fiduciary how they confirm that a new hire is who their CV says they are, and you'll often get a shrug. Maybe someone glanced at a passport during the first coffee meeting. Maybe HR trusts the reference check. Rarely is there a documented, repeatable process — and rarer still is that process fast enough to survive a busy hiring season.
That gap matters. A mismatched name, an expired residence permit, or a doctored ID can turn into a compliance headache, a payroll error, or worse, months down the line. Below is a short self-assessment. Go through it honestly before your next hire signs a contract.
The Checklist
1. Do you check the actual document, not just a photocopy someone emailed you?
A scanned passport sitting in an inbox proves nothing about whether it's genuine, current, or tampered with. If your process stops at "we have a copy on file," you don't have a verification process — you have a filing cabinet.
2. Can you validate the document's check digits, not just eyeball it?
Passports, ID cards and residence permits carry a machine-readable zone (MRZ) with check digits defined by ICAO standards. Validating these deterministically catches errors and forgeries that a visual scan misses entirely. If nobody on your team is doing this, you're relying on how convincing a fake looks.
3. Do you compare the person in front of you (or on the call) with the document photo?
Identity theft doesn't require a fake document — sometimes it just requires someone else's genuine one. A selfie-to-document face comparison, with a basic liveness check to rule out a photo-of-a-photo, closes that gap.
4. What happens when something looks off?
An expiring permit. A name on the ID that doesn't quite match the application. This is where most informal processes fail silently — nobody follows up, or someone approves it anyway because chasing it feels awkward. A defensible process routes anything inconclusive to a human reviewer with the evidence side by side, rather than letting it pass by default.
5. Is there a record you could produce if asked?
If a regulator, auditor, or the candidate themselves asked "how did you verify this person's identity," could you produce a file? Not a memory of a conversation — an actual reviewable record with document data, the check result, and who signed off.
6. Does the verified identity data actually reach HR?
Even where checks happen, they often live in a separate vendor portal or a PDF nobody re-opens. Meanwhile HR retypes the same passport number into the staff file by hand. That's a second failure point, not a safeguard.
7. Do you know how long you're storing identity documents, and why?
Passport and ID images are sensitive personal data. Keeping them indefinitely "just in case" is a liability, not a precaution. A defined retention period, with the extracted fields kept as the record of the check, is what GDPR-style data-subject requests actually expect to find.
Where This Usually Breaks Down
Most Swiss SMEs don't skip identity checks out of carelessness. They skip them because the standard route — a dedicated KYC vendor, a per-check fee, a separate login, a PDF that lands in nobody's workflow — is disproportionate for a business hiring a handful of people a year. So the check gets done loosely, or not at all, and the paperwork trail is whatever survives in an inbox.
Building the Check Into the Hiring Flow Instead
Flitz's identity verification module answers each item on that checklist directly, because it sits inside the hiring process rather than beside it. From a recruitment application or an HR staff file, you send one link. The candidate photographs their passport or ID card on their phone, takes a selfie, and answers a short questionnaire — no app, about five minutes.
From there: Claude reads the document, MRZ check digits are validated deterministically, expiry and tamper signals are checked, and the selfie is compared against the document portrait with a liveness sanity check. An AI-led interview then asks your own base questions plus follow-ups specific to what the document raised — say, an expiring permit or a name mismatch — and judges each answer for consistency.
Only when every gate passes does the system auto-verify. Hard failures are rejected outright. Everything in between — the genuinely ambiguous cases — waits for a human reviewer, who sees every signal side by side rather than a bare "pass" or "fail."
When the candidate is hired, the verified passport data and document image flow straight into their HR Management staff file — no retyping. Identity images sit on private storage under a defined retention purge, while the extracted fields remain as the permanent record of the check, ready for a data-subject request if one arrives.
Run the Checklist Again
Go back through the seven questions above. If a "no" showed up more than once, that's not a reason to panic — it's the normal state for most small businesses handling hiring manually. The fix isn't more diligence from your team; it's a process where the hard boxes get ticked automatically, and the easy ones — like getting verified data into HR without re-entry — stop being manual work at all.