Overview
Konfir verification results support different workflows and risk models. There is no single pass or fail outcome. This article explains how teams typically approach the review process.
1. Check status
Before reviewing any data, start by checking the verification status.
Completed - the applicant has submitted all data and results are ready to review
Waiting for applicant - the applicant is still completing the journey; some activities may already show outcomes, but the verification is not final
Cancelled - the verification was not completed; retry or move to a fallback process
2. Review Results
Once a verification is complete, you can review the results at the activity level. For each relevant activity, compare the Declared vs. Konfir Verified data to see if they match. If they don't, you have a discrepancy and will need to make a decision about how you handle this.
a. Read Alerts & Insights
First check for Alerts & Insights - these visual flags highlight discrepancies and other issues that may require your attention - helping you identify issues quickly without manually inspecting every field.
Note: For API customers, Alerts & Insights can be customised according to your tolerances upon on request.
Employment Date Alert
Employment Date Alert
Checks for discrepancies between employment dates provided by applicants vs. those verified by Konfir - useful for spotting red flags such as undisclosed gaps.
Employer Name Alert
Employer Name Alert
This flags inconsistencies between the employer names reported by applicants and those verified by Konfir.
Undeclared Employment Check
Undeclared Employment Check
This check uncovers employments that were not declared by your applicant, indicating a potentially concealed employment history.
Company Trading Date Check
Company Trading Date Check
This check detects when an applicant has listed an employment with a company that was not trading for part, or all, of the employment period the applicant declared.
Reference Fraud Check
Reference Fraud Check
This alert checks the applicant's declared employer against known reference fraud houses in Konfir's Employer Database, alert you to a potentially fraudulent employment record.
b. Handle discrepancies
A discrepancy is a difference between declared information and returned data.
Discrepancies should be assessed based on whether the difference is material to the decision being made, rather than whether values match exactly.
Note: For help with missing or unexpected data, see Troubleshooting
Data field | Common causes |
Name | Preferred vs legal name Middle name present/absent Typos in declared name |
Dates | Estimated start/end dates Payment dates may differ slightly from contractual dates |
Employer name | Trading vs legal name Group entities Umbrella/agency payer vs end client Rebrands or mergers |
Job title | Internal vs external titles Missing (no payroll record) |
Income | Variable pay Multiple payers Irregular pay cycles |
3. Take Action
Once results have been reviewed, teams typically take one of the following actions:
proceed with the decision
request clarification from the applicant or additional evidence
use a fallback verification method
The appropriate action depends on your organisation’s policy, risk tolerance, and use case.
🤝 Let's chat - If you’d like help designing or refining your verification workflow, our team can advise based on experience across industries and use cases. Book a demo.