Documentation Index
Fetch the complete documentation index at: https://docs.finpace.tech/llms.txt
Use this file to discover all available pages before exploring further.
Party and customer model
Core objects
Party
A party is any person or organization the platform needs to identify, evaluate, or relate to a banking arrangement. Examples:- natural person
- sole trader
- corporate entity
- beneficial owner
- authorized signatory
- director
- guarantor
Customer
A customer is the banking relationship representation used by Finpace for servicing, entitlements, product ownership, risk assessment, and communications.Relationship
Relationships connect parties to parties and parties to arrangements. Examples:director_ofbeneficial_owner_ofauthorized_signatory_forguarantor_forparent_of_group_memberrelationship_manager_for
Design rules
- a legal entity can exist before it becomes an active customer
- one party can participate in multiple customer contexts
- relationship validity is date-effective
- every high-risk relationship can carry enhanced due diligence attributes
- consent records are separate from party master data and are versioned
Required data clusters
Identity and profile
- names
- registration numbers
- tax identifiers
- incorporation details
- residency and jurisdiction markers
Risk and compliance
- PEP indicators
- sanctions screening outcomes
- customer risk rating
- KYB and KYC status
- periodic review dates
Contact and communication
- addresses
- phones
- emails
- preferred language
- channel preferences
Consent and preference
- marketing consent
- analytics consent
- open banking consent
- document and e-sign consent
- AI interaction consent where required by policy
Why this matters for AI
The AI runtime never infers authority from a conversation alone. Authority must come from:- authenticated actor identity
- represented customer context
- relationship rights
- arrangement-level entitlements
- policy evaluation