To initiate the connection with HMRC, we need to first check the applicant is a UK taxpayer. We do this by sending information such as the National Insurance Number and Date of Birth to HMRC.

If we cannot find the applicant with the details provided, they will now be able to re-enter their NI Number and DOB in the Konfir UX.

When Open Banking is used as one of the data sources to verify an Employment on the Timeline, we now return the Latest Payment Date for that employment, alongside the Start Date and the End Date.

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.