A borrower whose national ID / eIDAS shows "Thomas Müller", whose driver's license shows "Thomas Karl Müller", and whose prior KYC record shows "T K Müller" is not three different people. They are one person whose name has been rendered differently across three government databases — a phenomenon so common in EU identity infrastructure that any KYC / AML system that cannot handle it is not fit for purpose. The KYC / AML Verification Agent AI resolves conflicts, it does not simply report them.
The prior record conflict landscape
Prior KYC records records were designed to eliminate repetitive KYC / AML across financial institutions. In practice, they have created a new category of compliance complexity: the prior record conflict. A borrower with an existing prior KYC record at one financial institution presents to a new lender whose KYC / AML captures slightly different identity data — because the borrower's name has changed (marriage), because their address has changed (relocation), because the original prior CIP record was entered with a data error, or because different institutions use different transliteration conventions for the same name.
Each of these scenarios requires a different resolution. Name change due to marriage is a legitimate update requiring a supporting document, not a rejection. A data entry error in the original prior CIP record is a prior KYC correction process, not a borrower failing KYC / AML. An address update is a prior KYC modification, not an identity mismatch. Treating all conflicts as potential fraud — the default behaviour of binary KYC / AML systems — generates false positives that damage borrower experience and cost disbursements. Treating all conflicts as benign — the outcome of insufficient scrutiny — creates compliance exposure.
The KYC / AML Verification Agent AI classifies each conflict by type and applies the resolution pathway specific to that type.
The six conflict types and their resolution pathways
Name
Variant
Same person, different name rendering
national ID / eIDAS "Thomas Karl Müller" vs prior KYC "T K Müller". Fuzzy match score above threshold — same underlying identity. Resolution: auto-reconcile using the national ID / eIDAS name as primary (eIDAS-verified identity anchor is the most reliable identity document). Log the variant. No document request required. No borrower contact needed.
Name
Change
Different name — identity continuity via supporting document
national ID / eIDAS "Anna Schmidt" vs prior KYC "Anna Müller" (maiden name on the prior KYC record). Match score low due to surname change. AI classification: likely name change scenario (female borrower, prior KYC older than 2 years, maiden name pattern). Resolution: request marriage certificate or civil registry extract. Application held — not declined. Document receipt triggers CIP record update request on borrower's behalf.
DOB
Mismatch
DOB differs by 1–5 years — known government record issue
national ID / eIDAS DOB: 14/08/1984. prior KYC DOB: 14/08/1948. A 36-year discrepancy that is clearly a typo (84 vs 48 year inversion — common data entry error). AI classification: probable government data entry error, not identity fraud. Resolution: flag for manual review with discrepancy brief noting the likely error pattern. Reviewer requests DOB correction from original prior CIP record institution — does not reject borrower.
Address
Mismatch
prior KYC address outdated — borrower has moved
prior KYC address: Amsterdam. Current national ID / eIDAS address: Vienna. Name and DOB match perfectly. Resolution: auto-reconcile on identity (name + DOB match is sufficient for KYC / AML purposes). Initiate prior KYC address update on borrower's behalf as a post-KYC / AML compliance step — does not block the application. Log the address update for prior KYC registry submission.
Duplicate
prior KYC
Borrower has two prior KYC records — different record IDs
prior KYC hub returns two prior KYC records for the same national ID — one from 2018, one from 2021, with slightly different details. Resolution: use the most recent record as primary. Log both record IDs. Initiate deduplication request with prior KYC registry — a regulatory obligation that the KYC / AML AI handles automatically. Application proceeds on the more recent, complete record.
Identity
Mismatch
Identity data inconsistent — potential fraud or error — human review required
national ID / eIDAS name, passport name, and prior KYC name all show materially different surnames with no recognisable relationship (not transliteration, not initials, not name change pattern). DOB mismatch beyond known error ranges. Resolution: application held. Detailed discrepancy brief generated for KYC / AML officer. AML check triggered in parallel. No auto-resolution — human decision required at every step.
The conflict resolution outcome distribution
The conflict is the data — not the failure
A KYC / AML system that treats every prior record conflict as a rejection is not a compliance system — it is a risk-avoidance system that creates its own risk: the risk of rejecting creditworthy borrowers for bureaucratic data inconsistencies they did not create. The KYC / AML Verification Agent AI treats conflict as information to be classified and resolved, not as a binary blocker. The 2% of genuine identity mismatches are caught and escalated rigorously precisely because the 98% of recoverable conflicts are not treated with the same alarm.