Information Processing Apparatus and Information Processing Program

Abstract

To provide an information processing device and an information processing program, allowing a user of a contract request destination to use information other than information obtainable by the user of the contract request destination through an electronic signature service.SOLUTION: An information processing device includes a processor. The processor is configured to: obtain, from an electronic signature service, contract information related to a contract from a first user being a contract request source to a second user being a contract request destination, using authentication information on the first user for using the electronic signature service; and enable the second user to use also extended information other than information obtainable by the second user through the electronic signature service of the obtained contract information.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] The technology of the present invention relates to an information processing apparatus and an information processing program.

Background Art

[0002] There is a technology for securely sharing a contract document.

[0003] Patent Document 1 discloses a system for appropriately applying an electronic signature to an electronic document and managing it so that it can be viewed among a plurality of users. The system includes a plurality of terminals used by each user, a management device, an encrypted first communication path connecting each terminal and the management device, and a second communication path connecting between each terminal and between each terminal and the management device. The terminal of the first user transmits the data of the electronic document to the management device via the first communication path, and notifies the terminal of one or more second users who require a signature of the address of the document in the management device and the signature request via the second communication path. The terminal of the second user that has received the request receives the data of the document from the management device via the first communication path, and transmits the electronic signature data accompanying the confirmation of the document content to the management device via the first communication path. The management device stores the electronically signed document in a browsable manner at the address via the first communication path. An electronic signature document management system is disclosed.

[0004] There is a technology for maintaining the originality of an electronic contract.

[0005] In Patent Document 2, using a communication terminal, a service providing server, and a communication line connecting the server and the communication terminal, "each act in the negotiation process of a contract", "the signature act for contract conclusion", and "a series of histories up to contract conclusion" are proven on an information system such as a communication network, and the acts and the histories are safely stored as data maintaining readability equivalent to that of paper. A contract support integrated service system, wherein an internal certification authority of this service proven by a third-party certification authority performing a highly reliable authentication service receives a request from an enterprise or the like that wishes to issue "a program using encryption technology such as an electronic signature and its key" for using this service, and stores and issues the above "program using encryption technology such as an electronic signature and its key" in "a device having a function such that the encrypted program and data are not physically replicated", and has means for storing contract data signed or authenticated by the above "program using encryption technology such as an electronic signature and its key" in a device that cannot be safely tampered with. A contract support integrated service system is disclosed, which is characterized by the above.

Prior Art Documents

Patent Documents

[0006]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0007] In an electronic signature service, a user who is a registrant of the service can conclude a contract with a user of a contract recipient as a contract requester. The user of the contract requester can obtain contract information such as appendices as well as the final contract document using the electronic signature service.

[0008] On the one hand, a user who is the recipient of a contract request can only obtain, for example, the final contract document using an electronic signature service, and the amount of information that can be obtained is limited compared to the user who is the originator of the contract request. However, there may be cases where the user who is the recipient of the contract request also wants to obtain information other than the information that can be obtained from the electronic signature service.

[0009] The present disclosure aims to provide an information processing apparatus and an information processing program that are available to a user who is the recipient of a contract request, for information other than the information that can be obtained through an electronic signature service.

Means for Solving the Problem

[0010] The information processing apparatus according to the first aspect includes a processor. The processor uses the authentication information of a first user for using an electronic signature service to obtain contract information related to a contract from the first user who is the originator of the contract request to a second user who is the recipient of the contract request from the electronic signature service, and makes the second user available for the extended information included in the obtained contract information other than the information that the second user can obtain through the electronic signature service.

[0011] The information processing apparatus according to the second aspect is the information processing apparatus according to the first aspect, wherein the processor accumulates the obtained contract information, and makes the second user available for the extended information included in the accumulated contract information.

[0012] The information processing apparatus according to the third aspect is the information processing apparatus according to the second aspect, wherein the processor further obtains contract information related to a contract from the third user to the second user from the electronic signature service using the authentication information of a third user who is the originator of another contract, and makes the second user available for the extended information included in the contract information with the first user or the third user as the originator of the contract request.

[0013] The information processing apparatus according to the fourth aspect is the information processing apparatus according to any one of the first to third aspects, wherein the processor makes the second user able to use the extension information within the range specified by the first user.

[0014] The information processing apparatus according to the fifth aspect is the information processing apparatus according to any one of the first to fourth aspects, wherein the processor authenticates a user using identification information, and makes the extension information of the contract information including the identification information used for the authentication as the identification information of the second user available.

[0015] The information processing apparatus according to the sixth aspect is the information processing apparatus according to the fifth aspect, wherein the processor makes the extension information of the contract information including the e-mail address of the second user available, where the identification information is the e-mail address of the user.

[0016] The information processing apparatus according to the seventh aspect is the information processing apparatus according to the sixth aspect, wherein the processor makes a user with an e-mail address in the same domain as the e-mail address of the second user able to use the extension information.

[0017] The information processing program according to the eighth aspect causes a computer to obtain contract information regarding a contract from a first user who is a contract requester to a second user who is a contract recipient from an electronic signature service using authentication information of the first user for using the electronic signature service, and make the second user able to use the obtained contract information including extension information other than the information that the second user can obtain through the electronic signature service.

Advantages of the Invention

[0018] According to the first and eighth aspects, the second user can be made able to use extension information other than the information that the second user can obtain through the electronic signature service.

[0019] According to the second aspect, even when the authentication information of the first user becomes unavailable, the extended information can still be continuously made available to the second user.

[0020] According to the third aspect, the second user can be made able to use the extended information of the contract with users other than the first user.

[0021] According to the fourth aspect, the first user can restrict the extended information that the second user can use.

[0022] According to the fifth aspect, the user specified by the identification information included in the contract information can be made able to use the extended information.

[0023] According to the sixth aspect, the user having the email address included in the contract information can be made able to use the extended information.

[0024] According to the seventh aspect, the extended information can be shared among users having the same domain.

Brief Description of Drawings

[0025]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Mode for Carrying Out the Invention

[0026] Hereinafter, an example of an embodiment of the technology of the present invention will be described with reference to the drawings. In each drawing, the same or equivalent components and parts are given the same reference numerals. Also, the dimensional ratios in the drawings are exaggerated for the convenience of explanation and may be different from the actual ratios.

[0027] FIG. 1 is a schematic diagram of an electronic signature service 7. The electronic signature service 7 is a service that realizes the conclusion of a contract between a first user 90 who is a contract requester and a second user 95 who is a contract requestee by means of an electronic signature. Here, the first user 90 belongs to Company A 92 which is a tenant. The first user 90 uses a terminal device 91 to register and use the electronic signature service 7. The terminal device 91 is, for example, a terminal such as a smartphone, a tablet, and a personal computer. The first user 90 is registered with the electronic signature service 7. The second user 95 belongs to Company B 97 which is a tenant. The second user 95 uses a terminal device 96 to use the electronic signature service 7. The terminal device 96 is, for example, a terminal such as a smartphone, a tablet, and a personal computer. The second user 95 may or may not be registered with the electronic signature service 7.

[0028] The flow in which the first user 90 uses the electronic signature service 7 to request a contract from the second user 95 will be described in the order of the processes indicated by arrow Y1 to arrow Y5.

[0029] Arrow Y1 indicates the process in which the first user 90 uses the terminal device 91 to create the contract document 75 for the electronic signature service 7. The electronic signature service 7 provides the first user 90 with a contract document creation function on, for example, a WEB screen. Then, the first user 90 creates the contract document 75 by using the contract document creation function provided by the electronic signature service 7. Also, the first user 90 enters the E-mail address of the second user 95 as the contract request destination for the electronic signature service 7. Here, the contract document 75 is data stored, for example, in text data or PDF (Portable Document Format) format, etc.

[0030] Arrow Y2 indicates the process in which the electronic signature service 7 requests the second user 95 to sign via E-mail. The electronic signature service 7 sends, for example, an E-mail describing the URL (Uniform Resource Locator) of the WEB site for confirming the contract document 75 and implementing the signature. Also, the electronic signature service 7 attaches meta-information such as the signature area 76 to the contract document 75.

[0031] Arrow Y3 indicates the process in which the second user 95 uses the terminal device 96 to confirm or sign the contract document 75 for the electronic signature service 7. The second user 95, for example, signs the signature area 76 attached to the contract document 75. Then, the electronic signature service 7 executes the electronic signature using the said signature.

[0032] Arrow Y4 indicates the process in which the electronic signature service 7 notifies the first user 90 of the completion of signature via E-mail. Similarly, the electronic signature service 7 also notifies the second user 95 of the completion of signature (not shown in FIG. 1).

[0033] Arrow Y5 indicates the process in which the first user 90 uses the terminal device 91 to check the contract information for the electronic signature service 7. Here, the contract information is information regarding the contract and has one or more items. The contract information includes, for example, the contract status, the contract requester, the contract recipient, the contract date, the contract term, the contract document, or the contract document meta information of the contract. Here, the contract status indicates the conclusion status of the contract. The contract status is, for example, unrequested, contract in progress, or completed, etc. Also, the contract document meta information is information attached to the contract document. The contract document meta information is, for example, the meta information of a PDF that can be edited before contract conclusion, such as the signature area 76, the input box for the amount, or the check box for consent, etc.

[0034] In this way, the electronic signature service 7 provides a management function including a contract information checking function to the first user 90. The management function includes, for example, a function to make the contract information available, a function to check past contracts, and a function to update contracts, etc. Here, the function to make available means to send information to the user, to make it in a viewable state, or to make it in a downloadable state.

[0035] On the other hand, the electronic signature service 7 does not provide the management function to the second user 95. Or, the electronic signature service 7 provides a restricted management function compared to the first user 90. For example, the electronic signature service 7 makes the contract document meta information before and after signature available to the first user 90. On the other hand, the electronic signature service 7 does not make the contract document meta information before and after signature available to the second user 95. Also, for example, the electronic signature service 7 makes the contract information of past contracts with the second user 95 available to the first user 90. On the other hand, the electronic signature service 7 does not make the contract information of past contracts with the first user 90 available to the second user 95.

[0036] [First Embodiment] Figure 2 is a diagram showing the system configuration of the contract management system 1 according to the first embodiment. The contract management system 1 is a system that acquires contract information or service information from one or more electronic signature services 7 and performs unified management. The service information is information regarding the electronic signature service 7. The service information is, for example, the remaining number of uses that a contract request can be made on the electronic signature service 7, whether the electronic signature service is registered, and the expiration date of the authentication information, etc. In the following description, the contract information and the service information are referred to as "contract information, etc." Here, the contract management system 1 is composed of a contract management device 10, a WEB server 20, a contract document storage 30, and a contract management database 40.

[0037] The contract management device 10 acquires contract information, etc. from the electronic signature service 7 and creates extended information. Here, the extended information is information other than the information that the second user 95 can acquire through the electronic signature service 7 among the contract information acquired from the electronic signature service 7. The extended information includes information created based on the contract information, etc. For example, the contract management device 10 creates information on the number of contracts between the first user 90 and the second user 95 from the past contracts between the first user 90 and the second user 95 as the extended information. The extended information is, for example, contract document meta-information, flag information indicating relevance to past contracts, and related contract document data. Note that the contract management device 10 operates as the information processing device of the present disclosure.

[0038] The WEB server 20 is a server that communicates with a WEB browser or the like via HTTP (Hypertext Transfer Protocol). The WEB server 20 receives, for example, an HTTP request transmitted from a WEB browser installed in the terminal device 96. Further, the WEB server 20 transmits the information of the received HTTP request to the contract management device 10.

[0039] The contract document storage 30 is a storage that stores files such as the contract document 75. It transmits the file in response to a request from the contract management device 10 or the like.

[0040] The contract management database 40 is a database that stores information used for contract management.

[0041] Note that the contract management system 1, the mail server 50, the electronic signature service 7, Company A 92, and Company B 97 are connected to the network N. Also, the mail server 50 is a mail server for sending and receiving e-mails.

[0042] Figure 3 is a schematic diagram of the contract management system 1 according to the first embodiment. The process in which the first user 90 uses the contract management system 1 to request a contract from the second user 95 will be described in the order of the processes indicated by the arrows Y11 to Y19.

[0043] Arrow Y11 indicates the process in which the first user 90 uses the terminal device 91 to request a contract with the second user 95 from the contract management system 1.

[0044] Arrow Y12 indicates the process in which the contract management system 1 requests a contract from the electronic signature service 7. Here, when the electronic signature service 7 exposes an API (Application Programming Interface), the contract management system 1 uses the API to request a contract from the electronic signature service 7. Also, the electronic signature service 7 executes the API using the authentication information of the first user 90. Here, the authentication information is the authentication information for using the electronic signature service. The authentication information is, for example, a password or an authentication key for using the API of the electronic signature service 7. Note that the contract management device 10 stores the authentication information of the first user 90 in the contract management database 40 in advance.

[0045] Arrow Y13 indicates the process in which the electronic signature service 7 requests a signature from the second user 95.

[0046] Arrow Y14 indicates the process in which the second user 95 performs a signature on the electronic signature service 7.

[0047] Arrow Y15 indicates the flow of the process in which the electronic signature service 7 transmits contract information and the like to the contract management system 1. That is, the contract management system 1 acquires contract information and the like from the electronic signature service 7. When the electronic signature service 7 publishes an API, the contract management system 1 uses the API to acquire contract information and the like from the electronic signature service 7. The process of acquiring contract information and the like will be described later with reference to FIGS. 7, 8, and 9.

[0048] Arrow Y16 indicates the flow of the process in which the electronic signature service 7 notifies the first user 90 and the second user 95 of the completion of signature.

[0049] Arrow Y17 indicates the flow of the process in which the contract management system 1 notifies the first user 90 and the second user 95 of the update of contract information and the like. The update of contract information and the like is, for example, the update of the contract status by the signature of the second user 95.

[0050] Arrow Y18 indicates the flow in which the first user 90 uses the terminal device 91 to confirm contract information and the like with the contract management system 1.

[0051] Arrow Y19 indicates the flow in which the second user 95 uses the terminal device 96 to confirm the extended information with the contract management system 1.

[0052] FIG. 4 is a block diagram showing the hardware configuration of the contract management apparatus 10 according to the first embodiment. The contract management apparatus 10 includes components such as a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, a storage 14, an input unit 15, a display unit 16, and a communication interface (communication I / F) 17. Each component is communicably connected to each other via a bus 19.

[0053] The CPU 11 is a central processing unit that executes various programs and controls each part. That is, the CPU 11 reads a program from the ROM 12 or the storage 14 and executes the program using the RAM 13 as a work area. The CPU 11 performs control of each of the above configurations and various arithmetic processes according to the program recorded in the ROM 12 or the storage 14. In the first embodiment, an information processing program for managing contracts is stored in the ROM 12 or the storage 14. The contract management processing program will be described later with reference to FIGS. 7, 8, 9, 10, 11, and 16.

[0054] The ROM 12 stores various programs and various data. The RAM 13 temporarily stores a program or data as a work area. The storage 14 is composed of an HDD (Hard Disk Drive) or an SSD (Solid State Drive) and stores various programs including an operating system and various data.

[0055] The input unit 15 includes a pointing device such as a mouse and a keyboard and is used to perform various inputs.

[0056] The display unit 16 is, for example, a liquid crystal display and displays various information. The display unit 16 may adopt a touch panel method and function as the input unit 15.

[0057] The communication interface 17 is an interface for communicating with other devices such as a database, and for example, standards such as Ethernet (registered trademark), FDDI, Wi-Fi (registered trademark), etc. are used.

[0058] Next, the operation of the contract management system 1 will be described. FIGS. 5 and 6 are sequence diagrams showing the flow of contract management processing of the contract management system 1 according to the first embodiment. In FIG. 5, the processing of the first user 90, the contract management system 1, the electronic signature service 7, the second user 95, and the mail server 50 will be described.

[0059] In step S1, the first user 90 requests a contract from the contract management system 1. Note that step S1 corresponds to step S102 in FIG. 7 described later.

[0060] In step S2, the contract management system 1 requests a contract from the electronic signature service 7. Note that step S2 corresponds to step S106 in FIG. 7 described later.

[0061] In step S3, the electronic signature service 7 requests a signature from the second user 95.

[0062] In step S4, the electronic signature service 7 transmits contract information and the like to the contract management system 1. Note that step S4 corresponds to step S108 or step S112 in FIG. 7 described later.

[0063] In step S10, the second user 95 requests extension information from the contract management system 1. Note that step S10 corresponds to step S304 in FIG. 11 described later.

[0064] In step S11, the contract management system 1 transmits extension information to the second user 95. Note that step S10 corresponds to step S308 in FIG. 11 described later.

[0065] In step S20, the second user 95 executes a signature with respect to the electronic signature service 7.

[0066] In step S21, the electronic signature service 7 notifies the mail server 50 of the completion of the signature. That is, the electronic signature service 7 sends an e-mail to notify the first user 90 and the second user 95 of the completion of the signature.

[0067] In step S22, the mail server 50 notifies the contract management system 1 of the completion of signature. The contract management system 1 obtains, for example, an e-mail from the electronic signature service 7 to the first user 90 or the second user 95 by POP (Post Office Protocol) or IMAP (Internet Message Access Protocol). The contract management system 1 may, for example, obtain in advance the POP authentication information of the first user 90 or the second user 95. Also, the first user 90 or the second user 95 may transfer the e-mail to the contract management system 1 instead of the mail server 50. Note that step S22 corresponds to step S122 in FIG. 8 described later.

[0068] In step S23, the contract management system 1 requests the electronic signature service 7 for contract information and the like.

[0069] In step S24, the electronic signature service 7 transmits contract information and the like to the contract management system 1. Note that steps S23 and S24 correspond to step S126 in FIG. 8 described later.

[0070] In step S30, the second user 95 requests the contract management system 1 for extension information. Note that step S30 corresponds to step S304 in FIG. 11 described later.

[0071] In step S31, the contract management system 1 transmits extension information to the second user 95. Note that step S31 corresponds to step S308 in FIG. 11 described later.

[0072] FIG. 6 is a sequence diagram showing the flow of the contract management process of the contract management system 1 when requesting a contract from the electronic signature service 7 and when not using the mail server 50. In FIG. 6, the first user 90 will explain the processes of the contract management system 1, the electronic signature service 7, and the second user 95.

[0073] In step S40, the first user 90 requests a contract from the electronic signature service 7.

[0074] In step S41, the electronic signature service 7 requests a signature from the second user 95.

[0075] In step S50, the contract management system 1 periodically requests contract information and the like from the electronic signature service 7.

[0076] In step S51, the electronic signature service 7 transmits contract information and the like to the contract management system 1. Note that steps S50 and S51 correspond to steps S132 to S136 in FIG. 9 described later.

[0077] In step S60, the second user 95 requests extension information from the contract management system 1. Note that step S60 corresponds to step S304 in FIG. 11 described later.

[0078] In step S61, the contract management system 1 transmits extension information to the second user 95. Note that step S61 corresponds to step S308 in FIG. 11 described later.

[0079] In step S70, the second user 95 executes a signature with respect to the electronic signature service 7.

[0080] In step S80, the second user 95 requests extension information from the contract management system 1. Note that step S80 corresponds to step S304 in FIG. 11 described later.

[0081] In step S81, the contract management system 1 requests contract information and the like from the electronic signature service 7. That is, the contract management system 1 requests contract information and the like on the occasion of the request for extension information from the second user 95.

[0082] In step S82, the electronic signature service 7 transmits contract information and the like to the contract management system 1.

[0083] In step S83, the contract management system 1 transmits extension information to the second user 95. Note that step S83 corresponds to step S308 in FIG. 11 described later.

[0084] Next, the operation of the contract management apparatus 10 will be described. FIG. 7 is a flowchart showing the flow of processing for acquiring contract information and the like triggered by a contract request by the contract management apparatus 10 according to the first embodiment. The CPU 11 reads out a processing program for acquiring contract information and the like triggered by a contract request from the ROM 12 or the storage 14, expands it in the RAM 13, and executes it, thereby performing the processing for acquiring contract information and the like triggered by a contract request.

[0085] In step S102, the CPU 11 receives a contract request from the first user 90. The CPU 11 proceeds to step S104.

[0086] In step S104, the CPU 11 acquires the authentication information of the first user 90. That is, the CPU 11 acquires the authentication information of the first user 90 previously stored in the contract management database 40. The CPU 11 proceeds to step S106.

[0087] In step S106, the CPU 11 transmits contract request information to the electronic signature service 7 using the authentication information of the first user 90. The contract request information is information for causing the electronic signature service 7 to perform a contract request process. That is, the CPU 11 uses the API to cause the electronic signature service 7 to execute a contract request process. The CPU 11 proceeds to step S108.

[0088] In step S108, the CPU 11 receives the execution result of the contract request. The CPU 11 proceeds to step S110. Here, the execution result is a response to a request using the API.

[0089] In step S110, the CPU 11 determines whether the execution result includes contract information or the like. If it is determined that the execution result does not include contract information or the like (step S110: No), the CPU 11 proceeds to step S112. If it is determined that the execution result includes contract information or the like (step S110: Yes), the CPU 11 proceeds to step S114.

[0090] In step S112, the CPU 11 uses the authentication information of the first user 90 to obtain contract information or the like from the electronic signature service 7. That is, the CPU 11 uses the authentication information of the first user 90 to obtain the contract information from the first user 90 to the second user 95 who is the contract request destination. Note that the CPU 11 may obtain one or more contract information in which the first user 90 is the contract request source or the contract request destination using the authentication information of the first user 90. The CPU 11 proceeds to step S114.

[0091] In step S114, the CPU 11 stores the contract information or the like. That is, the CPU 11 accumulates the contract information or the like in the contract management database 40. The CPU 11 stores the contract information or the like in the common table of the contract management database 40. The common table will be described later with reference to FIG. 12. The CPU 11 ends the process of obtaining the contract information or the like upon the opportunity of the contract request. Note that by performing steps S102 to S114 using the authentication information of users other than the first user 90, the contract information or the like of users other than the first user 90 is accumulated in the contract management database 40. The same applies to steps S122 to S128 in FIG. 8 and steps S132 to S138 in FIG. 9.

[0092] FIG. 8 is a flowchart showing the flow of a process of obtaining contract information or the like upon the opportunity of a signature completion notification by the contract management apparatus 10 according to the first embodiment. When the CPU 11 reads out a process program for obtaining contract information or the like upon the opportunity of a signature completion notification from the ROM 12 or the storage 14 and expands and executes it in the RAM 13, the process of obtaining contract information or the like upon the opportunity of a signature completion notification is performed.

[0093] In step S122, the CPU 11 receives a notification of signature completion. The CPU 11 proceeds to step S124. For example, the CPU 11 receives, from the mail server 50 by POP or the like, a notification of signature completion by e-mail indicated by the arrow Y16 in FIG. 3.

[0094] In step S124, the CPU 11 acquires the authentication information of the first user 90. The CPU 11 proceeds to step S126.

[0095] In step S126, the CPU 11 uses the authentication information of the first user 90 to acquire contract information and the like from the electronic signature service 7. The CPU 11 proceeds to step S128.

[0096] In step S128, the CPU 11 stores the contract information and the like. The CPU 11 ends the process of acquiring the contract information and the like upon receiving the notification of signature completion.

[0097] FIG. 9 is a flowchart showing the flow of the process of periodically acquiring contract information and the like by the contract management apparatus 10 according to the first embodiment. The process of periodically acquiring contract information and the like is performed by the CPU 11 reading out a process program for periodically acquiring contract information and the like from the ROM 12 or the storage 14, expanding it in the RAM 13, and executing it.

[0098] In step S132, the CPU 11 determines whether or not a predetermined time has elapsed. If it is determined that the predetermined time has elapsed (step S132: Yes), the CPU 11 proceeds to step S134. If it is determined that the predetermined time has not elapsed (step S132: No), the CPU 11 ends the process of periodically acquiring contract information and the like. Note that the predetermined time is, for example, one hour.

[0099] In step S134, the CPU 11 acquires the authentication information of the first user 90. The CPU 11 proceeds to step S136.

[0100] In step S136, the CPU 11 acquires contract information and the like from the electronic signature service 7 using the authentication information of the first user 90. The CPU 11 proceeds to step S138.

[0101] In step S138, the CPU 11 stores the contract information and the like. The CPU 11 periodically ends the process of acquiring the contract information and the like.

[0102] FIG. 10 is a flowchart showing the flow of the process of creating extension information by the contract management apparatus 10 according to the first embodiment. The process of creating extension information is performed by the CPU 11 reading a process program for creating extension information from the ROM 12 or the storage 14, expanding it in the RAM 13, and executing it. Note that the contract management apparatus 10 creates extension information when there is storage of contract information and the like, when there is a request for extension information, or when a user login is received. The case where there is storage of contract information and the like means the case where the process of step S114 in FIG. 7, step S128 in FIG. 8, or step S138 in FIG. 9 has occurred. Also, the case where there is a request for extension information means the case where the process of step S304 in FIG. 11 has occurred. Further, the case where a login is received means the case where the process of step S302 in FIG. 11 or step S322 in FIG. 16 has occurred.

[0103] In step S202, the CPU 11 starts the user loop process. The user loop process is an iterative process that performs processing for each user. Note that the user is the contract requester or the contract requestee of the contract information. In the following description, the user during the iterative process is referred to as "the said user". The CPU 11 proceeds to step S204. Note that the determination of the end of the user loop process is made in step S220, which will be described later.

[0104] In step S204, the CPU 11 acquires the contract information for which the said user is the contract requestee. The CPU 11 proceeds to step S206.

[0105] In step S206, the CPU 11 acquires a contract sharing flag. The CPU 11 proceeds to step S208. Here, the contract sharing flag is a flag that determines whether to share contract information with the contract request destination. The contract sharing flag is a flag that can be set by the contract requester. A specific example of the contract sharing flag will be described later with reference to FIG. 12. In the present disclosure, for a flag, 0 represents OFF and 1 represents ON.

[0106] In step S208, the CPU 11 determines whether the contract sharing flag is ON. If it is determined that the contract sharing flag is ON (step S208: Yes), the CPU 11 proceeds to step S210. If it is determined that the contract sharing flag is OFF (step S208: No), the CPU 11 proceeds to step S216.

[0107] In step S210, the CPU 11 acquires an item sharing flag. The CPU 11 proceeds to step S212. Here, the item sharing flag is a flag that determines whether to share each item value of the contract information with the contract request destination. By sharing each item value of the contract information, the user of the contract request destination can use the item as extended information. The item sharing flag is a flag that can be set by the contract requester. A specific example of the item sharing flag will be described later with reference to FIG. 13.

[0108] In step S212, the CPU 11 determines whether the item sharing flag is ON. If it is determined that the item sharing flag is ON (step S212: Yes), the CPU 11 proceeds to step S214. If it is determined that the item sharing flag is OFF (step S212: No), the CPU 11 proceeds to step S216.

[0109] In step S214, the CPU 11 adds each item value to the extended information. That is, when the item sharing flag is ON, the CPU 11 adds the contract information corresponding to the item sharing flag to the extended information. The CPU 11 proceeds to step S216. The process of adding each item value to the extended information will be described later with reference to FIGS. 14 and 15.

[0110] In step S216, the CPU 11 acquires contract information for which the user is the contract requester. The CPU 11 proceeds to step S218.

[0111] In step S218, the CPU 11 adds the contract information to the extended information. The CPU 11 proceeds to step S220. The process of adding the contract information to the extended information will be described later with reference to FIGS. 14 and 15.

[0112] In step S220, the CPU 11 determines whether to end the user loop process. When the repetitive process has been performed for all users, the CPU 11 ends the process of creating the extended information. If the repetitive process has not been performed for all users, the CPU 11 proceeds to step S202.

[0113] FIG. 11 is a flowchart showing the flow of the process of making the extended information of the contract management apparatus 10 according to the first embodiment available. The process of making the extended information available is performed by the CPU 11 reading a process program for making the extended information available from the ROM 12 or the storage 14 and expanding and executing it in the RAM 13. Note that the contract management apparatus 10 has a user registration function. User registration will be described later with reference to FIG. 18.

[0114] In step S302, the CPU 11 accepts the login of the second user 95. As a login process, the CPU 11 uses the e-mail address for authentication. For example, the second user 95 logs in using the e-mail address included in the contract information and a preset password. Alternatively, the CPU 11 may use the identification information included in the contract information for authentication instead of the e-mail address. The identification information included in the contract information is, for example, a telephone number, an address, or a name. Specific examples of the e-mail address and password will be described later with reference to FIG. 18. The CPU 11 proceeds to step S304.

[0115] In step S304, the CPU 11 accepts a request for extended information from the second user 95. The CPU 11 proceeds to step S306.

[0116] In step S306, the CPU 11 acquires the extended information. The CPU 11 proceeds to step S308.

[0117] In step S308, the CPU 11 makes the extended information available to the second user 95. That is, the CPU 11 makes the extended information available when the e-mail address used for authentication matches the e-mail address of the second user 95 included in the contract information. Also, when there are multiple e-mail addresses included in the contract information, the extended information is made available when at least one of them matches. For example, the CPU 11 transmits the extended information to the second user 95 by e-mail. Also, for example, the CPU 11 makes the extended information downloadable for the second user 95. Also, for example, the CPU 11 causes the display unit 16 to display an extended information view, which will be described later with reference to FIGS. 14 and 15, for the second user 95 as the extended information. Also, the CPU 11 causes the display unit 16 to display the extended information by the process to be described later with reference to FIG. 16. The CPU 11 ends the process of making the extended information available.

[0118] FIG. 12 is a diagram showing an example of a common table used for contract management of the contract management apparatus 10 according to the first embodiment. The common table is a table for storing contract information. The common table has a contract number column, an electronic signature service column, a contract status column, a contract requester column, a contract recipient column, a contract date column, a contract expiration column, a contract document column, a contract document meta information column, a related contract column, and a contract sharing flag column. For example, the contract management apparatus 10 uses the authentication information of the user of A1@A.COM to acquire the contract information of contract number 001 from service X, which is the electronic signature service 7, and stores it in the common table. Also, for example, the contract management apparatus 10 uses the authentication information of the user of B1@B.COM to acquire the contract information of contract number 002 from service X, which is the electronic signature service 7, and stores it in the common table.

[0119] The contract number column stores the contract number obtained from the electronic signature service 7. The contract number is a number for identifying a contract in the electronic signature service 7. For example, "001" is stored in the contract number column. In the electronic signature service column, the contract management device 10 stores information for identifying the electronic signature service 7 used for the contract. In the record with the contract number "001", "Service X" is stored. In the contract status column, the contract management device 10 stores the contract status obtained from the electronic signature service 7. In the record with the contract number 001, "Completed" is stored. In the contract requester column, the contract management device 10 stores the contract requester obtained from the electronic signature service 7. In the record with the contract number 001, "A1@A.COM" is stored. In the contract recipient column, the contract management device 10 stores the contract recipient obtained from the electronic signature service 7. In the record with the contract number 001, "B1@B.COM" is stored. In the contract date column, the contract management device 10 stores the contract date obtained from the electronic signature service 7. In the record with the contract number 001, "2020.10.01" is stored. In the contract expiration column, the contract management device 10 stores the contract expiration obtained from the electronic signature service 7. In the record with the contract number 001, "2025.02.12" is stored. In the contract document column, the contract management device 10 stores the contract document obtained from the electronic signature service 7. In the record with the contract number 001, "001.PDF" is stored. Note that the contract document column may store the path of the contract document storage 30 where the contract document 75 is stored. In the contract document meta information column, the contract management device 10 stores the contract document meta information obtained from the electronic signature service 7. In the record with the contract number 001, "001A.PDF" is stored. Note that when the contract document meta information is in file format, the contract document meta information column may store the path of the contract document storage 30 where the contract document meta information is stored. In the related contract column, the contract management device 10 stores information for identifying related contracts. Related contracts are, for example, the original contract for contract updates or the original contract for copying contract documents. The contract management device 10 stores, for example, the contract number of the related contract in the related contract column when the contract information of the related contract is included in the contract information. Also, the contract management device 10 may, for example, accept input to the related contract column through a predetermined screen. In the contract sharing flag column, the contract management device 10 stores the contract sharing flag. The contract sharing flag is a flag that determines whether to share a record. When the contract sharing flag is 1, the contract management device 10 makes the record available to the contract request destination. In the record with contract number 001, "1" is stored. In this way, for each contract, it is possible to specify whether the contract requester shares the extended contract information with the contract request destination. This specification can be made by the user of the contract requester, that is, the first user 90, through a predetermined screen to the contract management device 10. Also, as will be described later with reference to FIG. 13, it is also possible to specify the range to be shared with the contract request destination for the content of each contract.

[0120] In this way, the contract management device 10 uses the authentication information of the first user 90 to obtain contract information related to the contract from the first user 90 to the second user 95 and stores it in the common table. For example, in the contract information with contract number 001, the user of A1@A.COM corresponds to the first user 90, and the user of B1@B.COM corresponds to the second user 95.

[0121] FIG. 13 is a diagram showing an example of an item sharing table used for contract management in the contract management apparatus 10 according to the first embodiment. The item sharing table is a table updated by specifying the range of extended information shared by the first user 90 with respect to the second user 95. For example, the first user 90 can specify the range of extended information to be shared with the second user 95 through a predetermined screen with respect to the contract management apparatus 10. The item sharing table has flags corresponding to each column of the common table. That is, the item sharing table has a contract number column, an electronic signature service flag column, a contract status flag column, a contract request source flag column, a contract request destination flag column, a contract date flag column, a contract expiration flag column, a contract document flag column, a contract document meta information flag column, and a related contract flag column. Each flag column is a flag that determines whether to share the value stored in the corresponding column of the common table. When the flag is ON, the value of the corresponding column of the common table is displayed in the extended information view described later with reference to FIGS. 14 and 15. That is, the contract management apparatus 10 displays the contract information in the range specified by the first user 90 in the extended information view of the second user 95. For example, in the record of contract number 001, the contract document meta information flag is 0, and the other various flags are 1.

[0122] FIGS. 14 and 15 are diagrams showing an example of an extended information view used for contract management by the contract management apparatus 10 according to the first embodiment. The extended information view is a view for displaying extended information. That is, when the flag in the item sharing table is ON, the extended information view displays the value of the corresponding common table for each contract number. In addition, the extended information view is a view created for each user. That is, the contract management apparatus 10 creates an extended information view for each user who is the contract request source or the contract request destination.

[0123] FIG. 14 is a diagram showing an example of an extended information view of a user with an e-mail address of B1@B.COM. In FIG. 14, records of contract number 001, contract number 002, and contract number 003 are displayed. However, the value of the contract document meta information for contract number 001 is not displayed. That is, the contract management device 10 displays contract numbers 001, 002, and 003, for which the contract requester or contract requestee is B1@B.COM, in the extended information view from the common table. Also, the value of the contract document meta information for contract number 001 is not displayed. This is because the contract document meta information flag for contract number 001 in the item sharing table is OFF.

[0124] FIG. 15 is a diagram showing an example of the extended information view of a user with the e-mail address C1@C.COM. In FIG. 15, records of contract number 003 and contract number 006 are displayed. That is, the contract management device 10 displays contract numbers 003 and 006, for which the contract requester or contract requestee is C1@C.COM, in the extended information view from the common table. Here, the contract requester for contract number 003 is A1@A.COM, and the contract requester for contract number 006 is E1@E.COM. That is, the contract management device 10 displays a plurality of contract information with different contract requesters in the extended information view. In other words, when the user of A1@A.COM is the first user 90, the user of C1@C.COM is the second user 95, and the user of E1@E.COM is the third user, the contract management device 10 displays the extended information of the second user 95 among the contract information for which the first user 90 or the third user is the contract requester in the extended information view. Note that the third user is a user who is the contract requester of a contract different from the contract with the first user 90. Note that the contract management device 10 does not display the contract information of contract number 005 in the extended information view. This is because the contract sharing flag for contract number 005 in the common table is OFF.

[0125] [Second Embodiment] Next, the second embodiment will be described. The second embodiment is an example of a process for making the extended information in the first embodiment available. In the first embodiment, as shown in FIG. 14, the second user 95 can use the contracts involved as the contract request destination user in the extended information view. In the second embodiment, in addition to being able to use the contracts involved as the contract request destination user, the second user 95 can classify and use the contracts created by their own company and the contracts they are in charge of. The hardware configuration of the second embodiment is the same as that of the first embodiment. Also, parts having the same configuration and operation as those in the first embodiment are denoted by the same reference numerals and the description thereof is omitted.

[0126] FIG. 16 is a flowchart showing the flow of the process of displaying the extended information by the contract management device 10 according to the second embodiment. The process of displaying the extended information is performed by the CPU 11 reading out the process program for displaying the extended information from the ROM 12 or the storage 14, expanding it in the RAM 13, and executing it.

[0127] In step S322, the CPU 11 accepts the login of the second user 95. The CPU 11 proceeds to step S324.

[0128] In step S324, the CPU 11 acquires the tenant information of the second user 95. The CPU 11 proceeds to step S326. Here, the tenant information is information of the tenant to which the user belongs. The tenant information includes a tenant-internal sharing flag. The tenant-internal sharing flag is a flag for determining whether to share contract information within the tenant. The tenant-internal sharing flag is a flag that can be set for each tenant. A specific example of the tenant-internal sharing flag will be described later with reference to FIG. 17.

[0129] In step S326, the CPU 11 acquires the extended information of the users of the tenant. The users of the tenant are one or more users belonging to the same tenant. The CPU 11 proceeds to step S328.

[0130] In step S328, the CPU 11 determines whether the contract requester is the second user 95. If it is determined that the contract requester is not the second user 95 (step S328: No), the CPU 11 proceeds to step S330. If it is determined that the contract requester is the second user 95 (step S328: Yes), the CPU 11 proceeds to step S334.

[0131] In step S330, the CPU 11 determines whether the in-tenant sharing flag is ON. If it is determined that the in-tenant sharing flag is ON (step S330: Yes), the CPU 11 proceeds to step S332. If it is determined that the in-tenant sharing flag is OFF (step S330: No), the CPU 11 ends the process of displaying the extended information.

[0132] In step S332, the CPU 11 determines whether the contract requester is a user of the tenant. If it is determined that the contract requester is a user of the tenant (step S332: Yes), the CPU 11 proceeds to step S334. If it is determined that the contract requester is not a user of the tenant (step S332: No), the CPU 11 proceeds to step S340.

[0133] In step S334, the CPU 11 determines whether the person in charge is the second user 95. The person in charge is the person in charge of the contract determined for each tenant. Specific examples of the person in charge will be described later with reference to FIG. 19. If it is determined that the person in charge is the second user 95 (step S334: Yes), the CPU 11 proceeds to step S336. If it is determined that the person in charge is not the second user 95 (step S334: No), the CPU 11 proceeds to step S338.

[0134] In step S336, the CPU 11 displays it as "Personally in Charge" of the "Contract Created by the Company". The CPU 11 ends the process of displaying the extended information.

[0135] In step S338, the CPU 11 displays it as "Others" of the "Contract Created by the Company". The CPU 11 ends the process of displaying the extended information.

[0136] In step S340, the CPU 11 determines whether the person in charge is the second user 95. If it is determined that the person in charge is the second user 95 (step S340: Yes), the CPU 11 proceeds to step S342. If it is determined that the person in charge is not the second user 95 (step S340: No), the CPU 11 proceeds to step S344.

[0137] In step S342, the CPU 11 displays it in "assigned by oneself" of "shared contract". The CPU 11 finishes the process of displaying the extended information.

[0138] In step S344, the CPU 11 displays it in "others" of "shared contract". The CPU 11 finishes the process of displaying the extended information.

[0139] FIG. 17 is a diagram showing an example of a tenant table used for contract management in the contract management apparatus according to the second embodiment. The tenant table is a table that stores tenant information and is updated each time a new tenant is created or a tenant is updated. The tenant table has a tenant number column, a tenant name column, a domain column, and a tenant-internal sharing flag column. The contract management apparatus 10 receives, for example, input of tenant information by a user at the time of user registration and stores the tenant information in the tenant table.

[0140] The tenant number column stores a tenant number for identifying a tenant. For example, "T001" is stored in the tenant number column. The tenant name column stores the tenant name. In the record where the tenant number column is T001, "Company A" is stored. The domain column stores the unique domain of the email address held by the tenant. In the record where the tenant number column is T001, "A.COM" is stored. Note that a plurality of unique domains may be stored for one tenant. The tenant-internal sharing flag column stores a flag that determines whether to share contract information within the tenant. In the record where the tenant number column is T001, "1" is stored.

[0141] FIG. 18 is a diagram showing an example of a user table used for contract management in the contract management apparatus according to the second embodiment. The user table is a table that stores user information when there is user registration. The user table has an email address column, a tenant number column, a password column, and a user name column.

[0142] The email address column stores the user's email address. For example, "A1@A.COM" is stored in the email address column. The tenant number column stores the tenant number to which the user belongs. In the record where the email address is A1@A.COM, "T001" is stored. When the domain of the email address matches the domain of the tenant, the contract management apparatus 10 assigns the user to that tenant. That is, users with the same email address domain belong to the same tenant. The password column stores the password for logging in to the contract management apparatus 10. The user name column stores the user name. In the record where the email address is A1@A.COM, "Fuji Tarou" is stored.

[0143] Since D1@D.COM does not exist in the user table, the user of D1@D.COM is not user-registered. Therefore, the user of D1@D.COM cannot log in to the contract management apparatus 10 and cannot use the extended information.

[0144] FIG. 19 is a diagram showing an example of a tenant contract table used for contract management by the contract management apparatus 10 according to the second embodiment. The tenant contract table creates a record for each pair of a contract and a tenant. The tenant contract table has a contract number column, a tenant number column, and a person in charge column.

[0145] In the person-in-charge column, the person in charge is stored. In the person-in-charge column of the record with contract number 001 and tenant number T001, "Fuji Tarou" is stored. Note that the person-in-charge column may store information for identifying a user such as an email address. Figures 20 to 22 are examples of the extended information display screen 100 displayed on the display unit 16 of the contract management device 10 according to the second embodiment. The extended information display screen 100 has a tab 101 and an extended information display area 102. As shown in Figure 20, the tab 101 has, as the first category, "Contracts created by the company" and "Shared contracts". Also, the tab 101 has, as the second category, "Personally in charge" and "Others". The contract management device 10 accepts the user's selection of the first category and the second category. As shown in Figure 20, the extended information display area 102 displays extended information in conjunction with the first category and the second category selected by the tab 101. The extended information display area 102 has, for example, a contract number item, an electronic signature service item, a contract status item, a contract requester item, and a contract recipient item, etc. The following description is an example when a user with email address B1@B.COM is logged in to the contract management device 10. Note that in the tenant with tenant number T002 to which the user B1@B.COM belongs, there is a user B2@B.COM belonging.

[0146] Figure 20 is an example when the tab 101 has "Contracts created by the company" and "Personally in charge" selected. The contract management device 10 causes the extended information of contract number 002 to be displayed in the extended information display area.

[0147] Figure 21 is an example when the tab 101 has "Shared contracts" and "Personally in charge" selected. The contract management device 10 causes the extended information of contract number 001 and contract number 003 to be displayed in the extended information display area.

[0148] FIG. 22 shows an example when the tab 101 has "Shared Contracts" and "Others" selected. The contract management device 10 causes the extended information of contract number 004 to be displayed in the extended information display area. That is, for a user with the email address B1@B.COM which is in the same domain as the email address of the user of B2@B.COM, the contract management device 10 enables the user to use the extended information of the user of B2@B.COM. In other words, when the user of B2@B.COM is the second user 95, the contract management device 10 enables a user with an email address in the same domain as the email address of the second user 95 to use the extended information of the second user 95.

[0149] (Modification example) As described above, the contract management device 10 of the first and second embodiments has been described. However, the present disclosure is not limited to the above embodiments. Various improvements or modifications are possible.

[0150] In step S114 of FIG. 7, regardless of whether the email address of the second user 95 included in the contract information exists in the user table, the CPU 11 stores the contract information and the like. The same applies to step S128 of FIG. 8 and step S138 of FIG. 9. As a result, contract information is accumulated even for contracts before the user registration of the second user 95. For example, contract information of contract number 002 with the contract recipient being D1@D.COM is stored in the common table of FIG. 12. On the other hand, since D1@D.COM does not exist in the user table of FIG. 18, the user of D1@D.COM is not user-registered. When the user of D1@D.COM performs user registration, the user of D1@D.COM can use contract number 002.

[0151] Regarding step S324 in FIG. 16, the CPU 11 may acquire tenant information that is the same domain as the domain of the email address of the second user 95. Hereinafter, the case where the tenant table has the content shown in FIG. 23 will be described. FIG. 23 is an example of a tenant table. The domains of tenant number T002A and tenant number T002B are both B.COM. When the logged-in user is a user of B1@B.COM, the CPU 11 acquires the tenant information of tenant number T002A and tenant number T002B. Then, in step S326, the extended information of the user of tenant number T002A and the extended information of the user of tenant number T002B are acquired. That is, the contract management device 10 enables a user with an email address in the same domain as the email address of the contract request destination to use the extended information.

[0152] The contract management device 10 of each of the above embodiments may limit the range of extended information by the access authority of the database instead of various flags. The access authority of the database is the authority to control access such as viewing for each user in units of tables, records, or columns. That is, instead of the contract sharing flag, access authority is granted to each user for the records of the common table. For example, in FIG. 12, the contract management device 10 grants access authority to the records of contract number 001 to the users of A1@A.COM and B1@B.COM.

[0153] FIG. 24 is a schematic diagram of the process of acquiring contract information and the like from the URL of the contract management device 10 according to each of the above embodiments. The contract management device 10 according to each of the above embodiments acquires contract information and the like from the electronic signature service 7 through the API using the authentication information of the first user 90. On the other hand, the contract management device 10 described in FIG. 24 acquires contract information and the like from the URL described in the email without using the API. Thereby, the contract management device 10 can acquire the information that the second user 95 can acquire through the electronic signature service 7 without using the authentication information of the first user 90. The process of obtaining contract information and the like from the URL described in the e-mail notifying the completion of signature will be described in the order of the processes indicated by arrow Y21 to arrow Y27. Arrow Y21 indicates the process in which the first user 90 uses the terminal device 91 to request a contract with the second user 95 from the electronic signature service 7. Arrow Y22 indicates the process in which the electronic signature service 7 requests a signature from the second user 95. Arrow Y23 indicates the process in which the second user 95 uses the terminal device 96 to perform a signature on the electronic signature service 7. Arrow Y24 indicates the process in which the electronic signature service 7 sends an e-mail for notifying the completion of signature to the mail server 50. That is, the electronic signature service 7 sends an e-mail to the mail server 50. Arrow Y25 indicates the process in which the mail server 50 forwards an e-mail for notifying the completion of signature to the second user 95. Arrow Y26 indicates the process in which the mail server 50 forwards an e-mail for notifying the completion of signature to the contract management device 10. That is, the contract management device 10 obtains an e-mail from the mail server 50 by POP or the like. Arrow Y27 indicates the process in which the contract management device 10 obtains contract information and the like from the electronic signature service 7. That is, the contract management device 10 obtains the URL described in the e-mail. Then, the contract management device 10 obtains contract information and the like from the website.

[0154] The above processing can also be realized by a dedicated hardware circuit. In this case, it may be executed by one piece of hardware or by a plurality of pieces of hardware.

[0155] In each of the above embodiments, the processor refers to a processor in a broad sense, including a general-purpose processor (e.g., CPU: Central Processing Unit, etc.) and a dedicated processor (e.g., GPU: Graphics Processing Unit, ASIC: Application Specific Integrated Circuit, FPGA: Field Programmable Gate Array, programmable logic device, etc.).

[0156] Also, the operation of the processor in each of the above embodiments may be achieved not only by one processor but also by a plurality of physically separated processors cooperating with each other. Also, the order of each operation of the processor is not limited to the order described in each of the above embodiments and may be changed as appropriate.

[0157] Also, the program for operating the contract management device 10 may be provided by a computer-readable recording medium such as a USB (Universal Serial Bus) memory, a flexible disk, a CD-ROM (Compact Disc Read Only Memory), etc., or may be provided online via a network such as the Internet. In this case, the program recorded on the computer-readable recording medium is usually transferred and stored in a memory or a storage, etc. Also, this program may be provided, for example, as a single application software or may be incorporated into the software of each device as a function of the contract management device 10.

Explanation of Signs

[0158] 1 Contract management system 7 Electronic signature service 10 Contract management device 20 WEB server 30 Contract storage 40 Contract management database 50 Mail server 75 Contract 76 Signature area 90 First user 91 Terminal device 92 Company A 95 Second user 96 Terminal device 97 Company B 100 Extended information display screen 101 Tab 102 Extended information display area

Claims

1. An information processing apparatus comprising a processor, wherein the processor mediates a contract between a first user who is a contract requester and a second user who is a contract recipient so that the first user can use an electronic signature service to contract with the second user, and uses the authentication information of the first user for using the electronic signature service to obtain contract information regarding the contract from the first user to the second user from the electronic signature service, creates extension information other than information that can be obtained by the second user through the electronic signature service using the obtained contract information, and makes the created extension information available to the second user.

2. wherein the processor accumulates the obtained contract information, and makes the contract information including the extension information among the accumulated contract information available to the second user. The information processing apparatus according to claim 1.

3. wherein the processor further obtains contract information regarding a contract from a third user to the second user from the electronic signature service using the authentication information of the third user who is a contract requester of another contract, and makes the contract information including the extension information among the contract information with the first user or the third user as the contract requester available to the second user. The information processing apparatus according to claim 2.

4. wherein the processor makes the extension information within the range specified by the first user available to the second user. The information processing apparatus according to any one of claims 1 to 3.

5. wherein the processor authenticates a user using identification information, Enabling the use of the extended information of the contract information including the identification information used for the authentication as the identification information of the second user. The information processing apparatus according to any one of claims 1 to 4.

6. The processor is The identification information is the e-mail address of the user, and enables the use of the extended information of the contract information including the e-mail address as the e-mail address of the second user. The information processing apparatus according to claim 5.

7. The processor is Enabling a user with an e-mail address in the same domain as the e-mail address of the second user to use the extended information. The information processing apparatus according to claim 6.

8. An information processing apparatus comprising a processor, The processor is Mediating the contracts between the first user and the second user, and between the third user and the second user so that the first user who is the contract requester and the third user who is the contract requester of another contract can contract with the second user who is the contract recipient using an electronic signature service, and Using the authentication information of the first user for using the electronic signature service to obtain contract information regarding the contract from the first user to the second user from the electronic signature service, and using the authentication information of the third user to obtain contract information regarding the contract from the third user to the second user from the electronic signature service, Creating extended information other than the information that the second user can obtain through the electronic signature service using each of the obtained contract information, Making the second user available for the contract information with the first user or the third user as the contract requester, including the created extended information. Information processing apparatus.

9. An information processing apparatus comprising a processor, The processor is To enable a first user who is a contract requester to conclude a contract with a second user who is a contract recipient using an electronic signature service, the contract between the first user and the second user is mediated, and Using the authentication information of the first user for using the electronic signature service, contract information regarding the contract from the first user to the second user is obtained from the electronic signature service, Using the obtained contract information, extension information other than the information that the second user can obtain through the electronic signature service is created, The second user is made able to use the extension information of the contract information in which the identification information used for user authentication when logging in to the electronic signature service is included as the identification information of the second user, An information processing apparatus.

10. To enable a first user who is a contract requester to conclude a contract with a second user who is a contract recipient using an electronic signature service, the contract between the first user and the second user is mediated, and Using the authentication information of the first user for using the electronic signature service, contract information regarding the contract from the first user to the second user is obtained from the electronic signature service, Using the obtained contract information, extension information other than the information that the second user can obtain through the electronic signature service is created, The second user is made able to use the created extension information, An information processing program for causing a computer to execute the process.

11. To enable a first user who is a contract requester and a third user who is a contract requester of another contract to conclude a contract with a second user who is a contract recipient using an electronic signature service, the contracts between the first user and the third user and the second user are mediated, and Using the authentication information of the first user for using the electronic signature service, obtain contract information regarding the contract from the first user to the second user from the electronic signature service, and using the authentication information of the third user, obtain contract information regarding the contract from the third user to the second user from the electronic signature service. Using each of the obtained contract information, create extended information other than the information that the second user can obtain through the electronic signature service. Among the contract information with the first user or the third user as the contract requester, including the created extended information, make it available to the second user. An information processing program for causing a computer to execute the processing.

12. In order for the first user, who is the contract requester, to be able to conclude a contract with the second user, who is the contract recipient, using the electronic signature service, mediate the contract between the first user and the second user, Using the authentication information of the first user for using the electronic signature service, obtain contract information regarding the contract from the first user to the second user from the electronic signature service. Using the obtained contract information, create extended information other than the information that the second user can obtain through the electronic signature service. Make the extended information of the contract information, in which the identification information used for user authentication when logging in to the electronic signature service is included as the identification information of the second user, available to the second user. An information processing program for causing a computer to execute the processing.

Images