JP2020009368A - Information processing device, program, and information processing system - Google Patents

Abstract

To charge a fee to an ordering company for an electronically recorded credit when transferring the electrically recorded credit.SOLUTION: An information processing device according to the present invention includes a storage device and a processor. The processor accesses the storage device, and controls occurrence and transfer of an electronically recorded credit. The storage device stores billing data. The billing data associates identification data on electronically recorded credit data, a creditor of the electronically recorded credit, and a billing amount. When the processor receives transfer approval related to the electronically recorded credit data from a device of a financial institution, it updates the billing amount associated with the identification data for the billing data.SELECTED DRAWING: Figure 2

Description

  The present invention relates to an information processing apparatus, a program, and an information processing system that handle electronically recorded bond data.

  In recent years, the Electronically Recorded Receivables Act has been enacted for the purpose of facilitating the financing of small and medium-sized enterprises, and the need for utilizing electronically recorded receivables has increased. Electronically recorded receivables are monetary receivables for the purpose of electronically recording and managing receivables generated in commercial transactions and the like. Since the electronically recorded receivables are managed electronically, the transfer procedure is simpler than conventional designated receivables such as receivables. When electronically recorded receivables are transferred, the contents of the transaction are recorded electronically, eliminating the risk of reassignment of receivables and the risk of the creditor becoming unclear due to repeated transfers. .

  The use of electronically recorded receivables will reduce the cost of drafting, issuing and storing bills, and reduce the risk of loss, theft, forgery, etc., compared to bills receivable that previously used paper media. Can be. That is, the electronically recorded receivable has an advantage that it can promote payment at face value more than the bill receivable.

Japanese Patent No. 6140909

  If the delivery company that is the order recipient needs a large amount of funds in the production process, the delivery company may receive a loan at the time of ordering from a financial institution or the like. The loan at the time of ordering is a mechanism for financing a subcontractor (delivery company) that receives an order from an ordering company. However, small and medium-sized enterprises, enterprises with insufficient financial resources, and enterprises without security such as real estate may not be able to receive loans. In addition, it is difficult to obtain consent from the ordering company, which is the debtor, for the transfer of the receivables before delivery and acceptance. Therefore, there is an increasing need to generate highly reliable electronically recorded receivables from the ordering stage and receive loans from financial institutions or the like using the electronically recorded receivables as collateral for transfer.

  In addition, under the Subcontract Payment Payment Delay Act (hereinafter referred to as the Subcontract Act), an ordering company must prepare an order document and place an order with a subcontractor (delivery company), and there will be a change from the contents of the order. If so, a supplementary document must be prepared. The purchase order and supplementary documents are required to be kept for at least two years. However, it takes time, effort, and cost to prepare and store the order form and the supplementary form.

  The present invention has been made in view of the above circumstances, and provides an information processing apparatus, a program, and an information processing system for managing generation and transfer of electronically recorded bonds.

  An information processing device according to the present invention includes a storage device and a processor. The processor accesses the storage device and controls generation and transfer of electronically recorded bond data relating to the electronically recorded bond. The processor receives, from the first terminal, creditor data, debtor data, loan amount data, and due date data relating to the electronically recorded receivable, and accepts the generation of the electronically recorded receivable from the second terminal. Receipt of the consent to the customer, and when the consent to the receipt is received, the electronically recorded receivable data including the identification data relating to the electronically recorded receivables, the creditor data, the debtor data, the receivable amount data, and the due date data And transmits the generated electronically recorded receivables data and the request for generation to a device of the electronic receivables recording organization or a proxy device provided in front of the device of the electronic receivables recording institution, and from the creditor's terminal, The identification data and the transfer destination data indicating the electronically recorded receivables data to be transferred are received, the transfer consent indicating that the transfer is approved is received from the financial institution device, and the transfer consent is received. In this case, the identification data, the transfer destination data, and the transfer request for requesting the transfer of the electronically recorded loan data stored in the database of the device of the electronic credit recording agency are transmitted to the device or the proxy device of the electronic credit recording agency. To the storage device that stores the billing data that associates the identification data with the creditor and the billing amount for the creditor with respect to the electronically recorded receivable when receiving the transfer consent, and is associated with the identification data. Update billing amount.

  ADVANTAGE OF THE INVENTION According to this invention, generation | occurrence | production and transfer of an electronically recorded claim can be managed appropriately.

FIG. 1 is a block diagram showing an example of the configuration of an electronically recorded bond system including the electronically recorded bond management device according to the first embodiment. FIG. 2 is a block diagram illustrating an example of a schematic configuration of the electronically recorded receivables management device according to the first embodiment. FIG. 3 shows the electronically recorded receivables-with-defense data to be split and transferred, the electronically recorded receivables-with-defense data after the split transfer, and the electronically-defendable claims transferred after the split transfer. It is a data structure figure which shows the example with recorded bond data. FIG. 4 is a block diagram illustrating an example of the electronically recorded receivables management device according to the second embodiment. FIG. 5 is a data structure diagram showing an example of electronically recorded bond data according to the second embodiment. FIG. 6 is a block diagram illustrating an example of the electronically recorded receivables management system according to the second embodiment. FIG. 7 is a diagram illustrating an example of a guarantee period for an electronically recorded claim according to the second embodiment and a financing period with the electronically recorded claim as collateral. FIG. 8 is a flowchart showing an example of an ordering flow and a process of generating electronically recorded claim data with a defense. FIG. 9 is a flowchart showing an example of a collateral setting flow, a loan execution flow, and a transfer process of electronically recorded receivables data with defense. FIG. 10 is a flowchart illustrating an example of a delivery flow and a process of changing electronically recorded bond data. FIG. 11 is a flowchart showing an example of a loan repayment flow and a process for completing payment of electronically recorded receivable data. FIG. 12 is a flowchart illustrating an example of the division transfer process of the electronically recorded claim data with defense according to the second embodiment. FIG. 13 is a block diagram illustrating an example of a configuration of an electronically recorded receivables management device according to the third embodiment. FIG. 14 is a data structure diagram showing an example of the loan frame data. FIG. 15 is a flowchart illustrating an example of a process of generating electronically recorded claim data with defense, which is executed by the electronically recorded claim management device according to the third embodiment. FIG. 16 is a flowchart illustrating an example of transfer and billing processing of electronically recorded claim data with defense, which is executed by the electronically recorded claim management device according to the third embodiment. FIG. 17 is a screen diagram showing a display example of transaction menu screen data. FIG. 18 is a screen diagram showing a display example of screen data for accepting selection of whether to operate as an ordering company or to operate as an ordering company. FIG. 19 is a diagram illustrating an example of a menu table displayed when an operation is received from a terminal of an order receiving company. FIG. 20 is a diagram illustrating an example of a menu table displayed when an operation is received from a terminal of an ordering company. FIG. 21 is a screen diagram showing a display example of screen data for allowing a financial institution to approve the transfer.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. In this description, common parts are denoted by common reference numerals throughout the drawings.

(1st Embodiment)
In the present embodiment, an outline of the electronically recorded bond management device 1 and the electronically recorded bond management system 10 will be described.

  FIG. 1 is a block diagram showing an example of a configuration of an electronically recorded debt management system 10 including an electronically recorded debt management device 1 according to the present embodiment.

  FIG. 2 is a block diagram illustrating an example of a schematic configuration of the electronically recorded receivables management device 1.

  FIG. 3 is an electronically recorded claim data C with a defense to be divided and transferred, which is stored in the device 106 of the electronic credit recording agency, and the electronically recorded claim data with a defense after the division and transfer of the electronically recorded claim data C with a defense. It is a data structure figure showing an example of CA_A and transferred electronically recorded claim data C_B with defense.

  The electronically recorded bond management system 10 is, for example, an information processing system. The electronically recorded bond management system 10 includes, for example, at least the electronically recorded bond management device 1 and a device 106 of an electronically recorded bond institution. In the present embodiment, the electronically recorded receivables management system 10 includes, for example, a terminal 100 of an ordering company (obligor), a terminal 104 of a delivery company (creditor), an electronic contract system 102, a device 108 of a financial institution, a credit guarantee association ( The device 110 and the proxy device 111 may be further included. In addition, a delivery company may be described as an order receiving company.

  In the present embodiment, the electronically recorded receivables management device 1, the terminal 100 of the ordering company, the terminal 104 of the delivery company, the electronic contract system 102, the device 108 of the financial institution, the device 110 of the guarantee association, the proxy device 111, and the The device 106 is, for example, an information processing device or an information processing system, and more specifically, may be, for example, a server device, a client device, a personal computer, a mobile terminal, or the like.

  The electronic record receivables management device 1 communicates with the terminal 100 of the ordering company, the terminal 104 of the delivery company, the electronic contract system 102, the device 108 of the financial institution, the device 110 of the guarantee association, the proxy device 111, and the device 106 of the electronic receivables record institution. Connected as possible.

  The electronic contract system 102 is communicably connected to the terminal 100 of the ordering company and the terminal 104 of the delivery company.

  The proxy device 111 is communicably connected to the electronically recorded bond management device 1 and the device 106 of the electronically recorded bond agency. The proxy device 111 cooperates with, for example, the electronically recorded receivables management device 1.

  In the present embodiment, data, information, request, consent, command, command, instruction, notification, response, signal, and the like can be transmitted and received between the devices that are communicably connected.

  The electronically recorded receivables management device 1 includes a processor 5 and a storage device 7.

  The processor 5 executes the program P stored in the storage device 7 to execute the first receiving unit 114, the second receiving unit 115, the extracting unit 54, the generation requesting unit 117, the third receiving unit 118, It functions as a fourth receiving unit 119, a division transfer request unit 120, a defense disconnection request unit 121, and a defense disconnection notification unit 122. The electronically recorded receivables management device 1 includes a plurality of processors, and the plurality of processors may cooperate and cooperate to realize the same function as the processor 5.

  The storage device 7 stores a plurality of template data 123_1 to 123_n and condition data E in addition to the program P. Further, the storage device 7 may store various data used in the processing in the processor 5 and various data received by the electronically recorded receivables management device 1 from other devices. The storage device 7 may be composed of a plurality of storage devices.

  The template data 123_1 to 123_n are used to generate defense content data D6 described later. Each of the template data 123_1 to 123_n includes, for example, document data that is a candidate for various types of defense contents.

  The condition data E includes, for example, creditor data D2, debtor data D3, credit amount data D4, which will be described later, based on order content data received from the terminal 104 of the supplier, the terminal 100 of the orderer, or the electronic contract system 102. Includes conditions used to extract payment date data D5 and defense content data D6. The condition data E may include, for example, a criterion for determining whether the data corresponds to an order document or a supplement document specified in Articles 3 and 5 of the Subcontract Act. Articles 3 and 5 of the Subcontract Act stipulate that order documents and supplementary documents should be retained for at least two years.

  In the present embodiment, the order content data includes, for example, first, the names, numbers, and symbols of the parent and subcontractors, and secondly, the production consignment, repair consignment, information product creation consignment, or service provision consignment. Third, the contents of the subcontractor's benefits, fourth, the date on which the subcontractor's benefits are received (in the case of outsourcing, the date or period for which the service is provided), and fifth, the subcontractor. Where to receive the benefits of the business, sixth, if you want to inspect the contents of the subcontractor's benefits, the date to complete the inspection, seventh, the amount of the subcontract price, eighth, payment of the subcontract price Due date, ninth, when issuing bills, the amount of bills and the maturity of the bills, and tenth, when paying in a lump sum settlement method, the name of the financial institution, lending or payable amount, and the parent company is subcontracted. The date when the amount equivalent to the receivables or the amount equivalent to the subcontractor's debt is paid to the financial institution In the case of payment by electronically recorded receivables, the amount of the electronically recorded receivables and the expiration date of the electronically recorded receivables; and twelfth, in the case of payment of raw materials, etc., the name, quantity, consideration, delivery date, settlement date and settlement Including information on how, etc.

  The ordering company terminal 100 is a terminal operated by a user (operator) of the ordering company.

  The terminal 104 of the delivery company is a terminal operated by the user of the delivery company.

  An ordering contract is concluded between the ordering company and the delivery company. The contract may be made electronically by using the electronic contract system 102 between the terminal 100 of the ordering company and the terminal 104 of the delivery company, or may be made offline.

  When a contract is concluded electronically using the electronic contract system 102, the first receiving unit 114 of the electronically recorded receivables management device 1 is generated from the electronic contract system 102 according to an order before delivery or acceptance. The creditor data D2, the debtor data D3, the loan amount data D4, the due date data D5, and the defense content data D6 relating to the electronically recorded receivables with defence are received.

  Note that the first receiving unit 114 can receive the creditor data D2, the debtor data D3, the credit amount data D4, the payment data from the terminal 104 of the delivery company or the terminal 100 of the ordering company without using the electronic contract system 102. The date data D5 and the defense content data D6 may be received.

  The first receiving unit 114 may receive the above-described order content data from the terminal 104 of the delivery company, the terminal 100 of the ordering company, or the electronic contract system 102.

  In the following, a description will be given mainly of the case where the supplier requests the generation of electronically recorded receivables with a defense, and the ordering company accepts the generation. A request may be made, and the delivery company may acknowledge the occurrence.

  In the present embodiment, the first receiving unit 114 reads the plurality of template data 123_1 to 123_n from the storage device 7 and supports the plurality of template data 123_1 to 123_n to support the generation of the defense content data D6. The information may be transmitted to the terminal 104 or the electronic contract system 102, or a process for displaying the plurality of template data 123_1 to 123_n and the input fields of the defense contents on the terminal 104 or the electronic contract system 102 of the delivery company may be executed. . In this case, the terminal 104 of the delivery company or the electronic contract system 102 selects the template data selected from the template data 123_1 to 123_n by the user of the delivery company, or the data input to the input field on the terminal 104 of the delivery company. Is the defense content data D6, and the defense content data D6 is transmitted to the first receiving unit 114. The first receiving unit 114 receives the defense content data D6 from the terminal 104 of the delivery company or the electronic contract system 102.

  When an electronic contract is concluded using the electronic contract system 102, the second receiving unit 115 of the electronically recorded receivables management device 1 transmits the creditor data D2, the debtor data D3, and the loan amount data D4 from the electronic contract system 102. , Receiving the generation approval 130 indicating that the generation of a defense-attached electronically recorded claim based on the payment date data D5 and the defense content data D6 is approved.

  Note that the second receiving unit 115 may receive the generation approval 130 from, for example, the terminal 100 of the ordering company without using the electronic contract system 102.

  The extracting unit 54 is configured such that the first receiving unit 114 sends the order content data (for example, the creditor data D2, the debtor data D3, and the credit amount data in FIG. 2) from the terminal 104 of the delivery company or the electronic contract system 102, for example. D4, payment due date data D5, and defense content data D6), the order content data is stored in the storage device 7.

  Further, when the second receiving unit 115 receives the consent corresponding to the partial data included in the order content data from the terminal 104 or the electronic contract system 102 of the delivery company, the extraction unit 54 is accepted from the order content data. The extracted partial data is stored in the storage device 7 as data necessary for complying with Articles 3 and 5 of the Subcontract Act.

  Further, the extraction unit 54 reads the condition data E from the storage device 7 and, based on the condition data E, from the order content data, the creditor data D2, the debtor data D3, the bond amount data D4, The payment date data D5 and the defense content data D6 are extracted, and the extracted creditor data D2, debtor data D3, amount of credit data D4, payment date data D5, and defense content data D6 satisfy the condition to comply with the Subcontract Act. It is determined whether or not.

  The extraction unit 54 may permit the operation by the occurrence requesting unit 117 when determining that the subcontracting law is complied with. When the extraction unit 54 determines that the subcontractor law is not complied with, the extraction unit 54 transmits a notification indicating this to at least one of the terminal 100 of the ordering company, the terminal 104 of the delivery company, and the electronic contract system 102. You may.

  In the present embodiment, the extraction unit 54 stores various data in the storage device 7. However, various data such as partial data extracted from order content data in order to comply with the Subcontract Act are stored in an electronic credit recording organization. May be stored in another device such as the device 106 of FIG.

  When the second receiving unit 115 receives the generation consent 130, the generation request unit 117, for example, identifies the identification data D1, the creditor data D2, the debtor data D3, and the debt amount data on the electronically recorded debt with defense. A generation request 131 for generating the defense-attached electronically recorded claim data C including D4, due date data D5, and defense content data D6, and requesting the generation of the generated defense-attached electronically recorded claim data C, and a defense-attached electronically recorded claim The data C is transmitted to the device 106 of the electronic bond recording organization or the proxy device 111. The generation requesting unit 117 may store the generated electronically recorded claim data C with defense in the storage device 7. Further, the generation requesting unit 117 may store the generated electronically recorded receivables-with-defense data C in the storage device 7 when receiving the notification of the completion of the generation from the device 106 of the electronic bond recording organization.

  The proxy device 111 is a device provided before the device 106 of the electronic bond recording institution, and is, for example, a bridge system that relays between the electronic bond management device 1 and the device 106 of the electronic bond recording institution 106. The proxy device 111 transmits a request to the device 106 of the electronic bond recording organization in response to various requests received from the electronically recorded bond management device 1. For example, the proxy device 111 transmits the electronically recorded claim data C with defense received from the electronically recorded claim management device 1 to the device 106 of the electronically receivable recording organization. When receiving various notifications from the device 106 of the electronic credit recording organization, the proxy device 111 transmits the notifications to the electronic credit management device 1. In the present embodiment, the proxy device 111 may be integrated with the electronically recorded receivables management device 1.

  Based on the request received from the electronically recorded receivables management device 1 or the proxy device 111, the device 106 of the electronically receivable recording organization generates, reads out, transfers, changes (defenses off), transfers, splits, Perform extinction, etc. The device 106 of the electronic bond recording organization is, for example, a database management system. The device 106 of the electronic bond recording organization can access the database 106A. The device 106 of the electronic bond recording organization includes, for example, a processor 106B and a storage device 106C, and the processor 106B may operate by executing a program stored in the storage device 106C.

  The financial institution device 108 and the guarantee institution device 110 transmit various requests to the electronically recorded receivables management device 1 in accordance with the operations of the financial institution user and the guarantee institution user. In addition, the financial institution device 108 and the guarantee association device 110 are recorded in the electronic credit recording institution device 106 via the electronically recorded receivables management device 1 or via the electronically recorded receivables management device 1 and the proxy device 111. You can read and view the existing electronic bond record data.

  The third receiving unit 118 receives, from the terminal 104 of the delivery company, designation data (identification data) 132 for designating the defense-recorded electronically recorded receivables data C to be a target (base) of the split transfer, transfer destination data D7, and transfer amount data D8. The third receiving unit 118 may store the received designation data 132, transfer destination data D7, and transfer amount data D8 in the storage device 7. In addition, the third receiving unit 118 receives, for example, a terminal 100 of the ordering company, a device 108 of the financial institution, a device 110 of the guarantee association, or another device that is not the terminal 104 of the delivery company, such as the electronic contract system 102. The designated data 132, the transfer destination data D7, and the transfer amount data D8 may be received.

  The fourth receiving unit 119 receives, from the device 108 of the financial institution, a split assignment approval 135 indicating that the split assignment is approved. In addition, the fourth receiving unit 119 may receive, for example, a terminal 100 of the ordering company, a terminal 104 of the delivering company, a device 110 of the guarantee association, or another device that is not the device 108 of the financial institution, such as the electronic contract system 102. The split assignment consent 135 may be received.

  When the fourth receiving unit 119 receives the split transfer agreement 135, the split transfer request unit 120 converts the split transfer request 136, the designation data 132, the transfer destination data D7, and the transfer amount data D8 into an electronic receivable. The information is transmitted to the recording institution device 106 or the proxy device 111. Here, the split transfer consent 135 is obtained by, for example, subtracting the value of the transfer amount data D8 from the value of the loan amount data D4 included in the electronically recorded claim data C with the defense indicated by the designated data 132 to obtain the electronically recorded claim data with the defense. It may be an instruction requesting to change C to the electronically recorded claim data C_A with defense and to generate the electronically recorded claim data C_B transferred by the division transfer.

As a result, as shown in FIG. 3, the device 106 of the electronic bond recording organization changes the defense-recorded electronically recorded bond data C in the database 106A to the split-sourced defense-recorded electronically recorded bond data C_A by split transfer and is transferred. The electronically recorded claim data C_B with defense is newly generated, and the electronically recorded claim data with defense C_B is additionally stored in the database 106A.
More specifically, for example, when the device 106 of the electronic bond recording organization receives the split transfer request 136, the designation data 132, the transfer destination data D7, and the transfer amount data D8, the electronic bond recording organization The value of the transfer amount data D8 is subtracted from the value of the bond amount data D4 based on the defense-recorded electronically recorded bond data C, the transferee data D7, and the transfer amount data D8, which are stored in the database 106A and indicated by the designated data 132. The electronically recorded claim data C_A including the claim amount data D4_A indicating the calculated value is generated. In addition, the device 106 of the electronic credit recording organization has a defense including the transferred identification data D1_B, the transferred creditor data D2_B corresponding to the transferee data D7, and the transferred loan amount data D4_B corresponding to the transferred amount data D8. The electronically recorded claim data C_B is generated. The device 106 of the electronic bond recording organization stores the generated electronically recorded bond data C_A and C_B with defense in the database 106A. Then, the device 106 of the electronic bond recording institution records the split transfer completion notification, which is a response to the split transfer request, and the identification data D1_B after transfer newly generated by the device 106 of the electronic bond recording institution, To the device 106 or the proxy device 111.
In the present embodiment, when the split transfer request unit 120 of the electronically recorded receivables management device 1 receives the split transfer completion notification and the identification data D1_B after the transfer from the device 106 or the proxy device 111 of the electronically receivable recording organization, the transfer is performed. The subsequent identification data D1_B may be stored in the storage device 7. Further, the split transfer request unit 120 stores the defense-attached electronically recorded claim data C, the designated data 132, the transfer destination data D7, the transfer amount data D8, and the received transfer identification data D1_B stored in the storage device 7. Based on this, the electronically recorded claim data C_A and C_B with defense may be stored in the storage device 7. As a result, the identification data of the electronically recorded loan data can be matched, synchronized, and shared between the electronically recorded bond management device 1 and the device 106 of the electronically recorded bond institution. Further, in the present embodiment, the electronically recorded loan data stored in the storage device 7 of the electronically recorded loan management device 1 is matched with the electronically recorded loan data stored in the database 106A of the device 106 of the electronically recorded loan agency. -Synchronization and sharing may be used.

  After the split transfer, the value of the loan amount data D4_A provided in the electronically recorded claim data C_A of the split source is calculated from the value of the loan amount data D4 provided in the electronically recorded claim data C with defense, which is the basis of the split transfer. This is a value obtained by subtracting the value of the data D8.

  After the split transfer, the identification data D1, the creditor data D2, the debtor data D3, the due date data D5, and the defense content data D6 provided in the electronically recorded receivable data C_A of the split source became the basis of the split transfer, for example. The identification data D1, the creditor data D2, the debtor data D3, the payment due date data D5, and the defense content data D6 provided in the defense-attached electronically recorded claim data C remain the same.

  In the present embodiment, the identification data D1 of the electronically recorded receivables data C_A after the divisional transfer is the same as the identification data D1 of the electronically recorded receivables data C on which the divisional transfer is based. However, the electronically recorded receivables data C_A of the division source after the split transfer may have identification data different from the identification data D1 of the electronically recorded receivable data C (the original of the division) that was the basis of the split transfer. In this case, the device 106 of the electronic bond recording institution generates new identification data of the electronically recorded bond data C_A of the division source, notifies the completion of the division transfer, the identification data D1_B after the transfer, and the generated electronically recorded bond data of the division source. New identification data of the data CA may be transmitted to the electronically recorded receivables management device 1. The split transfer request unit 120 receives the split transfer completion notification, the identification data D1_B after the transfer, and the new identification data of the electronically recorded claim data C_A from the split from the device 106 of the electronic bond recording organization. New identification data of the identification data D1_B and the original electronically recorded bond data C_A may be stored in the storage device 7.

  After the split transfer, the transferred electronically recorded receivables data C_B includes identification data D1_B after transfer, creditor data D2_B after transfer corresponding to transferee data D7, debtor data D3, and transfer amount data D8. Corresponding receivable amount data D4_B, due date data D5, and defense content data D6 are included.

  Here, FIG. 3 will be described in more detail.

  The electronically recorded claim data C with defense includes identification data D1, creditor data D2, debtor data D3, credit amount data D4, due date data D5, and defense content data D6.

Further, the identification data D1 includes unique data 142, division source data 143, and division count data 144.
It should be noted that the identification data D1 may be generated by the electronically recorded loan management device 1 or by the device 106 of the electronically receivable recording organization when the electronically recorded claim data C with defense is recorded.
When the electronically recorded bond management device 1 generates the identification data D1, the electronically recorded bond management device 1 stores the generated identification data D1 in the storage device 7.
When the device 106 of the electronic bond recording agency generates the identification data D1, the identification data of the electronically recorded claim data C with defense is transmitted from the electronically recorded bond management device 1 to the device 106 of the electronic bond recording agency. Alternatively, the device 106 of the electronic bond recording organization may allocate the identification data D1 to the received electronically recorded bond data C with defense. In this case, the device 106 of the electronic bond recording organization transmits the identification data D1 to the electronically recorded bond management device 1 together with the occurrence completion notification. The electronically recorded bond management device 1 stores the identification data D1 received from the device 106 of the electronic bond recording organization in the storage device 7.

  The unique data 142 is, for example, a unique identifier attached to the electronically recorded claim data C with defense in order to identify the electronically recorded claim data C with defense.

  When the electronically recorded claim data C with defense is electronically recorded claim data generated by division transfer, the division source data 143 includes unique data of the electronically recorded claim data of the division source. This makes it possible to recognize whether or not the electronically recorded receivables data C is data generated by split transfer, and when the electronically recorded receivables data C is data generated by split transfer, the division source (basic or parent) Can be recognized. If the electronically recorded receivables data C is not the data generated by the split transfer but the data generated based on the generation request, the split source data 143 indicates that the data is not the data generated by the split transfer ( For example, information indicating that the data is generated based on the generation request may be included.

  The number-of-divisions data 144 represents the number of times the electronically recorded receivables-with-defense data C is generated by division transfer. The division count data 144 is zero, for example, when the electronically recorded receivables-with-defense data C is not data generated based on the division transfer request but data received together with the generation request (route data). It is 1 for data that has been divided and transferred once, and 2 for data that has been once divided and transferred and further divided and transferred. Similarly, the division and transfer are repeated in the same manner. Increase. By referring to the division count data 144, it is possible to recognize whether the electronically recorded receivables-with-defense data C is root data, and it is possible to recognize the number of divisions and transfers from the root data.

  In the present embodiment, since the electronically recorded claim data with defense C is route data, the division source data 143 includes data indicating that the data is not data generated by division transfer, and the division count data 144 indicates zero. .

  When the split transfer is performed on the defense-attached electronically recorded claim data C, the defense-attached electronically recorded claim data C becomes the defense-sourced electronically recorded claim data C_A.

  The defense-recorded electronically recorded receivables data C_A includes identification data D1, creditor data D2, debtor data D3, credit amount data D4_A, payment due date data D5, and defense content data D6. In the data included in the electronically recorded claim data C_A with the defense, the loan amount data D4 of the electronically recorded claim data C with defense is updated to the bond amount data D4_A, but the other data is the electronically recorded claim with defense. This is the same as other data included in data C.

  The transferred electronically recorded claim data with defense C_B includes identification data D1_B, creditor data D2_B, debtor data D3, credit amount data D4_B, due date data D5, and defense content data D6.

  The identification data D1_B, creditor data D2_B, and loan amount data D4_B included in the transferred electronically recorded claim data C_B are identification data D1, creditor data D2, and creditor data D4_B included in the electronically recorded claim data C with defense. It is different from the loan amount data D4.

  The identification data D1_B includes unique data 142B, division source data 143B, and division number data 144B. This identification data D1_B may be transmitted from the device 106 of the electronic bond recording organization to the electronically recorded bond management device 1 together with the division transfer completion notification.

  The unique data 142B is, for example, a unique identifier attached to the electronically recorded claim data C_B to identify the electronically recorded claim data C_B.

  The division source data 143B includes the unique data 143 of the defense-attached electronically recorded claim data C because the defense-attached electronically recorded claim data C_B is data that is divided and transferred from the defense-attached electronically recorded claim data C. Accordingly, it is possible to recognize that the defense-attached electronically recorded claim data C_B is data that has been split and transferred, and the defense-attached electronically recorded claim data C is the data of the division source (parent) of the defense-attached electronically recorded claim data C_B. It is recognizable.

  The division count data 144B indicates that the electronically recorded claim data C_B with defense is data relating to the first division transfer. By referring to the division count data 144B, it is possible to recognize that the electronically recorded claim data C_B with defense is not the root data, and it is possible to recognize that the number of divisions and transfers from the root data is one.

  In the present embodiment, the device 106 of the electronic receivables recording organization or the split transfer request unit 120 of the electronically recorded receivables management device 1 forms the basis of the split transfer when the electronically recorded receivables data C with defense is split and transferred. The electronically recorded claim data C_A with the defense may be generated by associating and storing history data indicating that the transfer has been divided with respect to the electronically recorded claim data C with defense. The history data will be described in more detail later with reference to FIG.

  The device 106 of the electronic bond recording organization or the split transfer request unit 120, when split transfer of the electronic record bond data C with defense, splits the electronic record bond data C with defense, which is the basis of the split transfer, with the electronic source of the split. An update method of updating (or overwriting) with the recorded credit data C_A may be used. Alternatively, the device 106 of the electronic bond recording organization or the split transfer request unit 120 invalidates the electronically recorded claim data C with defense, which is the basis of the split transfer, and converts the electronically recorded bond data C_A of the split source after the split transfer. A write-once storage method may be used in which write-once storage is performed and the electronically recorded claim data C_A of the division source is made effective instead of the electronically recorded claim data C with defense.

  In the present embodiment, the electronically recorded bond data C is generated by the electronically recorded bond management device 1. The generation of the electronically recorded claim data C_A and C_B with a defense is executed based on the data received by the apparatus 106 of the electronic claim recording organization from the electronically recorded claim management apparatus 1 and the request. The electronically recorded receivables management device 1 generates the electronically recorded receivables-with-defense data C_A and C_B, for example, when receiving the divisional transfer completion notification from the device 106 of the electronically receivable recording organization, The data C_A and C_B may be stored in the storage device 7 of the electronically recorded receivables management device 1. Thereby, the contents of the electronically recorded bond data can be matched between the storage device 7 and the database 106A.

  In the present embodiment, the device 106 of the electronic bond recording organization or the division transfer request unit 120 of the electronic record bond management device 1 divides the identification data included in the defense-attached electronic record bond data C requested to be divided. If the number-of-times data is equal to or greater than the threshold, the division of the electronically recorded claim data C with defense may not be permitted.

  The defense disconnection request unit 121 transfers or delivers the electronically recorded claim data C with a defense from any of the terminal 104 of the delivery company, the terminal 100 of the ordering company, the electronic contract system 102, the device 108 of the financial institution, and the device 110 of the guarantee association. A defense valve cut (change) request 137 indicating that the acceptance has been completed is received.

  The defense disconnection request unit 121 sends a defense disconnection request 137 from at least one of the delivery company terminal 104, the ordering company terminal 100, the electronic contract system 102, the financial institution device 108, and the guarantee association device 110. A corresponding defense disconnect (change) acknowledgment 138 is received.

Then, the defense disconnection request unit 121 transmits the defense disconnection request 139 to the device 106 of the electronic credit recording organization or the proxy device 111.
Further, the defense disconnection request unit 121 receives the defense disconnection request 137 or receives a defense disconnection notification 140 which is a response to the defense disconnection request 139 from the device of the electronic credit recording agency or the proxy device 111. A defense disconnection process may be performed on the defense-recorded electronically recorded claim data C stored in the storage device 7. For example, the defense disconnection request unit 121 deletes the defense content data D6 included in the defense-attached electronically recorded claim data C stored in the storage device 7. This makes it possible to match the data content between the storage device 7 and the database 106A.

  Based on the defense disconnection request 139, the device 106 of the electronic bond recording organization executes a defense disconnection process on the defense-recorded electronically recorded bond data C corresponding to the defense disconnection request 139. For example, the device 106 of the electronic bond recording organization deletes the defense content data D6 included in the defense-attached electronically recorded bond data C stored in the database 106.

  In this manner, when the defense of the electronically recorded claim with a defense is cut off, by deleting the defense content data D6 from the corresponding electronically recorded claim data C, the electronically recorded claim data C can be replaced with the ordinary electronically recorded claim data. Can be changed to a data structure and then managed.

  Then, the device 106 of the electronic receivables recording institution transmits the defense disconnection notification 140 to the electronically recorded receivables management device 1 or the electronic receivables receivables management device 1 via the proxy device 111 as a response to the defense disconnection request 139.

  The defense disconnection notification unit 122, when receiving the defense disconnection notification 140 from the electronic credit recording institution device 106 or the proxy device 111, sends the defense disconnection notification 141 to the financial institution device 108, the ordering company terminal 100, The transmission is made to at least one of the terminals 104 of the delivery company.

The device 108 of the financial institution, the terminal 100 of the ordering company, or the terminal 104 of the delivery company can receive the defense disconnection notification 141 from the electronically recorded receivables management device 1. As a result, the financial institution can recognize that the defense of the electronically recorded receivable with a defense has been cut off, can perform the collateral information change procedure, and re-evaluates the cut off electronically recorded claim with the defense, A new amount of loan and collateral can be set. The ordering company can perform the due date change procedure and record the electronically recorded debt balance sheet. The supplier can make a note on the electronically recorded receivables balance sheet and make notes on the collateral setting balance sheet.
Note that the defense-recorded electronically recorded claim data C_A and C_B generated by the division transfer can also be defended in the same manner as the defense-recorded electronically recorded claim data C.

  In the present embodiment, the processor 5 may read various data related to the electronically recorded receivable with defense from the storage device 7 and extract the data from the order content data by the extraction unit 54 and stored in the storage device 7, and transmit the data to another device. Good. As a result, the other devices can access the electronically recorded receivables management device 1 and acquire data and the like stored in order to comply with the Subcontract Act without accessing the device 106 of the electronically receivable recording agency. can do. Further, by accessing the electronically recorded receivables management device 1, other devices can easily acquire the electronically recorded receivables data C, C_A, C_B, and the history data without accessing the device 106 of the electronically receivable recording organization. , You can check.

  By using the electronically recorded bond management device 1 according to the present embodiment described above, an electronically recorded bond can be generated from the ordering stage, and the handling of the electronically recorded bond can be lengthened.

  In the present embodiment, for example, generation, change, division transfer, transfer, defense disconnection, etc. of the electronically recorded claim data C with defense can be appropriately managed, and the data extracted from the order content data is stored in the storage device 7. By memorizing it, you can comply with the Subcontract Act.

  In the present embodiment, regarding the electronically recorded claim data C, C_A, and C_B with defense relating to the split transfer, it is possible to sequentially trace the child (transferred data) to the parent (base data).

  In the present embodiment, the electronically recorded receivables-with-defense data C, which is the basis of the split transfer, includes information indicating how many pieces of data have been divided, identification data indicating child data having the own data as a division source, and the like. May be included. Thus, the electronically recorded claim data C_A and C_B divided and transferred can be sequentially traced from the defense-recorded electronically recorded claim data C on which the division transfer is based.

In the present embodiment, the division transfer is mainly described. However, the electronically recorded claim data C with a defense may be simply divided into a plurality of pieces and not transferred. Further, it is not necessary to simply transfer the electronically recorded claim data C with defense and divide it.
When dividing the electronically recorded claim data C with a defense into a plurality of pieces, the electronically recorded claim management device 1 sends, for example, a request for division, designation data indicating a division target, and the amount of the post-divided claim to the apparatus 106 of the electronic claim recording organization. And data (divided amount data). When receiving the division request, the designated data, and the data of the amount of the divided bond from the electronically recorded bond management apparatus 1, the apparatus 106 of the electronic bond recording organization stores the electronic request stored in the database 106A and indicates the electronic data indicated by the specified data. A first electronic device including first bond amount data indicating a value obtained by subtracting the value of the divided bond amount data from the value of the bond amount data D4 based on the recorded bond amount data C and the divided bond amount data. The database 106 stores the recorded credit data and second electronically recorded credit data including the post-division identification data and the second credit data corresponding to the post-division credit data. Then, the device 106 of the electronic bond recording institution transmits the division completion notification and the divided identification data to the electronically recorded bond management device 1. When receiving the division completion notification and the post-division identification data, the electronically recorded receivables management device 1 stores the post-division identification data in the storage device 7. Note that, when receiving the division completion notification and the post-division identification data, the electronically recorded receivables management device 1 performs the same division processing on the defense-attached electronically recorded receivables data C stored in the storage device 7 as described above. It may be executed to match the data content between the storage device 7 and the database 106A.

  Currently, widely used paper bill receivables are indivisible. However, in the present embodiment, a part of the amount of the electronically recorded receivable with a defense can be divided, and further transferred after the division, so that the receivable can be operated flexibly.

  In the present embodiment, in the divisional transfer of the electronically recorded claim data C with defense, the first part of the electronically recorded claim data C with defense is held by the original creditor continuously, Is described as an example of transfer to another creditor. However, for example, each of the plurality of electronically recorded claim data C with defense may be transferred to a plurality of creditors different from the original creditor. Also, for example, the first part of the electronically recorded claim data C with defense is continuously held by the original creditor, and the other parts of the electronically recorded claim data C with defense are a plurality of other parts. May be transferred to creditors of In the case where there are a plurality of transferees as in these examples, the electronically recorded receivables management device 1 converts the transferee data and the transfer amount data corresponding to the respective transferred portions into the device 106 of the electronic receivable recording agency or a proxy. Transmit to the device 111. When receiving the plurality of transferee data and the transfer amount data, the apparatus 106 of the electronic bond recording agency generates a plurality of divided electronic defense bond data with a defense after the division, stores the generated data in the database 106A, and stores the divided transfer. The subsequent identification data is transmitted to the electronically recorded receivables management device 1.

(Second embodiment)
In the present embodiment, details of the electronically recorded receivables management device 1 will be described.

  In the present embodiment, the electronically recorded receivables management device 1 provides, for example, a cloud-based electronic payment service that satisfies the security standard of a financial institution. In this embodiment, the electronically recorded receivables management device 1 may be referred to as a POFS (Purchase Order Finance System). The terminal 100 of the ordering company, the terminal 104 of the delivery company, the device 106 of the electronic bond recording institution, the device 108 of the financial institution, and the device 110 of the guarantee association that use the electronic record receivables management device 1 use the ID and the ID, for example, via the Internet. By inputting a password or the like, the user can access the electronically recorded receivables management device 1.

In the present embodiment, the electronically recorded receivables management device 1 generates electronically recorded receivables data C with defense based on an ordering contract. The defense means, for example, that the ordering company pays the amount indicated in the receivable after delivery, acceptance, or delivery.
More specifically, the electronically recorded receivables management device 1 includes a creditor data D2 indicating a creditor relating to a credit generated with the order from the device 100 of the ordering company, the device 104 of the delivery company, or the electronic contract system 102, It receives the debtor data D3 indicating the debtor, the bond amount data D4 indicating the amount of the bond, the payment date data D5 indicating the payment date, and the defense content data D6 indicating the above-mentioned defense content.

  In addition, the electronically recorded receivables management device 1 uses the device 100 of the ordering company, the device 104 of the delivery company, or the electronic contract system 102 to perform the above-mentioned creditor data D2, debtor data D3, loan amount data D4, and due date data D5. , Receiving the generation consent 130 indicating the consent to the defense content data D6.

When receiving the approval 130, the electronically recorded receivables management apparatus 1 identifies the identification data D1, the obligor data D2, the obligor data D3, the receivable amount data D4, the payment due date data D5, the defense date, and the like. The electronically recorded claim data C with defense including the content data D6 is generated, and the generated electronically recorded claim data C with defense and the generation request 131 of the electronically recorded claim data C with defense are transmitted to the apparatus 106 or the proxy apparatus of the electronic claim recording organization. Send to 111. Further, the electronically recorded bond management device 1 stores the defense-attached electronically recorded bond data C in the storage device 7 when receiving the occurrence completion notification from the device 106 or the proxy device 111 of the electronic bond recording organization.
In the present embodiment, the identification data D1 of the electronically recorded receivables data C with defense is generated by the electronically recorded receivables management device 1, but may be generated by the device 106 of the electronically receivable recording organization. This identification data D1 is shared between the storage device 7 of the electronically recorded receivables management device 1 and the database 106 of the device 106 of the electronically receivable recording agency.

  In the present embodiment, the case where the electronically recorded receivables management device 1 accesses the device 106 of the electronically receivable recording organization without passing through the proxy device 111 will be described as an example, and the description of the case where the proxy device 111 is used will be omitted. I do.

  FIG. 4 is a block diagram illustrating an example of the electronically recorded receivables management device 1 according to the present embodiment.

  The electronically recorded bond management device 1 includes a memory 3, a processor 5, a storage device 7, and the like. The memory 3, the processor 5, and the storage device 7 are communicably connected to each other via a bus BA.

  The memory 3 may be divided into a plurality. The memory 3 and the processor 5 or the memory 3 and the storage device 7 may be integrated.

  The storage device 7 is a nonvolatile memory such as a hard disk, a solid state drive (SSD), and a flash memory. The storage device 7 may be a storage device such as a database.

  The storage device 7 stores, for example, user data U, case-by-case data I, condition data E, program P, electronically recorded claim data C with defense including generated identification data D1, and defense generated in response to a division transfer completion notice. The electronically recorded claim data C_A and C_B are stored. Note that the electronically recorded claim data C_A and C_B with defense may be stored in the storage device 7 when a split transfer request is received, instead of being stored in the storage device 7 in response to the split transfer completion notification.

  The user data U is stored in the terminal 100 of the ordering company using the electronically recorded receivables management device 1, the terminal 104 of the delivery company, the device 106 of the electronic receivables recording institution, the device 108 of the financial institution, the device 110 of the guarantee association, and the like. It contains information necessary to access the management device 1. As information necessary for accessing the electronically recorded receivables management device 1, for example, a user ID, a password, and the like are used. Further, it is preferable that the user data U is associated with, for example, a person in charge, an approver, and case-by-case data I that can be viewed or accepted, for each company that uses the electronically recorded receivables management device 1.

  The case-specific data I is data that is generated and managed for each order case, and includes order-order data B, bond-related data D, and the like.

  The order data B is data indicating the contents of an order contract generated between the ordering company and the delivery company. The order data B corresponds to, for example, the order content data described above. The order data B includes, for example, the content, quantity, unit price, and order amount of the product ordered by the terminal 100 of the ordering company, the terminal 104 of the delivering company, or the electronic contract system 102 (for example, FIG. 13 and FIG. 14 (corresponding to the order amount 302e of the credit line data 302 described below), the time of delivery to the delivery company, and the like.

  The bond related data D includes data necessary when the electronically recorded bond management device 1 requests the device 106 of the electronic bond recording organization to generate an electronically recorded bond. The bond-related data D includes, for example, identification data D1, creditor data D2, debtor data D3, bond amount data D4, due date data D5, defense content data D6, transferee data D7, transfer amount data D8, and consent data D9. Including.

  Further, in the present embodiment, the accepted data may be extracted from the order data B, and the extracted data may be included in the loan-related data D. Then, the bond-related data D may be managed as data necessary for complying with the Subcontract Act.

  The identification data D1 is data for identifying an electronically recorded bond. It is preferable that the identification data D1 is, for example, a number, a symbol, or the like assigned to each bond.

  The creditor data D2 is data indicating the creditor of the electronically recorded credit. The creditor is, for example, a delivery company.

  The debtor data D3 is data indicating the debtor of the electronically recorded claim. The debtor is, for example, an ordering company.

  The bond amount data D4 is data indicating the bond amount of the electronically recorded bond.

  The due date data D5 is data indicating the due date of the electronically recorded receivable. The payment due date is, for example, the same as the payment due date of ordinary accounts receivable and bill receivables.

  The defense content data D6 is data indicating the content of the defense attached to the electronically recorded claim when the electronically recorded claim is generated. The defense content data D6 is, for example, text data. More specifically, if an electronically recorded receivable is generated at the ordering stage, the defense content data D6 of the electronically recorded receivable includes that the ordering company pays the amount indicated in the receivable after delivery, acceptance, or delivery. Is preferred. Further, the defense content data D6 may include a statement that the obligor can refuse to pay the electronically recorded receivable when the deliverable according to the contract is not delivered.

  The transfer destination data D7 is data indicating a transfer destination of the electronically recorded claim. The transfer destination data D7 is, for example, data indicating the creditor of the electronically recorded bond after the transfer. The transfer destination indicated by the transfer destination data D7 may be, for example, a financial institution, a guarantee association, or an arbitrary third party.

  The transfer amount data D8 is data indicating the amount to be split from the loan amount data D4 of the electronically recorded receivable when the electronically recorded receivable is dividedly transferred (partially transferred). In the present embodiment, the electronically recorded receivable is divided into, for example, two, and if one of the receivables is transferred, the original electronically recorded receivable and the transferred electronically recorded receivable are generated. The transfer amount data D8 is, for example, data indicating the bond amount of the electronically recorded bond transferred after the division.

  The consent data D9 is data including various consents for a request for generation, change request, split transfer request, transfer request, etc. of an electronically recorded bond issued to the electronically recorded bond management device 1. Various consents included in the consent data D9 can be transmitted from the terminal 100 of the ordering company, the terminal 104 of the delivering company, the electronic contract system 102, the device 108 of the financial institution, or the device 110 of the guarantee association. More specifically, for example, the terminal 104 of the delivery company requests the electronically recorded receivables management device 1 to generate an electronically recorded receivable, and the creditor data D2, the debtor data D3, and the amount of the receivable, which indicate the contents of the electronically recorded receivable with defense. When the data D4, the due date data D5, the defense content data D6, and the like are transmitted, the terminal 100 of the ordering company transmits to the electronically recorded receivables management device 1 a consent to accept the contents of the electronically recorded receivables with defense. The electronically recorded receivables management device 1 stores the received consent data D9 including the generated consent in the storage device 7. By confirming the consent data D9, it is possible to know the status of the electronically recorded claim data C with defense and the progress of the operation. For example, the user can know that the electronically recorded claim data C with defense is in a state of waiting for approval. Can be.

  The consent to generate an electronically recorded receivable included in the consent data D9 corresponds to the consent to generate 130 described above.

  The split transfer agreement included in the agreement data D9 corresponds to the above-described split assignment agreement 135.

  Note that the bond-related data D may include other data not described above. For example, the bond-related data D may include data indicating the presence or absence of defense contents.

  The condition data E is, for example, data indicating a condition used to comply with the Subcontract Act. The condition data E includes, for example, data for extracting creditor data D2, debtor data D3, loan amount data D4, due date data D5, and defense content data D6 from the order data B. The condition data E includes, for example, data indicating conditions to qualify as a creditor, data indicating conditions to qualify as a debtor, data indicating conditions such as an appropriate amount of a loan and a due date according to a case, and contents of an appropriate defense. It may include data indicating conditions for confirmation, data indicating appropriate transaction conditions, and the like.

  The program P is a program for executing processing relating to electronically recorded receivables management. The program P is read by the processor 5 and stored in the memory 3, for example.

  The memory 3 is used when the processor 5 executes various software. The memory 3 is composed of, for example, a RAM (Random Access Memory) and is used as a work area or the like. The memory 3 stores, for example, various software or data read from the storage device 7 by the processor 5. The various software includes an operating system (OS), a data management program, various application programs, and the like.

  The processor 5 executes various software (programs) and controls the electronically recorded receivables management device 1. The processor 5 is, for example, a CPU (Central Processing Unit), an MPU (Micro Processing Unit), a DSP (Digital Signal Processor), or the like.

  In the present embodiment, the processor 5 functions as, for example, a user management unit 51, a request unit 52, a data processing unit 53, an extraction unit 54, and a communication unit 55 by executing the program P read into the memory 3. .

  The user management unit 51 manages users of the electronically recorded receivables management device 1. The user management unit 51 generates user data U required for a user to access the electronically recorded receivables management device 1 and stores the user data U in the storage device 7. When there is access from the user, for example, the user management unit 51 urges the user to input a user ID and a password, and compares the input user ID and password with the user data U read from the storage device 7. I do. If the verification is successful, the user management unit 51 permits the use of the electronically recorded receivables management device 1, and rejects the use of the electronically recorded receivables management device 1 if the verification is unsuccessful.

  The request unit 52 issues various requests to the device 106 of the electronic bond recording organization. The request unit 52 includes, for example, an occurrence request unit 52A, a change request unit 52B, a transfer request unit 52C, a payment completion unit 52D, and the like.

  The generation requesting unit 52A transmits the electronically recorded claim data C with defense and an occurrence request to the device 106 of the electronic bond recording organization. The details of the electronically recorded claim data C with defense will be described with reference to FIG.

  The generation requesting unit 52A reads, for example, identification data D1, creditor data D2, debtor data D3, credit amount data D4, due date data D5, defense content data D6 from the credit-related data D included in the storage device 7, The electronically recorded claim data C with defense is generated based on the read data. The generation request unit 52A transmits, for example, the generated electronically recorded claim data C with defense and a request to generate the electronically recorded claim data C with defense to the device 106 of the electronic bond recording organization. As a result, the electronically recorded claim data C with defense is stored in the database 106A of the apparatus 106 of the electronic claim recording organization. Note that the generation requesting unit 52A may also store the electronically recorded claim data C with defense in the storage device 7, and the processor 5 may manage the electronically recorded claim data C stored in the storage device 7. This occurrence request unit 52A corresponds to, for example, the above-described occurrence request unit 116.

When changing the electronically recorded claim data C with a defense, the change request unit 52B transmits, for example, identification data indicating the electronically recorded claim data with defenses C and a change request to the device 106 of the electronic bond recording organization. The items to be changed include, for example, a change in the receivable amount data D4, a change in the due date data D5, a defense disconnection (change in the presence or absence of a defense), a change in the defense content data D6, and the like. The change request unit 52B transmits a request to change the electronically recorded claim data C with defense, and if necessary, data indicating the details of the change to the apparatus 106 of the electronic claim recording organization. The change request unit 52B corresponds to, for example, the above-described defense disconnection request unit 121.
The change request unit 52B stores the change completion notification in the storage device 7 when, for example, a change completion notification is received from the device 106 of the electronic credit recording institution or when a change request is transmitted to the device 106 of the electronic credit recording institution. The electronically recorded claim data C with defense may be changed in the same manner.
A more specific example of defense valve cutting will be described. First, the electronically recorded receivables management device 1 transmits a change request indicating the defense disconnection and the identification data of the defense disconnection target to the device 106 of the electronic receivable recording organization. The apparatus 106 of the electronic bond recording organization receives the change request and the identification data, accesses the database 106A based on the received change request and the identification data, and defends the electronically recorded bond data with a defense to be changed in the database 106A. Delete the content data. After the change processing, the device 106 of the electronic bond recording organization transmits a defense disconnection notification 140 to the electronically recorded bond management device 1. Then, the electronically recorded receivables management device 1 executes the same change process as described above also on the electronically recorded receivables with defense stored in the storage device 7, and stores the electronically recorded receivables data in the database 106 </ b> A and the storage device 7. Reconcile with electronically recorded receivables data.

The transfer request unit 52C transmits the transfer destination data D7 and the electronically recorded claim data C with defense to the device 106 of the electronic claim recording organization when the electronically recorded claim with defense regarding the electronically recorded claim data C is transferred. The identification data and the transfer request are transmitted. In the present embodiment, the electronically recorded receivables can be split and transferred. Details of the processing executed by the transfer requesting unit 52C when the transfer is divided and transferred will be described later with reference to FIG. The transfer request unit 52C corresponds to, for example, the above-described split transfer request unit 120.
When the electronically recorded claim data C with defense is transferred, for example, the transfer requesting unit 52C converts the transfer destination data D7 and the electronically recorded claim data C with defense to be transferred stored in the storage device 7. Based on this, the electronically recorded claim data with the defense after the transfer may be generated, and the electronically recorded claim data with the defense after the transfer and the transfer request may be transmitted to the device 106 of the electronic bond recording organization.
The transfer request unit 52C receives the transfer completion notification from the device 106 of the electronic bond recording organization, or transmits the transfer request to the device 106 of the electronic bond recording organization, and stores the defense stored in the storage device 7. The electronically recorded receivables data C in the database 106A and the electronically recorded receivables in the storage device 7 by changing the attached electronically recorded receivables data C to the transferred electronically recorded receivables data including the creditor data corresponding to the transferee data D7. The data may be matched.

  When the payment completion unit 52D receives the completion of the payment of the amount of the receivable from the terminal 100 of the ordering company, the terminal 104 of the delivery company, or the device 108 of the financial institution, for example, the payment completion unit 52D Send payment complete.

  The data processing unit 53 performs, for example, input reception, comparison, and generation of various data. The data processing unit 53 may, for example, generate data necessary for dividing and transferring the electronically recorded claim data C with defense to the electronically recorded claim data C_A and the transferred electronically recorded claim data C_B. Further, the data processing unit 53 may generate, for example, a user interface for prompting the user to input various data, and store the input data in the storage device 7.

  The communication unit 55 connects the electronically recorded receivables management device 1 to a network so as to be communicable by wire or wireless communication. The communication unit 55 controls transmission and reception of data, information, requests, consents, commands, commands, instructions, notifications, responses, signals, etc. with external devices that can access the electronically recorded receivables management device 1 via a network. The network is, for example, the Internet.

  The part of the data processing unit 53 that accepts data input and the communication unit 55 include, for example, the first receiving unit 114, the second receiving unit 115, the third receiving unit 118, and the fourth receiving unit. 119.

  The part of the data processing unit 53 that generates data necessary for generating the electronically recorded claim data C_A of the division source and the transferred electronically recorded claim data C_B may be included in the transfer requesting unit 52C, for example.

  The extracting unit 54 receives, for example, the order data B from the external device, stores the order data B, receives the acceptance of the partial data included in the order data B from another external device, and receives the order data B By extracting the accepted partial data, the bond-related data D is generated, and the bond-related data D is stored in the storage device 7. For example, the extraction unit 54 may extract the creditor data D2, the debtor data D3, the loan amount data D4, the due date data D5, and the defense content data D6 from the order data B according to the condition data E.

  As described above, for example, the extraction unit 54 may use the condition data E stored in the storage device 7 to determine whether the transaction content between the ordering company and the delivery company complies with the Subcontract Act. Good. For example, the extraction unit 54 reads the order data B or the bond-related data D from the storage device 7 and compares the order included in the condition data E with the order data B or the bond-related data D, thereby obtaining the order data. It may be determined whether B or the bond-related data D satisfies the condition indicated by the condition data E. Further, for example, the extraction unit 54 compares the condition data E with the creditor data D2, the debtor data D3, the loan amount data D4, the due date data D5, the defense content data D6, etc. included in the electronically recorded loan data C. Alternatively, it may be determined whether each data included in the electronically recorded bond data C satisfies the condition indicated by the condition data E.

  When the extraction unit 54 determines that the condition is not satisfied, for example, the extraction unit 54 may transmit a notification indicating that the condition is not satisfied to the terminal 100 of the ordering company, the terminal 104 of the delivery company, and other external devices. .

  In the present embodiment, the functions of the program P are described separately for the user management unit 51, the request unit 52, the data processing unit 53, the extraction unit 54, and the communication unit 55 for convenience. However, the program P may include another processing unit. For example, the program P may be configured as a single processing unit by a control unit that controls the entire program, or a plurality of processing units may be configured in a different manner from FIG. It may be divided into parts. That is, the user management unit 51, the request unit 52, the data processing unit 53, the extraction unit 54, and the communication unit 55 may be further divided or integrated.

  FIG. 5 is a data structure diagram showing an example of the electronically recorded bond data C according to the present embodiment.

  In the present embodiment, the device 106 of the electronic bond recording organization or the electronically recorded bond management device 1 associates the electronically recorded bond data C with the history data CH for the electronically recorded bond data C and associates the database 106A or It is stored in the storage device 7 of the electronically recorded receivables management device 1.

  The history data CH indicates a data change state executed on the electronically recorded bond data C in a time series. The history data CH may have, for example, a tree structure.

  In the following, using the example of FIG. 5, the generation request, the division transfer request, the transfer request, the change request, the defense disconnection request, and the payment completion for the electronically recorded receivables data C are transmitted from the electronically recorded receivables management device 1 to the electronically receivable recording organization. A description will be given of a change state of the electronically recorded bond data C in the database 106A of the electronic bond recording organization when transmitted to the device 106. The changed state of the electronically recorded bond data C in the storage device 7 of the electronically recorded bond management device 1 may be the same as the changed state in FIG.

  First, the electronically recorded bond management device 1 transmits a request to generate electronically recorded bond data C and the electronically recorded bond data C to the device 106 of the electronic bond recording organization. Then, the device 106 of the electronic bond recording organization stores the electronically recorded bond data C in the database 106A.

  Next, the electronically recorded receivables management device 1 transmits the split transfer request 136 to the electronically recorded receivables data C, the designation data 132 for specifying the electronically recorded receivables data C, the transferee data D7, and the transfer amount data D8, It is assumed that the data is transmitted to the device 106. In this case, the apparatus 106 of the electronic bond recording organization accesses the electronically recorded bond data C of the database 106A based on the designated data 132, and obtains the bond amount data D4_A indicating the value obtained by subtracting the transfer amount data D8 from the bond amount data D4. Then, the request content R1 indicating the split transfer and the loan amount data D4_A after the split transfer are added to the history data CH related to the electronically recorded bond data C. This state corresponds to, for example, the electronically recorded bond data C_A. In addition, the device 106 of the electronic bond recording organization generates electronically recorded bond data C_B including the transferred creditor data D2_B corresponding to the transferee data D7 and the transferred bond amount data D4_B corresponding to the transfer amount data D8. Then, the electronically recorded bond data CB is stored in the database 106A.

  Next, it is assumed that the electronically recorded receivables management device 1 has transmitted the transfer request for the electronically recorded receivables data C and the creditor data D10 after the transfer to the device 106 of the electronic receivables recording organization. In this case, the device 106 of the electronic bond recording organization adds the request content R2 representing the transfer and the creditor data D10 (transfer destination data) after transfer to the history data CH related to the electronically recorded bond data C. This state corresponds to, for example, a state in which the creditor data D2 of the electronically recorded credit data C is updated to the creditor data D10.

  Next, it is assumed that the electronically recorded receivables management device 1 transmits a request to change the electronically recorded receivables data C and the receivable amount data D11 to the device 106 of the electronic receivables recording organization. In this case, the device 106 of the electronic bond recording organization adds the request content R3 indicating the change and the changed bond amount data D11 to the history data CH related to the electronically recorded bond data C. This state corresponds to, for example, a state in which the loan amount data D4_A after the division transfer of the electronically recorded loan data C is updated to the bond amount data D11.

  Next, it is assumed that the electronically recorded bond management device 1 has transmitted a defense disconnection request for the electronically recorded bond data C to the device 106 of the electronic bond recording organization. In this case, the device 106 of the electronic bond recording agency adds the request content R4 indicating the defense disconnection to the history data CH related to the electronically recorded bond data C. Note that, in response to the defense disconnection request, the device 106 of the electronic bond recording organization may delete the defense content data D6 of the electronically recorded bond data C. This state corresponds to, for example, a state in which the defense of the electronically recorded bond data C is cut off.

  Then, it is assumed that the electronically recorded receivables management device 1 has transmitted the payment completion for the electronically recorded receivables data C to the device 106 of the electronically receivable recording organization. In this case, the device 106 of the electronic bond recording institution adds the content R5 indicating the payment completion to the history data CH related to the electronically recorded bond data C. This state corresponds to, for example, a state in which the electronically recorded bond data C has disappeared.

  FIG. 6 is a block diagram illustrating an example of the electronically recorded receivables management system 10 according to the present embodiment.

  As described with reference to FIG. 1 above, the electronically recorded receivables management system 10 includes an electronically receivables receivable management device (POFS) 1, a terminal 100 of an ordering company, an electronic contract system 102, a terminal 104 of a delivery company, and a device of an electronic receivable recording organization. 106, a financial institution device 108, a guarantee association device 110, and the like.

  The terminal 100 of the ordering company and the terminal 104 of the delivery company transmit data related to ordering to the electronic contract system 102 (arrows A1 and A2).

  The electronic contract system 102 may be, for example, an EDI (Electric Data Interchange). In this case, the electronic contract system 102 is a system capable of exchanging data on ordering between the terminal 100 of the ordering company and the terminal 104 of the delivery company via a network, for example. In the electronic contract system 102, at least one of a widely agreed rule or a rule agreed between the ordering company and the delivery company is determined through data exchange.

  Note that the electronic contract system 102 is not limited to the terminal 100 of the ordering company and the terminal 104 of the delivery company, but also the terminal 100 of the ordering company, the terminal 104 of the delivery company, the device 108 of the financial institution, and the device 110 of the guarantee institution. May be used between the combinations of.

  The electronically recorded receivables management device 1 receives the order data B from the electronic contract system 102 (arrow A3) and stores it in the storage device 7. Note that the data processing unit 53 may have a function of mutually converting a widely agreed rule and a rule agreed between the ordering company and the delivery company.

  The order data B received by the electronically recorded receivables management device 1 may be a part of data on the order received and managed by the electronic contract system 102. That is, the data processing unit 53 stores, for example, a part of the order-related data managed by the electronic contract system 102 in the storage device 7 as the order-receiving data B. The accepted partial data may be extracted to generate the bond-related data D, and the bond-related data D may be stored in the storage device 7.

  The electronic record receivables management device 1 may acquire the order data B from the terminal 100 of the ordering company and / or the terminal 104 of the delivery company without passing through the electronic contract system 102 (arrows A4, A5). In this case, the data processing unit 53 may provide, for example, a user interface allowing direct input of the order data B or the like to the terminal 100 of the ordering company and / or the terminal 104 of the delivery company.

  The data processing unit 53 and the extracting unit 54 receive electronic data or the like in which order contents are described based on a predetermined format, and generate order data B and bond-related data D based on the received data. To achieve. The electronic data may be, for example, mail, FAX, PDF data, and other electronic data.

  The device 106 of the electronic credit recording agency is responsible for requesting generation, divisional transfer, change (defense cut, change in amount of credit), transfer (change of creditor), payment completion, etc. of the electronically recorded bond data C, and various requests related to this request. The data is received from the electronically recorded receivables management device 1, and based on the received request and various data, generation, divisional transfer, change, transfer, payment completion, etc. of the electronically recorded receivables data C are executed (arrow A6). In addition, the device 106 of the electronic bond recording organization transmits a completion notification to the electronic bond management device 1 indicating that various processes have been completed.

  The device 108 of the financial institution can read, for example, data stored in the electronically recorded receivables management device 1, and is stored in the device 106 of the electronic receivables recording institution via the electronically recorded receivables management device 1. The electronically recorded bond data C can be read. The financial institution refers to the data stored in the electronically recorded receivables management device 1 or the electronically recorded receivables data C stored in the device 106 of the electronically receivable recording institution, conducts a loan examination, and provides the lending company with the lender. Make a loan. More specifically, the financial institution examines, for example, whether the electronically recorded receivables in which the paying company is the creditor are appropriate as loan collateral. If the examination is successful, the financial institution receives the transfer of the electronically recorded receivables from the delivery company and executes a loan to the delivery company in accordance with the transfer. When a change occurs in the electronically recorded receivables, the device 108 of the financial institution transmits a request to change the electronically recorded receivables data C corresponding to the security information to the electronically recorded receivables management device 1 in accordance with the change. Further, the apparatus 108 of the financial institution gives the electronically recorded receivables management apparatus 1 a consent that the apparatus 106 of the electronically receivable recording institution changes or transfers the electronically recorded receivables data C, for example. Transmit to the device 1 (arrow A7).

  The Guarantee Association accepts guarantee applications from financial institutions. The guarantee association performs a guarantee examination on the loan to be executed by the financial institution, and if the examination is judged to be successful, guarantees the loan amount of the financial institution. As described above, when the guarantee association performs a guarantee examination on the loan amount of the financial institution, the device 110 of the guarantee association can, for example, view data stored in the electronically recorded receivables management device 1, and The electronically recorded bond data C stored in the device 106 of the electronic bond recording organization may be received via the bond management device 1 and the electronically recorded bond data C to be guaranteed may be browsed.

  FIG. 7 is a diagram illustrating an example of a guarantee period for an electronically recorded loan and a loan period with the electronically recorded loan as collateral according to the present embodiment. FIG. 7 shows the state of the electronically recorded receivables during the period from when the order is placed to when the payment is made, and the state of the guarantee, loan, and collateral for the electronically recorded receivables, with a time axis on the left and right.

  At time T1, an order is placed by the terminal 100 of the ordering company and the terminal 104 of the delivery company. After the order is placed, the electronically recorded receivables management device 1 and the device 106 of the electronic receivables recording organization generate electronically recorded receivables data C1 with a defense of delivery, acceptance or payment after delivery.

  In this case, the financial institution executes the first loan L1 based on the first collateral S1. The guarantee association makes a first guarantee G1 for the first loan L1.

  Next, at time T2, delivery, acceptance, or delivery is performed. After the delivery, acceptance, or delivery, the device 106 of the electronic credit recording agency executes the change, so that the defense-attached electronically recorded debt data C1 becomes the electronically recorded debt data C2 with no defense.

  In this case, the financial institution 108 executes the second loan L2 based on the second collateral S2. The guarantee association 110 makes a second guarantee G2 for the second loan L2.

  Here, as an example of the above-described first collateral S1, second collateral S2, first loan L1, second loan L2, first guarantee G1, and second guarantee G2, the following pattern is used. Can be considered.

  As a first pattern, the financial institution considers that the first loan L1 and the second loan L2 are loans for a defense-attached loan, and both provide a loan with an amount obtained by discounting a predetermined amount from the amount of the loan. . In this case, the guarantee association sets the first guarantee G1 and the second guarantee G2 as guarantees of the same amount as the first loan L1 and the second loan L2. The predetermined ratio is, for example, 50%. Note that the first collateral S1 and the second collateral S2 do not need to be distinguished from each other, but the financial institution may use the first collateral S1 as collateral at a stage with a defense (before the time T2).

  As a second pattern, the financial institution considers that the defense will be cut off at the time T2, and makes the first loan L1 a loan of a predetermined rate discounted from the amount of the loan, and the second loan L2 as the loan Loans up to the upper limit of the amount. For example, the financial institution performs the early collection of the loan amount at the time T2 and newly increases the amount. In this case, the first security S1 is security with a defense, and the second security S2 is security without a defense. The first guarantee G1 is the same as the first loan L1, and the second guarantee G2 is the same as the second loan L2.

  As a third pattern, the financial institution sets the second loan L2 in the first pattern up to the upper limit of the amount of the loan, but the guarantee association may not perform the second guarantee G2. That is, the financial institution may be able to lend the amount up to the maximum amount of the loan without guarantee by the guarantee association, considering that the payment of the loan has been confirmed due to the absence of the defense at the time T2.

  As a fourth pattern, the financial institution may change the amount of the second loan L2 in the first pattern up to the upper limit of the amount of the loan. That is, the financial institution may be able to change the amount of the second loan L2 without guarantee by the guarantee association.

  As a fifth pattern, the financial institution may make the first loan and the second loan without the first guarantee G1 and the second guarantee G2 by the guarantee association. In other words, financial institutions can take out loans without guarantees by the Guarantee Association, taking into account the reliability of electronically recorded receivables (eg, eliminating the risk of double transfer and the risk of losing creditors). It may be.

  At time T3, the payment by the ordering company is made, and the electronically recorded claims disappear.

  Hereinafter, a process performed by the electronically recorded receivables management system 10 during a period from when an order is placed by an ordering company and a delivery company to when payment is made by the ordering company will be described with reference to FIGS. 8 to 11.

  FIG. 8 is a flowchart showing an example of an ordering flow and a process of generating the electronically recorded claim data C with defense.

  It is preferable that the ordering company and the delivering company consult in advance about the contents of the order, the amount, the payment conditions, the use of the electronically recorded receivables management device 1, and the contents of the defense. In addition, it is preferable that the delivery company has received a notification of consent from the ordering company in advance and a notification of a possible loan from a financial institution.

  In step S101, the terminal 100 of the ordering company transmits order content data to the electronic contract system 102, for example.

  In step S102, the terminal 104 of the delivery company, for example, confirms the order content data input to the electronic contract system 102, and transmits data indicating that an order is received to the electronic contract system 102.

  In step S103, the electronic contract system 102 transmits the order data B obtained in steps S101 and S102 to the electronically recorded receivables management device 1. The electronically recorded bond management device 1 generates bond-related data D and the like based on the order data B. As described above, the electronically recorded receivables management device 1 acquires the ordering data B and the like by accessing from the terminal 100 of the ordering company and / or the terminal 104 of the delivering company without going through the electronic contract system 102. Is also good.

  In step S104, the electronically recorded receivables management device 1 may transmit the order data B to the device 106 of the electronically receivable recording organization.

  In step S105, the terminal 104 of the delivery company transmits a request to generate an electronically recorded claim with defense to the electronically recorded claim management device 1.

  Note that, when receiving the request for occurrence, the electronically recorded receivables management device 1 may transmit a consent request corresponding to the request for occurrence to the terminal 100 of the ordering company. Further, the electronically recorded receivables management device 1 may receive the order data B together with the occurrence request.

  In step S <b> 106, the terminal 100 of the ordering company transmits an occurrence consent corresponding to the occurrence request to the electronically recorded receivables management device 1.

  In step S107, the electronically recorded receivables management device 1 stores the consent data D9 including the consent to be received received from the terminal 100 of the ordering company in the storage device 7, and, among the receivable-related data D associated with the consent data D9, Data necessary for generating the recorded bond data C is read from the storage device 7 to generate electronically recorded claim data C with defense, and the request for generation and the generated electronically recorded claim data C with defense are transmitted to the device 106 of the electronic bond recording organization. Send to The electronically recorded bond management apparatus 1 transmits the request for generation and the data necessary for generating the electronically recorded bond data C with defense to the apparatus 106 of the electronic bond recording organization, and the apparatus 106 of the electronic bond recording organization transmits the request for generation. The electronically recorded claim data C with defense may be generated on the basis of the data required for generating the electronically recorded claim data C with defense.

  In step S108, the apparatus 106 of the electronic bond recording organization stores the electronically recorded bond data C with defense in the database 106A based on the received occurrence request and the electronically recorded bond data C with defense.

  In step S109, the device 106 of the electronic receivables recording agency sends a notification of completion of the generation of the electronically recorded receivables data C with defense to the electronically recorded receivables management device 1.

  In step S110, the electronically recorded receivables management device 1 transmits a notice of completion of the generation of the electronically recorded receivables data C with defense to the terminal 104 of the delivery company and the terminal 100 of the ordering company.

  FIG. 9 is a flowchart illustrating an example of a collateral setting flow, a loan execution flow, and a transfer process of the electronically recorded receivables data C with defense.

  In step S201, the terminal 104 of the delivery company transmits to the financial institution device 108 a loan application indicating that a loan is desired, for example, with the electronically recorded receivables with security as collateral.

  In step S202, the financial institution device 108 transmits a guarantee application for the loan application to the guarantee association device 110.

  In step S203, the financial institution performs a loan examination, the guarantee association performs a guarantee examination, and the financial institution apparatus 108 and the guarantee association apparatus 110 transmit the loan examination result and the guarantee examination result to the terminal 104 of the delivery company, respectively. Send. In the following, it is assumed that both the loan examination and the guarantee examination have passed.

  In step S204, when guaranteeing the loan, the device 110 of the guarantee association executes a process of issuing guarantee data or the like to the device 108 of the financial institution, for example.

  In step S205, a loan contract and a transfer security contract are executed between the terminal 104 of the delivery company and the device 108 of the financial institution.

  In step S206, the terminal 104 of the delivery company transmits the transferee data D7 indicating that the transferee is a specific financial institution and a transfer request for the electronically recorded claim data C with defense to the electronically recorded claim management device 1. . The electronically recorded receivables management device 1 recognizes the financial institution indicated by the transferee data D7 as the transferee based on the received transferee data D7. When receiving the transfer request, the electronically recorded receivables management device 1 may transmit an acceptance request corresponding to the transfer request to the device 108 of the financial institution.

  In step S207, the financial institution device 108 transmits the transfer approval corresponding to the transfer request to the electronically recorded receivables management device 1.

  In step S208, the electronically recorded receivables management device 1 stores the consent data D9 including the consent for transfer received from the device 108 of the financial institution in the storage device 7, and the transfer destination data D7 of the receivable-related data D associated with the consent data D9. Is read from the storage device 7 and a transfer request for the electronically recorded claim data C with defense is transmitted to the device 106 of the electronic claim recording organization together with the transfer destination data D7.

  In step S209, the device 106 of the electronic bond recording organization stores the transferred electronically recorded bond data C after transfer in the database 106A based on the transfer request and the transfer destination data D7 received from the electronically recorded bond management device 1. More specifically, the device 106 of the electronic bond recording organization updates the creditor data D2 of the electronically recorded bond data C stored in the database 106A with the transfer destination data D7.

  In step S210, the device 106 of the electronic bond recording organization transmits a transfer completion notification of the electronically recorded bond data C with defense to the electronically recorded bond management device 1.

  In step S211, when the electronically recorded receivables management device 1 receives the transfer completion notification from the electronically recorded receivables management device 1, at least one of the terminal 104 of the delivery company, the terminal 100 of the ordering company, and the device 108 of the financial institution. For one, a transfer completion notification of the electronically recorded claim data C with defense is transmitted. Note that, when the transfer of the electronically recorded receivables data C is completed, the electronically recorded receivables management device 1 may execute a charging process such as a facility usage fee or a fee to the delivering company. This billing process will be described in detail in a third embodiment described later.

  In step S212, the financial institution may execute the loan using the transferred electronically recorded receivables after the transfer as collateral.

  FIG. 10 is a flowchart illustrating an example of a delivery flow and a process of changing the electronically recorded bond data C. This change process includes a process for defending the electronically recorded claim with defense.

  In step S301, the delivery company performs delivery (or delivery) to the ordering company. In this case, the terminal 104 of the delivery company or the terminal 100 of the ordering company may transmit the delivery completion to the device 108 of the financial institution via the electronically recorded receivables management device 1.

  In step S302, the ordering company inspects the delivered product. In this case, the terminal 100 of the ordering company may transmit the acceptance completion to the terminal 104 of the delivering company or the device 108 of the financial institution via the electronically recorded receivables management device 1.

  In step S303, the terminal 104 of the delivery company inputs billing contents using the electronic contract system 102.

  In step S304, the electronic contract system 102 transmits the billing data indicating the billing content input in step S303 to the electronically recorded receivables management device 1. Note that the terminal 104 of the delivery company may input or transmit billing data to the electronically recorded receivables management device 1 without passing through the electronic contract system 102. In this case, the data processing unit 53 of the electronically recorded receivables management device 1 may have a function of taking in claim data in which the contents of the claim are described based on a predetermined format.

  In step S305, the electronically recorded receivables management device 1 transmits a notification indicating that the billing data has been received to the terminal 104 of the delivery company.

  In step S306, the terminal 104 of the delivery company transmits a request to change the electronically recorded claim data C with defense to the electronically recorded claim management device 1. The contents of the change include, for example, disconnection of the defense, change of the contents of the defense, and change of the amount of the receivable. More specifically, since the defense can be cut off when the delivery is performed, for example, the terminal 104 of the delivery company requests deletion of the defense content data D6. Further, the terminal 100 of the ordering company, the terminal 104 of the delivery company, and the device 108 of the financial institution can request to change the data included in the electronically recorded receivables data C to the extent that they have authority. For example, if there is a change in the billing amount (claims data D4), the terminal 100 of the ordering company, the terminal 104 of the delivering company, or the device 108 of the financial institution stores the changed claim amount data in the electronically recorded credit management device. Send to 1.

  In step S307, the terminal 100 of the ordering company transmits a change approval corresponding to the change request to the electronically recorded receivables management device 1.

  In step S308, the device 108 of the financial institution transmits, for example, a change approval corresponding to the change request to the electronically recorded receivables management device 1 after receiving the acceptance completion from the terminal 100 of the ordering company.

  In step S309, the electronically recorded receivables management device 1 stores the consent data D9 including the consent for change obtained in steps S307 and S308 in the storage device 7, and sends a request to change the electronically recorded receivables data C to the device of the electronic receivable recording institution. Send to 106. In addition, when there is data necessary for change among the bond-related data D associated with the consent data D9, the electronically recorded bond management device 1 reads out the data necessary for the change from the storage device 7, and reads the electronically recorded bond data. A request for change of C and data necessary for the change are transmitted to the device 106 of the electronic bond recording organization.

  In step S310, the device 106 of the electronic bond recording organization receives the change request, and changes the electronically recorded bond data C stored in the database 106A. Further, when the data required for the change is received together with the change request, the device 106 of the electronic bond recording organization changes the electronically recorded bond data C stored in the database 106A based on the data necessary for the change. Execute.

  In step S311, the device 106 of the electronic bond recording organization transmits a change completion notification of the electronically recorded bond data C to the electronically recorded bond management device 1.

  In step S312, the electronically recorded receivables management device 1 notifies at least one of the terminal 104 of the delivery company, the terminal 100 of the ordering company, and the device 108 of the financial institution of the completion of the change of the electronically recorded receivable data C. Send

  In step S313, the financial institution device 108 changes, for example, security information. More specifically, the change in the security information is, for example, a change from collateral security to qualified security.

  Note that the terminal 104 of the delivery company may transmit the change request in step S306 to the electronically recorded receivables management device 1 together with the delivery in step S301. That is, the terminal 104 of the delivery company may request the electronic record receivables management device 1 to disconnect the defense immediately after delivery.

  FIG. 11 is a flowchart showing an example of the loan repayment flow and the payment completion processing of the electronically recorded receivables data C.

  In step S401, the electronically recorded receivables management device 1 transmits a notice urging payment to the terminal 100 of the ordering company. The notification may be performed, for example, before a predetermined period of the payment date indicated by the payment date data D5.

  In step S402, the terminal 100 of the ordering company executes payment (transfer processing) to the financial institution device 108 indicated by the creditor data D2 based on the credit amount data D4.

  In step S403, the financial institution device 108 transmits a notification of the receipt of the price to the electronic credit recording institution device 106 and the electronically recorded credit management device 1.

  In step S404, the financial institution device 108 executes a process of, for example, transferring the remaining amount after collecting the principal and interest of the loan to the delivery company. In addition, the apparatus 108 of the financial institution may perform the processing when the payment is received as scheduled instead of the security.

  In step S405, the electronically recorded receivables management device 1 transmits the completion of the payment to the device 106 of the electronically receivable recording organization.

  In step S406, based on the received payment completion, the device 106 of the electronic bond recording institution executes a payment completion process of storing that the payment has been made for the electronically recorded bond data C corresponding to the payment completion. Note that the device 106 of the electronic receivables recording agency does not receive the payment completion from the electronically recorded receivables management device 1 and, when receiving the payment receipt notification in step S403, performs the payment completion process for the electronically recorded receivables data C. May be executed.

  In step S <b> 407, the device 106 of the electronic receivables recording agency sends a payment completion notification to the electronically recorded receivables management device 1.

  In step S408, the electronically recorded receivables management device 1 transmits a payment completion notification to at least one of the terminal 100 of the ordering company and the device 108 of the financial institution.

  Hereinafter, the processing in the case where the electronically recorded claim data C with defense is divided and assigned, and the electronically recorded claim data C_A and C_B after the division and transfer will be described in detail with reference to FIG.

  FIG. 12 is a flowchart illustrating an example of a division transfer process of the electronically recorded claim data C with defense according to the present embodiment, and illustrates a process executed by the processor 106 </ b> B of the apparatus 106 of the electronic claim recording agency.

  In step S601, the processor 106B of the apparatus 106 of the electronic bond recording organization sends, from the electronically recorded bond management apparatus 1, the identification data D1, which indicates the electronically recorded bond data C with defense to be divided and transferred, and the transfer amount data D8, The transfer destination data D7 is received, and the electronically recorded claim data C with defense stored in the database 106A is accessed based on the identification data D1.

  In step S602, the processor 106B adds identification data D1 and D1_B to the electronically recorded claim data C_A and C_B after the division transfer. For example, after the split transfer, the processor 106B assigns the same identification data D1 as the electronically recorded claim data C on which the split transfer is based to the electronically recorded claim data C_A of the split source, and transfers the transferred electronically recorded claim data C_B. To the newly generated identification data D1_B. It should be noted that new identification data may be generated as the identification data of the electronically recorded receivables data C_A as the division source instead of the same as the identification data D1.

  In step S603, the processor 106B sets the transferee data D7 to the creditor data D2_B of the electronically recorded bond data C_B to be transferred.

  In step S604, the processor 106B determines, based on the loan amount data D4 of the electronically recorded claim data C with defense stored in the database 106A and the received transfer amount data D8, the bond of the electronically recorded claim data C_A of the division source. Claim amount data D4_B of the amount data D4_A and the transferred electronically recorded claim data C_B are obtained. More specifically, the processor 106B calculates an amount obtained by subtracting the value of the transfer amount data D8 from the value of the bond amount data D4 included in the electronically recorded bond data C, which is the basis of the split transfer, into the electronically recorded bond data of the division source. The credit amount data D4_A of C_A is set, and the transfer amount data D8 is set as the bond amount data D4_B of the transferred electronically recorded bond data C_B.

  In step S605, the processor 106B copies the data that can be diverted from the electronically recorded bond data C, which is the basis of the split transfer, to the electronically recorded bond data C_A of the division source and the electronically recorded bond data C_B to be transferred. More specifically, the processor 106B converts the creditor data D2, the debtor data D3, the due date data D5, and the defense content data D6 of the electronically recorded receivable data C, which is the basis of the split transfer, into the electronically recorded receivable data The creditor data D2, debtor data D3, payment due date data D5, and defense content data D6 of CA are copied. Further, the processor 106B converts the obligor data D3, the due date data D5, and the defense content data D6 of the electronically recorded receivables data C, which are the basis of the split transfer, into the obligor data D3 of the transferred electronically recorded receivables data C_B, and the due date. Data D5 and defense content data D6 are copied.

  In step S606, the processor 106B stores the electronically recorded receivables data C_A and C_B in the database 106A. For example, the processor 106B stores the divided transfer completion notification and the identification data D1_B of the transferred electronically recorded receivables receivable data C_B with the electronically recorded receivables management. Transmit to the device 1.

  When receiving the split transfer completion notification and the identification data D1_B from the device 106 of the electronic bond recording organization, the electronically recorded bond management device 1 transmits the electronically recorded bond data C with defense stored in the storage device 7, Based on the data D1, the transfer amount data D8, the transferee data D7, and the received identification data D1_B, the electronic recording claim data C_A of the division source and the electronically recorded claim data C_B to be transferred are generated and stored in the storage device 7. Is also good.

The division transfer request may be realized, for example, by combining the division request and the transfer request. A specific example in a case where the division transfer is realized by a combination of the division request and the transfer request will be described.
First, the electronically recorded receivables management device 1 transmits a request for division, data on the amount to be divided and identification data to be divided to the device 106 of the electronic receivable recording organization.
The device 106 of the electronic credit recording organization receives the division request, the amount data to be divided, and the identification data of the division target, and based on the identification data of the division target, the electronically recorded receivable with defense to be divided stored in the database 106A. Data C is divided, and a plurality of electronically recorded receivables-with-defense data relating to the division are stored in database 106A. After the division processing, the apparatus 106 of the electronic bond recording organization transmits the division completion notification and the identification data of the electronically recorded claim data with defense newly generated by the division to the electronically recorded bond management apparatus 1. When receiving the division completion notification and the identification data newly generated by the division from the apparatus 106 of the electronic bond recording organization, the electronically recorded bond management device 1 deletes the electronically recorded bond data C with the defense stored in the storage device 7 from the storage unit 7. Also, the same division processing as described above is executed, and a plurality of defense-attached electronically recorded claim data relating to the division is stored in the storage device 7. This makes it possible to match the electronically recorded claim data with defense in the database 106A with the electronically recorded claim data with defense in the storage device 7.
Next, upon receiving the division completion notification from the device 106 of the electronic credit recording institution, the electronic record receivable management device 1 transmits the transfer request, the transfer destination data, and the identification data of the transfer target to the device 106 of the electronic receivable recording institution. .
The device 106 of the electronic credit recording organization receives the transfer request, the transfer destination data, and the identification data of the transfer target, accesses the database 106A based on the identification data, and obtains the bond of the electronically recorded loan data with defense corresponding to the identification data. Transfer processing for updating the user data with the received transfer destination data. After the transfer processing, the device 106 of the electronic bond recording organization transmits a transfer completion notification to the electronically recorded bond management device 1. When receiving the transfer completion notification from the device 106 of the electronic bond recording organization, the electronically recorded bond management device 1 also performs the above-mentioned defense-attached electronically recorded bond data stored in the storage device 7 and corresponding to the identification data to be transferred. A transfer process similar to the above is executed. Thereby, the electronically recorded bond data in the database 106A and the electronically recorded bond data in the storage device 7 can be matched.
The split transfer request may be realized, for example, by combining a request for changing the amount of credit data with respect to the electronically recorded claim data C serving as a basis for the split transfer and a request for generating the transferred electronically recorded claim data C_B. In this case, the generation request may be transmitted from the generation request unit 52A of the electronically recorded bond management device 1 to the device 106 of the electronic bond recording organization. When the contents of the electronically recorded claim data C_A and / or the transferred electronically recorded claim data C_B are changed at the time of the division, the change request unit 52B of the electronically recorded claim management device 1 transmits the electronically recorded claim device. A change request may be transmitted to 106.

  In the split transfer, first, the electronically recorded bond data C, which is the basis of the split transfer, is divided into a plurality of electronically recorded bond data C_A and C_B by a division request, and then a change request for the plurality of electronically recorded bond data C_A and C_B ( This may be realized by transmitting a change in the name of the creditor or a change in the amount of the credit.

  As described above, the divisional transfer of the electronically recorded claim data C with defense can be realized by appropriately selecting or combining a division request, a transfer request, a change request, an occurrence request, and the like.

  In the present embodiment described above, the electronically recorded receivables management device 1 obtains, from the terminal 100 of the ordering company, the terminal 104 of the supplier, or the electronic contract system 102, the creditor data D2 and the debtor data relating to the electronically recorded receivables with defense. D3, receivable amount data D4, due date data D5, and defense content data D6 indicating that payment is made after delivery, inspection, or delivery are received. The electronically recorded receivables management device 1 generates the electronically recorded receivables data C with a defense when receiving the consent corresponding to these data from the terminal 100 of the ordering company, the terminal 104 of the delivery company, or the electronic contract system 102. Then, it transmits the electronically recorded claim data C with defense and the request for occurrence to the device 106 of the electronic claim recording organization. The device 106 of the electronic bond recording agency stores the electronically recorded claim data C with defense in the database 106A based on the occurrence request received from the electronically recorded bond management device 1 and the electronically recorded claim data C with defense. Thereby, the electronically recorded bond management system 1 can generate the electronically recorded bond data C corresponding to the electronically recorded bond with defense from the ordering stage. Therefore, the financial institution can lend to the delivery company from the ordering stage as a collateral using the electronically recorded receivable with defense regarding the electronically recorded receivables data C. For example, the convenience of the electronically recorded receivables to the delivering company and the financial institution can be improved. Can be improved.

  In the present embodiment, the electronically recorded claim management device 1 transmits a defense cut request to the electronically recorded claim data C relating to the electronically recorded claim with defense after delivery, acceptance, or delivery to the device 106 of the electronically receivable recording organization, The defense disconnection notification can be received from the credit recording institution device 106 and the defense disconnection notification can be transmitted to the financial institution device 108 or the like. As a result, the financial institution can increase the loan amount after the defense is cut off, and can improve the convenience of the electronically recorded receivables for, for example, the delivering company and the financial institution.

  In the present embodiment, when the electronically recorded receivables with a defense are divided and transferred, the electronically recorded receivables management device 1 transmits the divisional transfer request and necessary data to the device 106 of the electronically receivable recording organization, and records the electronically receivables. The institutional device 106 divides the electronically recorded claim data C stored in the database 106A into the electronically recorded claim data C_A and the electronically recorded claim data C_B while maintaining the defense content data D6. . Then, the device 106 of the electronic bond recording organization transfers at least one of the electronically recorded bond data C_A with defense and the electronically recorded bond data C_B with defense and stores it in the database 106A. As a result, the electronically recorded receivables with a defense can be divided and transferred, and a more convenient and flexible financial service than paper bills can be provided.

  In the present embodiment, the electronically recorded receivables management device 1 stores the data of the approved part of the order data B in the storage device 7 in order to comply with the Subcontract Act. The electronically recorded receivables management device 1 compares the order data B and / or the receivable-related data D with the condition data E to determine whether or not the transaction between the ordering company and the delivery company complies with the Subcontract Act. can do. Under the Subcontracting Law, the ordering company is obliged to prepare an order document and place an order with the subcontracting company (delivery company), and to prepare a supplementary document when there is a change from the order contents. I have. The purchase order and supplementary documents are required to be kept for at least two years. In the present embodiment, the generation or change of the electronically recorded receivables data C requires the consent (that is, consent) of both the ordering company and the delivering company. The electronically recorded receivables management device 1 stores the order data B and the receivable-related data D as alternatives to the order document and the supplementary document, and can be read out as necessary. Therefore, in this embodiment, the order data B and the receivable-related data D can be used as a substitute for an order document and a supplementary document that comply with the subcontract law, and can comply with the subcontract law at low cost. The convenience of the company can be improved.

  In the present embodiment, the due date data D5 included in the electronically recorded receivables data C of the device 106 of the electronic receivables recording agency can be changed by the change request. As a result, early delivery / acceptance or delivery delay / acceptance can be easily dealt with.

In the present embodiment, the transfer request changes the creditor data D2 included in the defense-attached electronically recorded claim data C of the device 106 of the electronic claim recording organization, and changes the electronically recorded claim relating to the defense-attached electronically recorded claim data C. For example, it can be transferred to a financial institution, a guarantee association, or any third party. Thus, for example, it is possible to easily cope with a case where the delivery company goes bankrupt before delivery, acceptance, or delivery.
In the present embodiment, the electronically recorded receivables data C is generated by the electronically recorded receivables management apparatus 1, and the electronically recorded receivables data C is transferred to the electronically recorded receivables data C, the divisional transfer, the defense and the like are performed by the electronically receivable recording organization This is executed by the device 106. As a result, the processing can be dispersed, the processing efficiency can be improved, and the functions of the electronically recorded receivables management device 1 and the device of the electronically receivable recording organization 106 can be used efficiently.

  Note that, as described above, the electronically recorded receivables management device 1 stores a plurality of template data 123_1 to 123_n that are candidates for the defense content data D6 in the storage device 7, and provides the user with any of the template data 123_1 to 123_n. The defense content data D6 may be generated by selecting at least one, and the defense content data D6 may be generated by allowing the user to edit the selected template data after selecting the template data. The data input in the input field may be used as the defense content data D6. In this case, the data processing unit 53 of the electronically recorded receivables management device 1 provides the template data 123_1 to 123_n to the access source according to the user's access, further edits the selected template data, and inputs the template data into the input field. Provide a user interface that prompts the user. The data processing unit 53 stores in the storage device 7 defense content data D6 obtained by selection, editing, and input by the user. Thereby, even when the delivery company or the ordering company is not accustomed to creating a defense, the defense content data D6 can be easily generated, and the convenience for the user is improved.

  In the above embodiments, the exchange of the order and the consent are merely examples, and the source of the order and the source of the consent can be changed as appropriate.

  In each of the above embodiments, the defense of the electronically recorded receivable with a defense is cut off, for example, in response to delivery from the delivery company to the ordering company, completion of acceptance by the ordering company, or completion of delivery.

(Third embodiment)
In the present embodiment, a charging process, a loan determination process, and a user interface provided by the electronically recorded receivables management device 1 will be described. In the present embodiment, the above-mentioned delivery company is referred to as an ordering company.
Note that, in the present embodiment, a case will be described as an example in which a charging process is performed on an ordering company in accordance with transfer and division transfer of the electronically recorded claim data C with defense before the defense is cut off. Similar charging processing may be performed on the order receiving company in accordance with the transfer and the split transfer of the electronically recorded receivable data.

  FIG. 13 is a block diagram illustrating an example of a configuration of the electronically recorded receivables management device 1 according to the present embodiment. In FIG. 13 and its description, portions different from those in FIGS. 2 and 4 will be mainly described, and description of the same portions will be omitted.

The storage device 7 of the electronically recorded receivables management device 1 further stores user master data 300 (corresponding to the user data U), screen data H1 to Hm, billing data 301 on the ordering company, and credit line data 302. The storage device 7 may further store the electronically recorded bond data F1 to Fk and the history data CH1 to CHk.
The user master data 300 includes, for example, company identification data 300a for identifying a company, user identification data 300b for identifying a user, and user attribute data 300c indicating whether the user is a person in charge or an administrator. Associated. For example, the person in charge is permitted to perform operations except for consent. For example, the administrator is permitted to perform an operation including consent.
The screen data H1 to Hm are, for example, HTML (Hyper Link Markup Language) format data. The screen data H1 to Hm are transmitted from the electronically recorded receivables management device 1 to the terminal 100 of the ordering company, the terminal 104 of the ordering company, or the device 108 of the financial institution. The user interface is provided by being displayed by the browser 104 used in the device 104 or the device 108 of the financial institution. The screen data H1 is, for example, login screen data. The screen data H2 is, for example, data relating to a menu. A display example of the screen data H2 will be described later with reference to FIG.

  The billing data 301 associates the identification data 301a of each electronically recorded receivables data, the identification data 301b of the ordering company, and the billing amount 301c for the ordering company.

  The loan facility data 302 includes financial institution identification data 302a, ordering firm identification data 302b, ordering firm identification data 302c, an individual loan facility 302d set by the financial institution for the ordering firm, and an ordering firm. Associates the order amount 302e corresponding to the order amount received from the ordering company with the loan execution amount 302f which is the amount financed by the financial institution to the order receiving company. The individual financing line 302d is, in other words, the financing possible (upper limit) amount. Here, the identification data 302a of the financial institution, the identification data 302b of the ordering company, the identification data 302c of the ordering company, the order amount 302e, and the like are acquired by the processor 5, for example, based on the above-mentioned order content data or ordering data B. You may. Note that the order amount 302e may be omitted from the loan frame data 302.

  The processor 5 of the electronically recorded receivables management device 1 executes the program P stored in the storage device 7, and executes a user management unit 51, an interface unit 303, a loan determination unit 304, a billing unit 305, an API (Application Programming Interface) unit. 306 is realized.

  The user management unit 51 of the electronically recorded receivables management device 1 transmits screen data H1 for login to the terminal 100 of the ordering company, the terminal 104 of the order receiving company, or the device 108 of the financial institution.

The terminal 100 of the ordering company, the terminal 104 of the ordering company, or the device 108 of the financial institution displays the screen data H1 using the browser B or the like, for example.
The terminal 100 of the ordering company, the terminal 104 of the ordering company, or the device 108 of the financial institution acquires the company identification data 300a and the user identification data 300b based on the operation of the user, and acquires the acquired company identification data 300a and the user identification. The data 300b is transmitted to the electronically recorded receivables management device 1.

  The user management unit 51 of the electronically recorded receivables management device 1 receives the company identification data 300a and the user identification data 300b from the terminal 100 of the ordering company, the terminal 104 of the order receiving company, or the device 108 of the financial institution, and Access the user master data 300 stored in the.

  The user management unit 51 determines whether to permit the user to log in based on the received user identification data 300b and the user master data 300 stored in the storage device 7.

  When the login is permitted, the user management unit 51 converts the user attribute data 300c of the user based on the received company identification data 300a, the received user identification data 300b, and the user master data 300 stored in the storage device 7. Recognize and recognize whether the user is an administrator or a person in charge from the user attribute data 300c of the user.

  The user management unit 51 retrieves the electronically recorded bond data C and the history data CH relating to the company identification data 300a from the electronically recorded bond data F1 to Fk and the history data CH1 to CHk. As a specific example, the user management unit 51 selects, from the electronically recorded credit data F1 to Fk, electronically recorded credit data including the received company identification data 300a as creditor data or debtor data, and selects the selected electronic record. Select the historical data corresponding to the receivables data.

  The user management unit 51 generates an electronically recorded bond list 306 (shown in FIG. 17 described later) including the electronically recorded bond data C relating to the received company identification data 300a.

  Based on the user attribute data 300c and the retrieved electronically recorded receivables data C and history data CH, the user management unit 51 provides an approval waiting list 307 (see FIG. 17 described later) indicating a case waiting for approval by the logged-in user. Is generated).

  The user management unit 51 selects a designation unit (button that can be pressed) corresponding to an operation that can be executed by the user.

  When the login is permitted, the interface unit 303 of the electronically recorded receivables management device 1 transmits the screen data H2 to the terminal 100 of the ordering company, the terminal 104 of the order receiving company, or the device 108 of the financial institution, to which the login is permitted, as appropriate. To Hm.

  For example, as described later with reference to FIG. 17, the interface unit 303 includes an approval waiting list 307, an electronically recorded bond list 306, and menu tables 308 and 309 including a designation unit selected for the user. The screen data H2 is generated, and the screen data H2 is transmitted to the terminal 100 of the ordering company, the terminal 104 of the ordering company, or the device 108 of the financial institution.

  For example, as described later with reference to FIG. 21, the interface unit 303 transmits screen data H3 for the financial institution to execute the consent for the transfer record to the device 108 of the financial institution.

  The terminal 100 of the ordering company, the terminal 104 of the ordering company, or the device 108 of the financial institution accepts a user operation (for example, selection, designation, input of data, etc.), and according to the operation, data, request, or The consent is transmitted to the electronically recorded receivables management device 1.

  The processor 5 of the electronically recorded receivables management device 1 receives data, a request, or a consent from the terminal 100 of the ordering company, the terminal 104 of the order receiving company, or the device 108 of the financial institution, and based on the data or the request, The management processing of the electronically recorded bond data C described in each of the embodiments is executed.

  The loan determining unit 304 of the electronically recorded receivables management device 1 accesses the loan facility data 302 at an arbitrary timing, and the loan to the order receiving company satisfies the loan permission condition, and the financial institution makes a loan to the order receiving company (creditor). Determine whether it is possible.

  The arbitrary timing may be, for example, the timing at which the loan determination unit 304 receives the loan determination request, the execution timing of the processing for generating the electronically recorded receivables with a defense (when the generation consent 130 is received), or the electronic record with the defenses. The execution timing of the transfer process or the split transfer process regarding the receivables (when the transfer approval or the split transfer approval 135 is received) may be used.

Specifically, the loan determination unit 304 determines the loan amount for determining a loan based on the electronically recorded receivables, the financial institution identification data 302a, the ordering company identification data 302b, the ordering company identification data 302c, and the storage device 7. Based on the loan facility data 302 stored in the financing facility, the provisional loan execution amount assuming that a new loan has been executed for the order receiving company is equal to or less than the order receipt amount 302e, and It is determined whether the value is equal to or less than the value. Here, the provisional loan execution amount is, for example, an addition value of the loan amount and the loan execution amount 302f of the loan frame data 302. The loan amount may be, for example, the bond amount indicated by the bond amount data D4.
Then, when the provisional loan execution amount is equal to or less than the order amount 302e and equal to or less than the individual loan amount 302d, the loan determination unit 304 permits a new loan and is included in the loan amount data 302. The loan amount 302f is updated with the provisional loan amount.
On the other hand, if the provisional loan execution amount exceeds the order amount 302e or exceeds the individual loan amount 302d, the loan determination unit 304 rejects the loan.

In the present embodiment, the loan determination unit 304 executes the above loan determination processing at the execution timing of the processing for generating an electronically recorded claim with a defense, and if the loan is not permitted, the generation of the electronically recorded claim with a defense is stopped. Is also good.
Further, even if the loan determination unit 304 does not receive the consent to generate 130, the loan determination unit 304 may execute a process of generating an electronically recorded receivable with a defense if the loan is permitted.
Similarly, the loan determination unit 304 executes the above-described loan determination processing at the execution timing of the transfer or split transfer of the electronically recorded receivable with a defense, and if the loan is not permitted, the transfer or split of the electronically recorded receivable with a defense is performed. The transfer may be discontinued.
In addition, even if the loan determination unit 304 does not receive the transfer consent or the split transfer consent 135, if the loan is permitted by the loan determination unit 304, the loan determination unit 304 performs the transfer process or the split transfer process of the electronically recorded receivable with defense. You may.

  Thereby, the electronically recorded receivables management device 1 can control the loan execution amount 302f to be within the range not exceeding the individual loan amount 302d and not exceeding the order amount 302e.

  The charging unit 305 of the electronically recorded receivables management device 1 receives the transfer approval for the electronically recorded receivables data C from the device 108 of the financial institution or the transfer completion notification from the device 106 of the electronically receivable recording institution. Then, the accounting data 301 is accessed based on the identification data D1 of the electronically recorded receivables data C to be transferred, and the accounting amount 301c associated with the identification data 301a corresponding to the identification data D1 is updated.

The charging unit 305 may charge the ordering company based on, for example, a fixed usage fee or another criterion.
As an example, the charging unit 305 may calculate the usage fee based on the loan amount, the loan period, and the usage fee rate, and may add the calculated usage fee to the charging amount 301c of the charging data 301. For example, the loan amount is P, the usage fee rate (annual rate) is R%, and the loan period is T days. In this case, the charging unit 305 calculates usage fee = P × (R / 100) × (T / 365). Thus, the usage fee can be changed according to the loan period, and the usage fee can be increased as the loan period becomes longer. The contracting company pays a usage fee according to the loan period.

FIG. 14 is a data structure diagram showing an example of the credit line data 302. In the credit line data 302, the individual credit line 302d is set in accordance with the credit of the ordering company.
As described above, the credit line data 302 includes the identification data 302a of the financial institution, the identification data 302b of the ordering company, the identification data 302c of the ordering company, and the individual credit line set by the financial institution for the ordering company. 302d, the order amount 302e that the ordering company has received from the ordering company, and the loan execution amount 302f that the financial institution has financed the ordering company with each other.

The loan determination unit 304 determines that the added value, which is the sum of the loan amount 302f of the loan amount data 302 and the loan amount to be newly provided, is equal to or less than the individual loan amount 302d and equal to or less than the order amount 302e. It is determined that financing is possible. When it is determined that the loan is possible, the loan determining unit 304 updates the loan amount 302f of the loan frame data 302 with the added value.
The loan determining unit 304 determines that the sum of the loan execution amount 302f and the loan amount to be newly provided in the loan amount data 302 is less than the individual loan amount 302d or less than the order amount 302e. Judge that loan is not possible.

  FIG. 15 is a flowchart illustrating an example of a process of generating electronically recorded claim data C with defense, which is executed by the electronically recorded claim management device 1 according to the third embodiment. In the process of FIG. 15, step S1504 may be omitted.

  In step S1501, the processor 5 of the electronically recorded receivables management device 1 transmits the electronically recorded receivables data C with defense from any of the ordering company terminal 100, the ordering company terminal 103, the financial institution device 108, and the electronic contract system 102. Data required for generation (for example, creditor data D2, debtor data D3, credit amount data D4, due date data D5, and defense content data D6) are received.

  In step S1502, the processor 5 accesses the credit line data 302, calculates an added value that is the sum of the loan amount 302f and the loan amount to be newly loaned when the loan is permitted, and calculates the added value individually. It is determined whether it is less than or equal to the credit line 302d and less than or equal to the order amount 302e.

  If the added value is not equal to or less than the individual credit line 302d or is not equal to or less than the order amount 302e (if financing is not possible), the processor 5 determines in step S1503 that the financing is not permitted in the electronically recorded claim data C with defense. The data necessary for generation is transmitted to the terminal of the transmission source, and the processing is thereafter terminated.

  If the added value is equal to or less than the individual credit line 302d and equal to or less than the order amount 302e (in the case of loan permission), in step S1504, the processor 5 sets the terminal 100 of the ordering company, the terminal 103 of the ordering company, and the device of the financial institution. 108, receiving an occurrence approval 130 from any of the electronic contract systems 102.

  In step S1505, the processor 5 updates the loan execution amount 302f of the credit line data 302 with the added value.

  In step S1506, the processor 5 generates the identification data D1 and generates the electronically recorded claim data C with defense based on the generated identification data D1 and the data necessary for generating the received electronically recorded claim data C with defense. I do. Note that the identification data D1 may be generated not by the processor 5 but by the processor 106B of the device 106 of the electronic credit recording agency. In this case, the electronically recorded claim data C with defense generated by the processor 5 may include temporary identification data or may not include identification data. Further, the processor 106B of the device 106 of the electronic bond recording agency may transmit the generated identification data D1 to the processor 5 of the electronically recorded bond management device 1.

  In step S1507, the processor 5 transmits the electronically recorded bond data C with defense and the generation request 131 to the device 106 or the proxy device 111 of the electronic bond recording organization.

  In step S <b> 1508, the processor 5 stores the defense-recorded electronically recorded claim data C in the storage device 7 when receiving the occurrence completion notification from the device 106 or the proxy device 111 of the electronic bond recording agency.

  FIG. 16 is a flowchart illustrating an example of transfer and billing processing of the electronically recorded claim data C with defense, which is executed by the electronically recorded claim management device 1 according to the third embodiment. The same processing and billing processing as the transfer may be applied to the split transfer. In the process of FIG. 16, step S1604 may be omitted.

  In step S1601, the processor 5 of the electronically recorded receivables management device 1 receives the designation data 132 for designating the electronically recorded receivables-with-defense data C to be transferred and the transfer destination data D7.

  In step S1602, the processor 5 accesses the credit line data 302, calculates an added value that is the sum of the loan amount 302f and the loan amount to be newly loaned when the loan is permitted, and calculates the added value as the loan amount. It is determined whether or not the amount is equal to or less than the possible amount 302d and equal to or less than the order amount 302e.

  If the added value is not equal to or less than the individual credit line 302d or is not equal to or less than the order amount 302e, the processor 5 determines in step S1603 that the loan is not permitted, and transmits the data required for transfer of the designated data 132 and the like. , And then the process ends.

  When the added value is equal to or less than the individual credit line 302d and equal to or less than the order amount 302e, the processor 5 receives the transfer consent from the financial institution device 108 in step S1604.

  In step S1605, the processor 5 updates the loan amount 302f of the loan frame data 302 with the added value.

  In step S1606, the processor 5 transmits the transfer request, the designation data 132, and the transfer destination data D7 to the device 106 of the electronic bond recording organization. Then, the device 106 of the electronic bond recording organization receives the transfer request, the designated data 132, and the transfer destination data D7, accesses the database 106A, and includes the electronically recorded bond data including the identification data D1 corresponding to the designated data 132. The creditor data D2 of C is updated to the creditor data D10 corresponding to the transferee data D7. Then, the device 106 of the electronic bond recording organization transmits a transfer completion notice to the electronically recorded bond management device 1.

  In step S1607, the processor 5 receives the transfer completion notification from the device 106 of the electronic credit recording agency.

  In step S1608, the processor 5 accesses the storage device 7 and converts the creditor data D2 of the electronically recorded credit data C including the identification data D1 corresponding to the designated data 132 into the creditor data D10 corresponding to the transfer destination data D7. Update. This makes it possible to match the content of the electronically recorded bond data in the storage device 7 of the device of the electronic bond recording agency with the content of the electronically recorded bond data in the database 106A of the device of the electronic bond recording agency.

  In step S1609, the processor 5 accesses the billing data 301 in the storage device 7 and executes a billing process for updating the billing amount 301b associated with the identification data D1 of the electronically recorded claim data C with defense.

FIG. 17 is a screen diagram illustrating a display example of screen data H2 related to a menu.
When the screen data H2 is displayed by the browser B operating on the terminal 100 of the ordering company, the terminal 104 of the ordering company, or the device 108 of the financial institution, the screen shown in FIG. 17 is displayed.

  The screen data H2 includes an approval waiting list 307 indicating a case waiting for approval by the logged-in user, an electronically recorded bond list 306, a menu table 308, and a menu table 309.

  Below the waiting list for approval 307, the electronically recorded bond list 306 is arranged. Below the electronically recorded bond list 306, a menu table 308 is arranged.

In the menu table 308, the items of "1 order registration", "2 occurrence record", "3 transfer record", "4 change record (defense cut)", and "5 payment record" are arranged in the horizontal direction, and "order company" is arranged in the vertical direction. Items for "ordering companies" and "financial institutions" are listed. The numbers and positions of “1 Order Registration”, “2 Occurrence Record”, “3 Transfer Record”, “4 Change Record (Defense Disconnect)”, and “5 Payment Record” correspond to the order of various operations related to Electronically Recorded Claim Data C with Defense. I do.
Note that, in the menu table 308, the item of "5 payment record" may be omitted.

  In the menu table 308, various operations (designating parts such as buttons) are arranged in association with respective items. Among the operations arranged in the menu table 308, the operations permitted for the user specified by the user management unit 51 and the operations related to the specified user are displayed in a selectable or designable state. You. The state that can be selected or specified is, for example, a state that is displayed in a specific color, an emphasized state, or the like. The user recognizes the operation that can be selected or specified by himself / herself among the operations included in the menu table 308. can do.

  More specifically, a designation part A0 for selecting (for example, pressing) “occurrence” at a position corresponding to the “ordering company” column and corresponding to the “2 occurrence record” column, and “accept” Is specified. When the designation unit A0 or A1 is designated, the terminal 100 of the ordering company transmits information indicating that the designation unit A0 or A1 has been designated to the interface unit 303 of the electronically recorded receivables management device 1. The interface unit 303 transmits screen data H4 or H5 for executing generation or acceptance of an electronically recorded receivable to the terminal 100 of the ordering company in accordance with the information indicating that the designation unit A0 or the designation unit A1 has been designated. I do.

  In the position corresponding to the column of "ordering company" and in the column of "4 Change record (defense cut)", a designation section A18 for selecting "change" and a designation for selecting "accept" The part A2 is arranged. When the designation unit A18 or A2 is designated, the terminal 100 of the ordering company transmits information indicating that the designation unit A18 or A2 is designated to the interface unit 303 of the electronically recorded receivables management device 1. The interface unit 303 transmits the screen data H6 or H7 for executing the defense or the acceptance of the electronically recorded claim to the terminal 100 of the ordering company in accordance with the information indicating that the designation unit A18 or A2 has been designated. .

  At a position corresponding to the column of “order receiving company” and corresponding to the column of “1 order registration”, a designation section A3 for selecting “order registration” is arranged. When the designation section A3 is designated, the terminal 104 of the order receiving company transmits information indicating that the designation section A3 has been designated to the interface section 303 of the electronically recorded receivables management device 1. The interface unit 303 transmits screen data H8 for executing ordering registration to the terminal 104 of the order receiving company according to the information indicating that the specifying unit A3 has been specified.

  A designation part A4 for selecting "occurrence" and a designation part A5 for selecting "accept" are arranged at positions corresponding to the "order receiving company" column and the "2 occurrence record" column. Is done. When the designation unit A4 or A5 is designated, the terminal 104 of the order receiving company transmits information indicating that the designation unit A4 or A5 is designated to the interface unit 303 of the electronically recorded receivables management device 1. The interface unit 303 transmits screen data H9 or H10 for executing generation or acceptance of an electronically recorded receivable to the terminal 104 of the receiving company in accordance with the information indicating that the specifying unit A4 or A5 has been specified.

  A designation part A6 for selecting "transfer" and a designation part A7 for selecting "accept" are arranged at positions corresponding to the "order receiving company" column and the "3 transfer record" column. Is done. When the designation unit A6 or A7 is designated, the terminal 104 of the order receiving company transmits information indicating that the designation unit A6 or A7 has been designated to the interface unit 303 of the electronically recorded receivables management device 1. The interface unit 303 transmits screen data H11 or H12 for executing the transfer or acceptance of the electronically recorded receivable to the terminal 104 of the receiving company in accordance with the information indicating that the specifying unit A6 or A7 has been specified.

  A designation section A8 for selecting "change" and a designation for selecting "accept" at a position corresponding to the column of "Order receiving company" and corresponding to the column of "4 Change record (defense cut)" The part A9 is arranged. When the designation unit A8 or A9 is designated, the terminal 104 of the order receiving company transmits information indicating that the designation unit A8 or A9 has been designated to the interface unit 303 of the electronically recorded receivables management device 1. The interface unit 303 transmits screen data H13 or H14 for executing the defense disconnection or acceptance of the electronically recorded receivable to the terminal 104 of the order receiving company in accordance with the information indicating that the specifying unit A8 or A9 has been specified. .

  At a position corresponding to the “financial institution” column and corresponding to the “3 transfer record” column, a designation unit A10 for selecting “accept” is arranged. When the designation unit A10 is designated, the device 108 of the financial institution transmits information indicating that the designation unit A10 has been designated to the interface unit 303 of the electronically recorded receivables management device 1. The interface unit 303 transmits the screen data H3 for executing the approval of the transfer record to the financial institution to the device 108 of the financial institution according to the information indicating that the specifying unit A10 has been specified. The screen data H3 for executing the transfer record approval by the financial institution will be described later with reference to FIG.

  A designation section A11 for selecting “accept” is arranged at a position corresponding to the “financial institution” column and corresponding to the “4 change record (defense disconnection)” column. When the designation unit A11 is designated, the financial institution device 108 transmits information indicating that the designation unit A11 has been designated to the interface unit 303 of the electronically recorded receivables management device 1. The interface unit 303 transmits screen data H15 for executing acceptance of the defense disconnection by the financial institution to the device 108 of the financial institution in accordance with the information indicating that the specifying unit A11 has been specified. When receiving the consent to defend the defense from the financial institution device 108, the electronically recorded receivables management device 1 transmits, for example, a change request for the purpose of defending the defense to the device 106 of the electronic credit recording institution.

  A designation section A12 for selecting "payment" and a designation section A13 for selecting "accept" are arranged in the "financial institution" column and in a position corresponding to the "5 payment record" column. You. When the designation unit A12 or A13 is designated, the device 108 of the financial institution transmits information indicating that the designation unit A12 or A13 has been designated to the interface unit 303 of the electronically recorded receivables management device 1. The interface unit 303 transmits screen data H16 or H17 for executing payment or consent to the device 108 of the financial institution in accordance with the information indicating that the specifying unit A12 or A13 has been specified.

“Consent” in the above menu table 308 may be omitted for simplification of the operation.
In the menu table 309, regarding the “other change record” for the change record other than the defense disconnection, the “payment date” and the “receivable amount” are arranged side by side. The menu table 309 is arranged below the menu table 308.

  In the menu table 309, a designation section A14 for selecting "change" and a designation section A15 for selecting "accept" are arranged at positions corresponding to the "payment date" column. The terminal 100 of the ordering company, the terminal 104 of the order receiving company, or the device 108 of the financial institution that has received the designation for the designation unit A14 or A15 transmits information indicating that the designation unit A14 or A15 has been designated to the electronically recorded loan management. The data is transmitted to the interface unit 303 of the device 1. The interface unit 303 displays screen data H18 or H19 for changing or accepting the due date of the electronically recorded receivable in response to the information indicating that the designation unit A14 or A15 has been designated. The information is transmitted to the terminal 100 of the designated ordering company, the terminal 104 of the order receiving company, or the device 108 of the financial institution.

  In the menu table 309, a designation part A16 for selecting "change" and a designation part A17 for selecting "accept" are arranged at positions corresponding to the column "money amount". The terminal 100 of the ordering company, the terminal 104 of the order-receiving company, or the device 108 of the financial institution that has been designated for the designated section A16 or A17 transmits information indicating that the designated section A16 or A17 has been designated to the electronically recorded loan management. The data is transmitted to the interface unit 303 of the device 1. The interface unit 303 displays screen data H20 or H21 for executing change or acceptance of the amount of the electronically recorded claim in response to the information indicating that the designation unit A16 or A17 has been designated. The information is transmitted to the terminal 100 of the designated ordering company, the terminal 104 of the order receiving company, or the device 108 of the financial institution.

  FIG. 18 is a screen diagram illustrating a display example of screen data 314 that accepts selection of operation as an ordering company or operation as an ordering company.

The terminal 104 of the receiving company accepts the selection of the receiving company operation 314A in the screen data 314 by the user of the receiving company, and transmits information indicating that the receiving company operation 314A has been selected to the electronically recorded receivable management device 1. Then, the electronically recorded receivables management device 1 generates screen data H2 including the menu table 308A for the receiving company, and transmits the generated screen data H2 to the terminal 104 of the receiving company.
On the other hand, the terminal 100 of the ordering company accepts the selection of the ordering company operation 314B in the screen data 314 by the user of the ordering company, and transmits information indicating that the ordering company operation 314B has been selected to the electronically recorded receivables management device 1. I do. Then, the electronically recorded receivables management device 1 generates the screen data H2 including the menu table 308B for the ordering company, and transmits the generated screen data H2 to the terminal 100 of the ordering company.

  FIG. 19 is a diagram illustrating an example of a menu table 308A displayed when an operation is received from the terminal 104 of the ordering company.

In FIG. 19, when an operation is received from the terminal 104 of the ordering company, the designation unit A0 to be selected by the terminal 100 of the ordering company is not displayed.
Further, in FIG. 19, the designation unit A18 to be selected by the terminal 100 of the ordering company is not displayed.

  FIG. 20 is a diagram illustrating an example of a menu table 308B displayed when an operation is received from the terminal 100 of the ordering company.

In FIG. 20, when an operation is received from the terminal 100 of the ordering company, the designation section A4 to be selected by the terminal 104 of the ordering company is not displayed.
In FIG. 20, the designation section A8 to be selected by the terminal 104 of the ordering company is not displayed.

  FIG. 21 is a screen diagram showing a display example of screen data H3 for allowing the financial institution to consent to the transfer.

  The interface unit 303 of the electronically recorded receivables management device 1 transmits the screen data H3 to the device 108 of the financial institution when the approval of the transfer record regarding the electronically recorded receivables data C is selected. The browser B of the financial institution device 108 displays the received screen data H3.

  The screen displayed based on the screen data H3 includes the contents 310 of the electronically recorded receivables data C to be transferred, the transfer contents 311, the loan amount setting area 312, the loan period setting area 313, the usage rate setting area 312, and the acceptance status 313. Including.

  The content 310 of the electronically recorded receivables data C includes, for example, the identification data D1 of the electronically recorded receivables data C to be transferred and the amount of receivables indicated by the receivables amount data D4.

The transfer contents 311 include, for example, a transferor indicating an ordering company and a transferee indicating a financial institution.
The loan amount setting area 312 is an area for setting the loan amount P.
The financing period setting area 313 is an area for setting the financing period T.
The usage rate setting area 314 is an area for setting the usage rate R. The usage fee rate R is used to calculate a usage fee for the transfer record when the transfer record is accepted by the financial institution. The usage fee rate R may be set in advance or may be changeable by a user of the financial institution. The changed usage rate R is transmitted from the financial institution device 108 to the electronically recorded receivables management device 1 after being accepted by the user of the financial institution, for example.

As described above, the charging unit 305 of the electronically recorded receivables management device 1, for example, determines the loan amount P set in the loan amount setting area 312, the loan period T (day) set in the loan period setting area 313, A charge is calculated based on the charge rate R (%) set in the charge rate setting area 312, and charging processing for charging the charge to the ordering company is executed.
Specifically, the charging unit 305 updates the charging amount 301c associated with the identification data 301a in the charging data 301 with the calculated usage fee.

  The approval status 315 indicates the execution status of the approval by the user of the financial institution.

  As described above, the interface unit 303 transmits the screen data H1 to Hm to the terminal 100 of the ordering company, the terminal 104 of the ordering company, or the device 108 of the financial institution, and the terminal 100 of the ordering company and the terminal 104 of the ordering company. Or various data, requests, consents, etc. from the financial institution device 108.

  On the other hand, the API unit 306 receives various data, requests, and consents from the terminal 100 of the ordering company, the terminal 104 of the order receiving company, the device 108 of the financial institution, or the electronic contract system 102 according to a predetermined API. Then, based on the received data, request, and consent, the above various processes (more specifically, for example, order registration, occurrence record, transfer record, change in defense cut, change in due date, change in receivable amount) , Browsing history data, etc.).

  The API unit 306 cooperates with the loan determination unit 304 to set the electronically recorded credit data C within the range of the individual credit line 302d set by the financial institution according to the credit of the ordering company and the range of the order amount 302e. Allow financing based on.

  In the present embodiment described above, the screen data H2 including the approval waiting list 307, the electronically recorded bond list 306, the menu table 308, and the menu table 309 are displayed on the terminal 100 of the ordering company, the terminal 104 of the ordering company, or the financial institution. Of the device 108 is displayed. Then, the interface unit 303 of the electronically recorded receivables management device 1 receives data, a request, and a consent from the terminal 100 of the ordering company, the terminal 104 of the order receiving company, or the device 108 of the financial institution.

  This allows the user to understand the flow and progress of the transaction and proceed with the operation. In addition, the user can check the electronically recorded receivables data C relating to the company to which the user belongs, and can quickly approve the case waiting for his / her approval.

  In the present embodiment, when the electronically recorded receivables data C is transferred, a charging process is performed on the ordering company. The loan amount P, the loan period T, and the utilization rate R used for charging can be set by screen data H3 displayed on the device 108 of the financial institution.

  In the present embodiment, when the electronically recorded receivables data C is transferred or split and transferred, the usage fee is charged to the ordering company, and when the transfer or split and transfer does not occur, the charging is not executed. One user can reduce the usage fee. Therefore, the number of users of the electronically recorded receivables management device 1 can be increased, user convenience can be improved, and usage fees can be stably collected.

  In the present embodiment, the electronically recorded receivables management device 1 provides APIs to the terminal 100 of the ordering company, the terminal 104 of the ordering company, the device 108 of the financial institution, and the electronic contract system 102. Thereby, the convenience of the electronically recorded receivables management device 1 is improved.

In this embodiment, the financial institution uses the loan amount within the range of the individual credit line 302d set by the financial institution according to the credit of the ordering company and within the range of the order amount 302e of the ordering company. You can decide whether to grant a loan.
In the present embodiment, instead of receiving the consent, when the loan is permitted, the generation, transfer, and split transfer of the electronically recorded receivable data may be automatically consent, and the process may proceed. As a result, operations such as consent to generate, consent to transfer, and consent to split transfer can be omitted, and the work load and management load of the ordering company, the order receiving company, and the financial institution can be reduced.

  The present invention is not limited to the embodiments described above, and each embodiment can be implemented by deleting, adding, or changing components. Further, by appropriately combining or exchanging the components of each embodiment, the present invention can be embodied in further different modes. As described above, even in the embodiment which is directly different from the embodiment described above, the same concept as the present invention is described as the embodiment of the present invention, and the description is omitted. I have.

  DESCRIPTION OF SYMBOLS 1 ... Electronic record receivables management apparatus, 10 ... Electronic record receivables management system, 100 ... Terminal of ordering company, 102 ... Electronic contract system, 104 ... Terminal of supplier company, 106 ... Equipment of electronic receivables record institution, 108 ... Financial institution Apparatus, 110: Guarantee Association apparatus, 111: Proxy apparatus, 5, 106B: Processor, 7, 106C: Storage device, 114: First receiving section, 115: Second receiving section, 54: Extracting section, 117 ... Generation requesting unit, 118: third receiving unit, 119: fourth receiving unit, 120: split transfer requesting unit, 121: defense disconnection requesting unit, 122: defense disconnection notifying unit, 3: memory, 51: user management unit , 52 request unit, 52A generation request unit, 52B change request unit, 52C transfer request unit, 52D payment completion unit, 53 data processing unit, 55 communication unit, D debt related data, D1, D1_B ... identification data, D2, D2_B ... creditor data, D3 ... debtor data, D4, D_4A, D_4B ... receivable amount data, D5 ... payment date data, D6 ... defense contents data, 130 ... 132: designation data, D7: transfer destination data, D8: transfer amount data, 135: split transfer acceptance, 136 ... split transfer request, 137 ... defense cutoff data, 138 ... defense cutoff approval, 139 ... defense cutoff request, 140, 141 … Notice of disconnection of defense, C, C_A, C_B, F1 to Fk… Electronically recorded claim data with defense, 123_1 to 123_n… Model data, D9… Acceptance data, E… Condition data, I… Data by case, P… Program, U ... user data, CH, CH1 to CHk ... history data, 142, 142B ... unique data, 143, 143B ... division source data, 14 .., 144B: Division number data, 51: User management unit, 303: Interface unit, 304: Loan determination unit, 305: Billing unit, 306: API unit, H1 to Hm: Screen data, 300: User master data, 300a: Company Identification data, 300b: user identification data, 300c: user attribute data, 301: billing data, 301a: identification data, 301b: identification data of the ordering company, 301c: billing amount, 302: loan facility data, 302a: identification of financial institution Data, 302b: identification data of the ordering company, 302c: identification data of the ordering company, 302d: individual loan facility, 302e: order amount, 302f: loan execution amount.

Claims (10)

A storage device;
A processor that accesses the storage device and controls generation and transfer of electronically recorded bond data regarding the electronically recorded bond;
With
The processor comprises:
Receiving, from the first terminal, creditor data relating to the electronically recorded claim, debtor data, claim amount data, and due date data;
Receiving a consent from the second terminal indicating the consent of the occurrence of the electronically recorded receivable;
Upon receiving the accreditation, generating the electronically recorded receivable data including the identification data for the electronically recorded receivables, the creditor data, the debtor data, the receivable amount data, and the due date data. Then, the generated electronically recorded bond data and the generation request, the electronic bond recording organization device, or, to the proxy device provided in the preceding stage of the electronic bond recording organization device,
From the terminal of the creditor, receiving the identification data and the transferee data indicating the electronically recorded claim data to be transferred,
Receiving, from a device of the financial institution, a transfer consent indicating that the transfer is consent,
When the transfer consent is received, the identification data, the transfer destination data, and a transfer request for requesting transfer of the electronically recorded credit data stored in a database of the device of the electronic credit recording agency. , Transmitted to the device of the electronic credit recording agency or the proxy device,
Upon receiving the transfer consent, accessing the storage device that stores the identification data and the charge data that associates the creditor and the charge amount for the creditor with respect to the electronically recorded bond, and associates the identification data with the identification data. Updating the billing amount being
Information processing device. The electronically recorded receivables data is defense-equipped electronically recorded receivables data relating to electronically receivables with defense, which is generated in accordance with an order before delivery or acceptance.
The processor controls the generation, the transfer, and the defense disconnection of the defense-recorded electronically recorded receivable data,
The processor comprises:
From the first terminal, the creditor data, the debtor data, the loan amount data, the payment due date data, and the portion that has not been delivered or has not been received for the electronically recorded claim with defense Part receives the defense data indicating that the payment can be refused,
Receiving the consent from the second terminal indicating the consent of the generation of the electronically recorded claim with defense;
Upon receiving the consent to accrue, the identification data relating to the defense-recorded electronically recorded claim, the creditor data, the debtor data, the claim amount data, the due date data, and the defense content data. Generates the defense-recorded electronically recorded claim data, including the generated defense-recorded electronically recorded claim data and the generation request, and transmits the generated claim to the device of the electronic credit recording organization, or the proxy device,
From the terminal of the creditor, receiving the identification data and the transferee data indicating the defense-recorded electronically recorded claim data to be transferred,
Receiving the transfer consent from the financial institution device;
Upon receiving the transfer consent, the request for transferring the identification data, the transfer destination data, and the defense-attached electronically recorded claim data stored in the database of the apparatus of the electronic credit recording agency is provided. Transfer request and transmit to the device of the electronic credit recording agency or the proxy device,
Upon receiving the transfer consent, accessing the storage device and updating the billing amount associated with the identification data in the billing data;
The information processing device according to claim 1. The storage device further stores credit line data,
The loan facility data includes the identification data of the financial institution, the identification data of the ordering company regarding the electronically recorded receivables, the identification data of the ordering company, the individual loan facility of the ordering company, and the financial institution to the ordering company. With the loan disbursement amount of
The processor comprises:
The loan amount for determining a loan based on the electronically recorded receivables, the identification data of the financial institution, the identification data of the ordering company, the identification data of the ordering company, and the loan facility data stored in the storage device. And when the sum of the loan amount and the loan amount of the loan frame data is equal to or less than the individual loan frame, the loan is permitted and the loan amount of the loan frame data is added to the loan amount. Update with a value, reject the loan if the added value exceeds the individual credit line,
The information processing apparatus according to claim 1. The storage device further stores credit line data,
The loan facility data includes identification data of the financial institution, identification data of the ordering company regarding the electronically recorded receivables, identification data of the ordering company, individual loan facilities of the ordering company, and the ordering company from the ordering company. Correlating the received order amount and the loan execution amount from the financial institution to the order receiving company,
The processor comprises:
The loan amount for determining a loan based on the electronically recorded receivables, the identification data of the financial institution, the identification data of the ordering company, the identification data of the ordering company, and the loan facility data stored in the storage device. Based on the above, if the sum of the loan amount and the loan execution amount of the loan frame data is equal to or less than the order amount and equal to or smaller than the individual loan frame, the loan is permitted and the loan frame is Updating the loan execution amount of the data with the added value, and rejecting the loan if the added value exceeds the order amount or exceeds the individual credit line,
The information processing apparatus according to claim 1. The storage device further stores menu screen data that prompts the user to select the occurrence, the occurrence consent, the transfer, and the transfer consent,
The menu screen data includes:
A table in which the items of the occurrence and the transfer are arranged in the horizontal direction, and the ordering company, the ordering company, and the financial institution are arranged in the vertical direction,
A first designation unit for selecting the occurrence is arranged at a position corresponding to the order receiving company column and corresponding to the occurrence column,
A second designation unit for selecting the consent for occurrence is arranged at a position corresponding to the column of the ordering company and corresponding to the column of occurrence,
A third designation unit for selecting the transfer is disposed at a position corresponding to the order receiving company column and at a position corresponding to the transfer column,
A fourth designation unit for selecting the transfer consent is arranged at a position corresponding to the financial institution column and corresponding to the transfer column,
The processor comprises:
Transmitting the menu screen data stored in the storage device to the terminal of the ordering company, the terminal of the contractor, and the device of the financial institution;
The information processing device according to claim 1. The storage device further stores menu screen data that prompts the user to select the occurrence, the occurrence consent, the transfer, and the transfer consent,
The menu screen data includes:
A table in which the items of the occurrence and the transfer are arranged in the horizontal direction, and the ordering company, the ordering company, and the financial institution are arranged in the vertical direction,
A first designation unit for selecting the occurrence is arranged at a position corresponding to the ordering company column and corresponding to the occurrence column,
A second designation unit for selecting the consent for occurrence is arranged at a position corresponding to the column of the order receiving company and corresponding to the column of the occurrence,
A third designation unit for selecting the transfer is disposed at a position corresponding to the order receiving company column and at a position corresponding to the transfer column,
A fourth designation unit for selecting the transfer consent is arranged at a position corresponding to the financial institution column and corresponding to the transfer column,
The processor comprises:
Transmitting the menu screen data stored in the storage device to the terminal of the ordering company, the terminal of the order receiving company, and the device of the financial institution;
The information processing device according to claim 1. Computer
First receiving means for receiving, from the first terminal, creditor data relating to electronically recorded receivables, debtor data, receivable amount data, and due date data;
Second receiving means for receiving, from the second terminal, a consent to be generated indicating that the generation of the electronically recorded receivable is consent,
Upon receiving the accreditation, generating the electronically recorded receivable data including the identification data for the electronically recorded receivables, the creditor data, the debtor data, the receivable amount data, and the due date data. And a first transmitting unit that transmits the generated electronically recorded bond data and the generation request to a device of an electronic bond recording organization, or a proxy device provided in front of the device of the electronic bond recording organization.
Third receiving means for receiving, from a terminal of a creditor, the identification data indicating the electronically recorded claim data to be transferred and transferee data,
Fourth receiving means for receiving, from a device of the financial institution, a transfer consent indicating that the transfer is consent,
When the transfer consent is received, the identification data, the transfer destination data, and a transfer request for requesting transfer of the electronically recorded credit data stored in a database of the device of the electronic credit recording agency. Second transmission means for transmitting to the apparatus of the electronic credit recording agency or the proxy apparatus,
Upon receiving the transfer consent, accessing a storage device that stores the identification data and the charge data relating the creditor and the charge amount for the creditor related to the electronically recorded bond, and associated with the identification data. Charging means for updating the charging amount,
Program to function as. A first information processing device including a storage device,
A second information processing device communicably connected to the first information processing device and capable of accessing a database;
With
The first information processing device includes:
Receiving, from the first terminal, creditor data relating to electronically recorded receivables, debtor data, receivable amount data, and due date data;
Receiving, from the second terminal, a consent to consent to the generation of the electronically recorded receivable,
Upon receiving the accreditation, generating electronically recorded receivable data including identification data relating to the electronically recorded receivables, the creditor data, the debtor data, the receivable amount data, and the due date data. Transmitting an occurrence request for requesting generation of the electronically recorded claim data and the electronically recorded claim data to the second information processing apparatus,
From the terminal of the creditor, receiving the identification data and the transferee data indicating the electronically recorded claim data to be transferred,
Receiving, from a device of the financial institution, a transfer consent indicating that the transfer is consent,
When receiving the transfer consent, the identification data, the transfer destination data, and a transfer request for requesting transfer of the electronically recorded receivable data stored in the database of the second information processing device; To the second information processing device,
Upon receiving the transfer consent, accessing the storage device that stores the identification data and the charge data that associates the creditor and the charge amount for the creditor with respect to the electronically recorded bond, and associates the identification data with the identification data. Updating the billing amount being
The second information processing device includes:
From the first information processing device, when receiving the occurrence request and the electronically recorded claim data, storing the received electronically recorded claim data in the database,
When the transfer request, the identification data, and the transfer destination data are received from the first information processing apparatus, the bond of the electronically recorded bond data stored in the database and including the identification data is received. Updater data with the transferee data,
Information processing system. The first information processing device includes:
When receiving the identification data of the electronically recorded receivables data to be split and the split amount data from the terminal requesting the split, the split request, the identification data, and the split amount data are converted to the second data. Transmitted to the information processing device,
Receiving a division completion notification and post-division identification data as a response to the division request from the second information processing apparatus, storing the post-division identification data in the storage device,
The second information processing device includes:
When the division request, the identification data, and the division amount data are received from the first information processing device, the electronically recorded bond data stored in the database and indicated by the identification data; First electronically recorded claim data including first claim amount data indicating a value obtained by subtracting the value of the sectional amount data from the value of the claim amount data based on the sectional amount data; And storing second electronically recorded claim data including second claim amount data corresponding to the split amount data in the database;
Transmitting the division completion notification and the post-division identification data to the first information processing apparatus;
The first electronically recorded bond data includes the identification data, the creditor data, the debtor data, the first bond amount data, the due date data,
The second electronically recorded bond data includes the post-division identification data, the creditor data, the debtor data, the split amount data, and the due date data.
The information processing system according to claim 8. The first information processing device includes:
When receiving the identification data of the electronically recorded receivables data to be split and transferred, the transfer amount data, and the transfer destination data from the terminal requesting the split transfer, the split transfer request, the identification data, and the transfer amount Transmitting data and the transfer destination data to the second information processing apparatus,
Receiving, from the second information processing apparatus, a division transfer completion notification and post-transfer identification data as a response to the division transfer request, and storing the post-transfer identification data in the storage device;
The second information processing device includes:
When the split transfer request, the identification data, the transfer amount data, and the transfer destination data are received from the first information processing device, the split transfer request is stored in the database and indicated by the identification data. A first claim amount data including first claim amount data indicating a value obtained by subtracting a value of the transfer amount data from a value of the claim amount data based on the electronically recorded claim data, the transfer amount data, and the transfer destination data; Electronically recorded claim data, second electronically recorded claim data including the post-transfer identification data, post-transfer creditor data corresponding to the transferee data, and second claim amount data corresponding to the transfer amount data. Is stored in the database,
Transmitting the division transfer completion notification and the post-transfer identification data to the first information processing apparatus;
The first electronically recorded bond data includes the identification data, the creditor data, the debtor data, the first bond amount data, the due date data,
The second electronically recorded receivable data includes the post-transfer identification data, the post-transfer creditor data, the debtor data, the second receivable amount data, and the due date data.
The information processing system according to claim 8.

Images