Compliance Information Acquisition Device
The compliance information acquisition device addresses the inadequacies of existing systems by efficiently acquiring and processing compliance data from direct trading partners and supply chain companies, enabling comprehensive risk assessment and adherence to regulatory requirements.
Patent Information
- Application Number
- JP2026206425
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2021-07-12
- Filing Date
- 2026-09-15
- Publication Date
- 2026-11-19
AI Technical Summary
Existing compliance systems in corporations are inadequate for identifying risks across the entire supply chain, failing to meet global and domestic regulatory requirements for assessing capital affiliations and conducting comprehensive checks.
A compliance information acquisition device that receives requests for compliance information from designated companies, acquires data from direct trading partners, supply chain companies, and group companies, and outputs the results efficiently, utilizing a server system with various functional units for data processing and risk scoring.
Enables comprehensive and efficient compliance checks throughout the supply chain, providing risk scores and compliance information for all relevant companies, thereby ensuring adherence to laws and regulations.
Smart Images

Figure 2026183092000001_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a compliance information acquisition apparatus.
Background Art
[0002] Currently, the need for compliance in corporations is increasing in order to conduct sound and efficient corporate management. Patent Document 1 discloses a technology that prevents compliance violations in advance by issuing warnings and notifying administrators before violations of laws, regulations, internal rules, etc., based on management of the transaction status of customers.
Prior Art Documents
Patent Documents
[0003]
Patent Document 1
Summary of Invention
Problems to be Solved by the Invention
[0004] At present, the reality is that many Japanese corporations only conduct compliance checks on their direct business partners (Compliance 1.0 in Figure 1). However, global regulations and some domestic regulations require identifying the persons who substantially control the relevant corporation and assessing risks by looking even at the capital affiliations of the relevant customers and business partners (Compliance 2.0 in Figure 1). Furthermore, in the latest trends, not only basic affiliation checks but also compliance checks across the entire supply chain are being required, which means corporations need to carry out enormous amounts of investigation (Compliance 3.0 in Figure 1).
[0005] The present invention has been made in view of such circumstances, and an object thereof is to efficiently and effectively conduct compliance checks through the supply chain.
Means for Solving the Problems
[0006] To achieve the above objective, one aspect of the present invention is: A means of receiving requests for compliance information from designated companies, Acquisition means for acquiring the compliance information of target companies, including trading partners that conduct direct transactions with the specified company, supply chain companies that constitute the supply chain of the specified company and are upstream of the trading partners, and group companies of the trading partners or the supply chain companies. Output means for outputting the acquired compliance information to the designated company, This is a compliance information acquisition device that has [a certain feature]. [Effects of the Invention]
[0007] According to the present invention, compliance checks can be performed efficiently and effectively throughout the supply chain. [Brief explanation of the drawing]
[0008] [Figure 1] This diagram shows the scope of compliance checks. [Figure 2] This diagram shows an overview of compliance checks throughout the supply chain. [Figure 3] This is a diagram illustrating the system configuration. [Figure 4] Block diagram showing the server hardware configuration. [Figure 5] This is a functional block diagram showing an example of the server's functional configuration. [Figure 6] This figure shows an example of CCMM levels and compliance stages. [Figure 7] A flowchart illustrating an example of the compliance information acquisition process. [Figure 8] This flowchart shows an example of the setup process. [Figure 9] This is a flowchart showing the process of receiving a survey request. [Figure 10]This is a flowchart showing an example of screening processing. [Figure 11] This is a flowchart showing an example of supplier evaluation processing. [Figure 12] This is a flowchart showing an example of risk score calculation processing. [Figure 13] This is a diagram showing an example of a score table. [Figure 14] This is a diagram showing an example of a score table. [Figure 15] This is a flowchart showing an example of report creation processing. [Figure 16] This is a flowchart showing an example of status confirmation processing. [Figure 17] This is a diagram showing a display example of a supply chain tree. [Figure 18] This is a flowchart showing an example of name consolidation processing. [Figure 19] This is a diagram showing an example of reference information in the name consolidation processing. [Figure 20] This is a diagram showing an example of reference information in the name consolidation processing. [Detailed Description of the Invention]
[0009] (Embodiment) <Overview> Hereinafter, the present embodiment will be described with reference to the drawings. Figure 2 is a diagram showing an overview of compliance checks through a supply chain. In the present embodiment, an example of checking compliance at a plurality of enterprises constituting the supply chain of a predetermined enterprise will be described.
[0010] In the example of Figure 2, the compliance station (server 1; compliance information acquisition apparatus) accepts a check request for Tier 1 (Supplier A; business partner enterprise) from a predetermined enterprise (customer terminal 2). Here, "specified companies" refer to companies that have suppliers in the supply chain. Examples of specified companies include end-users (companies furthest downstream) and intermediaries in the supply chain. End-users vary depending on the supply chain, but examples include final product manufacturers, trading companies, and telecommunications companies. Examples of intermediaries include parts manufacturers, material manufacturers (intermediate manufacturers), processors, distributors, and wholesalers. Tier 1 refers to a company that is a primary contractor for a designated company and conducts business directly with that company. A check request is a request to obtain compliance information. The Compliance Station receives the Tier 1 company name, address, email address, company number, etc., from the designated company along with the Tier 1 check request.
[0011] Furthermore, the Compliance Station acquires compliance information from Tier 2 (Supplier B; supply chain companies) that constitute the supply chain of a designated company and are upstream of Tier 1. Tier 2 information will be obtained by requesting input from Tier 1. In addition, the Compliance Station acquires compliance information from group companies in Tier 1 to N (where N is a natural number greater than or equal to 2). A supply chain refers to the entire process from the procurement of raw materials and components for a product, to manufacturing, inventory management, distribution, sales, and consumption. In this embodiment, the processes closer to the raw materials in the flow of goods such as raw materials, components, and the final product in the manufacturing process are referred to as upstream, and the processes closer to the final product are referred to as downstream. Tier 2 refers to a company that is a second-tier contractor of the specified company and conducts direct business with Tier 1. In the example in Figure 2, Tier 1 and Tier 2 are shown as companies that make up the specified company's supply chain, but there may be multiple companies (Nth-tier contractors) that make up the specified company's supply chain, such as Tier 3 to N. In this case, information for Tier N is obtained by requesting input from Tier (N-1). Also, in the example in Figure 2, there is one Tier 1 and one Tier 2, but there may be multiple Tier Ns for a single Tier (N-1).
[0012] The Compliance Station acquires compliance information from the aforementioned Tier 1 to N companies and their group companies. Specifically, the Compliance Station acquires compliance information based on information such as corporate databases (DBs) and screening databases (DBs) provided by data providers. The Compliance Station outputs the acquired compliance information as the result of compliance checks to each company, including designated companies.
[0013] Here, compliance refers to a company adhering to laws, social norms, and business ethics. A compliance check is the process of verifying whether or not the aforementioned compliance is being followed. For example, a compliance check may be conducted based on information indicating whether or not the company under investigation is associated with anti-social forces, money laundering, or PEPs (Politically Exposed Persons). A compliance check may also be conducted based on whether or not the company under investigation is listed on national sanctions lists, public lists, or negative corporate information.
[0014] This embodiment describes a platform for checking whether there are companies with compliance issues throughout the supply chain. As described above, when the Compliance Station receives a request for a compliance check from a designated customer company, it accepts information on the company to be checked (Tier 1). The Compliance Station can then check the supply chain from Tier 2 to N. In this embodiment, an example is described in which a score indicating the risk of violating the aforementioned compliance is obtained as compliance information.
[0015] In this embodiment, "enterprises" include individuals (sole proprietors, freelancers, etc.) and corporations. "Corporations" include public corporations (public corporations, public enterprises, public financial institutions, etc.) and private corporations. "Private corporations" include non-profit organizations (NPOs, school corporations, medical corporations, religious corporations, etc.) and for-profit corporations (companies, etc.). "Companies" include limited liability companies, limited partnerships, joint-stock companies, limited partnerships, general partnerships, etc.
[0016] <System Configuration> Figure 3 is a diagram illustrating the schematic configuration of the system according to this embodiment. The system according to this embodiment consists of a server 1 that performs compliance information acquisition processing, and customer terminals 2 and supplier terminals 3 operated by users, which are interconnected via a predetermined network N such as the Internet. In this embodiment, customer terminal 2 is a terminal operated by a person in charge of a predetermined company. Also, in this embodiment, supplier terminal 3 is a terminal operated by a person in charge of a supplier (for example, Ter1). Note that customer terminal 2 may consist of multiple terminals depending on the number of people in charge of a predetermined company, but in this embodiment, they are not particularly distinguished and are referred to as "customer terminal 2". Similarly, supplier terminals may consist of multiple terminals depending on the number of suppliers (Tier1 to N) and the number of people in charge of each supplier, but in this embodiment, they are not particularly distinguished and are referred to as "supplier terminal 3". Note that customer terminal 2 and supplier terminal 3 are, for example, personal computers, tablets, smartphones, etc.
[0017] Server 1 performs various processes in cooperation with the operations of customer terminal 2 and supplier terminal 3. Customer terminal 2 and supplier terminal 3 accept user input and display the processing results of Server 1.
[0018] <Hardware Configuration> Figure 4 is a block diagram showing the hardware configuration of Server 1 according to this embodiment. Server 1 includes a CPU (Central Processing Unit) 11, ROM (Read Only Memory) 12, RAM (Random Access Memory) 13, a bus 14, an input / output interface 15, an output unit 16, an input unit 17, a storage unit 18, a communication unit 19, and a drive 20.
[0019] The CPU 11 executes various processes according to the program stored in the ROM 12 or the program loaded from the storage unit 18 into the RAM 13. The RAM 13 also stores data necessary for the CPU 11 to execute various processes. The CPU 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output interface 15 is also connected to this bus 14.
[0020] The input / output interface 15 is connected to an output unit 16, an input unit 17, a storage unit 18, a communication unit 19, and a drive 20. The output unit 16 consists of a display, speakers, etc., and outputs various information as images and sounds. The input unit 17 consists of a keyboard, mouse, etc., and inputs various information. The storage unit 18 consists of a hard disk, DRAM (Dynamic Random Access Memory), etc., and stores various data. The communication unit 19 communicates with other devices via a network N, including the Internet.
[0021] The drive 20 is appropriately equipped with removable media 21, which may consist of a magnetic disk, optical disk, magneto-optical disk, or semiconductor memory. Programs read from the removable media 21 by the drive 20 are installed in the storage unit 18 as needed. The removable media 21 can also store various types of data stored in the storage unit 18, just like the storage unit 18.
[0022] Although not shown in the diagram, customer terminal 2 and supplier terminal 3 have the hardware configuration shown in Figure 4.
[0023] <Functional Configuration> Figure 5 is a functional block diagram showing an example of the functional configuration of Server 1 according to this embodiment. In the CPU 11 of Server 1, the following functions operate: reception unit 31, acquisition unit 32, output unit 33, setting unit 41, investigation request reception unit 42, screening unit 43, supplier evaluation unit 44, risk score calculation unit 45, report creation unit 46, status confirmation unit 47, and name matching unit 48. In addition, one area of the storage unit 18 is provided with acquisition information DB 51, supplier information DB 52, score DB 53, and risk DB 54. Furthermore, the data provider with which Server 1 exchanges data via the communication unit 19 is provided with a company DB 4, screening DB 5, etc.
[0024] The reception unit 31 receives requests for compliance information from customer terminal 2 (designated company). The reception unit 31 also receives the company name, address, email address, company number, etc. of the Tier 1 company being investigated from customer terminal 2. The reception unit 31 records the received information about Tier 1 in the acquired information DB 51.
[0025] The acquisition unit 32 acquires compliance information of Tier 1 (business partners) that conduct business directly with the designated company. The acquisition unit 32 also acquires compliance information of Tier 2 to N (supply chain companies) that constitute the designated company's supply chain and are upstream of Tier 1. Furthermore, the acquisition unit 32 acquires compliance information of group companies of Tier 1 to N. Tier 1 to N and their group companies are referred to as the companies under investigation (target companies).
[0026] The output unit 33 outputs the compliance information acquired by the acquisition unit 32 to the customer terminal 2. The output unit 33 also displays information indicating compliance risks for Tier 1 to N in a tree structure. Furthermore, the output unit 33 outputs the aforementioned compliance risk information (risk score information) to companies that have provided information on their suppliers (upstream companies with which they conduct direct transactions) among Tier 1 to N. Details of the output unit 33 will be described later.
[0027] Here, the acquisition unit 32 described above includes a setting unit 41, a survey request reception unit 42, a screening unit 43, a supplier evaluation unit 44, a risk score calculation unit 45, a report creation unit 46, a status confirmation unit 47, and a name matching unit 48.
[0028] The configuration unit 41 performs various settings. For example, the configuration unit 41 sets the compliance management level (first setting item) for the customer company. Furthermore, the setting unit 41 sets the scope of compliance management (second setting item). Furthermore, the settings unit 41 sets the types of databases (third setting item) used to acquire compliance information of the companies under investigation. Furthermore, the setting unit 41 sets the type of score (fourth setting item) calculated by the risk score calculation unit 45, which will be described later. The details of the above-mentioned process performed by the setting unit 41 will be explained below.
[0029] As the first setting item (management level for compliance), for example, the setting unit 41 sets the CCMM (Compliance Capability Maturity Model) level. The CCMM level is an indicator of the maturity of management, and can define the company's management level in terms of, for example, the status of master data preparation, risk identification or assessment, and risk reduction.
[0030] Figure 6A shows an example of the CCMM level (and overview (criteria)) according to this embodiment. The higher the company's management level, the higher the CCMM level, and the lower the company's management level, the lower the CCMM level is set. In this embodiment, the CCMM level is described as having five levels as shown in Figure 6A, but it is not limited to this, and may have four or fewer levels or six or more levels. The CCMM level may be set automatically based on the customer company's information, or it may be set manually by the customer company's users. An example of automatically setting the CCMM level will be described below.
[0031] Figure 6B shows an example of a questionnaire for automatically determining (setting) the CCMM level. The Compliance Station prepares a questionnaire and answer choices as shown in Figure 6B in advance and obtains responses to the questionnaire from designated companies. The setting unit 41 then compiles the scores corresponding to the above responses. Here, we will explain an example where the total score is between 0 and 100.
[0032] Figure 6C shows an image illustrating the determination of the CCMM level. The setting unit 41 sets the CCMM level (1 to 5) according to the sum of the above scores (0 to 100).
[0033] Furthermore, the setting unit 41 may set the cost of compliance checks obtained from customer companies higher when the CCMM level is higher. Conversely, the setting unit 41 may set the cost of compliance checks obtained from customer companies lower when the CCMM level is lower. This allows compliance checks to be performed in a way that suits the needs of the customer company.
[0034] As part of the setting of the second setting item (scope of compliance management), for example, the setting unit 41 sets the compliance stage. The compliance stage is an indicator that shows the target of the compliance investigation. For example, "Compliance 1.0" is set when only direct customers or business partners are to be investigated. "Compliance 2.0" is set when, in addition to the targets of the above Compliance 1.0 investigation, companies and individuals in the capital group are also to be investigated. "Compliance 3.0" is set when companies and individuals in the supply chain are to be investigated.
[0035] Figure 6D shows an example of a questionnaire for determining the compliance stage. The compliance station prepares a questionnaire and answer choices as shown in Figure 6D in advance and obtains responses to the questionnaire from designated companies. The setting unit 41 then determines the compliance stage based on the above responses. In this embodiment, an example where "Compliance 3.0" is set as the compliance stage will be described.
[0036] As a setting for the third setting item (types of various databases used to acquire compliance information), for example, the setting unit 41 selects the number and types of corporate databases and screening databases to be used to acquire compliance information, in accordance with the CCMM level and compliance stage set as described above.
[0037] For example, the higher the CCMM level (higher level of corporate management), the more detailed the screening will be, targeting more corporate information. Conversely, the lower the CCMM level (lower level of corporate management), the less detailed the screening will be, targeting less corporate information. For instance, a higher CCMM level may allow for an increase in the types and number of corporate databases and screening databases referenced, while a lower CCMM level may allow for a decrease in the types and number of corporate databases and screening databases referenced.
[0038] Furthermore, for example, the higher the compliance stage (closer to "Compliance 3.0"), the more detailed the screening will be conducted on a larger amount of company information. Conversely, the lower the compliance stage (closer to "Compliance 1.0"), the less detailed the screening will be conducted on a smaller amount of company information. The configuration unit 41 may also select the number and type of company databases and screening databases to be used for acquiring compliance information by combining the CCMM level and compliance stage.
[0039] As part of the setting of the fourth setting item (score type), for example, the setting unit 41 selects a score to be used in the risk score calculation process described later, in accordance with the customer company's risk management policy (e.g., CCMM level or compliance stage). This is suitable, for example, when it is not desired to grasp a wide range of risks. A wide range of risks refers to various risks related to compliance. An example of a situation where it is not desired to grasp a wide range of risks is when it is only desired to know whether the company under investigation is an anti-social force or not, but it is not necessary to know whether or not it is on a sanctions list.
[0040] For example, the number of score types may be increased as the CCMM level increases, and the number of score types may be decreased as the CCMM level decreases. Alternatively, for example, the number of score types may be increased as the compliance stage increases (closer to "Compliance 3.0"), and the number of score types may be decreased as the compliance stage decreases (closer to "Compliance 1.0"). The setting unit 41 may also select the scores to be used in the risk score calculation process by combining the CCMM level and the compliance stage. In this embodiment, an example of calculating the risk score using all scores will be described.
[0041] The investigation request receiving unit 42 accepts the supplier's investigation request based on the information received by the receiving unit 31. The investigation request receiving unit 42 then identifies the supplier company. For example, the investigation request receiving unit 42 may use a predetermined matching engine to identify the supplier's company code, etc., based on the supplier information entered by the customer company.
[0042] The screening unit 43 conducts a survey of the target companies. Specifically, the screening unit 43 requests suppliers (Tier 1) to input information on their primary suppliers (Tier 2). This eliminates the need for the requesting client company to conduct a separate survey targeting Tier 2 suppliers. The screening unit 43 records the acquired information on suppliers (Tier 1 to N) in the supplier information DB 52. When requesting Tier 1 to input Tier 2 information, the screening unit 43 should disclose the requesting client company. This is expected to increase the response rate from Tier 1.
[0043] Similarly, the screening unit 43 requests suppliers (Tier 2 to N-1) to input information on their primary suppliers (Tier 3 to N). When requesting Tier 2 to N-1 to input information on Tier 3 to N, the screening unit 43 should clarify the requesting customer company or purchasing company (downstream company). This is expected to increase the response rate from suppliers by clearly indicating that the request comes from a purchasing company that significantly impacts their own business. The screening unit 43 should obtain information on the group companies of suppliers (Tier 1 to N) based on the aforementioned company DB 4.
[0044] Furthermore, the screening unit 43 screens the companies under investigation according to the compliance management level (CCMM level) of the client company. For example, if the aforementioned management level is lower than a predetermined level, the screening unit 43 uses the company's trade name and address to perform the screening. If the management level is higher than a predetermined level, the screening unit 43 uses the company's trade name and address, as well as its representative, officers, beneficial owners, etc., to perform the screening. This enables compliance checks that are tailored to the management level of the client company that requested the investigation.
[0045] The supplier evaluation unit 44 evaluates suppliers. Specifically, the supplier evaluation unit 44 conducts objective evaluations of suppliers (Tier 1 to N) and also accepts subjective evaluations from suppliers.
[0046] As an objective evaluation, the supplier evaluation unit 44 performs a quantitative evaluation (e.g., calculates a score) based on external data. The external data is not particularly limited, but information posted on web pages, etc. (e.g., news, etc.) may be used. In this case, the supplier's evaluation can be raised or lowered depending on the content of the news, etc. The supplier evaluation unit 44 may also evaluate a supplier based on the number of times that supplier has been the subject of an investigation. For example, if a supplier has been the subject of an investigation many times, it may be given a positive evaluation as a company that is of high interest. The supplier evaluation unit 44 may also evaluate suppliers based on the requesting company. For example, if the requesting company is a large corporation, the supplier may be given a higher evaluation as a trustworthy company.
[0047] As a subjective evaluation, the supplier evaluation unit 44 receives qualitative evaluations of suppliers (e.g., Tier 2) from the product purchaser (e.g., Tier 1). For example, the supplier evaluation unit 44 receives qualitative evaluations and comments on the telephone and email responses of the person in charge, quality, environmental awareness, compliance awareness, etc. Information such as personnel changes and resignations may also be collected and stored in the supplier information DB 52, thereby ensuring that the latest information is always maintained.
[0048] The score information obtained through the above evaluation should be stored on Server 1. This will allow for the accumulation of useful information about the source of the survey requests, such as identifying companies that have made many survey requests and those that are involved in new businesses.
[0049] The risk score calculation unit 45 calculates a risk score related to compliance. In this embodiment, the risk score is calculated not only for the client company's direct trading partners (Tier 1), but also for the supply chain companies that constitute the supply chain (Tier 2 to N), and further for the target companies including these group companies. In this embodiment, an example will be described in which the risk score calculation unit 45 calculates a compliance risk score based on six scores: corporate risk score, information disclosure score, competitor evaluation score, trading partner risk score, business activity score, and screening score. The company risk score is calculated based on company information obtained from sources such as the Company Database (DB4). This company information includes items such as the company's region (headquarters), whether it is publicly listed, its industry, and whether it imports goods. The company risk score is calculated based on the content of these items. The information disclosure score is a score assigned based on the degree to which a company discloses its information. For example, in this embodiment, the information disclosure score is assigned depending on whether or not various pieces of company information, such as the company's website, representative, officers, shareholders, sales, number of employees, and financial information, are publicly available. The competitor evaluation score is a score assigned based on subjective evaluations of the surveyed company (e.g., word-of-mouth). Evaluation items include, for example, delivery time, quality, telephone or email responsiveness, environmental awareness, and compliance awareness. The competitor evaluation score is assigned based on the evaluation values for each item. The supplier risk score is a score assigned based on the compliance risks of the supplier to the company being investigated. For example, the supplier risk score is assigned based on whether or not the company has had transactions with high-risk companies in the past (including other supply chains). The business activity score is a score assigned based on the number of compliance-related investigations conducted. The screening score is a score assigned based on the screening results performed in step S3. Details regarding the calculation of each score will be described later. The risk score calculation unit 45 calculates the risk score based on the scores recorded in the score DB 53. The risk score calculation unit 45 also records the calculated risk score in the risk DB 54.
[0050] The report generation unit 46 creates a compliance report. In this embodiment, the report generation unit 46 collects company information and screening results from the above-mentioned multiple information sources and creates a report.
[0051] The status confirmation unit 47 checks the compliance status in the supply chain. In this embodiment, the status confirmation unit 47 creates a supply chain tree as a result of the investigation, visually connecting the investigation requester (customer company) and suppliers (Tier 1 to N). The created supply chain tree is controlled by the output unit 33 to be displayed on the customer terminal 2 (or supplier terminal 3). This allows the user to grasp information regarding compliance throughout the entire supply chain. In addition, the user can see at a glance which suppliers have what level of risk on the tree.
[0052] The data matching unit 48 performs data matching on individuals (representatives, officers, shareholders, etc.). Specifically, the data matching unit 48 performs data matching based on information on representatives, officers, shareholders, etc. collected by Server 1 (platform; compliance station) through the above-mentioned investigation. This allows for linking with the results of investigations of other companies (for example, investigations conducted in the past), enabling appropriate risk assessment. In this embodiment, an example of performing data matching as one function when conducting a compliance check of the entire supply chain is described, but it is not limited to this. For example, even when conducting a compliance check targeting only the business partners of a given company, or only the group companies of that company, data matching processing can be performed to effectively conduct a compliance check. That is, when conducting a compliance check of a target company, a risk score may be calculated as compliance information based on information of companies related to at least one of the representatives, officers, or shareholders of the target company.
[0053] The acquired information DB51 is a database that stores information about Tier 1 received by the reception unit 31.
[0054] The supplier information DB52 is a database that stores information about suppliers (Tier 1 to N) acquired by the screening unit 43. The supplier information DB52 also stores information acquired by the supplier evaluation unit 44, such as personnel changes and retirements within supplier companies.
[0055] The score DB53 is a database that stores various scores referenced by the risk score calculation unit 45.
[0056] Risk DB54 is a database that stores the risk scores calculated by the risk score calculation unit 45.
[0057] Corporate DB4 is a database containing corporate information provided by various data providers. In this embodiment, a corporate database from an external data provider is used, but the corporate information may also be located within Server 1.
[0058] Screening DB5 is a database provided by various data providers. Screening DB5 stores information that is subject to compliance violations, such as antisocial forces, money laundering, sanctions lists, blacklists, and PEPs.
[0059] <Compliance Information Acquisition Process> Figure 7 is a flowchart showing the operation of the compliance information acquisition process according to this embodiment. In step S1, the configuration unit 41 sets the CCMM level, compliance stage, company database, cleaning database, and appropriate score. In step S2, the investigation request reception unit 42 receives investigation requests from suppliers. In step S3, the screening unit 43 conducts an investigation of the target companies based on the CCMM level described above. In step S4, the supplier evaluation unit 44 conducts objective evaluations of suppliers (Tier 1 to N) and also accepts subjective evaluations from suppliers. In step S5, the risk score calculation unit 45 calculates a risk score related to compliance. In step S6, the report creation unit 46 creates a compliance report. In step S7, the status confirmation unit 47 confirms the compliance status in the supply chain. In step S8, the name matching unit 48 performs name matching of individuals (representatives, officers, shareholders, etc.). The details of steps S1 to S8 are explained below.
[0060] ≪Step S1: Setup Process≫ Figure 8 shows an example of the setting process (step S1) performed by the setting unit 41 according to this embodiment.
[0061] In step S11, the setting unit 41 sets the CCMM level and compliance stage. In this embodiment, the CCMM level is set automatically based on the customer company's information, but it may also be set manually by the customer company's users.
[0062] In step S12, the configuration unit 41 sets (selects) the types of corporate databases and screening databases to be used to acquire compliance information, according to the CCMM level or compliance stage described above.
[0063] In step S13, the setting unit 41 sets the type of score to be used (applied) when calculating the risk score in step S5, according to the CCMM level or compliance stage described above.
[0064] Step S2: Processing of Investigation Request Received Figure 9 shows an example of the investigation request reception process (step S2) performed by the investigation request reception unit 42 according to this embodiment.
[0065] In step S21, the survey request reception unit 42 accepts the input of supplier company information (Tier 1) based on the information received by the reception unit 31.
[0066] In step S22, it is determined whether the supplier's company information mentioned above includes a corporate number or company code. If it does, the process proceeds to step S23; otherwise, the process proceeds to step S24.
[0067] In step S23, the investigation request receiving department 42 identifies the supplier's company information using the corporate number or company code.
[0068] In step S24, the survey request reception unit 42 performs matching based on the supplier's company name and address. For example, the survey request reception unit 42 performs the above matching using a predetermined matching engine.
[0069] In step S25, the survey request reception unit 42 displays (retrieves) the matching results described above.
[0070] In step S26, the survey request receiving unit 42 selects a company that is a supplier from the list of matching results. For example, the survey request receiving unit 42 selects the company with the highest degree of matching. Alternatively, the unit may select a company from the list of matching results depending on the user's selection.
[0071] In step S27, the survey request reception unit 42 obtains the company code of the company selected in step S26.
[0072] In step S28, the survey request reception unit 42 accepts input such as the name of the supplier's contact person, email address, and target product based on the supplier's company information. By identifying the target product, the survey described below can be conducted on supply chain companies that match the customer company's target product.
[0073] In step S29, the investigation request reception unit 42 completes the investigation request reception process, and the process proceeds to step S3.
[0074] ≪Step S3: Screening Process≫ Figure 10 shows an example of a screening process (step S3) performed by the screening unit 43 according to this embodiment.
[0075] In step S311, the screening unit 43 begins investigating the supplier (Tier 1). In this embodiment, the processes described in steps S321 to S323 are executed simultaneously with the investigation from step S311 onward.
[0076] In step S312, the screening unit 43 determines whether the compliance stage is 2.0 or higher. If the compliance stage is 2.0 or higher (2.0 or 3.0), the process proceeds to step S314; if the compliance stage is less than 2.0 (1.0), the process proceeds to step S313.
[0077] In step S313, the screening unit 43 obtains the official trade name and address of the company (Tier 1) identified in step S2, as well as information on the representative and officers obtained in step S323, which will be described later.
[0078] In step S314, the screening unit 43 uses the company code obtained in step S2 as a key to refer to the company database and obtains information on the supplier (Tier 1), including its official trade name, address, representative, officers, shareholders, and beneficial owner.
[0079] In step S315, the screening unit 43 compares the information obtained in step S313 or S314 with the information obtained in step S323, which will be described later. The screening unit 43 may also issue an alert if the comparison results are different (inconsistent). For example, if the supplier information obtained in step S323 (information entered by the customer company) is compared with the information of an external vendor (data provider) obtained in step S313 or S314 and the representative, officers, and beneficial owners are different, the screening unit 43 may display an alert on the customer terminal 2 such as, "The representative, officers, and beneficial owners do not match." This allows the customer company to recognize if the supplier (Tier 1)'s representative has entered incorrect information or if the representative, etc., has changed.
[0080] In step S316, the screening unit 43 inputs the information obtained by the above-described process into a screening format.
[0081] In step S317, the screening unit 43 connects to the screening DB5 configured in step S1.
[0082] In step S318, the screening unit 43 sends a file (data) in the above format to the data provider that manages the connected screening DB5.
[0083] In step S319, the screening unit 43 performs screening.
[0084] In step S320, the screening unit 43 acquires the file (data) output as a result of the screening. The acquired data is stored in the supplier information DB 52.
[0085] In step S321, the screening unit 43 requests the supplier under investigation (Tier 1) to input information about its primary supplier (Tier 2). For example, the screening unit 43 sends an email to the supplier terminal 3 requesting Tier 1 to input information about Tier 2. This email may include, for example, information for logging into the system according to this embodiment.
[0086] In step S322, the screening unit 43 receives a login request to the system according to this embodiment from a representative of the supplier (Tier 1) to be investigated.
[0087] In step S323, the screening unit 43 receives input from the person in charge of the supplier (Tier 1) under investigation, including information such as the representative, officers, shareholders, and beneficial owners. The process then proceeds to step S2. This allows the acquisition of the supplier (Tier 2) company information obtained in step S321. By performing steps S2 and S3 multiple times, company information for Tier 2 through N can be acquired.
[0088] Step S4: Supplier Evaluation Process Figure 11 shows an example of the supplier evaluation process (step S4) performed by the supplier evaluation unit 44 according to this embodiment.
[0089] In step S41, the supplier evaluation unit 44 begins evaluating the suppliers. Here, we will evaluate the supplier (Tier 1), but the process described later will be carried out similarly for suppliers (Tier 2 to N).
[0090] In step S42, the supplier evaluation unit 44 determines whether the supplier to be evaluated is a supplier that was recently investigated (within a predetermined period). If it is a supplier that was recently evaluated, the process proceeds to step S43; otherwise, the process proceeds to step S44.
[0091] In step S43, the supplier evaluation unit 44 displays a list of suppliers that have been investigated in the past, focusing on a predetermined period. The display is shown to the terminals of the personnel (evaluators) of companies that have direct business dealings with the suppliers being evaluated.
[0092] In step S44, the supplier evaluation unit 44 searches for suppliers to be evaluated.
[0093] In step S45, the supplier evaluation unit 44 displays a list of search results. As described above, the target of the display is the evaluator's terminal.
[0094] In step S46, the supplier evaluation unit 44 selects a supplier to evaluate from the list.
[0095] In step S47, the supplier evaluation unit 44 receives input from the evaluator regarding the evaluation of the supplier to be evaluated. For example, it accepts qualitative evaluations and comments such as the person in charge's telephone response, email response, quality, environmental awareness, and compliance awareness.
[0096] In step S48, the supplier evaluation unit 44 calculates the supplier's evaluation score by including past evaluations and the evaluation received in step S47, if evaluations have been conducted in the past. For example, the supplier evaluation unit 44 can use the average value of past evaluations and the evaluation received in step S47 as the supplier's evaluation score.
[0097] In the examples of steps S41 to S48 described above, we explained an example of performing a subjective evaluation (qualitative evaluation) by the evaluator. However, objective evaluations (quantitative evaluations) based on information such as web pages may also be performed, or a combination of these may be used.
[0098] Step S5: Risk Score Calculation Process Figure 12 shows an example of the risk score calculation process (step S5) performed by the risk score calculation unit 45 according to this embodiment. In this embodiment, the risk score calculation unit 45 calculates a compliance risk score by integrating six scores: corporate risk score, information disclosure score, competitor evaluation score, business partner risk score, business activity score, and screening score. In this embodiment, a higher score indicates a higher risk of compliance violation, and a lower score indicates a lower risk of compliance violation. Here, we will calculate a risk score for the supplier (Tier 1), but the process described later will also be applied to suppliers (Tier 2 to N) and their group companies, etc.
[0099] In step S51, the risk score calculation unit 45 calculates a company risk score based on the supplier's attribute information. Attribute information can be obtained from the company DB4. Examples of attribute information include region, whether the company is listed on the stock exchange, industry, and whether it engages in imports or exports. The risk score calculation unit 45 calculates the total or average value of the scores corresponding to these items as the company risk score.
[0100] Figure 13A is a corporate risk score table that associates attribute information with corporate risk scores according to this embodiment. For example, as shown in Figure 13A, the corporate risk score table is a table in which a five-level score is assigned to the region (location), whether or not the company is listed, the industry, whether or not it imports, etc. of the company under investigation. The risk score calculation unit 45 calculates the corporate risk score using the corporate risk score table shown in Figure 13A. For example, if the company under investigation is located in Japan, is a listed company, is in the financial industry, and does not import, a corporate risk score of 7 (=1+1+4+1) is assigned.
[0101] In step S52, the risk score calculation unit 45 assigns an information disclosure score to the supplier based on the degree to which corporate information has been collected (the percentage that has been collected).
[0102] Figure 13B is an information disclosure score table that associates company information with a score corresponding to the presence or absence of said company information according to this embodiment. For example, as shown in Figure 13B, the information disclosure score table is a table in which a score is assigned on a 5-point scale depending on whether or not information for each item is publicly available. The risk score calculation unit 45 calculates the information disclosure score using the information disclosure score table shown in Figure 13B. For example, if information for all items shown in Figure 13B is publicly available, an information disclosure score of 7 is assigned. Note that if sufficient information cannot be obtained as a result of attempts to collect information from external data, publicly available data, etc., the information disclosure score may be considered low.
[0103] In step S53, the risk score calculation unit 45 assigns a competitor evaluation score (a second score indicating the evaluation from other companies) based on the supplier evaluation by other companies in step S4.
[0104] Figure 13C shows an example of a competitor evaluation score (supplier evaluation score) according to this embodiment. For example, as shown in Figure 13C, the competitor evaluation score can be a five-level evaluation: "1: Very good", "2: Good", "3: Average", "4: Poor", and "5: Very bad".
[0105] In step S54, the risk score calculation unit 45 assigns a supplier risk score based on whether or not there have been transactions with high-risk companies in the present or past. For example, even if there are no high-risk companies among the suppliers of Tier 1 company A (e.g., company B) in company T's supply chain (SC1 below), there may be high-risk companies among the suppliers of Tier 1 company A (e.g., company C) in company S's supply chain (SC2 below). In this case, company A's supplier risk score will also be increased in company T's supply chain. This makes it possible to generate risk information that takes into account different supply chains (supplies for different industries or target products). The risk score can also be considered as a score that shows a high value when there are transactions with high-risk companies in the present or past (first score). SC1: Company T (customer company) Company A (Tier 1) Company B (Tier 2) SC2: Company S (customer company) Company A (Tier 1) Company C (Tier 2)
[0106] Figure 14A shows an example of a supplier risk score according to this embodiment. The supplier risk score of the company (the company under investigation) is determined by referring to the compliance risk scores of its suppliers in its own supply chain and the supply chains of other companies. In addition, the supplier risk score of the company is determined by referring to the compliance risk scores of the ordering parties (the company under investigation) of its suppliers in the supply chains of other companies. Specifically, for example, in the case of SC1 and SC2 mentioned above, the supplier risk score for Company A (the company under investigation) is determined as follows: Company B's compliance risk score of "1" in Company T's supply chain and Company C's compliance risk score of "4" in Company S's supply chain are referenced. Additionally, Company A's compliance risk score of "7" in Company S's supply chain is referenced. The sum or average of these values is then determined as the supplier risk score. Furthermore, if there are multiple supply chains from other companies, for example, their average value can be used as a compliance risk score.
[0107] In step S55, the risk score calculation unit 45 assigns a business activity score based on the number of times other companies have investigated the supplier in the past.
[0108] Figure 14B shows an example of a business activity score table according to this embodiment. For example, as shown in Figure 14B, the business activity score table is a table in which a supplier is assigned a score on a 5-point scale according to the situation (sudden increase, sharp decrease, consistently low, consistently high, etc.) based on the number of times the supplier has been surveyed in the past (number of surveyed cases). Alternatively, the business activity score may be assigned based on the number of surveyed cases itself, such as setting the score to 1 when the number of surveyed cases is 1 to 10, and setting the score to 2 when the number of surveyed cases is 11 to 29.
[0109] In step S56, the risk score calculation unit 45 assigns a screening score. The risk score calculation unit 45, for example, refers to the screening results and assigns a screening score based on the risk category, stage (such as the progress of the confirmed crime), and timing of occurrence.
[0110] Figure 14C shows an example of a screening score table according to this embodiment. For example, the screening score table shown in Figure 14C is a table that lists risk categories and assigns scores according to their stages. Risk categories include serious risks (terrorism-related, money laundering, sanctions lists, etc.), high risks (smuggling, espionage, document forgery, etc.), and cautionary risks (environmental violations, copyright infringement, illegal gambling, etc.). Stages include accusation / investigation, arrest / indictment, appeal / settlement, and finalization of sentence. As shown in Figure 14C, it is preferable to set the scores so that serious risks have higher scores and cautionary risks have lower scores.
[0111] In step S57, the risk score calculation unit 45 calculates the compliance risk score. In this embodiment, the risk score calculation unit 45 integrates the six scores obtained in steps S51 to S56 to calculate the compliance risk score. The calculated compliance risk score is stored in the risk DB 54.
[0112] Figure 14D shows an example of a compliance risk score according to this embodiment. As shown in Figure 14D, for the six scores obtained in steps S51 to S56, a compliance risk score (coefficient × score) and the sum of each score are calculated based on a (predetermined) coefficient and a score (reference value).
[0113] In steps S52 to S57, the risk score calculation unit 45 can output the sum or average value of the corresponding scores as the output value for each score. The mapping of each score is not limited to the examples shown in Figures 13A to 13C and 14A to 14D, and any table may be used. In this embodiment, each score table is assumed to be recorded in the score DB 53.
[0114] ≪Step S6: Report Creation Process≫ Figure 15 shows an example of the report creation process (step S6) performed by the report creation unit 46 according to this embodiment.
[0115] In step S61, the report creation unit 46 inputs the supplier's company information into the report.
[0116] In step S62, the report generation unit 46 inputs the screening results performed in step S3 into the report.
[0117] In step S63, the report creation unit 46 sets each score calculated in step S5 into the report.
[0118] In step S64, the report creation unit 46 saves the report created in steps S61 to S63 to the supplier information DB 52 on server 1.
[0119] In step S65, the report creation unit 46 notifies the customer terminal 2 (the requesting customer company) that the report creation is complete.
[0120] In step S66, the report creation unit 46 receives an access request from the customer terminal 2 to the report on server 1. This allows the requesting company to access the report and review its contents.
[0121] Step S7: Status Confirmation Process Figure 16 shows an example of the status confirmation process (step S7) performed by the status confirmation unit 47 according to this embodiment.
[0122] In step S71, the status confirmation unit 47 creates a supply chain tree. An example of the supply chain tree display will be described later using Figures 17A and 17B.
[0123] In step S72, the status confirmation unit 47 visually connects the investigation requester (customer company) and the supplier to create a supply chain tree. The investigation requester and the supplier are displayed with predetermined icons. The icons for the investigation requester and the supplier may be the same or different.
[0124] In step S73, the status confirmation unit 47 adds color to the icons on the supply chain tree for companies for which a report has been prepared in step S6. The status confirmation unit 47 adds a color (information about the risk score) to the icon according to the compliance risk score, for example, using a predetermined threshold. Specifically, the status confirmation unit 47 adds green to the icon if the compliance risk score is lower than the first threshold, yellow if it is higher than the first threshold but lower than the second threshold, and red if it is higher than the second threshold. The status confirmation unit 47 may also add gray to the icon if no response has been received.
[0125] In step S74, the status confirmation unit 47 displays an alert for companies that did not register supplier information in step S2. For example, the status confirmation unit 47 can display a gray icon for companies that have not registered supplier information (companies that have not responded), as described above, and then display a message such as, "We can send reminders to companies that have not responded."
[0126] In step S75, the status confirmation unit 47 displays information about the company corresponding to the icon selected by the user. This allows the user to refer to the information of the selected company. It is recommended that the user from the requesting customer company only be able to refer to the company name and address of Tier 1 companies. This is because suppliers (Tier 1) often do not want their suppliers (Tier 2) to be known to the purchasing company (customer company).
[0127] In step S76, the status confirmation unit 47 prompts companies that have not registered supplier information to register it. For example, the status confirmation unit 47 makes the above prompt if no response is received after a predetermined period of time. Also, for example, the status confirmation unit 47 makes the above prompt if requested by a user. A user can request a prompt from the server 1 by selecting an icon or the above alert message. In this embodiment, a company downstream in the supply chain from a company that has not responded (the purchasing company or a designated company) can make the above prompt. In addition, the name of the company that requested the prompt may be disclosed to the company that has not responded. The name of the company that has not responded may also be disclosed to the user.
[0128] In step S77, the status confirmation unit 47 receives information input from the supplier. For example, if the supplier is the furthest upstream supplier (Tier N), they can input that the supplier does not exist.
[0129] In step S78, the status confirmation unit 47 requests a detailed investigation from suppliers with high risk. The request for a detailed investigation may be automatically sent from server 1 to companies whose risk exceeds a predetermined value, or it may be sent according to the user's instructions. Here, the detailed investigation is assumed to be a compliance risk investigation conducted by specialized investigators, as in the past.
[0130] In step S79, the status confirmation unit 47 displays a progress rate indicating how far the investigation has progressed. For example, the status confirmation unit 47 displays the number of suppliers in the supply chain, the number of low-risk companies, the number of medium-risk companies, the number of high-risk companies, the number of companies that have not responded, the investigation progress rate (response rate), etc. This allows the user to grasp at a glance how much of the entire supply chain has been investigated.
[0131] In step S80, the status confirmation unit 47 notifies the user of any changes in company information or investigation status within the supply chain. This allows the user to receive and understand the changes in real time.
[0132] The status confirmation unit 47 may also calculate the average number of suppliers based on pre-registered information on parts or materials. This allows the unit to issue an alert if the number of suppliers for a particular part or material is extremely low, indicating that there may be no suitable suppliers registered.
[0133] Furthermore, the status confirmation unit 47 may allow a supplier (e.g., Tier 1) to view a risk overview of its suppliers (e.g., Tier 2) free of charge if the supplier registers information about its suppliers. This can provide an incentive for suppliers to register information about their suppliers. The risk overview that suppliers (e.g., Tier 1) can view includes information indicating the supplier's risks as described above, as well as information such as the supplier's suitability and the progress rate of the investigation. Detailed information such as company names and addresses of suppliers other than the supplier's own (e.g., Tier 2) (e.g., Tier 3 to N) will not be viewable. Details will be described later using Figure 17B.
[0134] Figure 17A shows an example of a supply chain tree displayed on the customer terminal 2 in this embodiment. In Figure 17A, the customer company that requested the investigation, "AZ Electric Co., Ltd.," the trading partners (Tier 1) that directly deal with the customer company, "ABC Co., Ltd.," "XYZ Industrial Co., Ltd.," and "Iroha Industrial Co., Ltd.," and the supply chain companies (Tier 2 to N) are displayed as icons. In this embodiment, as shown in Figure 17A, the customer company user only sees the company name and address of Tier 1 companies, but does not see company name or other information for Tier 2 to N companies. The status confirmation unit 47 may also display risk information for group companies of Tier 1 to N companies. Furthermore, when displaying risk information for Tier 1 to N companies, the status confirmation unit 47 may also take into account the risk information of each group company. For example, the status confirmation unit 47 may display risk information based on the risk information of group companies and the average risk score of the company under investigation (any of Tier 1 to N).
[0135] Figure 17B shows an example of a supply chain tree displayed on the supplier terminal 3 in this embodiment. In the example shown in Figure 17B, the supply chain tree displayed on the supplier terminal 3 of "ABC Corporation," which is Tier 1, is shown. "ABC Corporation" has registered information of its suppliers (Tier 2), "AB Construction Co., Ltd." and "AC Industry Co., Ltd.", with the server 1. Therefore, detailed information such as company names can be viewed for these companies, but for other companies, only a risk overview can be viewed. Note that there is no particular limit to whether or not detailed information is displayed for companies downstream from the supplier (Tier 1) whose information is registered for one's own suppliers (e.g., Tier 2). For example, as shown in Figure 17B, only detailed information for the company one level downstream (e.g., a customer company) may be displayed.
[0136] Step S8: Data matching process Figure 18 shows an example of the name matching process (step S8) performed by the name matching unit 48 according to this embodiment.
[0137] In step S81, the name matching unit 48 lists companies that have individuals with the same name from among companies that have been investigated in the past, based on personal information related to the companies under investigation.
[0138] Figure 19A shows an example of a company being surveyed. In the example shown in Figure 19A, personal information related to the surveyed company, "P Trading Co., Ltd.", is obtained. For example, the information of executive "Ichiro Sato" is obtained.
[0139] Figure 19B shows an example of a listed company. In Figure 19B, companies that have been surveyed in the past have individuals with the same name as "P Trading Co., Ltd."
[0140] In step S82, the data matching unit 48 assigns levels (reliability ratings) to the listed companies based on the degree of agreement between the companies under investigation and the listed companies. For example, to confirm that an individual is the same person, the data matching unit 48 compares the attributes of the companies under investigation with those of the listed companies and checks the degree of agreement. Then, the data matching unit 48 assigns a degree of agreement such as A, B, C, N to each item and assigns levels according to that degree of agreement.
[0141] Figure 19C shows an example of the degree of agreement and level classification. Each item is assigned a level (confidence level) based on the degree of agreement: "A: Match," "B: Partial Match," "C: Mismatch," and "N: No Data." For example, if all items match, the confidence level can be set to 7, and if all items do not match, the confidence level can be set to 0.
[0142] Figure 20A shows detailed information about the surveyed companies. Figure 20B shows an example of companies listed from those previously surveyed, along with the degree of agreement and level of matching among them. In the examples shown in Figures 20A and 20B, the name of the representative of "P Trading Co., Ltd." matches the name of the representative of "V Co., Ltd." and the name of an officer of "W Association." Also in the examples shown in Figures 20A and 20B, the names of officers of "P Trading Co., Ltd." match the names of officers of "X Co., Ltd." and "Y Co., Ltd."
[0143] In step S83, the data matching unit 48 evaluates the risks of the listed companies. For example, if the reliability (matching) of the listed companies is above a predetermined value, the data matching unit 48 increases the score of the corresponding company under investigation (for example, the competitor evaluation score assigned in step S53). The data matching unit 48 may also notify the customer terminal 2 if the reliability of the listed companies is above a predetermined value.
[0144] <Advantageous effects of this embodiment> According to the above-described embodiment, compliance checks can be conducted more efficiently and effectively throughout the supply chain than traditional compliance checks performed by specialized investigators.
[0145] Furthermore, by conducting compliance checks according to the CCMM level and compliance stage, it is possible to perform compliance checks that meet the needs of the client company.
[0146] Furthermore, by requesting suppliers to input information on their primary suppliers, it is possible to efficiently obtain information on companies that make up the supply chain. In this case, disclosing the customer company or purchasing company (downstream company) that is making the request to the supplier can be expected to increase the response rate from the supplier.
[0147] Furthermore, by calculating a compliance risk score using evaluation scores from other companies, it is possible to calculate a score based on qualitative evaluations (such as word-of-mouth) from other companies. In addition, by calculating a compliance risk score using supplier scores, it is possible to consider whether suppliers are doing business with risky companies beyond one's own supply chain.
[0148] Furthermore, by creating a supply chain tree based on the survey results, it is possible to grasp information regarding compliance across the entire supply chain. In addition, by allowing suppliers to view a risk overview of their suppliers free of charge if they register their supplier information, it can be incentivized for suppliers to register their supplier information. Moreover, by making detailed information such as company names viewable only for first-tier suppliers in the supply chain tree, it is possible to prevent the leakage of information about suppliers that first-tier suppliers do not want to be known to other companies.
[0149] Furthermore, by performing data matching and compliance checks, it is possible to make appropriate risk assessments.
[0150] Although one embodiment of the present invention has been described above, the present invention is not limited to the embodiments described above, and any modifications, improvements, etc. that can achieve the objectives of the present invention are included in the present invention.
[0151] (modified version) In the embodiments described above, the compliance checks may be performed continuously (for example, once a year). This allows compliance checks to be conducted in light of the latest information, thereby increasing reliability.
[0152] In the embodiments described above, an example of conducting compliance checks on upstream companies in the supply chain was explained, but compliance checks may also be conducted on downstream companies of any trading partner. This makes it possible to conduct compliance checks that take into account the ordering companies (downstream companies) of the customer company's suppliers.
[0153] The series of processes described above can be executed by hardware or by software. In other words, the functional configuration in Figure 5 is merely an example and is not particularly limited. That is, it is sufficient for the system to have the functionality to execute the series of processes described above as a whole, and the type of functional block used to realize this functionality is not particularly limited to the example in Figure 5. Furthermore, the location of the functional blocks is not particularly limited to Figure 5 and can be arbitrary. For example, the functional blocks of the server may be transferred to customer terminals or supplier terminals, etc. Conversely, the functional blocks of customer terminals or supplier terminals may be transferred to the server, etc. Also, a single functional block may be composed of hardware alone, software alone, or a combination of both.
[0154] When a series of processes are executed by software, the programs that make up that software are installed on a computer or other device from a network or storage medium. The computer may be a computer built into dedicated hardware. Alternatively, the computer may be a computer capable of performing various functions by installing various programs, such as a server, a general-purpose smartphone, or a personal computer.
[0155] Such recording media containing programs may consist not only of removable media (not shown) distributed separately from the main unit to provide programs to users, but also of recording media provided to users, etc., that are pre-installed in the main unit.
[0156] In this specification, the step of describing a program to be recorded on a recording medium includes not only processes that are performed chronologically in that order, but also processes that are not necessarily performed chronologically, but are executed in parallel or individually. Furthermore, in this specification, the term "system" refers to an overall system composed of multiple devices, means, etc. [Explanation of symbols]
[0157] 1: Server 2: Customer terminal 3: Supplier terminal 11:CPU 18:Storage section 19:Communication section 31: Reception Unit 32: Acquisition Unit 33: Output Unit 45: Risk score calculation unit
Claims
1. A means of receiving requests for compliance information from designated companies, A setting means for setting the level of compliance management at the specified company in accordance with the score based on the response to the first questionnaire obtained from the specified company, Depending on the management level, the type or number of corporate databases or screening databases to be used to acquire the compliance information are selected, and acquisition means for acquiring the compliance information of the target company using the selected corporate databases or screening databases, Output means for outputting the acquired compliance information to the designated company, A compliance information acquisition device having the following features.
2. The acquisition means increases the number or types of the corporate database or the screening database as the management level increases. The compliance information acquisition device according to claim 1.
3. The setting means further sets compliance stages indicating the scope of compliance investigations based on responses to a second questionnaire obtained from the designated company, The acquisition means selects the type or number of the corporate database or the screening database according to the combination of the management level and the compliance stage. The compliance information acquisition device according to claim 2.
4. The setting means further sets the type of score used to calculate the risk score of the target company according to the management level or compliance stage, The compliance information acquisition device further comprises a calculation means for calculating the risk score of the target company based on the set type of score. The compliance information acquisition device according to claim 3.
5. The setting means increases the number of score types as the management level or compliance stage increases. The compliance information acquisition device according to claim 4.
6. The setting means aggregates the scores corresponding to the responses to the first questionnaire obtained from the predetermined company, and sets the management level according to the total value of the aggregated scores. The compliance information acquisition device according to claim 5.
7. The compliance stages include a first stage in which only business partners that conduct direct transactions with the designated company are investigated, a second stage in which, in addition to the business partners, companies that have capital relationships with the business partners are investigated, and a third stage in which companies upstream of the business partners are investigated. The compliance information acquisition device according to claim 6.
8. The process involves receiving requests for compliance information from designated companies, and A setting step to set the level of compliance management at the specified company in accordance with the score based on the response to the first questionnaire obtained from the specified company, Depending on the management level, the type or number of corporate databases or screening databases to be used to acquire the compliance information are selected, and the acquisition step involves using the selected corporate databases or screening databases to acquire the compliance information of the target company. An output step which outputs the acquired compliance information to the designated company, A method for obtaining compliance information performed by a computer.
9. The process involves receiving requests for compliance information from designated companies, and A setting step to set the level of compliance management at the specified company in accordance with the score based on the response to the first questionnaire obtained from the specified company, Depending on the management level, the type or number of corporate databases or screening databases to be used to acquire the compliance information are selected, and the acquisition step involves using the selected corporate databases or screening databases to acquire the compliance information of the target company. An output step which outputs the acquired compliance information to the designated company, A program that causes a computer to execute something.
Citation Information
Patent Citations
Business support system
JP2019057142A
