Trade receivables platform service method and system

Abstract

The present invention relates to a platform service method having the functions of managing information about trade receivables held and transferring and receiving trade receivables. An embodiment of the present invention includes: a step in which a first terminal device transmits, to a server computer, information about trade receivables input by a transferor, and the server computer registers the received information about the trade receivables; a step in which the first terminal device transmits, to the server computer, identification information about trade receivables the transferor has requested to transfer, and the server computer updates the state of the trade receivables, corresponding to the received identification information about the trade receivables, to a transfer requested state; and a step in which the second terminal device transmits, to the server computer, the identification information about trade receivables, the receipt of which a transferee has approved, and the server computer updates the state of the trade receivables, corresponding to the received identification information about the trade receivables, to a reception approved state.

Description

Sales receivable platform service method and system

[0001] The present invention relates to a platform service method having a function of managing information on accounts receivable held and transferring and receiving accounts receivable.

[0002] And it relates to a platform service method having a function of evaluating the price of accounts receivable and recommending accounts receivable to be transferred to a user.

[0003]

[0004] Trade receivables are debts arising from the sale of a company's goods. Examples include accounts receivable and notes receivable. Companies with trade receivables can transfer them to financial institutions to raise funds.

[0005] The domestic annual market for accounts receivable is approximately 4,100 trillion won. Industrial complexes, fund companies, banks, and corporations are engaging in factorsing and other businesses to securitize accounts receivable. However, current businesses struggle to accommodate the volume of accounts receivable transactions, preventing the creation of a market of adequate size.

[0006] In addition, there is a problem that the trading of accounts receivable is not active due to the difficulty in easily concluding a trade in accounts receivable between a company that wants to transfer accounts receivable and an institution or individual that wants to acquire them, and the inconvenience of inconsistent transaction methods.

[0007]

[0008] The purpose of the present invention is to solve the above problems, and to provide a method and system for a sales receivable platform service having the function of managing information on sales receivables held and transferring and receiving sales receivables.

[0009] And, it provides a method and system for a sales receivable platform service having a function of evaluating the price of sales receivable and recommending sales receivables to be transferred to users.

[0010]

[0011] In order to achieve the above object, one embodiment of the present invention includes a step in which a first terminal device transmits information on a sales receivable entered by a transferor to a server computer, and the server computer registers the information on the received sales receivable; a step in which the first terminal device transmits identification information on a sales receivable for which a transferor has applied for transfer to the server computer, and the server computer updates the status of the sales receivable corresponding to the identification information on the sales receivable received to a transfer application status; and a step in which a second terminal device transmits identification information on a sales receivable for which a transferee has approved transfer to the server computer, and the server computer updates the status of the sales receivable corresponding to the identification information on the sales receivable received to a transfer approval status.

[0012] Another embodiment of the present invention includes a first terminal device that receives, from a transferor, a command to register a sales receivable, to search for information on registered sales receivables, and to apply for transfer of sales receivables; a second terminal device that receives, from a transferee, a command to search for information on registered sales receivables and to approve transfer of sales receivables; and a server computer that receives request messages from the first terminal device and the second terminal device, processes a task in response to the request message, and then processes and transmits the processing result as a response message.

[0013]

[0014] The present invention can activate transactions of accounts receivable by providing a platform service that supports the transfer and acceptance of accounts receivable and recommends accounts receivable according to the user's preferences, and can support easy management of registered accounts receivable information and transaction information.

[0015] Furthermore, by enabling safer transactions through credit screening and quantification of non-financial information, and by calculating the positive amount of accounts receivable by considering the cost of procurement and credit risk, the securitization of accounts receivable can be promoted.

[0016] Additionally, when calculating the required cost, the probability of default of the issuer of accounts receivable can be reflected in the adjustment coefficient, allowing for more accurate calculation of the positive amount.

[0017]

[0018] FIG. 1 is a diagram illustrating a sales receivable platform service system according to a first embodiment of the present invention.

[0019] FIG. 2 is a drawing illustrating a sales receivable platform service method according to one embodiment of the present invention.

[0020] FIG. 3 is a diagram showing the configuration of a server computer in a second embodiment of the present invention.

[0021] FIG. 4 is a diagram showing the configuration of a server computer in a third embodiment of the present invention.

[0022] FIG. 5 is a diagram illustrating a process for classifying user groups in a third embodiment of the present invention.

[0023] FIG. 6 is a diagram showing a computing device included in each configuration in one embodiment of the present invention.

[0024] The present invention can be implemented with various modifications without departing from the spirit or scope of the invention, and may have one or more embodiments. Furthermore, the embodiments described in the "Specific Description for Carrying Out the Invention" and "Drawings" sections of the present invention are examples intended to specifically illustrate the invention and do not limit or restrict the scope of the invention.

[0025] Accordingly, anything that a person with ordinary knowledge in the technical field to which the present invention belongs can easily infer from the “specific contents for carrying out the invention” and “drawings” of the present invention can be interpreted as falling within the scope of the present invention.

[0026] In addition, the size and shape of each component shown in the drawing may be exaggerated for the purpose of explaining the embodiment, and do not limit the size and shape of the invention actually implemented.

[0027] Unless specifically defined, terms used in the specification of the present invention may have the same meaning as commonly understood by a person of ordinary skill in the art to which the present invention pertains.

[0028] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

[0029]

[0030] FIG. 1 is a diagram illustrating a sales receivable platform service system according to a first embodiment of the present invention.

[0031] A sales receivable platform service system (100) according to one embodiment of the present invention may include a server computer (110), a first terminal device (120), and a second terminal device (130).

[0032] The server computer (110) can provide services related to the management and transaction of accounts receivable to transferors and transferees of accounts receivable. The server computer (110) can receive request messages from terminal devices used by transferors and transferees of accounts receivable, process tasks in response to the request messages, and then process the processing results into a response message and transmit them to the terminal devices.

[0033] A server computer (110) may be a collection of multiple computing devices connected to each other via a computer network. For example, the server computer (110) may be composed of multiple rack-mount servers, blade servers, etc., and may be connected to a network device such as a router.

[0034] The sales receivable platform service may include functions for registering sales receivables, searching for information on registered sales receivables, applying for transfer of sales receivables, and approving the transfer of sales receivables.

[0035] The server computer (110) includes a relational database and may include tables for storing information on transferors and transferees using the sales receivable platform service, information on sales receivables, and transaction information on sales receivables.

[0036] The first terminal device (120) is a computing device used by the transferor holding the accounts receivable. The first terminal device (120) can execute a first application software installed therein. The first application software may be a web browser or a program implementing a client-server architecture. When the first terminal device (120) executes the first application software, it can display a first user interface on the first terminal device (120) in response to commands included in the first application software. Furthermore, the first terminal device (120) can process tasks in response to input from the transferor, transmit messages and data to the server computer (110), or receive them from the server computer (110).

[0037] The transferor can register accounts receivable, view information about registered accounts receivable, and submit an application for transfer of accounts receivable through the first user interface. The first terminal device (120) can process the menu selected by the transferor and the information entered into data and transmit it to the server computer (110).

[0038] The second terminal device (130) is a computing device used by the transferee to whom the accounts receivable are transferred. The second terminal device (120) can execute second application software installed therein. The second application software may be a web browser or a program implementing a client-server architecture. When the second terminal device (120) executes the second application software, it can display a second user interface on the second terminal device (130) in response to commands included in the second application software. Furthermore, it can process tasks in response to input from the transferee, transmit messages and data to the server computer (110), or receive them from the server computer (110).

[0039] The assignee can view information on registered accounts receivables and enter information to approve the assignment of accounts receivables through the second user interface. The second terminal device (130) can process the menu selected by the assignee and the information entered into data and transmit it to the server computer (110).

[0040] FIG. 2 is a drawing showing a sales receivable platform service method according to the first embodiment of the present invention.

[0041] Each step of the sales receivable platform service method according to the first embodiment of the present invention may be executed selectively or in a different order, unless other steps depend on it.

[0042] In the sales receivable registration step (S1010), the transferor holding the sales receivable can register the information of the sales receivable in the sales receivable platform service system.

[0043] The transferor can enter information about the accounts receivable in the first user interface. For example, the transferor can enter the creditor's business registration number, company name, representative name, contract name for the accounts receivable, contract amount, and contract execution date in the first user interface.

[0044] When the transferor selects a menu for registering information on a sales receivable in the first user interface, the first terminal device (120) can process the information entered by the transferor into data and transmit it to the server computer (110) along with a message requesting registration. The server computer (110) can store the information entered by the transferor in a database in response to the received registration request message.

[0045] The transferor can input a keyword in the first user interface and select a menu to search for registered accounts receivable. The first terminal device (120) can transmit the keyword input by the transferor to the server computer (110). The server computer (110) can search for registered accounts receivable using the received keyword, process the list into data, and then transmit it to the first terminal device (120). The first terminal device (120) can display a list of received accounts receivables in the first user interface.

[0046] The transferor can select a menu to view information on accounts receivable in the first user interface. The first terminal device (120) can transmit identification information of the accounts receivable for which the transferor has requested a search to the server computer (110). The server computer (110) can search for accounts receivable using the received identification information, process the information on the accounts receivable into data, and then transmit it to the first terminal device (120). The first terminal device (120) can display the received information on the accounts receivable in the first user interface.

[0047] At the transfer application stage (S1020), the transferor can apply for transfer of the sales receivable to the sales receivable platform service system.

[0048] The transferor can select a menu item in the first user interface to request the transfer of registered accounts receivable. The first terminal device (120) can transmit a message requesting a list of registered accounts receivable to the server computer (110). The server computer (110) can process the list of registered accounts receivable into data and then transmit it to the first terminal device (120). The first terminal device (120) can display the list of registered accounts receivable on the first user interface.

[0049] The transferor can select a menu item for requesting a transfer of accounts receivable from the list displayed on the first user interface. The first terminal device (120) can display a form for entering information necessary for the transfer of accounts receivable on the first user interface. For example, the form can include information such as the transfer price of the accounts receivable, the transfer period, and other transfer conditions. When the transferor enters the necessary information on the first user interface, the first terminal device (120) can transmit the entered information to the server computer (110). The server computer (110) can then add the received input information to its database.

[0050] The server computer (110) can process the result of the application for transfer of sales receivables into a message and transmit it to the first terminal device (120). The first terminal device (120) can display the received application result message on the first user interface.

[0051] The transfer approval step (S1030) allows the transferee to approve the transfer of the sales receivable to the sales receivable platform service system.

[0052] The transferee can select a menu for transferring the requested accounts receivable from the second user interface. The second terminal device (130) can transmit a message requesting a list of requested accounts receivable to the server computer (110). The server computer (110) can process the list of requested accounts receivable into data and then transmit it to the second terminal device (130). The second terminal device (130) can display the list of requested accounts receivable on the second user interface.

[0053] The assignee can select a menu item to approve the assignment of accounts receivable from the list displayed on the second user interface. The second terminal device (130) can display a form for entering the information required for the assignment of accounts receivable on the second user interface. When the assignee enters the required information on the second user interface, the second terminal device (130) can transmit the entered information to the server computer (110). The server computer (110) can then add the received input information to its database.

[0054] The server computer (110) can process the result of approving the transfer of sales receivables into a message and transmit it to the second terminal device (130). The approval result message received by the second terminal device (130) can be displayed on the second user interface.

[0055] FIG. 3 is a diagram showing the configuration of a server computer in a second embodiment of the present invention.

[0056] The configuration and operation method of the sales receivable platform service system according to the second embodiment of the present invention may be the same as the corresponding configuration and operation method of the first embodiment, except for what is additionally described.

[0057] In a second embodiment, the system may include functions for reviewing and evaluating the counterparty's credit when transacting accounts receivable, and functions for quantifying non-financial information to determine the appropriate amount of accounts receivable. Accounts receivables may also be issued by the seller to employees of the seller in exchange for services or goods provided by the seller.

[0058] In the second embodiment, the server computer (210) can execute functions such that the issuer of accounts receivable issues accounts receivable, manages accounts receivable by transaction, and transfers the accounts receivable to a transferee. Furthermore, the server computer (210) can execute functions such as calculating the transfer amount of accounts receivable, and when the transferee pays the transfer amount, the accounts receivable is transferred to the transferee, and the transfer amount is paid to the transferor.

[0059] The server computer (210) can transmit and receive data to and from a third-party system (T) via a computer network. The third-party system (T) is a system operated by a credit rating agency, credit information company, bank, securities company, Financial Supervisory Service, etc., and can transmit a business's credit information and financial information (credit grant information, delinquency information, etc.) to the server computer (210).

[0060] The server computer (210) may include a credit information evaluation unit (211), a quantitative factor calculation unit (212), a required cost calculation unit (213), and a sales receivable evaluation unit (214).

[0061] The credit information evaluation unit (211) can obtain, review, and evaluate the credit information of parties to a sales receivable transaction (creditor, debtor). The credit information evaluation unit (211) can receive credit information data from a third-party system (T) and evaluate the credit information of parties to a sales receivable transaction.

[0062] Credit information data may include, for example, credit ratings based on a company's credit rating information, the fair book value of total assets, absolute quantitative figures of total sales based on National Tax Service data, operating profit margin, operating profit margin to total assets, current ratio, interest coverage ratio, return on equity (ROE), and processed quantitative figures of debt dependence.

[0063] The quantitative factor calculation unit (212) can calculate non-financial factors as quantifiable factors based on a company's market evaluation. The quantitative factor calculation unit (212) can calculate non-financial factors as quantifiable factors using textual information based on the external market environment.

[0064] The quantitative factor calculation unit (212) can determine at least one abnormal verification factor by specifying the transaction purpose, transaction request size, transaction request industry and business conditions, past transaction history, major shareholders and equity relationships, and corporate type as the primary evaluation factors of non-financial factors. Then, transaction relationships, industry-specific construction capability evaluation amounts, and medical foundation ratings can be selected as secondary evaluation factors. The quantitative factor calculation unit (212) can determine the score value for each evaluation item, individual scoring options, and the range of the total score.

[0065] The purpose of the transaction is given points for the purpose of issuing accounts receivable, the size of the transaction request is given points for the amount of accounts receivable to be issued, the industry and business conditions of the transaction request are given points for the business conditions of both or more parties to the transaction, the past transaction history is given points for the past history of accounts receivable of the transaction counterparty, the major shareholder and equity relationship items are given points for the type of shareholder of the transaction counterparty, and the corporate form can be given points for whether the transaction counterparty is listed or externally audited.

[0066] The required cost calculation unit (213) can calculate credit risk costs from the transaction costs and holding period of accounts receivable. The required cost calculation unit (213) can calculate transaction costs by multiplying the issuance price of accounts receivable by the transferee's cost of financing other people's capital.

[0067] In terms of the buyer's market capital procurement cost, the correlation between the base interest rate of the cost of other people's capital procurement and the new transaction amount interest rate of the Cost of Funds Index (COFIX) may be a positive function.

[0068] The cost calculation unit (213) can calculate the cost of the transferee's cost of procuring external capital. Since the transferee must bear the cost of procuring funds for a certain period of time before and after the acquisition and holding period of the company's accounts receivable expires, an opportunity cost corresponding to the acquired funds may be incurred. The market value of this opportunity cost can be expressed as the cost of procuring external capital. For example, when the transferee acquires accounts receivable from a financial institution such as a bank, the portion of the accounts receivable balance applied with external borrowing rates, such as bank interest rates, can be calculated as the cost of procuring external capital. The following mathematical formula represents the cost of procuring external capital.

[0069]

[0070] (a represents the cost of financing other people's capital, b represents the balance of accounts receivable, and c represents the coefficient of the cost of financing other people's capital.)

[0071] The cost of borrowing from others can be determined by the external borrowing rate actually used by the transferee when using a financial institution such as a bank, or by the average lending rate of the financial institution when the transferee uses its own funds. The required cost calculation unit (213) can receive information on external borrowing rates or average lending rates from a third-party system (T) of the financial institution. The required cost calculation unit (213) or the accounts receivable evaluation unit (214) can store the received information in a database.

[0072] The cost calculation unit (213) may include, in addition to the cost of raising capital from others, the cost corresponding to various expenses until the transaction is completed as transaction costs. These various expenses may include one or more of fees, management costs, and authentication costs.

[0073] The cost of credit risk is the expected loss incurred when holding accounts receivable for a certain period of time. The following mathematical formula represents the cost of credit risk.

[0074]

[0075] (d represents the cost of credit risk, e represents the balance of accounts receivable, f represents the probability of default, and g represents the probability of loss in case of default.)

[0076] For example, if the balance of accounts receivable is 1 million won, the probability of default of the accounts receivable issuer is 5%, and the probability of loss in case of default is 30%, the credit risk cost can be calculated as 1 million won x 5% x 30% = 15,000 won.

[0077] The probability of default (PD) represents the likelihood of default on a trade receivable. The PD can be calculated using either an internal rating method, which aggregates the credit rating of the trade receivable issuer and uses the financial institution's internal data, or an external rating method, which uses external data from a credit information provider.

[0078] The probability of default (PD) represents the probability of default of the issuer (debtor) of accounts receivable, the entity that received the goods and services. This probability can be expressed using financial data such as the issuer's credit rating and total assets. For example, if the issuer has an "A" credit rating and total assets of KRW 1 billion to KRW 10 billion, the probability of default can be calculated as 5%.

[0079] The probability of default can be calculated by multiplying the default probability of a receivable issuer by "1 + an adjustment factor." The adjustment factor can be derived from unstructured data indicating the creditworthiness of the receivable issuer. The unstructured data can include one or more of the following: the purpose, size, industry, and business conditions of the receivable issuer's purchase transactions, and the three-year sales growth rate. The purpose and size of the purchase transactions can be weighted toward the sales volume of the receivable issuer, the industry and business conditions of the receivable issuer can be weighted toward the business conditions, and the three-year sales growth rate can be weighted toward sales growth. Furthermore, the adjustment factor can be the sum of the items included in the unstructured data (the sales volume, business conditions, and sales growth of the receivable issuer).

[0080] Loss Given Default (LGD) represents the economic loss a creditor may incur from the balance of a receivable if the issuer or account defaults. The loss given default rate, excluding the amount recoverable through demand and legal proceedings, can be expressed as the LGD.

[0081] The probability of loss upon default can be expressed differently based on the credit rating of the account receivable issuer. Alternatively, the probability of loss upon default can be determined differently depending on the characteristics of the bond. For example, the probability of loss upon default can be determined based on the type of bond, such as retail bonds, corporate loans, or housing bonds. In the second embodiment, the probability of loss upon default is determined based on the credit rating of the account receivable issuer. If this information is unavailable, the probability of loss upon default can be determined using information on similar products provided by institutions such as banks.

[0082] Information such as the probability of default, the probability of loss in case of default, and the credit rating of the issuer of accounts receivable can be collected from a third-party system (T) and stored in the database of the cost calculation unit (213).

[0083] Credit risk expense is the amount of loss that occurs beyond the expected loss amount. The required cost calculation unit (213) can calculate the credit risk expense by multiplying the issuance price of accounts receivable by the required equity ratio and the internal rate of return on equity.

[0084] In terms of credit risk cost, the correlation coefficient of the SME default index to the overall corporate default index may be a positive function.

[0085] The accounts receivable valuation unit (214) can evaluate the value of accounts receivable by reflecting the required cost. The accounts receivable valuation unit (214) can calculate the positive amount of accounts receivable according to the following mathematical formula.

[0086]

[0087] (l represents the positive amount of accounts receivable, m represents the balance of accounts receivable, and n represents the cost of goods sold.)

[0088] The required cost may be the sum of the procurement cost and the credit risk cost. Alternatively, the required cost may be the sum of the procurement cost and the credit risk cost, plus the operating margin and transaction costs. The operating margin may be entered by the system user or calculated by entering a fixed margin rate, or it may be a fee.

[0089] For example, if the balance of accounts receivable is 1 million won, the cost of procurement is 20,000 won, and the credit risk expense is 15,000 won, excluding operating margins, the cost of acquisition would be 35,000 won, resulting in a total acquisition price of 965,000 won. Accordingly, the assignee of the accounts receivable would pay 965,000 won to the assignor and receive the accounts receivable.

[0090] FIG. 4 is a diagram illustrating the configuration of a server computer according to a third embodiment of the present invention. FIG. 5 is a diagram illustrating a process for classifying user groups according to a third embodiment of the present invention.

[0091] The configuration and operation method of the sales receivable platform service system according to the third embodiment of the present invention may be the same as the corresponding configuration and operation method of the first embodiment, except for what is additionally described.

[0092] In the third embodiment, a receivables platform service can recommend receivables for purchase to users. In other words, receivables can be recommended for purchase to potential assignees.

[0093] The server computer (310) may include a data acquisition unit (3101), a user classification unit (3102), a transaction history classification unit (3103), a user group classification unit (3104), a user group creation unit (3105), a purchase history creation unit by user group (3106), a purchase history classification unit (3107), a similarity calculation unit (3108), a similar user selection unit (3109), and a bond recommendation unit (3110).

[0094] The data acquisition unit (3101) can collect customer information and bond type information from a third-party system (T).

[0095] The user information database (31011) can store user information. For example, it can store information on individuals, sole proprietors, and corporations, addresses, total transaction amounts, total number of transactions, and purchasing tendencies (risk-buying, risk-neutral, stability-seeking, safe, etc.).

[0096] The bond information database (31012) can store information about bond types. For example, it can store information about the credit rating of the issuer of a trade receivable, the industry, the bond amount, and the number of days prior to the bond's maturity date.

[0097] The user classification unit (3102) can classify users based on user and bond type information collected by the data acquisition unit (3101).

[0098] Existing registered users can be categorized based on their transaction information. For example, users can be categorized as risk-seeking, who seek to maximize investment returns while actively accepting the associated risk of loss and willing to invest in risky bonds; risk-neutral, who are fully aware of the risks and willing to accept a certain level of risk if they can expect higher returns than deposits and savings; stability-seeking, who seek to minimize the risk of loss on purchased principal and aim for slightly higher returns than deposits and savings; and stable, who expect returns similar to those of deposits and savings but seek to avoid losses on purchased principal.

[0099] Newly registered users can be classified using the individual, sole proprietor, or corporate classification values, address, and purchasing tendency questionnaire, as they have no bond purchase history.

[0100] The transaction history classification unit (3103) can classify a user's bond transaction history by scoring it. The scoring variable setting unit (31031) can collect information on the user's bond transaction history. Bond transaction history information can include the issuer's industry, credit rating, amount, maturity date, etc. of bonds purchased by the user in the past.

[0101] The scoring unit (31032) can calculate the transaction recency indicating when a transaction was made during a given period, the transaction frequency indicating the transaction quantity during a given period, and the transaction size indicating the total amount used for purchase during a given period from the user's bond transaction history information, and can calculate the bond transaction history score.

[0102] The user group classification unit (3104) can classify user groups using the following mathematical formula from the bond transaction history score.

[0103]

[0104] (V is the variance, xj is the bond history score of each buyer, μi is the bond history score of the central buyer in each group, Si is the group, i is the number of the buyer group, and j is a variable that identifies the buyer belonging to the group.)

[0105] The user group classification unit (3104) can search for a set of buyer groups that minimizes the variance value, then classify buyers and create buyer groups using the classified buyer information.

[0106] More specifically, as shown in FIG. 5, it may include a step (S3010) of randomly classifying users classified in the transaction history classification unit (3103) into K groups, a step (S3020) of randomly selecting one central user from each group, a step (S3030) of classifying users in order of the user with the closest distance to the central user's score, a step (S3040) of calculating the average score in the group and reselecting the central user, and a step (S3050) of repeating until the central user does not change.

[0107] The user group creation unit (3105) can determine and group similar users within a certain range by using the bonds traded by the user and the bond transaction history score.

[0108] The similar user determination unit (31051) determines similar users based on the user's bond transaction information and bond transaction history score. The bond transaction information can be obtained from user information data, and the bond transaction history score may be calculated by the transaction history classification unit (300).

[0109] For example, users who traded bonds in related industries, such as manufacturing-related bonds or hospital-related bonds, can be considered users who traded similar bonds. Furthermore, users with bond trading history scores that do not differ significantly (e.g., (3,4,3) and (3,4,4)) can be considered users with similar bond trading history scores. The similarity range is not restricted and can be freely adjusted to better suit bond recommendations.

[0110] The user grouping unit (31052) can group similar users within a certain range among the similar users determined by the similar user determination unit (31051). For example, a user-based collaborative filtering (user-based CF) method can be used.

[0111] User-based collaborative filtering (CF) is a user-based collaborative filtering technique that identifies similar user groups (neighborhoods) and recommends bonds that share common interests among those users. Collaborative filtering (CF) leverages user preference information and assumes that past trends (patterns) will persist in the future. For example, users who favored a particular bond in the past are likely to favor it in the future.

[0112] User-based collaborative filtering (User-based CF) is a type of active filtering that analyzes user interests and selects users with similar preferences using the trading history of classified bonds, which are scored. This method predicts user behavior by scoring user behavior. Similar scores are assumed to indicate similar interest in a given stock. Therefore, since similar users, as determined by the similar user determination unit (510), have similar bond trading scores, their preferences are similar and their predicted behaviors are also similar, users can be grouped by users with similar bond trading scores.

[0113] User-based collaborative filtering (user-based CF) is a method of recommending bonds based on the actual evaluations of bonds by users interested in the bond, so it can generate reliable explanations and rankings from reliable information.

[0114] The user information collection unit (31061) of the purchase input generation unit (3106) by user group can collect information on bonds purchased by grouped users, the number of bonds purchased, the average purchase price, and the number of bonds held in transactions.

[0115] The purchase history generation unit (31062) can generate a purchase history for each user group from the collected information.

[0116] The purchase history classification unit (3107) can score users' purchase history.

[0117] The scoring variable setting unit (31071) can collect information such as industry code, bond purchase quantity, total purchase amount, bond amount, and maturity date. Information on purchased bonds can be obtained through the industry code.

[0118] The purchase history scoring unit (31072) can score purchase history using purchase recency, purchase frequency, and purchase size. This can be based on transactions over a given period. Recency indicates which bond type was purchased and when during the given period. Purchase frequency indicates the number of bonds purchased during the given period. Purchase size indicates the total amount spent on bond purchases during the given period. Users' bond purchase history can be classified into scores such as (3, 1, 1), (2, 3, 4), etc.

[0119] The similarity calculation unit (3108) can calculate the similarity between users from the users' bond scores.

[0120] The purchase history collection unit (31081) can collect information on bonds commonly purchased by users. This may be data generated by the purchase history classification unit (700).

[0121] The evaluation value input section (31082) can calculate the similarity between users by inputting the scores of bonds commonly purchased by users into the following mathematical formula.

[0122]

[0123] We use the NeuMF model, which combines the outputs of the generalized matrix factorization (GMF) function and the multi-layer perceptron (MLP) function. The embedding vectors generated through one-hot encoding can be latent vectors for users and items. (pu is the user latent vector, qi is the item latent vector, the GMF function uses a sigmoid activation function, and the MLP function uses a ReLU function. hT can be the log loss function as the loss function. zL is the output of the Lth hidden layer, zL-1 is the output of the previous layer, WL is the weight matrix of the Lth hidden layer, bL is the bias vector of the Lth hidden layer, and yui represents the output.)

[0124] The similar user selection unit (3109) can select similar users using similarity.

[0125] The number of users determination unit (31091) can determine in advance the number of users to be selected.

[0126] The user selection unit (31092) can select users in the order in which the similarity calculation result value is closer to 1, corresponding to the determined number of users. For example, users can be selected in the order in which the cosine similarity value is closer to 1.

[0127] The bond recommendation unit (3110) can recommend bonds to purchase to selected users.

[0128] Some selected users have purchased bonds, while others have not. For example, among users A, B, and C selected as similar users, if A and B purchased bonds related to manufacturing, construction, and hospitals, and C purchased bonds related to manufacturing and construction, hospital-related bonds could be recommended to C.

[0129] The bond recommendation unit (3110) analyzes user preferences and recommends bonds commonly purchased by users with similar preferences to users in a group that did not purchase those bonds. In this case, the user group classification unit (3104) can be omitted, and bonds can be recommended by classifying users.

[0130] And, in order to reduce the complexity of calculation and quickly recommend bonds, the process of classifying users by operating up to the user group creation unit (3105), generating purchase history by user group, calculating similarity, and selecting similar users can be omitted, and bonds can be recommended.

[0131] FIG. 6 is a diagram showing a computing device included in each configuration in one embodiment of the present invention.

[0132] A computing device (10) including a server computer (110), a first terminal device (120), and a second terminal device (130) includes a processor (11), a memory device (12), an input / output device (13), a display device (14), and a system board (15).

[0133] The processor (11) executes an operation of reading and changing data input into the interior of a computing device or generating data output to the outside. In addition, the processor (11) interprets and processes computer-readable instructions that execute a method according to an embodiment of the present invention. The processor (11) may be a microprocessor including a control device that interprets instructions and generates a control signal for execution, an arithmetic and logic operation device that executes arithmetic and logic operation instructions, a register that stores a plurality of instructions and the location of the next instruction to be executed, input or output data, a cache memory that temporarily stores data exchanged between the processor (11) and a memory device (12), and a system bus that is a passage through which data moves within the processor (11).

[0134] The memory device (12) stores data processed or input / output within the computing device. In addition, the memory device (12) stores computer-readable instructions for executing a method according to an embodiment of the present invention. The memory device (12) may include a main memory device and an auxiliary memory device. The main memory device may include a random access memory device or a flash memory device. The auxiliary memory device may include one or more of a hard disk drive, a solid state drive (SSD), an optical disc drive, and a magnetic tape.

[0135] The input / output device (13) inputs data into the computing device and outputs data to the outside. In addition, the input / output device (13) inputs a computer-readable command that executes a method according to an embodiment of the present invention. The input / output device may include an external input / output terminal and a driver device that processes the external input / output terminal. For example, the external input / output terminal may include one or more of a serial port, a parallel port, a small computer system interface (SCSI), a universal serial bus (USB), IEEE 1394, an external serial advanced technology attachment (e-SATA), and Thunderbolt. In addition, the input / output device may include a network interface controller, and the network interface controller may be connected to a local area network (LAN) based on Ethernet in a wired manner, or to a wireless local area network (WLAN) based on Wi-Fi in a wireless manner.

[0136] The display device (14) can display data processed by the processor (11) or stored in the memory device (12). The display device (14) can be a display device or a printing device.

[0137] The system board (15) connects between the processor (11), the memory device (12), the input / output device (13), and the display device (14), and provides a path for data processed in the computing device. The system board (15) may include an address bus, a command bus, a data bus, a chipset device that controls the bus, and a power system.

[0138]

[0139] While the embodiments of the present invention have been described above, the present invention is not limited to the above embodiments, and various modifications may be made within the scope of the detailed description and the attached drawings, as long as the spirit of the present invention is not deviated from or the effects are not impaired. Furthermore, it is obvious that such embodiments fall within the scope of the present invention.

Claims

1. A step in which the first terminal device transmits the information on the sales receivable entered by the transferor to the server computer, and the server computer registers the information on the received sales receivable; A step in which the first terminal device transmits the identification information of the sales receivable for which the transferor has applied for transfer to the server computer, and the server computer updates the status of the sales receivable corresponding to the identification information of the sales receivable received to a transfer application status; and A step in which the second terminal device transmits the identification information of the sales receivable approved by the transferee to the server computer, and the server computer updates the status of the sales receivable corresponding to the identification information of the sales receivable received to the transfer approval status; Sales receivable platform service method.

2. In claim 1, The information of the sales receivable entered by the transferor in the first terminal device is at least one of the creditor's business registration number, business name, representative name, sales receivable contract name, contract amount, and contract conclusion date. Sales receivable platform service method.

3. In claim 1, The transferor inputs the transfer price, transfer period, and transfer conditions of the sales receivable in the first terminal device, and the first terminal device transmits the input information along with the identification information of the sales receivable to the server computer. Sales receivable platform service method.

4. A first terminal device that receives an order to register sales receivables from the transferor, to search for information on registered sales receivables, and to apply for transfer of sales receivables; A second terminal device for receiving information on registered sales receivables from the assignee and an order to approve the transfer of sales receivables; and A server computer that receives a request message from the first terminal device and the second terminal device, processes a task in response to the request message, and then processes the processing result into a response message and transmits it; Sales receivable platform service system.

5. In claim 4, The above server computer, Credit information evaluation department that obtains, reviews, and evaluates credit information of parties to sales receivable transactions; A quantitative factor calculation unit that calculates non-financial factors of the parties to a sales receivable transaction into quantitative factors; A cost calculation unit that calculates credit risk costs from the transaction costs and holding periods of accounts receivable; and Includes an accounts receivable valuation department that evaluates the value of accounts receivable by reflecting the cost of sales; Sales receivable platform service system.

6. In claim 5, The above credit information evaluation department obtains credit information from one or more of the following items: credit rating in the company's credit evaluation information, fair book value of total assets, absolute quantitative figures of total sales based on National Tax Service data, operating profit margin, operating profit margin of total assets, current ratio, interest coverage ratio, ROE (return on equity), and processed quantitative figures of debt dependence. Sales receivable platform service system.

7. In claim 5, The above quantitative factor calculation section conducts a first evaluation by specifying the transaction purpose, transaction request size, transaction request industry and business conditions, past transaction history, major shareholders and equity relationships, and whether the company is a company, and then conducts a second evaluation by selecting the transaction relationship, construction capability evaluation amount by industry, and medical foundation grade. Sales receivable platform service system.

8. In claim 5, The above cost calculation section calculates the credit risk cost by multiplying the balance of accounts receivable by the probability of default and the probability of loss in the event of default, and calculates the cost by adding the procurement cost and the credit risk cost. Sales receivable platform service system.

9. In claim 5, The above sales receivables evaluation department determines the amount of sales receivables by deducting the cost of sales from the balance of sales receivables. Sales receivable platform service system.

10. In claim 5, When the transferee pays the transfer amount, the server computer transfers the sales receivable to the transferee and pays the transfer amount to the transferor. Sales receivable platform service system.

Images