Category: Islamic Names

  • When OFAC and the EU Spell the Same Name Differently, What Are You Liable For?

    It is a question experienced practitioners run into constantly but rarely see answered head-on. A person is designated by both OFAC and the EU. OFAC’s SDN entry romanizes the name one way; the EU’s Official Journal renders it another. Your screening system matches one string cleanly and scores the other below threshold. If a transaction slips through against the spelling you did not catch, what exactly is the liability – and is “we ran a standard edit-distance match” a defense?

    The short version: you are liable for the person, not the spelling, and the expectation clearly goes beyond raw edit distance. Here is the reasoning, with the supporting regulatory language.

    1. The obligation attaches to the designated person, not to a romanization

    OFAC’s prohibitions run against the designated person and that person’s property and interests in property. The name spellings, aliases, and other identifiers published in an SDN entry are aids to identification; they are not the legal definition of the target. That distinction matters because it means a spelling discrepancy between OFAC’s list and another regulator’s list is not, by itself, a shield. You cannot defend a missed match by pointing out that OFAC and the EU transliterated the underlying name differently, because your obligation was never keyed to a specific Latin string in the first place.

    This is reinforced by the strict-liability character of most OFAC prohibitions. Civil liability under IEEPA-based programs does not require intent or knowledge, so “the file we screened against spelled it differently” is not a recognized excuse. It goes to mitigation, not to whether an apparent violation occurred.

    2. Each list is authoritative in its own jurisdiction – so you screen against each as published

    OFAC, the EU, the UN, and OFSI transliterate Arabic, Cyrillic, Farsi, and Chinese names using different conventions. The same human being legitimately produces different Latin strings across the lists – Mohammed / Muhammad / Mohamed; Qadhafi / Gaddafi / Kadafi; hyphenated, spaced, or dropped “Al-” prefixes. Each list is, in its own jurisdiction, the authoritative legal instrument. A firm subject to more than one regime is therefore expected to screen against each list as published and to reconcile the fact that one person maps to several spellings across them. There is no regulator that publishes an explicit “you must reconcile our transliteration against the EU’s” rule – the expectation is inferred from how the obligations are framed and enforced, not from a single on-point statement.

    3. Does the expectation go beyond standard edit-distance matching? Yes – and OFAC has said so in substance

    Edit distance (Levenshtein, Jaro-Winkler, and similar) is treated as necessary but not sufficient. OFAC does not prescribe an algorithm, but its guidance and enforcement record point squarely at the failure modes that character-level distance handles poorly.

    In A Framework for OFAC Compliance Commitments (May 2, 2019), OFAC identifies deficient screening as a recurring root cause of apparent violations, and it specifically calls out the failure to account for alternative spellings of designated parties. Commentators summarizing the Framework note that OFAC warns screening software must, among other things, account for alternative spellings of prohibited firms or people – the Habana / Havana example is OFAC’s own. That is the closest thing to a direct statement that naive string matching is not enough.

    Why edit distance alone falls short in the cross-list transliteration scenario:

    • Cross-alphabet variance. Two valid romanizations of one name can sit at a large character-level distance from each other. “Qadhafi” versus “Kadafi” is a big edit distance but the same person. A threshold tight enough to suppress false positives will miss these; a threshold loose enough to catch them floods the review queue.
    • Phonetic equivalence. Names that sound alike but score as distant (the “Mohammed” / “Muhammad” family) are better bridged by phonetic logic (Soundex, Metaphone) or transliteration-aware normalization than by raw distance.
    • Name-order and segmentation. Arabic kunya/nasab structures, Chinese surname-first ordering, and dropped or added particles defeat token-by-token distance scoring.
    • Culture and script-specific normalization rather than a single global threshold applied to every population.

    4. The enforcement record: tool tuning for name variants is a cited deficiency

    Two settlements make the point concretely, and neither turns on willful conduct – both are about how the screening tool was configured.

    Apple / SIS (FNKSR, 2023 settlement). As part of resolving apparent violations tied to a designated Slovenian developer, OFAC highlighted remedial measures Apple undertook, including reconfiguring its primary screening tool to fully capture spelling and capitalization variations and to account for country-specific business suffixes, plus annual review of the tool’s logic and configuration. The remediation itself tells you what OFAC viewed as the gap: a tool that did not adequately capture variant spellings.

    JPMorgan Chase (FNKSR and Syria, 2018 Finding of Violation). OFAC found that the bank’s screening system, as configured over a multi-year period, failed to identify customer names with hyphens, initials, or additional middle or last names as potential matches to identical or similar names on the SDN List – and that staff did not escalate the red flags despite matching addresses and dates of birth. Again, the deficiency is in the matching logic and the procedures around it, not in the absence of screening.

    The through-line: OFAC does not penalize you for the existence of a spelling difference. It looks at whether a reasonable, risk-appropriate program – with fuzzy matching, phonetic and transliteration handling, and periodic tuning and testing – should have caught the target. A tool that “ran” but was mis-tuned to variant spellings is treated as a deficient program.

    5. How the liability actually resolves

    Put the pieces together and the liability is not “for the spelling” as such. It is for processing a transaction involving a designated person you should reasonably have identified. If your program screens against OFAC’s spelling with matching logic calibrated to catch reasonable variants, and a genuinely divergent EU transliteration was the only version that would have matched, OFAC’s inquiry is whether a reasonable, risk-based program should have caught it anyway. A documented, risk-based methodology – fuzzy plus phonetic and transliteration-aware matching, with periodic tuning and testing – is simultaneously the compliance expectation and, under OFAC’s Economic Sanctions Enforcement Guidelines, a mitigating factor if something still slips through.

    Bottom line

    No regulator publishes an express “reconcile our transliteration against the EU’s” instruction. But the combination of three things – strict liability, the principle that the obligation runs to the designated person rather than to a designated spelling, and OFAC’s explicit citation of alternate-spelling failures as an enforcement root cause – produces a clear expectation. Screen against each authoritative list as published, and use matching logic that goes beyond raw edit distance to account for transliteration, phonetic, and structural name variation. Edit distance alone, without transliteration and phonetic handling and risk-based tuning, would most likely be viewed as a deficient program.


    Source confidence. The Framework‘s treatment of alternate spellings as a screening root cause, and the Apple/SIS and JPMorgan Chase remediation details, are well supported by OFAC’s published materials and settlement summaries. The broader proposition – that this framework requires cross-list transliteration reconciliation – is inference drawn from the Framework, the enforcement record, and the strict-liability structure, rather than from a single on-point OFAC statement, because OFAC has not issued express guidance addressing cross-regulator transliteration divergence directly.

    Key references: OFAC, A Framework for OFAC Compliance Commitments (May 2, 2019), Appendix root-cause analysis; OFAC settlement with Apple Inc. under the Foreign Narcotics Kingpin Sanctions Regulations; OFAC Finding of Violation involving JPMorgan Chase (FNKSR and Syrian Sanctions Regulations, 2018).

  • The prompt:

    What are the most prominent sanctions screening challenges for Islamic personal names, and how are these addressed by current software and data solutions in the market? If there are notable challenges that are more prominent for male names, or female names, list and explain them. If there are notable challenges specific to transaction screening, list and explain them. Provide a source list (with URLs in parentheses) but do not produce citation markers within the response.

    The response:

    Prominent Sanctions Screening Challenges: Islamic Personal Names

    Screening Islamic personal names for sanctions compliance presents unique linguistic and cultural challenges. These difficulties often lead to high rates of “false positives” (incorrectly flagging innocent individuals) or “false negatives” (failing to catch sanctioned entities).

    1. General Screening Challenges

    These challenges apply broadly across Islamic naming conventions, regardless of gender.

    • Transliteration Variability (Romanization): The most significant challenge is converting names from Arabic script (or Persian/Urdu) into Latin characters for Western watchlists.
      • Vowel Ambiguity: Arabic script often omits short vowels. A name like “Mohammed” can be validly transliterated as Mohamed, Muhammad, Muhamed, Mahomet, etc.
      • Letter Substitution: Certain Arabic sounds have no direct English equivalent. The letter Qaf might be transliterated as ‘Q’, ‘K’, or ‘G’. For example, Qasem vs. Kasem vs. Gasem.
    • The “Mohammad Bias” (Frequency Noise): The name Mohammad (and its variants) is the most common given name in the world. In sanctions lists, it appears frequently as a first name or part of a patronymic chain.
      • Challenge: Simple exact-match or loose fuzzy-match logic often triggers thousands of false positives because the name is so ubiquitous.
    • Complex Naming Structures (The Chain of Names): Unlike the Western “First-Middle-Last” format, traditional Islamic names often follow a chain:
      • Ism: Proper name (e.g., Ali).
      • Nasab: Patronymic chain indicating lineage, often using bin or ibn (son of). (e.g., Ali bin Ahmed bin Saeed).
      • Nisba: Adjective indicating origin, tribe, or affiliation (e.g., Al-Masri = “The Egyptian”).
      • Challenge: Western systems frequently mistake bin Ahmed for a middle name or Al-Masri for a surname, failing to match when the components are reordered or when bin is dropped.
    • Honorifics and Titles: Titles are often embedded into the name string and can be mistaken for part of the name.
      • Examples: Sheikh, Hajji, Sayyid, Imam.
      • Challenge: If a sanctions list includes “Sheikh Yassin” and a customer is onboarded as “Yassin” (without the title), a strict system might miss the match. Conversely, treating “Sheikh” as a first name causes false alerts against anyone with that title.

    2. Gender-Specific Challenges

    While many challenges are shared, distinct issues affect male and female names differently.

    Challenges More Prominent for Male Names:

    • Use of Kunya (Technonyms): Men are frequently referred to by a Kunya—a name meaning “Father of [Eldest Son’s Name]”—rather than their legal given name.
      • Example: Abu Mazen (Father of Mazen).
      • Challenge: Sanctions lists often designate terrorists or political figures by their Kunya (nom de guerre). If a bank screens only the legal name (Mahmoud Abbas), they may miss the alias Abu Mazen.
    • Nasab Chains: The patronymic chain (bin X bin Y) is prevalent in male names and often leads to truncation errors where the grandfather’s name is mistaken for the surname.

    Challenges More Prominent for Female Names:

    • Teh Marbuta (Feminine Suffix) Transliteration: Many female names end with the Teh Marbuta character (ة), which denotes femininity.
      • Challenge: When transliterated, this can be written as an ‘a’, ‘h’, or ‘ah’. For example, Fatima vs. Fatimah. This inconsistency frequently breaks exact-match algorithms.
    • “Umm” (Mother of) Titles: Similar to the male Abu, women may be known as Umm [Son’s Name].
      • Challenge: Screening systems that do not account for “Umm” as a title rather than a name component may fail to match against lists using the legal name.
    • Maiden vs. Married Names: In many Islamic cultures, women traditionally retain their father’s family name after marriage rather than adopting their husband’s.
      • Challenge: Western compliance systems often assume a “maiden name” field is necessary or that a name change has occurred post-marriage. Incorrectly forcing a husband’s surname onto a female customer can lead to a data mismatch against sanctions lists that use her legal (father’s) surname.

    3. Transaction Screening Challenges

    Transaction screening involves monitoring payment messages (like SWIFT/ISO 20022) in real-time. Specific challenges for Islamic finance include:

    • Religious Terminology False Positives: Transaction description fields often contain religious terms that fuzzy matching algorithms mistake for names of sanctioned entities or groups.
      • Zakat / Sadaqah: Terms for charity. Can trigger false positives against entities with similar names (e.g., Al-Zakat Foundation).
      • Hajj / Umrah: Pilgrimage terms. “Hajj” is also a title (Hajji) often found in sanctioned names, leading to stops on payments simply labeled “Savings for Hajj.”
      • Eid: Festival names (e.g., Eid Gift) can trigger matches against individuals named Eid.
    • Compound Tokens in Institution Names: Islamic financial institutions often use compound names that get broken apart incorrectly.
      • Example: Islamic Bank of [Country].
      • Challenge: Generic words like “Islamic” or “Bank” are high-frequency. If the screening software does not treat the institution name as a single entity, it may flag the transaction based on partial matches with sanctioned banks containing those generic terms.

    4. Current Software and Data Solutions

    The market has shifted from simple “fuzzy matching” to more sophisticated AI and culture-aware approaches.

    • Culture-Sensitive Algorithms: Advanced software now includes specific logic for Arabic naming conventions.
      • Solution: These tools can identify and ignore “noise” words (like bin, al, abu) during matching or treat them as connectors rather than core name parts. They can also recognize that Mohammed and Mohd are equivalent.
    • Multi-Script Screening: Instead of relying solely on Latin transliteration, newer solutions screen names in their original Arabic script against the original script versions of sanctions lists.
      • Solution: This bypasses the transliteration ambiguity entirely (e.g., matching محمد directly to محمد).
    • Secondary Identifier Matching: To combat the “Mohammad Bias,” systems now weigh secondary data points (Date of Birth, Nationality, Location) much more heavily.
      • Solution: A match on the name “Mohammad Ali” is automatically discarded by the software unless the Year of Birth or Country also matches, reducing manual review volume.
    • AI & Entity Resolution: Machine learning models are trained on vast datasets of name variants to predict valid matches.
      • Solution: These models “learn” that Fatima and Fatimah are the same entity without needing hard-coded rules, and they can distinguish between a person named Hajji and a payment reference to a pilgrimage.

    Source List

  • This sort of summarization task, especially when you can rein it in by making AI share its work, and by not asking it make conclusions about the data it finds, is a fine use for Gemini.

    This was my prompt:

    In layperson terms, explain the structure of personal Islamic names. Include a section on the particles prevalent in such names. Explain the differences between male and female names. Include a section on the differences across countries, regions and cultures. If using linguistic terms like demonym or patronym, define them in parentheses after their first use. Also explain, by country, identify documents and how or when they are updated (e.g. when children are born). Include sources, but Instead of inserting citation markers throughout the response , provide a source list, including URLs in parentheses (as appropriate), at the end of the response. If multiple citations refer to the same base domain, refer to the base domain instead of the specific page.

    And this was its response – I knew the real basics (e.g. the 5 name parts), but having it lay out some of the details, like the national identity documents) was beyond my available time and abilities:

    The structure of Islamic names can seem complex to the outsider because, historically, they functioned more like a “chain of identity” than a simple “First Name + Last Name” format used in the West.

    In many parts of the Arab world, a person’s name tells a story about who they are, who their father is, and where they come from. However, this structure varies significantly depending on the country and local culture.

    The Classical Structure of an Islamic Name

    A traditional name is often built from five distinct building blocks. While modern official documents often shorten these, understanding the full chain is key to understanding the name.

    1. Ism (The Given Name):This is the personal name given at birth, equivalent to a “First Name” in English (e.g., Muhammad, Fatima, Omar).
    2. Nasab (The Patronymic):This indicates lineage. It is a chain of names linking the person to their ancestors, usually defined by the particle bin (son of) or binti (daughter of).
      • Example: Ahmad bin Omar (Ahmad, son of Omar).
    3. Kunya (The Paedonymic):This is an honorific name derived from the person’s eldest child. It is a polite way to address someone socially. It usually begins with Abu (Father of) or Umm (Mother of).
      • Example: If Ahmad has a son named Hamza, Ahmad might be called Abu Hamza (Father of Hamza).
    4. Laqab (The Honorific/Nickname):This is a descriptive name or title, often religious or related to a physical trait or virtue.
      • Example: Al-Rashid (The Rightly Guided) or Al-Siddiq (The Truthful).
    5. Nisba (The Demonym/Origin):This functions like a surname and indicates where the person is from, their tribe, or their profession. It almost always ends in an “i” sound.
      • Example: Al-Masri (The Egyptian) or Al-Baghdadi (The one from Baghdad).

    Common Particles and Their Meanings

    Particles are the small connector words that link the names together.

    ParticleMeaningContext
    Al / El / UlTheThe definite article. Used before tribe names, regions, or titles (e.g., Al-Saud = The Saud family).
    Bin / IbnSon ofConnects a man’s name to his father’s name (e.g., Saeed bin Ahmed).
    Binti / BintDaughter ofConnects a woman’s name to her father’s name (e.g., Aisha binti Ahmed).
    AbuFather ofUsed in a Kunya (e.g., Abu Bakr).
    UmmMother ofUsed in a Kunya (e.g., Umm Kulthum).
    Abd / AbdulServant ofAlways followed by one of the 99 names of God. Abdul is actually “Abd” + “Al” (The). (e.g., Abdullah = Servant of God).

    Differences Between Male and Female Names

    1. Linguistic Markers

    • The “ah” ending: Many female names end with a “soft h” or “a” sound, represented in Arabic by the letter Ta Marbuta.
      • Male: Jamil (Beautiful/Handsome) → Female: Jamila (Beautiful).
      • Male: Samir (Companion) → Female: Samira.

    2. Thematic Differences

    • Male names often convey servitude to God (AbdullahAbdulrahman), strength (Hamza – Lion), or historical religious figures.
    • Female names often refer to nature (Yasmin – Jasmine, Warda – Rose), virtues (Amal – Hope, Iman – Faith), or the wives and daughters of the Prophet.

    3. Marriage and Surnames

    • In strict Islamic tradition, women do not change their names upon marriage. A woman named Fatima binti Aliremains Fatima binti Ali for life, as she remains the daughter of Ali regardless of whom she marries. However, in some modern Westernized contexts or specific countries (like Turkey or parts of South Asia), women may adopt the husband’s surname legally.

    Regional and Cultural Differences

    While the religious roots are the same, naming conventions change drastically across borders.

    1. The Arab World (e.g., Saudi Arabia, UAE, Egypt)

    • Structure: Heavily relies on the Ism + Bin + Father + Bin + Grandfather + Family Name structure.
    • Legal IDs: Often drop the “Bin” in English fields but keep the four-name chain (Own Name + Father + Grandfather + Family).
    • Egypt specific: Often omits the “Bin” entirely. A person is simply named Ahmed Mohamed Ali (Ahmed [son of] Mohamed [son of] Ali).

    2. South Asia (Pakistan, India, Bangladesh)

    • Surnames: The “Bin” structure is rare. Instead, they use family surnames or caste/tribal names (Khan, Chaudhry, Patel).
    • Honorifics as Names: Titles often become part of the official name. Syed (lineage of the Prophet) or Sheikh may act as a first name or surname.
    • Naming: Names are heavily influenced by Persian and local languages (Urdu/Pashto) alongside Arabic.

    3. Southeast Asia (Malaysia, Indonesia)

    • Malaysia: Strictly follows the patronymic (name derived from father) system. Surnames are rare.
      • Format: [Own Name] BIN [Father’s Name].
    • Indonesia: Very fluid. Many people have only one name (Mononym), like Sukarno or Suharto. They do not strictly require surnames. A child’s name might be totally different from the father’s name.

    4. Turkey

    • Surnames: In 1934, Turkey mandated surnames for all citizens.
    • Turkification: Arabic names were adapted to Turkish spelling and pronunciation.
      • Muhammad became Mehmet.
      • Uthman became Osman.
    • Patronymics: The suffix -oğlu (son of) is common in surnames (e.g., Davutoğlu), but the “Bin” system is not used legally.

    Identity Documents and Updates by Country

    How governments capture these names varies, as does the timeline for updating them.

    Saudi Arabia

    • Document: National ID Card (Bataka Al-Ahwal / Hawiya).
    • Issuance/Update:
      • Birth: Parents must register the birth via the Absher digital platform after the hospital issues a notification. This generates a Family Register listing the child.
      • Adulthood: A separate photo ID card is issued to citizens usually starting at age 15 (mandatory by 15, optional from 10-14).

    Pakistan

    • Document: CNIC (Computerized National Identity Card).
    • Issuance/Update:
      • Birth: Parents register the child at the local Union Council to get a CRC (Child Registration Certificate), colloquially called the “B-Form.” This form assigns the unique 13-digit ID number immediately.
      • Adulthood: At age 18, the individual converts the B-Form into a full photo CNIC.

    Malaysia

    • Document: MyKad (Government Multipurpose Card).
    • Issuance/Update:
      • Birth: The National Registration Department (JPN) issues a Birth Certificate upon registration.
      • Childhood: From birth to age 12, children carry a MyKid (chip-based card without a photo).
      • Adulthood: At age 12, it is mandatory to apply for the MyKad (the primary photo ID), which must be updated again at age 18 to ensure the photo is current.

    Egypt

    • Document: National ID Card (Raqam Qawmi).
    • Issuance/Update:
      • Birth: Births must be registered within 15 days at the local Health Office to obtain a computerized Birth Certificate.
      • Adulthood: It is mandatory to obtain the National ID card at age 15 (lowered from 16 recently). This card is the primary proof of citizenship.

    Source List

    • Kingdom of Saudi Arabia National Portal (my.gov.sa): Information on “Register Newborn Service” and Civil Affairs updates.
    • Ministry of Interior – Egypt (moi.gov.eg): Regulations regarding Civil Registry and National ID issuance.
    • National Database and Registration Authority – Pakistan (nadra.gov.pk): Procedures for CRC (B-Form) and CNIC issuance.
    • National Registration Department – Malaysia (jpn.gov.my): Details on MyKid and MyKad application procedures.
    • Encyclopedia of Islam (Brill): Academic definitions of IsmNasab, and Nisba.
  • So, I was playing with Gemini to ask about Arabic name structure, and it came up with this term I had never heard of, so I decided to ask it what it meant:

    Nunation (called Tanween in Arabic) is a linguistic term that refers to adding an “n” sound to the end of a word.

    It is not written with the letter “N” (Nun). Instead, it is indicated by doubling the accent mark at the end of the word.

    1. What does it do?

    In standard grammar, it acts like the English word “A” or “An.” It marks a word as indefinite.

    • Kitab = Book
    • Al-Kitab = The Book (Specific)
    • Kitabun = A Book (General / Indefinite)

    2. Why is this in the video about names at the end of this response?

    This is the key difference between traditional male and female names in Classical Arabic grammar.

    • Male names typically take Nunation. Even though they are specific people, male Arabic names (like MuhammadZayd, or Khalid) are grammatically treated as “triptotes” (words that accept all case endings).
      • You say: “Muhammadun” (Nominative case).
    • Female names are “Diptotes” (Forbidden from Nunation). Female names (like FatimaZainab, or Maryam) fall into a grammatical category called Mamnu’ min al-sarf (forbidden from exchanging). They generally cannot take the “n” sound at the end.
      • You say: “Fatima-u” (NOT Fatima-un).

    3. Summary

    In the context of the video: Nunation is the “Un” sound you hear at the end of male names (Muhammad-un) that is grammatically stripped away from female names (Fatima-u).

    Sources

    • Council on American-Islamic Relations (cair.com)
    • Learn Arabic Online (learnarabiconline.com)
    • Transparent Language (blogs.transparent.com)
    • Wikipedia (en.wikipedia.org)

    Relevance of Video

    The video below provides a linguistic breakdown of the grammatical differences between male and female names in Arabic, specifically focusing on “Tanween” (nunation) and how endings change based on gender, which is useful for understanding the spoken nuances of these names.

    Male vs. Female Names (Tanween)

    [Ep. 11] Madinah Arabic – “Male vs. Female Names (Tanween)” – YouTube

    Saajid Lipham · 1.4K views