Data Model
The Party Microservice uses the NoSQL data model to manage party information. NoSQL is the standard language to manage unstructured data. A NoSQL database can be used to insert, update, and retrieve database records. A NoSQL database is more scalable and provides superior performance.
In the NoSQL data model, the KEY_PARTITION attribute is available to store unique records in the database.
To view the data model of different entities that are associated with Party Groups, click here.
The Data Model of Party Microservice contains the following attributes:
A bank or a financial institution may deal with different persons or entities beyond customers, such as Associated Party, Supplier, and Agent. Their details are also captured and maintained in the Party microservice. A person or entity can have multiple roles in relation to the bank. They can be a customer but also an associated party of another customer. For example, Power of Attorney. Party Roles entity captures the information of the role that a party has in relation to the bank and the status of the respective role.
|
Entity Attribute |
Type |
Description |
Example |
|---|---|---|---|
|
Role Type |
Enum-Dynamic |
Defines the type of relationship between the party and the bank. |
Supplier, Agent, Contractor, Staff |
|
From Date |
Date |
Role Effective date for the party. |
01-Feb-20 |
|
Status |
Enum-Dynamic |
Current status of the role for the party. |
Active, Inactive, Prospect |
|
Exit Date |
Date |
Date from which the role is no more effective for the party. |
01-Feb-22 |
|
Exit Reason |
Text |
Reason for the role that is no more effective for the party. |
Staff - Resignation |
|
Comments |
Text |
Free text to store any comments by the user. |
|
Reference data for defining the party roles, as required by the implementation. All defined Role types are required to map to a pre-set of Role Classifications released from the product.
|
Entity Name |
Type |
Description |
Example |
|---|---|---|---|
|
Role Classification |
Enum |
Classification of the type of the role. |
Refer below for the List |
|
Description |
Text |
Free text to store any description for the role type by the user. |
|
|
Role Classification |
Description |
|---|---|
|
Customer |
An individual or an organization who has availed or availing the services of the bank. |
|
Associated Party |
An individual or an organization who is related to the party with the role as the customer of the bank. The actual relationship between the party needs to be recorded by using the Party Relationship entity. |
|
Staff |
An individual who is employed with the bank but not limited to contractors and trainees. |
|
Agent |
An individual or an organization who acts as an agent to sell the products of the bank. For example, Insurance Agent of the bank. |
|
Representative |
An individual who represents or acts on behalf of an organization with the role of customer. Formerly External User in Transact. |
|
Supplier/Service Providers |
An individual or an organization who sells their products to the bank or provide services to the banks. |
Customership is a sub-entity under Party Roles that captures the details of the branch, division, and sub-division through which the Party is associated with the financial institution. Customership details are captured for each role of a party. The following table explains how the data can be captured in the Customership entity.
|
Party |
Party Role |
Customership
|
Details |
|||||
|---|---|---|---|---|---|---|---|---|
|
Role Type |
Role Status |
Legal Unit |
Responsible Unit 1 |
Responsible Unit 2 |
||||
|
Sub-Legal Unit |
Rel. Officer |
Branch |
Rel. Officer |
|||||
|
John |
Customer |
Active |
ABC Bank |
Finland |
N/A |
Finland. Br.101 |
Officer. A |
John's savings accounts are held with the ABC Bank branch in Finland, where he currently resides. |
|
Sweden |
N/A |
Sweden. Br.99 |
Officer. Z |
John's mortgage is with ABC Bank branch in Sweden, where is hails from. |
||||
| ABC Insurance |
Sweden |
N/A |
Sweden.Br.99 |
Officer. W |
John has insured his house also with ABC Insurance company. |
|||
|
Associated Party |
Active | ABC Bank |
Finland |
N/A |
Finland. Br.50 |
Officer. C |
John is the sole proprietor of his café and the account of the café is also maintained with another branch of the ABC Bank Finland. Hence, John is marked as an associated party. In this case, it is purely optional for a relationship officer to be nominated and if needed, it is possible as per our model. |
|
| ABC AMC |
UK |
Officer.D |
|
|
John is a nominee for the assets of his wife Mary that is managed by a subsidiary ABC Asset Management company in the UK. In this case, there is no branch-level setup for the subsidiary. |
|||
|
John's Café |
Customer |
Active |
ABC Bank |
Finland |
N/A |
Finland. Br.50 |
Officer. C |
|
|
Mary |
Customer |
Active | ABC AMC |
UK |
Officer.D |
|
|
|
|
Attribute Name |
Type |
Description |
Example |
|---|---|---|---|
|
Company Legal Unit |
Enum-Dynamic |
Legal Unit of the bank to which the party is associated with. |
ABC Bank, ABC Insurance. |
|
Status |
Text |
Specifies the current lifecycle status of customership as per the context of a specific bank legal unit |
Active/Inactive |
Responsible Unit is a collection as a part of Customership Sub-Entity.
|
Attribute Name |
Type |
Description |
Example |
|---|---|---|---|
|
Responsible Unit Type |
Enum-Dynamic |
Specifies the type of unit with which the party is associated with. It is possible to define the granular level of Responsible Unit Types as required by the Client implementation. |
Country, Branch, Division |
|
Business Unit |
Enum-Dynamic |
The ID of the business unit under the respective Responsible Unit Type. For example, Name/ID of the Branch or Sub-Division |
Branch.101, Division.Finance |
|
Relationship Officer |
Enum-Dynamic |
Specifies the bank employee responsible for managing the relationship and providing service to the party. |
Officer. A, Officer.100100 |
|
Start Date |
Date |
Date from which the party is associated with the respective responsible unit. |
|
|
End Date |
Date |
Date until which the party was associated with the respective responsible unit. |
|
Party Legal Status captures information about the legal status of the party (from external sources or legal documents) as this can have an impact on how its relationship with the financial institution.
|
Attribute Name |
Type |
Description |
Example |
|---|---|---|---|
|
Legal Status Type |
Enum-Dynamic |
The legal status of the party |
Liquidation |
|
Legal Status Country |
Enum-Dynamic |
Country in which the legal status was imposed. |
US |
|
Effective From Date |
Date |
Date from which the legal status is effective. |
|
|
Effective To Date |
Date |
Date until which the legal status is effective. |
|
|
Change Reason |
Text |
Reason for change in the legal status of the party. |
Dissolution of the company |
Party Observation entity allows the bank to document important observations noticed by bank users related a party, that may require attention or restrict the management of the party. For Example – Under Recovery, Adverse Media
|
Attribute Name |
Type |
Description |
Example |
|---|---|---|---|
|
Observation Type |
Enum-Dynamic |
Type of Observation of the party. |
Adverse Media |
|
Date |
Date |
Date of observation |
|
|
Detail |
Text |
A detailed description of the observation. |
Adverse Media report published |
|
Reason |
Text |
Any explicit reason for the observation. |
The Customer has married a mogul on the OFAC list |
|
Source |
Text |
Reference to the user who have recorded the observation. |
The ABC Newspaper |
Tax Details entity captures the details about taxation for a specific person or organization. It identifies the tax eligibility of a party in different countries and for different tax types. A person or organization may be taxable in multiple countries at one point in time.
|
Attribute Name |
Type |
Description |
Example |
|---|---|---|---|
|
Tax Type |
Enum-Dynamic |
Tax type applicable for the individual or the entity. |
WHT, VAT, GST, Income Tax |
|
Tax Country |
Enum-Dynamic |
Country in which the respective tax type is applicable. |
US, DK |
|
Tax ID |
Text |
Unique Tax Reference or Identification Number for the party. |
|
|
Eligibility Type |
Enum-Dynamic |
Denotes the party eligibility criteria for the respective tax type. |
Fully Taxable, Exempted |
|
Eligibility Reason |
Text |
Reason for the eligibility. |
|
|
Start Date |
Date |
Date from which the respective tax type is applicable for the party. |
|
|
End Date |
Date |
Date until which the respective tax type is applicable for the party. |
|
|
Reason Type |
Enum-Dynamic |
The reason why the tax type is applicable for the party. |
Resident |
|
Reason Comment |
Text |
Comments on why the tax type is applicable for the party. |
|
|
Id Lack Reason |
Text |
Reason (if any) for not having a tax ID for the party. |
|
|
Is Main Tax Residency |
Enum |
Specifies if the defined tax for a specific tax type and the country as being the main tax residency. |
Yes / No |
Employment entity captures the current and previous employment details of a party. An individual may be employed with more than one employment. All such employments of the party can be captured, and it is possible to flag one of the employment as the primary employment of the party. It is also possible to mark an individual as either Unemployed or Retired.
|
Attribute Name |
Type |
Description |
Example |
|---|---|---|---|
|
Employment Type |
Enum-Dynamic |
Nature of the employment |
Employed, Unemployed, Self-Employed, Retired |
|
Country |
Enum-Dynamic |
Country of employment of the party |
US, GB |
|
Job Title |
Text |
Job Title of the party |
Director, Vice President, Business Analyst |
|
Employer Name |
Text |
Name of the employee |
Temenos, Tata Consultancy Services |
|
Start Date |
Date |
Start date of the employee |
|
|
End Date |
Date |
End date of the employee. It is applicable for capturing the previous employment details of an individual. |
|
|
Employer Segment |
Text |
|
|
|
Employer Office Phone IDD |
Text |
IDD Prefix associated with the Phone Number. |
+91 |
|
Employer Office Phone |
Text |
Phone number of the employer. |
123-456-7778 |
|
Employer Office E-Mail |
Text |
E-Mail address of the employer. |
|
|
Salary |
Decimal |
Gross Annual Salary that is earned through the employment. |
100000 |
|
Salary Frequency |
Text |
Salary Payment Frequency |
Monthly |
|
Salary In Currency |
Text |
Currency in which the salary is paid. |
GBP |
|
Primary Employment |
Boolean |
Identifies the primary employment of party. |
True/False |
Employment Type is a reference data entity that identifies the nature of employment of a party. For example, Employed, Unemployed, Self-Employed, and Retired.
It is possible to define the granular level of employment types as required by the client implementation.
Every employment type is linked to one of the pre-defined employment status released from the product that is Employed and Unemployed.
|
Attribute Name |
Type |
Description |
Example |
|---|---|---|---|
|
Employment Type |
Text |
Identifies the nature of employment of a party. |
Employed, Unemployed, Self-Employed, Retired |
|
Employment Status Type |
Enum |
Status of the employment. |
Employed (or) Unemployed |
|
Description |
Text |
Short description of the employment type. |
|
The occupation entity captures the occupation details of a party.
|
Attribute Name |
Type |
Description |
Example |
|---|---|---|---|
|
Occupation Type |
Enum-Dynamic |
Type of the occupation. |
Doctor, Architect, Attorney |
|
Description |
Text |
Description of the occupation. |
|
Party Assessment entity captures the results of various assessments performed on a party either by bank users or by external or third-party systems. For example, Assessment Results of KYC, AML, or Credit Risk of a Party can be stored.
It is possible to store either current or latest assessment results that is historical assessment details cannot be stored here. Due Diligence Microservice provides the ability to store historical data of assessment details of party. Refer to Assessment Entity section of the Due Diligence microservice.
|
Attribute Name |
Type |
Description |
Example |
|---|---|---|---|
|
Assessment Type |
Enum-Dynamic |
Type or nature of the assessment. |
KYC, AML, Credit Risk |
|
Decision Body |
Text |
The Group or Third-Party Organization responsible for the assessment. |
Moody’s, CIBIL, Credit Committee. |
|
Conclusion Date |
Date |
Assessment Conclusion Date. |
|
|
Details |
Text |
Details specific to assessments conclusion. |
|
|
Expiry Date |
Date |
Date until which the assessment results are valid. |
|
|
Level |
Text |
Outcome of the assessment. |
High, Low, Moderate |
|
Score |
Text |
The outcome of the assessment. |
800 |
|
Status |
Text |
Status of the assessment. |
Complete, Awaiting Documents |
|
Next Assessment Date |
Date |
Date on which the assessment needs to be performed again. |
|
|
Reason |
Text |
Any specific reason for the assessment decision. |
|
Party Addresses entity captures the addresses of a party including Mailing, Phone, E-Mail and other social media address. Communication Type attribute identifies the nature of the communication address for example Mailing, Phone or E-Mail etc.
Address Type attribute identifies the type of the physical location of the address for example Residence, Office, Warehouse, etc. Using Address Type it is possible to capture more than one address for the same Communication Type of a Party. For example – It is possible to capture both Residences as well Office addresses of an Individual.
- To capture Residence Address, the Communication Type should be Mailing and the Address Type should be Residence.
- To capture Office Address Communication Type should be the Mailing and Address Type should be Office.
|
Attribute Name |
Type |
Description |
Example |
|---|---|---|---|
|
Communication Type |
Enum-Dynamic |
Identifies the nature of the communication address. |
Mailing, Phone, E-Mail |
|
Address Type |
Enum-Dynamic |
Identifies the physical nature of the address. |
Office, Residence, Warehouse |
|
Electronic Address |
Text |
E-Mail ID or other electronic address of a party. It is applicable with the electronic forms of communication types such as E-Mail and Twitter. |
@satyanadella |
|
Idd Prefix Phone |
Text |
IDD Prefix that is associated with the phone number. It is applicable with the Phone communication type. |
+1, +44 |
|
Phone Number |
Text |
Phone number of the party. It is applicable with the Phone communication type. |
123-456-9877 |
|
Address Free Format |
Text |
The mailing address of a party in unstructured or free format. It is applicable with the Mailing communication type. |
Flat 11, The Mews, 56, Groove Road, Sutton, Surrey, SM2 6PP |
|
Country Code |
Enum-Dynamic |
Identifies the country of the party's mailing address. It is applicable with Mailing Communication Type. |
US, GB |
|
Country Sub Division |
Text |
Represents the subdivision of a country such as a state, region, county of the Party mailing address. |
California, Texas, Delhi, Mumbai, Surrey |
|
Flat Number |
Text |
The number that identifies the apartment or door number of the party mailing address. |
11 |
|
Building Number |
Text |
The number that identifies the position of a building on a street of the party mailing address. |
56 |
|
Building Name |
Text |
Identifies the name of the building of the party mailing address. |
The Mews |
|
Floor |
Text |
Identifies the floor within a building of party mailing address. |
First Floor |
|
Street Name |
Text |
Identifies the street of party mailing address. |
Groove Road |
|
Town |
Text |
Identifies the town/city of the party mailing address |
Sutton |
|
Region Code |
Text |
Identifies the region within a country of the party mailing address. |
Wales, Scotland, England. |
|
Postal Or Zip Code |
Text |
Identifies the postal code of the party mailing address. |
SM2 6PP |
|
Post Box Number |
Text |
Identifies the postal office (PO) box number for the party mailing address. |
189 |
|
District |
Text |
Identifies the district to which the party mailing address belongs. |
Surrey |
|
Landmark |
Text |
Landmark to the party mailing address. |
|
|
Department |
Text |
Identifies the division within a large organization building of the party mailing address. |
Finance |
|
Sub Department |
Text |
Identifies the sub-division within a large organization building of the party mailing address. |
Audit |
|
Validated By |
Text |
Bank user or source through which the party address is validated. |
|
|
Use Purpose |
Text |
The purpose for which the respective address was provided by the party |
|
|
Primary |
Boolean |
Identifies the Primary Address of a party for the respective communication type. |
True/False |
Communication Type is a Reference Data entity that identifies the communication nature of the party address. For example, Mailing, Phone, or E-Mail.
It is possible to define the granular level of communication types as required by the client implementation.
Every Communication Type is linked to one of the pre-defined communicate type nature that is released from the product such as Electronic, Phone, or Postal.
|
Attribute Name |
Type |
Description |
Example |
|---|---|---|---|
|
Communication Type Name |
Text |
Name of the communication type. |
E-Mail, Twitter, Mobile, Landline, Mailing |
|
Communication Type Nature |
Enum |
Nature of the communication type. |
Electronic, Phone, or Postal |
|
Description |
Text |
Short description of the communication type. |
Twitter handle of the party. |
Address Type is a Reference Data entity that identifies the type of the physical location of the party address. For example, Residence, Office, and Warehouse.
It is possible to define the granular level of address types as required by the client implementation.
|
Attribute Name |
Type |
Description |
Example |
|---|---|---|---|
|
Address Type Name |
Text |
Name of the address type. |
Residence, Office, Warehouse |
|
Description |
Text |
Short Description of the address type. |
Address where the Party Resides. |
Contact References entity acts as a link between the address of a party to that of the point of contact in the respective address. In the case of an organization or entities, the bank can have contact with more than one person in the same office address. For example, contact with CEO for marketing purposes and contact with finance manager for operational purpose.
Banks can create an N number of contact references for the same address and link the contact reference with the Party ID of the person to be contacted in the address by using the Contact References entity.
|
Attribute Name |
Type |
Description |
Example |
|---|---|---|---|
|
Address Reference |
Text |
The ID of the Party Address that needs to be linked. |
AD20200J33YH |
|
Contact Party Reference |
Text |
The ID of the Party to whom the address need to be linked |
200722804 |
|
Job Title |
Text |
Job Title of the party to be contacted at the respective address. |
Director, Vice-President, Finance Manager |
|
Reliability Type |
Text |
Indicates if the contact party is validated at the address. |
Confirmed |
|
Start Date |
Date |
Date from which the contact point is effective. |
|
|
End Date |
Date |
Date until which the contact point is effective. |
|
|
Contact Type Purpose |
Enum-Dynamic |
Indicates the purpose of the contact point. |
Marketing, Operation, Billing |
Party Identifier entity captures details of the identification documents that are applicable for a party. For example, Passport and Driving License.
|
Attribute Name |
Type |
Description |
Example |
|---|---|---|---|
|
Identifier Type |
Enum-Dynamic |
Identifies the nature of the party identification document. |
Passport, Driving License. |
|
Issuing Authority |
Text |
Name of the legal authority that has issued the identification document. |
Ministry of Foreign Affairs, Driver and Vehicle Licensing Agency |
|
Identifier Number |
Text |
Identification Document Number or Reference. |
Passport Number |
|
Issued Date |
Date |
Date of issue of the identification document. |
|
|
Expiry Date |
Date |
Date of expiry of the identification document. |
|
|
Issuing Country |
Enum-Dynamic |
The country that issued the identification document. |
US, GB |
|
Holder Name |
Text |
Name of the party as per the identification document. |
|
Party Identifier Type is a Reference Data entity that identifies type of the Identification document. For example, Passport and Driving License.
It is possible to define the granular level of Identifier Types as required by the client implementation.
|
Attribute Name |
Type |
Description |
Example |
|---|---|---|---|
|
Identifier Type |
Text |
Name of the identification document |
Passport, Driving License. |
|
Is Legal Identifier |
Text |
Identifies whether the respective identification document is a accepted legal document or not. |
Yes / No |
|
Allowed Party Types |
Enum-Dynamic |
List of party types allowed for the respective type of identifier. |
Individual, Corporate |
Party Classification entity captures various classification codes and related schemes applicable for a party. It is possible to classify a party with more than one classification code with different schemes. For example, a party that belongs to the Rice Farming industry can link to two different classification schemes such as NAICS and SIC.
|
Party ID |
Classification Scheme |
Classification Code |
|---|---|---|
|
100100 |
NAICS |
111160 |
|
100100 |
SIC |
0112 |
|
Attribute Name |
Type |
Description |
Example |
|---|---|---|---|
|
Classification Code |
Text |
Identifies the classification code and the applicable scheme for the party. |
NAICS-111160 |
|
Classification Date |
Date |
Date from which the party is recognized for the respective classification scheme-code. |
|
|
Reason |
Text |
Reason for classifying the party under the respective classification scheme-code. |
|
|
Source |
Enum-Dynamic |
Source based on which the party was identified for the respective classification scheme-code |
Certificate of Incorporation, |
|
End Date |
Date |
Date until when the party is recognized for the respective classification scheme-code. |
|
Classification Code is a Reference Data entity that stores the list of classification codes and associated classification schemes.
|
Attribute Name |
Type |
Description |
Example |
|---|---|---|---|
|
Classification Code |
Text |
Classification code for the respective classification scheme. |
111160 |
|
Classification Scheme |
Enum-Dynamic |
Classification scheme that is associated with the classification code. |
NAICS, SIC |
|
Name |
Text |
Name of the classification code. |
|
|
Description |
Text |
Short description of the classification code and scheme. |
Rice Farming Industry |
|
Allow Usage |
Enum |
Are the respective classification code and scheme can be linked with the party? |
Yes / No |
A classification scheme is a Reference Data Entity that stores the list of the applicable classification schemes.
|
Attribute Name |
Type |
Description |
Example |
|---|---|---|---|
|
Scheme ID |
Text |
Identifies the classification scheme. |
NAICS, SIC |
|
Description |
Text |
Short description code for the scheme. |
|
|
Authority |
Text |
Authority responsible for the respective classification scheme. |
North American Industry Classification, Internal |
|
Category Name |
Enum-Dynamic |
Category of the respective scheme. |
Sector, Industry, Target, Internal |
|
Internal Flag |
Enum |
If the classification scheme. |
Yes / No |
Party Relationship entity captures the relationship between two parties.
The relationship is expressed by the Relationship Type (Refer Relationship Type Entity for details). Every relationship can have two sides named Forward and Reverse Relationship. When the Forward relationship is recorded between two parties Party MS would automatically record the reverse relationship between the two parties.
For example - If John is the father of Tom & Sam and John is recorded as Parent-of Sam & Tom, system should automatically record Tom as Child-of John and Sam as Child of John.
|
Attribute Name |
Type |
Description |
Example |
|---|---|---|---|
|
Party ID |
Text |
ID of the primary party involved in the relationship. |
|
|
Related Party |
Text |
ID of the related party involved in the relationship. |
|
|
Relationship Type |
Enum-Dynamic |
Nature of the relationship between the two parties |
Parent-of, Wife-of, Subsidiary-of |
|
Start Date |
Date |
Date from which the relationship is applicable or effective from. |
|
|
Hierarchy Type |
Enum |
Identifies the hierarchy in the relationship. It is applicable primarily for relationship between Corporate Entities. |
Parent, Child or Other |
|
Ownership Percentage |
Text |
Indicates the Percentage of ownership on the related party. It is applicable primarily for relationship between Corporate Entities. |
|
|
End Date |
Date |
Date on which the relationship between the parties is deemed to have ended. |
|
Relationship Type is a reference data entity that identifies the nature of relationship such as Parent-of, Wife-of, or Subsidiary-of.
It is possible to define the granular level of Relationship Types as required by the client implementation.
Every relationship type must be defined with the reverse relationship type. For example, the Parent-Of relationship type must be defined with the reverse relationship type as Child-Of.
|
Attribute Name |
Type |
Description |
Example |
|---|---|---|---|
|
Relationship Type |
Text |
Identifies the nature of relationship between two parties. |
Parent-of, Subsidiary-of |
|
Description |
Text |
Short description of the relationship type |
|
|
Reverse Relationship Type |
Text |
Identifies the reverse relationship between two parties. |
Child-of, Parent-Organisation-of |
|
Reverse Relationship Description |
Text |
Short description of the reverse relationship type |
|
|
Hierarchy Type |
Enum |
Identifies the hierarchy in the Relationship. Applicable primarily for the relationship between Corporate Entities. Defaulted when |
Parent, Child or Other |
|
Party Role |
Enum-Dynamic |
List of Party Roles associated with the respective Relationship Types. Example: Sole-Proprietor-of relation code can be linked to Party Role Associated Party. |
|
Main Entity captures the basic details of a party such as Name, Date of Birth, and Nationality.
|
Attribute Name |
Type |
Description |
Example |
|---|---|---|---|
|
Date of Birth |
Date |
Date of birth of the party as recorded in the Date of Birth document. It is applicable only for Individuals. |
1956-07-04 |
|
Date of Death |
Date |
Date of death of the party as recorded in the Death certificate. It is applicable only for Individuals. |
2020-07-04 |
|
Notification of Death |
Date |
Date on which the bank was notified about the death of the party. It is applicable only for Individuals. |
2020-07-10 |
|
City of Birth |
Text |
City of birth of the party as recorded in the Date of Birth document. It is applicable only for Individuals. |
Dallas |
|
Country of Birth |
Text |
Country of birth of the party as recorded in the Date of Birth document. It is applicable only for Individuals. |
US |
|
Gender |
|
Gender of the individual. It is applicable only for Individuals. |
Male, Female |
|
Marital Status |
|
Identifies the legally defined marital state of an individual. It is applicable only for Individuals. |
Married, Single, Divorced |
|
Default Language |
Enum-Dynamic |
The preferred language that can be used for communication with the customer. |
English |
|
No Of Dependents |
Text |
Number of financially dependent persons of the party |
1,2 |
|
Reason for No Citizenship |
Text |
Reason for party not holding the citizenship in the country of residence. |
Asylum Claim Pending for Approval |
|
Party Type |
Enum-Dynamic |
Identifies the nature of the party. |
Individual, Corporate. |
|
Party Status |
Text |
Identifies the current status of party. |
Active, Inactive |
|
First Name |
Text |
First Name of the party. It is applicable only for Individuals. |
|
|
Middle Name |
Text |
Middle Name of the party. It is applicable only for Individuals. |
|
|
Last Name |
Text |
Last Name of the party. It is applicable only for Individuals. |
|
|
Nick Name |
Text |
Short Name of the party. It is applicable only for Individuals. |
|
|
Suffix |
Text |
|
|
|
Alias |
Text |
Any alias name by which the party is known. It is applicable only for Individuals. |
|
|
Entity Name |
Text |
Name of the Entity or Organization. It is applicable only for Organization. |
|
Other Names is a collection as a part of party main entity. It stores the names by which an organization is known. An organization can have one or more name types.
|
Attribute Name |
Type |
Description |
Example |
|---|---|---|---|
|
Name Type |
Enum-Dynamic |
Indicated the type of the entity name. |
Legal Name |
|
From Date |
Date |
Date from which the respective name is applicable. |
|
|
Name |
Text |
Name of the entity. |
|
|
Name Language |
Enum-Dynamic |
Language in which the name is expressed. |
English |
|
To Date |
Date |
Date until which the respective name was applicable for the entity. |
|
Citizenship is a collection as a part of party main entity. It stores the list of countries where the individual holds the citizenship or held citizenship previously.
|
Attribute Name |
Type |
Description |
Example |
|---|---|---|---|
|
Country of Citizenship |
Enum-Dynamic |
Identifies the country where the party holds or held the citizenship. |
US, GB |
|
End Date |
Date |
Date on which the citizenship of the party in the respective country was revoked. |
|
Person Position is a collection as a part of the main entity of the party. It stores the details of the important positions that are held by the respective party. For example, Prime Minister.
|
Attribute Name |
Type |
Description |
Example |
|---|---|---|---|
|
Person Position Type |
Enum-Dynamic |
Identifies the nature of the Person Position Type |
Prime Minister, Health Secretary |
|
Country of Position |
Enum-Dynamic |
Country in which the party held the position. |
US, GB |
|
Effective From Date |
Date |
Date from which the party held the position |
|
|
Effective To Date |
Date |
Date until which the party held the position |
|
|
Last Update |
Date |
Last date on which the respective person position data is updated. |
|
|
Information Source |
Text |
Source from which the information of the party position was obtained. |
Media |
The residence is a collection as a part of the main entity of the party. It stores information about the domicile and residence for a person.
|
Attribute Name |
Type |
Description |
Example |
|---|---|---|---|
|
Residence Type |
Enum-Dynamic |
Nature of the residence type. |
Domicile |
|
Country |
Enum-Dynamic |
Country of the residence type |
US, GB |
|
Status |
Text |
Status of the respective residence type. |
Active, Inactive |
|
Statutory Requirement Met |
Enum |
Specifies whether the party met the statutory requirements of the country to be a resident. |
True / False |
|
Status Comments |
Text |
Details about the status of residency. |
|
|
End Date |
Date |
Date until which the party held the respective residency. |
|
Other Risk Indicators is a collection as a part of the party main entity. It captures the specific risk indicators identified for the party. For example, Adverse Media and High Risk.
|
Attribute Name |
Type |
Description |
Example |
|---|---|---|---|
|
Risk Type |
Enum-Dynamic |
Indicates the nature of risk applicable for the party. |
Adverse Media |
|
Does Risk Apply |
Enum |
Indicates if the respective risk type is still applicable for the party. |
True / False |
|
Explanation If Applies |
Text |
Reason for the risk that is applicable for the party. |
|
|
Explanation Not Apply |
Text |
Reason for the risk that is not applicable for the party |
|
In this topic