JP7049417B2 - Account management equipment and programs - Google Patents

Description

The present invention relates to an account management device and a program.

An accounting management system that supports the financial accounting work of a business operator has been known (see, for example, Patent Document 1).
[Prior Art Document]
[Patent Document]
[Patent Document 1] Japanese Unexamined Patent Publication No. 2012-146158

It is desirable to provide technology that enables support for businesses using data managed by accounting management systems.

According to the first aspect of the present invention, an account management device is provided. The account management device may include an account management unit that manages the account balance of the business operator. The account management device may include a loan admissibility determination unit that determines whether or not to lend to a business operator based on at least one of accounting data relating to the accounting of the business operator and transaction data relating to transactions by the business operator. The account management unit may add the loan amount to the account balance of the business operator when the loan availability determination unit determines that the loan is available.

The loan approval / disapproval determination unit may determine the loanable amount to the business operator based on at least one of the accounting data and the transaction data, and the account management unit is determined by the loan approval / disapproval determination unit. The above loanable amount may be added to the account balance of the above business operator. The account management device may further include a payment request acquisition unit for acquiring a payment request including a payment amount to a business partner by the business operator, and the loan approval / disapproval determination unit may have the payment amount as the account balance of the business operator. If it is larger than the above, it may be determined whether or not it is possible to lend an amount equal to or greater than the difference between the payment amount and the account balance.

The account management unit may add a loan amount equal to or greater than the difference between the payment amount and the account balance to the account balance, and the account management device responds to the payment request from the account balance to the payment amount. It may be further provided with a payment processing execution unit that executes payment processing for paying the above-mentioned business partner. The account management device executes loan repayment by subtracting the loan amount from the account balance when the account balance of the business operator is larger than the loan amount after the payment process is executed by the payment processing execution unit. You may have more parts. The loan repayment execution unit may subtract a part of the loan amount from the account balance when the account balance of the business operator is smaller than the loan amount. The account management device may further include an interest rate payment execution unit that subtracts an interest rate amount determined according to a predetermined interest rate rule from the account balance after the payment processing is executed by the payment processing execution unit.

The account management device may include a future CF information generation unit that generates future CF information indicating the future cash flow of the business operator based on at least one of the accounting data and the transaction data, and the loan availability may be provided. The determination unit may determine whether or not to lend to the business operator based on the future CF information. The future CF information generation unit may generate the future CF information based on the accounting data and the transaction data. The account management device may further include a past CF information generation unit that generates past CF information indicating the past cash flow of the business operator based on the accounting data, and the future CF information generation unit may further include the past CF information generation unit. The CF information may be generated in the future based on the CF information. The account management device may further include a financial institution data acquisition unit that acquires financial institution data including a history of deposits and withdrawals to the bank account of the business operator, and the future CF information generation unit may include the past CF information and the above. The above-mentioned future CF information may be generated by using the difference from the financial institution data. The account management device may further include a transaction relationship data acquisition unit that identifies a transaction partner of the business operator using the transaction data and acquires transaction relationship data related to a transaction with another business operator by the transaction partner. The future CF information generation unit may further generate the future CF information based on the transaction relationship data acquired by the transaction relationship data acquisition unit. The account management device may further include a business group specifying unit that specifies a business group corresponding to the business, and the future CF information generation unit may include a business group specified by the business group specifying unit. The above-mentioned future CF information may be generated based on the characteristic data indicating the characteristics of the cash flow of. The account management unit may manage the account balances of a plurality of businesses in one or a plurality of bank accounts.

According to the third aspect of the present invention, a program for making a computer function as the information processing apparatus is provided.

The outline of the above invention does not list all the necessary features of the present invention. A subcombination of these feature groups can also be an invention.

An example of the communication environment of the loan determination device 100 is schematically shown. An example of past CF information 182 and future CF information 184 is shown schematically. An example of the data item 22 of the loan application data is shown schematically. An example of the data item 212 of the journal data is shown schematically. An example of the data item 214 of the balance data is shown schematically. An example of the data item 222 of the billing data is shown schematically. An example of the data item 224 of the estimation data is shown schematically. An example of data item 232 of financial institution data is shown schematically. An example of the data item 242 of the credit information data is shown schematically. An example of the data item 170 of the past history data is shown schematically. An example of the data item 252 of the business group data is shown schematically. An example of the data item 262 of the transaction relation data is shown schematically. An example of the processing flow by the loan determination device 100 is schematically shown. Another example of the processing flow by the loan determination device 100 is schematically shown. An example of the functional configuration of the loan determination device 100 is schematically shown. An example of the functional configuration of the account management device 300 is schematically shown. An example of the hardware configuration of the computer 1000 functioning as the loan determination device 100 or the account management device 300 is schematically shown.

Hereinafter, the present invention will be described through embodiments of the invention, but the following embodiments do not limit the invention within the scope of the claims. Also, not all combinations of features described in the embodiments are essential to the means of solving the invention.

FIG. 1 schematically shows an example of the communication environment of the loan determination device 100. The loan determination device 100 is an example of an information processing device.

The loan determination device 100 according to the present embodiment determines whether or not a loan to a business operator is possible. The loan determination device 100 receives, for example, loan application data including a loan application amount, a desired loan date, a loan period, and the like from a communication terminal 20 of a business operator, and determines whether or not a loan can be made to the business operator. A business operator for which the loan determination device 100 determines whether or not a loan can be made may be described as a target business operator.

The communication terminal 20 may be any terminal as long as it has a communication function, and is, for example, a PC (Personal Computer), a tablet terminal, a mobile phone such as a smartphone, and the like. The loan determination device 100 communicates with the communication terminal 20 via the network 10. The network 10 may include the Internet. The network 10 may include a telephone network. The network 10 may include a dedicated network.

The loan determination device 100 may generate probability information indicating the probability of loan repayment of the business operator, and determine whether or not to lend to the business operator based on the probability information. The probability information is, for example, future CF information indicating the future cash flow of the business operator (may be referred to as CF). Further, the probability information is, for example, a score indicating the probability of loan repayment of the business operator. The score may be anything as long as it indicates the degree of probability of the loan repayment of the business operator.

The loan determination device 100 generates probability information using, for example, accounting data related to the accounting of the target business operator. The loan determination device 100 may receive the accounting data of the target business operator from the accounting data management device 210 that manages the accounting data of a plurality of business operators via the network 10.

The accounting data management device 210 may manage accounting data input by a business operator, an accounting office, or the like by using so-called accounting software, so-called cloud-type accounting software, and related software thereof. The accounting data management device 210 may manage accounting data provided by a business operator, an accounting office, or the like without going through accounting software, cloud-type accounting software, or related software thereof.

The loan determination device 100 may manage the accounting data of a plurality of businesses by itself. That is, the loan determination device 100 may have the function of the accounting data management device 210.

The loan determination device 100 generates probability information using, for example, transaction data related to a transaction by a target business operator. The loan determination device 100 may receive transaction data of a target business operator from a transaction data management device 220 that manages transaction data of a plurality of business operators via a network 10.

The transaction data management device 220 may manage transaction data input by a business operator, an accounting firm, or the like using so-called sales management software, so-called cloud-type sales management software, and related software thereof. The transaction data management device 220 may manage transaction data input by a business operator, an accounting office, or the like using accounting software, cloud-based accounting software, and related software thereof. The transaction data management device 220 is a transaction provided by a business operator, an accounting office, or the like without going through sales management software, cloud-type sales management software, accounting software, cloud-type accounting software, and related software. You may manage the data.

The loan determination device 100 may manage transaction data of a plurality of businesses by itself. That is, the loan determination device 100 may have the function of the transaction data management device 220.

The loan determination device 100 generates probability information using, for example, financial institution data including a history of deposits and withdrawals to and from the financial institution account of the target business operator. The financial institution account may be an account managed by a financial institution such as a bank or a credit union. The loan determination device 100 may receive financial institution data of a target business operator from a financial institution data management device 230 that manages financial institution data of a plurality of business operators via a network 10.

The financial institution data management device 230 may receive and manage financial institution data of a plurality of businesses from a plurality of financial institutions. The financial institution data management device 230 may receive and manage financial institution data certified by a financial institution from each of a plurality of businesses.

The loan determination device 100 may manage the financial institution data of a plurality of businesses by itself. That is, the loan determination device 100 may have the function of the financial institution data management device 230.

The loan determination device 100 generates probability information using, for example, the credit information data of the target business operator generated by a third party. The loan determination device 100 may receive the credit information data of the target business operator from the credit information management device 240 that manages the credit information data of a plurality of business operators via the network 10.

The credit information management device 240 is managed by, for example, a company that implements a service that generates and provides credit information data of a plurality of businesses. The method of generating the credit information data by the trader may be any method.

The loan determination device 100 may manage the credit information data of a plurality of businesses by itself. That is, the loan determination device 100 may have the function of the credit information management device 240.

The loan determination device 100 generates probability information using, for example, characteristic data indicating the characteristics of the CF of the business group corresponding to the target business. The loan determination device 100 may receive the characteristic data of the business group corresponding to the target business from the business group data management device 250 that manages the characteristic data of the plurality of business groups via the network 10.

The business group means, for example, a group of business operators by industry. For example, when the target business operator is a construction company, the business group corresponding to the target business operator may be the construction industry. The characteristics of the CF of the business group may be the characteristics of the CF fluctuation for each industry, for example, the construction industry tends to improve sales in March. The feature data may be data that embodies the content of fluctuations, such as increasing sales in March of the construction industry by 20%.

The business group is not limited to the group of business operators by industry, and may indicate other groups. For example, the business group may be a group of business operators for each series. Further, the business group may be a group of business operators determined by the person in charge of grouping the business operators.

The business operator group data management device 250 generates characteristic data by analyzing various data for each of a plurality of business operators, for example. The business group data management device 250 analyzes, for example, the accounting data of a plurality of business operators and generates characteristic data for each business group. The business group data management device 250 may independently collect accounting data of a plurality of businesses, or may receive accounting data of a plurality of businesses from the accounting data management device 210. Further, the business group data management device 250 may manage the feature data generated by the person in charge of generating the feature data.

The loan determination device 100 may manage the characteristic data of a plurality of business operators by itself. That is, the loan determination device 100 may have the function of the business group data management device 250.

The loan determination device 100 generates probability information using, for example, transaction relationship data regarding transactions with other businesses by the business partners of the target business. The transaction-related data includes, for example, collection records and payment records between business operators. The loan determination device 100 may receive the business relationship data of the business partner of the target business operator from the business relationship management device 260 that manages the business relationship data between a plurality of business operators via the network 10.

The transaction relationship management device 260 manages a transaction relationship between a plurality of businesses. Then, the transaction relationship management device 260 manages the transaction relationship data regarding the transaction between the business operator and the business partner for each of the plurality of business operators.

A business relationship between a plurality of businesses includes, for example, a correspondence between a certain business and a business having a business relationship with the business. According to the business relationship managed by the business relationship management device 260, it is possible to identify a business operator having a business relationship with a certain business operator, and further to identify a business operator having a business relationship with the business operator having the business relationship. Is. As described above, according to the business relationship managed by the business relationship management device 260, it is possible to identify a business operator having a business relationship in a chain reaction with respect to a certain business operator.

The loan determination device 100 may manage the transaction relationship and the transaction relationship data between a plurality of businesses by itself. That is, the loan determination device 100 may have the function of the transaction relationship management device 260.

The loan determination device 100 may generate probability information using the above-mentioned plurality of types of data. The loan determination device 100 may determine whether or not to lend to the target business operator by using the generated probability information. As described above, according to the loan determination device 100 according to the present embodiment, it is determined whether or not the loan can be made to the target business operator by using the probability information generated by using a plurality of types of data. It is possible to reduce the probability of occurrence of a situation that cannot be collected. In addition, it is possible to eliminate the need to set excessively strict standards regarding whether or not to make a loan, and it is possible to reduce the probability of a situation in which a business operator who would otherwise be able to receive a loan cannot easily receive a loan. ..

The account management device 300 manages the accounts of a plurality of businesses. The account management device 300 may open an account for the business operator in response to a request from the business operator. The account management device 300 manages the account balances of a plurality of businesses in, for example, one or a plurality of bank accounts. As a specific example, the account management device 300 manages the account balances of N business operators or a larger number of business operators in N bank accounts. The account management device 300 may manage the account balances of a plurality of businesses in a bank account in the name of the administrator of the account management device 300.

The business operator can deposit money from a bank account to an account managed by the account management device 300, or withdraw money from an account managed by the account management device 300 to a bank account. Further, the business operator can specify an account managed by the account management device 300 as a settlement account in a transaction with another business operator. That is, the business operator can receive payment as consideration for the transaction through the account managed by the account management device 300, and can also make payment.

The account management device 300 may be linked with any transaction platform, and the transaction content can be uniquely specified between the account management device 300 and any transaction platform. Instead of linking the account management device 300 with any trading platform, the account management device 300 may also serve as a trading platform.

The account management device 300, for example, receives a payment request from a business operator that manages an account to another business operator, and executes payment processing if the account balance is not insufficient. When the account balance is insufficient, the account management device 300 determines whether or not to lend to the business operator, and when it is determined that the loan is possible, the loan amount may be added to the account balance.

The account management device 300 uses the same method as the loan determination device 100 to generate probability information indicating the probability of loan repayment of the business operator, and determines whether or not to lend to the business operator based on the probability information. good. For example, the account management device 300 determines whether or not to lend to the business operator in the same manner as when the loan application data including the loan application amount corresponding to the shortfall amount is received from the business operator.

The account management device 300 may execute the payment process after adding the loan amount equal to or more than the shortage to the account balance. Further, the account management device 300 may execute the loan repayment process according to a predetermined repayment rule after the payment process is executed. For example, the account management device 300 executes a loan repayment process for repayment of the entire loan amount when the account balance of the business operator is larger than the loan amount. Further, for example, the account management device 300 executes a loan repayment process for repayment of a part of the loan amount when the account balance of the business operator is smaller than the loan amount. Further, the account management device 300 may execute the interest payment processing according to a predetermined interest rate rule when the account balance of the business operator is smaller than the loan amount after the payment processing is executed.

In this way, the account management device 300 manages the accounts of a plurality of businesses, and when the business receives a payment request from another business, if the account balance is insufficient, the business concerned. It automatically determines whether or not to lend to the loan and executes the loan processing. This makes it possible to provide a mechanism that allows a business operator to obtain a loan and conduct a transaction with fewer procedures than before.

FIG. 2 schematically shows an example of past CF information 182 and future CF information 184. Here, an example of the flow of the generation processing of the past CF information 182 and the future CF information 184 by the loan determination device 100 will be described.

The loan determination device 100 generates past CF information 182 indicating the past cash flow of the target business operator by using the data of the account items related to the deposits and savings included in the accounting data of the target business operator. The loan determination device 100 may compare the past CF information 182 with the financial institution data of the target business operator, and if there is an inconsistency, correct the past CF information according to the financial institution data.

The loan determination device 100 generates future CF information 184 based on the past CF information 182. The loan determination device 100 generates, for example, the past CF information 182 for a plurality of years to the future CF information 184 for one year. The loan determination device 100 may generate future CF information 184 by averaging the past CF information 182 for a plurality of years or predicting from the past CF information 182 for a plurality of years. The loan determination device 100 may derive, for example, a sales generation pattern, a purchase generation pattern, an expense generation pattern, and the like in the past CF information 182, and generate future CF information 184 using these.

The loan determination device 100 may generate future CF information 184 by further using the data of the account items related to the increase / decrease of the deposit / savings balance in the future among the accounts items included in the accounting data. The loan determination device 100 generates CF information 184 in the future by using, for example, an account item related to trade receivables and an account item related to trade payables.

The loan determination device 100 may correct the CF information 184 in the future by using the transaction data of the target business operator. The loan determination device 100 corrects the future CF information 184 by using, for example, the estimation data and the order data included in the transaction data. The loan determination device 100 may calculate the order rate indicating the probability of receiving an order for the estimate of the target business operator from the estimate data and the order data, and may correct the future CF information 184 using the order rate. Further, the loan determination device 100 corrects the future CF information 184 by using, for example, the billing data and the estimation data included in the transaction data. The loan determination device 100 may calculate the order rate indicating the probability of receiving an order for the estimate of the target business operator from the billing data and the estimate data, and may correct the future CF information 184 using the order rate. Further, the loan determination device 100 may calculate a billing payment rate indicating the probability of payment for the bill of the target business operator based on the billing data, and may correct the CF information 184 in the future using the billing payment rate.

The loan determination device 100 may specify a trading partner of the target business operator and correct the CF information 184 in the future by using the transaction relationship data regarding the transaction with the other business partner by the trading partner. The loan determination device 100 corrects the CF information 184 in the future by using, for example, the payment status to another business operator by the trading partner. Further, the loan determination device 100 corrects the CF information 184 in the future by using, for example, the attribute information of the trading partner of the trading partner. The attribute information is the scale of the business operator, the creditworthiness of the business operator, and the like.

The loan determination device 100 may correct the CF information 184 in the future by using the characteristic data of the business group corresponding to the target business. The loan determination device 100 corrects the future CF information 184 by using, for example, the sales generation pattern, the purchase generation pattern, the expense generation pattern, and the like indicated by the feature data.

As described above, the loan determination device 100 will generate CF information 184 in the future using a plurality of types of data. In addition, to generate future CF information 184 using a plurality of types of data, as described above, future CF information 184 is generated using a part of a plurality of types of data, and a plurality of types of generated future CF information 184 are generated. Includes generating final future CF information 184 by correcting with other data of the data in.

The loan determination device 100, for example, creates a loan repayment schedule from the loan application data received from the target business operator, and determines whether or not the repayment schedule is feasible based on the CF information 184 in the future, thereby determining whether or not the loan is possible. You may judge. The loan determination device 100 may further use the credit information data to determine whether or not the loan is possible. Further, the loan determination device 100 may determine whether or not the loan is possible by further using the history of the loan to the target business operator.

FIG. 3 schematically shows an example of data item 22 of the loan application data. FIG. 3 also shows an example of the data value of each data item 22.

The loan application data may include a target person ID for identifying the target person. The loan application data may include target person information including the name of the target person. The loan application data may include the loan application amount. The loan application data may include the desired loan date. The loan application data may include the loan period. The loan application data may include data items other than these.

FIG. 4 schematically shows an example of data item 212 of journal data included in accounting data. FIG. 4 also shows an example of the data value of each data item 212.

The journal data may include a data ID for identifying the journal data. The journal data may include the transaction date. Journal data may include debit / credit classifications. Journal data may include accounts. The journal data may include monetary amounts. The journal data may include data items other than these.

FIG. 5 schematically shows an example of data item 214 of balance data included in accounting data. FIG. 5 also shows an example of the data value of each data item 214.

The balance data may include a data ID for identifying the balance data. The balance data may include the balance date. Balance data may include debit / credit categories. Balanced data may include accounts. The balance data may include an amount. The balance data may include data items other than these.

FIG. 6 schematically shows an example of data item 222 of billing data included in transaction data. FIG. 6 also shows an example of the data value of each data item 222.

The billing data may include a data ID for identifying the billing data. The billing data may include the transaction date. The billing data may include billing information including the name of the billing party. The billing data may include billing content. Billing data may include monetary amounts. The billing data may include data items other than these.

FIG. 7 schematically shows an example of data item 224 of the quotation data included in the transaction data. FIG. 7 also shows an example of the data value of each data item 224.

The quotation data may include a data ID for identifying the quotation data. The estimate data may include an estimate date. The quotation data may include quotation information including the name of the quotation. The quotation data may include the content of the quotation. Estimated data may include monetary amounts. The estimation data may include data items other than these.

FIG. 8 schematically shows an example of data item 232 of financial institution data. FIG. 8 also shows an example of the data value of each data item 232.

The financial institution data may include an account ID that identifies the account. Financial institution data may include balance dates. Financial institution data may include deposit / withdrawal categories. Financial institution data may include monetary amounts. Financial institution data may include data items other than these.

FIG. 9 schematically shows an example of data item 242 of credit information data. FIG. 9 also shows an example of the data value of each data item 242.

The credit information data may include a data ID for identifying the credit information data. The credit information data may include subject information including the subject's name. The credit information data may include a score indicating the creditworthiness of the subject. The credit information data may include data items other than these.

FIG. 10 schematically shows an example of data item 170 of past history data. FIG. 10 also shows an example of the data value of each data item 170.

The past history data may include a target person ID for identifying the target person. The past history data may include subject information including the name of the subject. The historical data may include the loan amount. The historical data may include the loan date. The past history data may include a repayment history. The past history data may include data items other than these.

FIG. 11 schematically shows an example of data item 252 of the characteristic data of the business group. FIG. 11 also shows an example of the data value of each data item 252.

The feature data may include an industry ID that identifies the industry of the business group. The feature data may include a correction period indicating a period to be corrected. The feature data may include a correction target indicating an item to be corrected. The feature data may include correction information indicating the content of the correction. The data values shown in FIG. 11 show an example of increasing the sales in March by 20% for the business group having the industry ID of 00001. The feature data may include data items other than these.

FIG. 12 schematically shows an example of data item 262 of transaction-related data. FIG. 12 also shows an example of the data value of each data item 262.

The business relationship data may include a business ID that identifies the business. The business relationship data may include the name of the business operator. The business relationship data may include a business partner ID, which is a business ID of a business partner of a business identified by a business ID. The business relationship data may include the name of the business partner. The business relationship data may include a collection history for the business operator identified by the business partner business ID by the business operator identified by the business ID. The collection history is, for example, the ratio of the number of claims made by the business operator identified by the business operator ID to the business operator identified by the business partner business ID and the number of collections of the billed amount. The business relationship data may include data items other than these.

FIG. 13 schematically shows an example of the processing flow by the loan determination device 100. Here, an example of the flow from the loan determination device 100 to acquiring the loan application data from the communication terminal 20 and notifying the communication terminal 20 of the result for the loan application data will be described. Each process shown in FIG. 13 is mainly executed by the control unit included in the loan determination device 100.

In the step (the step may be abbreviated as S) 1302, the loan application data transmitted by the business operator wishing to make a loan is acquired by the communication terminal 20. In S1304, the accounting data of the target business operator is acquired. In S1306, past CF information is generated based on the accounting data.

In S1308, various data are acquired. The loan determination device 100 includes transaction data, financial institution data, credit information data, and past history data of the target business operator, characteristic data of the business operator group corresponding to the target business operator, and a business relationship of the business partner of the target business operator. Get at least one of the data. In S1310, future CF information is generated by using the past CF information generated in S1306 and various data acquired in S1308.

In S1312, whether or not to lend to the target business operator is determined based on the future CF information generated in S1310. If it is determined that the loan is possible, the process proceeds to S1314, and if it is determined that the loan is not possible, the process proceeds to S1316.

In S1314, the loan determination device 100 starts the loan procedure for the target business operator. The loan determination device 100 receives, for example, loan procedure data including the content of notifying that the loan is possible and the content of requesting the information necessary for the loan for the loan application data acquired in S1302. Send to. The information required for a loan included in the loan procedure data may be less than the information required for a normal loan application.

In S1316, the target business operator is notified that the loan is rejected. The loan determination device 100 transmits, for example, notification data notifying that the loan is rejected to the communication terminal 20 with respect to the loan application data acquired in S1302.

FIG. 14 schematically shows another example of the processing flow by the loan determination device 100. Here, the flow when the loan determination device 100 executes the process without using the accounting data will be described with respect to the example shown in FIG. Here, the points different from the processing flow shown in FIG. 13 will be mainly described.

In S1402, the loan application data transmitted by the communication terminal 20 is acquired. In S1404, the transaction data of the target business operator is acquired. In S1406, the financial institution data of the target business operator is acquired.

In S1408, past CF information is generated using the financial institution data acquired in S1406. In S1410, various data are acquired. The loan determination device 100 is at least one of the credit information data and past history data of the target business operator, the characteristic data of the business operator group corresponding to the target business operator, and the business relationship data of the business partner of the target business operator. To get. In S1412, future CF information is generated by using the past CF information generated in S1408 and various data acquired in S1410.

In S1414, whether or not to lend to the target business operator is determined based on the future CF information generated in S1412. If it is determined that the loan is possible, the process proceeds to S1416, and if it is determined that the loan is not possible, the process proceeds to S1418. In S1416, the loan procedure is started for the target business operator. In S1418, the target business operator is notified that the loan is rejected.

FIG. 15 schematically shows an example of the functional configuration of the loan determination device 100. The loan determination device 100 includes an application data acquisition unit 102, an accounting data acquisition unit 104, a financial institution data acquisition unit 106, a transaction data acquisition unit 108, an order rate calculation unit 110, a billing payment rate calculation unit 112, and a transaction-related data acquisition unit 114. , Business group identification unit 116, feature data acquisition unit 118, past CF information generation unit 120, probability information generation unit 130, request data transmission unit 142, loan availability determination unit 144, credit rating acquisition unit 146, loan processing execution unit 148, It includes a post-loan management unit 150, a repayment information generation unit 152, and a repayment information transmission unit 154. It is not always essential that the loan determination device 100 has all of these configurations.

The application data acquisition unit 102 acquires loan application data. The application data acquisition unit 102 may receive loan application data from the communication terminal 20. The application data acquisition unit 102 may read out the loan application data received and stored from the communication terminal 20.

The accounting data acquisition unit 104 acquires the accounting data of the target business operator. The accounting data acquisition unit 104 specifies, for example, the target business operator by the loan application data acquired by the application data acquisition unit 102, requests the accounting data of the target business operator from the accounting data management device 210, and requests the accounting data management device 210 to perform the accounting data management device. Receive accounting data from 210. Further, when the loan determination device 100 manages the accounting data of a plurality of business operators, the accounting data acquisition unit 104 may read the accounting data of the target business operator from the accounting data under the control. Further, the accounting data acquisition unit 104 may receive accounting data from the communication terminal 20 that has transmitted the loan application data.

The financial institution data acquisition unit 106 acquires the financial institution data of the target business operator. The financial institution data acquisition unit 106 specifies, for example, a target business operator by the loan application data acquired by the application data acquisition unit 102, requests the financial institution data of the target business operator from the financial institution data management device 230, and finances. Receives financial institution data from the institutional data management device 230. Further, when the loan determination device 100 manages the financial institution data of a plurality of businesses, the financial institution data acquisition unit 106 may read the financial institution data of the target business from the managed financial institution data. Further, the financial institution data acquisition unit 106 may receive the financial institution data certified by the financial institution from the communication terminal 20 that has transmitted the loan application data.

The transaction data acquisition unit 108 acquires the transaction data of the target business operator. The transaction data acquisition unit 108 identifies the target business operator based on the loan application data acquired by the application data acquisition unit 102, requests the transaction data of the target business operator from the transaction data management device 220, and requests the transaction data management device 220. Receive transaction data from 220. Further, when the loan determination device 100 manages the transaction data of a plurality of businesses, the transaction data acquisition unit 108 may read the transaction data of the target business from the managed transaction data. Further, the transaction data acquisition unit 108 may receive transaction data from the communication terminal 20 that has transmitted the loan application data. The transaction data acquisition unit 108 may acquire estimation data as transaction data. Further, the transaction data acquisition unit 108 may acquire billing data as transaction data. Further, the transaction data acquisition unit 108 may acquire order data as transaction data. The order data may be data indicating that an order has been received from another business operator or the like. For example, the order data indicates that the order has been received for the quotation indicated by the quotation data. The order data may include a data ID for identifying the order data. The order data may include the order date. The order data may include ordering party information including the name of the ordering party. The order data may include the contents of the order. The order data may include the amount. The order data may include data items other than these.

The order rate calculation unit 110 calculates the order rate of the target business operator based on the transaction data acquired by the transaction data acquisition unit 108. The order rate calculation unit 110 may calculate the order rate using the estimate data and the order data included in the transaction data. For example, the order rate calculation unit 110 calculates the order rate by dividing the number of quotations by the number of orders corresponding to the quotations. The order rate calculation unit 110 may calculate the order rate using the estimation data and the billing data included in the transaction data. For example, the order rate calculation unit 110 calculates the order rate by dividing the number of quotations by the number of invoices corresponding to the quotations. The order rate calculation unit 110 may calculate the order rate using the estimate data and the billing data, for example, when there is no order data corresponding to the estimate data.

The transaction data may include a correspondence between the quotation and the order, and the order rate calculation unit 110 may specify the number of orders corresponding to the quotation by referring to the correspondence. When the transaction data does not include the correspondence between the quotation and the order, the order rate calculation unit 110 determines the relationship between the quotation date in the quotation data and the order date in the order data, and the quotation destination, the quotation content, and the quotation content in the quotation data. By confirming the match between the amount and the ordering source, order details, and amount in the order data, the order corresponding to the quotation may be specified. The transaction data may include a correspondence between the quotation and the bill, and the order rate calculation unit 110 may specify the number of bills corresponding to the quotation by referring to the correspondence. When the transaction data does not include the correspondence between the quotation and the billing, the order rate calculation unit 110 determines the relationship between the quotation date in the quotation data and the billing date in the billing data, and the quotation destination, the quotation content, and the quotation content in the quotation data. By confirming the match between the amount and the billing address, billing content, and amount in the billing data, the billing corresponding to the estimate may be specified.

The billing payment rate calculation unit 112 calculates the billing payment rate of the target business operator based on the transaction data acquired by the transaction data acquisition unit 108. The billing deposit rate calculation unit 112 may calculate the billing deposit rate using the billing data included in the transaction data. For example, the billing deposit rate calculation unit 112 calculates the billing deposit rate by dividing the number of billing by the number of billing made.

The billing data may include information on whether or not a deposit has been made, and the billing deposit rate calculation unit 112 may specify the number of bills for which a deposit has been made by referring to the information. When the billing data does not include the information, the billing payment rate calculation unit 112 determines whether or not the billing has been made by referring to the financial institution data acquired by the financial institution data acquisition unit 106, for example. May be specified.

The transaction relationship data acquisition unit 114 acquires the transaction relationship data of the transaction partner of the target business operator. The transaction relationship data acquisition unit 114 identifies the transaction partner of the target business operator using the transaction data acquired by the transaction data acquisition unit 108, and requests the transaction relationship data of the specified transaction partner from the transaction relationship management device 260. Transaction relationship data may be received from the transaction relationship management device 260. Further, when the loan determination device 100 manages the transaction relationship and the transaction relationship data between a plurality of businesses, the transaction relationship data acquisition unit 114 uses the managed transaction relationship data to determine the transaction of the transaction partner of the target business operator. The related data may be read out.

The business group identification unit 116 identifies the business group corresponding to the target business. For example, the business group identification unit 116 refers to a list in which a plurality of business groups are registered, and selects a business group corresponding to the target business from the business groups included in the list. Further, the business group specifying unit 116 may specify the business group corresponding to the target business by referring to the list in which the business corresponding to each of the plurality of business groups is registered.

The business group identification unit 116 may specify the business group corresponding to the target business by using the industry information, the scale information, and the like of the target business. The business group identification unit 116 may receive the industry information and the scale information of the target business from the communication terminal 20. In addition, the business group identification unit 116 stores business information including business information and scale information of a plurality of business in advance, and acquires business information and scale information of the target business from the business information. You may.

The feature data acquisition unit 118 acquires the feature data of the business group specified by the business group identification unit 116. The feature data acquisition unit 118 requests, for example, the feature data of the business group specified by the business group identification unit 116 from the business group data management device 250, and receives the feature data from the business group data management device 250. do. Further, when the loan determination device 100 manages the characteristic data of a plurality of business operators, the characteristic data acquisition unit 118 is the business operator group specified by the business operator group identification unit 116 from the managed characteristic data. The feature data may be read out.

The past CF information generation unit 120 generates past CF information of the target business operator. The past CF information generation unit 120 generates past CF information, for example, based on the accounting data acquired by the accounting data acquisition unit 104. The past CF information generation unit 120 uses the data of the account items related to deposits and savings included in the accounting data, and adds or subtracts the transfer details starting from the cash and deposit balance on the record date, for each predetermined period. You may generate past CF information indicating the cash and deposit balance of. For example, the past CF information generation unit 120 generates past CF information indicating the daily, weekly, or monthly cash and deposit balances by adding and subtracting movement details starting from the cash and deposit balance at the beginning of the year. The cash and deposit balance referred to here indicates the total of cash and deposits and savings, but may include the case where cash is 0. That is, the cash and deposit balance may indicate only the deposit and savings balance.

The past CF information generation unit 120 may generate past CF information based on the financial institution data acquired by the financial institution data acquisition unit 106. The past CF information generation unit 120 generates past CF information using the financial institution data acquired by the financial institution data acquisition unit 106, for example, when the accounting data acquisition unit 104 cannot acquire the accounting data. The past CF information generation unit 120, for example, starts from the cash and deposit balance on the record date, and adds or subtracts the transfer details based on the deposit and attendance included in the financial institution data, so that the current cash and deposits are present for each predetermined period. Generates past CF information indicating the deposit balance.

The probability information generation unit 130 generates probability information indicating the probability of loan repayment of the target business operator. The probability information generation unit 130 has a future CF information generation unit 132, a score generation unit 134, and a consistency confirmation unit 136. It is not always essential that the probability information generation unit 130 has all of these configurations.

The future CF information generation unit 132 generates future CF information of the target business operator. The future CF information generation unit 132 may generate future CF information using accounting data, financial institution data, transaction data, feature data, transaction relationship data, past CF information, order rate, and billing / payment rate. The future CF information generation unit 132 may generate future CF information by using all of them, or may generate future CF information by using a part of them.

The future CF information generation unit 132 generates future CF information based on, for example, past CF information. The future CF information generation unit 132 may generate future CF information by averaging the future CF information for a plurality of years or predicting from the past CF information for a plurality of years. The future CF information generation unit 132 derives, for example, a sales generation pattern, a purchase generation pattern, an expense generation pattern, etc. in the past CF information, and generates future CF information using at least one of these. ..

The future CF information generation unit 132 may generate future CF information by using the data of the account items related to the increase / decrease in the future deposit / savings balance among the accounts included in the accounting data. For example, the loan determination device 100 generates CF information in the future by using an account item related to trade receivables and an account item related to trade payables.

As a specific example, the future CF information generation unit 132 generates future CF information using the data of accounts receivable. The future CF information generation unit 132 generates future CF information, for example, assuming that cash and deposits will increase on the scheduled collection date of accounts receivable.

Further, the future CF information generation unit 132 may generate future CF information using the accounts payable data. The future CF information generation unit 132 generates future CF information, for example, assuming that cash and deposits decrease on the scheduled payment date of accounts payable.

Further, the future CF information generation unit 132 may generate future CF information using the data of accounts payable. The future CF information generation unit 132 generates future CF information, for example, assuming that cash and deposits decrease on the scheduled payment date of accounts payable.

Further, the future CF information generation unit 132 may generate future CF information using the data of the advance payment. The future CF information generation unit 132 generates future CF information, assuming that cash and deposits do not decrease on the scheduled payment date of the fee, for example, when the advance payment data indicates that there is an advance payment. As a specific example, the future CF information generation unit 132 may generate future CF information assuming that the cash and deposits do not decrease when the advance payment is larger than the charge. Further, when the advance payment is smaller than the charge, the future CF information generation unit 132 may generate the future CF information from the cash and deposit, assuming that the difference between the charge and the advance payment is reduced.

The future CF information generation unit 132 may generate future CF information using the estimated data and the order rate. For example, the future CF information generation unit 132 generates future CF information on the assumption that the quotation data corresponding to the order rate is received and received from the plurality of quotation data. For example, when the number of quotation data is 5, and the order rate is 80%, CF information is generated in the future assuming that 4 of the 5 quotation data are ordered and deposited.

The future CF information generation unit 132 may generate future CF information using the billing data and the billing payment rate. For example, the future CF information generation unit 132 generates future CF information as the billing data corresponding to the billing payment rate among the plurality of billing data to be deposited. For example, when the number of billing data is 20 and the billing payment rate is 95%, CF information will be generated in the future for 19 of the 20 estimated data as being deposited.

The future CF information generation unit 132 may generate future CF information using the estimation data, the billing data, the order rate, and the billing deposit rate. For example, in the future, the CF information generation unit 132 shall receive an order for the quotation data that matches the order rate among a plurality of quotation data, and shall request the quotation data that matches the billing payment rate. CF information will be generated in the future as if it were to be deposited.

The future CF information generation unit 132 may generate future CF information by using the business relationship data of the trading partner of the target business operator. For example, the future CF information generation unit 132 identifies the payment status of the target business operator to another business operator by using the transaction relationship data, and generates future CF information using the payment status. As a specific example, the future CF information generation unit 132 refers to the transaction relationship data of the trading partner who is the billing destination of the billing data of the target business partner, identifies the payment status of the trading partner to another business partner, and determines the payment status to the other business partner. It is determined whether or not the billing data is paid according to the specified payment status. For example, if the payment rate to another business operator of the transaction partner is lower than a predetermined threshold value, CF information will be generated in the future assuming that payment is not made for the billing data. As a result, CF information can be generated in the future in consideration of the possibility that the trading partner of the target business does not make a payment to the target business. The future CF information generation unit 132 may generate future CF information in consideration of the amount of money to be paid in addition to the payment rate to other businesses of the trading partner.

Further, for example, the future CF information generation unit 132 identifies the trading partner of the trading partner of the target business operator using the transaction relationship data, and generates future CF information using the attribute information of the specified trading partner. As a specific example, the future CF information generation unit 132 refers to the transaction relationship data of the transaction partner who is the billing destination of the billing data of the target business operator, identifies the transaction partner of the transaction partner, and identifies the transaction partner of the specified transaction partner. It is determined whether or not the billing data is paid according to the attribute information. For example, at least one of the business size and creditworthiness of the specified trading partner is compared with the threshold value, and if it is lower than the threshold value, CF information is generated in the future assuming that the billing data is not paid. As a result, CF information can be generated in the future in consideration of the possibility that the trading partner of the target business cannot collect from the trading partner of the trading partner.

Further, for example, the future CF information generation unit 132 generates future CF information by using the difference between the past CF information and the financial institution data. For example, the future CF information generation unit 132 corrects the past CF information based on the difference between the past CF information and the financial institution data, and generates the future CF information using the corrected past CF information. The future CF information generation unit 132 may correct the past CF information so that the difference between the past CF information and the financial institution data is closer to the financial institution data, for example.

The score generation unit 134 generates a score indicating the probability of loan repayment of the target business operator. The score generation unit 134 may generate a score using accounting data, financial institution data, transaction data, feature data, transaction relationship data, past CF information, order rate, and billing / payment rate. The score generation unit 134 may generate a score by using all of them, or may generate a score by using a part of them. The score generation unit 134 may generate a score by using an arbitrary method.

The consistency confirmation unit 136 confirms the consistency of various collected data in determining whether or not to lend to the target business operator with respect to the loan application data received from the communication terminal 20. For example, the consistency confirmation unit 136 confirms the consistency between the balance data acquired by the accounting data acquisition unit 104 and the financial institution data acquired by the financial institution data acquisition unit 106. Further, for example, the consistency confirmation unit 136 checks the consistency between the billing data acquired by the transaction data acquisition unit 108 and the deposit data in the financial institution data acquired by the financial institution data acquisition unit 106.

For example, when the consistency confirmation unit 136 detects inconsistency of data as a result of confirming the consistency, the consistency confirmation unit 136 determines that the data is invalid data. The consistency check unit 136 may generate a data validity score for each data based on the degree of consistency.

The consistency confirmation unit 136 may notify the request data transmission unit 142 of the data determined to be invalid data. The request data transmission unit 142 may transmit the request data including at least one of data correction and additional data submission request to the communication terminal 20 for the data determined to be invalid data by the consistency confirmation unit 136. .. When the consistency confirmation unit 136 receives the correction content of the data and the additional data for the requested data, the consistency confirmation unit 136 may correct the data by using these.

The consistency confirmation unit 136 may notify the request data transmission unit 142 of data having a data validity score lower than a predetermined threshold value. The request data transmission unit 142 includes at least one of data correction and additional data submission request for data for which the consistency confirmation unit 136 determines that the data validity score is lower than a predetermined threshold value. The request data may be transmitted to the communication terminal 20. When the consistency confirmation unit 136 receives the correction content of the data and the additional data for the requested data, the consistency confirmation unit 136 may correct the data by using these.

As described above, the consistency confirmation unit 136 confirms the consistency of the data collected when determining whether or not to lend to the target business operator, so that, for example, an unauthorized application can be detected. In addition, it is possible to prevent the determination of whether or not the loan is possible based on erroneous data.

The loan availability determination unit 144 determines whether or not the loan application data acquired by the application data acquisition unit 102 can be financed to the target business operator by using the probability information generated by the probability information generation unit 130. For example, the loan approval / disapproval determination unit 144 first creates a loan repayment schedule using the loan application amount, desired loan date, and loan period in the loan application data. As a specific example, a repayment schedule showing the monthly repayment amount is created.

Then, the loan availability determination unit 144 determines whether or not the loan is possible by determining whether or not the repayment schedule is feasible based on the future CF information generated by the future CF information generation unit 132. For example, the loan availability determination unit 144 determines whether or not the cash and deposits are insufficient when the monthly repayment amount scheduled to be repaid is subtracted from the cash and deposits of each month indicated by the CF information in the future.

The credit rating acquisition unit 146 acquires the credit rating of the target business operator. The credit rating acquisition unit 146 acquires, for example, the score in the credit information data of the target business as the credit rating of the target business. The credit rating acquisition unit 146 may request the credit information management device 240 for the credit information data of the target business operator and receive the credit information data from the credit information management device 240. Further, when the loan determination device 100 manages the credit information data of a plurality of businesses, the credit rating acquisition unit 146 may read the credit information data of the target business from the credit information data under the control. Further, the credit rating acquisition unit 146 may acquire credit rating information indicating the credit rating of the target business operator by the financial institution as the credit rating of the target business operator. The credit rating acquisition unit 146 may request the financial institution for the credit rating information of the target business operator and receive the credit rating information from the financial institution. Further, the credit rating acquisition unit 146 may receive and store credit rating information of a plurality of businesses from a financial institution, and may read out the credit rating information of the target business from the stored credit rating information.

The credit rating acquisition unit 146 may generate the credit rating of the target business operator by using the credit information data of the business partner of the target business operator. For example, the credit rating acquisition unit 146 deducts the score of the target business operator when the score of the business partner of the target business operator is lower than a predetermined threshold value. Further, for example, when the credit rating acquisition unit 146 has a score higher than a predetermined threshold value of the business partner of the target business, the credit rating acquisition unit 146 adds points to the score of the target business. In addition, the credit rating acquisition unit 146 adds points according to the scores of the business partners of the target business to the scores of the target business. Further, the credit rating acquisition unit 146 may generate the credit rating of the target business operator by using the credit rating information of the business partner of the target business operator. For example, the credit rating acquisition unit 146 deducts the credit rating of the target business operator when the credit rating information of the business partner of the target business operator is lower than a predetermined threshold value. Further, for example, when the credit rating information of the business partner of the target business operator is higher than a predetermined threshold value, the credit rating acquisition unit 146 adds points to the credit rating of the target business operator. In addition, the credit rating acquisition unit 146 adds points according to the credit rating information of the business partner of the target business operator to the credit rating of the target business operator.

The credit rating acquisition unit 146 may generate the credit rating of the target business operator by using the credit information data of the business operators having a chained business relationship with the target business operator. For example, the credit rating acquisition unit 146 weights and adds the score of the target business operator to the score of the business operator having a chain-like business relationship with the target business operator. As the weighting, for example, the weight of the score of the business operator whose chain relationship is farther from the target business operator may be lowered. Further, the credit rating acquisition unit 146 may generate the credit rating of the target business operator by using the credit rating information of the business operators having a chained business relationship with the target business operator. For example, the credit rating acquisition unit 146 weights and adds the credit rating of the target business operator to the value corresponding to the credit rating information of the business operators having a chain-like business relationship with the target business operator. As the weighting, for example, the weight of the score of the business operator whose chain relationship is farther from the target business operator may be lowered.

The credit rating acquisition unit 146 may generate the credit rating of the target business operator by combining a plurality of data existing on the Internet. The credit rating acquisition unit 146 generates the credit rating of the target business operator by using information such as the update frequency of the website operated by the target business operator and the number of site visitors. In addition, the credit rating acquisition unit 146 may generate the credit rating of the target business operator by using the evaluation information indicating the evaluation of the business run by the target business operator on the website operated by a third party. Further, the credit rating acquisition unit 146 may generate the credit rating of the target business operator by using the information about the person related to the target business operator such as the representative of the target business operator. For example, the credit rating acquisition unit 146 generates the credit rating of the target business operator by using the information of the SNS (Social Networking Service) of the representative of the target business operator.

The loan approval / disapproval determination unit 144 may determine whether or not to lend to the target business operator using the creditworthiness of the target business operator generated by the creditworthiness acquisition unit 146. For example, the loan approval / disapproval determination unit 144 determines whether or not the loan is possible if the creditworthiness of the target business operator is low even if there are many cash and deposits indicated by CF information in the future with respect to the repayment schedule. For example, the loan approval / disapproval determination unit 144 registers the credit rating for determining the loan rejection for each difference between the repayment schedule and the cash and deposit indicated by the future CF information, and the credit rating generated by the credit rating acquisition unit 146 is calculated. If the credit rating is lower than the credit rating corresponding to the difference, the loan is judged to be rejected.

Further, for example, the loan approval / disapproval determination unit 144 determines that the loan is possible if the creditworthiness of the target business operator is high, even if the cash and deposits indicated by the CF information in the future are small with respect to the repayment schedule. For example, the loan availability determination unit 144 registers the credit rating for determining that the loan is acceptable for each difference between the repayment schedule and the cash and deposit indicated by the future CF information, and the credit rating generated by the credit rating acquisition unit 146 is , If the credit rating is higher than the credit rating corresponding to the difference, it is judged that the loan is possible.

The loan processing execution unit 148 executes the loan processing according to the determination result by the loan approval / disapproval determination unit 144. For example, when the loan approval / disapproval determination unit 144 determines that the loan is possible, the loan processing execution unit 148 starts the loan procedure. The loan processing execution unit 148 provides the communication terminal 20 with loan procedure data including the content of notifying the communication terminal 20 of the target business that the loan is possible and the content of requesting the information necessary for the loan. You may send it. Further, for example, when the loan approval / disapproval determination unit 144 determines that the loan is possible, the loan processing execution unit 148 makes a loan offer to the target business operator. The loan processing execution unit 148 provides the communication terminal 20 with loan offer data including the content of notifying the communication terminal 20 of the target business that the loan is possible and the content of requesting the information necessary for the loan. You may send it.

When the loan processing execution unit 148 determines that the loan is not possible by the loan approval / disapproval determination unit 144, the loan processing execution unit 148 may notify the target business operator that the loan is not possible. The loan processing execution unit 148 transmits, for example, notification data notifying the communication terminal 20 of the target business operator that the loan has been rejected.

The post-loan management unit 150 manages the target business operator after the loan is made. After the loan is made, the post-loan management unit 150 causes the future CF information generation unit 132 to continuously generate future CF information of the target business operator, for example. Then, when it is detected that the loan repayment may be hindered based on the CF information in the future, the post-loan management unit 150 notifies the person in charge of collecting the loan to that effect. The post-loan management unit 150 determines that the loan repayment may be hindered, for example, if the cash and deposits of the newly generated future CF information in each month are less than the monthly repayment amount.

When it is detected that the loan repayment may be hindered, the post-loan management unit 150 may execute a process such as accelerating the timing of reminding to send to the target business operator. The post-loan management unit 150 executes various processes in a manner that does not deviate from the purpose of the Money Lending Business Act.

The repayment information generation unit 152 generates repayment information. The repayment information is, for example, a loan repayment schedule. The repayment information generation unit 152 may generate a repayment schedule according to the purpose by using the CF information in the future. For example, the repayment information generation unit 152 generates a repayment schedule when repayment is made by profit, a repayment schedule when repayment is made by cash flow, and the like.

The repayment information generation unit 152 may generate a loan repayment schedule using the CF information in the future when the loan availability determination unit 144 determines that the loan is possible. For example, the repayment information generation unit 152 refers to future CF information, identifies a month in which the amount of cash and deposits is larger than in other months, and generates a repayment schedule in which the repayment amount in that month is larger than in other months. do.

The repayment information transmission unit 154 may transmit the repayment information generated by the repayment information generation unit 152 to the communication terminal 20 of the target business operator. This makes it possible to flexibly propose a repayment schedule to the target business operator.

The repayment information generation unit 152 may generate a repayment schedule that can be financed by using the CF information in the future when the loan approval / disapproval determination unit 144 determines that the loan is not possible. For example, the repayment information generation unit 152 generates a repayment schedule in which at least a part of the loan application data is changed.

For example, the repayment information generation unit 152 generates a repayment schedule when the loan date is changed when it can be determined that the loan is possible by changing the desired loan date included in the loan application data using the CF information in the future. do. As a specific example, if the desired loan date included in the loan application data is April 2017, and the loan is rejected as it is, but the loan can be made by changing the loan date to July 2017, July 2017 is set. Generate a repayment schedule for the loan date.

Further, the repayment information generation unit 152 generates a repayment schedule with a changed loan period when it can be determined that the loan is possible by changing the loan period included in the loan application data using the CF information in the future. As a specific example, if the loan period included in the loan application data is June and the loan is rejected as it is, but the loan can be made by changing the loan period to October, the repayment schedule will be set to October. Generate.

By transmitting the repayment information to the communication terminal 20 of the target business operator, the repayment information transmission unit 154 can inform the target business operator that the loan can be made by changing the conditions of the loan application data. For example, if the business of the target business is agriculture, it is difficult to distribute the loan amount evenly to repay each month, but it may be possible to repay all at once during the harvest season. The characteristics of repayment ability differ depending on the business. According to the repayment information generation unit 152 according to the present embodiment, a repayment schedule suitable for the cash flow indicated by the future CF information of the target business operator can be generated, so that the repayment schedule can be flexibly provided according to the situation of the target business operator. be able to.

FIG. 16 schematically shows an example of the functional configuration of the account management device 300. The account management device 300 includes an account management unit 302, a data acquisition unit 304, a future CF information generation unit 306, a payment request acquisition unit 308, a payment processing execution unit 310, a loan availability determination unit 312, a loan repayment execution unit 314, and interest rate processing execution. A unit 316 and an instruction receiving unit 318 are provided. It is not always essential that the account management device 300 has all of these configurations.

The account management unit 302 manages the account balances of a plurality of businesses. The account management unit 302 may open an account for the business operator in response to a request from the business operator. The account management unit 302 manages the accounts of a plurality of businesses in, for example, one or a plurality of bank accounts. As a specific example, the account management unit 302 manages the account balances of N business operators or a larger number of business operators in N bank accounts. The account management unit 302 manages the accounts of a plurality of businesses in a bank account in the name of the administrator of the account management device 300, for example.

The data acquisition unit 304 acquires various data. The data acquisition unit 304 may acquire accounting data, financial institution data, transaction data, feature data, transaction-related data, past CF information, order rate, and billing / payment rate. The data acquisition unit 304 may acquire all of them, or may acquire a part of them.

The future CF information generation unit 306 uses the data acquired by the data acquisition unit 304 to generate future CF information of the business operator who manages the account. The future CF information generation unit 306 may generate future CF information of the business operator based on at least one of accounting data and transaction data. The future CF information generation unit 306 may generate future CF information by executing the same processing as the future CF information generation unit 132.

The payment request acquisition unit 308 acquires a payment request to a business partner from a business operator that manages an account. The payment request includes, for example, the payee's account number and the payment amount. The payment request acquisition unit 308 receives, for example, the payment request transmitted by the communication terminal 20. The business operator who made the payment request may be described as the target business operator.

The payment processing execution unit 310 executes payment processing in response to the payment request acquired by the payment request acquisition unit 308. The payment processing execution unit 310 may execute payment processing when the account balance of the target business operator is larger than the payment amount of the payment request. The payment processing execution unit 310 remits the payment amount to, for example, the account number of the payment destination of the payment request. The payment processing execution unit 310 may present an instruction to remit the payment amount to the payment destination account number of the payment request to the operator or the like of the account management device 300. The payment processing execution unit 310 subtracts the payment amount from the account balance in connection with the payment. When the account balance of the target business operator is smaller than the payment amount of the payment request, the payment processing execution unit 310 causes the loan approval / disapproval determination unit 312 to determine whether or not to lend to the target business operator.

The loan availability determination unit 312 determines whether or not to lend to the target business operator. The loan approval / disapproval determination unit 312 may determine whether or not to lend to the target business operator based on the future CF information of the target business operator generated by the future CF information generation unit 306. The loan approval / disapproval determination unit 312 may determine whether or not a loan is possible by executing the same processing as the loan approval / disapproval determination unit 144.

The loan approval / disapproval determination unit 312 may determine whether or not to lend to the target business operator in response to a request from the payment processing execution unit 310. For example, the loan approval / disapproval determination unit 312 determines whether or not to lend a loan amount equal to or greater than the difference between the payment amount of the payment request and the account balance of the target business operator.

The loan availability determination unit 312 determines, for example, whether or not to finance the difference between the payment amount of the payment request and the account balance of the target business operator. In addition, the loan approval / disapproval determination unit 312 may determine whether or not to lend an amount obtained by adding a predetermined amount to the difference between the payment amount of the payment request and the account balance of the target business operator. The predetermined amount may be determined by the administrator of the account management device 300, the target business operator, or the like as the minimum necessary amount for the account balance of the target business operator.

When the loan availability determination unit 312 determines that the loan is possible, the account management unit 302 may add the loan amount to the account balance of the target business operator. The account management unit 302 adds, for example, the difference between the payment amount of the payment request and the account balance of the target business operator to the account balance of the target business operator. Further, the account management unit 302 adds, for example, an amount obtained by adding a predetermined amount to the difference between the payment amount of the payment request and the account balance of the target business operator to the account balance of the target business operator.

The loan approval / disapproval determination unit 312 may periodically determine whether or not to lend to the business operator that manages the account. The loan availability determination unit 312 periodically determines, for example, the loanable limit to the business operator that manages the account. The loan availability determination unit 312 may notify the account management unit 302 of the loanable amount. The account management unit 302 may present the loanable limit determined by the loan availability determination unit 312 to the business operator who manages the account. As a result, the business operator can grasp how much loan can be obtained at the present time.

The loan repayment execution unit 314 monitors the account balance of the target business operator after the loan amount is added to the account balance by the account management unit 302 and the payment processing is executed by the payment processing execution unit 310. Then, the loan repayment execution unit 314 executes the repayment process from the account balance according to the predetermined conditions. For example, the loan repayment execution unit 314 subtracts the loan amount from the account balance when the account balance of the target business operator is larger than the loan amount. The deducted loan amount will be used to repay the loan. Further, the loan repayment execution unit 314 may execute a repayment process in order to repay the loan amount in stages. For example, the loan repayment execution unit 314 subtracts the difference between the account balance and the predetermined threshold value from the account balance when the account balance of the target business operator is smaller than the loan amount. As a specific example, when the loan amount is 1,000, the account balance is 500, and the predetermined threshold value is 300, the loan repayment execution unit 314 accounts 200, which is the difference between the account balance and the threshold value. Subtract from the balance. The deducted amount will be used to repay the loan.

The interest rate processing execution unit 316 monitors the account balance of the target business operator after the loan amount is added to the account balance by the account management unit 302 and the payment processing is executed by the payment processing execution unit 310. Then, the interest rate processing execution unit 316 may subtract the interest rate amount determined according to the predetermined interest rate rule from the account balance when the account balance of the target business operator is smaller than the loan amount. The deducted interest rate will be used to pay interest on the loan amount. The interest rate processing execution unit 316 subtracts the interest rate amount from the account balance according to a predetermined timing regardless of the amount of the account balance of the target business operator. For example, even if the interest rate is 50 and the account balance of the target business operator is -300 with a loan balance of 300, when the timing comes, 316 subtracts 50 to obtain the account balance. -350. As long as it is within the credit line, the actual repayment may be made when the account balance exceeds a predetermined threshold.

The instruction receiving unit 318 receives an instruction for the managed account from the communication terminal 20 of the business operator. The instruction receiving unit 318, for example, withdraws money from the managed account to the account designated by the business operator.

FIG. 17 schematically shows an example of the hardware configuration of the computer 1000 that functions as the loan determination device 100 or the account management device 300. The computer 1000 according to the present embodiment includes a CPU peripheral portion having a CPU 1010, a RAM 1030, and a graphic controller 1085 connected to each other by a host controller 1092, a ROM 1020 connected to the host controller 1092 by an input / output controller 1094, and a communication I /. It includes an input / output unit having an F1040, a hard disk drive 1050, a DVD drive 1070, and an input / output chip 1080.

The CPU 1010 operates based on the programs stored in the ROM 1020 and the RAM 1030, and controls each part. The graphic controller 1085 acquires image data generated on a frame buffer provided in the RAM 1030 by the CPU 1010 or the like, and displays the image data on the display 1090. Alternatively, the graphic controller 1085 may include a frame buffer internally for storing image data generated by the CPU 1010 or the like.

The communication I / F 1040 communicates with other devices via a network by wire or wirelessly. Further, the communication I / F 1040 functions as hardware for communication. The hard disk drive 1050 stores programs and data used by the CPU 1010. The DVD drive 1070 reads a program or data from the DVD-ROM 1072 and provides it to the hard disk drive 1050 via the RAM 1030.

The ROM 1020 stores a boot program executed by the computer 1000 at startup, a program depending on the hardware of the computer 1000, and the like. The input / output chip 1080 connects various input / output devices to the input / output controller 1094 via, for example, a parallel port, a serial port, a keyboard port, a mouse port, and the like.

The program provided to the hard disk drive 1050 via the RAM 1030 is stored in a recording medium such as a DVD-ROM 1072 or an IC card and provided by the user. The program is read from the recording medium, installed in the hard disk drive 1050 via the RAM 1030, and executed in the CPU 1010.

A program installed in the computer 1000 that causes the computer 1000 to function as the loan determination device 100 or the account management device 300 works on the CPU 1010 or the like to cause the computer 1000 to function as each part of the loan determination device 100 or the account management device 300, respectively. good. The information processing described in these programs is read into the computer 1000, and the application data acquisition unit 102 and the accounting data acquisition unit, which are specific means in which the software and the various hardware resources described above cooperate with each other, are used. 104, financial institution data acquisition unit 106, transaction data acquisition unit 108, order rate calculation unit 110, billing payment rate calculation unit 112, transaction-related data acquisition unit 114, business group identification unit 116, feature data acquisition unit 118, past CF Information generation unit 120, probability information generation unit 130, request data transmission unit 142, loan availability determination unit 144, credit rating acquisition unit 146, loan processing execution unit 148, post-loan management unit 150, repayment information generation unit 152, and repayment information transmission. It functions as a unit 154. Further, the information processing described in these programs is read into the computer 1000, and is a specific means in which the software and the various hardware resources described above cooperate with each other. The account management unit 302 and the data acquisition unit. It functions as 304, future CF information generation unit 306, payment request acquisition unit 308, payment processing execution unit 310, loan availability determination unit 312, loan repayment execution unit 314, interest rate processing execution unit 316, and instruction receiving unit 318. Then, by realizing the calculation or processing of information according to the purpose of use of the computer 1000 in the present embodiment by these specific means, a loan determination device 100 or an account management device 300 peculiar to the purpose of use is constructed. Will be done.

Although the present invention has been described above using the embodiments, the technical scope of the present invention is not limited to the scope described in the above embodiments. It will be apparent to those skilled in the art that various changes or improvements can be made to the above embodiments. It is clear from the description of the claims that the form with such changes or improvements may be included in the technical scope of the present invention.

The order of execution of each process, such as operation, procedure, step, and step in the apparatus, system, program, and method shown in the claims, specification, and drawings, is particularly "before" and "prior to". It should be noted that it can be realized in any order unless the output of the previous process is used in the subsequent process. Even if the scope of claims, the specification, and the operation flow in the drawings are explained using "first", "next", etc. for convenience, it means that it is essential to carry out in this order. It's not a thing.

10 network, 20 communication terminals, 22 data items, 100 loan judgment device, 102 application data acquisition department, 104 accounting data acquisition department, 106 financial institution data acquisition department, 108 transaction data acquisition department, 110 order rate calculation department, 112 billing payment Rate calculation unit, 114 Transaction-related data acquisition unit, 116 Business group identification unit, 118 Feature data acquisition unit, 120 Past CF information generation unit, 130 Probability information generation unit, 132 Future CF information generation unit, 134 Score generation unit, 136 Consistency confirmation unit, 142 request data transmission unit, 144 loan availability determination unit, 146 credit rating acquisition unit, 148 loan processing execution department, 150 post-finance management department, 152 repayment information generation unit, 154 repayment information transmission unit, 170 data items, 182 past CF information, 184 future CF information, 210 accounting data management device, 212 data item, 214 data item, 220 transaction data management device, 222 data item, 224 data item, 230 financial institution data management device, 232 data item, 240 Credit information management device, 242 data items, 250 business group data management device, 252 data items, 260 business relationship management device, 262 data items, 300 account management device, 302 account management department, 304 data acquisition department, 306 future CF information Generation unit, 308 payment request acquisition unit, 310 payment processing execution unit, 312 loan availability determination unit, 314 loan repayment execution unit, 316 interest rate processing execution unit, 318 instruction receiving unit, 1000 computer, 1010 CPU, 1020 ROM, 1030 RAM, 1040 communication I / F, 1050 hard disk drive, 1070 DVD drive, 1072 DVD-ROM, 1080 input / output chip, 1085 graphic controller, 1090 display, 1092 host controller, 1094 input / output controller

Claims (14)

The account management department that manages the account balance of the business operator,
A future CF information generation unit that generates future CF information indicating the future cash flow of the business operator by analyzing accounting data related to the accounting of the business operator.
The payment request acquisition unit that acquires the payment request including the payment amount to the business partner by the business operator,
A payment processing execution unit that executes payment processing for the payment request when the account balance of the business operator is larger than the payment amount of the payment request.
When the account balance of the business operator is smaller than the payment amount of the payment request, it is automatically determined whether or not the loan amount equal to or larger than the difference between the payment amount and the account balance can be loaned to the business operator. The loan approval / disapproval determination unit creates a loan repayment schedule using the loan amount, the loan date and the loan period when the loan is made for the loan amount, and the repayment schedule is realized by the future CF information. It is equipped with a loan availability determination unit that determines whether or not a loan can be made by determining whether or not it is possible .
The account management unit is an account management device that adds the loan amount to the account balance of the business operator when the loan availability determination unit determines that the loan is possible. The account management device according to claim 1, wherein the loan admissibility determination unit determines whether or not to lend the difference between the payment amount of the payment request and the account balance of the business operator. The first aspect of claim 1, wherein the loan admissibility determination unit determines whether or not to lend an amount obtained by adding a predetermined amount to the difference between the payment amount of the payment request and the account balance of the business operator. Account management device. The loan approval / disapproval determination unit adds an amount predetermined as the minimum required amount for the account balance of the business operator to the difference between the payment amount of the payment request and the account balance of the business operator. The account management device according to claim 3, which determines whether or not to lend. The claim that the payment processing execution unit executes payment processing for paying the payment amount from the account balance to the business partner after the loan amount is added to the account balance of the business operator by the account management unit. The account management device according to any one of 1 to 4. After the loan amount is added to the account balance of the business operator by the account management unit, and then the payment process of paying the payment amount from the account balance to the business partner is executed by the payment processing execution unit. The account management device according to claim 5, further comprising a loan repayment execution unit that monitors the account balance of the business operator and executes repayment processing from the account balance according to predetermined conditions. The loan repayment execution unit subtracts the loan amount from the account balance when the account balance of the business operator is larger than the loan amount, and when the account balance of the business operator is smaller than the loan amount. The account management device according to claim 6, wherein the difference between the account balance and a predetermined threshold value is subtracted from the account balance. After the loan amount is added to the account balance of the business operator by the account management unit, and then the payment process of paying the payment amount from the account balance to the business partner is executed by the payment processing execution unit. An interest rate processing execution unit that monitors the account balance of the business operator and subtracts the interest rate amount determined according to a predetermined interest rate rule from the account balance when the account balance of the business operator is less than the loan amount. The account management device according to claim 5, further comprising. The account management device according to claim 8, wherein the interest rate processing execution unit subtracts the interest rate amount from the account balance according to a predetermined timing regardless of the amount of the account balance of the business operator. The loan approval / disapproval determination unit determines whether or not the cash and deposits are insufficient when the monthly repayment amount scheduled to be repaid is subtracted from the cash and deposits of each month indicated by the future CF information. The account management device according to any one of claims 1 to 9 , which determines whether or not a loan can be made. The future CF information generation unit acquires past CF information indicating the past cash flow of the business operator for a plurality of years by analyzing the accounting data, and the past CF information for a plurality of years is used for one year. The account management device according to any one of claims 1 to 10, which will generate CF information in the future. The eleventh claim, wherein the future CF information generation unit generates the future CF information by at least one of the averaging of the past CF information for the plurality of years and the prediction from the past CF information for the plurality of years. The account management device described. The future CF information generation unit derives the sales generation pattern, the purchase generation pattern, and the expense generation pattern in the past CF information for the plurality of years, and the sales generation pattern and the purchase generation pattern. The account management device according to claim 11 , wherein the future CF information is generated using the expense generation pattern. A program for operating a computer as the account management device according to any one of claims 1 to 13 .

Images