Skip to main content

How to read a verification

Learn how a Konfir verification is laid out and how to read the employment timeline, statuses and data sources.

Jacob avatar
Written by Jacob
Updated over 2 weeks ago

Overview

A Konfir verification is a structured summary of employment and/or income evidence. The same structure appears in Konsole, PDF exports, and API results - the format changes, but the information hierarchy stays consistent.


The structure of a verification

Use this table as a quick map of where key information appears and what it’s used for.

Component

The question it answers

Values

Verification status

Has the applicant submitted their verification?

  • Waiting for Candidate

  • Completed

  • Cancelled

Applicant details

Am I reviewing the right person and request?

Applicant identifiers and request details

Activity statuses

Which activities have strong evidence, partial evidence, or no evidence?

Each actvity has its own status:

  • Verified

  • Connected

  • Not Connected

Activity details

What data was returned, from which sources, and does it align with what was declared?

Employment dates

employer name

Job title

Data sources


Verification information

Verification status

This status describes whether the applicant has submitted their verification. It is not a measure of how many activities were verified.

Status

What it means

Waiting for Candidate

The applicant has not submitted their verification yet.

Completed

The applicant has submitted; results are available to review.

Cancelled

The verification ended before submission.

If a verification is cancelled, a reason may be shown (for example: timed out, rejected, duplicate, verifier cancelled, failed).

Applicant details

This section helps you confirm you are reviewing the correct person and request. Depending on your configuration and the available sources, you may see identifiers captured at request creation and/or returned by sources.


Activity timeline

The timeline organises all activities (typically employment and gaps) into a single chronological view, ordered from most recent (top) to oldest (bottom).

Activity status

Each activity in the timeline receives one status:

  • Verified - strong enough evidence was found to automatically verify the activity

  • Connected - some relevant data was found, but not enough to auto-verify

  • Not Connected - no usable evidence was found for that activity

For deeper definitions and recommended next steps, see Verification and activity statuses.

Activity details

When you expand an activity, you’ll see the evidence and fields returned for that activity. This typically includes:

  • Employment dates (start/end, or payment date range where applicable)

  • Employer name (standardised using Konfir’s Employer Directory/Database)

  • Job title (where available from sources)

  • Source logos indicating which sources contributed evidence (e.g., HMRC, payroll, bank, document processing)

  • Supporting documents where applicable (for audit/review, such as self-employment evidence)

This is where you compare what was declared in the request (and/or by the applicant) against what Konfir could evidence.


A simple review approach

If you’re new to reviewing verifications, a practical starting point is:

  1. Confirm the verification is Completed

  2. Scan the timeline and expand activities that are Connected or Not Connected

  3. Use your policy to decide whether evidence is sufficient or whether you need a fallback process

Did this answer your question?