Method, device, equipment, and storage medium for determining suspected related parties

Abstract

The embodiment of the present invention relates to the field of big data technology, and discloses a method, device, equipment and storage medium for determining suspected related parties. By determining the suspected related parties of a target subject according to the matching degree between the customer information of a customer and the keywords in the keyword library of the target subject, and determining the suspected related parties of the target subject according to set rules, the suspected related parties of the target subject can be automatically determined, the occupation of human resources can be reduced, and the timeliness and accuracy of obtaining information can be improved. In addition, by determining the suspected related parties of the target subject according to the matching degree between the customer information of a customer and the keywords in the keyword library of the target subject and according to set rules, the suspected related parties of the target subject can be determined more comprehensively.

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of big data technology, and in particular, to a method, device, equipment, and storage medium for determining a suspected related party. Background Art

[0002] With the development of my country's market economy, there are more and more group companies with cross-industry and cross-regional business scope, and the relationships between companies are becoming increasingly complex. Therefore, it is increasingly important to identify the relationships between companies (companies that have a relationship with a main company can be called the related parties of the main company).

[0003] In the related party management work, the collection and reporting of related party information requires the involvement of a large number of grassroots personnel. At the same time, due to the large number of regulatory agencies, each regulatory agency has a different definition of related parties, which puts high demands on the professionalism of personnel, resulting in high human resource utilization costs and low timeliness and accuracy in obtaining information. Summary of the invention

[0004] The present invention provides a suspected related party determination method, device, equipment, and storage medium to realize automatic identification of related parties, reduce waste of human resources, and improve the timeliness and accuracy of acquisition.

[0005] In a first aspect, an embodiment of the present invention provides a method for determining a suspected related party, including:

[0006] Determine the suspected related parties of the target subject based on the matching degree between the customer information of the client and the keywords in the keyword library of the target subject;

[0007] The suspected related parties of the target subject are determined according to the set rules; wherein the set rules are related to at least part of the information of the determined related parties of the target subject.

[0008] Optionally, before determining the suspected related party of the target subject according to the matching degree between the customer information of the client and the keywords in the keyword library of the target subject, the method further includes:

[0009] A keyword library of the target subject is established, wherein the keyword library includes certificate information of the target subject and its determined associated parties, and at least part of the words or letters in the unit names of the target subject and its determined associated parties, or abbreviations of the unit names.

[0010] Optionally, create a keyword library for the target subject, including:

[0011] Extracting at least part of the characters or letters or the abbreviation of the unit name from the certificate information of the target subject and the unit name of the target subject and adding them to the keyword library of the target subject;

[0012] Extract the certificate information of the target subject's determined associated party and at least part of the text or letters or abbreviation of the unit name of the target subject's determined associated party and add them to the target subject's keyword library, and record the time when the keyword was generated, the reason for the keyword's formation and the associated party involved in the keyword.

[0013] Optionally, the customer information includes customer certificate information, and the suspected related parties of the target subject are determined according to the matching degree between the customer information of the customer and the keywords in the keyword library of the target subject, including:

[0014] Determine whether the customer is a suspected related party of the target subject based on the matching degree between the customer's certificate information and the certificate information of the target subject in the keyword library or the matching degree between the customer's certificate information and the certificate information of the determined related party of the target subject in the keyword library.

[0015] Optionally, determining whether the client is a suspected associated party of the target subject according to the matching degree between the client certificate information and the certificate information of the target subject in the keyword library or the matching degree between the client certificate information and the certificate information of a determined associated party of the target subject in the keyword library includes:

[0016] The certificate information of the target subject and its determined related parties are extracted from the keyword library, and matched with the customer certificate information in the system or account storing the customer information at set time intervals. If the match is consistent, the customer is determined as a suspected related party of the target subject.

[0017] Optionally, the customer information includes the name of the customer company, and the suspected related parties of the target entity are determined according to the matching degree between the customer information of the customer and the keywords in the keyword library of the target entity, including:

[0018] Determine whether the customer is a suspected affiliate of the target entity based on the degree of match between at least part of the customer's unit name and at least part of the text or letters or abbreviation of the unit name of the target entity in the keyword library, or the degree of match between at least part of the customer's unit name and at least part of the text or letters or abbreviation of the unit name of a determined affiliate of the target entity in the keyword library.

[0019] Optionally, the keyword library of the target subject also includes the actual controller of the determined related party of the target subject, and the customer information includes the actual controller of the customer; determining the suspected related party of the target subject according to the matching degree between the customer information of the customer and the keywords in the keyword library of the target subject includes:

[0020] Determine whether the customer is a suspected related party of the target entity based on the degree of match between the customer's actual controller and the actual controller of the related party identified in the keyword library.

[0021] Optionally, the keyword library of the target subject also includes a customer number of a determined associated party of the target subject; determining whether the customer is a suspected associated party of the target subject according to a set rule includes:

[0022] According to the customer number of the determined related party of the target entity, the related persons of the determined related party are extracted from the unified view of corporate customers as suspected related parties, where the related persons of the determined related party include the superior legal person and the invested enterprise.

[0023] Optionally, the suspected related parties of the target entity are determined according to the set rules, including:

[0024] According to the determined related parties of the target entity, customers who have a superior or subordinate equity control relationship with the determined related parties reaching a set ratio are extracted from the unified view of corporate customers as suspected related parties of the target entity.

[0025] Optionally, the suspected related parties of the target entity are determined according to the set rules, including:

[0026] According to the customer number of the determined related party with the set identification among the determined related parties of the target entity, the associated companies of the determined related party with the set identification are extracted from the unified view of corporate customers as suspected related parties.

[0027] Optionally, the suspected related parties of the target entity are determined according to the set rules, including:

[0028] Other companies in the credit group to which the target entity's confirmed related parties belong shall be regarded as suspected related parties of the target entity.

[0029] Optionally, after the suspected related parties of the target entity are determined according to the set rules, the following is also included:

[0030] Generate a list of suspected related parties.

[0031] Optionally, after generating the list of suspected related parties, it also includes:

[0032] For the same suspected related parties of the target entity, duplicates are removed and one suspected related party record is retained for the same suspected related party.

[0033] In a second aspect, an embodiment of the present invention further provides a suspected related party determination device, including:

[0034] A first determination module is used to determine the suspected related party of the target subject according to the matching degree between the customer information of the client and the keywords in the keyword library of the target subject;

[0035] The second determination module is used to determine the suspected related party of the target subject according to the set rules; wherein the set rules are related to at least part of the information of the determined related party of the target subject.

[0036] In a third aspect, an embodiment of the present invention further provides a suspected related party determination device, including:

[0037] one or more processors;

[0038] A storage device for storing one or more programs;

[0039] When one or more programs are executed by one or more processors, the one or more processors implement the method of the first aspect.

[0040] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, which implements the method of the first aspect when executed by a processor.

[0041] In a fifth aspect, an embodiment of the present invention further provides a computer program product, the computer program product comprising computer executable instructions, and the computer executable instructions are used to implement the method of the first aspect when executed.

[0042] The method, device, equipment and storage medium for determining suspected related parties provided by the embodiments of the present invention can automatically determine the suspected related parties of the target subject by determining the suspected related parties of the target subject according to the matching degree between the customer information of the customer and the keywords in the keyword library of the target subject, and determining the suspected related parties of the target subject according to the set rules, thereby reducing the occupation of human resources and improving the timeliness and accuracy of obtaining information. In addition, by determining the suspected related parties of the target subject in two ways, namely, the matching degree between the customer information of the customer and the keywords in the keyword library of the target subject and according to the set rules, the suspected related parties of the target subject can be determined more comprehensively. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] Figure 1 A flowchart of a method for determining a suspected related party provided by an embodiment of the present invention;

[0044] Figure 2 is a flow chart of another method for determining a suspected related party provided by an embodiment of the present invention;

[0045] Figure 3 is a flow chart of another method for determining a suspected related party provided by an embodiment of the present invention;

[0046] Figure 4 is a flow chart of another method for determining a suspected related party provided by an embodiment of the present invention;

[0047] Figure 5 is a flow chart of another method for determining a suspected related party provided by an embodiment of the present invention;

[0048] Figure 6is a flow chart of another method for determining a suspected related party provided by an embodiment of the present invention;

[0049] Figure 7 is a flow chart of another method for determining a suspected related party provided by an embodiment of the present invention;

[0050] Figure 8 is a flow chart of another method for determining a suspected related party provided by an embodiment of the present invention;

[0051] Fig. 9 is a flow chart of another method for determining a suspected related party provided by an embodiment of the present invention;

[0052] Fig.10 is a structural schematic diagram of a suspected related party determination device provided by an embodiment of the present invention;

[0053] Fig.11 It is a structural diagram of a suspected related party determination device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0054] The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the present invention, rather than to limit the present invention. It should also be noted that, for ease of description, only parts related to the present invention, rather than all structures, are shown in the accompanying drawings.

[0055] The embodiment of the present invention provides a method for determining a suspected related party. Figure 1 This is a flow chart of a method for determining a suspected related party provided by an embodiment of the present invention. This embodiment can be applied to the case of automatically determining a suspected related party of a target subject. The method can be executed by a suspected related party determination device, which can be implemented in software and / or hardware. The device can be configured in an electronic device, such as a server or a terminal device. Typical terminal devices include mobile terminals, specifically mobile phones, computers or tablet computers, etc. Figure 1 As shown, the method may specifically include:

[0056] Step 110: Determine the suspected related parties of the target entity according to the matching degree between the customer information of the client and the keywords in the keyword library of the target entity.

[0057] Specifically, before taking the step of determining suspected related parties, a keyword library of the target entity can be established first. The keyword library of the target entity can be established by collecting publicly disclosed information of the target entity (including equity changes, establishment of new subsidiaries, and relevant information of the directors, supervisors, and senior managers of the related parties. For listed companies, the semi-annual or annual reports of the related legal persons of the listed companies can be downloaded from the website of the stock exchange to obtain information on the actual controllers, controlling shareholders, subsidiaries, joint ventures, associated companies, other subsidiaries of the controlling shareholders, etc.), investigating and reviewing the credit information provided by the target entity, obtaining information on its equity relations, invested enterprises and other related parties, and collecting information on the determined related parties of the target entity.

[0058] In this step, whether the newly added customer is a suspected related party of the target entity can be determined based on the matching degree between the customer information of the newly added customer and the keywords in the keyword library of the target entity. Specifically, if the customer information of the newly added customer can match any keyword in the keyword library, the newly added customer can be determined as a suspected related party of the target entity.

[0059] Step 120: Determine the suspected related parties of the target subject according to the set rules; wherein the set rules are related to at least part of the information of the determined related parties of the target subject.

[0060] As a supplement to step 110, the suspected related parties of the target subject may also be determined according to set rules. The set rules are related to at least part of the information of the determined related parties of the target subject. That is, the suspected related parties of the target subject may be determined according to at least part of the information of the determined related parties of the target subject, thereby making the determination of the suspected related parties of the target subject more comprehensive.

[0061] The method for determining suspected related parties of this embodiment can automatically determine the suspected related parties of the target subject by determining the suspected related parties of the target subject according to the matching degree between the customer information of the customer and the keywords in the keyword library of the target subject, and determining the suspected related parties of the target subject according to the set rules, thereby reducing the occupation of human resources and improving the timeliness and accuracy of obtaining information. In addition, by determining the suspected related parties of the target subject in two ways, namely, the matching degree between the customer information of the customer and the keywords in the keyword library of the target subject and according to the set rules, the suspected related parties of the target subject can be determined more comprehensively.

[0062] Figure 2 is a flowchart of another method for determining a suspected related party provided by an embodiment of the present invention, refer to Figure 2 Optionally, the method for determining the suspected related party includes:

[0063] Step 210: Establish a keyword library of the target subject, wherein the keyword library includes certificate information of the target subject and its determined associated parties, and at least part of the words or letters in the unit names of the target subject and its determined associated parties, or abbreviations of the unit names.

[0064] The certificate information includes the certificate type and certificate number. The certificate number includes the organization code, business license number, tax registration certificate number, other certificate numbers, legal person certificate number, internal account number, etc. The unit name can be in Chinese or English; the abbreviation of the unit name can be in Chinese or English. Therefore, the keywords in the keyword library include numeric keywords and text keywords, where numeric keywords can include certificate numbers, and text keywords can include certificate types, at least part of the words or letters in the unit name, or the abbreviation of the unit name.

[0065] Optionally, step 210 includes:

[0066] Extract at least part of the text or letters or abbreviation of the unit name from the certificate information of the target subject and the unit name of the target subject, and add them to the keyword library of the target subject; and extract at least part of the text or letters or abbreviation of the unit name from the certificate information of the target subject's determined associated party and the unit name of the target subject's determined associated party, and add them to the keyword library of the target subject, and record the time when the keyword was generated, the reason for the keyword being formed, and the associated party involved in the keyword.

[0067] Specifically, in this step, a keyword library can be established by automatic extraction, so that the establishment of the keyword library does not waste human resources, further reducing the occupation of human resources by the determination of suspected related parties. Exemplarily, if the unit name of the target entity includes "AB", and the unit name of the determined related party also includes "AB", then "AB" can be recorded as a keyword in the keyword library, and the time when the keyword was formed and the reason for the formation of the keyword is that the unit name of the determined related party contains "AB", and the related party involved in the keyword is the determined related party.

[0068] Among them, when the information of a confirmed related party customer changes, such as a change in its legal representative, the new legal representative certificate information of the customer can be automatically refreshed from the key library to update and maintain the suspected related party keyword library. If the related party identity of a confirmed related party customer expires, the system can refresh the keyword library after receiving the expiration prompt and remove the legal representative certificate information of the expired related party. The staff obtains the certificate information of a related party customer who can be identified as the target entity from some channels, but the customer may not currently have an account or business dealings with the target entity. The staff can maintain the certificate information in the keyword library, enter the certificate information of the related party customer, and search for the related party and its other information in the unified view of corporate customers.

[0069] To establish a keyword library, the first-level system review operator and the second-level system operator can submit a keyword list (including Chinese and English), and the final system administrator will review and confirm it. At the same time, the final system administrator regularly maintains the information in the keyword library. The new addition of keywords can be divided into one-by-one entry and batch import. One-by-one entry requires one to be entered one by one in the interface. Batch import requires the addition of a batch import text information component. The staff can upload files in a fixed text format, which will be reviewed and confirmed by the ultimate system administrator.

[0070] Step 220: Determine whether the client is a suspected associated party of the target subject based on the degree of match between the client's certificate information and the certificate information of the target subject in the keyword library or the degree of match between the client's certificate information and the certificate information of a determined associated party of the target subject in the keyword library.

[0071] Specifically, when the customer certificate information matches the certificate information of the target subject in the keyword library or when the customer certificate information matches the certificate information of a determined associated party of the target subject in the keyword library, the customer corresponding to the customer certificate information is determined to be a suspected associated party of the target subject.

[0072] Optionally, step 220 includes:

[0073] The certificate information of the target subject and its determined related parties are extracted from the keyword library, and matched with the customer certificate information in the system or account storing the customer information at set time intervals. If the match is consistent, the customer is determined as a suspected related party of the target subject.

[0074] Exemplarily, the certificate information of the target subject and its determined related parties can be extracted from the keyword library, and matched with the customer certificate information in the system or account storing customer information at the end of each day to determine the suspected related parties of the target subject. As the business expands, the customer information in the system or account storing customer information may be updated every day. Therefore, the certificate information of the target subject and its determined related parties is extracted from the keyword library, and matched with the customer certificate information in the system or account storing customer information at set time intervals to determine the suspected related parties. This can ensure that the newly added suspected related parties of the target subject are determined in a timely manner, and ensure the timeliness of the acquisition of related parties.

[0075] Step 230: Determine whether the client is a suspected affiliate of the target entity based on the degree of match between at least part of the client's unit name and at least part of the text or letters or abbreviation of the unit name of the target entity in the keyword library, or the degree of match between at least part of the client's unit name and at least part of the text or letters or abbreviation of the unit name of a determined affiliate of the target entity in the keyword library.

[0076] Specifically, when at least part of the customer's unit name matches at least part of the text or letters in the unit name of the target entity in the keyword library or the abbreviation of the unit name, or when at least part of the customer's unit name matches at least part of the text or letters in the unit name of a determined associated party of the target entity in the keyword library, the customer corresponding to the customer's unit name is determined to be a suspected associated party of the target entity.

[0077] Step 240, determine the suspected related parties of the target subject according to the set rules; wherein the set rules are related to at least part of the information of the determined related parties of the target subject; step 240 is the same as step 120 in the above embodiment and will not be repeated here.

[0078] The method for determining suspected related parties of the present embodiment extracts at least part of the characters or letters or abbreviations of the unit name of the target subject and adds them to the keyword library of the target subject; and extracts at least part of the characters or letters or abbreviations of the unit name of the target subject and adds them to the keyword library of the target subject. It determines whether the customer is a suspected related party of the target subject according to the matching degree between the customer's certificate information and the certificate information of the target subject in the keyword library, or the matching degree between the customer's certificate information and the certificate information of the determined related party of the target subject in the keyword library, and determines whether the customer is a suspected related party of the target subject according to the matching degree between at least part of the customer's unit name and at least part of the characters or letters or abbreviations of the unit name of the target subject in the keyword library, or according to the matching degree between at least part of the customer's unit name and at least part of the characters or letters or abbreviations of the unit name of the determined related party of the target subject in the keyword library, so as to realize automatic establishment of the keyword library and automatic determination of related parties, further reduce the waste of human resources, and ensure the timeliness and accuracy of related party acquisition.

[0079] Optionally, the keyword library of the target entity also includes the actual controller of the target entity's determined associated party, and the customer information includes the actual controller of the customer. Figure 3 is a flowchart of another method for determining a suspected related party provided by an embodiment of the present invention, refer to Figure 3 Optionally, the method for determining the suspected related party includes:

[0080] Step 310: Determine whether the customer is a suspected related party of the target entity based on the matching degree between the actual controller of the customer and the actual controller of the related party determined in the keyword library.

[0081] Specifically, when the actual controller of the customer matches the actual controller of the determined related party, the customer is determined to be a suspected related party of the target entity. Step 310 may include: extracting other customers controlled by the same actual controller of the determined related party from the unified view of public customers as suspected related parties of the target entity.

[0082] Step 320, determine the suspected related parties of the target subject according to the set rules; wherein the set rules are related to at least part of the information of the determined related parties of the target subject; step 320 is the same as step 120 in the above embodiment and will not be repeated here.

[0083] Optionally, the keyword library of the target entity also includes the customer number of the target entity's determined associated party. Figure 4 is a flowchart of another method for determining a suspected related party provided by an embodiment of the present invention, refer to Figure 4Optionally, the method for determining the suspected related party includes:

[0084] Step 410: determine the suspected related party of the target subject according to the matching degree between the customer information of the client and the keywords in the keyword library of the target subject; step 410 is the same as step 110 in the above embodiment and will not be repeated here.

[0085] Step 420: extract the associated persons of the determined associated parties from the unified view of corporate customers as suspected associated parties according to the customer number of the determined associated parties of the target entity, wherein the associated persons of the determined associated parties include the superior legal person and the invested enterprise.

[0086] Specifically, the customer number can be used as a customer identifier. Each customer corresponds to a customer number, and different customers correspond to different customer numbers. When determining that a related party has a relationship with the target subject, the related person of the determined related party may also have a relationship with the target subject. According to the customer number of the determined related party of the target subject, the related person of the determined related party is extracted from the unified view of public customers. For example, the superior legal person of the determined related party and the invested enterprise are extracted from the unified view of public customers as suspected related parties of the target subject.

[0087] Step 430, determine the suspected related parties of the target subject according to the set rules; wherein the set rules are related to at least part of the information of the determined related parties of the target subject; step 430 is the same as step 120 in the above embodiment and will not be repeated here.

[0088] Optionally, the keyword library of the target entity also includes the customer number of the target entity's determined associated party. Figure 5 is a flowchart of another method for determining a suspected related party provided by an embodiment of the present invention, refer to Figure 5 Optionally, the method for determining the suspected related party includes:

[0089] Step 510: determine the suspected related party of the target entity according to the matching degree between the customer information of the client and the keywords in the keyword library of the target entity; step 510 is the same as step 110 in the above embodiment, and will not be repeated here.

[0090] Step 520: According to the determined related parties of the target entity, customers who have a superior or subordinate equity control relationship with the determined related parties reaching a set ratio are extracted from the unified view of corporate customers as suspected related parties of the target entity.

[0091] Specifically, it is determined that there is an association relationship between the related party and the target subject, so the customers who have a superior or subordinate equity control relationship with the determined related party may also have an association relationship with the target subject, and among the customers who have a superior or subordinate equity control relationship with the determined related party, the greater the superior or subordinate equity control ratio, the higher the probability of becoming a suspected related party of the target subject. In this step, by extracting customers who have a superior or subordinate equity control relationship with the determined related party that reaches a set ratio from the unified view of corporate customers as suspected related parties of the target subject, that is, extracting customers who have a superior or subordinate equity control relationship with the determined related party that is greater than or equal to the set ratio from the unified view of corporate customers as suspected related parties of the target subject, wherein the set ratio can be adjusted according to actual conditions, and illustratively, the set ratio is 20%, thereby realizing the determination of the suspected related parties of the target subject according to the equity control relationship.

[0092] Optionally, the keyword library of the target entity also includes the customer number of the target entity's determined associated party. Figure 6 is a flowchart of another method for determining a suspected related party provided by an embodiment of the present invention, refer to Figure 6 Optionally, the method for determining the suspected related party includes:

[0093] Step 610: determine the suspected related party of the target entity according to the matching degree between the customer information of the client and the keywords in the keyword library of the target entity; step 610 is the same as step 110 in the above embodiment and will not be repeated here.

[0094] Step 620: extract the associated companies of the determined associated parties with the set identifier from the unified view of corporate customers as suspected associated parties according to the customer numbers of the determined associated parties with the set identifier among the determined associated parties of the target entity.

[0095] For example, in the banking industry, most banks will hold shares in insurance companies, and the bank's customers include customers with the logo of the insurance company in which the bank holds shares. The set logo can be the above-mentioned logo of the insurance company in which the bank holds shares. In this step, based on the customer number of the determined related party with the set logo in the determined related parties of the target entity, the affiliated companies of the determined related parties with the set logo are extracted as suspected related parties from the unified view of corporate customers, and the affiliated companies of the customer with the logo of the insurance company in which the bank holds shares can be regarded as suspected related parties.

[0096] In another optional embodiment of the present invention, it is also possible to extract the associated companies of the deemed associated parties with set identifiers from the unified view of corporate customers as suspected associated parties based on the customer numbers of the deemed associated parties with set identifiers among the deemed associated parties of the target entity. Unlike the determined associated parties, the relevant information of the deemed associated parties may not be in the keyword library, but they are also regarded as the determined associated parties of the target entity.

[0097] In order to more comprehensively determine the definite related parties of the target entity, the related enterprises of the definite related parties with set identification can be extracted from the unified view of corporate customers as suspected related parties based on the customer number of the definite related parties with set identification among the definite related parties of the target entity; and the related enterprises of the deemed related parties with set identification can be extracted from the unified view of corporate customers as suspected related parties based on the customer number of the deemed related parties with set identification among the deemed related parties of the target entity.

[0098] Optionally, the keyword library of the target entity also includes the customer number of the target entity's determined associated party. Figure 7 is a flowchart of another method for determining a suspected related party provided by an embodiment of the present invention, refer to Figure 7 Optionally, the method for determining the suspected related party includes:

[0099] Step 710: determine the suspected related parties of the target entity according to the matching degree between the customer information of the client and the keywords in the keyword library of the target entity; step 710 is the same as step 110 in the above embodiment and will not be repeated here.

[0100] Step 720: other enterprises in the credit group to which the determined related parties of the target entity belong are regarded as suspected related parties of the target entity.

[0101] Specifically, based on the customer number of the determined related party, other enterprises in the credit group to which the determined related party belongs can be extracted from the unified view of corporate customers as suspected related parties of the target entity.

[0102] Figure 8 is a flowchart of another method for determining a suspected related party provided by an embodiment of the present invention, refer to Figure 8 Optionally, the method for determining the suspected related party includes:

[0103] Step 810: Establish a keyword library of the target entity.

[0104] The keyword library includes the certificate information of the target entity and its determined related parties, at least part of the text or letters in the unit name of the target entity and its determined related parties, or the abbreviation of the unit name; it can also include the actual controller of the determined related party of the target entity, and the customer number of the determined related party of the target entity.

[0105] Step 820: determine whether the customer is a suspected associated party of the target subject based on the degree of match between the customer's certificate information and the certificate information of the target subject in the keyword library, or the degree of match between the customer's certificate information and the certificate information of the determined associated party of the target subject in the keyword library; step 820 is the same as step 220 in the above embodiment and will not be repeated here.

[0106] Step 830: determine whether the customer is a suspected affiliate of the target entity based on the degree of match between at least part of the customer's unit name and at least part of the text or letters or abbreviation of the unit name of the target entity in the keyword library, or the degree of match between at least part of the customer's unit name and at least part of the text or letters or abbreviation of the unit name of a determined affiliate of the target entity in the keyword library; step 830 is the same as the process of step 230 in the above embodiment, and will not be repeated here.

[0107] Step 840: Determine whether the customer is a suspected related party of the target entity based on the matching degree between the actual controller of the customer and the actual controller of the related party determined in the keyword library; step 840 is the same as step 310 in the above embodiment and will not be repeated here.

[0108] Step 850: According to the customer number of the determined related party of the target entity, the related persons of the determined related party are extracted from the unified view of corporate customers as suspected related parties, wherein the related persons of the determined related party include the superior legal person and the invested enterprise; this step 850 is the same as the process of step 420 in the above embodiment and will not be repeated here.

[0109] Step 860: According to the determined related parties of the target entity, extract from the unified view of corporate customers the customers who have a superior or subordinate equity control relationship with the determined related parties that reaches a set ratio as suspected related parties of the target entity; this step 860 is the same as the process of step 520 in the above embodiment and will not be repeated here.

[0110] Step 870: According to the customer number of the determined related party with the set identifier among the determined related parties of the target entity, the associated enterprises of the determined related party with the set identifier are extracted from the unified view of corporate customers as suspected related parties; this step 870 is the same as the process of step 620 in the above embodiment and will not be repeated here.

[0111] Step 880: other enterprises in the credit group to which the determined related parties of the target entity belong are regarded as suspected related parties of the target entity; this step 880 is the same as the process of step 720 in the above embodiment, and will not be repeated here.

[0112] The method for determining suspected related parties in this embodiment realizes automatic determination of suspected related parties by matching customer information with keywords included in the keyword library and determining the suspected related parties of the target subject according to different set rules. Compared with the prior art, it effectively saves human resources and can make the determined suspected related parties more comprehensive, which is conducive to improving the timeliness and accuracy of determining suspected related parties.

[0113] Fig. 9is a flowchart of another method for determining a suspected related party provided by an embodiment of the present invention, refer to Fig. 9 Optionally, the method for determining the suspected related party includes:

[0114] Step 910: Determine the suspected associated party of the target entity according to the matching degree between the customer information of the client and the keywords in the keyword library of the target entity, wherein step 910 may include steps 820 to 840 in the above embodiment.

[0115] Step 920: determine the suspected related parties of the target subject according to the set rules; wherein the set rules are related to at least part of the information of the determined related parties of the target subject, wherein step 920 may include steps 850 to 880 in the above embodiment.

[0116] Step 930: Generate a list of suspected related parties.

[0117] Specifically, in an optional embodiment, after the suspected related party is determined in step 910, a list of suspected related parties may be generated, and after the suspected related party is determined in step 920, the list of suspected related parties may be generated again. In another optional embodiment, after the suspected related party is determined in step 910 and the suspected related party is determined in step 920, the list of suspected related parties may be generated once, which is not specifically limited in this embodiment.

[0118] Step 940: De-duplicate the same suspected related parties of the target entity, and retain one suspected related party record for the same suspected related party.

[0119] Since the setting rules may include multiple types, the suspected related parties determined by different setting rules may be the same. In addition, the suspected related parties of the target subject determined in step 910 based on the matching degree between the customer information of the customer and the keywords in the keyword library of the target subject and the suspected related parties of the target subject determined in step 920 based on the setting rules may also be the same. In this embodiment, the same suspected related parties of the target subject are deduplicated to ensure the simplicity of the list of suspected related parties and facilitate staff viewing. Optionally, when generating a list of suspected related parties, the formation reason of each suspected related party is recorded. For the same suspected related parties with the same formation reason, only one suspected related party record may be retained; for the same suspected related parties with different formation reasons, only one suspected related party record may also be retained, but the formation reasons of each suspected related party are recorded in the next level list of suspected related parties in the list of suspected related parties.

[0120] It should be noted that, if the following circumstances are met, they will be directly deleted from the final list of suspected related parties and will not be managed as suspected related parties to be identified: 1. The suspected related party is already in the stages of declaration, review, confirmation, etc. of related parties or clients deemed to be managed as related parties; 2. The suspected related party has been confirmed as a related party of the target entity or a client deemed to be managed as a related party; 3. The suspected related party has been screened by the business and permanently deleted (except for new causes).

[0121] The embodiment of the present invention also provides a device for locating elements in a robot process automation interface. Fig.10 The structure diagram of a suspected related party determination device provided by an embodiment of the present invention is a schematic diagram of a suspected related party determination device provided by an embodiment of the present invention. This embodiment can be applied to the case of automatically determining suspected related parties. The suspected related party determination device provided by an embodiment of the present invention can execute the suspected related party determination method provided by any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0122] The device specifically includes a first determination module 10, which is used to determine the suspected associated party of the target subject according to the matching degree between the customer information of the client and the keywords in the keyword library of the target subject;

[0123] The second determination module 20 is used to determine the suspected associated party of the target subject according to the set rules; wherein the set rules are related to at least part of the information of the determined associated party of the target subject.

[0124] The suspected related party determination device provided in the embodiment of the present invention can execute the suspected related party determination method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0125] Fig.11 It is a structural diagram of a suspected related party determination device provided by an embodiment of the present invention. Fig.11 A block diagram of an exemplary apparatus suitable for implementing embodiments of the present invention is shown. Fig.11 The suspected related party determination device 41 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0126] like Fig.11 As shown, the suspected related party determination device 41 is in the form of a general device. The components of the suspected related party determination device 41 may include but are not limited to: one or more processors 416, a storage device 428, and a bus 418 connecting different system components (including the storage device 428 and the processor 416).

[0127] Bus 418 represents one or more of several types of bus structures, including a storage device bus or storage device controller, a peripheral bus, an accelerated graphics port, a processor or a local bus using any of a variety of bus architectures. For example, these architectures include but are not limited to Industry Subversive Alliance (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus and Peripheral Component Interconnect (PCI) bus.

[0128] The suspected related party determination device 41 typically includes a variety of computer system readable media, which can be any available media that can be accessed by the suspected related party determination device 41, including volatile and non-volatile media, removable and non-removable media.

[0129] The storage device 428 may include a computer system readable medium in the form of a volatile memory, such as a random access memory (RAM) 431 and / or a cache memory 432. The suspected associated party determination device 41 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 434 may be used to read and write non-removable, non-volatile magnetic media ( Fig.11 not shown, usually called a "hard drive"). Although Fig.11 Not shown in the figure, a disk drive for reading and writing a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing a removable non-volatile optical disk, such as a read-only optical disk (Compact Disc Read-Only Memory, CD-ROM), a digital video disk (Digital Video Disc-Read Only Memory, DVD-ROM) or other optical media) may be provided. In these cases, each drive may be connected to the bus 418 via one or more data medium interfaces. The storage device 428 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the various embodiments of the present invention.

[0130] A program / utility 441 having a set (at least one) of program modules 442 may be stored, for example, in a storage device 428, such program modules 442 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. Program modules 442 generally perform the functions and / or methods of the embodiments described herein.

[0131] The suspected associated party determination device 41 may also communicate with one or more external devices 414 (e.g., a keyboard, a pointing terminal, a display 424, etc.), and may also communicate with one or more terminals that enable a user to interact with the suspected associated party determination device 41, and / or communicate with any terminal that enables the suspected associated party determination device 41 to communicate with one or more other computing terminals (e.g., a network card, a modem, etc.). Such communication may be performed through an input / output (I / O) interface 422. Furthermore, the suspected associated party determination device 41 may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) through a network adapter 421. Fig.11 As shown, the network adapter 421 communicates with other modules of the device 41 via the bus 418. It should be understood that, although not shown in the figure, other hardware and / or software modules can be used in conjunction with the suspected associated party determination device 41, including but not limited to: microcode, terminal drivers, redundant processors, external disk drive arrays, disk arrays (Redundant Arrays of Independent Disks, RAID) systems, tape drives, and data backup storage systems.

[0132] The processor 416 executes various functional applications and data processing by running the program stored in the storage device 428, for example, implementing the suspected related party determination method provided in the embodiment of the present invention, which includes:

[0133] Determine the suspected related parties of the target subject based on the matching degree between the customer information of the client and the keywords in the keyword library of the target subject;

[0134] The suspected related parties of the target subject are determined according to the set rules; wherein the set rules are related to at least part of the information of the determined related parties of the target subject.

[0135] The embodiment of the present invention further provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the method for determining a suspected related party provided in the embodiment of the present invention is implemented. The method includes:

[0136] Determine the suspected related parties of the target subject based on the matching degree between the customer information of the client and the keywords in the keyword library of the target subject;

[0137] The suspected related parties of the target subject are determined according to the set rules; wherein the set rules are related to at least part of the information of the determined related parties of the target subject.

[0138] The computer storage medium of the embodiment of the present invention can adopt any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this document, a computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.

[0139] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0140] Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0141] Computer program code for performing the operations of the present invention may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or terminal. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0142] An embodiment of the present invention further provides a computer program product, which includes computer executable instructions. When the computer executable instructions are executed by a computer processor, they are used to execute the suspected related party determination method in the above method embodiment.

[0143] Of course, the computer program product provided by the embodiment of the present application, whose computer executable instructions are not limited to the method operations described above, can also execute related operations in the method provided by any embodiment of the present application.

[0144] It should be noted that in the embodiments of the present invention, the acquisition, storage and / or processing of the financial data involved complies with the relevant provisions of national laws and regulations and does not violate public order and good morals.

[0145] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A method for determining a suspected related party, characterized in that: include: Determine the suspected related party of the target subject according to the matching degree between the customer information of the client and the keywords in the keyword library of the target subject; Determine the suspected related party of the target subject according to the set rules; wherein the set rules are related to at least part of the information of the determined related party of the target subject; before determining the suspected related party of the target subject according to the matching degree between the customer information of the customer and the keywords in the keyword library of the target subject, it also includes: Establishing a keyword library of the target subject, wherein the keyword library includes certificate information of the target subject and its determined associated parties, at least part of the words or letters in the unit names of the target subject and its determined associated parties, or abbreviations of the unit names; The customer information includes customer certificate information, and the determining of the suspected related party of the target subject according to the matching degree between the customer information of the customer and the keywords in the keyword library of the target subject includes: Determining whether the customer is a suspected related party of the target subject according to the matching degree between the customer certificate information and the certificate information of the target subject in the keyword library or the matching degree between the customer certificate information and the certificate information of the determined related party of the target subject in the keyword library; The determining whether the customer is a suspected associated party of the target subject according to the matching degree between the customer certificate information and the certificate information of the target subject in the keyword library or the matching degree between the customer certificate information and the certificate information of a determined associated party of the target subject in the keyword library includes: Extract the certificate information of the target subject and its determined related party from the keyword library, and match it with the customer certificate information in the system or account storing the customer information at a set time interval. If the match is consistent, the customer is determined as a suspected related party of the target subject; The keyword library of the target subject also includes the customer number of the determined associated party of the target subject; the determining whether the customer is a suspected associated party of the target subject according to the set rules includes: According to the customer number of the determined related party of the target entity, the related persons of the determined related party are extracted from the unified view of corporate customers as suspected related parties, wherein the related persons of the determined related party include the superior legal person and the invested enterprise.

2. The method for determining a suspected related party according to claim 1, characterized in that: The step of establishing the keyword library of the target subject includes: Extracting the certificate information of the target subject and at least part of the characters or letters in the unit name of the target subject or the abbreviation of the unit name and adding them to the keyword library of the target subject; Extract the certificate information of the determined associated party of the target subject and at least part of the text or letters in the unit name of the determined associated party of the target subject or the abbreviation of the unit name and add them to the keyword library of the target subject, and record the time when the keyword was generated, the reason for the formation of the keyword and the associated party involved in the keyword.

3. The method for determining a suspected related party according to claim 1, characterized in that: The customer information includes the name of the customer unit, and the determining of the suspected related party of the target entity according to the matching degree between the customer information of the customer and the keywords in the keyword library of the target entity includes: Whether the customer is a suspected affiliate of the target entity is determined based on the degree of match between at least part of the customer's unit name and at least part of the characters or letters in the unit name of the target entity in the keyword library or the abbreviation of the unit name, or the degree of match between at least part of the customer's unit name and at least part of the characters or letters in the unit name of a determined affiliate of the target entity in the keyword library or the abbreviation of the unit name.

4. The method for determining a suspected related party according to claim 1, characterized in that: The keyword library of the target subject also includes the actual controller of the determined associated party of the target subject, and the customer information includes the actual controller of the customer; The determining of the suspected associated party of the target subject according to the matching degree between the customer information of the client and the keywords in the keyword library of the target subject includes: According to the matching degree between the actual controller of the customer and the actual controller of the determined related party in the keyword library, it is determined whether the customer is a suspected related party of the target entity.

5. The method for determining a suspected related party according to claim 1, characterized in that: The determining the suspected related party of the target subject according to the set rules includes: According to the determined related parties of the target entity, customers who have a superior or subordinate equity control relationship with the determined related parties reaching a set ratio are extracted from the unified view of corporate customers as suspected related parties of the target entity.

6. The method for determining a suspected related party according to claim 1, characterized in that: The determining the suspected related party of the target subject according to the set rules includes: According to the customer number of the determined related party with a set identifier among the determined related parties of the target entity, the associated enterprises of the determined related party with the set identifier are extracted from the unified view of corporate customers as suspected related parties.

7. The method for determining a suspected related party according to claim 1, characterized in that: The determining the suspected related party of the target subject according to the set rules includes: Other enterprises in the credit group to which the determined related parties of the target entity belong are regarded as suspected related parties of the target entity.

8. The method for determining a suspected related party according to claim 1, characterized in that: After determining the suspected related parties of the target subject according to the set rules, it also includes: Generate a list of suspected related parties.

9. The method for determining a suspected related party according to claim 8, characterized in that: After generating the list of suspected related parties, it also includes: The same suspected related parties of the target entity are deduplicated, and one suspected related party record is retained for the same suspected related party.

10. A device for determining a suspected related party, characterized in that: include: A first determination module, configured to determine a suspected associated party of a target entity according to a matching degree between the customer information of the client and a keyword in a keyword library of the target entity; A second determination module, configured to determine a suspected associated party of the target subject according to a set rule; wherein the set rule is related to at least part of the information of the determined associated party of the target subject; Before determining the suspected related party of the target subject according to the matching degree between the customer information of the client and the keywords in the keyword library of the target subject, the method further includes: Establishing a keyword library of the target subject, wherein the keyword library includes certificate information of the target subject and its determined associated parties, at least part of the words or letters in the unit names of the target subject and its determined associated parties, or abbreviations of the unit names; The customer information includes customer certificate information, and the determining of the suspected related party of the target subject according to the matching degree between the customer information of the customer and the keywords in the keyword library of the target subject includes: Determining whether the customer is a suspected related party of the target subject according to the matching degree between the customer certificate information and the certificate information of the target subject in the keyword library or the matching degree between the customer certificate information and the certificate information of the determined related party of the target subject in the keyword library; The determining whether the customer is a suspected associated party of the target subject according to the matching degree between the customer certificate information and the certificate information of the target subject in the keyword library or the matching degree between the customer certificate information and the certificate information of a determined associated party of the target subject in the keyword library includes: Extract the certificate information of the target subject and its determined related party from the keyword library, and match it with the customer certificate information in the system or account storing the customer information at a set time interval. If the match is consistent, the customer is determined as a suspected related party of the target subject; The keyword library of the target subject also includes the customer number of the determined associated party of the target subject; the determining whether the customer is a suspected associated party of the target subject according to the set rules includes: According to the customer number of the determined related party of the target entity, the related persons of the determined related party are extracted from the unified view of corporate customers as suspected related parties, wherein the related persons of the determined related party include the superior legal person and the invested enterprise.

11. A suspected related party determination device, characterized in that: include: one or more processors; A storage device for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 9.

12. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 9 is implemented.

13. A computer program product, comprising computer executable instructions, wherein the computer executable instructions are used to implement the method according to any one of claims 1 to 9 when executed.

Images