For new organisations or users creating an account with Konfir, there's now wording and logic to deter use of shared inboxes in lieu of personal work accounts.
New employer names in Konsole can now include both letters and numbers.
Verifications now automatically complete after 7 days if at least one activity is connected, or cancel if no activities are connected.
If an applicant actively declines consent in the Government Gateway flow, we'll now handle this gracefully and allow the user to try again if they wish.
If an applicant hasn't connected any available data sources and attempts to submit their verification request, they'll now see a new modal asking them to try one of the data sources again
Our new product, Respond, is now live for verifiers, enabling them to request and manage references on behalf of their applicants with ease.
Email addresses are now matched to an organisation based on their domain, helping identify the correct admin before approval.
Address fields now support any length, allowing more flexibility when entering details.
Users can no longer retry a verification if it was submitted without any connections.
Self employed applicants who do not use an accounting platform can now provide details on how they manage their finances, helping to capture additional insights.
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.