FUZZY matching guidance ARCS transaction matching
Summary:
Guidance on how to perform fuzzy transaction in ARCS TM
Content (required):
Currently, there are no identical or consistent matching refences in both sources. However, part of the information is embedded in the reference section (couple of examples below). We have cleansed the data as much as possible (eg removing spaces, special characters, using trailing characters, etc) but there’s still a large volume of unmatched transactions. Appreciate if you could provide some guidance on how these sort of transactions can be matched off.
Example1:
Source 1: MRTHOMASLONDON135554628LONDON
Source 2: MRTHOMAS13555628LOND
Example2:
Source 1: MRJOHN139105678MAGUIREMAGUIRE
Source 2: MRJOHNMAGU139105678MAGUIRE
Version (include the version you are using, if applicable):