Resolved a problem where some applicants were stuck on the payroll consent page due to the spinner not displaying on the continue button.

Applicants now see a confirmation screen when their bank has been successfully connected.

Income verification now only returns HMRC employments that are current or have income in the current tax year.

The sign in page has been refreshed with an improved design for a cleaner and more consistent experience.

Resolved a problem that caused some applicants to get stuck after submitting their address in the payroll information step.

Applicants are now only asked to provide a single address, with the option to re-enter it if needed.

We’ve made performance improvements to the applicant journey, reducing load times and making the process quicker from start to finish.

Users can now view monthly income amounts directly in Konsole for easier review of verification results.

Applicants who decline consent in the HMRC flow can now retry straight away, with the option to provide a reason and reconnect, instead of waiting for the previous delay.

First-time users now see a guided product tour in Konsole to help them get started with employment verification.

We now allow applicants to provide their National Insurance Number up to 2 times before taking them to the next data source if we cannot successfully match it with the Payroll provider.

If an applicant can't, or doesn't want to connect to HMRC, we will ask them what happened.

If the applicant selects "I don't want to connect it" or "other", we'll now show them an extra page that provides additional information on why the HMRC connection is useful & security at Konfir.

We identified that data reported by some employers to HMRC were duplicated. This was particularly common among NHS Trusts. We've now released functionality to merge any duplicate employments from the same employer from HMRC.

We've rolled out a suite of checks on National Insurance Number to maximise data connectivity and conversion rates.

If an invalid National Insurance Number is provided, we'll clear the provided value and ask the applicant to re-enter the correct one in our journey.

We've added 6 banks into our Bank Selection screen that are not supported by Open Banking yet.

When an applicant selects one of these banks, they'll be taken to the next available data source to ensure there are no deadends in the journey.

When creating a verification via API, you can now send through a custom ID per activity.

We'll return the custom ID via the TImeline endpoint to help match verified data with data in your system.