@cfxlabsinc/b2b-services
    Preparing search index...
    RelatedPerson: Simplify<
        Omit<
            SelectRelatedPerson,
            | "id"
            | "externalId"
            | "customerId"
            | "organizationId"
            | "status"
            | "data"
            | "deletedAt",
        > & Omit<
            SelectRelatedPerson["data"],
            | "verificationProfileId"
            | "personReferenceId"
            | "routeFusionRepresentativeId",
        > & {
            deletedAt?: Date;
            id: SelectRelatedPerson["externalId"];
            status: SelectRelatedPerson["status"];
        },
    >

    A person related to an organization for KYB purposes — either a person who controls the business (CONTROL) or a beneficial owner (BENEFICIAL_OWNER).

    The AiPrise linkage ids (verificationProfileId, personReferenceId) and the RouteFusion representative id (routeFusionRepresentativeId) live on the DB row's data jsonb but are internal-only and stripped from this domain object, so they are never surfaced via the API.