Why this matters

Before normalisation, the same role could arrive under dozens of different labels — across languages, abbreviations, casing, and registry-specific conventions. This made it harder to:

Match and process cases consistently, since logic had to account for every possible spelling and variant.
Filter by role reliably (for example, "show me all UBOs"), since a UBO might be labelled UBO, Beneficial Owner, Dueño Beneficiario, or Bénéficiaire Ultime.
Onboard new registries, since each new source introduced its own role vocabulary that had to be learned and handled — a recurring, manual task.

Role Normalisation removes this overhead by resolving every raw role to a known, standard value.

How it works

For each related person, AiPrise returns both the original role from the registry and the normalised role.

role – The raw role exactly as provided by the registry source.
normalised_role – The standard AiPrise role the raw value maps to.

This means you keep full visibility into the source data while being able to build your logic against a stable, predictable set of values.
JSON

related_persons:
 [{
  "name": "Jane Doe",
  "role": "Administrador Único",
  "normalised_role": "DIRECTOR"
}]

Normalised Roles

📘 Normalised roles: Consistent person roles across registries and languages

1. ULTIMATE_BENEFICIAL_OWNER — Individual who ultimately owns or controls the company, typically through significant ownership or influence.
2. CONTROLLING_PERSON — Person with effective control over the company through management authority, ownership rights, or executive responsibility.
3. DIRECTOR — Board member or senior official responsible for company governance, oversight, and strategic decisions.
4. LEGAL_REPRESENTATIVE — Individual or entity legally authorised to act, sign, or represent the company in official, financial, or compliance matters.
5. SHAREHOLDER — Individual or entity holding shares or financial ownership in the company.
6. EMPLOYEE — Person associated with the company in an operational or administrative role without ownership or governance responsibilities.
7. UNKNOWN — Roles that do not fit standard categories or are ambiguous and require manual review.
   

Examples