Skip to main content

Automatic Detection and Prevention of Duplicate Records

Erdi Yerebasmaz avatar
Written by Erdi Yerebasmaz
Updated over a week ago

What is the Duplicate Record Detection Function?

This function determines whether a newly entered record should update an existing user/organization record (e.g., after a donation, form submission, membership payment, or event participation) or create a new record.

Fonzip’s duplicate prevention system provides an intelligent comparison mechanism that minimizes errors when managing user/organization records. This is particularly important for large databases, ensuring correct user matching and preventing duplicate records.

How It Works

When a new user/organization record is entered, Fonzip compares it with existing records and decides whether to update an existing record or create a new one. This decision is based on the following criteria:

Mandatory Exact Match Fields:

The following fields must match 100% for an update to occur:

  • National ID / Tax Number

  • Email Address

  • Phone Number (GSM)

  • Membership Number

Additional Check:

  • Name Similarity: The similarity between the existing name and the new name is calculated. If the similarity is 80% or higher, the names are considered a match.

  • If all required matches occur, the existing record is updated. Otherwise, a new record is created.

  • Newly created records that could be duplicates are listed under Potential Duplicate Records.

Records that do not fully match are listed under Potential Duplicate Records in the Users & Companies menu for manual review. From this screen, records believed to belong to the same user/organization can be merged.

If records are not the same, the unique fields below must be corrected in both profiles to ensure no duplicates exist:

  • National ID / Tax Number

  • Email Address

  • Phone Number (GSM)

  • Membership Number

IMPORTANT WARNING

Records in this list may not be able to log in to Fonzip panels or access other Fonzip features.

Example:

If two different users share the same email address, the system cannot determine which record should gain access. To prevent unauthorized data access, these potential duplicate records cannot log into Fonzip.

Example Scenarios:

Existing User Info

New User Info

Result

User can be updated

Ali Velioglu, [email protected]

If name similarity <80%, create new user

Email differs → create new user

5551234567

5559876543

Phone differs → create new user

12345678901

98765432109

National ID differs → create new user

12345

(Empty)

Update can be made

Ali Veli

Veli Ali

If name similarity ≥80%, update can be made

New user → create new record

Ali Veli, [email protected], 5551234567

Mehmet Yılmaz, [email protected], 5559876543

New user → create new record

(Empty)

(Empty)

Update can be made

This system ensures data integrity by automatically detecting duplicates while allowing controlled manual review when necessary.

Did this answer your question?