JP7499808B2 - Information processing device, information processing method, and program - Google Patents

Description

The present invention relates to an information processing device, information processing method, and program that generate and transmit accrual record requests to electronic claim recording institutions for the automatic and early issuance of electronically recorded claims.

Electronically recorded claims are monetary claims that replace traditional bills and accounts receivable, and their use has expanded rapidly in recent years. Issuers of electronically recorded claims set the period and amount on a website prepared by each financial institution and submit requests to electronic claim recording institutions to record the accrual of electronically recorded claims at any time. Electronic claim recording institutions are equipped with a record master, and in response to requests for accrual recording, electronically record the contents of the requests in the record master, thereby generating electronically recorded claims.

Previously, a buyer would order goods from a supplier, the supplier would deliver the goods by the due date, and then the buyer would complete inspection of the delivered goods and then send an accrual record request to the electronic claim recording institution by entering the necessary information on each financial institution's website. Previously, the inspection work and the input work required to send the accrual record request took time, and depending on the company, it took a long time between completing inspection and entering the information.

The introduction of electronically recorded claims has lightened the administrative burden and cut costs compared to traditional bills, but there is also a growing need among users of electronically recorded claims to improve cash flow by converting electronically recorded claims into cash early. For example, there is a greater need for early cashing than ever before among companies that have just been established or that need sudden working capital. One known mechanism for responding to this need for early cashing is the scheme for electronically recorded claims with precedent conditions described in Patent Document 1.

Patent No. 6140909

Patent Document 1 discloses a scheme for early issuance of electronically recorded claims while reducing the risk to the issuer of the electronically recorded claims, but this scheme is not user-friendly in that its use is limited to specific electronically recorded claims and recording institutions. In addition, the scheme in Cited Document 1 requires administrative processing such as inputting necessary information to early issue electronically recorded claims, and is not a scheme that allows for automatic issuance of electronically recorded claims.

Previously, issuers of electronically recorded claims had to set the period and amount on a website prepared by each financial institution and make requests to record the accrual of electronically recorded claims at any time after completing the inspection of delivered goods. Because the completion of inspection and the request to record the accrual of electronically recorded claims were not automatically linked, it took time to send the request after the completion of inspection, and because multiple administrative procedures and operations were required, the risk of human error due to the manual intervention was unavoidable.

The present invention has been made to solve these problems, and aims to provide an information processing device, information processing method, and program that generate and transmit an accrual record request to an electronic claim recording institution for the automatic and early issuance of electronically recorded claims.

In order to solve the above problems, the information processing device according to the present invention comprises:
A communication unit for communicating with an external network, a storage unit, and a control unit,
The control unit is
receiving inspection information for the traded product from the creditor device via the communication unit, and updating the order data in the storage unit based on the inspection information;
in response to the order data in the storage unit being updated based on the inspection information, acquiring creditor information and debtor information associated with the creditor ID and debtor ID included in the order data from a user master in the storage unit, and calculating a credit amount based on the order information and the inspection information included in the order data;
and generating accrual record request data based on the acquired creditor information, the debtor information, and the calculated debt amount, and transmitting the data to a recording agency system.

The present invention can automatically generate request data for recording the accrual of electronically recorded claims based on the order information stored on the platform and transmit it to the recording agency system, thereby reducing the administrative workload of issuers of electronically recorded claims and lowering the risk of human error.

The present invention can automatically transmit accrual record request data to the recording agency system for electronically recorded claims, and more quickly than ever before, without the need to add specific information or conditions to electronically recorded claims, and therefore can be a means of contributing to the efficiency of fund-raising for many users as a general-purpose mechanism that can be used when issuing general electronically recorded claims.

A more detailed understanding of the embodiments disclosed herein can be had from the following description, taken in conjunction with the accompanying drawings, in which:
1 is a configuration diagram of an entire system including an information processing device 10. 1 is a system configuration diagram of an information processing device 10. 2 is a diagram illustrating an example of a data structure of a user master 106. FIG. 2 is a diagram illustrating an example of a data structure of a product master 107. FIG. 1 is a diagram illustrating an example of a data structure of order data 108. FIG. 10 is a diagram illustrating an example of the data structure of occurrence record request data 109. FIG. 10 is a diagram illustrating an example of a data structure of an early discount rate table 110. FIG. FIG. 2 is a flow diagram illustrating a process according to the first embodiment of the present invention. FIG. 11 is a flow diagram illustrating a process according to a second embodiment of the present invention. FIG. 11 is a flow diagram illustrating a process according to a third embodiment of the present invention. FIG. 13 is a flow diagram illustrating a process according to a fourth embodiment of the present invention. FIG. 13 is a flow diagram illustrating a process according to a fifth embodiment of the present invention.

(overall structure)
Fig. 1 is a configuration diagram of an entire system including an information processing device 10 according to the present invention. As shown in Fig. 1, the information processing device 10 is connected to a supplier device 11, a buyer device 12, a recordation agency system 13, and a financial institution server 14 so as to be able to communicate with each other. For the sake of explanation, Fig. 1 shows only one supplier device 11, one buyer device 12, one recordation agency system 13, and one financial institution server 14, but there may be a plurality of these.

The information processing device 10 provides an order placement platform as described in this specification to the supplier device 11 and the buyer device 12. Specifically, the information processing device 10 processes and stores order placement data relating to orders, deliveries, and settlements between the supplier (creditor) and the buyer (debtor) via an application of the order placement system, and broadcasts the order placement data to the supplier device 11 and the buyer device 12. The stored order placement data becomes data that constitutes the blockchain. The order placement data may be broadcast to any device or server other than the supplier device 11 and the buyer device 12.

The information processing device 10 generates and stores accrual record request data for electronically recorded claims using the order data, and transmits the accrual record request data to the recording agency system 13. More specifically, the information processing device 10 can log in to the recording agency system 13 using a login ID and password for issuing electronically recorded claims that have been lent to the user in advance at various times as described herein, and transmit accrual record request data for issuing electronically recorded claims to the recording agency system 13 using the claim amount and user information in the order data stored on the blockchain.

The information processing device 10 can receive and store information related to payment from the supplier device 11 and/or the buyer device 12. The information processing device 10 can use the information related to payment when generating the accrual record request data for electronically recorded claims.

The information processing device 10 can send a request to the financial institution server 14 of the financial institution that holds the supplier's account to transfer an amount equivalent to the security deposit from the supplier's account to the platform operator's account. The information processing device 10 can send a request to the financial institution server 14 of the financial institution that holds the supplier's account to transfer all or part of the security deposit from the platform operator's account to the supplier's account. The information processing device 10 can also send a request to transfer the remaining amount of the security deposit that has not been returned to the supplier from the platform operator's account to the buyer's account.

Suppliers can use the ordering platform provided by the information processing device 10, deliver the products they handle to the buyers who place orders, and receive payment via electronically recorded claims. The supplier device 11 is a device used by the supplier (creditor) and can be, for example, a computer with communication capabilities such as a personal computer (PC), a smartphone, or a tablet terminal, or a combination of a server and a client terminal, but is not limited to a specific device.

The supplier device 11 is a device that receives order data via the order placement and receipt platform, performs confirmation processing on the order, and inputs other necessary information, which will be described later. The confirmation processing results and input information are sent to the information processing device 10 for processing. The supplier device 11 can store the order placement and receipt data broadcast by the information processing device 10. The order placement and receipt data becomes data that constitutes the blockchain.

Buyers can use the ordering platform provided by the information processing device 10, place orders for the necessary goods and other items with suppliers who are the recipients of orders, receive the deliveries, inspect the deliveries, and pay the price via electronically recorded claims. The buyer device 12 is a device used by the buyer (debtor), and can be, for example, a computer with communication capabilities such as a personal computer (PC), a smartphone, or a tablet terminal, or a combination of a server and a client terminal, but is not limited to a specific device.

The buyer device 12 is a device that inputs and transmits order data via the order placement and receipt platform, and receives result information and other information confirmed and processed by the supplier. The input order data is transmitted to the information processing device 10 for processing. The buyer device 12 can store the order placement and receipt data broadcast by the information processing device 10. The order placement and receipt data becomes data that constitutes the blockchain.

The recording agency system 13 is a system of an electronic claim recording agency based on the Electronically Recorded Claims Act, and records the accrual record and transfer record of an electronically recorded claim in the record book in response to receiving request data such as an accrual record request and an transfer record request from the information processing device 10. When the payment due date of an electronically recorded claim arrives, the recording agency system 13 communicates with the financial institution server 14 of the financial institution associated with the electronically recorded claim to settle the transfer between accounts from the debtor's account to the creditor's account, and records the payment etc. in the record book.

The financial institution server 14 performs an inter-account remittance settlement from the debtor's account to the creditor's account in response to receiving an instruction for inter-account remittance settlement from the recording institution system 13. The financial institution server 14 can perform a funds transfer process in response to receiving a request to transfer an amount equivalent to the security deposit from the supplier's account to the platform operator's account, and can perform a funds transfer process in response to receiving a request to transfer all or part of the security deposit from the platform operator's account to the supplier's account. The financial institution server 14 can also perform a funds transfer process in response to receiving a request to transfer the remaining amount of the security deposit that has not been returned to the supplier from the platform operator's account to the buyer's account. As described above, there can be multiple financial institution servers 14, and a request for a funds transfer is made to the financial institution that holds the remitter's account.

(System configuration)
2 is a system configuration diagram of an information processing device 10 according to the present invention. Like a general computer, the information processing device 10 includes a control unit 101, a main memory unit 102, an auxiliary memory unit 103, an interface (IF) unit 104, and an output unit 105, which are interconnected by a bus 120 or the like. The information processing device 10 includes a user master 106, a product master 107, order data 108, occurrence record request data 109, and an early discount rate table 110 in the form of storage means such as a file/database in the auxiliary memory unit 103.

The control unit 101, also called a central processing unit (CPU), controls each component of the information processing device 10 and performs data calculations, and can also read and execute various programs stored in the auxiliary storage unit 103 into the main storage unit 102. The main storage unit 102, also called a main memory, can store various received data, computer-executable instructions, and data after calculation processing based on those instructions. The auxiliary storage unit 103 is a storage device such as a hard disk drive (HDD), and is used for long-term storage of data and programs.

The embodiment in FIG. 2 describes an embodiment in which the control unit 101, main memory unit 102, and auxiliary memory unit 103 are provided in the same computer, but in another embodiment, the information processing device 10 can be configured to realize parallel distributed processing by multiple computers by using multiple control units 101, main memory units 102, and auxiliary memory units 103. In another embodiment, it is also possible to install multiple servers for the information processing device 10, and have the multiple servers share a single auxiliary memory unit 103.

The IF unit 104 acts as an interface when sending and receiving data between other systems and devices, and also provides an interface for accepting various commands and input data (various masters, tables, etc.) from the system operator. The output unit 105 provides a display screen for displaying the processed data and a printing means for printing the data.

Note that components with functions similar to those of the control unit 101, main memory unit 102, auxiliary memory unit 103, IF unit 104, and output unit 105 also exist in the supplier device 11, buyer device 12, recording agency system 13, and financial institution server 14, but detailed explanations of these will be omitted in this specification.

The user master 106 stores information about users who use the ordering platform provided by the information processing device 10. Figure 3 is a diagram illustrating an example of the data structure of the user master 106 according to one embodiment of the present invention. The user master 106 can include a user ID 301, user information 302, and a payment account 303, but is not limited to these data items and can also include other data items.

User ID 301 is an identifier that identifies a user, such as a supplier or buyer, who uses the ordering platform. User information 302 includes information associated with the user, such as the user's name, location, contact information, etc., but is not limited to the information shown in this specification. Settlement account 303 indicates the information of the settlement account when a user who uses the ordering platform uses an electronically recorded claim.

Returning to FIG. 2, the product master 107 stores information on products associated with each user. FIG. 4 is a diagram illustrating an example of the data structure of the product master 107 according to one embodiment of the present invention. The product master 107 can include a user ID 301, a product ID 401, product information 402, and greenhouse gas emissions 403, but is not limited to these data items and can also include other data items.

Product ID 401 is an identifier that identifies a product associated with a user (e.g., a supplier). Product information 402 includes information associated with a product, such as product name, unit price, volume, and number per case, but is not limited to the information shown in this specification. Greenhouse gas emissions 403 are information that indicate the amount of greenhouse gas (e.g., carbon dioxide (CO2)) emitted until one unit of product is completed. The value of greenhouse gas emissions 403 may be information on the results of a survey conducted by an external organization or information on the results of a survey conducted by the user.

Returning to FIG. 2, the order data 108 stores information related to transactions between suppliers and buyers. FIG. 5 is a diagram illustrating an example of the data structure of the order data 108 according to one embodiment of the present invention. The order data 108 can include a transaction ID 501, a product ID 401, a purchaser ID 502, order information 503, inspection information 504, a contractor ID 505, order information 506, delivery date 507, transaction results 508, security deposit information 509, greenhouse gas emissions 510, and electronically recorded claim issuance timing 511, but is not limited to these data items and can also include other data items.

The transaction ID 501 is an identifier for identifying a transaction between a supplier and a buyer. The product ID 401 is an identifier for identifying a product to be traded. The purchaser ID 502 is an identifier for identifying the user (buyer) who is the purchaser, and is set to the user ID 301. The order information 503 indicates information such as the name of the ordered product, the number of orders, the delivery date, and the unit price. The inspection information 504 includes information on the inspection results performed by the purchaser, such as delivery information such as delivery as ordered, delivery was delayed but the number of orders was delivered (delay), delivery was kept but only a smaller amount than the number ordered was delivered (out of stock), defective product rate information, and information on the inspection completion date, but is not limited to the examples of information shown in this specification. The defective product rate information may be calculated based on the actual delivered quantity or the scheduled delivered quantity. In the latter case, the quantity that is out of stock for some reason is also calculated as defective.

The contractor ID 505 is an identifier that identifies the user (supplier) who is the contractor, and is set to the user ID 301. The order information 506 indicates information such as that the supplier has confirmed the order information. The delivery date 507 indicates the actual delivery date. The transaction result 508 can include information on the result of the transaction, for example, information on the inter-account remittance settlement received from the supplier device 11 and/or the buyer device 12. Information on the inter-account remittance settlement can include, for example, information on whether the settlement was made in accordance with the claim amount (payment) or whether the settlement was not made completely or conditionally (default on debt: impossibility of performance, delayed performance, incomplete performance).

Deposit information 509 indicates the amount of the deposit calculated according to predetermined standards. The deposit is transferred from the supplier's account to the platform operator's account, and is returned in full if there are no defective products, otherwise the amount returned is determined according to the percentage of defective products. Greenhouse gas emissions 510 indicates the total amount of greenhouse gas emissions emitted in the transaction (emissions per unit of product x number of deliveries). Electronically recorded claim issuance timing 511 indicates the timing for early issuance of the electronically recorded claim after discounting it in advance (a specified number of days after delivery).

Returning to FIG. 2, the accrual record request data 109 stores accrual record request information to be sent to the recording agency system 13. FIG. 6 is a diagram illustrating an example of the data structure of the accrual record request data 109 according to one embodiment of the present invention. The accrual record request data 109 can include a transaction ID 501, debtor information 601, creditor information 602, debt amount 603, payment due date 604, and notes 605, but is not limited to these data items and can also include other data items.

The transaction ID 501 is an identifier that identifies a transaction conducted between a supplier and a buyer. The debtor information 601 indicates the name, address, settlement account information, etc. of the debtor buyer. The creditor information 602 indicates the name, address, settlement account information, etc. of the creditor supplier. The debt amount 603 indicates the debt amount (payment amount) in the transaction. The payment due date 604 indicates the date on which the electronically recorded debt is settled between accounts. The payment due date 604 may be blank (null value) with no specific date set. The remarks 605 can indicate supplementary information regarding the electronically recorded debt, such as supplementary information that the electronically recorded debt has been granted a repurchase claim by a financial institution. The remarks 605 may be blank (null value).

Returning to FIG. 2, the early discount rate table 110 shows information on the early discount rate of electronically recorded claims that has been pre-determined between the supplier (receiver) and the buyer (orderer). FIG. 7 is a diagram illustrating an example of the data structure of the early discount rate table 110 according to one embodiment of the present invention. The early discount rate table 110 can include product ID 401, orderer ID 502, contractor ID 505, normal inspection period 701, electronically recorded claim issuance timing 702, and discount rate 703, but is not limited to these data items and can also include other data items.

Product ID 401 is an identifier for identifying a product that is eligible for early discount on electronically recorded claims. Purchaser ID 502 is an identifier for identifying the user (buyer) who places the order, and seller ID 505 is an identifier for identifying the user (supplier) who receives the order, and user ID 301 is set for each. Normal inspection period 701 indicates the period (e.g., 15 days) that normally takes from the time of delivery to the completion of inspection for a product traded between the purchaser (buyer) and seller (supplier). Electronically recorded claim issuance timing 702 indicates the timing at which the electronically recorded claim is issued (e.g., 5 days after delivery, 30 days after order acceptance, etc.), and discount rate 703 indicates the discount rate when an electronically recorded claim is issued at that timing (e.g., 90% of the full amount, etc.).

(Processing flow for automatic issuance and early issuance of electronically recorded monetary claims)
The process flows of the first to fifth embodiments for generating and transmitting an accrual record request to an electronic claim recording institution for automatic and early issuance of electronically recorded claims will be described below with reference to Figures 8 to 12. The premise of these process flows is that the supplier and the buyer are users who use the ordering platform provided by the information processing device 10, and that the supplier device 11 and the buyer device 12 have successfully completed authentication processing for the information processing device 10 and are in an accessible state.

In addition, in the first to fifth embodiments, the information processing device 10 logs in to the recording agency system 13 at various times as described in this specification using a login ID and password for issuing electronically recorded claims that have been loaned to it by the user in advance, and generates accrual record request data for issuing electronically recorded claims using information such as the claim amount and user information in the order/receive data stored on the blockchain, and transmits the data to the recording agency system 13.

First Embodiment
FIG. 8 is a flow diagram for explaining the processing of the first embodiment, including the order processing, the request for recording the accrual of electronically recorded claims, and the reception of settlement information, which are carried out by the information processing device 10.

At S801, the information processing device 10 receives from the buyer device 12 order information for a certain product, i.e., product ID 401, user ID 301 associated with the buyer (orderer), user ID 301 associated with the supplier (receiver), order quantity, unit price, delivery date, and amount. The information processing device 10 generates a transaction ID 501, and based on the received order information, generates order data by setting the product ID 401, orderer ID 502, order information 503, and recipient ID 505 in the order data 108. In response to the generation of the order data, the information processing device 10 notifies the supplier device 11 of the user associated with the recipient ID 505 that an order has been placed.

In S802, the supplier confirms the order details of S801 and inputs information indicating that the order has been approved to the supplier device 11. The information processing device 10 receives information indicating that the order has been approved, which is associated with the transaction ID 501, from the supplier device 11. In response to receiving the order approval information, the information processing device 10 updates the order information 506 of the corresponding order data stored in the order data 108.

In S803, when the supplier delivers the product to the buyer, the information processing device 10 receives delivery information, i.e., information on the delivery date, from the supplier device 11 and updates the delivery date 507 of the corresponding order data in the order data 108.

In S804, when the buyer has finished inspecting the delivered goods, the buyer inputs the inspection information into the buyer device 12. The information processing device 10 receives the inspection information, such as delivery information such as "delivery was made as ordered," "delivery was delayed but the ordered quantity was delivered," "delivery was made on time but less than the ordered quantity was delivered," defect rate information, and inspection completion date information from the buyer device 12, and updates the inspection information 504 of the corresponding order data in the order data 108.

In S805, in response to the update of the inspection information 504, the information processing device 10 queries the user master 106 using the purchaser ID 502 and the contractor ID 505, and obtains the user information 302 and settlement account 303 information of the buyer and the supplier, respectively. The information processing device 10 calculates the amount of the claim based on the information stored in the order information 503 and the inspection information 504.

The information processing device 10 generates accrual record claim data using the transaction ID of the order data for which the inspection information 504 has been updated as transaction ID 501, the acquired buyer information as debtor information 601, the acquired supplier information as creditor information 602, the calculated credit amount as credit amount 603, and the payment due date calculated from the predetermined payment period as payment due date 604, and transmits the generated accrual record claim data to the recording agency system 13 and stores the accrual record claim data in accrual record claim data 109.

At S806, the information processing device 10 receives information regarding the inter-account remittance settlement carried out for the electronically recorded claim from the supplier device 11 and/or the buyer device 12. Information regarding the inter-account remittance settlement may include, for example, information such as whether the settlement was made in accordance with the claim amount (payment) or whether the settlement was not made completely or conditionally (default on the debt: impossibility of performance, delayed performance, incomplete performance).

In the conventional technology flow, after inspection was completed, in-house procedures had to be completed before requesting the accrual of electronically recorded claims, and each financial institution had to set the period and amount on a website prepared by the financial institution, which involved cumbersome procedures. As a result, it took a considerable amount of time for the supplier to collect the funds, and the risk of human error was unavoidable due to the manual intervention.

In the first embodiment, the ordering platform and the recording agency system 13 are automatically linked, and as soon as inspection is performed, a request for recording the occurrence of an electronically recorded claim is sent to the recording agency system 13, enabling the supplier to significantly shorten the time it takes to collect funds and minimizing problems caused by human error.

Second Embodiment
9 is a flow diagram explaining the processing of the second embodiment, including the order processing, the request for recording the accrual of electronically recorded claims, and the reception of settlement information, performed by the information processing device 10. The second embodiment shows that, unlike the first embodiment, if there were no problems with inspection and settlement in a past transaction of the same product between the same supplier and buyer, a request for recording the accrual of electronically recorded claims can be made without waiting for the completion of inspection.

In the second embodiment, the same processing as steps S801 to S803 in the first embodiment described with reference to FIG. 8 is performed.

In S901, in response to an update of the delivery date 507 of the corresponding order data in the order data 108, the information processing device 10 queries the order data 108 based on the product ID 401, purchaser ID 502, and contractor ID 505 of the updated order data, and acquires the order data of the past transaction. The information processing device 10 determines whether there was a problem in the past transaction based on the information on the inspection information 504 and transaction result 508 of the acquired order data of the past transaction. Whether there was a problem is determined based on the delivery information and defective product rate information included in the inspection information 504, and the information on the inter-account remittance settlement included in the transaction result 508.

If it is determined in the determination process of S901 that there is a problem, the process proceeds to S804. Thereafter, the same processes as those of S804 to S806 in the first embodiment described with reference to FIG. 8 are carried out. That is, in the second embodiment, if there is a problem with inspection and payment in a past transaction of the same product between the same supplier and buyer, the same processes as in the first embodiment are carried out.

On the other hand, if it is determined in the judgment process of S901 that there is no problem, the process proceeds to S902. In S902, the information processing device 10 queries the user master 106 using the purchaser ID 502 and the contractor ID 505 of the order data updated in the process of S803, and obtains the user information 302 and settlement account 303 information of the buyer and supplier. The information processing device 10 calculates the amount of the receivable based on the information stored in the order information 503 (e.g., the order quantity and unit price).

In the second embodiment, the amount of receivables is calculated based only on the information stored in the order information 503 (e.g., order quantity and unit price) because, in a previous transaction of the same product between the same supplier and buyer, there were no problems with inspection and payment, and therefore it is assumed that the product was delivered without problems in the current transaction as well (the defective product rate is below the threshold).

The information processing device 10 generates accrual record claim data using the transaction ID of the order data updated in the processing of S803 as transaction ID 501, the acquired buyer information as debtor information 601, the acquired supplier information as creditor information 602, the calculated credit amount as credit amount 603, and the payment due date calculated from the predetermined payment period as payment due date 604, and transmits the generated accrual record claim data to the recording agency system 13 and stores the accrual record claim data in accrual record claim data 109.

After the processing of S902 is completed, processing similar to the processing of S804 and S806 in the first embodiment described with reference to FIG. 8 is performed.

In the second embodiment, if there have been no problems with inspection and settlement in past transactions of the same product between the same supplier and buyer, a request to record the accrual of an electronically recorded claim can be made without waiting for the completion of inspection, making it possible to make a request to record the accrual of an electronically recorded claim earlier than in the conventional art or the flow of the first embodiment. The second embodiment describes a case in which, in cases of continuous transactions of the same product between the same supplier and buyer, where inspection and settlement have been carried out without problems up until now, and where the rate of defective products is below a predetermined threshold, there is no problem with generating an electronically recorded claim without waiting for the completion of inspection.

In the second embodiment, the ordering platform and the recording agency system 13 are automatically linked, and a request for recording the occurrence of an electronically recorded claim is sent to the recording agency system 13 as soon as delivery is made. This allows the supplier to significantly reduce the time it takes to collect funds compared to the first embodiment, and also minimizes problems caused by human error.

Third Embodiment
10 is a flow diagram explaining the processing of the third embodiment, including the order processing, the request for recording the accrual of electronically recorded claims, and the reception of settlement information, performed by the information processing device 10. The third embodiment shows that a request for recording the accrual of electronically recorded claims can be made at a designated timing (e.g., xx days after delivery, xx days after order acceptance) before the completion of inspection, based on an early discount rate predetermined between the supplier and the buyer.

At S1001, the information processing device 10 receives from the buyer device 12 order information for a certain product, i.e., product ID 401, user ID 301 associated with the buyer (orderer), user ID 301 associated with the supplier (receiver), order quantity, unit price, delivery date, and amount. The information processing device 10 generates a transaction ID 501, and based on the received order information, generates order data by setting the product ID 401, orderer ID 502, order information 503, and recipient ID 505 in the order data 108. In response to the generation of the order data, the information processing device 10 notifies the supplier device 11 of the user associated with the recipient ID 505 that an order has been placed.

At S1002, the supplier confirms the order details of S1001 and inputs information indicating the electronically recorded claim issuance timing and order approval to the supplier device 11. The information processing device 10 receives information indicating the electronically recorded claim issuance timing and order approval, which is associated with the transaction ID 501, from the supplier device 11. In response to receiving the electronically recorded claim issuance timing and order approval information, the information processing device 10 updates the order information 506 and electronically recorded claim issuance timing 511 of the corresponding order data stored in the order data 108. The electronically recorded claim issuance timing 511 can indicate information such as x days after the delivery date.

At S1003, when the supplier delivers the product to the buyer, the information processing device 10 receives delivery information, i.e., information on the delivery date, from the supplier device 11 and updates the delivery date 507 of the corresponding order data in the order data 108. In one embodiment of the present invention, the information processing device 10 may be configured to receive information on the issuance timing of the electronically recorded claim during delivery processing and update the electronically recorded claim issuance timing 511 of the corresponding order data.

At S1004, the information processing device 10 queries the early discount rate table 110 based on the product ID 401, purchaser ID 502, contractor ID 505, and electronically recorded claim issuance timing 511 of the order data in which the delivery date 507 has been updated, and obtains the value of the discount rate 703. This process obtains the early discount rate for the electronically recorded claim issuance timing specified by the supplier, from among the early discount rates for electronically recorded claims predetermined between the supplier (contract recipient) and the buyer (order recipient).

In S1005, in response to obtaining the value of the discount rate 703, the information processing device 10 queries the user master 106 using the purchaser ID 502 and the contractor ID 505, and obtains the user information 302 and settlement account 303 information of the buyer and the supplier, respectively. The information processing device 10 calculates the amount of the claim based on the information stored in the order information 503 (e.g., the order quantity and unit price) and the value of the discount rate 703.

The information processing device 10 generates accrual record claim data using the transaction ID of the order data in which the delivery date 507 was updated in S1004 as transaction ID 501, the acquired buyer information as debtor information 601, the acquired supplier information as creditor information 602, the calculated credit amount as credit amount 603, and the payment due date calculated from the predetermined payment period as payment due date 604, and transmits the generated accrual record claim data to the recording agency system 13 and stores the accrual record claim data in accrual record claim data 109.

In S1006, when the buyer has finished inspecting the delivered goods, the buyer inputs the inspection information into the buyer device 12. The information processing device 10 receives the inspection information, such as delivery information such as "delivery was made as ordered," "delivery was delayed but the ordered quantity was delivered," "delivery was made on time but less than the ordered quantity was delivered," defect rate information, and inspection completion date information from the buyer device 12, and updates the inspection information 504 of the corresponding order data in the order data 108.

At S1007, the information processing device 10 receives information regarding the inter-account remittance settlement carried out for the electronically recorded claim from the supplier device 11 and/or the buyer device 12. Information regarding the inter-account remittance settlement may include, for example, information such as whether the settlement was made in accordance with the claim amount (payment) or whether the settlement was not made completely or conditionally (default on the debt: impossibility of performance, delayed performance, incomplete performance).

Above, with reference to FIG. 10, an embodiment in which an accrual record request is made at a specified timing after delivery has been described, but the third embodiment is not limited to this, and an accrual record request may be made at a specified timing before delivery and after order approval (for example, x days after order approval). In such a case, the electronically recorded claim issuance timing 511 may indicate information such as x days after the order approval date. The operation described in S1003 is performed after the operations of S1004 and S1005.

In the third embodiment, a request for recording the accrual of an electronically recorded claim can be made at a specified timing before completion of inspection, such as after order approval or after delivery, based on an early discount rate previously determined between the supplier and the buyer, so that a request for recording the accrual of an electronically recorded claim can be made earlier than in the conventional art and the flows of the first and second embodiments. The third embodiment describes a case in which it is possible to discount an electronically recorded claim at a timing specified by the supplier. The discount rate set in the third embodiment may be a discount rate that is more favorable than the discount that would be offered by any financial institution if the electronically recorded claim were issued normally.

In the third embodiment, the ordering platform and the recording agency system 13 are automatically linked, and a request for recording the accrual of discounted electronically recorded claims is sent to the recording agency system 13 at the timing specified by the supplier. This allows the supplier to significantly shorten the time it takes to collect funds even if the amount of collected funds decreases, and also minimizes problems caused by human error. In addition, the supplier will no longer need to apply for a discount on electronically recorded claims at a later date at any financial institution.

Fourth Embodiment
11 is a flow diagram for explaining the processing of the fourth embodiment, including order placement and receipt processing, request for recording the accrual of electronically recorded claims, and receipt of settlement information, performed by the information processing device 10. The fourth embodiment shows how a deposit is automatically calculated based on delivery risks (e.g., risks in terms of delivery time, quantity, quality, etc.) in past transactions of the same product between the same supplier and buyer, the deposit is transferred from the supplier's account to the platform operating company's account, an electronically recorded claim is issued early, and all or part of the deposit is returned to the supplier based on the results of inspection.

At S1101, the information processing device 10 receives from the buyer device 12 order information for a certain product, i.e., product ID 401, user ID 301 associated with the buyer (orderer), user ID 301 associated with the supplier (receiver), order quantity, unit price, delivery date, and amount. The information processing device 10 generates a transaction ID 501, and based on the received order information, generates order data by setting the product ID 401, orderer ID 502, order information 503, and recipient ID 505 in the order data 108. In response to the generation of the order data, the information processing device 10 notifies the supplier device 11 of the user associated with the recipient ID 505 that an order has been placed.

In S1102, the supplier confirms the order details of S1101 and inputs information indicating a desire for a deposit transaction and information indicating that the order has been approved to the supplier device 11. The information processing device 10 receives information indicating a desire for a deposit transaction and information indicating that the order has been approved from the supplier device 11, which are associated with the transaction ID 501. In response to receiving the order approval information, the information processing device 10 updates the order information 506 of the corresponding order data stored in the order data 108.

In S1103, in response to receiving the information requesting a deposit transaction, the information processing device 10 queries the order data 108 based on the product ID 401, purchaser ID 502, and contractor ID 505 of the updated order data, and acquires the order data of past transactions. The information processing device 10 determines the supplier's delivery risk based on the delivery information and defect rate information contained in the inspection information 504 of the acquired order data of past transactions. The delivery risk is determined based on multiple thresholds that are determined in advance based on information such as the rate of stockouts and the defect rate in past transactions. For example, the delivery risk may be indicated in multiple stages indicating low risk to high risk, and the deposit rate may be determined according to each stage.

The information processing device 10 determines the deposit ratio based on the determined supplier's delivery risk, calculates the amount of the deposit from the order quantity and unit price information stored in the order information 503 and the deposit ratio, and stores the amount in the deposit information 509.

The information processing device 10 queries the user master 106 based on the contractor ID 505, acquires information on the supplier's settlement account 303, and sends a request message to the financial institution server 14 of the financial institution where the supplier's account is located to transfer the calculated amount of the security deposit from the supplier's account to the platform operator's account. The financial institution server 14 transfers the calculated amount of the security deposit from the supplier's account to the platform operator's account in accordance with the request message.

In S1104, in response to calculating the amount of the security deposit, the information processing device 10 queries the user master 106 using the purchaser ID 502 and the contractor ID 505, and obtains the user information 302 and settlement account 303 information of the buyer and the supplier. The information processing device 10 calculates the amount of the claim based on the order quantity and unit price information stored in the order information 503.

The information processing device 10 generates accrual record claim data using the transaction ID of the order data for which the deposit amount was calculated in S1104 as transaction ID 501, the acquired buyer information as debtor information 601, the acquired supplier information as creditor information 602, the calculated credit amount as credit amount 603, and the payment due date calculated from the predetermined payment period as payment due date 604, and transmits the generated accrual record claim data to the recording agency system 13 and stores the accrual record claim data in accrual record claim data 109.

In S1105, when the supplier delivers the product to the buyer, the information processing device 10 receives delivery information, i.e., information on the delivery date, from the supplier device 11 and updates the delivery date 507 of the corresponding order data in the order data 108. In one embodiment of the present invention, the information processing device 10 may be configured to execute the processes of S1103 and S1104 after the delivery process.

In S1106, when the buyer has finished inspecting the delivered goods, the buyer inputs the inspection information into the buyer device 12. The information processing device 10 receives the inspection information, such as delivery information such as "delivery was made as ordered," "delivery was delayed but the ordered quantity was delivered (delay)," "delivery was made on time but less than the ordered quantity was delivered (out of stock)," defect rate information, and inspection completion date information from the buyer device 12, and updates the inspection information 504 of the corresponding order data in the order data 108.

In S1107, the information processing device 10 determines the deposit refund rate based on the defective product rate information received in S1106 and a predetermined standard, for example, a deposit refund rate table such as Table 1. The contents of the deposit refund rate table in Table 1 may be determined for each product traded between the supplier and the buyer.

The information processing device 10 calculates the security deposit refund amount based on the amount of the security deposit stored in the security deposit information 509 and the determined security deposit refund ratio. The information processing device 10 queries the user master 106 based on the contractor ID 505, acquires information on the supplier's settlement account 303, and sends a request message to the financial institution server 14 of the financial institution where the platform operator's account is located to transfer the security deposit refund amount from the platform operator's account to the supplier's account. The financial institution server 14 transfers the security deposit refund amount from the platform operator's account to the supplier's account in accordance with the request message.

If there is a difference between the amount of the security stored in the security information 509 and the calculated security refund amount, i.e., if there is a remaining security amount, the information processing device 10 queries the user master 106 based on the purchaser ID 502, obtains information on the buyer's settlement account 303, and sends a request message to the financial institution server 14 of the financial institution where the platform operator's account is located to transfer the remaining security amount from the platform operator's account to the buyer's account. The financial institution server 14 transfers the remaining security amount from the platform operator's account to the buyer's account in accordance with the request message.

At S1108, the information processing device 10 receives information regarding the inter-account remittance settlement carried out for the electronically recorded claim from the supplier device 11 and/or the buyer device 12. Information regarding the inter-account remittance settlement may include, for example, information such as whether the settlement was made in accordance with the claim amount (payment) or whether the settlement was not made completely or conditionally (default on the debt: impossibility of performance, delayed performance, incomplete performance).

In the fourth embodiment, the delivery risk (e.g., risk in terms of delivery time, quantity, quality, etc.) in past transactions of the same product between the same supplier and buyer is calculated, and a security deposit is automatically calculated and secured as a deposit, so that compensation is provided to the buyer according to the defective product rate. In the fourth embodiment, because a compensation scheme for the buyer exists, the risk to the buyer can be reduced even if a request for recording the accrual of an electronically recorded claim is made before or immediately after delivery, and it becomes possible to make a request for recording the accrual of an electronically recorded claim earlier and with greater security than in the conventional technology or the flow of the first embodiment.

In the fourth embodiment, the ordering platform and the recording agency system 13 are automatically linked, and a request for recording the occurrence of an electronically recorded claim is sent to the recording agency system 13 before or immediately after delivery. This allows the buyer to reduce transaction risks by depositing a security, and the supplier to significantly shorten the time until collection of funds compared to the first embodiment, while minimizing problems caused by human error.

Fifth Embodiment
12 is a flow diagram explaining the processing of the fifth embodiment, including order placement and receipt processing, requests for recording the accrual of electronically recorded claims, and receipt of settlement information, performed by the information processing device 10. The fifth embodiment shows a scheme in which the claim amount of an electronically recorded claim to be issued early is variable according to the greenhouse gas emissions preset for each commodity, etc. to be traded. The fifth embodiment shows a scheme in which early issuance of an electronically recorded claim is not permitted, or only a portion of it is permitted, when the amount of greenhouse gas emissions is greater than a threshold value.

At S1201, the information processing device 10 receives from the buyer device 12 order information for a certain product, i.e., product ID 401, user ID 301 associated with the buyer (orderer), user ID 301 associated with the supplier (receiver), order quantity, unit price, delivery date, and unit price. The information processing device 10 generates a transaction ID 501, and based on the received order information, generates order data by setting the product ID 401, orderer ID 502, order information 503, and recipient ID 505 in the order data 108. In response to the generation of the order data, the information processing device 10 notifies the supplier device 11 of the user associated with the recipient ID 505 that an order has been placed.

In S1202, the supplier confirms the order details of S1201 and inputs information indicating that the order has been approved to the supplier device 11. The information processing device 10 receives information indicating that the order has been approved, which is associated with the transaction ID 501, from the supplier device 11. In response to receiving the order approval information, the information processing device 10 queries the product master 107, obtains the value of the greenhouse gas emission amount 403 associated with the product ID 401, calculates the total greenhouse gas emission amount generated in this transaction based on the order quantity, and updates the order information 506 and greenhouse gas emission amount 510 of the corresponding order data stored in the order data 108.

In S1203, in response to an update of the greenhouse gas emission amount 510 of the corresponding order data stored in the order data 108, the information processing device 10 determines whether the value of the greenhouse gas emission amount 510 of the updated order data (total emission amount) is equal to or less than a predetermined threshold. A plurality of thresholds may be prepared according to the characteristics and delivery quantity of each product. If the value of the greenhouse gas emission amount 510 is equal to or less than the predetermined threshold, the process proceeds to S1204, and the electronically recorded claim can be issued early. On the other hand, if the value of the greenhouse gas emission amount 510 is greater than the predetermined threshold, the processes of S803 to S806 described in the first embodiment are performed.

In S1204, in response to determining that the value of the greenhouse gas emission amount 510 is equal to or less than the predetermined threshold, the information processing device 10 queries the user master 106 using the purchaser ID 502 and the contractor ID 505 to obtain the user information 302 and the settlement account 303 information of each of the buyer and the supplier. The information processing device 10 calculates the credit amount based on the order quantity and unit price information stored in the order information 503. In one embodiment of the present invention, the information processing device 10 can vary the credit amount in stages according to the value of the greenhouse gas emission amount 510. This indicates that the higher the greenhouse gas emission effect of the product, the closer the credit amount the supplier receives to the full amount (i.e., no discount is given even if the product is issued early), and conversely, the lower the greenhouse gas emission effect of the product, the lower the credit amount the supplier receives due to discounts.

The information processing device 10 generates accrual record claim data using the transaction ID of the order data in which the greenhouse gas emissions 510 have been updated as transaction ID 501, the acquired buyer information as debtor information 601, the acquired supplier information as creditor information 602, the calculated credit amount as credit amount 603, and the payment due date calculated from the predetermined payment period as payment due date 604, and transmits the generated accrual record claim data to the recording agency system 13 and stores the accrual record claim data in accrual record claim data 109.

In S1205, when the supplier delivers the product to the buyer, the information processing device 10 receives delivery information, i.e., information on the delivery date, from the supplier device 11 and updates the delivery date 507 of the corresponding order data in the order data 108. In one embodiment of the present invention, the information processing device 10 may be configured to execute the process of S1204 after the delivery process, in which case the degree of variability in the receivable amount may be changed from that described above.

In S1206, when the buyer has finished inspecting the delivered goods, the buyer inputs the inspection information into the buyer device 12. The information processing device 10 receives the inspection information, such as delivery information such as "delivery was made as ordered," "delivery was delayed but the ordered quantity was delivered (delay)," "delivery was made on time but less than the ordered quantity was delivered (out of stock)," defect rate information, and inspection completion date information from the buyer device 12, and updates the inspection information 504 of the corresponding order data in the order data 108.

At S1207, the information processing device 10 receives information regarding the inter-account remittance settlement carried out for the electronically recorded claim from the supplier device 11 and/or the buyer device 12. Information regarding the inter-account remittance settlement may include, for example, information such as whether the settlement was made in accordance with the claim amount (payment) or whether the settlement was not made completely or conditionally (default on the debt: impossibility of performance, delayed performance, incomplete performance).

In one embodiment of the present invention, by using multiple thresholds in the judgment process of S1203, it is possible to distinguish between cases in which early issuance of an electronically recorded claim is made for the full amount of the claim, cases in which early issuance of an electronically recorded claim is made for a portion of the claim amount, and cases in which early issuance is not made at all.

In the fifth embodiment, it is possible to issue electronically recorded claims early and/or gradually vary the claim amount depending on the greenhouse gas emissions of the products that are the subject of the transaction. In the fifth embodiment, electronically recorded claims can be issued early for products with greenhouse gas emissions higher than a threshold value, so that requests for the recording of the occurrence of electronically recorded claims can be made earlier and with greater security than in the conventional technology or the flow of the first embodiment.

In the fifth embodiment, the ordering platform and the recording agency system 13 are automatically linked, and a request for recording the occurrence of an electronically recorded claim is sent to the recording agency system 13 before delivery. This allows the supplier to significantly reduce the time it takes to collect funds compared to the first embodiment, and also minimizes problems caused by human error.

(summary)
In the conventional technology, it took a considerable amount of time from the completion of inspection to the issuance of electronically recorded claims, but in this invention, by automatically linking the platform that accumulates order information with the recording agency of electronically recorded claims, it becomes possible to automatically generate and transmit accrual record request data at any timing before delivery, after delivery, or immediately after the completion of inspection. This allows the debtor (buyer) to receive electronically recorded claims earlier than before, and the debtor (supplier) to improve capital efficiency. In addition, the issuer (debtor) of electronically recorded claims can significantly reduce the clerical work of closing after inspection and issuing electronically recorded claims that was previously performed.

Conventionally, the administrative work related to discount applications was done by creditors (suppliers), but with this invention, it is possible to issue electronically recorded claims that are discounted from the start, which not only leads to improved capital efficiency but also helps reduce administrative work.

The principles of the present invention have been described above with reference to exemplary embodiments, but those skilled in the art will understand that various embodiments that change the configuration and details can be realized without departing from the gist of the present invention. In other words, the present invention can be embodied, for example, as a system, device, method, program, or storage medium.

REFERENCE SIGNS LIST 10 Information processing device 11 Supplier device 12 Buyer device 13 Recording agency system 14 Financial institution server 101 Control unit 102 Main memory unit 103 Auxiliary memory unit 104 Interface (IF) unit 105 Output unit 106 User master 107 Product master 108 Order data 109 Accumulation record request data 110 Early discount rate table

Claims (7)

An information processing device configured for automatic issuance and early issuance of electronically recorded claims,
A communication unit for communicating with an external network, a storage unit, and a control unit,
The control unit is
receiving inspection information for the traded product from the creditor device via the communication unit, and updating the order data in the storage unit based on the inspection information;
in response to the order data in the storage unit being updated based on the inspection information, acquiring creditor information and debtor information associated with the creditor ID and debtor ID included in the order data from a user master in the storage unit, and calculating a credit amount based on the order information and the inspection information included in the order data;
an information processing device that executes a step of generating accrual record request data based on the creditor information, the debtor information, and the calculated claim amount obtained in response to updating the order data in the memory unit based on the inspection information , and transmitting the generated accrual record request data to the recording agency system in order to generate an electronic recorded claim associated with the accrual record request data in the recording agency system after inspection is completed . The inspection information includes defective product rate information,
The credit amount is calculated based on the defective product rate information.
2. The information processing device of claim 1. The inspection information further includes delivery information,
The delivery information is
The delivery was as ordered,
The delivery was delayed but the ordered quantity was delivered, or
Although the delivery date was kept, the amount delivered was less than the number ordered.
The information processing device of claim 2 . An information processing method executed by an information processing device configured for automatic issuance and early issuance of electronically recorded monetary claims, comprising:
The information processing device includes a communication unit for communicating with an external network, a storage unit, and a control unit, and the information processing method includes:
the control unit receiving inspection information for the traded product from the first device via the communication unit, and updating the order data in the storage unit based on the inspection information;
said control unit, in response to updating of the order data in said storage unit based on said inspection information, acquiring creditor information and debtor information associated with the creditor ID and debtor ID included in said order data from a user master in said storage unit, and calculating a credit amount based on the order information and said inspection information included in said order data;
an information processing method comprising a step of: the control unit generating accrual record request data based on the creditor information, the debtor information, and the calculated claim amount obtained in response to updating the order data in the memory unit based on the inspection information , and transmitting the generated accrual record request data to the recording agency system in order to generate an electronic recorded claim associated with the accrual record request data in the recording agency system after inspection is completed . The inspection information includes defective product rate information,
The credit amount is calculated based on the defective product rate information.
The information processing method according to claim 4. The inspection information further includes delivery information,
The delivery information is
The delivery was as ordered,
The delivery was delayed but the ordered quantity was delivered, or
Although the delivery date was kept, the amount delivered was less than the number ordered.
The information processing method according to claim 5 , A program for causing a computer to execute the method according to any one of claims 4 to 6 .

Images