Associated entity schema
The Associated Entity Schema contains information about entities associated with the main business or individual. It is used for tracking Ultimate Beneficial Owners (UBOs) and other related entities in Parcha’s case management system.
This schema is crucial for maintaining accurate records of related entities and ensuring compliance with KYB regulations.
Example
Field Descriptions
Case ID
Unique identifier for the case. Used to tie cases together when running workflows and can be used to link back to internal case management systems.
Self Attested Data
The name of the UBO entity
The registered name of the business
The incorporation date of the UBO entity, format YYYY-MM-DD
Whether or not the UBO Entity is a trust
The address of the business
The industry of the UBO entity
The tax identification number of the business
Whether or not the UBO entity is a business owner
The business ownership percentage of the business
The website(s) of the business
The description of the business
The relationship of the business to the main entity
Whether or not to skip KYB validation, for cases when it is a well-known company
Address Object
Primary street address
Secondary street address
City name
State or province
Postal or ZIP code
Two-letter country code
Validation Rules
incorporation_date
, if provided, must be in the format YYYY-MM-DD.business_ownership_percentage
, if provided, must be a number between 0 and 100.- If
website
is provided, it must be a valid URL or a list of valid URLs. description
is typically limited to a maximum length (e.g., 512 characters).
Validation Process
When submitting data for the Associated Entity Schema, the system performs several validation checks:
- Field formats are validated (e.g., date formats, URL formats).
- Field values are checked for validity (e.g., ownership percentage range).
- If
skip_validation
is false, additional KYB (Know Your Business) checks may be performed.
If any validation errors occur, the system will return a SchemaValidationError
with details about the specific fields that failed validation.
Usage in API
When using this schema in API calls:
- Provide as much information as available about the associated entity.
- Follow the specified formats for dates, URLs, and other structured data.
- Set
skip_validation
to true only for well-known entities where extensive KYB checks are not necessary. - Be prepared to handle validation errors and adjust your data accordingly.
API Documentation
Dive into our comprehensive API documentation to understand all available endpoints and features.