KYC / Customer Identity Data Quality
BSAfreeValidate customer identity data — legal names, DOB, government IDs, address verification, KYC refresh, PEP flags, and duplicate detection per CIP/FATF/eIDAS requirements.
Checks included (10)
Customer Legal Name Present(legal_name)
Validates that the customer legal name field is non-null and non-empty. A complete legal name is required for all customer records under CIP regulations to establish and verify customer identity during account opening.
Customer Address Verified(address_verified)
Validates that the address_verified flag is true for all active customers. CIP regulations require financial institutions to verify the customer's physical address through documentary or non-documentary methods. An unverified address on an active account indicates an incomplete onboarding process.
Politically Exposed Person Flag Present(pep_flag)
Validates that the Politically Exposed Person (PEP) flag is non-null for all customer records. The PEP flag must be explicitly set to true or false; a null value indicates the PEP screening was not performed, which is a compliance gap for enhanced due diligence requirements.
Source of Funds Documented for High-Risk Customers(source_of_funds)
Validates that the source_of_funds field is non-null and non-empty for all high-risk customers. Enhanced due diligence requires documenting the origin of customer funds to detect potential money laundering, terrorist financing, or other illicit financial activity.
Government ID Number Format(gov_id_number)
Validates that the government-issued identification number conforms to expected formats based on ID type: SSN must be 9 digits (NNN-NN-NNNN or NNNNNNNNN), passport must be 6-9 alphanumeric characters, and driver license must follow state code plus number pattern. Proper ID format is essential for identity verification under CIP requirements.
Customer Nationality ISO Country Code Valid(nationality)
Validates that the customer nationality field contains a valid ISO 3166-1 alpha-2 country code (two uppercase letters). Standardized country codes are required for sanctions screening, FATCA/CRS reporting, and cross-border regulatory compliance.
Customer Status Valid(customer_status)
Validates that the customer status field contains one of the allowed values: active, dormant, suspended, closed, or pending_review. Invalid or unexpected status values can break downstream processes for transaction monitoring, regulatory reporting, and account lifecycle management.
Date of Birth Valid and Customer is Adult(date_of_birth)
Validates that the customer date of birth is a valid date, is not in the future, and that the customer is at least 18 years of age. CIP regulations require date of birth collection, and most financial products require the customer to be a legal adult.
KYC Review Date Current(kyc_review_date)
Validates that the KYC review date is not stale based on the customer risk rating. High-risk customers must have KYC refreshed within 1 year, medium-risk within 2 years, and low-risk within 3 years. Stale KYC reviews expose the institution to regulatory risk and may indicate gaps in ongoing due diligence.
Duplicate Customer Detection(legal_name)
Flags potential duplicate customer records by identifying rows with the same legal name, same date of birth, and similar address within the customer base. Duplicate records can lead to fragmented transaction monitoring, missed suspicious activity, and regulatory reporting failures.