Person Resource Advanced
Direct person record management for specialized scenarios
Person records store individual identity data for investors, trustees, directors, signatories, and beneficiaries. Most person management occurs through BizEntity operations which handle complete investor setups with relationship management and deduplication. Direct Person endpoints support bulk imports, cross-entity queries, and data migration scenarios.
Usage Notes
When
- Manage person records independently of BizEntity for bulk imports or data migration
- Query person details for cross-entity relationship verification
- Create standalone person records for later association with multiple entities
Requirements
- Valid Bearer token with person permissions
Notes
- Person records typically created via BizEntity operations; use direct endpoints for specialized scenarios
- Same
externalPersonIdacross multiple BizEntity operations reuses ONE person record (deduplication) - Person-to-BizEntity relationships managed through BizEntityParty with role classifications
- Cannot delete persons with active BizEntityParty relationships
Available Endpoints
Core Operations
Core Data Transfer Objects
Use Cases & Scenarios
Most person management occurs through BizEntity operations. Use direct Person endpoints for bulk imports, cross-entity updates, standalone KYC collection, or data migration scenarios.
→ See BizEntity Overview for standard entity operations
Business Rules & Constraints
BizEntity Integration & Deduplication
- Automatic Deduplication: When creating persons through BizEntity operations, the system automatically deduplicates based on
externalPersonId - Reuse Pattern: Same
externalPersonIdin multiple locations within a BizEntity request creates ONE person record - Multi-role support: Person records link to BizEntity through BizEntityParty relationships with defined roles (investor, signatory, controller, beneficial owner)
- Flexible ownership: Multiple entity relationships supported with different capacity types and shareholding percentages
Validation & Compliance Standards
- Age validation: Date of birth validation ensures logical age restrictions for investment eligibility
- Identification requirements: Passport, driver's license, and other ID validation for KYC/AML compliance
- Tax residency: Support for up to three tax jurisdictions with TIN tracking and reporting requirements
- Compliance workflows: Significant person changes (name, identification) trigger entity validation and compliance update workflows
Referential Integrity & Management
- Deletion restrictions: Person records cannot be deleted if active BizEntityParty relationships exist
- External integration: ExternalPersonId supports third-party system integration and idempotency
- Contact management: Communication and Address records link through entity relationships, enabling multiple addresses and communications per person