Location:  United Kingdom  (clear)

Authenticate Search Errors

Document type: Tech doc  
Associated product(s): Product name: AuthenticateImplementation: Web APIOS: Windows
Views: 181  |  Created: Last yearLast updated: Last year

Summary

Authenticate Pro search errors occur when the address or name data supplied to Authenticate Pro is insufficient to find a full name and address match. The actual error encountered may vary. A selection of errors is shown below (Figure 1):

Figure 1: Common Authenticate search errors

Solution

It may not be obvious at first glance what the issue with the address is. For instance consider the following address (name changed):

John Doe

37 Brenthurst Road

London

NW10 2DX

This address returns the ADDRESS NUMBER 01 CANNOT BE RESOLVED error as shown above (Figure 1) as it does not match any addresses in the Experian database. The problems with this address can be summarised as such:

a. There are flats at 37 Brenthurst Road registered on the voters roll

b. The person mentioned is not registered

c. A flat was not entered

In this case, the person being authenticated should be contacted to gather further details.

In the event that the error still occurs after further details have been collected, it is possible that the person cannot be authenticated via Authenticate Pro due to external factors. Such external factors may include:

a. The property not yet registered within the Authenticate Pro database (e.g. new builds)

b. The person having recently moved into a new residence

c. The person having recently entered the country

In these cases a paper-based authentication will be required.

Was this document helpful?

What can we do to improve this information?