Duplicate Candidates

Surfaces likely duplicate member records (mfi.member.duplicate.candidate) detected by matching names, identity documents and contact details. Resolving duplicates is core to KYC integrity - it stops one person holding multiple unscreened identities and keeps screening accurate. Staff review each candidate pair and merge or dismiss it.

Workflow

Open Duplicate Candidates under Compliance.
Review the kanban of suspected duplicate pairs.
Open a candidate to compare the two member records side by side.
Confirm a true duplicate or dismiss a false match.
Merge confirmed duplicates to consolidate the member identity.

Fields reference

Every field on this screen, drawn from the live data model.

Field	Type	Required	Description
Member A `member_id_a`	Link → mfi.member	Yes	Member A
Member B `member_id_b`	Link → mfi.member	Yes	Member B
Similarity Score `similarity_score`	Decimal	Yes	Similarity Score
State `state`	Choice: Pending Review, Confirmed Duplicate, False Positive, Merged	Yes	State
Has Message `has_message`	Yes/No	—	Has Message
Match Factors (JSON) `match_factors`	Long text	—	Match Factors (JSON)
Name Trigram `name_trgm`	Decimal	—	Name Trigram
DOB Match `dob_match`	Yes/No	—	DOB Match
Partial National ID Match `national_id_partial`	Yes/No	—	Partial National ID Match
Phone Match `phone_match`	Yes/No	—	Phone Match
Address Trigram `address_trgm`	Decimal	—	Address Trigram
Detected On `detected_on`	Date & time	—	Detected On
Reviewed By `reviewed_by`	Link → res.users	—	Reviewed By
Reviewed On `reviewed_on`	Date & time	—	Reviewed On
Reviewer Notes `notes`	Long text	—	Reviewer Notes

Actions & buttons

Buttons available on this screen and what they do:

Confirm Duplicate
Not a Duplicate
Merge...

Status lifecycle

Records on this screen move through these statuses:

Pending Review → Confirmed Duplicate → False Positive → Merged

Notes & rules

Matches on name, ID document and contact data.
Prevents fragmented, unscreened member identities.
Each decision is recorded for KYC audit.
Merging consolidates history under a single member record.

Technical model: mfi.member.duplicate.candidate · Record: Potential Duplicate Member Pair