Why is the middle name not always checked, even when entered?
Some document verification services do not accept middle names as a matchable field, even when the middle name is captured in easyAML.
Because the underlying document verification services don't accept middle names as a matchable field for some document types. easyAML captures the middle name and shows it on the record, but the field isn't always sent to the verifying authority, which can produce a "match without middle name" result that looks odd at first glance.
Where middle names aren't enforced:
- Australian driver's licences. The document verification check accepts given name(s) and surname but state authorities don't require an exact middle-name match for licence verification. A licence reading "John David Smith" verifies as "John Smith" if the firm only enters first and last.
- Passports. Middle names aren't compulsory on some international passports. The MRZ check uses the names exactly as they appear in the document; middle names are optional.
- Other ID documents. Same pattern - the document-issuer's data fields control what's compared.
What this means in practice:
- A "match without middle name" is expected behaviour, not a bug or a weakened verification. The first name and surname matched against the issuing authority's record; the middle name isn't part of the match key.
- The middle name is still stored in the easyAML record for completeness, and is visible on the customer profile.
- PEP, sanctions and adverse-media screening does include the middle name in the fuzzy-match logic - where a customer has the same first and last name as a PEP but a different middle name, the screen looks at the full name to assess match strength.
Where middle names matter most. Family-trust contexts where multiple individuals share first and last names but differ in middle name - particularly named beneficiaries. Make sure middle names are entered consistently across the family group to keep the audit trail clean.