@cfxlabsinc/b2b-services
    Preparing search index...

    One of the org's related people, with whatever RouteFusion needs and CFX doesn't have. Carried on the candidate so the panel can offer a per-person fix without a second fetch.

    type RfRepresentative = {
        id: string;
        missing: string[];
        name: string;
        type: "CONTROL" | "BENEFICIAL_OWNER";
    }
    Index
    id: string
    missing: string[]

    RouteFusion-required fields this person lacks, as operator-facing nouns. Empty ⇒ sendable. Computed by missingRepresentativeFields, the SAME function the onboarding workflow's gate (toRepresentativeInput) uses — so the panel can never call an org ready that the workflow will refuse. This used to be an independently-hardcoded copy of the list, which is how an org came to show "eligible" while RouteFusion rejected the finalize for tax_number and residential_postal_code.

    name: string

    Best-effort display name — blank when the name is itself what's missing.

    type: "CONTROL" | "BENEFICIAL_OWNER"