Person matching

Whether you are checking that the account owner is rightfully representing the company with the Legal authorization task or you are automatically adding missing UBOs with the Add UBOs from official register task, Ondorse is matching persons in the background.

Can Anderson Paul, with no date of birth, represent a company that has a Paul Thomas Anderson, born on June 26, 1970, listed as a director ?

Unambiguous matches

These are the easy cases. Two persons are an unambiguous match when:

• Their first names match, and
• Their family names match, and
• Their date of birth is coherent.

Close matches

To reduce false negative matches, Ondorse introduces a refined notion of a close match. This occurs when two persons look the same but are not an unambiguous match.

Two persons are considered a close match if:

• They are an unambiguous match, or
• When inverting the first names with the last names of the first person, the two persons are an unambiguous match, or
• When splitting the first names correctly, the two persons are an unambiguous match and their birthdate is explicit, or
• When splitting the last names correctly, the two persons are an unambiguous match and their birthdate is explicit, or
• When removing middle names (the first part of the last name), the two persons are an unambiguous match.

Additionally, fuzzy matching is employed to account for possible spelling mistakes in first or last names when two persons are close but not exact matches.

📘

Your call

Using Ondorse close matching functions is a setting. You can activate it or not.

Birthdate coherence

We also ensure that birthdates are coherent. For example:

• Two empty birthdates are acceptable.
• If one birthdate is empty, it is also acceptable.
• However, if one birthdate has a day, month, or year that conflicts with the other, it is considered a mismatch.
• Partial dates (e.g., 5/1994) will match full dates (e.g., 14/5/1994) if the month and year are coherent.

---

Examples