Summary
If something in a verification result doesn’t look right, this article helps you:
Validate whether it’s a normal discrepancy or a genuine issue
Escalate genuine issues to Konfir for investigation
Re-verify (or use your fallback process) to keep your checks on track
Step-by-Step
1) Validate
Start by working out what kind of “wrong” you’re seeing:
What you’re seeing | What it usually means | Where to go next |
Verified data doesn’t match what was declared | The evidence may be correct, but differs from what the applicant declared (common and often explainable). | Start with Handling discrepancies. |
Verified data looks wrong (implausible, inconsistent with other proof, clearly incorrect) | There may be an issue in the underlying source record used to create the verification | Continue below to validate and report it. |
Note: Konfir reflects the evidence available from the data sources the applicant connected with minimal transformation.
We do not invent missing evidence or fill gaps. Where we standardise data (such as employer naming), it is for consistency and readability only.
How to validate
If you believe the verified data looks wrong, we ask that you validate this outside Konfir before escalating. This may involve asking the applicant for alternative evidence, checking with their employer, or referencing another trusted data source you use.
2) Escalate to Konfir
If you have a reasonable basis to believe the evidence is incorrect, contact Konfir so we can investigate. Please include:
Verification ID
Which activity is affected (employment or gap)
What looks wrong (one or two sentences)
Any supporting evidence you obtained (high-level is fine)
3) Re-verify
If the suspected incorrect activity appears to be supported by only one data source, you may re-submit a new verification and ask the applicant not to connect that source (where other sources are enabled and sufficient for your use case).
This is often the quickest way to remove misleading evidence while still completing the verification within Konfir.
If re-verifying isn’t suitable for your process, use your normal fallback route instead.