Skip to main content

Konfir's Employer Database

How employer records support accurate verification outcomes.

Jacob avatar
Written by Jacob
Updated over 2 weeks ago

Overview

Employer names are one of the most common sources of inconsistency in employment verification. The same organisation may appear differently across systems, for example, as a legal entity name, trading name, payroll payer, abbreviated label, or bank transaction string.

Konfir's Employer Database helps us recognise these variations, building a true map of employers in the UK, powering match accuracy in the verification engine and delivering employer details (e.g. tradiing dates) as alerts & insights.


Where the Employer Database is used

The Employer Database is applied at specific points in the verification flow to support accuracy and consistency.

Creating a verification

When creating a verification, Konfir may present an employer selection dropdown.

This helps to:

  • reduce inconsistent or abbreviated employer entry

  • improve the quality of declared employer information

  • provide a cleaner starting reference for later processing

This does not prevent employers from appearing differently in connected data sources, but it reduces avoidable ambiguity introduced at the outset.

During processing

Within the Verification Engine, the Employer Database supports Klarity’s contextual analysis by providing reference information about known employer naming patterns. This helps Klarity:

  • match related evidence into one a coherent timeline

  • compare declared vs. verified employer names

  • eliminate duplicate activities caused by naming variations

During decisioning

During decisioning, the Employer Database is used to support certain alerts and insights that rely on employer reference data. For example, Konfir's trading date check (which highlights whether an employer was operating during a given period) can only function with the supplementary data that the Employer Database provides.

Did this answer your question?