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

Description

Application of Article 30, Paragraph 2 of the Patent Act On August 4, 2021, Retex Co., Ltd. released a product related to the information processing device invented by Takashi Ogura at an online web conference. On August 5, 2021, Retex Co., Ltd. released a product related to the information processing device invented by Takashi Ogura at a meeting at Sumitomo Mitsui Banking Corporation. On August 25, 2021, Retex Co., Ltd. released a product related to the information processing device invented by Takashi Ogura at an online web conference. On August 25, 2021, Retex Co., Ltd. released a product related to the information processing device invented by Takashi Ogura at an online web conference. On September 1, 2021, Retex Co., Ltd. released a product related to the information processing device invented by Takashi Ogura at a meeting at the head office of Tokyo Star Bank.

The present invention relates to an information processing device, an information processing method, and a program.

2. Description of the Related Art Conventionally, an electronic contract system has been used to electronically conclude a contract by transmitting and receiving data using an information processing device between an ordering company and an order receiving company. In recent years, in particular, the Electronically Recorded Monetary Claims Act has been enacted for the purpose of facilitating corporate fund raising, and the need for utilization of electronically recorded monetary claims is increasing. Electronically recorded claims are monetary claims for the purpose of electronically recording and managing claims arising in commercial transactions.

For example, Patent Document 1 describes an electronic contract system connected to an electronically recorded monetary bond management apparatus in order to generate an electronically recorded monetary bond from the ordering stage. The electronic contract system receives order content data from the ordering company's equipment, receives data indicating that an order has been received from the delivery company's equipment, and transmits the received/ordered data to the electronically recorded monetary claims management device. The electronically recorded monetary claims management device generates electronically recorded monetary claims by registering information contained in order receiving/ordering data received from the electronic contract system in the record ledger.

JP 2019-079539 A

By the way, for example, contracts such as monthly payment contracts, subscription contracts, and real estate lease contracts, which are assumed to be paid multiple times, are used in various situations. Such contracts often do not qualify for financing (such as accounts receivable collateral or factoring), as each payment can be small. It is possible to generate multiple Electronically Recorded Monetary Claims by making multiple payments based on a single contract, but the burden of managing Electronically Recorded Monetary Claims becomes extremely heavy, and the small amount of money makes it difficult to finance. It is also assumed that it will not be subject to Electronically recorded monetary claims are usually used for electronic bills, so electronically recorded monetary claims are generated for each payment.

SUMMARY OF THE INVENTION Accordingly, it is an object of the present invention to provide an information processing apparatus, an information processing method, and a program that enable efficient collective management of multiple payments based on one electronic contract.

In an information processing method according to an aspect of the present invention, a computer receives from a first information processing device of a first party in a contract a plurality of payment schedules including record items indicating the details of the contract, a scheduled payment date, and a scheduled payment amount. storing a plurality of payment schedule information in a predetermined storage unit; sending a request for approval of the item to be recorded to a second information processing device of a second party to the contract; A step of receiving approval for a recorded matter from an information processing device, and a step of transmitting an electronically recorded monetary claim generation request including the recorded matter to an electronic monetary claim recording agency system that manages registration of information in the electronically recorded monetary claim recording ledger. and run

According to this aspect, with respect to the recorded matter indicating the content of the contract received from the first information processing device of the first party in the contract, the second information processing device of the second party in the contract approves the recorded matter. After receiving the electronically recorded monetary claims, a request for generation of electronically recorded monetary claims including recorded matters is transmitted to the electronic monetary claims recording agency system that manages the registration of information in the electronically recorded monetary claims recording ledger. At this time, a plurality of pieces of scheduled payment information including the scheduled payment date and the scheduled payment amount received from the first information processing device of the first party are also stored in a predetermined storage unit. Therefore, it is possible to collectively and efficiently manage multiple payments based on one electronic contract.

In the above-described mode, the computer may transmit an electronically recorded monetary claim generation request including recorded matters to an electronic monetary claim recording institution system that manages registration of information in the electronically recorded monetary claim record ledger. According to this structure, multiple payments within the contract period of one contract are generated as one electronically recorded claim, thereby increasing the amount of the claim and making it an object of finance, as well as the number of electronically recorded claims. can be reduced and the management and operation cost can be made more efficient. For example, if electronically recorded monetary claims are generated for each payment, the amount of each of the 12 electronically recorded monetary claims generated would be as small as 100,000 yen. It is possible to generate one electronically recorded claim with a claim amount of 1,200,000 yen for one year.

ADVANTAGE OF THE INVENTION According to this invention, it becomes possible to collectively manage multiple payments based on one electronic contract efficiently.

It is a figure showing an example of composition of electronic contract system 1 concerning this embodiment. It is a figure which shows an example of a structure of the electronic contract management server 10 which concerns on this embodiment. It is a figure which shows an example of the data structure of the cooperation data which concerns on this embodiment. It is a figure which shows an example of the data structure of the payment related data which concerns on this embodiment. It is a figure which shows an example of a structure of the user terminal 20 which concerns on this embodiment. It is a figure which shows an example of the operation|movement sequence of the process by the electronic contract system 1 which concerns on this embodiment. 4 is a diagram showing an example of an input screen 40 for contract transmission information according to the present embodiment; FIG. It is a figure which shows another example of the operation|movement sequence of a process by the electronic contract system 1 which concerns on this embodiment.

Preferred embodiments of the present invention will be described with reference to the accompanying drawings. (In addition, in each figure, those with the same reference numerals have the same or similar configurations.)

(1) Configuration (1-1) Overall Configuration FIG. 1 is a diagram showing an example of the configuration of an electronic contract system 1 according to this embodiment. The electronic contract system 1, for example, provides users with electronic contract services for concluding and managing electronic contracts. The electronic contract service provided by the electronic contract system 1 enables efficient management of multiple payments included in the contract. In the following, the term “user” refers to a party to a contract who concludes an electronic contract using this system, and the term “contract sender” refers to one of the parties to a contract among users. "Contract Recipient" shall mean the person who is the other party to the contract among the users and is the other party to the contract of the sender of the contract. . Here, if one contracting party is the ordering party and the other contracting party is the contractor in the contract, either the ordering party or the contractor may be the above-mentioned "contract sender", and the ordering party and Either of the contractors may become the "contract recipient" described above.

As shown in FIG. 1, the electronic contract system 1 includes, for example, an electronic contract management server 10, a user terminal 20S used by a contract sender (first party in the contract), and a contract receiver (second party in the contract). and a user terminal 20R to be used. The electronic contract system 1 may further include an electronic monetary claim recording agency system 30 . The electronic contract management server 10 is communicably connected to each of the user terminal 20S, the user terminal 20R, and the electronic monetary claim recording institution system 30 via a predetermined communication network. In this embodiment, the user terminals 20S and 20R may simply be referred to as user terminals 20 when there is no need to distinguish between them.

(1-2) Electronic contract management server 10
FIG. 2 is a diagram showing an example of the configuration of the electronic contract management server 10 according to this embodiment. The electronic contract management server 10 according to this embodiment may be configured by one or a plurality of information processing devices, for example. The electronic contract management server 10 manages the conclusion of an electronic contract between parties to a contract by taking charge of sending and receiving recorded items and contract data between the contract sender and the contract receiver. In particular, the electronic contract management server 10 has access to a predetermined storage unit that stores data related to multiple payments included in a contract (payment-related data), whereby the contracting parties It is possible to collectively and efficiently manage multiple payments included in . The electronic contract management server 10 includes, for example, a communication section 11, a storage section 12, and a processing section 13. Furthermore, the electronic contract management server 10 manages the generation of electronically recorded claims based on electronic contracts by requesting the electronically recorded claims based on recorded items and contract data from the electronic monetary claim recording institution system 30. is also possible.

The communication unit 11 has a communication interface circuit for connecting the electronic contract management server 10 to a communication network. The communication unit 11 supplies the processing unit 13 with data received from the user terminal 20, the electronic monetary claim recording institution system 30, and the like. The communication unit 11 also transmits the data supplied from the processing unit 13 to the user terminal 20, the electronic monetary claim recording institution system 30, and the like.

The storage unit 12 has, for example, at least one of a semiconductor memory, a magnetic disk device, and an optical disk device. The storage unit 12 stores driver programs, operating system programs, application programs, data, and the like used for processing by the processing unit 13 . Various programs may be installed in the storage unit 12 from computer-readable portable recording media such as CD-ROMs and DVD-ROMs.

The storage unit 12 may also include a linked data storage unit 121 that stores linked data, a contract data storage unit 122 that stores contract data, and a payment related data storage unit 123 that stores payment related data. . At least one of the linked data storage unit 121, the contract data storage unit 122, and the payment-related data storage unit 123 is one or more devices (cloud storage, database device, etc.) different from the electronic contract management server 10. may be configured as

FIG. 3 is a diagram showing an example of the data structure of the linked data stored in the linked data storage unit 121. As shown in FIG. Here, the linked data is data such as recorded items indicating the content of the contract. The electronic contract management server 10 may release the linked data stored in the linked data storage unit 121 to the electronic monetary claim recording institution system 30 through, for example, ODBC connection. Linkage of linkage data between the electronic contract management server 10 and the electronic claim recording institution system 30 may be managed by time stamps or the like.

As shown in FIG. 3, the linked data records include, for example, contract ID, debtor data, obligee data, credit amount data, payment date data, contract content data, transfer restriction data, defense content data, attachment data, etc. including. The contract ID is identification information (ID) for identifying a contract, and may be an ID or the like assigned by the electronic contract management server 10 or the like. In addition, if the relevant Electronically Recorded Monetary Claims are created by dividing other Electronically Recorded Monetary Claims, the linking data shall include data for identifying the original Electronically Recorded Monetary Claims, the number of divisions, etc. It's okay. The obligor data includes various information about the obligor (payer), for example, the obligor's user number, information about the financial institution and account used by the obligor (financial institution code, branch code, account type , account number, account name, etc.). The obligee data includes various information about the obligee (recipient), for example, the obligee's user number, information about the financial institution and account used by the obligee (financial institution code, branch code, account type , account number, account name, etc.). The credit amount data is data indicating the credit amount (total amount of multiple payment amounts). The payment date data is data indicating the payment date of the claim (the last payment date among multiple payments). The contract content data is data such as text representing at least a part of the contract (for example, key points and important matters of the contract) arbitrarily input by the sender of the contract. The transfer restriction data is data relating to restrictions on assignment of claims, and may include, for example, whether or not there are restrictions on assignment, the number of times the assignment is restricted, and whether or not there are restrictions. The defense content data is data relating to the defense of the claim, and may include, for example, whether or not the defense is to be cut off, the content of the defense regulations, and the like. As attachment data, a predetermined path of an area in which predetermined contract data is stored in the contract data storage unit 122 is registered.

The contract data storage unit 122 stores contract data. The contract data stored (stored) in the contract data storage unit 122 may be encrypted or may be electronically signed. The subject of the electronic signature may be the contract sender, the contract receiver, the administrator of the electronic contract management server 10, or the like.

FIG. 4 is a diagram showing an example of the data structure of payment-related data stored in the payment-related data storage unit 123. As shown in FIG. Here, the payment-related data is data relating to individual payments among multiple payments included in the contract. The electronic contract management server 10 may manage payment-related data independently of the electronic monetary claim recording institution system 30 . The electronic contract management server 10 may release the payment-related data stored in the payment-related data storage unit 123 to the electronic monetary claim recording institution system 30 through, for example, ODBC connection. In that case, the linkage of payment-related data between the electronic contract management server 10 and the electronic claim recording institution system 30 may be managed by time stamps or the like.

The payment-related data shown in FIG. 4 corresponds to a single payment included in multiple payments. Therefore, when a contract includes multiple payments, the payment-related data storage unit 123 stores payment-related data for each payment. As shown in FIG. 4, the payment-related data includes, for example, a contract ID, a payment number, a recipient, a payer, payment schedule information, payment report information, payment confirmation information, and payment completion information. include. The contract ID corresponds to, for example, the contract ID of the linked data described above, and is identification information (ID) for identifying the contract. The number of times of payment is, for example, information indicating what number of times payment is made among multiple payments included in the contract. The payee is, for example, information indicating the party to the contract (creditor) who receives the payment. The payer is, for example, information indicating a party to the contract (obligor) who makes the payment. The payment schedule information is, for example, information about the payment schedule entered by one of the parties to the contract (recipient or payer). The scheduled payment information may include, for example, a scheduled payment date, which is information indicating the scheduled date of payment, and a scheduled payment amount, which is information indicating the scheduled amount of payment. The payment declaration information is, for example, information declared by the payer that payment has been completed. The payment declaration information includes, for example, the payment declaration date, which is information indicating the date declared by the payer as the date when payment was completed, and the scheduled payment amount, which is information indicating the amount declared by the payer as the amount of payment completed. may include The payment confirmation information is, for example, information indicating that the recipient has confirmed the payment corresponding to the payment schedule information. Payment confirmation information may include, for example, a payment confirmation notification sent in response to a payment confirmation input by the payee. The payment completion information is, for example, information indicating that payment has been completed, which is obtained from a system such as a financial institution that manages the account of the contracting parties. The payment completion information may include, for example, the payment completion date, which is information indicating the date when payment was completed, and the payment completion amount, which is information indicating the amount of money for which payment was completed.

The processing unit 13 includes one or more processors and their peripheral circuits. The processing unit 13 controls overall operations of the electronic contract management server 10, and is, for example, a CPU. The processing unit 13 executes processing based on programs (operating system programs, driver programs, application programs, etc.) stored in the storage unit 12 .

The processing unit 13 includes, for example, a transmission/reception unit 131, a data management unit 132, an encryption unit 133, a decryption unit 134, and an electronic signature unit 135.

The transmission/reception unit 131 transmits and receives various information between the user terminal 20 (the user terminal 20S used by the contract sender, the user terminal 20R used by the contract receiver, etc.) and the electronic monetary claim recording institution system 30. receive. The transmitting/receiving unit 131 receives, for example, contract transmission information including recording items indicating contract details, contract data, and payment schedule information from the user terminal 20S used by the contract sender. Further, the transmitting/receiving unit 131 sends, for example, to the user terminal 20R used by the contract recipient, a contract application notification including contract transmission information (recorded items, contract data, payment schedule information, etc.), and an approval request for the contract transmission information. to send. Further, the transmission/reception unit 131 receives approval for the contract transmission information from the user terminal 20R used by the contract receiver. Further, the transmitting/receiving unit 131 transmits, for example, an electronically recorded monetary claim request including recording matters and contract data to the electronic monetary claim recording institution system 30 . Also, the transmitting/receiving unit 131 receives, for example, the record number of the electronically recorded monetary claim from the electronic monetary claim recording institution system 30, and transmits the record number to the user terminal 20S, the user terminal 20R, and the like. Further, the transmitting/receiving unit 131 receives payment report information input by the payer, for example, from the user terminal 20H used by the payer. Also, the transmission/reception unit 131 transmits a payment confirmation request to, for example, the user terminal 20U used by the recipient. Further, the transmitting/receiving unit 131 receives payment confirmation information input by the recipient, for example, from the user terminal 20U used by the recipient. The transmitting/receiving unit 131 also transmits payment content information, which is information including at least part of payment-related data, to the electronic claim recording institution system 30, for example. Details of the payment content information will be described later. Further, the transmitting/receiving unit 131 receives, for example, a predetermined notification from the electronic monetary claim recording institution system 30 (such as a notification that the electronically recorded monetary claim has been extinguished, a notification that the payment details information has been registered, etc.). Further, the transmitting/receiving unit 131, for example, sends a predetermined notification (a notification to the effect that the electronically recorded monetary claim has been extinguished, which will be described later, or payment content information to be registered in the user terminal 20H used by the payer or the user terminal 20U used by the receiver). (e.g., notification that it has been completed).

The data management unit 132 causes the storage unit 12 to store, for example, items to be recorded, contract data, payment-related data, and the like. For example, the data management unit 132 registers a record item indicating the content of the contract in the linked data stored in the linked data storage unit 121 or the like. In addition, the data management unit 132, for example, sends approval to the contract transmission information received from the user terminal 20R used by the contract receiver to the cooperation data storage unit 121, the contract data storage unit 122, the payment-related data storage unit 123, and the like. Memorize. The data management unit 132 also registers (stores) contract data in the contract data storage unit 122, for example. The data management unit 132 also causes the payment-related data storage unit 123 to store payment-related data, for example. Specifically, the data management unit 132, for example, as a payment schedule information management unit, stores the payment schedule information received from the user terminal 20S used by the contract originator as the payment related data stored in the payment related data storage unit 123. to register. Also, the data management unit 132 registers, for example, the payment report information received from the user terminal 20H used by the payer in the payment-related data stored in the payment-related data storage unit 123 . The data management unit 132 also registers, for example, payment confirmation information received from the user terminal 20U used by the recipient in the payment-related data stored in the payment-related data storage unit 123. FIG. Also, the data management unit 132 registers, for example, payment completion information received from the financial institution system that manages the account of the recipient in the payment-related data stored in the payment-related data storage unit 123 . The data management unit 132 also registers information received from the electronic monetary claim recording institution system 30, for example. Specifically, for example, the data management unit 132 causes the storage unit 12 to store information (record number, etc.) regarding electronically recorded monetary claims received from the electronic monetary claims recording institution system 30 . Also, for example, the data management unit 132 registers in the linked data stored in the linked data storage unit 121 that the electronically recorded monetary bond has been extinguished. The data management unit 132 also registers the notification in the payment-related data stored in the payment-related data storage unit 123, for example.

The encryption unit 133, for example, encrypts the contract data received from the user terminal 20S used by the contract sender. The encryption method is not particularly limited, but may be, for example, a common key encryption method using algorithms such as RC4, DES, 3DES, and AES. The encrypted contract data is stored in the contract data storage unit 122 by the data management unit 132, for example.

The decryption unit 134 decrypts the contract data encrypted by the encryption unit 133, for example. The decryption method is not particularly limited, but may be a common key encryption method using algorithms such as RC4, DES, 3DES, and AES.

For example, the electronic signature unit 135 attaches an electronic signature to arbitrary data by the administrator of the electronic contract management server 10 . The format of the electronic signature is not particularly limited. It can be an electronic signature. The electronic signature unit 135 may, for example, attach an electronic signature to contract data received from the user terminal 20S or the like.

(1-3) User terminal 20
FIG. 4 is a diagram showing an example of the configuration of the user terminal 20 according to this embodiment. As shown in FIG. 4, the user terminal 20 includes a communication unit 21, a storage unit 22, a display unit 23, an operation unit 24, and a processing unit 25, for example.

The communication unit 21 has, for example, a communication interface circuit for connecting the user terminal 20 to a communication network. The communication unit 21 supplies data received from the electronic contract management server 10 or the like to the processing unit 25, for example. In addition, the communication unit 21, for example, transmits data supplied from the processing unit 25 to the electronic contract management server 10 or the like. The communication unit 21 may connect the user terminal 20 to the electronic monetary claim recording institution system 30 via a communication network, for example.

The storage unit 22 has, for example, at least one of a semiconductor memory, a magnetic disk device, and an optical disk device. The storage unit 22 stores, for example, a driver program, an operating system program, an application program, data, etc. used for processing by the processing unit 25 . Various programs may be installed in the storage unit 22 from computer-readable portable recording media such as CD-ROMs and DVD-ROMs.

The display unit 23 may be any device as long as it can display video, images, and the like, such as a liquid crystal display and an organic EL display. The display unit 23 displays, for example, a video corresponding to the video data supplied from the processing unit 25, an image corresponding to the image data, and the like.

The operation unit 24 is, for example, a touch panel, a mouse, a keyboard, or the like, and is a device for a user such as a contract sender or a contract receiver to input characters, numbers, symbols, and the like. The operation unit 24 generates, for example, a signal according to the user's operation and supplies the signal to the processing unit 25 .

The processing unit 25 includes, for example, one or more processors and their peripheral circuits. The processing unit 25 comprehensively controls the overall operation of the user terminal 20, and is, for example, a CPU. The processing unit 25 executes processing based on, for example, programs (operating system programs, driver programs, application programs, etc.) stored in the storage unit 22 .

The processing unit 25 includes, for example, a transmission/reception unit 251, a display control unit 252, and an electronic signature unit 253.

The transmission/reception unit 251 transmits and receives various information to and from the electronic contract management server 10, for example. The transmitting/receiving unit 251 transmits, to the electronic contract management server 10, contract transmission information including, for example, recorded items indicating contract details, contract data, payment schedule information, and the like. The transmitting/receiving unit 251 also receives, from the electronic contract management server 10, for example, a contract application notification including contract transmission information (recorded items, contract data, payment schedule information, etc.) and an approval request for the contract transmission information. The transmitting/receiving unit 251 also transmits, for example, approval of the contract transmission information input by the contract recipient to the electronic contract management server 10 . The transmitting/receiving unit 251 also receives, for example, the record number of the electronically recorded monetary claim from the electronic contract management server 10 . Also, the transmitting/receiving unit 251 transmits, for example, the payment report information input by the payer to the electronic contract management server 10 . Also, the transmission/reception unit 251 receives, for example, a payment confirmation request from the electronic contract management server 10 . Also, the transmission/reception unit 251 transmits, for example, the payment confirmation information input by the recipient to the electronic contract management server 10 . Further, the transmitting/receiving unit 251 receives, for example, a predetermined notification (a notification that an electronically recorded claim has been extinguished, a notification that payment content information has been registered, etc.) from the electronic contract management server 10 .

The display control unit 252 causes the display unit 23 to display a predetermined screen, for example, based on the display data. The display control unit 252 causes the display unit 23 to display, for example, a screen for inputting contract transmission information, a screen for displaying contract transmission information, a screen for inputting payment report information, a payment confirmation screen, and the like.

The electronic signature unit 253, for example, attaches an electronic signature to arbitrary data by a user of the user terminal 20 (a contract party such as a contract sender and a contract receiver). The format of the electronic signature is not particularly limited. It can be an electronic signature. The electronic signature unit 253 may, for example, attach an electronic signature to contract data received from the electronic contract management server 10 or the like.

(1-4) Electronic Monetary Claim Recording Institution System 30
The electronic monetary claim recording institution system 30 according to this embodiment may be, for example, a device or system configured by one or a plurality of information processing devices. The electronic monetary claim recording institution system 30 manages, for example, a record ledger for generating electronically recorded monetary claims. The electronic monetary claim recording institution system 30 records items to be recorded and contract data in a record ledger in order to generate electronically recorded monetary claims, for example, based on requests received from the electronic contract management server 10 or the like.

(2) Flow (2-1) Processing Related to Conclusion of Electronic Contract and Generation of Electronically Recorded Monetary Claim FIG. 6 is a diagram showing an example of an operation sequence of processing by the electronic contract system 1 according to the present embodiment. In this process, agreement on the details of the contract is formed between the contract originator and the contract recipient, and then the electronic contract is concluded. Furthermore, under certain conditions, an electronically recorded claim based on the electronic contract is generated.

(S101) First, the display control unit 252 of the user terminal 20S used by the contract caller displays on the display unit 23 an input screen for contract call information. Here, the contract transmission information includes, for example, recorded items indicating the content of the contract, contract data, payment schedule information, and the like.

FIG. 6 is a diagram showing an example of an input screen 40 for contract transmission information. As shown in FIG. 6, the input screen 40 includes, for example, a destination input section 41, a contract name input section 42, an electronic bond conversion selection section 43, a contract related date input section 44, and an order receipt/order selection section 45. , a label input section 46, a viewing authority setting input section 47, a payment schedule information input section 48, a defense information input section 49, and the like.

In the destination input section 41, for example, it is possible to input the name and contact information of the recipient of the contract who is the other party of the contract. In the contract name input section 42, for example, an arbitrarily devised contract name can be input. In the electronic bond generation selection unit 43, for example, it is possible to select whether or not to generate an electronically recorded bond based on the recorded items entered in the contract transmission information. For example, it is possible to select "yes" when generating electronically recorded monetary claims, and "no" when not generating electronically recorded monetary claims. When "Yes" is selected to generate electronically recorded monetary claims, the electronic contract management server 10 transmits an electronically recorded monetary claim generation request to the electronic monetary claims recording institution system 30 under predetermined conditions, as will be described later.

In the contract-related date input unit 44, for example, a date related to the contract can be input. The dates associated with the contract may include, for example, the contract date (contract date), contract start date, contract end date, and the like. For example, it is possible to select whether the contract originator is the orderer or the contractor in the order selection section 45 . For example, if the contract sender is the orderer, "Order" can be selected, and if the contract sender is the contractor, "Receive order" can be selected. In the label input section 46, for example, a label to be associated with the contract can be input. The input label is stored in the electronic contract management server 10 or the like in association with the contract ID or the like, and used for contract management. Labels may be input by selecting from, for example, preset items (in the example shown in FIG. 7, "estimate", "business consignment contract", "software development consignment contract", etc.). , a label arbitrarily devised by the contract originator may be entered.

In the viewing authority setting input section 47, for example, a person (including a group) to whom the contract viewing authority is granted can be input. By accessing the electronic contract management server 10, a person (group) for whom viewing authority has been set may be able to view at least part of the contents of the contract (electronically recorded monetary claim). For this reason, when the electronic contract management server 10 acquires a contract viewing request, the electronic contract management server 10 acquires the user ID included in the viewing request, etc., and determines whether or not the viewing authority is set for the user ID. , predetermined information included in the content of the contract may be transmitted as a response to the viewing request. The viewing authority may be granted to persons (groups) other than parties to the contract as well as parties to the contract.

In the payment schedule information input unit 48, for example, payment schedule information regarding multiple payments included in the contract can be input. The input unit 48 may include, for example, one or a plurality of pairs of a scheduled payment date input unit 48a and a scheduled payment amount input unit 48b. The contract originator may be able to arbitrarily add or delete the number of displayed sets of the scheduled payment date input section 48a and the scheduled payment amount input section 48b. The sum of the amounts entered in all of the input units 48b for the expected payment amount may be calculated as the amount of the claim in the contract.

In the defense information input unit 49, for example, information regarding defense can be input. The information about the defense may include, for example, whether or not the defense is cut off, the content of the defense, and the like. Note that the above-described items displayed on the input screen 40 are only examples, and the input screen 40 may not include some of the above-described items, or may include other items. The input screen 40 may also allow contract data to be input.

(S102) Next, when the contract sender operates the operation unit 24 to input the contract transmission information, the transmission/reception unit 251 of the user terminal 20S used by the contract sender transmits the contract transmission information to the electronic contract management server 10. Send to The electronic signature unit 253 of the user terminal 20S attaches the electronic signature of the contract sender to the contract transmission information (recorded items, contract data, etc.), for example, in response to the operation of the contract sender on the operation unit good too.

(S103) Next, the data management unit 132 of the electronic contract management server 10 causes the storage unit 12 to store the contract transmission information received from the user terminal 20S used by the contract sender. For example, the data management unit 132 associates various recording items included in the contract transmission information with the newly issued contract ID and registers them in the linked data stored in the linked data storage unit 121 . The data management unit 132 also registers (stores) the contract data included in the contract transmission information in a predetermined area of the contract data storage unit 122 in association with the contract ID described above. At this time, the encryption unit 133 may encrypt the contract data. Further, the data management unit 132 registers the path of a predetermined area in the contract data storage unit 122 storing the contract data in the “attachment data” in the linked data stored in the linked data storage unit 121. good too.

In addition, the data management unit 132 associates the scheduled payment information (scheduled payment date, scheduled payment amount, etc.) included in the contract transmission information with the contract ID described above, and stores the payment-related data stored in the payment-related data storage unit 123. to register. Note that the payment schedule information stored in the payment-related data storage unit 123 may be changed at any timing by an operation via the user terminal 20 by any contract party or the like. A contracting party may, for example, change the scheduled payment date, the scheduled payment amount, or the number of payments included in the contract.

The electronic contract management server 10, for example, at an arbitrary timing such as when the payment schedule information is acquired, determines whether the total amount of the payment schedule included in the payment schedule information matches the credit amount data included in the linked data. It may be determined whether Further, the electronic contract management server 10 notifies the user terminal 20 of an error or the like if, for example, the total amount of the scheduled payment amount included in the scheduled payment information does not match the credit amount data included in the linked data. may

(S104) Next, the transmitting/receiving unit 131 of the electronic contract management server 10 refers to the contract receiver's contact information included in the contract transmission information, and confirms that a contract application has been received at the user terminal 20R used by the contract receiver. Send a contract application notice to that effect. The contract application notice may include, for example, information for specifying the contract sender, contract name, and other information included in the contract sending information. As a result, the contract receiver can grasp that the contract sender has applied for the contract.

(S105) Next, when the contract receiver operates the operation unit 24 to input a confirmation request for contract details, the transmission/reception unit 251 of the user terminal 20R used by the contract receiver transmits the confirmation request to the electronic contract management server. Send to 10.

(S106) Next, in response to the confirmation request received from the user terminal 20R used by the contract recipient, the transmitting/receiving unit 131 of the electronic contract management server 10 sends an approval request for the contract transmission information to the user used by the contract recipient. Send to the terminal 20R. The confirmation request may include any data contained in the contract origination information, such as record items, contract data, and payment schedule information. If the contract data is encrypted and stored in the contract data storage unit 122, the decryption unit 134 of the electronic contract management server 10 may decrypt the encrypted contract data.

(S107) Next, the display control unit 252 of the user terminal 20R used by the contract recipient receives contract transmission information (recorded items, contract data, payment schedule information, etc.) are displayed on the display unit 23. At this time, in particular, the display control unit 252 of the user terminal 20R may display a plurality of scheduled payment dates and scheduled payment amounts on the display unit 23 based on the scheduled payment information included in the contract transmission information. This allows the contract recipient to confirm the scheduled payment date and amount due for each of the multiple payments included in the contract.

(S108) Next, when the contract receiver inputs approval for the contract transmission information, the transmission/reception unit 251 of the user terminal 20R transmits the approval to the electronic contract management server 10. FIG. In this way, it can be considered that agreement on the details of the contract has been formed by the contract receiver inputting approval for the contract transmission information. Note that the electronic signature unit 253 of the user terminal 20R attaches the electronic signature of the contract recipient to the contract transmission information (recorded items, contract data, etc.), for example, in response to the operation of the operation unit 24 by the contract recipient. good too.

(S109) Next, when the data management unit 132 of the electronic contract management server 10 receives approval for the contract transmission information from the user terminal 20R, the information (approval information) indicating that there was approval is sent to the cooperation data storage unit 121, It is stored in the contract data storage unit 122, the payment-related data storage unit 123, and the like. Note that the electronic signature unit 135 of the electronic contract management server 10 may, for example, attach the electronic signature of the administrator to contract transmission information (recorded items, contract data, etc.). The approval information may include at least one of data such as a flag indicating approval, the electronic signature of the contract recipient, and the electronic signature of the administrator.

(S110) Next, the data management unit 132 of the electronic contract management server 10 determines whether or not accrual of electronically recorded claims is selected in the contract transmission information (linked data stored in the linked data storage unit 121). do. If it is determined that the generation of electronically recorded monetary claims has been selected, the process proceeds to step S101, and if it is determined that the generation of electronically recorded monetary claims has not been selected, the process proceeds to step S115.

(S111) If the transmission/reception unit 131 of the electronic contract management server 10 determines that generation of electronically recorded monetary claims is selected (S110; Yes), it transmits a request for generation of electronically recorded monetary claims to the electronic monetary claims recording institution system 30. do. Here, the request for issuance of electronically recorded monetary claims includes recorded matters. Also, the generation request may include contract data. The contract data included in the issuance request may be data with an electronic signature of at least one of the contract sender, contract receiver, and administrator, or may be encrypted data. .

(S112) Next, the electronic monetary claim recording institution system 30 records matters to be recorded in the record ledger based on the electronically recorded monetary claim request received from the electronic contract management server 10. FIG. This creates an electronically recorded claim. When the electronic monetary claim recording institution system 30 receives an electronically recorded monetary claim request including contract data, the contract data may also be recorded as a reference record in the record ledger. As a result, an electronically recorded claim including contract data is generated, so it is possible to reflect the content of the contract itself, which is different from the typical recorded matters extracted from the content of the contract, in the electronically recorded claim.

(S113) Next, the electronic claim recording institution system 30 transmits the record number unique to the generated electronically recorded claim to the electronic contract management server 10. FIG.

(S114) Next, the data management section 132 of the electronic contract management server 10 causes the storage section 12 to store the record number.

(S115) When it is determined that generation of electronically recorded monetary claims is not selected (S110; No), the transmitting/receiving unit 131 of the electronic contract management server 10 sends a predetermined notification (a etc.) is transmitted to the user terminal 20S used by the contract sender and/or the user terminal 20R used by the contract receiver. Also, when the record number is stored in the storage unit 12 (S114), a notification including the record number is transmitted to the user terminal 20S used by the contract caller. As a result, the contract caller can grasp the record number. The transmitting/receiving unit 131 of the electronic contract management server 10 may transmit the notification including the record number to the user terminal 20R used by the contract recipient. This allows the contract recipient to know the record number. This completes the operation sequence.

As described above, in the electronic contract system 1 according to the present embodiment, the contract receiver confirming the contract transmission information provided by the contract sender transmits the approval of the contract transmission information to the electronic contract management server 10 . Therefore, by electronically forming an agreement on contract details, it becomes possible to conclude an electronic contract. Furthermore, in the processing by the electronic contract system 1 according to the present embodiment, a plurality of pieces of payment schedule information including the payment schedule date and payment schedule amount input by the contract sender are stored in the predetermined storage unit 12 . Therefore, it is possible to efficiently manage multiple payments collectively for one electronic contract.

(2-2) Processing for Individual Payments FIG. 8 is a diagram showing another example of the operation sequence of processing by the electronic contract system 1 according to this embodiment. The process is performed when any one of the multiple payments included in the contract is made. Hereinafter, the user terminal 20H is assumed to be the user terminal 20 used by the contracting party as the payer, and the user terminal 20U is assumed to be the user terminal 20 used by the contracting party as the payee. The contract sender (first party) may be the payer and the contract receiver (second party) may be the receiver, or the contract receiver (second party) may be the payer and the contract sender ( first party) may be the recipient.

(S201) First, the display control unit 252 of the user terminal 20H used by the payer displays on the display unit 23 an input screen for payment report information. The payment declaration information is, for example, information declared by the payer that payment has been completed. For example, the payment declaration date, which is information indicating the date declared by the payer as the date of completion of payment, and the amount of payment completed. and the planned payment amount, which is information indicating the amount declared by the payer. The payment report information may also include, for example, information indicating the number of payments among a plurality of payments (information indicating the number of payments). For example, when one scheduled payment date arrives, the payer makes the payment scheduled for that scheduled payment date via the financial institution system that manages the payer's account, and then reports the payment. Information may be entered into the user terminal 20H.

(S202) Next, when the payer operates the operation unit 24 to input the payment declaration information, the transmission/reception unit 251 of the user terminal 20H used by the payer transmits the payment declaration information to the electronic contract management server 10. do.

(S203) Next, the data management unit 132 of the electronic contract management server 10 adds the payment report information received from the user terminal 20H used by the payer to the payment-related data stored in the payment-related data storage unit 123. Register in association with schedule information. The electronic contract management server 10 may determine whether or not the payment report information (payment report date and payment report amount) matches the payment schedule information (payment schedule date and payment schedule amount). If not, an error notification may be sent to the user terminal 20 .

(S204) Next, the transmission/reception unit 131 of the electronic contract management server 10 transmits a payment confirmation request, which is a payment confirmation request, to the user terminal 20U used by the recipient. The payment confirmation request may, for example, include at least a portion of the payment declaration information (such as payment declaration date and payment declaration amount). Note that the transmission/reception unit 131 may transmit payment completion information, which will be described later, to the user terminal 20U together with the payment confirmation request.

(S205) Next, the display control section 252 of the user terminal 20U displays a payment confirmation screen on the display section 23 based on the payment confirmation request received from the electronic contract management server 10. FIG. The payment confirmation screen may include, for example, information indicating at least part of the payment report information (payment report date, payment report amount, information indicating the number of payments, etc.). The payee confirms that the payer has made a payment to the account through, for example, a financial institution system that manages the account of the payee, and then operates the operation unit 24 on the payment confirmation screen. to confirm payment.

(S206) Next, when the receiver performs a payment confirmation operation via the operation unit 24, the transmission/reception unit 251 of the user terminal 20U to be used transmits payment confirmation information to the electronic contract management server 10. FIG.

(S207) Next, the data management unit 132 of the electronic contract management server 10 adds the payment confirmation information received from the user terminal 20H used by the recipient to the payment-related data stored in the payment-related data storage unit 123. Register in association with schedule information.

(S208) Next, the data management unit 132 of the electronic contract management server 10 acquires payment completion information, which is information indicating that payment has been completed, from the financial institution system that manages the accounts of the payer and the recipient, It is registered in the payment-related data stored in the payment-related data storage unit 123 in association with the payment schedule information. The payment completion information may include, for example, the payment completion date, which is information indicating the date when payment was completed, and the payment completion amount, which is information indicating the amount of money for which payment was completed. The electronic contract management server 10 may acquire the payment completion information via the electronic claim recording institution system 30, for example. Further, the electronic contract management server 10 may transmit the acquired payment completion information to the user terminal 20H used by the payer or the user terminal 20U used by the payee. In addition, the electronic contract management server 10 allows the payment completion information (payment completion date and payment completion amount) to match the payment report information (payment report date and payment report amount) and payment schedule information (scheduled payment date and schedule payment amount). It may be determined whether or not they match, and if they do not match, an error notification may be sent to the user terminal 20H, the user terminal 20U, and the like.

(S209) Next, the data management unit 132 of the electronic contract management server 10 refers to the contract transmission information (linked data stored in the linked data storage unit 121) and the like to determine whether electronically recorded claims have been generated. judge. If it is determined that an electronically recorded bond has been generated, the process proceeds to step S210, and if it is determined that an electronically recorded bond has not been generated, the process proceeds to step S214.

(S210) When the transmitting/receiving unit 131 of the electronic contract management server 10 determines that an electronically recorded monetary claim has occurred (S219; Yes), the payment content information including at least part of the payment-related data is sent to the electronic monetary claim record. Send to the agency system 30 . The payment content information may optionally include information included in payment-related data according to the specifications of the electronic monetary claim recording institution system 30 . For example, the payment content information may include information related to payment date (payment declaration date, payment completion date, etc.), information related to payment amount (payment declaration amount, payment completion amount, etc.), payment confirmation information, etc. .

(S211) Next, the electronic claim recording institution system 30 executes payment confirmation processing based on the payment details information. In the payment confirmation process, the total amount of payment (declared payment amount or payment completion amount) included in all payment content information received from the electronic contract management server 10 so far has reached the credit amount included in the recorded items. It is determined whether or not When the electronic monetary claim recording institution system 30 determines that the total amount of payment has reached the amount of the claim, it executes processing to extinguish the electronically recorded monetary claim. Register payment information.

(S212) Next, the electronic monetary claim recording institution system 30 transmits a predetermined notification to the electronic contract management server 10. For example, when the process of extinguishing the electronically recorded monetary claim is executed in step S211, the electronic monetary claim recording institution system 30 transmits to the electronic contract management server 10 a notification to the effect that the electronically recorded monetary claim has been extinguished. Further, for example, when the process of registering the payment details information is executed in step S211, the electronic monetary claim recording institution system 30 transmits to the electronic contract management server 10 a notice that the payment details information has been registered.

(S213) Next, the data management section 132 of the electronic contract management server 10 registers the notification received from the electronic monetary claim recording institution system 30. FIG. For example, in the case of a notification that the electronically recorded monetary claim has been extinguished, the data management unit 132 registers the fact that the electronically recorded monetary bond has been extinguished in the linked data stored in the linked data storage unit 121 . Also, for example, in the case of a notification that payment content information has been registered, the data management unit 132 registers the notification in the payment-related data stored in the payment-related data storage unit 123 .

(S214) When it is determined that an electronically recorded claim has not been generated (S209; No), the transmitting/receiving unit 131 of the electronic contract management server 10 sends a predetermined notification (payment confirmation information, payment completion information, etc. etc.) to the user terminal 20H and/or the user terminal 20U. Further, when the notification received from the electronic claim recording institution system 30 is registered (S213), the transmitting/receiving unit 131 of the electronic contract management server 10 sends a predetermined notification to the user according to the content of the notification registered in step S212. It is transmitted to the terminal 20H and/or the user terminal 20U. For example, in the case of the notification that the electronically recorded monetary bond has been extinguished, the transmitting/receiving unit 131 transmits, for example, the notification that the electronically recorded monetary bond has been extinguished to the user terminal 20H and/or the user terminal 20U. Further, for example, in the case of a notification that payment content information has been registered, the transmitting/receiving unit 131 transmits the notification to the user terminal 20H and/or the user terminal 20U, for example. With this, the operation sequence ends.

As described above, in the electronic contract system 1 according to the present embodiment, the payment declaration information entered by the payer, the payment confirmation information entered by the recipient, and the payment completion information acquired from a predetermined financial institution system, etc. It is stored in the payment related data stored in the related data storage unit 123 . Therefore, it becomes possible to efficiently manage multiple payments for an electronic contract collectively.

The embodiments described above are for facilitating understanding of the present invention, and are not intended to limit and interpret the present invention. Each element provided in the embodiment and its conditions are not limited to those illustrated and can be changed as appropriate. It is also possible to partially replace or combine each configuration.

DESCRIPTION OF SYMBOLS 1... Electronic contract system 10... Electronic contract management server 11... Communication part 12... Storage part 121... Cooperation data storage part 122... Contract data storage part 123... Payment related data storage part 13... Processing part , 131... transmission/reception unit, 132... data management unit, 133... encryption unit, 134... decryption unit, 135... electronic signature unit, 20, 20S, 20R... user terminal 20, 21... communication unit, 22... storage unit, 23 ... display section, 24 ... operation section, 25 ... processing section, 251 ... transmission/reception section, 252 ... display control section

Claims (9)

A computer that manages a storage unit that stores the contents of the contract,
receiving, from a first information processing device of a first party in a contract, recorded items indicating the content of the contract and a plurality of pieces of scheduled payment information including a scheduled payment date and a scheduled payment amount;
a step of storing the plurality of payment schedule information in the storage unit in association with the record item;
sending a request for approval of the recorded matter to a second information processing device of a second party in the contract;
receiving approval for the recorded item from the second information processing device;
a step of storing approval information indicating that the approval has been given in the storage unit in association with the recorded item;
Payment report for a payer to report that a payment corresponding to one of the plurality of payment schedule information has been made from one of the first information processing device and the second information processing device receiving information;
a step of storing the payment report information in the storage unit in association with the one piece of payment schedule information;
Information processing method that performs the computer
Payment confirmation information, which is information indicating that the recipient has confirmed payment corresponding to the one piece of payment schedule information, is received from the other of the first information processing device and the second information processing device, which is different from the one. and
a step of storing the payment confirmation information in the storage unit in association with the one piece of payment schedule information;
The information processing method according to claim 1 , further comprising: the computer
receiving payment completion information indicating that a payment corresponding to one of the plurality of scheduled payment information has been completed;
a step of storing the payment completion information in the storage unit in association with the one piece of payment schedule information;
3. The information processing method according to claim 1 , further comprising: 4. The information processing method according to claim 3 , wherein said payment completion information includes information generated by an account management system that manages said first party's account and said second party's account. the computer
a step of sending a request for issuance of electronically recorded monetary claims including the recorded matters to an electronic monetary claims recording agency system that manages registration of information in the electronically recorded monetary claims recording ledger;
The information processing method according to any one of claims 1 to 4 , further comprising: the computer
a step of transmitting payment content information indicating payment content corresponding to one of the plurality of payment schedule information to the electronic claim recording institution system;
6. The information processing method according to claim 5 , further comprising: the computer
a step of receiving information indicating whether or not the electronically recorded monetary claim corresponding to the recorded matter has been extinguished from the electronic monetary claim recording institution system;
7. The information processing method according to claim 6 , further comprising: In the computer that manages the storage unit that stores the contents of the contract,
receiving, from a first information processing device of a first party in a contract, recorded items indicating the content of the contract and a plurality of pieces of scheduled payment information including a scheduled payment date and a scheduled payment amount;
a step of storing the plurality of payment schedule information in the storage unit in association with the record item;
sending a request for approval of said recorded matter to a second information processing device of a second party in said contract;
receiving approval for the recorded item from the second information processing device;
a step of storing approval information indicating that the approval has been given in the storage unit in association with the recorded item;
Payment report for a payer to report that a payment corresponding to one of the plurality of payment schedule information has been made from one of the first information processing device and the second information processing device receiving information;
a step of storing the payment report information in the storage unit in association with the one piece of payment schedule information;
program to run the An information processing device that manages a storage unit that stores contract details,
a first receiving unit for receiving, from a first information processing device of a first party in a contract, recorded items indicating the content of the contract and a plurality of pieces of scheduled payment information including a scheduled payment date and a scheduled payment amount;
a payment schedule information management unit that stores the plurality of payment schedule information in the storage unit in association with the recording items;
a transmission unit that transmits an approval request for the recorded matter to the second information processing device of the second party in the contract;
a second receiving unit that receives approval for the recorded item from the second information processing device;
an approval information management unit that stores approval information indicating that the approval has been given in the storage unit in association with the recorded item;
Payment report for a payer to report that a payment corresponding to one of the plurality of payment schedule information has been made from one of the first information processing device and the second information processing device a third receiving unit for receiving information;
a payment declaration information management unit that stores the payment declaration information in the storage unit in association with the one payment schedule information;
Information processing device.

Images