Program, method, information processing device

Abstract

To solve the problem that it extremely takes in the management of information on an electronic contract to a user of an electronic contract service because various electronic contract services exist.SOLUTION: A program for operating a computer, makes a processor of the computer execute the steps for: acquiring a message transmitted to a first user; and notifying a second user different from the first user of prescribed notification in the case that a message is issued by a specific electronic contract service and performs a conclusion request before concluding a contract by the specific electronic contract service.SELECTED DRAWING: Figure 9

Description

[Technical field]

[0001] The present disclosure relates to a program, a method, and an information processing device. [Background technology]

[0002] In business activities, various agreements and applications are approved both inside and outside the company to advance the business. For example, within a business, an approver makes decisions on the contents that need to be approved. In addition, with regard to contracts both inside and outside a business, in recent years, advances in IT technology have meant that contracts that were previously concluded on paper are gradually being converted to electronic contracts.

[0003] In electronic contracts, users of electronic contract services electronically sign the contract documents to be signed. Electronic contract services are provided by businesses in various formats, including the so-called party signature type and the so-called business signature type (witness type). When a contract is concluded using an electronic contract service, the parties may be able to view the contract document between themselves using information that identifies the parties. For example, when an email address is used to identify the parties, one of the parties who wants to enter into a contract sends the contract to the electronic contract service with the email address of the other party specified. The person who receives the contract then uses the electronic contract service to approve the contract, and so on, thereby proceeding with the conclusion of the electronic contract.

[0004] The following JP 2023-147212 A (Patent Document 1) describes a technology for supporting the management of information related to electronic contracts. According to one aspect of Patent Document 1, an information processing system is provided. This information processing system includes a control unit. The control unit is configured to execute a first acquisition step, a second acquisition step, and a linking step. In the first acquisition step, an e-mail related to an electronic contract realized by an electronic contract service is acquired. In the second acquisition step, contract-related information is acquired from the acquired e-mail. The contract-related information is information related to an electronic contract. In the linking step, the acquired contract-related information is linked to case management information. The case management information is information related to a case managed using an electronic contract. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2023-147212 A Summary of the Invention [Problem to be solved by the invention]

[0006] There are many different electronic contract services available for the conclusion of electronic contracts. For this reason, it is a hassle for users of these services to manage information related to electronic contracts. [Means for solving the problem]

[0007] One embodiment described in the present disclosure is a program for operating a computer, the program causing a processor of the computer to execute the steps of acquiring a message sent to a first user, and, if the message was issued by a specific electronic contract service and is for requesting conclusion of a contract prior to the conclusion of the contract through the specific electronic contract service, sending a predetermined notification to a second user different from the first user. Effect of the Invention

[0008] According to the present disclosure, users of electronic contract services can prevent contracts from being concluded through electronic contract services that do not adopt the standard. This makes it easier for users of electronic contract services to manage contracts. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a block diagram showing the overall configuration of the system 1. [Diagram 2] FIG. 2 is a block diagram showing the functional configuration of first device 10. As shown in FIG. [Diagram 3] FIG. 3 is a block diagram showing the functional configuration of the server 20 of the first electronic contract service. [Figure 4] FIG. 4 is a conceptual diagram for explaining an electronic contract. [Diagram 5] FIG. 5 is a diagram showing the data structure of the database 2021 of document data. [Figure 6] FIG. 6 is a diagram showing the data structure of the document management database 2022. As shown in FIG. [Figure 7] FIG. 7 is a diagram showing the data structure of the user database 2023. As shown in FIG. [Figure 8] FIG. 8 is a diagram showing the data structure of the message database 2024. As shown in FIG. [Figure 9] FIG. 9 is a diagram showing a process flow relating to a message. [Figure 10] FIG. 10 is a diagram showing a process flow relating to a message. [Figure 11] FIG. 11 is a diagram showing a process flow relating to fastening. [Figure 12] FIG. 12 is a diagram showing a process flow regarding an approver's proposal. [Figure 13] FIG. 13 shows a screen relating to receiving a message. [Figure 14] FIG. 14 shows a screen relating to receiving a message. [Figure 15] FIG. 15 is a diagram showing information related to a message on a screen in the first electronic contract service. [Figure 16] FIG. 16 is a diagram showing information related to a message on a screen in the first electronic contract service. [Figure 17] FIG. 17 is a diagram showing information regarding conclusion on a screen in the first electronic contract service. [Figure 18] FIG. 18 is a diagram showing information regarding conclusion on a screen in the first electronic contract service. [Figure 19] FIG. 19 is a diagram showing a screen relating to an approver's proposal in the first electronic contract service. [Figure 20] FIG. 20 is a diagram showing information on a screen relating to a document that objectively certifies that an electronic contract has been exchanged. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] The following describes an embodiment of the present disclosure. The embodiment of the present disclosure will be described with reference to the drawings. In addition, in the description of the embodiment of the present disclosure, the same components are denoted by the same reference numerals. Their names and functions are also the same. Therefore, detailed descriptions thereof will not be repeated.

[0011] <Outline of the first embodiment> In this embodiment, a user who uses the system 1 operates a PC (Personal Computer) or the like to manage document data such as contracts.

[0012] Document data such as contracts are classified into the following types, for example: The following are examples, but are not limited to these. ·Confidentiality agreement Rental agreement Real estate purchase and sale contracts Land lease agreement ·Sales contract · Goods rental contract Employment contract · Labor dispatch contract · Service contract · Transfer of security agreement M&A contracts Business transfer agreement ·Joint Venture Agreement · Software Development Contract Intellectual property agreements (license agreements, etc.) Copyright Transfer Agreement ·Trademark license agreement License Agreement Franchise agreement ·Minutes of Board of Directors Meetings -Product manufacturing contract ·Contract regarding architectural drawings ·Construction contract Insurance contract Consulting Agreement Agency Agreement

[0013] Document data such as a contract may include, for example, the following information: The following are examples, but are not limited to these. The subject matter and purpose of the contract The contract contains a section describing the subject matter and purpose of the contract. For example, if the contract is for the purchase of a property, the contents include the address of the property, the purpose of the property, the purchase price, and the payment terms. · Terms and conditions of the contract; The contract contains the terms and conditions of the contract. For example, if the contract is a property purchase contract, the contents include the time of delivery, the method of delivery, the buyer's obligations, the buyer's responsibilities, and the seller's guarantees. Signature and date information Contracts may contain information such as signatures and dates that are important in determining the validity and timing of a contract.

[0014] An electronic contract service is a service that manages contracts. Specifically, it manages information such as who operated what, when, and at what point in time document data such as contracts held by the parties is operated. Electronic contract services also have a function for managing document data agreed upon between the parties. For example, electronic contract services can manage information regarding the validity period of an electronic signature affixed to a contract. In this way, in addition to the basic function of managing contracts, electronic contract services also support the sharing of information about contracts between the parties.

[0015] In the present embodiment, it is also assumed that a user operates a PC (Personal Computer) and concludes a contract using an electronic contract service. In this embodiment, an electronic contract refers to exchanging electronic data of a contract that has been digitized on the Internet, the contracting parties expressing their intention to agree, and attaching an electronic signature to the electronic data of the contract. A contract is typically created using document creation software and is an electronic data file whose contents cannot be altered. Electronic data includes, for example, PDF files. The contracting parties include a contract sender and a contract receiver. An electronic contract has one or more approvers who approve the contract. The approver determines whether or not the contract can be concluded under the conditions indicated in the contents of the contract based on the contract. When a contract is concluded between the parties using the electronic contract service, the electronic contract service may manage the contract data related to the agreement.

[0016] <1.1 Overall system configuration> Fig. 1 is a block diagram showing an example of the overall configuration of a system 1 according to the present embodiment. As shown in Fig. 1, the system 1 includes a first device 10, a server 20 for a first electronic contract service, a server 30 for a third electronic contract service, a second device 70, a server 90 for a second electronic contract service, and a mail server 100. In the system 1, the first device 10, the server 20 for the first electronic contract service, the server 30 for the third electronic contract service, the second device 70, the server 90 for the second electronic contract service, and the mail server 100 are connected to each other via a network 80 so as to be able to communicate with each other.

[0017] The example in FIG. 1 shows a first device 10. The first device 10 indicates a device used by a first user. The first user refers to a user who uses the system 1. In this embodiment, the first user refers to a user who mainly uses the first electronic contract service in the system 1. The first device 10 is realized by, for example, a PC, a smartphone, etc. The first device 10 executes a program to provide the first user with an environment for operating the system 1 according to the program.

[0018] The first device 10 is assumed to be a device that accepts an input operation from a first user.

[0019] The first device 10 includes a communication IF (Interface) 12 , an input device 13 , an output device 14 , a memory 15 , a storage unit 16 , and a processor 19 .

[0020] The communication IF 12 is an interface for inputting and outputting signals so that the first device 10 can communicate with an external device.

[0021] The input device 13 is a device for receiving an input operation from a first user. The device for receiving an input operation is, for example, a touch panel, a touch pad, a pointing device such as a mouse, or a keyboard.

[0022] The output device 14 is a device (such as a display or a speaker) for presenting information to the first user.

[0023] The memory 15 is for temporarily storing programs, data to be processed by the programs, etc. The memory 15 is, for example, a volatile memory such as a DRAM (Dynamic Random Access Memory).

[0024] The storage unit 16 is for storing data and is, for example, a flash memory or a hard disk drive (HDD).

[0025] The processor 19 is hardware for executing an instruction set written in a program, and is composed of an arithmetic unit, a register, peripheral circuits, and the like.

[0026] The example of Fig. 1 illustrates a first electronic contract service server 20. Hereinafter, the first electronic contract service server 20 may be abbreviated to server 20.

[0027] The server 20 includes a communication IF 22 , an input / output IF 23 , a memory 25 , a storage 26 , and a processor 29 .

[0028] The communication IF 22 is an interface for inputting and outputting signals so that the server 20 can communicate with external devices.

[0029] The input / output IF 23 functions as an interface with an input device for receiving an input operation from a user and an output device for presenting information to the user.

[0030] The memory 25 is for temporarily storing programs, data to be processed by the programs, etc. The memory 25 is, for example, a volatile memory such as a DRAM (Dynamic Random Access Memory).

[0031] The storage 26 is for storing data and is, for example, a flash memory or a hard disk drive (HDD).

[0032] The processor 29 is hardware for executing an instruction set written in a program, and is composed of an arithmetic unit, a register, peripheral circuits, and the like.

[0033] The server 20 is a device that manages information on users who use the first electronic contract service, information on document data, and the like.

[0034] The server 20 transmits data necessary for using the document management service to the first device 10 as appropriate, thereby visualizing the status of the document management service on the first device 10. The server 20 also communicates with the first device 10, and transmits images, files, text data, and the like to the first device 10 in response to operations by each user. Similarly, the server 20 transmits data necessary for using the document management service to the second device 70 as appropriate, thereby visualizing the status of the document management service on the second device 70. The server 20 also communicates with the second device 70, and transmits images, files, text data, and the like to the second device 70 in response to operations by each user.

[0035] The example of Fig. 1 illustrates a third electronic contract service server 30. Hereinafter, the third electronic contract service server 30 may be abbreviated to server 30. The third electronic contract service is an electronic contract service different from the first electronic contract.

[0036] The server 30 includes a communication IF 32 , an input / output IF 33 , a memory 35 , a storage 36 , and a processor 39 .

[0037] The communication IF 32 is an interface for inputting and outputting signals so that the server 30 can communicate with external devices.

[0038] The input / output IF 33 functions as an interface with an input device for receiving an input operation from a user and an output device for presenting information to the user.

[0039] The memory 35 is for temporarily storing programs, data to be processed by the programs, etc. The memory 35 is, for example, a volatile memory such as a DRAM (Dynamic Random Access Memory).

[0040] The storage 36 is for storing data and is, for example, a flash memory or a hard disk drive (HDD).

[0041] The processor 39 is hardware for executing an instruction set written in a program, and is composed of an arithmetic unit, a register, peripheral circuits, and the like.

[0042] The server 30 is a device that manages information on users who use the third electronic contract service, information on document data, and the like.

[0043] The functional configuration of the server 30 is the same as the functional configuration of the server 20 of the first electronic contract service described below, and therefore a description of the functional configuration of the server 30 will be omitted.

[0044] The example of FIG. 1 shows a second device 70. The second device 70 indicates a device used by a second user. The second user refers to a user who uses the system 1. In this embodiment, the second user refers to a user who mainly uses the first electronic contract service in the system 1. The second user refers to a user who uses the system 1 and is different from the first user. In this embodiment, there are some parts where a specific example is explained in which the second user is the boss of the first user. Note that the second user does not have to be a user who works in the same company as the first user. The second device 70 is realized by, for example, a PC, a smartphone, etc. The second device 70 executes a program to provide the second user with an environment for operating the system 1 according to the program.

[0045] The functional configuration of the second device 70 is the same as the functional configuration of the first device 10 described below. Therefore, the description of the functional configuration of the second device 70 will be omitted.

[0046] The example of Fig. 1 illustrates a second electronic contract service server 90. Hereinafter, the second electronic contract service server 90 may be abbreviated to server 90. The second electronic contract service is an electronic contract service different from the third electronic contract. The functional configuration of the server 90 is the same as the functional configuration of the server 20 of the first electronic contract service described below, and therefore a description of the functional configuration of the server 90 will be omitted.

[0047] The example in Fig. 1 shows a mail server 100. The mail server 100 is a server that manages the sending and receiving, storage, forwarding, etc. of mail. In this embodiment, the mail server 100 may also manage mails sent and received from each electronic contract service.

[0048] <1.2 Functional configuration of the first device 10> 2 is a diagram showing a functional configuration of the first device 10. The first device 10 includes an antenna 111, a first wireless communication unit 121, a processor 19, an operation reception unit 130, a storage unit 16, a memory 15, a display 132, an audio processing unit 140, a microphone 141, and a speaker 142.

[0049] Antenna 111 radiates the signal emitted by first device 10 into space as a radio wave. Antenna 111 also receives the radio wave from space and provides the received signal to first wireless communication unit 121.

[0050] The first wireless communication unit 121 performs modulation / demodulation processing and the like for transmitting and receiving signals via the antenna 111 and the like so that the first device 10 can communicate with other communication devices. The first wireless communication unit 121 is a communication module for wireless communication including a tuner, a high-frequency circuit, and the like, and performs modulation / demodulation and frequency conversion of wireless signals transmitted and received by the first device 10, and provides the received signals to the processor 19.

[0051] The processor 19 reads and executes a program stored in the storage unit 16 to control the operation of the first device 10. The processor 19 is realized by, for example, an application processor.

[0052] The operation reception unit 130 has a mechanism for receiving an input operation by a user. For example, the operation reception unit 130 is realized as a pointing device such as a mouse, a touch pad, or a touch panel, a keyboard, a controller, a photographing means for sensing the end user's body movement as an input operation, or the like. For example, the operation reception unit 130 senses the movement of a body part such as a hand, the end user's facial expression, or the like as the end user's body movement, and receives the movement of these body parts, or the like, as an input operation. The operation reception unit 130 determines the type of operation, such as whether the end user's operation is a flick operation or a tap operation, based on the coordinates at which the end user touches a finger on a touch panel or the like to receive the input operation.

[0053] The storage unit 16 is configured with a flash memory, a RAM (Random Access Memory), etc. The storage unit 16 also stores programs used by the first device 10, various data received by the first device 10 from the server 20, etc.

[0054] The display 132 displays data such as images, videos, and text under the control of the processor 19. The display 132 is realized by a display device such as an LCD (Liquid Crystal Display) or an organic EL (Electro Luminescence) display.

[0055] The audio processing unit 140 modulates and demodulates an audio signal. The audio processing unit 140 modulates a signal provided from a microphone 141, and provides the modulated signal to the processor 19. The audio processing unit 140 also provides the audio signal to a speaker 142.

[0056] The microphone 141 receives a voice input and provides the voice processor 140 with a voice signal corresponding to the voice input.

[0057] The speaker 142 converts the audio signal provided from the audio processor 140 into audio, and outputs the audio to the outside of the first device 10.

[0058] The processor 19 operates according to a program to thereby fulfill the functions of an input operation reception unit 191, a transmission / reception unit 192, a data processing unit 193, and a notification control unit 194. The input operation reception unit 191 performs processing to receive a user's input operation to an input device such as the operation reception unit 130. When the operation reception unit 130 is, for example, a touch device, the input operation reception unit 191 determines the type of operation, such as whether the user's operation is a flick operation or a tap operation, based on information on the coordinates where the user touches the touch device with a finger or the like. The transmission / reception unit 192 performs processing for the first device 10 to transmit and receive data to and from an external device such as the server 20 in accordance with a communication protocol. Data processing unit 193 performs a process of performing calculations on data that first device 10 accepts as input in accordance with a program, and outputs the calculation results to a memory or the like. The notification control unit 194 performs processing for presenting information to the user, such as processing for displaying a display image on the display 132, processing for outputting sound to the speaker 142, and processing for causing a vibrator or the like to generate vibrations.

[0059] <1.3 Functional configuration of the server 20 of the first electronic contract service> 3 is a diagram showing the functional configuration of the server 20 of the first electronic contract service. As shown in FIG. 3, the server 20 fulfills the functions of a communication unit 201, a storage unit 202, and a control unit 203.

[0060] The communication unit 201 performs processing for the server 20 to communicate with external devices.

[0061] The storage unit 202 stores various databases such as a document data database 2021, a document management database 2022, a user database 2023, a message database 2024, and the like.

[0062] The document data database 2021 is a database for managing information on the document data in the first electronic contract service. Details will be described later.

[0063] The document management database 2022 is a database for managing information on the parties in the document data in the first electronic contract service. Details will be described later.

[0064] The user database 2023 is a database for managing information on users who use the first electronic contract service. Details will be described later.

[0065] The message database 2024 is a database for managing information on messages in the first electronic contract service. Details will be described later.

[0066] The control unit 203 is realized by the processor 29 reading a program stored in the storage unit 202 and executing instructions included in the program. The control unit 203 performs functions shown as a reception control module 2031 and a transmission control module 2032 by operating according to the program.

[0067] The reception control module 2031 controls the process in which the server 20 receives a signal from an external device in accordance with a communication protocol.

[0068] The transmission control module 2032 controls the process in which the server 20 transmits signals to external devices in accordance with a communication protocol.

[0069] <1.4 Conceptual diagram to explain electronic contracts> Fig. 4 is a conceptual diagram for explaining an electronic contract. As shown in Fig. 4, the system for electronic contracts includes a device 40 of a user who is a contract sender, a server 50 of a contract management service, and a device 60 of a user who is a contract recipient.

[0070] First, the contract sender uploads the contract to the contract management service server 50 on the cloud by operating the contract sender's user device 40. The contract management service server 50 affixes the contract sender's digital signature to the contract that the contract sender has agreed to send.

[0071] The contract sender performs an operation to request the contract receiver to conclude an agreement. Specifically, the device 40 of the user of the contract sender accepts an operation to designate a contract receiver from the contract sender, and transmits the operation to the contract management service server 50. In this embodiment, the device 40 of the user of the contract sender accepts an operation to designate the email addresses of one or more contract receivers from the contract sender as information identifying the contract receiver. The contract management service server 50 sends information for accessing the contract to the contract recipient, addressed to the recipient's email address specified by the contract sender's user. In this embodiment, the contract management service server 50 sends information for accessing the contract to the contract recipient's device 60, addressed to the recipient's email address specified by the contract sender's user. The information for accessing the contract includes, for example, a link described as a URL (Uniform Resource Locator), etc.

[0072] The contract recipient performs an operation (click, tap, etc.) to specify information for accessing the received contract on the contract recipient's user device 60, and can confirm the contents of the contract on the contract management service server 50 online and enter into an agreement. The contract recipient's user device 60 presents a screen for accepting an operation indicating agreement to the contract to the user of the contract recipient's user device 60, and accepts an operation for agreement from the contract recipient. If there is any defect in the contract contents at this stage, the server 50 of the contract management service may accept an operation from the contract recipient indicating that the contract is not agreed to.

[0073] The contract management service server 50, upon receiving an operation from the contract recipient agreeing to the contract, affixes the contract recipient's digital signature to the contract. The contract management service server 50 stores the contract in a database that manages the contract. Tampering with the contract is prevented by affixing digital signatures from both contracting parties.

[0074] This embodiment realizes such a cloud-based electronic contract service.

[0075] <2 Data Structure> 5, 6, 7, and 8 are diagrams showing the data structures of the databases stored in the server 20. In FIG. Note that Figures 5, 6, 7, and 8 are merely examples and do not exclude data not shown.

[0076] 5 is a diagram showing the data structure of the document data database 2021. The document data database 2021 is a database for managing information on the document data. Each record in the document data database 2021 in Figure 5 includes the items "Document Data ID", "Title", "Link", "Contract Conclusion Date", "Contract Start Date", "Contract End Date", and "Message ID".

[0077] The item "document data ID" indicates a unique ID for the document data, which is necessary when managing the document data in the first electronic contract service. For example, the identification information of the document data includes unique information associated with the document data and issued by the server 20 when the server 20 accepts upload of the document data as the subject of the electronic contract. The unique information associated with the document data and issued is, for example, identification information issued to the document data, link information for each terminal device to access the document data, etc. The document data is, for example, a contract. A contract is typically created using document creation software and is a file whose contents cannot be altered. The contract is, for example, a PDF file. The advantage of document data IDs is that they make it easy to search, reference, and manage documents. For example, even if there is a large number of contracts, the document data ID makes it possible to quickly identify the necessary document data. Document data IDs are also used for version management, authority management, etc. of document data.

[0078] The item "Title" indicates the title of the document data. The title is a concise name that represents each document data. An example of the title of the document data may be, for example, a name that indicates the type of contract. Examples of the title of the document data are "Confidentiality Agreement.pdf", "Contract regarding Architectural Blueprints.pdf", etc.

[0079] The item "Link" indicates a link to a cloud or the like that stores the document data. By following the link, the server 20 can refer to information about the file of the document data.

[0080] The item "contract conclusion date" indicates the date on which the document data was concluded.

[0081] The item "contract start date" indicates the date on which the contract for the document data started.

[0082] The item "contract termination date" indicates the date on which the contract for the document data ended.

[0083] The item "message ID" is a unique ID required for managing messages in the first electronic contract service. The message is, for example, received by email, SMS, chat app, etc. The information contained in the message will be described in detail later in the message database 2024.

[0084] 6 is a diagram showing the data structure of the document management database 2022. The document management database 2022 is a database for managing information on the parties involved in document data. Each record of the document management database 2022 in FIG. 6 includes an item "document management ID", an item "document data ID", an item "sender", an item "recipient", and an item "approver".

[0085] The item "document management ID" indicates identification information for each contract concluded by electronic contract, for example, issued by the server 20. Specifically, the item "document management ID" is a unique ID for each electronic contract that is required when managing each contract concluded by electronic contract between users.

[0086] The item "Document Data ID" is as explained above.

[0087] The item "sender" is an item that indicates information about the sender of the contract in the first electronic contract service. In addition, there are cases where the sender of the contract is not just one person but multiple people.

[0088] The item "recipient" is an item that indicates information about the recipient of the contract in the first electronic contract service. Note that there may be cases where the recipient of the contract is not one person but multiple people.

[0089] The item "Approver" indicates information about the approver in the contract. Note that there may be more than one approver.

[0090] 7 is a diagram showing the data structure of the user database 2023. The user database 2023 is a database for managing information on users who use the first electronic contract service. Each record in the user database 2023 in FIG. 7 includes the items "user ID", "email address", "name", "company name", "department", and "position".

[0091] The item "user ID" indicates a unique ID for a user that is required when managing users of the first electronic contract service in the first electronic contract service. User IDs can take various forms, such as a combination of character strings, a combination of numbers and character strings, an email address, etc. In general, it is important that user IDs are unique within a system, and they are designed to prevent duplication. For example, in the first electronic contract service, when issuing an account to a user of the first electronic contract service, the first device 10 accepts an input for registering an email address from the user of the first electronic contract service. In response to accepting the input for registering an email address, the server 20 issues a user ID.

[0092] The item "email address" is the email address of a user who uses the first electronic contract service. An email address refers to an address required to send and receive emails.

[0093] The item "name" represents information about the user's name.

[0094] The item "Company Name" indicates the name of the company to which the user belongs. The company name is one piece of information for identifying a user, and if multiple users belong to the same company, they can be grouped and statistically processed based on the company name.

[0095] The item "department" represents information about the department of the company to which the user belongs. An item representing department information is one piece of information for identifying a user, and also includes information about the user's business operations. The item "department" is, for example, the development department, security department, accounting department, intellectual property department, etc.

[0096] The item "position" indicates the role and job of the user in the company to which the user belongs. The position is one piece of information for identifying the user, and also includes information regarding the user's skills and work content. The item "position" is, for example, department manager, section manager, CEO, etc.

[0097] 9 is a diagram showing the data structure of the message database 2024. The message database 2024 is a database for managing information related to messages. Each record in the message database 2024 of Figure 9 includes the items "Message ID", "Subject", "Body", "Issuer", "Destination", "File", "Electronic Signature", "Timestamp", and "Received Date and Time".

[0098] The item "Message ID" is as explained above.

[0099] The item "Subject" indicates the subject of a message. The subject of a message is a concise name that represents the content of the message. Examples of the "Subject" item include the following. The following are examples and are not limited to these. "We have received a signature request from XXX service." "Signature Request Notice" "Notice regarding request for conclusion" "Notice regarding conclusion from electronic contract XXX service"

[0100] The item "Body" refers to the body of the message. If the body of the message is related to a request for a contract, it may contain the following information. The following are examples and are not limited to these. - A request to sign a message Information about who sent the message Information about the recipient of the message Contract information

[0101] The item "issuer" indicates information about the issuer of the message. The information about the issuer of the message may include the following information. The following are examples and are not limited to these. Issuer email address information Information about the issuing domain Information about the publisher's service name

[0102] The item "Destination" indicates information about the destination of the message. The destination information of the message may include the following information. The following is an example, but is not limited to this. Recipient email address information Information about the destination domain

[0103] The item "file" indicates information about a file attached to a message. If the file attached to a message is related to a request for a contract, it is, for example, document data such as a contract.

[0104] The "digital signature" item indicates the digital signature information of the file attached to the message. Digital signature is a cryptographic technique to prove that a file has not been tampered with. Specifically, digital signatures make it possible to technically verify who approved what in specific document data.

[0105] The item "timestamp" indicates timestamp information of a file attached to a message. Timestamps are a technology that enables signature verification even after the validity period of the original electronic certificate has expired, by adding necessary information (such as revocation information) to document data bearing an electronic signature within the validity period of the electronic certificate and assigning a new timestamp. In electronic signatures, a certification authority verifies the identity of the person in question and issues a public key certificate. This public key certificate is paired with a private key, and since the private key is held by the person in question, there is a risk of loss, leakage, or changes to the person's attributes. For this reason, the validity period is generally several months to several years. As far as authentication is concerned, if it is possible to confirm it at the time, a short validity period is not a problem, but if it is necessary to be verifiable in the future, this cannot be achieved with electronic signatures alone. As for time stamps, the certification authority uses PKI technology to guarantee them, so the concept of the validity period is the same as above. However, since time stamps are issued to time stamp servers that strictly manage and operate private keys not by individuals but by businesses, public key certificates with relatively long validity periods can be issued. However, the longer the validity period of a time stamp, the more issues there are, such as loss, leakage, and changes to personal attributes. To solve this problem, the private key used to generate the timestamp is updated every year. The old private key is then discarded to ensure security. If the private key used to generate it is lost, the same timestamp cannot be reproduced. In this way, long-term signatures make it possible to verify the signature even after the validity period of the electronic certificate has expired.

[0106] The item "received date and time" indicates the date and time when the message was received. In this item, the year, month, and day when the message was received is recorded. For example, when a message is sent from a third electronic contract service to a first electronic contract service, the item “Received date and time” records the date and time when the message was received by the first electronic contract service.

[0107] <Operation of the First Embodiment> Next, the operation of each device constituting the system 1 will be described.

[0108] FIG. 9 is a diagram showing a process flow relating to a message.

[0109] In step S90101, the mail server 100 receives a message from the server 30. The message may be received, for example, by email, SMS, or a chat application.

[0110] As a premise, the server 30 may send a message to the first user before sending the message in step S90101.

[0111] In step S90102, the mail server 100 transfers the message to another electronic contract service (here, server 20) based on the transfer setting in the mail server 100.

[0112] In step S9021, the server 20 receives the message forwarded in step S90102.

[0113] In step S9022, the server 20 judges whether the message was issued by the server 30 and is for requesting conclusion of a contract before the contract is concluded by the third electronic contract service. For example, if the subject of the message contains "request for conclusion," it is judged to be for a request for conclusion.

[0114] In step S9023, the server 20 performs a predetermined notification to a second user different from the first user, depending on the result of the determination in step S9022.

[0115] In step S9071, the second device 70 receives a predetermined notification. In this way, if a first user receives a message requesting the conclusion of an electronic contract that the second user should also see, the second user can detect the message. For example, if the first user is a junior colleague in the same company and the second user is the first user's boss, the second user (the boss) can understand the message received by the first user before the contract is concluded.

[0116] FIG. 10 is a diagram showing a process flow relating to a message.

[0117] Step S9071 is as described above.

[0118] In step S10071, the second device 70 accepts an input of an operation indicating that a plurality of items of information related to a message are to be imported into the first electronic contract service. The plurality of items of information related to a message shall include at least two of the following: Message body Message subject Information about the message's origin Message destination information Information about files attached to messages - The date and time the message was received

[0119] In step S10072, the second device 70 transmits a plurality of items of information related to the message to the server 20 in response to the operation in step S10071.

[0120] In step S10021, the server 20 receives a plurality of items of information relating to the message.

[0121] In step S10022, server 20 executes processing such as importing information of multiple items related to the message received in step S10021 into message database 2024. Each record in message database 2024 includes, for example, an item "Message ID", an item "Subject", an item "Body", an item "Issuer", an item "Destination", an item "File", an item "Digital Signature", an item "Timestamp", and an item "Receipt Date and Time". For example, if electronic signature processing has already been performed by the third electronic contract service, the server 20 imports information about the electronic signature by the third electronic contract service into the "electronic signature" item of the message database 2024. Similarly, if timestamp processing has been performed by the third electronic contract service, the server 20 imports information about the timestamp by the third electronic contract service into the "timestamp" item of the message database 2024.

[0122] In step S10023, the server 20 presents a plurality of items of information related to the message in the first electronic contract service. The plurality of items of information related to the message may include the following information. The following are examples and are not limited to these. Message body Message subject Information about the message's origin Message destination information Information about files attached to messages - The date and time the message was received ·Statistical information regarding messages (e.g., information on how many messages were received for each electronic contract service) By doing this, users (first user, second user, etc.) who use the first electronic contract service can centrally manage contracts for messages and the like sent from various electronic contract services using one electronic contract service. Therefore, doing this makes it possible to reduce the effort required to manage information related to electronic contracts.

[0123] FIG. 11 is a diagram showing a process flow relating to fastening.

[0124] Step S10023 is as described above.

[0125] In step S11011, the first device 10 accepts an input of an operation to start a procedure for concluding the contract in the first electronic contract service for the contract request associated with the message. Note that a specific example of the screen in this case is described in FIG. 17 below.

[0126] In step S11021, the server 20 receives an input of an operation to start the conclusion procedure.

[0127] In step S11022, the server 20 presents a screen for performing the conclusion of the conclusion request. A specific example of the screen in this case is described in the following FIG.

[0128] In step S11012, the first device 10 accepts an input of an operation indicating that the contract is to be concluded. A specific example of this case is described in 1806 of Fig. 18 below. For example, the first device 10 accepts an input of an operation indicating that the first user agrees to the contents of the document after confirming the contents of the document.

[0129] In step S11023, the server 20 receives an input of an operation indicating that a conclusion is to be performed.

[0130] In step S11024, the server 20 executes the process of attaching an electronic signature and a time stamp in the first electronic contract service to the conclusion. The process of attaching an electronic signature and a time stamp is as described above. Note that attaching multiple electronic signatures to the same contract by multiple parties or businesses in this way is called overlapping electronic signatures. By applying multiple electronic signatures in this way, it becomes difficult to tamper with the contract, and the reliability of the contract increases. Therefore, by applying multiple electronic signatures in this way, it is possible to increase the legal credibility of the contract. In addition, by overlapping time stamps, it is possible to check the time the contract was created, the contract's change history, etc., which also makes it possible to improve the reliability of the contract.

[0131] FIG. 12 is a diagram showing a process flow regarding an approver's proposal.

[0132] Step S11022 is as described above.

[0133] In step S12021, the server 20 proposes incorporating a third user as an approver for the conclusion. The third user refers to a user who uses the system 1. In this embodiment, the third user refers to a user who mainly uses the first electronic contract service in the system 1. The third user refers to a user who uses the system 1 and is different from the first user and the second user. In this embodiment, the third user may be, for example, the boss of the first user. Note that the third user does not have to be a user who works in the same company as the first user. A specific example of a screen for proposing to include a third user as an approver for the conclusion is described below in Fig. 19. The server 20 may use a technique such as machine learning based on information on the past contract status, for example, to infer a user who is likely to be suitable as an approver, and may propose the user as an approver. The timing for proposing an approver does not have to be limited to the moment of conclusion.

[0134] In step S12011, the first device 10 accepts an input of an operation to add a third user to the approvers. A specific example of a screen in this case is described in FIG. 19 below. The first device 10 accepts an input of an operation to add a third user to the approvers, for example.

[0135] In step S12022, the server 20 receives an input of an operation for adding a third user to the approvers.

[0136] In step S12023, the server 20 executes a process of incorporating the third user into the approvers for the conclusion. Specifically, the server 20 updates the information in the item "Approver" of the document management database 2022 according to the information of the approver to be added.

[0137] <Screen example> FIG. 13 shows a screen relating to receiving a message.

[0138] As described in Fig. 9, the server 30 may send a message to the first user before sending the message in step S90101. Fig. 13 is an example of a screen example when the first device 10 accepts receipt of a message.

[0139] Specifically, the first device 10 presents the following information on the dialog screen 1300: Area 1301 is an area related to the login name on the mail screen. Area 1302 is an area related to the date and time when the email was received. An area 1303 is an area related to the subject of the email. The subject of the email is, for example, "A signature request has been received from XXX service." Area 1304 is an area related to the sender and destination of the mail. The sender of the mail is, for example, information on the email address of the sender of the mail. Similarly, the destination of the mail is, for example, information on the email address of the destination (recipient) of the mail. Area 1305 is an area related to the body of the email. Area 1306 is an area related to information about a file attached to the mail.

[0140] FIG. 14 shows a screen relating to receiving a message.

[0141] As described in step S9071, the second device 70 receives the predetermined notification from the server 20. Fig. 14 is an example of a screen example when the second device 70 accepts receipt of the predetermined notification.

[0142] Specifically, the following information is presented on a dialog screen 1400: Area 1301 is as explained above. Area 1302 is as explained above. Area 1303 is as explained above. Area 1304 is as explained above. Area 1305 is as explained above. Area 1306 is as explained above. An area 1401 is an area related to the forwarding date and time of the mail. Area 1402 is an area related to the subject of the forwarded mail. Area 1403 is an area related to the sender and destination of the forwarded mail. The button 1404 is a button for importing multiple items of information related to the message into the first electronic contract service. As described in step S10071, the second device 70 imports multiple items of information related to the message into the first electronic contract service in response to an input operation from the second user. Then, as described in step S10072, for example, in response to the second user pressing the button 1404, the second device 70 transmits the multiple items of information related to the message to the server 20.

[0143] FIG. 15 is a diagram showing information related to a message on a screen in the first electronic contract service.

[0144] As described in step S10023, the server 20 presents a plurality of items of information related to the message. Fig. 15 is an example of a screen example on which the server 20 presents a plurality of items of information related to the message.

[0145] Specifically, the second device 70 presents the following information on a dialog screen 1500: Area 1501 is an area related to a login name in the first electronic contract service. Area 1502 is an area showing specific information indicating a message. The specific information indicating a message is, for example, "Regarding message number #1126." Message number #1126 is, for example, an identification number assigned to each message. Area 1503 is an area that presents multiple items of information regarding the message.

[0146] FIG. 16 is a diagram showing information related to a message on a screen in the first electronic contract service.

[0147] As described in step S10023, the server 20 presents a plurality of items of information related to the message. Fig. 16 is an example of a screen example on which the server 20 presents a plurality of items of information related to the message.

[0148] Specifically, the second device 70 presents the following information on the dialog screen 1600: Area 1501 is as explained above. Area 1601 is an area that presents a dashboard in the first electronic contract service. The dashboard in the first electronic contract service presents, for example, statistical information and the like related to an electronic contract service different from the first electronic contract service. When presenting statistical information, the dashboard in the first electronic contract service may display the statistical information in a visually easy-to-understand format using tables, graphs, and the like. Area 1602 is an area that presents information on the target range, target period, etc., of the statistical information. Area 1603 is an area that presents statistical information regarding messages. For example, area 1603 presents information such as the number of received messages per electronic contract service, and the number of received messages that were concluded by the first electronic contract service. The button 1604 is a button for viewing detailed information about the dashboard in response to an input operation by the second user. For example, in response to the second user pressing the button 1604, the server 20 presents information about more detailed statistical information, etc.

[0149] FIG. 17 is a diagram showing information regarding conclusion on a screen in the first electronic contract service.

[0150] As described in step S10023, the server 20 presents a plurality of items of information related to the message in the first electronic contract service. Fig. 17 is an example of a screen example that presents information related to the conclusion in the first electronic contract service. As described in step S11011, the server 20 accepts an input of an operation to start the procedure for concluding the contract in the first electronic contract service for the contract request linked to the message. Fig. 17 is also an example of a screen example related to starting the procedure for concluding the contract in the first electronic contract service for the contract request linked to the message in the server 20.

[0151] Specifically, the first device 10 presents the following information on the dialog screen 1700: Area 1501 is as explained above. Area 1502 is as described above. Area 1503 is as explained above. Area 1701 is an area that presents information about the message issuer. The information about the message issuer is, for example, the name of the electronic contract service that issued the message. Area 1702 is an area indicating that the procedure for concluding the message is to be started in the first electronic contract service. An area indicating that the procedure for concluding the message in the first electronic contract service is, for example, "If you wish to proceed with concluding the message number #1126 in the first electronic contract service, please press this button." Button 1703 is a button for receiving an input of an operation to start a procedure for concluding a contract in the first electronic contract service for the contract request linked to the message in response to an input operation from the first user. For example, in response to the first user pressing button 1703, as described in step S11021, server 20 receives an input of an operation to start a procedure for concluding a contract.

[0152] FIG. 18 is a diagram showing information regarding conclusion on a screen in the first electronic contract service.

[0153] As described in step S11012, the first device 10 accepts an input of an operation indicating that the fastening is to be performed from the first user. Fig. 18 is an example of a screen example for accepting an input of an operation indicating that the fastening is to be performed.

[0154] Specifically, the first device 10 presents the following information on a dialog screen 1800: Area 1501 is as explained above. Area 1801 is an area related to confirmation of document contents. The area 1802 is an area related to the contents of the contract. The area related to the contents of the contract presents, for example, the main text of the contract. The area 1803 is an area related to the parties of the contract. The area related to the parties of the contract presents, for example, information on users who should be approved by the contractor. The area 1804 is an area related to input items of the contract. The area related to input items of the contract presents, for example, information of items that the logged-in user should input in the contract. Area 1805 is an area for inputting a signature for the contract. Button 1806 is a button for agreeing to the contents of the document in response to an input operation from the first user. For example, in response to the first user pressing button 1806, as described in step S11023, server 20 receives an input of an operation indicating that the conclusion will be performed. Then, server 20 executes a process of applying an electronic signature and a timestamp in the first electronic contract service to the conclusion.

[0155] FIG. 19 is a diagram showing a screen relating to an approver's proposal in the first electronic contract service.

[0156] As described in step S12011, the first device 10 accepts an input for an operation to add a third user to the approvers from the first user. Fig. 19 is an example of a screen example for accepting an input for an operation to add a third user to the approvers.

[0157] Specifically, the first device 10 presents the following information on a dialog screen 1900: Area 1501 is as explained above. Area 1801 is as explained above. Area 1802 is as explained above. Area 1803 is as explained above. Area 1804 is as explained above. Area 1805 is as explained above. Button 1806 is as explained above. The area 1901 is an area related to the approver's proposal. An example of an area related to the approver's proposal is "We recommend that the following approver be added to this document: Suzuki Hanako, President and CEO of XX Corporation." Button 1902 is a button for adding an approver proposed in area 1901 in response to an input operation from the first user. For example, in response to the first user pressing button 1902, as described in step S12022, server 20 receives input of an operation for adding a third user to the approvers. Then, as described in step S12023, server 20 executes a process for incorporating the third user into the approvers for the conclusion.

[0158] FIG. 20 is a diagram showing on the screen items related to documents that objectively certify that an electronic contract has been exchanged.

[0159] As described in step S11024, the server 20 executes the process of attaching an electronic signature and a time stamp in the first electronic contract service to the conclusion linked to the message. Fig. 20 shows an example of a screen relating to the process of attaching an electronic signature and a time stamp in the first electronic contract service. Documents that objectively certify that an electronic contract has been exchanged include, for example, an agreement conclusion certificate, an electronic contract conclusion certificate, etc. Documents that objectively certify that an electronic contract has been exchanged contain information on who agreed to which contract, when, and when. Documents that objectively certify that an electronic contract has been exchanged contain, for example, a record of an electronic signature, timestamp information, etc.

[0160] Specifically, the first device 10 presents the following information on the dialog screen 2000: An area 2001 is an area for displaying bibliographic information of the contract. The bibliographic information of the contract is, for example, the title of the contract, an ID related to the contract for identifying the contract, and the like. An area 2002 indicates the parties to the contract. The area 2003 is an area that displays information about the parties to the contract. For example, the area 2003 displays information about an electronic signature and a time stamp in the third electronic contract service. Area 2004 is an area that displays information about the parties to the contract. Area 2003 presents, for example, information about the electronic signature and time stamp in the first electronic contract service.

[0161] <Modification> (1) Judgment in the notice In step S9023, the server 20 issues a predetermined notification to a second user different from the first user, depending on the result of the determination in step S9022. The following determination methods are also possible for the determination in step S9022. The following are examples, and are not limited to these. For example, the server 20 may implement a predetermined notification when the third electronic contract service is a second electronic contract service different from the first electronic contract service used by the second user. In addition, the server 20 may implement a predetermined notification, for example, when the second user has a user account with a first electronic contract service and the third electronic contract service is a second electronic contract service for which the second user does not have a user account.

[0162] Although several embodiments of the present disclosure have been described above, these embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and modifications are within the scope of the invention and its equivalents as described in the claims, as well as the scope and spirit of the invention.

[0163] <Additional Notes> The following description adds to the matters described in the above embodiments. (Appendix 1) A program for operating a computer, the program causing a processor of the computer to execute the steps of: acquiring a message sent to a first user; and, if the message was issued by a specific electronic contract service and is for requesting conclusion of a contract prior to the conclusion of the contract through the specific electronic contract service, sending a predetermined notification to a second user different from the first user (S9023).

[0164] (Appendix 2) A program as described in (Appendix 1), which, in a notification step (S9023), issues a specified notification if the specific electronic contract service is a second electronic contract service different from the first electronic contract service used by the second user.

[0165] (Appendix 3) A program as described in (Appendix 2), which, in a notification step (S9023), issues a specified notification when the second user has a user account for a first electronic contract service and the specific electronic contract service is a second electronic contract service for which the second user does not have a user account.

[0166] (Appendix 4) The program described in (Appendix 1) further causes the processor to execute a step (S10022) of importing multiple items of information regarding the message into a first electronic contract service used by a second user.

[0167] (Appendix 5) The program described in (Appendix 4), wherein the multiple items of information about the message include at least two of the following: the body of the message, the subject of the message, information about the sender of the message, destination information for the message, information about files attached to the message, and the date and time the message was received.

[0168] (Appendix 6) The program described in (Appendix 4) makes multiple items of information related to the message viewable on a first electronic contract service (S10023).

[0169] (Appendix 7) A program as described in (Appendix 4), in which, for a request for conclusion linked to a message, a first electronic contract service presents a screen to at least one of the first user, the second user, or the sender of the message for operating the request for conclusion linked to the message (S11022).

[0170] (Appendix 8) The program according to (Appendix 7), which proposes to at least one of the first user, the second user, and the sender of the message that a specific approver be incorporated as an approver for the request for conclusion (S12021).

[0171] (Appendix 9) A program as described in (Appendix 7), in which, for a contract request linked to a message, if a record of the electronic signature of the contract remains in the specific electronic contract service that issued the message, and if the contract request linked to the message is to be concluded in a first electronic contract service, an electronic signature from the first electronic contract service is also added in addition to the electronic signature from the specific electronic contract service (S11024).

[0172] (Appendix 10) A program as described in (Appendix 9), in which, when an electronic signature is assigned in the first electronic contract service, the first electronic contract service assigns an electronic signature and a timestamp (S11024).

[0173] (Appendix 11) A method for operating a computer, the method including a step (S9023) of the computer processor acquiring a message sent to a first user, and if the message was issued by a specific electronic contract service and is for requesting conclusion of a contract prior to the conclusion of the contract by the specific electronic contract service, sending a predetermined notification to a second user different from the first user.

[0174] (Appendix 12) An information processing device having a control unit, the control unit executing the steps of: acquiring a message sent to a first user; and, if the message was issued by a specific electronic contract service and is for requesting conclusion of a contract prior to the conclusion of the contract by the specific electronic contract service, sending a predetermined notification to a second user different from the first user (S9023). [Explanation of symbols]

[0175] 1: system, 10: first device, 12: communication IF, 13: input device, 14: output device, 15: memory, 16: storage unit, 19: processor, 20: server of first electronic contract service, 22: communication IF, 23: input / output IF, 25: memory, 26: storage, 29: processor, 30: server of third electronic contract service, 32: communication IF, 33: input / output IF, 35: memory, 36: storage, 39: processor, 40: device of user of contract sender, 50: server of contract management service, 60: device of user of contract recipient, 70: second device, 80: network, 90: second The electronic contract service server, 100: mail server, 111: antenna, 121: first wireless communication unit, 130: operation reception unit, 132: display, 140: voice processing unit, 141: microphone, 142: speaker, 191: input operation reception unit, 192: transmission / reception unit, 193: data processing unit, 194: notification control unit, 201: communication unit, 202: storage unit, 203: control unit, 2021: document data database, 2022: document management database, 2023: user database, 2024: message database, 2031: reception control module, 2032: transmission control module

Claims

1. A program for operating a computer, The program causes a processor of the computer to: obtaining a message sent to a first user; A program that executes a step of making a specified notification to a second user different from the first user when the message is issued by a specific electronic contract service and is for requesting conclusion of a contract prior to the conclusion of the contract through the specific electronic contract service.

2. In the step of notifying, The program according to claim 1 , wherein the predetermined notification is given when the specific electronic contract service is a second electronic contract service different from a first electronic contract service used by the second user.

3. In the step of notifying, 3. The program of claim 2, further comprising: a program for sending the specified notification when the second user has a user account for the first electronic contract service and the specific electronic contract service is the second electronic contract service for which the second user does not have a user account.

4. The program further causes the processor to The program of claim 1 , further comprising: a step of: importing a plurality of items of information related to the message into a first electronic contract service used by the second user.

5. The information on the plurality of items relating to the message includes: The body of said message, The subject of said message; Information regarding the origin of the message; destination information of said message; Information about any files attached to said message; The date and time of receipt of said message; The program according to claim 4, comprising at least two of the following:

6. The program according to claim 4 , further comprising making a plurality of items of information relating to the message viewable on the first electronic contract service.

7. The program according to claim 4, wherein the first electronic contract service presents a screen for operating the request for conclusion linked to the message to at least one of the first user, the second user, or the sender of the message.

8. 8. The program according to claim 7, further comprising a step of proposing to at least one of the first user, the second user, and the sender of the message that a specific approver be incorporated into the approvers related to the request for conclusion.

9. Regarding the conclusion request linked to the message, when a record of the electronic signature of the contract remains in the specific electronic contract service that issued the message, and when the conclusion request linked to the message is to be concluded in the first electronic contract service, The program according to claim 7 , further comprising an electronic signature in the first electronic contract service, in addition to the electronic signature in the specific electronic contract service.

10. The program according to claim 9 , wherein when the first electronic contract service assigns an electronic signature, the first electronic contract service assigns the electronic signature and a timestamp.

11. 1. A method for operating a computer, comprising: The method further comprises the steps of: obtaining a message sent to a first user; and if the message is issued by a specific electronic contract service and is for requesting conclusion of a contract prior to the conclusion of the contract through the specific electronic contract service, a step of giving a predetermined notification to a second user different from the first user.

12. An information processing device including a control unit, The control unit: obtaining a message sent to a first user; An information processing device that executes a step of making a predetermined notification to a second user different from the first user when the message is issued by a specific electronic contract service and is for requesting conclusion of a contract before the contract is concluded by the specific electronic contract service.

Images