Bad quality master data increases the probability of missed hits; for instance, when matching customer names against names of politically exposed persons (PEP), relevant hits may be missed due to character encoding problems.

In banking systems, names are represented as sequences of binary digits (bits). The first name “Jim”, for instance, can be represented by three called ASCII characters:

"01001010" "01101001" "01101101".

Character encodings such as ISO-8859-1 and UTF-8 have different character representations, since ASCII cannot represent ä, ö, ü and other characters.

For example, the name “Jürg Näf” has different encodings in ISO-8859-1 and UTF-8.

"01001010" "11111100" "01110010" "01100111"

"01001010" "11000011 10111100" "01110010" "01100111"

"01001110" "11100100" "01100110"

"01001110" "11000011 10100100" "01100110"

The character encoding becomes compliance-relevant when a banking system uses simultaneously different types for legacy reasons. In this case, one encoding of “Jürg Näf” may match perfectly. However, if by mistake the UTF-8 encoding is assumed to be ISO-8859-1, 44% of the characters will not match (4 out of 9).

Generation of verifications for hits that differ by 40% or more, would obtain a significant number of false positives.

Complete Revision of the Federal Data Protection Act

The complete revision's draft of the Federal Data Protection Act is currently in political consultation. Data Protection is to be increased by giving people more control over their private data as well as reinforcing transparancy regarding the handling of confidential data.

Links: draft, report

Eurospider Information Technology AG
Schaffhauserstrasse 18
8006 Zürich

 

Cookies make it easier for us to provide you with our services. With the usage of our services you permit us to use cookies.
More information Ok Decline