JP5922089B2 - Credit management system and method using exchange statement information - Google Patents

Description

  The present invention relates to a credit management system and method using exchange statement information.

  When a financial institution makes a loan to a customer, a determination is made as to whether or not how much credit can be provided to the customer and so-called credit determination. What is important in making this determination is managing information such as receivables and payables of customer customers, and sales partners and suppliers to customer customers (this is called credit management). If this credit management is not performed properly, it is impossible to grasp abnormal information such as that the payment from the customer of the customer of the customer is delayed or the customer went bankrupt, and the loan with high risk (In the worst case, the loan may not be collected). Therefore, there is a need for a system and method for managing customer customer credit.

  However, the number of customers and suppliers in one customer is not always one, and there may be many accounts to handle, and it is not easy to manage them. Furthermore, since one customer customer may have a plurality of accounts, and the plurality of accounts are not related as information, the deposit and withdrawal for the plurality of accounts are centrally managed as information of one customer customer. It is not easy.

  If it is possible to centrally manage the deposit / withdrawal information of customers and customers, for example, when making credit decisions, it is possible to grasp abnormal information such as the fact that deposits from customers are delayed or bankrupt, etc. There is a need for a system and method that can provide reliable credit management. In addition, it is also required to utilize such information for business promotion for the business partner customers by grasping the business partner customer information collectively.

In order to achieve such an object, the present invention is a system for managing credit data of a customer for a financial institution using exchange statement data, and the system includes:
Means for creating commercial flow data based on the customer and vendor data of the customer,
A means for executing a name identification process for the exchange statement data, wherein the name identification process includes summarizing data relating to the same commercial flow in the exchange statement data and the customer of the customer included in the exchange statement data. By converting the character string included in each company name of the seller and the supplier into a predetermined character string, and associating the converted character string with the company name in the company attribute data, the exchange statement Means for recognizing data relating to the same company in the data;
Means for extracting deposit / withdrawal data of the customer from the exchange statement data subjected to the name identification process, summarizing data relating to the same commercial flow, and creating commercial flow detailed statement data. Features.

Further, in the invention described in the preceding paragraph, a means for creating alarm data of the customer for the customer based on the merchandise exchange statement data and bankruptcy data, the alarm data being bankrupt by the customer Data indicating at least one of the following: bankruptcy of the seller, bankruptcy of the supplier, and a decrease in a predetermined percentage of the payment at the customer When,
And a means for transmitting the created alarm data to a client terminal.

Further, in the invention described in the preceding two paragraphs, each company name included in the exchange statement data is the account name of the customer, the seller, and the supplier,
In order to improve the accuracy of the name identification process, the name identification process includes matching the financial institution and branch code in the account name included in the exchange statement data with the financial institution and branch code in the company attribute data. It is characterized by that.

  Further, the invention described in the preceding three paragraphs is characterized by further comprising means for receiving the seller and supplier data, and the company attribute data from an external server.

  As described above, according to the present invention, it is possible to centrally manage information such as receivables and payables of business partner customers, sales destinations and suppliers to business partner customers, and grasp abnormal information at the time of credit judgment. Appropriate credit management can be performed. Further, by grasping the information of the business partner customers in a lump, such information can be utilized for business promotion for the business customers.

It is a figure which shows the system configuration | structure which concerns on one Embodiment of this invention. It is a figure which shows the data stored in the customer data storage part which concerns on one Embodiment of this invention. It is a figure which shows the data stored in the supplier data storage part which concerns on one Embodiment of this invention. It is a figure which shows the data stored in the commercial flow data storage part which concerns on one Embodiment of this invention. It is a figure which shows the data stored in the exchange detail data storage part which concerns on one Embodiment of this invention. It is a figure which shows the data stored in the company attribute data storage part which concerns on one Embodiment of this invention. It is a figure which shows the data stored in the commercial exchange detailed statement data storage part which concerns on one Embodiment of this invention. It is a figure which shows the data stored in the bankruptcy data storage part which concerns on one Embodiment of this invention. It is a figure which shows the data stored in the alarm data storage part which concerns on one Embodiment of this invention. It is a figure which shows the data stored in the name collation condition data storage part which concerns on one Embodiment of this invention. It is a flowchart which shows the credit management process which concerns on one Embodiment of this invention.

  Hereinafter, a credit management system according to an embodiment of the present invention will be described in detail with reference to the accompanying drawings.

  First, the outline of the credit management system will be described. FIG. 1 is a diagram showing a system configuration according to an embodiment of the present invention. In FIG. 1, an external server 100 is a server installed in an external network. The credit management server 101 installed in a data center or the like is configured to communicate with the external server 100 via a network 102 (for example, the Internet). The credit management server 101 communicates with one or a plurality of client terminals 104a,..., 104n (hereinafter collectively referred to as “client terminals 104”) via a network 103 (for example, an intranet or an extranet). Configured to do. For example, the client terminal 104 is a terminal used by a person in charge of a financial institution that makes a credit decision. Although the credit management server 101 is shown as a single server in FIG. 1, it can be configured as a distributed system with a plurality of servers.

  The credit management server 101 receives sales destination data and supplier data from the external server 100 and creates commercial flow data. Also, the credit management server 101 creates commercial exchange detailed statement data from the exchange detailed statement data based on the created commercial distribution data. At this time, the account name is different in the exchange statement data, so it is treated as separate data (record). Originally the same commercial flow (the customer and the customer are substantially the same, or purchased with the customer. Summarize the data (substantially the same as before). Therefore, the credit management server 101 receives company attribute data from the external server 100, and executes a name identification process based on the company attribute data.

  Next, the configuration of the credit management server 101 will be described in detail. In FIG. 1, only a necessary functional configuration is shown assuming a single computer system.

  In the credit management server 101, a RAM 111, an input device 112, an output device 113, a communication control device 114, and a storage device 116 including a nonvolatile storage medium (ROM, HDD, etc.) are connected to the CPU 110 via a system bus 115. It has the structure made. The storage device 116 includes a program storage area for storing a software program for performing each function of the credit management system, and a data storage area for storing data handled by the software program. Each means in the program storage area described below is actually an independent software program, its routines, components, and the like, which are called from the storage device 116 by the CPU 110 and expanded in the work area of the RAM 111, with reference to the database and the like as appropriate. Each function is performed by being executed sequentially.

  As the data storage area in the storage device 116, only those related to the present invention are enumerated. The sales destination data storage unit 131, the supplier data storage unit 132, the commercial flow data storage unit 133, the exchange statement data storage unit 134, the company It includes an attribute data storage unit 135, a merchandise exchange statement data storage unit 136, a bankruptcy data storage unit 137, an alarm data storage unit 138, and a name identification condition data storage unit 139. Both are fixed storage areas secured in the storage device 116.

  The sales destination data storage unit 131 stores sales destination data for business customers. FIG. 2 is a diagram showing data stored in the sales destination data storage unit 131 according to the embodiment of the present invention. The sales destination data in FIG. 2 includes a “company number” that uniquely indicates a business partner customer, a “sales company number” that uniquely indicates a sales destination for the business customer, and an “update date” that indicates a data registration (update) date. "including. The “company number” and the “sales company number” may be in the same format, and the customer may be a customer for another customer. In addition, when there are a plurality of external servers 100, sales destination data may be linked from each server. In this case, the “company number” and “sales company number” are unique in the DB held by each server. Number. Therefore, for example, in place of the “company number” in FIG. 2, even if the same company is indicated, a plurality of “first company numbers” and “second company numbers” are held (ie, Even the company number indicating the company A may be “11111111” in the first company number and “9999999999” in the second company number). This concept can also be applied to the “sales company number”.

  The supplier data storage unit 132 stores supplier data for the customer. FIG. 3 is a diagram showing data stored in the supplier data storage unit 132 according to an embodiment of the present invention. The supplier data in FIG. 3 indicates a “company number” that uniquely indicates a supplier customer, a “supplier company number” that uniquely indicates a supplier for the supplier customer, and a data registration (update) date. Includes "update date". It should be noted that the “company number” and the “supplier company number” may be in the same format, and the customer customer may be a supplier to another customer customer. The concept of “first company number” and “second company number” described in the previous section can also be applied to “supplier company number”.

  The commercial flow data storage unit 133 stores commercial flow data for the customer of the customer. FIG. 4 is a diagram illustrating data stored in the commercial flow data storage unit 133 according to an embodiment of the present invention. The commercial data in FIG. 4 includes the “company number” that uniquely indicates the customer, the “customer company number” that uniquely indicates the sales destination or supplier to the customer, and the company indicated by the customer company number. It includes a “commercial flow category” indicating whether it is a seller or a supplier, and an “update date” indicating a data registration (update) date. Here, the “commercial flow classification” is, for example, “1” when the company indicated by the supplier company number is the sales destination, and “2” when the company is the supplier. In addition, when there is a commercial flow between a customer of the customer (referred to as company A) and the client of the customer (referred to as company B), and the sales destination for the company A is the company B, The supplier is in the relationship of company A. Therefore, in principle, the commercial flow data includes data for two records for transactions between companies.

  The exchange statement data storage unit 134 stores exchange statement data indicating deposits and withdrawals with respect to business partners. FIG. 5 is a diagram showing data stored in the exchange detail data storage unit 134 according to an embodiment of the present invention. The exchange statement data in FIG. 5 includes the financial institution data and account data of the sender who is the payer (debtor), and the financial institution data and account data and transactions of the receiver who is the payer (creditor). “Transaction amount” indicating the amount of money traded, and “Transaction date” indicating the date of transaction.

  The company attribute data storage unit 135 stores data of business partners including sales partners and suppliers. FIG. 6 is a diagram showing data stored in the company attribute data storage unit 135 according to the embodiment of the present invention. The company attribute data in FIG. 6 includes “company number” that uniquely identifies the business partner company, “company name kana” that is the katakana notation of the company name, and “corporate case code” that indicates what the legal entity (corporation, limited company) is. ”,“ Pre- and post-corporate display ”indicating whether the corporate case is displayed before or after the company name, and financial institution data and account data of the client company. Here, the “corporate case code” is, for example, “01” when the client company is a stock company and “02” when it is a limited company. In addition, “pre- and post-corporate display” is “01” when the corporate case is displayed before the company name (for example, Patent Shoji Co., Ltd.), and “02” when it is displayed after (for example, ABC Corporation). . “Financial institution code” and “branch code” in FIG. 6 means that the business partner can have a combination of three types of financial institutions and branches of 1 to 3. In another embodiment, the number of items can be increased so that three or more types of “financial institution code” and “branch code” can be provided, or one record can be provided as one type and a plurality of records can be provided.

  The commercial exchange statement data storage unit 136 performs a name identification process on the same holder in the exchange statement data and stores the summarized commercial exchange statement data. FIG. 7 is a diagram showing data stored in the commercial exchange statement data storage unit 136 according to an embodiment of the present invention. The merchandise exchange statement data in FIG. 7 is a “sender company number” and “sender name” uniquely indicating a sender who is paying the price (debtor), and a party receiving the price (creditor). It includes a “recipient company number” and “recipient name” that uniquely indicate the recipient, a “total transaction amount” that indicates the total amount of the transaction, and a “transaction month” that indicates the month of transaction. 7 assumes that the transaction details in FIG. 5 are summarized for each transaction month with respect to the details in FIG. This is the total of “transaction amount” in “transaction month”.

  The bankruptcy data storage unit 137 stores bankrupt company data. FIG. 8 is a diagram showing data stored in the bankruptcy data storage unit 137 according to an embodiment of the present invention. The bankruptcy data in FIG. 8 stores the “company number” of the bankrupt company and the “bankruptcy date” indicating the date of bankruptcy.

  The alarm data storage unit 138 stores alarm data for each customer. FIG. 9 is a diagram showing data stored in the alarm data storage unit 138 according to an embodiment of the present invention. The alarm data in FIG. 9 stores “company number” uniquely indicating a customer and each alarm data. Each alarm data includes, in one embodiment, “bankruptcy” indicating that the customer has gone bankrupt, “commercial bankruptcy” indicating that the seller or supplier for the customer has gone bankrupt, and This is a “decrease in deposit” indicating that the deposit has decreased by a predetermined percentage over a certain period. In this case, for example, each data can be used as an ON / OFF flag indicating that “0” is not applicable as an alarm and “1” is applicable. However, in the case of “commercial bankruptcy”, “0” is not applicable, “1” is bankrupt sales, “2” is bankrupt, and “3” is bankrupt. be able to. In addition, “decrease in deposits” can be divided into stages ranging from a small decrease to a large decrease, and a numerical value indicating each can be assigned. Thereby, more detailed alarm data can be shown.

  The name identification condition data storage unit 139 stores conversion data used for name identification processing. FIG. 10 is a diagram showing data stored in the name identification condition data storage unit 139 according to an embodiment of the present invention. The name identification condition data in FIG. 10 stores “conversion source” indicating a character string before conversion and “conversion destination” indicating a character string after conversion. If the “conversion destination” is blank, it means that the character string indicated by the “conversion source” is simply deleted. In another embodiment, only the deleted character string can be held as data. In this case, the name identification process is performed based on the conversion data and the deletion data as the name identification condition data. In still another embodiment, when the conversion and deletion conditions are described on the program (so-called hard coding), the conversion data used for the name identification process becomes unnecessary, and therefore the name identification condition data storage unit 139 is also unnecessary.

  Next, the software programs stored in the program storage area in the storage device 116 list only those related to the present invention. The data transmission / reception means 120, the commercial flow data creation means 121, the commercial flow statement data creation means 122 are listed. , Name identification means 123, and abnormal value capturing means 124. These means 120 to 124 are executed by the CPU 110.

  The data transmission / reception means 120 receives sales destination data, vendor data, company attribute data, bankruptcy data, etc. from the external server 100, and receives the sales destination data storage unit 131, supplier data storage unit 132, company attribute, respectively. The data is stored in the data storage unit 135 and the bankruptcy data storage unit 137. Further, the data transmitting / receiving unit 120 transmits alarm data to the client terminal 104.

  The commercial flow data creating unit 121 creates commercial flow data as shown in FIG. 4 based on the sales destination data and the supplier data received from the external server 100 and stores them in the commercial flow data storage unit 133. In other embodiments, if the external server 100 already holds data in the form of commercial flow data as shown in FIG. 4 and is linked to the credit management server 101, this means is naturally not necessary.

  Based on the commercial flow data and the company attribute data, the commercial exchange detailed statement data creating means 122 extracts the customer customer deposit / withdrawal data from the exchange detailed statement data, for example, summarizes it for each transaction month, as shown in FIG. The commercial exchange statement data is created and stored in the commercial exchange statement data storage unit 136.

  The name identification unit 123 executes name identification processing based on the company attribute data and the name identification condition data when creating the commercial exchange detailed statement data.

  The abnormal value capturing means 124 creates customer customer alarm data based on the commercial exchange statement data and bankruptcy data.

  Next, referring to the flowchart of FIG. 11 and the table of FIG. 2-10, a credit management process according to an embodiment of the present invention will be described along the flow.

  FIG. 11 is a flowchart showing a credit management process according to an embodiment of the present invention. In addition, although the flowchart of FIG. 11 has described a series of processes continuously, it does not necessarily need to process continuously. The processing timing and cycle can be arbitrarily set. In particular, the commercial flow data creation processing in steps 1101-1102 and the commercial flow exchange statement data creation and abnormal value capture processing in step 1103 and subsequent steps are performed once a day with, for example, commercial flow data creation processing in advance. Based on the commercial flow data in a night batch or the like, it is assumed that commercial flow statement data is created from the exchange statement data and abnormal value capturing processing is executed. In addition, when creating the commercial flow detailed statement data, it can be assumed that the corresponding commercial flow data does not exist. In this case, the relevant commercial flow data is created at the timing of creating the commercial flow detailed statement data. become.

  The flowchart of FIG. 11 will be described in detail. First, in step 1101, the data transmission / reception means 120 receives the sales destination data (FIG. 2) and the supplier data (FIG. 3) from the external server 100, and receives the sales destination data storage unit 131 and the supplier, respectively. The data is stored in the data storage unit 132. The sales destination data and the supplier data are data indicating the relationship between the business customer (the company indicated by the “company number”), the sales destination, and the business partner company, respectively. The external server 100 is a server installed in an external network, for example. The processing in this step means acquiring merchandise flow data of the seller and supplier from the external DB. For this reason, when selling destination data and supplier data are acquired from a plurality of external DBs, a plurality of selling destination data and supplier data exist. In addition, the data items “company number”, “sales company number”, and “supplier company number” that are the data items of each data need only be unique in each external DB (the data format is different because each management source is different). Is virtually impossible). Therefore, when handled by the credit management system, for example, “company number” needs to be managed as a separate item from “first company number”, “second company number”, and the like. In this case, in order to indicate that the “first company number” and the “second company number” are the same company, the credit management system associates both numbers using a mapping table or the like.

  Next, based on the received sales destination data and supplier data, the commercial flow data creation unit 121 creates commercial flow data (FIG. 4) and stores it in the commercial flow data storage unit 133 (step 1102). The commercial flow data is data indicating a relationship between a customer (a company indicated by “company number”) and a customer company (a company indicated by “client company number”). In the present embodiment, when the “commercial flow classification” is “1”, the customer company is a sales company for the customer, and when it is “2”, it is a supplier company. The “commercial flow classification” can be determined based on whether the data acquisition source when creating the commercial flow data is sales destination data or supplier data. The commercial data can also be created from the transfer results between companies. For example, in the case where Company A performs a plurality of times continuously from Company B for a certain period (such as three months), Company B is a sales destination of Company A (On the other hand, Company A is Company B. And commercial flow data can be created for each. Moreover, in another embodiment, when a transaction form is a bill transaction, when this occurs even once, it can be determined that both are mutual suppliers. In still another embodiment, if the data linked from the external server 100 is already commercial data in the format as shown in FIG. 4, steps 1101 and 1102 simply receive this and commercial data It is only stored in the storage unit 133. Note that after step 1102, the process can be terminated without proceeding to step 1103 and subsequent steps. In this case, step 1103 and subsequent steps are executed as separate processing.

  Next, the name identification unit 123 performs name identification processing based on the company attribute data (FIG. 6) and the name identification condition data (FIG. 10) with respect to the exchange detail data (FIG. 5) stored in advance in the currency detail data storage unit 134. Is executed (step 1103). The exchange statement data is deposit / withdrawal data, and includes financial institution and account data of a sender (payer) and a receiver (payee), a transaction amount, and the like. However, each company may have a plurality of accounts, and may use a plurality of accounts for transactions with the same business partner company. Therefore, because the account name is different in the exchange statement data, it is treated as separate data (record), originally the same commercial flow (the customer and the customer are substantially the same, or the customer and the supplier In order to summarize the data related to (substantially the same), name identification processing is executed. In addition, each account used as a name collation object is not restricted to the thing of the same financial institution, It can also be set as the account between different financial institutions.

  The name identification process is performed by deleting a predetermined character string or converting it to another character string in the account name of the exchange statement data. As an example of the exchange statement data in FIG. 5, “Yugen Gaisha Trademark Design” and “(Yu) Trademark Design” indicated by “Receiving Account Name” in the first to fourth records are all the same company ( The 9th record of the company attribute data in FIG. 6 is “Yugen Geisha trademark design” of the company number “999999999”). However, since it is determined that the character string is different in terms of data, data conversion is performed using name identification condition data as shown in FIG. For example, the sixth record of the name identification condition data in FIG. 10 indicates that the character string “(Yu)” is converted to the character string “Yugen Geisha”. As a result, “(Yu) Trademark Design” is converted to “Yugen Gaisha Trademark Design”, and “Receiving Account Name” in the first to fourth records in FIG. 5 is all of the company attribute data in FIG. It can be associated with the ninth record, and it can be determined that they are the same company. At this time, by further matching each combination of the financial institution code and the branch code in the company attribute data of FIG. 6 with the financial institution code and the branch code in the exchange statement data, the accuracy of the name identification process can be improved. .

  In FIG. 10, “conversion destination” being blank means that “conversion source” is converted to blank, that is, the character string of “conversion source” is deleted. The name identification condition data can also be stored as separate data for character string conversion and deletion.

  On the other hand, when the character strings indicated by “conversion source” overlap, for example, “(Cub)” in the first record and “Cub” in the second record in FIG. In the case of “Tokyo”, both are applicable. However, if conversion is performed using “Cub” in the second record, it is possible that “(Kabushiki-Gaisha-kyo-shoji)” and “(” will remain. Therefore, the priority order is added to the name identification condition data in FIG. (Not shown, but a numerical value indicating the priority order), or when the company attribute data has “pre- and post-corporate display” as shown in FIG. If the “Corporate case display” is “01” and the previous display is displayed, the character string “(Cub) Tokyo” in the account name is checked one character at a time from the front (left), and the character string to be converted is “Cub”. Instead, it can be determined to be “(cub)”.

  Next, the merchandise exchange statement data creating means 122 creates the customer's customer's customer based on the merchandise flow data (FIG. 4) and the company attribute data (FIG. 6) from the exchange statement data subjected to the name identification process in step 1103. Deposit / withdrawal data is extracted to create commercial exchange statement details data (FIG. 7) and store it in the commercial exchange statement data storage unit 136 (step 1104). In one embodiment, for each business partner customer indicated by the company number of the commercial flow data, summary is made for each transaction month and sorted in chronological order to create commercial flow detailed statement data.

  More specifically, each “company name Kana” is specified from the company attribute data (FIG. 6) using “company number” and “business partner company number” of the commercial flow data (FIG. 4) as search keys (ie, , The company name Kana indicated by the company number and the company name Kana indicated by the business partner company number are acquired). Next, the target record is extracted from the exchange detail data subjected to the name identification process by using each identified “company name kana” as a search key (AND condition). At this time, the details of the exchange with the name identification process matched with the search key (the company name Kana indicated by the company number and the company name Kana indicated by the business partner company number) by the “commercial flow classification” of the commercial flow data (FIG. 4). Data items in the data change. For example, when the “commercial flow category” is “1” (seller), the company indicated by the supplier company number is “seller”. Therefore, the company indicated by the business partner company number is a sender (payment side) in the exchange statement data, and the company indicated by the company number is a receiver (side receiving the price). On the other hand, when the “commercial flow category” is “2” (supplier), the company indicated by the supplier company number is “supplier” and becomes the receiver (recipient), and the company number The company indicated by becomes the caller (payer). Therefore, depending on the “commercial flow classification”, which “company name Kana” is matched with the “sender account name” and the “recipient account name” in the exchange detail data subjected to the name identification process is changed.

  Each company name of the company indicated by the company number and the partner company is matched with the "sender account name" and "recipient account name", and after obtaining the exchange statement data, the "transaction date" in the exchange statement data Are summarized for each transaction month, for example, and sorted in chronological order, thereby creating commercial exchange detail data (FIG. 7) as shown in FIG. Here, when summarizing every transaction month, the “transaction amount” of the commercial exchange statement data is calculated by summing up the “transaction amount” of the exchange statement data.

  Next, the abnormal value capturing means 124 creates customer customer alarm data based on the merchandise exchange statement data (FIG. 7) and bankruptcy data (FIG. 8) (step 1106). This step is processed for each type of alarm. The order of processing for each type of alarm is irrelevant. Processing will be described for each type of alarm.

  The “bankrupt” alarm indicating that the customer has gone bankrupt is the customer whose company is indicated by the company number whose “bankruptcy date” in the bankruptcy data (FIG. 8) is within a certain period (for example, within the last two weeks). This is the case. In this case, “bankruptcy” becomes “1” (bankruptcy alarm ON) as shown in the alarm data in FIG.

  As with the “bankruptcy” alarm, the “bankruptcy” alarm, which indicates that the customer or supplier for the customer, went bankrupt, indicates the “bankruptcy date” in the bankruptcy data (FIG. 8). This is the case when the company is a seller and / or supplier. Since the seller and the supplier may go bankrupt at the same time as a possibility, in one embodiment, the “commercial bankruptcy” alarm in the alarm data of FIG. 9 is “1” when the seller is bankrupt. “2” when the supplier is bankrupt, and “3” when both are bankrupt.

  When the company indicated by the recipient company number is the customer account in the merchandise exchange statement data (FIG. 7), the “Deposit Decrease” alarm indicating that the payment at the customer customer has decreased by a predetermined percentage over a certain period of time. This is the case where the company indicated by the sender company number, that is, the total transaction amount (payment total) from the sales destination company is reduced by a predetermined percentage compared to the previous month's transaction month. In such a case, as shown in the alarm data of FIG. 9, “Deposit decrease” becomes “1” (Deposit decrease alarm ON). Further, in another embodiment, finer alarm data can be shown by categorizing “decrease in deposit” as non-applicable, small decrease, large decrease, etc., and indicating each in numerical values.

  Next, the data transmitting / receiving unit 120 transmits the created alarm data to the client terminal 104 (step 1107). After step 1107, the process ends. Thereafter, in the client terminal 104, the alarm data is displayed as a list on the Web screen, or notified by e-mail or instant message, so that the person in charge of the financial institution can make a credit judgment for the customer.

  Further, in another embodiment, by analyzing the business flow and analyzing the needs of the business partner customer from the company attribute data (FIG. 6), the commercial exchange statement data (FIG. 7), and the bankruptcy data (FIG. 8), It can also be used for promotion. This periodically captures the deposit / withdrawal information with respect to the customer and the bankruptcy information of the customer and the seller and supplier based on a predetermined condition. The captured information is transmitted to the client terminal 104, and a list is displayed on the client terminal 104, so that the person in charge of the financial institution can determine the trend and needs of the customer. For example, when a customer customer receives payment from a venture capital (VC), it can be determined that the customer has a need to accept investment. Further, when the customer of the customer of the customer goes bankrupt, it can be determined that there is a need for factoring (guarantee receivable guarantee) for collection of accounts receivable. Furthermore, when a customer withdraws money from the customer to the audit corporation, it can be determined that the customer has a need for IPO (public offering).

Claims (6)

Utilizing exchange detailed data for indicating the receipt and payment status of suppliers customer for financial institutions, a system for managing the credit data of the suppliers customer, the system comprising:
On the basis of the partner vendor data for indicating a vendor for sales destination data and the suppliers customer to indicate the purchaser to customers, sales and vendors that do business with the suppliers customer Means for creating commercial flow data to show relationships ;
A means for executing a name identification process on the exchange statement data, wherein the name identification process is included in each company name of the customer, the seller, and the supplier included in the exchange statement data. By converting the character string into a predetermined character string and associating the converted character string with the company name in the company attribute data for indicating the customer, the data relating to the same company in the exchange statement data is obtained. process of recognizing der is, each of the company name, the transaction destination customer, the sales destination, and is the account holder of the supplier, the name identification process, in order to determine whether or not the same company, Further, the method includes matching the financial institution code and branch code in the name of the account included in the exchange statement data with the financial institution code and branch code in the company attribute data. System characterized in that a means. A means for creating alarm data of the customer of the customer based on the exchange statement data and bankruptcy data subjected to name identification processing , wherein the alarm data indicates that the customer of the customer has gone bankrupt, and that the customer has gone bankrupt. Means, data indicating at least one of the following: the supplier has gone bankrupt, and the payment at the customer customer has decreased by a predetermined percentage over a period of time;
The system according to claim 1, further comprising means for transmitting the created alarm data to a client terminal. The decrease in the deposit at the customer account for a predetermined period in a predetermined period includes a decrease in the deposit for the current month as compared to the deposit for the previous month at the customer customer. 2. The system according to 2. The sales destination data, the vendor data, and the company attribute data may be further received from an external server, and the sales destination and the vendor may be the same company as the customer. the system of claim 1 or 2, characterized in that. Utilizing exchange detailed data for indicating the receipt and payment status of suppliers customer for financial institutions, a method for managing credit data of the suppliers customer, the method comprising:
Computer, on the basis of the vendor data for indicating a vendor for sales destination data and the suppliers customer to indicate a purchaser for suppliers customers, sales destination and specification with dealing with the suppliers customer Creating commercial flow data to show the relationship of the destinations ;
The computer is a step of executing a name identification process on the exchange detail data , wherein the name identification process is performed by each of the customer, the seller, and the supplier companies included in the exchange detail data. By converting the character string included in the name into a predetermined character string and associating the converted character string with the company name in the company attribute data for indicating the customer, the same company in the exchange statement data process of recognizing der data related to is, each of the company name, the transaction destination customer, the sales destination, and is the account holder of the supplier, the name identification process, determines whether or not the same company In addition, a financial institution code and a branch code in the name of an account included in the exchange statement data, and a financial institution code and a branch code in the company attribute data It includes matching, a method of comprising the steps. A computer having a system for managing the credit data suppliers customer for financial institutions, perform a method for utilizing the exchange detailed data for indicating the receipt and payment status of the suppliers customer, manages the credit data of the suppliers customer A computer program, the method comprising:
On the basis of the partner vendor data for indicating a vendor for sales destination data and the suppliers customer to indicate the purchaser to customers, sales and vendors that do business with the suppliers customer Creating commercial flow data to show the relationship ;
A step of performing name identification processing on the exchange statement data, wherein a character string contained in each company name of the customer, the seller, and the supplier included in the exchange statement data is predetermined. And recognizing data relating to the same company in the exchange statement data by associating the converted character string with the company name in the company attribute data for indicating the customer. In addition , each company name is the account name of the customer, the seller, and the supplier, and the name identification process further includes the exchange statement in order to determine whether or not the company is the same company. Including matching a financial institution code and a branch code in the name of an account included in the data with a financial institution code and a branch code in the company attribute data. A computer program characterized by comprising.

Images