Overview
Occasionally, a verification may contain data that looks wrong - for example:
an employer that seems unrelated
dates that appear impossible
Before escalating, it’s important to identify what kind of issue you’re seeing.
1) Identify the issue
What it might be | What it means | Where to go |
A discrepancy (most common)
| Data differs from what was declared, but may be explainable (names, dates, patterns) | |
Missing data | Data field is blank or missing | |
Incorrect Result (least common) | Data looks implausible even after basic sense-checking | Continue below |
2) Validate the issue
Before contacting support, sense-check whether the issue could be explained.
Examples of clear red flags:
an employer clearly unrelated to the applicant’s context
data directly contradicted by other evidence
Sources for validation may include:
applicant clarification
employer confirmation
alternative internal evidence
If the issue remains unexplained, escalate.
3) Escalate to Konfir
If you believe the evidence is genuinely incorrect, contact Konfir Support and include:
Verification ID
Affected activity/employment (including employer name shown)
What looks wrong (1–2 sentences)
Affected fields (e.g. dates, employer name, income, job title)
Any relevant context (high level only)
Tip: Avoid sending personal data where possible. The Verification ID and activity context are usually sufficient.
Keeping your process moving
Teams handle exceptions differently. If needed, proceed using your standard fallback process while we investigate.