Key concepts
Verification request vs verification result
A verification request is what you create and send to an applicant (via Konsole, CSV, or API).
A verification result is what you review once the applicant has submitted—shown as a structured timeline with activities, statuses, and supporting evidence.
Timeline and activities
A timeline is the chronological view of the applicant’s history for the requested period.
Each row in the timeline is an activity—usually an employment, and sometimes a gap.
Two kinds of statuses
Konfir uses two different “status” concepts:
Verification status (the overall request)
Activity status (each activity inside the timeline)
Data sources
An activity can be supported by one or more data sources (e.g., HMRC, Payroll, Open Banking). More sources typically increases confidence, but it’s normal for coverage to vary by role and time period.
Discrepancies, alerts, and insights
A discrepancy is simply a difference between what was declared and what sources show.
Alerts are rule-based flags that prompt you to look closer.
Insights add context (especially around gaps and income patterns). Not every discrepancy will trigger an alert.
Glossary (A–Z)
Term | Meaning in Konfir | Where to learn more |
Activity | A single item in the timeline (usually an employment; sometimes a gap). Each activity has one activity status. | Understanding Results → Verification & Activity Statuses |
Activity status | The status shown on each timeline activity: Verified, Connected, or Not Connected. | Understanding Results → Verification & Activity Statuses |
Alert | A rule-based flag highlighting something that may need attention (e.g., date mismatch, undeclared employment, employer name mismatch). Alerts are prompts, not decisions. | Understanding Results → Alerts, Insights & Discrepancies |
Connected | An activity status meaning there was some relevant evidence from at least one source, but it didn’t meet the rules for automatic verification. | Understanding Results → When an activity is Connected |
Data sources | Systems Konfir can use (with applicant consent) to retrieve evidence—commonly HMRC, Payroll, and Open Banking. | How Verifications Work → Data Sources Overview |
Declared data | Information provided by the applicant (or passed in by your system) about roles, dates, etc. This is what evidence is compared against. | Understanding Results → Declared vs Verified |
Discrepancy | A difference between declared information and what data sources show. Discrepancies are common and don’t automatically imply fraud. | Understanding Results → Handling Discrepancies |
Gap | A period with no employment activity visible for the requested timeline window. Can be declared by the applicant or implied by lack of evidence. | Understanding Results → Gaps & overlapping employments |
HMRC | A data source that provides official PAYE records (strong for historic coverage; can lag for very recent roles). | How Verifications Work → HMRC |
Insight | Additional context to help interpret the story (often around gaps and income patterns). Insights don’t “decide” anything; they provide context. | Understanding Results → Alerts, Insights & Discrepancies |
Konsole | Konfir’s UI used by clients to create requests and review verification results. | Account Setup / Creating Verifications |
Not Connected | An activity status meaning no usable evidence was found from any source for that activity period (even if an applicant started a connection). | Understanding Results → When an activity is Not Connected |
Open Banking | A regulated framework allowing applicants to share specific banking data via secure APIs. Konfir turns transaction history into structured signals (not raw statements). | How Verifications Work → Open Banking |
Payroll | A data source providing employer HR/payroll records (often includes job title and structured employment details where integrated). | How Verifications Work → Payroll |
Respond | Konfir workflow for handling inbound reference requests at scale via a standardised process. | Respond collection |
Review Transactions | An optional module (if enabled) allowing manual review of grouped Open Banking transaction evidence for Connected activities. | Understanding Results → Manual review (Open Banking) |
Timeline | The chronological list of activities used to show coverage across the requested period. | Understanding Results → How to read a verification |
Verification status | The overall request status (e.g., Waiting for Candidate, Completed, Cancelled) and—if cancelled—the reason. | Creating & Managing Verifications → Verification statuses |
Verified | The strongest activity status, meaning the activity is supported by good-quality evidence from trusted sources and aligns sufficiently for Konfir to treat it as verified. | Understanding Results → Activity statuses |
Verify | Konfir workflow where you send outbound verification requests to applicants. | Creating & Managing Verifications |