Summary
A Konfir verification is a structured, auditable record of someone’s employment and/or income, generated from trusted source data (with the applicant’s consent). It’s designed to replace manual processes like traditional referencing and document chasing.
If you’re new to Konfir, read this first, then move on to How verifications work (simple explainer) for the end-to-end journey.
What a verification is
A verification answers a simple question:
“What objective evidence is available to support this person’s employment and/or income history?”
Unlike traditional references, Konfir verifications are built from data retrieved from trusted systems (e.g. HMRC, banking, payroll) rather than relying on employer responses or subjective statements.
Types of verification you can run
Konfir supports different verification types depending on what you’re checking.
Client Help Center (Current)v1
Verification type | Designed to confirm | Typical use cases |
Employment verification | Employer(s), employment dates, and employment history coverage | Hiring and screening |
Income verification | Income totals/patterns, pay frequency, latest pay date (where available) | Affordability (renting/lending), income checks |
Employment + income | Combines employment history with income evidence | Higher confidence decisions |
The exact fields returned can vary depending on which sources the applicant connects and what those sources contain.
What’s included
Regardless of verification type, you’ll typically see:
Verification ID (for audit/reference)
Completion timestamp
Data sources used (e.g. HMRC, Open Banking, payroll, documents)
Alerts & insights (where applicable)
A structured timeline of the applicant’s activities (employments and sometimes gaps), depending on the requested period and declared activities
To see exactly how results are laid out in Konsole (and how they map to PDF/API), go to How to read a verification (Konsole and API).
What’s not included
Konfir is not a full background screening suite. For example, verifications do not include:
International checks - employment or income outside the UK
Other checks - DBS, Right to Work, etc.
Qualitative reference information - performance, character, reasons for leaving
If you need these checks, they should sit alongside Konfir in your process.
Why verifications matter
Teams use verifications because they are designed to be faster, more consistent, and more auditable than manual alternatives.
Common benefits include:
Speed: verifications can often be completed quickly once the applicant submits
Consistency: structured outputs are easier to review at scale than free-text references
Reduced admin: less chasing of employers and documents
Improved decision confidence: evidence is sourced directly from trusted systems rather than self-reporting
Verify vs Respond: how verifications are initiated
A “verification” is the output — Verify and Respond are the two ways you can initiate the workflow.
Verify: your team creates and sends verification requests outbound
Respond: your organisation routes inbound reference requests into Konfir for handling
If you’re not sure which you’re using, see Konfir products explained: Verify and Respond.
Next steps
Want the end-to-end journey? How verifications work (simple explainer)
Client Help Center (Current)v1
Ready to send one? Create a verification (Konsole / CSV / API)
Want to interpret outcomes confidently? Understanding verification results (start with How to read a verification)