Program, method, information processing apparatus, and system

Abstract

To eliminate the necessity of another conclusion of an electronic contract which includes an error, the electronic contract having been concluded between a plurality of users in an electronic contract procedure.SOLUTION: In a computer equipped with a processor and a storage unit, a program that provides a service related to a contract document which is to be concluded between parties concerned causes the processor to execute: a contract storage step of storing a contract document related to a contract concluded between a plurality of users; a correction receiving step of receiving a correction operation on the content of contract in the contract document stored in the contract storage step; and a signing step of storing the content of correction related to the content of the correction operation received in the correction receiving step, with an electronic signature affixed thereto, in association with the contract document.SELECTED DRAWING: Figure 19

Description

[Technical field]

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

[0002] With the development and spread of computer technology, documents that were previously paper-based are being digitized. For example, documents such as contracts that require the signatures and seals of the parties involved are being considered for management as electronic data. Patent Document 1 discloses an information processing system for digital contracts that includes a creator terminal, a verifying terminal, and a contract management server. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2017-10096 Summary of the Invention [Problem to be solved by the invention]

[0004] In electronic contract procedures between multiple users, if an error is contained in an electronic contract that has been concluded, there is a problem that the electronic contract must be concluded anew. Therefore, the present disclosure has been made to solve the above problem, and its purpose is to provide technology that can correct an error in an electronic contract without having to re-conclude the electronic contract, even if the error is contained in the electronic contract. [Means for solving the problem]

[0005] A program having a processor and a memory unit, for providing a computer with a service related to a contract document that is the subject of an agreement between parties, wherein the processor executes a contract storage step of storing a contract document related to a contract agreed upon between a plurality of users, a correction acceptance step of accepting correction operations for the contract content of the contract document stored in the contract storage step, and a signature assignment step of associating the correction content related to the correction operation accepted in the correction acceptance step with the contract document, assigning an electronic signature to the correction content, and storing it. Effect of the Invention

[0006] According to the present disclosure, even if an electronic contract contains an error, it can be corrected without having to re-conclude the electronic contract. [Brief description of the drawings]

[0007] [Figure 1] FIG. 2 is a block diagram showing the functional configuration of the system 1. [Diagram 2] FIG. 2 is a block diagram showing the functional configuration of the server 10. [Diagram 3] 2 is a block diagram showing a functional configuration of a first user terminal 20. FIG. [Figure 4] 2 is a block diagram showing a functional configuration of a second user terminal 30. FIG. [Diagram 5] FIG. 13 is a diagram showing the data structure of a user table 1012. [Figure 6] 13 is a diagram showing the data structure of a group table 1013. FIG. [Figure 7] FIG. 13 shows the data structure of a document table 1014. [Figure 8] FIG. 13 is a diagram showing the data structure of a confirmation table 1015. [Figure 9] 13 is a diagram showing the data structure of an input item table 1016. FIG. [Figure 10] FIG. 13 is a diagram showing the data structure of a contract group table 1017. [Figure 11] FIG. 13 shows the data structure of a correction table 1021. [Figure 12] 13 is a flowchart showing the operation of a contract creation process. [Figure 13] 13 is a flowchart showing the operation of a contract confirmation process. [Figure 14] 13 is a flowchart showing the operation of a contract correction process. [Figure 15] FIG. 2 is a block diagram showing the basic hardware configuration of a computer 90. [Figure 16] 13 is a screen example showing a confirmation request message sent to the second user terminal 30. [Figure 17] 13 is a screen example showing the operation of a contract confirmation process. [Figure 18] 13 is a screen example showing a conclusion completion message notified to the first user terminal 20. [Figure 19] 13 is a screen example showing the operation of contract correction processing. [Figure 20] 13 is a screen example showing the operation of a correction confirmation process. [Figure 21] 13 is a screen example showing a reflected contract document. [Figure 22] FIG. 2 is a block diagram showing the basic hardware configuration of a computer 90. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] Hereinafter, an embodiment of the present disclosure will be described with reference to the drawings. In all the drawings explaining the embodiment, the same reference numerals are given to common components, and repeated explanations are omitted. Note that the following embodiment does not unduly limit the contents of the present disclosure described in the claims. In addition, not all of the components shown in the embodiment are essential components of the present disclosure. In addition, each figure is a schematic diagram and is not necessarily illustrated strictly.

[0009] <System 1 Configuration> The system 1 in the present disclosure is an information processing system for realizing a service for storing and managing contract information concluded between a plurality of users. The system 1 includes information processing devices, a server 10, a first user terminal 20, and a second user terminal 30, which are connected via a network N. FIG. 1 is a block diagram showing the functional configuration of the system 1. FIG. 2 is a block diagram showing the functional configuration of the server 10. As shown in FIG. FIG. 3 is a block diagram showing the functional configuration of the first user terminal 20. As shown in FIG. FIG. 4 is a block diagram showing the functional configuration of the second user terminal 30. As shown in FIG. FIG. 15 is a block diagram showing the basic hardware configuration of a computer 90. As shown in FIG.

[0010] Each information processing device is configured by a computer equipped with a calculation device and a storage device. The basic hardware configuration of the computer and the basic functional configuration of the computer realized by the hardware configuration will be described later. For each of the server 10, the first user terminal 20, and the second user terminal 30, descriptions that overlap with the basic hardware configuration and basic functional configuration of the computer described later will be omitted.

[0011] <Server 10 Configuration> The server 10 includes an information processing device that provides an electronic contract conclusion service between multiple users. The server 10 includes an information processing device that provides a service of storing and managing contract information concluded between multiple users. The server 10 also includes any information processing service that stores and manages contract information. The server 10 includes a storage unit 101 and a control unit 104 .

[0012] <Configuration of the storage unit 101 of the server 10> The memory unit 101 of the server 10 includes an application program 1011 , a user table 1012 , a group table 1013 , a document table 1014 , a confirmation table 1015 , an input item table 1016 , a contract group table 1017 , and a correction table 1021 .

[0013] The application program 1011 is a program for causing the control unit 104 of the server 10 to function as each functional unit.

[0014] The user table 1012 is a table for storing and managing information on member users (hereinafter, users) who use the service. When a user registers to use the service, the user's information is stored in a new record in the user table 1012. This allows the user to use the service according to the present disclosure. Note that a user who uses a service according to the present disclosure does not necessarily need to be registered in the user table 1012. The user table 1012 is a table having a user ID as a primary key, and columns of user ID, user name, email address, group ID, and approval authority. FIG. 5 is a diagram showing the data structure of the user table 1012. As shown in FIG.

[0015] The user ID is an item for storing user identification information for identifying a user. The user identification information is an item for which a unique value is set for each user. The user name is an item for storing the name of the user. The user name may be set to any character string such as a nickname instead of a name. The email address is an item for storing the email address of the user. The group ID is an item for storing group identification information of a group to which a user belongs. Groups are defined by a group table 1013, which will be described later, and a user may belong to multiple groups. The approval authority is an item that stores authority information regarding approval of a user. For a user who has the authority to approve the conclusion of a contract (approval authority), information that indicates the authority to approve the conclusion of a contract, such as True, is stored. On the other hand, for a user who does not have the authority to approve the conclusion of a contract, information that indicates the lack of authority to approve the conclusion of a contract, such as False, blank, or null value, is stored. The approval authority may be set according to the contract information. For example, a user A may have approval authority for specific contract information A, but not approval authority for specific contract information B. The system may be configured so that approval authority can be set according to the type of contract information (contract information type) such as a confidentiality agreement, a joint research agreement, a contract agreement, etc. For example, the system may be configured so that user A has approval authority for a confidentiality agreement but does not have approval authority for a contract agreement. Alternatively, the system may be configured to store multiple levels (levels, ranks) of authority information depending on the user's department, government office, etc. For example, information such as C for temporary staff, B for general employees, A for managers, and S for executives may be stored in the approval authority field, and only users with approval authority of a predetermined rank or higher (e.g., A or higher for non-disclosure agreements) may be able to approve the conclusion of a contract depending on the contract type information, contract amount, etc. of the contract information.

[0016] The group table 1013 is a table for storing and managing information (group information) about groups to which a user belongs. The group can define any group to which a user belongs, such as a corporation, a company, a club, an organization, or a department within a company. The group table 1013 is a table having the group ID as a primary key, and columns of the group ID, group name, and administrator ID. FIG. 6 is a diagram showing the data structure of the group table 1013. As shown in FIG.

[0017] The group ID is an item for storing group identification information for identifying a group. The group identification information is an item for which a unique value is set for each group. The group name is an item for storing the name of the group. Any character string can be set as the group name. The administrator ID is an item for storing user identification information of a user who has administrator authority in a group. A user with administrator authority can arbitrarily define and set a user who has a certain or higher position or authority in a group such as an organization.

[0018] The document table 1014 is a table for storing and managing information (contract information) relating to an electronic contract exchanged between a creator and a recipient. The document table 1014 is a table having the document ID as a primary key and columns of the document ID, document data, and creator ID. FIG. 7 is a diagram showing the data structure of the document table 1014. As shown in FIG.

[0019] The document ID is an item for storing document identification information for identifying contract information. The document identification information is an item for which a unique value is set for each contract information. The document data is an item that stores contract information (binary or text data) of a contract document related to the conclusion of a contract. Specifically, the document data includes data in any data format such as PDF (Portable Document Format), Word, and XML (Extensible Markup Language). Creator ID is an item for storing user identification information for identifying the user who created the contract information.

[0020] The confirmation table 1015 is a table for storing and managing information (checker information) including the email address of the user who will be the checker of the contract information. The confirmation table 1015 is a table having columns for document ID, confirmation order, confirmer email address, confirmation flag, language data, access code, and date and time. FIG. 8 is a diagram showing the data structure of the confirmation table 1015. As shown in FIG.

[0021] The document ID is an item for storing document identification information of the contract information to be confirmed by the confirmer. The confirmation order is an item for storing information regarding the confirmation order when the confirmer confirms the contract information. The contract information stored by the creator is circulated to the confirmers in the confirmation order, and is confirmed. The checker email address is an item for storing the email address of the checker of the contract information. The checker's email address does not need to be registered in advance as a user when using the service according to the present disclosure. In other words, the checker's email address does not need to be included in the user table 1012. The confirmation flag is an item for storing confirmation identification information for identifying whether or not the confirmer has completed the procedure for confirming the contract information. When the confirmer has completed the confirmation of the contract information, information indicating that the confirmation has been completed, such as a value of True, is stored in the confirmation flag item. The language data is an item for storing information (language information) related to the language of the verifying person. The access code is an item for storing an access code set for the verifying person. The date and time is an item for storing the date and time when the confirming procedure of the contract information is performed by the confirmer. Specifically, the date and time when the confirmation identification information is stored in the confirmation flag item is stored.

[0022] The input item table 1016 is a table that stores and manages information (input item information) related to the input items associated with the electronic contract information. The input item table 1016 is a table having columns of input item ID, document ID, inputter ID, input data, input rule, and date and time. FIG. 9 is a diagram showing the data structure of the input item table 1016. As shown in FIG.

[0023] The input item ID is an item that stores input item identification information for identifying an input item. The document ID is an item that stores the document identification information of the electronic contract information with which the input item is associated. The inputter ID is an item that stores the user identification information or email address of the inputter who inputs input data into the input item. Specifically, the inputter ID stores the creator ID, the email address of the user identified by the creator ID, the verifying person's email address, etc. The input data is an item that stores input data entered into an input item by a user. The input rule is a field that stores input rule information related to the input rules of the input fields. As input rules, in addition to data types such as date, datetime, text, and integer, it is possible to store input rule information related to any input field, such as the number of characters in a text string or the regular expression of the text string. The date and time is an item for storing the date and time when the input data is input into the input item by the inputter.

[0024] The contract group table 1017 is a table for storing and managing information related to contract groups (contract group information). Contract information can be stored and managed in association with one or more cabinets (classification information) for managing contract information. Depending on the information processing service, a cabinet may be called a group, a tag, a label, or the like. The contract group table 1017 is a table having columns for document ID and cabinet ID. FIG. 10 is a diagram showing the data structure of the contract group table 1017.

[0025] The document ID is an item for storing document identification information for identifying contract information. The cabinet ID stores cabinet identification information for identifying a cabinet. The cabinet ID is classification information for managing and classifying contract information.

[0026] The correction table 1021 is a table for storing and managing information (correction information) regarding corrections to the contract contents of the contract information. The correction table 1021 is a table having columns of correction ID, document ID, user ID, correction confirmation data, correction data, clean data, and date and time. FIG. 11 is a diagram showing the data structure of the correction table 1021. As shown in FIG.

[0027] The correction ID is an item for storing correction identification information for identifying correction information. The document ID is an item for storing document identification information of the contract information to be corrected. The user ID is an item for storing the user identification information of the user who executed the contract correction process. The correction confirmation data is a table that stores and manages information (correction confirmer information) including the email addresses of users who confirm the correction information. The correction data is an item that stores information regarding corrections to the contract contents of the contract information. Specifically, information regarding cancellation of a portion of the contract contents included in the contract information, addition of text, and electronic seal is stored. For example, the correction data is Includes information on the placement position, size, etc. of objects such as the cancel object. Includes information such as the position and size of the input field. -Includes information entered into the input field. Includes information on the location and size of the stamp area. Includes the stamping information entered in the stamping field. Clean data is an item that stores a contract document (clean version, plain number) in which the correction content is reflected in the main text, based on contract information, and does not contain object information (correction objects) used during correction operations, such as cancellation objects, correction input fields, and correction stamp fields, in which the contents of the correction data are reflected. The date and time is an item for storing the date and time when a record is newly stored or updated in the correction table.

[0028] <Configuration of the control unit 104 of the server 10> The control unit 104 of the server 10 includes a user registration control unit 1041, a contract creation unit 1042, a contract confirmation unit 1043, and a contract correction unit 1051. The control unit 104 executes an application program 1011 stored in the storage unit 101 to realize each functional unit.

[0029] The user registration control unit 1041 performs processing to store, in the user table 1012, information on users who wish to use the service according to the present disclosure. The information stored in the user table 1012 is generated when a user opens a web page operated by a service provider from any information processing terminal, enters information into a specific input form, and transmits the information to the server 10. The user registration control unit 1041 stores the received information in a new record in the user table 1012, completing the user registration. This allows the user stored in the user table 1012 to use the service. Before the user registration control unit 1041 registers user information in the user table 1012, the service provider may carry out a predetermined examination to restrict whether or not the user is permitted to use the service. The user ID may be any character string or number that can identify the user, any character string or number desired by the user, or an arbitrary character string or number may be automatically set by the user registration control unit 1041.

[0030] The contract preparation unit 1042 executes a contract preparation process, the details of which will be described later.

[0031] The contract confirmation unit 1043 executes a contract confirmation process, the details of which will be described later.

[0032] The contract correction unit 1051 executes a contract cancellation process, the details of which will be described later.

[0033] <Configuration of First User Terminal 20> The first user terminal 20 is an information processing device operated by a user who uses a service. The first user terminal 20 may be, for example, a desktop PC (Personal Computer) or a laptop PC, or may be a mobile terminal such as a smartphone or a tablet. It may also be a wearable terminal such as an HMD (Head Mount Display) or a wristwatch terminal. The first user terminal 20 includes a storage unit 201 , a control unit 204 , an input device 206 , and an output device 208 .

[0034] <Configuration of the storage unit 201 of the first user terminal 20> The storage unit 201 of the first user terminal 20 includes a first user ID 2011 and an application program 2012 .

[0035] The first user ID 2011 is an account ID of the user. The user transmits the first user ID 2011 from the first user terminal 20 to the server 10. The server 10 identifies the user based on the first user ID 2011 and provides the user with the service according to the present disclosure. The first user ID 2011 includes information such as a session ID temporarily assigned by the server 10 when identifying the user using the first user terminal 20.

[0036] The application program 2012 may be stored in advance in the storage unit 201, or may be configured to be downloaded from a web server operated by a service provider via a communication IF. The application programs 2012 include applications such as a web browser application. The application program 2012 includes an interpreted programming language such as JavaScript™ that runs on a web browser application stored on the first user terminal 20.

[0037] <Configuration of the control unit 204 of the first user terminal 20> The control unit 204 of the first user terminal 20 includes an input control unit 2041 and an output control unit 2042. The control unit 204 executes an application program 2012 stored in the storage unit 201, thereby realizing each functional unit.

[0038] <Configuration of the input device 206 of the first user terminal 20> The input device 206 of the first user terminal 20 includes a camera 2061 , a microphone 2062 , a position information sensor 2063 , a motion sensor 2064 , and a touch device 2065 .

[0039] <Configuration of the output device 208 of the first user terminal 20> The output device 208 of the first user terminal 20 includes a display 2081 and a speaker 2082 .

[0040] <Configuration of second user terminal 30> The second user terminal 30 is an information processing device operated by a user who uses the service. The second user terminal 30 may be, for example, a desktop PC (Personal Computer) or a laptop PC, or may be a mobile terminal such as a smartphone or a tablet. It may also be a wearable terminal such as an HMD (Head Mount Display) or a wristwatch terminal. The second user terminal 30 includes a storage unit 301 , a control unit 304 , an input device 306 , and an output device 308 .

[0041] <Configuration of the storage unit 301 of the second user terminal 30> The storage unit 301 of the second user terminal 30 includes a second user ID 3011 and an application program 3012 .

[0042] The second user ID 3011 is a user's account ID. The user transmits the second user ID 3011 from the second user terminal 30 to the server 10. The server 10 identifies the user based on the second user ID 3011 and provides the user with the service according to the present disclosure. The second user ID 3011 includes information such as a session ID temporarily assigned by the server 10 to identify the user using the second user terminal 30.

[0043] The application program 3012 may be stored in advance in the storage unit 301, or may be configured to be downloaded from a web server operated by a service provider via a communication IF. Application programs 3012 include applications such as a web browser application. The application program 3012 includes an interpreted programming language such as JavaScript (registered trademark) that runs on a web browser application stored on the second user terminal 30.

[0044] <Configuration of the control unit 304 of the second user terminal 30> The control unit 304 of the second user terminal 30 includes an input control unit 3041 and an output control unit 3042. The control unit 304 executes an application program 3012 stored in the storage unit 301, thereby realizing each functional unit.

[0045] <Configuration of the input device 306 of the second user terminal 30> The input device 306 of the second user terminal 30 includes a camera 3061 , a microphone 3062 , a position information sensor 3063 , a motion sensor 3064 , and a keyboard 3065 .

[0046] <Configuration of the output device 308 of the second user terminal 30> The output device 308 of the second user terminal 30 includes a display 3081 and a speaker 3082 .

[0047] <System 1 Operation> Each process of the system 1 will be described below. FIG. 12 is a flowchart showing the operation of the contract creation process. FIG. 13 is a flowchart showing the operation of the contract confirmation process. FIG. 14 is a flowchart showing the operation of the contract correction process. FIG. 16 is an example of a screen showing a confirmation request message sent to the second user terminal 30. In FIG. FIG. 17 is a screen example showing the operation of the contract confirmation process. FIG. 18 is an example of a screen showing a conclusion completion message sent to the first user terminal 20. In FIG. FIG. 19 is an example of a screen showing the operation of the contract correction process. FIG. 20 is a screen example showing the operation of the correction confirmation process. FIG. 21 is an example of a screen showing the reflected contract document.

[0048] In the present disclosure, the contract creation process and contract confirmation process in the server 10 will be described below.

[0049] <Contract creation process> The contract creation process is a process in which the creator creates electronic contract information and transmits it to the confirmer.

[0050] 15 is an example of a screen showing the operation of the contract creation process. A screen 50 for creating contract information, which is displayed on the display 2081 of the first user terminal 20, displays a status 510 showing the current creation status of the contract information, buttons 521, 522, and 523 for specifying input items, a contract information display area 530, document data 531, input items 532, 533, and 534, and a send button 540.

[0051] <Outline of contract creation process> The contract creation process is a series of processes in which the creator creates electronic contract information, sets the verifying party to whom the electronic contract information will be sent, sets input fields for the electronic contract information, sets input rules for the input fields, accepts input data for the input fields from the creator, and sends the electronic contract information to the set verifying party.

[0052] <Details of contract creation process> The contract creation process will be described in detail below.

[0053] In step S101, the contract preparation unit 1042 of the server 10 receives, from the preparer, contract information to be the subject of a contract to be concluded between the preparer and the verifyer. Specifically, the first user operates the input device 206 of the first user terminal 20 to create contract information including document data related to the contract. The document data may be in any data format such as PDF (Portable Document Format), Word, or XML (Extensible Markup Language) and may be included in the contract information. The first user operates the input device 206 of the first user terminal 20 and transmits the created document data and the first user ID 2011 to the server 10. The contract creation unit 1042 of the server 10 accepts the received first user ID 2011 and document data, and stores them in the creator ID and document data items of a new record in the document table 1014, respectively. As a result, the contract creation unit 1042 of the server 10 stores the new contract information in the document table 1014.

[0054] Document data 531 stored in document table 1014 is displayed on screen 50 for creating contract information.

[0055] In step S102, the first user operates the input device 206 of the first user terminal 20 to select and specify a user who will be a confirmer (recipient) of the contract information. In the present disclosure, it is assumed that the first user selects and specifies a second user as the recipient. The first user operates the input device 206 of the first user terminal 20, inputs the email address of the second user who will be the checker, and transmits it to the server 10. The contract creation unit 1042 of the server 10 stores the received email address and the document ID of the contract information created and stored in step S101 in the checker email address and document ID items of the confirmation table 1015, respectively, and stores the contract information in association with the email address of the second user. The first user may set the language and access code of the second user, and store them in association with the email address of the second user. At this time, a value of 1 is stored in the confirmation order field of confirmation table 1015. In step S102, the first user may be able to select and set multiple users to be the confirmers. In this case, the value of the confirmation order field of the users to be the confirmers is incremented by one and stored according to the selection order. This sets the circulation order of the confirmers in the contract confirmation process described later. Note that setting the circulation order is not essential.

[0056] In step S103, the first user operates the input device 206 of the first user terminal 20 to set input items for the contract information. Specifically, the first user operates the input device 206 of the first user terminal 20 and sets multiple input items for the contract information created and stored in step S101. The input items can be any input item, such as a seal field for stamping seal data, an input field for inputting text data such as signature data, a check box field for selecting check items, a date field for inputting a date, etc. The first user operates the input device 206 of the first user terminal 20 to send a request to add an input item to the server 10. When the contract creation unit 1042 of the server 10 receives the request, it stores the document ID of the contract information as the document ID of a new record in the input item table 1016. As a result, the newly added input item information is stored in association with the contract information. The first user can store multiple pieces of input item information in association with the contract information.

[0057] In step S104, the first user sets input rules for each input item to be added. The first user operates the input device 206 of the first user terminal 20 or the like to specify input rules for each piece of input item information set in step S103, and transmits them to the server 10. The contract creation unit 1042 of the server 10 stores the received input rules in the input rule field of the record of each piece of input item information in the input item table 1016. This makes it possible to set input rules for each input item.

[0058] In step S105, the contract preparation unit 1042 of the server 10 accepts input data for a plurality of input items input by the first user. Specifically, the first user operates the input device 206 of the first user terminal 20 to input input data for each input item set in step S104. For example, the first user may input input data of a number for managing contract information, such as a serial number for a group to which the first user belongs, into an input item in which a management number is set. The first user may input input data of the contract conclusion date of the contract information into an input item in which a contract conclusion date is set. After completing input of the input data into the input items, the first user transmits the input item ID and input data for each input item to the server 10. The contract creation unit 1042 of the server 10 receives and accepts the input item ID and input data for each input item. The contract creation unit 1042 of the server 10 stores the received input data in the input data item of the input item information of the input item table 1016 specified by the received input item ID. As a result, the input data entered by the first user is stored in the input item table 1016.

[0059] The contract creation unit 1042 of the server 10 receives an instruction from the first user to request the second user to conclude a contract for the contract information. Specifically, the first user operates the input device 206 of the first user terminal 20 and presses the send button 540 displayed on the screen 50 for creating contract information, thereby sending a request to send the contract information to the server 10.

[0060] In step S106, the contract creation unit 1042 of the server 10 transmits a message to the second user notifying that a request to confirm the contract information has been sent from the first user. Specifically, the contract creation unit 1042 of the server 10 searches the confirmation order field of the confirmation table 1015, and identifies a user (first confirmation user) who will be the first confirmer and who has the smallest value stored in the confirmation order field. In the present disclosure, the first confirmation user is, as an example, the second user. The contract creation unit 1042 of the server 10 transmits a message to the email address of the second user by a communication means such as email notifying that a request to confirm the contract information has been sent from the first user. The message to be notified to the second user includes URL (Uniform Resource Locator) information including a document ID for identifying the contract information. The URL may directly include the document ID, or may include information such as a character string obtained by arbitrarily encrypting the document ID, or a character string that can identify the document ID by referring to a table (not shown). The URL may also include information for identifying the second user. For example, if the second user is not registered as a user with the service according to the present disclosure, the URL needs to include information for identifying the second user.

[0061] When the first user sets an access code for the second user, the first user separately communicates the access code to the second user by means of e-mail, etc. In this way, even if the message notified to the second user is obtained by a third party, the third party cannot execute the contract confirmation process unless he or she obtains the access code.

[0062] 16 is an example of a screen showing a message notified to the second user terminal 30. The message screen 60 displayed on the display 3081 of the second user terminal 30 includes information of a message 61 and a URL 62 including a document ID for identifying contract information.

[0063] <Modification> When the first user selects and sets multiple checkers in step S102, the first user may be configured to set different input item information for each of the multiple checkers independently in step S103. For example, when the first user sets two users, the second user and the ninth user, as checkers, the first user may set the input items of the contract start date and contract end date for the second user, and the input item of the contract conclusion date for the ninth user. In this case, in the contract confirmation process described later, the second user can input input data for the input items of the contract start date and contract end date, but cannot input input data for the input item of the contract conclusion date. On the other hand, the ninth user cannot input input data for the input items of the contract start date and contract end date, but can input input data for the input item of the contract conclusion date. The first user may be configured to select and set multiple checkers for one input item information in a duplicated manner.

[0064] On screen 50 for creating contract information, input items 532, 533, and 534 are drawn as drawing objects. In input items 532 and 533, user identification information "USER-B" of a user who has selected and set to input the input item is drawn as an assignment, and an item called "text" is drawn as an input item type. In input item 534 related to stamping, user identification information "USER-C" of a user who has selected and set to stamp is drawn as an assignment, and an item called "stamp" is drawn as an input item type.

[0065] In addition, in the present disclosure, a configuration in which the contract information and various input information are stored in various tables of the server 10 in each step has been disclosed as an example, but is not limited thereto. For example, in the transmission step of step S106, the contract information and various input information input by the creator may be collectively stored in various tables of the server 10.

[0066] <Contract confirmation process> The contract confirmation process is a process in which the confirmer confirms the contents of the electronic contract information received from the creator.

[0067] <Outline of contract confirmation process> The contract confirmation process is a series of processes that accepts access from a confirmer, presents a confirmation screen displaying contract information to the confirmer, accepts input data for input fields from the confirmer, and accepts data regarding confirmation of the contract information from the confirmer.

[0068] <Details of contract confirmation process> The contract confirmation process will be described in detail below.

[0069] In step S301, the second user who is to be the confirmer can select the URL described in the received message by operating the input device 306 of the second user terminal 30 or the like, thereby opening the web page specified by the URL with the browser application of the second user terminal 30. As a result, the second user terminal 30 transmits a request to the server 10 to execute the contract confirmation process.

[0070] If an access code item is stored in the record of the second user in confirmation table 1015, the second user is requested to input an access code, and the input access code is compared with the access code stored in the record of the second user in confirmation table 1015, thereby performing authentication processing for the second user. Specifically, the server 10 transmits an input screen for authenticating the access code to the second user terminal 30. The second user operates the input device 306 of the second user terminal 30 to input the access code and transmit it to the server 10. The contract confirmation unit 1043 of the server 10 determines whether the received access code matches the access code stored in the record of the second user in the confirmation table 1015, and if they match, continues the contract confirmation process. On the other hand, if they do not match, stops the contract confirmation process. Note that the authentication process using the access code may be omitted.

[0071] The contract confirmation unit 1043 of the server 10 searches the document ID item in the document table 1014 based on the document ID included in the received request, and acquires the contract information. The contract confirmation unit 1043 of the server 10 searches the document ID item in the confirmation table 1015 based on the document ID included in the received request, and acquires the confirmer information. The contract confirmation unit 1043 of the server 10 searches the document ID item in the input item table 1016 based on the document ID included in the received request, and acquires the input item information associated with the contract information.

[0072] In step S302, the contract confirmation unit 1043 of the server 10 identifies the second user. The second user may be identified based on the second user ID 3011 included in the request received from the second user terminal 30, or may be identified based on identification information for identifying the second user included in the URL. If the second user is not registered as a user in the service according to the present disclosure, it is necessary to identify the second user from the URL. For example, the URL may include the email address, user ID, etc. of the second user as information for identifying the second user.

[0073] In step S303, the contract confirmation unit 1043 of the server 10 generates a confirmation screen based on the acquired contract information, confirmer information (information for identifying the second user), and input item information, and transmits the generated confirmation screen to the second user terminal 30.

[0074] Specifically, the display 3081 of the second user terminal 30 presents a confirmation screen for accepting an operation to approve the contract information to the second user. The second user checks and approves the contract information displayed on the display 3081 of the second user terminal 30. In addition, the confirmation screen presented to the second user may be configured to be presented to the second user in a language specified for the confirmer, based on the language information stored in the language data item of the second user's record in confirmation table 1015.

[0075] 17 is an example of a confirmation screen showing the operation of the contract confirmation process. A confirmation screen 70 for approving the contract information, which is displayed on the display 3081 of the second user terminal 30, displays a status 710 showing the current creation status of the contract information, a contract information display area 730, document data 731, input items 732, 733, 734, 735, 736, and an Agree button 740.

[0076] In step S304, the contract confirmation unit 1043 of the server 10 accepts input for one or more input items of the contract information. Specifically, the second user operates the input device 306 of the second user terminal 30, and inputs input data into the input items 732, 733, 734, and 735 set in the contract information. Note that in the present disclosure, input by the second user is not assigned to the input item 736, and therefore, it is visually displayed that the second user cannot input input data.

[0077] In step S305, the contract confirmation unit 1043 of the server 10 executes a contract storage step of storing a contract document related to a contract agreed upon between a plurality of users. The contract storage step executes a step of storing a contract document agreed upon between a first user and a second user. The contract storage step executes a step of storing a contract document agreed upon between a plurality of users including the first user. Specifically, the contract confirmation unit 1043 of the server 10 receives an instruction from the second user to agree to and approve the conclusion of the contract in the contract information received from the first user. The second user checks the contract information and input data displayed on the display 3081 of the second user terminal 30, and if he or she agrees or accepts the contents, he or she operates the input device 306 of the second user terminal 30 or the like to press the Agree button 740 displayed on the confirmation screen 70 for confirming the contract information, thereby executing a process of transmitting a request including the document ID, information identifying the second user, and the input data for each input item entered in step S305 to the server 10. The information identifying the second user may be the second user ID 3011. The contract confirmation unit 1043 of the server 10 stores information indicating that the second user has confirmed the contract information based on the received request. Specifically, the contract confirmation unit 1043 of the server 10 searches the confirmation table 1015 based on the received document ID and information identifying the second user, and stores a value of True in the confirmation flag field of the record. For example, if the information identifying the second user is an email address, the contract confirmation unit 1043 searches the document ID and confirmer email address fields of the confirmation table 1015, and stores a value of True in the confirmation flag field of the record. If the information identifying the second user is user identification information, the contract confirmation unit 1043 searches the document ID and confirmer email address fields of the confirmation table 1015 based on the email address of the second user identified by searching the user ID field of the user table 1012, and stores a value of True in the confirmation flag field of the record. The contract confirmation unit 1043 of the server 10 stores the received input data in the input data item of the input item table 1016 specified by the input item ID associated with the input data. As a result, in step S305, the input data entered by the second user is stored as input item information in the input item table 1016.

[0078] The contract confirmation unit 1043 of the server 10 determines that the contract confirmation process has been performed by all the checkers. Specifically, the contract confirmation unit 1043 of the server 10 determines that the contract confirmation process has been performed by all the checkers when a value of True is stored in the confirmation flag of the checker's record in the confirmation table 1015. When the contract confirmation process has been performed by all the confirmers, the contract confirmation unit 1043 of the server 10 transmits a message to the first user notifying the completion of the contract confirmation process. Similarly, the contract confirmation unit 1043 of the server 10 may transmit a message to the second user notifying the completion of the contract confirmation process.

[0079] Specifically, the contract confirmation unit 1043 of the server 10 sends a message to the email address of the first user by a communication means such as email to notify the first user that the second user has completed confirmation of the contract information. In other words, the first user is notified that the second user has approved the conclusion of the contract. This allows the first user to know that the conclusion of the contract with the second user has been completed. The message sent to the first user may include information about a URL that is an end point including a document ID for identifying the contract information.

[0080] 18 is an example of a screen showing a message notified to the first user terminal 20. The message screen 80 displayed on the display 2081 of the first user terminal 20 includes information of a message 81 and a URL 82 including a document ID for identifying contract information.

[0081] Similarly, the contract confirmation unit 1043 of the server 10 may use a chat service (not shown) or the like to send a message notifying the first user that the second user has completed confirmation of the contract information, including a mention to the first user. In other words, the first user is notified via the chat service that the second user has approved the conclusion of the contract. This allows the first user to know that the conclusion of the contract with the second user has been completed. The message sent to the first user may include information about a URL that is an end point including a document ID for identifying the contract information.

[0082] The first user can open a web page specified by the URL included in the received message using a browser application on the first user terminal 20. The first user terminal 20 refers to the contract information and transmits a request to the server 10 for inquiry. The contract confirmation unit 1043 of the server 10 generates a web page for referring to the contract information and transmits it to the first user terminal 20. The first user can obtain the document data included in the contract information by downloading it or the like from the web page screen displayed on the display 2081 of the first user terminal 20.

[0083] When multiple users are set as confirmers, the contract confirmation unit 1043 of the server 10 may send a message to confirmers other than the user who last executed the contract confirmation process to notify them that the contract confirmation process has been completed. This allows the confirmers to receive a notification that the contract confirmation process has been completed by all confirmers. Furthermore, the contract confirmation unit 1043 of the server 10 may transmit a message notifying a user having authority equivalent to that of an administrator in a group to which a plurality of confirmers belong that the contract confirmation process has been completed. The message may be sent via email, chat service, etc. This allows the administrator in the group to which the user who performed the check belongs to to be notified that the contract check process has been completed.

[0084] Specifically, the contract confirmation unit 1043 of the server 10 acquires the group ID item by searching the user ID or email address item in the user table 1012 based on the user ID or email address. The contract confirmation unit 1043 of the server 10 searches the group ID item in the group table 1013 based on the acquired group ID item, acquires the administrator ID item, identifies a user having authority equivalent to that of an administrator by searching the user ID in the user table 1012 based on the administrator ID, and transmits a message notifying that the contract confirmation process has been completed.

[0085] <Electronic signature processing> An electronic signature process may be included in step S305. In response to an instruction to approve the conclusion of the contract received from the second user in step S305, the contract confirmation unit 1043 of the server 10 adds an electronic signature indicating that the conclusion of the contract of the contract information has been approved to the contract information received from the first user, and stores the same. Specifically, the contract confirmation unit 1043 of the server 10 assigns a digital signature to the contract information based on the received request and stores it. The contract confirmation unit 1043 of the server 10 searches the document ID item of the document table 1014 based on the document ID, and acquires the contract information. The contract confirmation unit 1043 of the server 10 affixes a digital signature to the acquired contract information and stores it in the document data item of the document table 1014. The contract confirmation unit 1043 of the server 10 may update (overwrite) the document data item with the contract information to which the digital signature has been affixed, or may store the contract information before the digital signature has been affixed in a separate storage device (not shown). The contract confirmation unit 1043 of the server 10 may include in the electronic signature any of the following information: document ID, email address of the first user, email address of the second user, approval date and time, confirmation date and time, authentication method of the approval date and time, authentication method of the confirmation date and time, value of input data for each input item, consent (approval) of the first user, second user, timestamp, etc. As a result, the contract confirmation unit 1043 of the server 10 attaches a digital signature indicating that the second user has approved the conclusion of the contract in the contract information to the contract information, and stores the contract information. This makes it possible to prevent a third party from impersonating or tampering with the contract information.

[0086] <Contract correction processing> The contract correction process is a process for correcting the electronic contract information concluded by the user through the contract creation process and the contract confirmation process. In this disclosure, a contract correction process performed by a first user will be described as an example, but the contract correction process may be performed by a second user or any other user.

[0087] <Outline of contract correction processing> The contract correction process is a series of processes that accept access from a user, present the user with a correction screen that displays the contract information, accept correction operations for the contract information from the user, accept confirmation operations regarding the content of the correction operations from the contracting parties, and store the correction content.

[0088] <Details of contract correction processing> The contract correction process is explained in detail below.

[0089] In step S501, the first user operates the input device 206 of the first user terminal 20 to execute a browser application or the like, and opens the correction page D1 by inputting the URL of a web page (correction page) for executing the correction process. The control unit 204 of the first user terminal 20 transmits a request including the first user ID 2011 for opening the correction page to the server 10.

[0090] When the server 10 receives the request, it generates a correction page and transmits it to the first user terminal 20. The control unit 204 of the first user terminal 20 displays the correction page on the display 2081 of the first user terminal 20 for presentation. The correction page D1 includes an input field for inputting a document ID. The first user operates the input device 206 of the first user terminal 20 to input the document ID of the contract information for which the contract correction process is to be performed. The contract correction unit 1051 of the server 10 acquires one or more pieces of contract information in which the first user was previously involved as a creator or a checker from the document table 1014, and transmits the information to the first user terminal 20. The control unit 204 of the first user terminal 20 displays a list of the received one or more pieces of contract information on the display 2081 of the first user terminal 20. The first user may operate the input device 206 of the first user terminal 20 to select contract information related to the contract document correction process from the one or more pieces of contract information displayed in the list. The control unit 204 of the first user terminal 20 transmits the first user ID 2011 and the document ID related to the contract correction process to the server 10. The contract correction unit 1051 of the server 10 receives and accepts the first user ID 2011 and the document ID.

[0091] In step S502, the contract correction unit 1051 of the server 10 searches the document ID item of the document table 1014 based on the document ID included in the received request, and acquires contract information. The contract correction unit 1051 of the server 10 searches the document ID item of the confirmation table 1015 based on the document ID included in the received request, and acquires confirmer information. The contract correction unit 1051 of the server 10 identifies the first user based on the first user ID 2011 included in the request received from the first user terminal 20.

[0092] In step S503, upon receiving the request, the server 10 generates a correction page and transmits it to the first user terminal 20. The control unit 204 of the first user terminal 20 displays the correction page on the display 2081 of the first user terminal 20 for presentation. 19 is an example of a correction screen in the correction process. A correction page D1 is displayed on the display 2081 of the first user terminal 20. The correction page D1 includes an object D11 for arranging object information in the contract information, document data D12, and a send button D13. The object D11 includes a cancellation object D111, an input field D112, and a stamp field D113. The first user can operate the input device 206 of the first user terminal 20 to select an icon representing each object included in the object D11, thereby placing the selected object at any position in the document data D12. The document data D12 includes cancellation objects D121 and D122, input fields D123 and D124, stamp fields D125 and D126, and corrections D127 and D128 arranged in the document data D12. The user can freely input character string information (text information), image information, and other arbitrary information into the input fields D123 and D124. In the present disclosure, an example in which character string information is input into the input fields D123 and D124 will be described as an example. Note that the input fields D123 and D124 may be input fields that accept information input from at least one of the first user and the second user, or from both of them. The user can input information indicating the seal, such as image information related to the user's seal, character string information, etc., in the seal fields D125 and D126. Note that the seal fields D125 and D126 may be input fields that accept input of information indicating the seal from at least one of the first user and the second user, or both.

[0093] <Correction input operation> In step S504, the contract correction unit 1051 of the server 10 executes a correction receiving step of receiving a correction operation for the contract content of the contract document stored in the contract storage step. The correction receiving step executes a step of receiving a correction operation for the content of the contract document from the first user. Specifically, the first user can operate the input device 206 of the first user terminal 20 to place the object D11 at any position in the document data D12. The first user operates the input device 206 of the first user terminal 20 to select icons representing each object included in object D11 (cancel object D111, input field D112, stamp field D113), thereby placing the cancel objects D121, D122, input fields D123, D124, stamp fields D125, and D126 in the desired positions of the document data D12. For example, the first user can express a part of the contract information related to the document data D12 as being crossed out with a double line by placing the cancellation objects D121 and D122 on a clause, provision, wording, or the like that the first user wants to cancel among the parts and sections of the document data D12. This makes it possible to express as data that a part of the part and section of the document data D12 has been cancelled for the contract information. For example, the first user can place input fields D123 and D124 at the position of the article, clause, wording, etc., within the part or section of document data D12 where the first user wants to insert the wording, thereby expressing that the character string information (text information) entered into input fields D123 and D124 has been inserted (added, appended) to a specified position of document data D12 as part of the contract information related to document data D12. For example, the first user can place stamp fields D125, D126 at the desired location within a portion or section of document data D12 where the first user wants to stamp, thereby expressing that the stamp information entered in stamp fields D125, D126 has been placed (stamped) at a specified location on document data D12 as part of the contract information related to document data D12. This makes it possible to make corrections to the contract, such as deleting (canceling) clauses, provisions, wording, etc., and inserting clauses, provisions, wording, etc., in the contract information related to document data D12, and to approve the corrections by affixing a seal, in the electronic contract system.

[0094] In step S504, the correction acceptance step includes a cancellation step of accepting from the user an operation to place a cancellation object indicating cancellation of part of the contract content over a part of the contract document, a correction placement step of placing a correction input field capable of accepting input from the user near the cancellation object placed in the cancellation step, and a correction input step of accepting input from the user into the correction input field placed in the correction placement step. Specifically, in response to the first user's operation to place the cancel object D121 at a predetermined position in the document data D12, the control unit 204 of the first user terminal 20 automatically places an input field D123 near the predetermined position where the cancel object D121 is placed. The first user can input a character string (text information) relating to the correction content in input field D123, thereby inserting (adding, appending) the character string information (text information) at a predetermined position in document data D12. This allows the user to cancel part of the contract document by placing the cancel object at the part of the contract document that he or she wishes to cancel without performing complicated operations. Also, the user can add text or the like to the contract document by entering it in the correction input field.

[0095] In step S504, the correction acceptance step includes a stamp placement step of placing a correction stamp field capable of accepting stamping operations from one or more users near the correction input field placed in the correction placement step, and a correction stamp step of accepting input from one or more users into the correction stamp field placed in the correction placement step. Specifically, in response to the first user's operation to place the cancellation object D121 at a predetermined position in the document data D12, the control unit 204 of the first user terminal 20 automatically places a stamp field D125 near the predetermined position where the cancellation object D121 is placed. The first user can input information indicating the seal, such as image information related to his / her seal, character string information, etc., by performing a predetermined operation in the seal field D125. Note that the seal field D125 may be configured not to accept input from the first user, but to accept input from the second user in the correction confirmation process described later. This allows the corrected contract document to be approved by one or more users again. In this case, by making it possible to accept a seal operation near the correction, the experience of correcting a contract document, which has traditionally been done with paper contract documents, can be realized electronically.

[0096] In step S504, the control unit 204 of the first user terminal 20 executes a correction portion presenting step of presenting information indicating the correction portion of the content of the contract document, based on the correction operation accepted in the correction accepting step. Specifically, the control unit 204 of the first user terminal 20 displays the corrections D127 and D128 on the correction page D1 in accordance with the arrangement of the cancellation objects D121 and D122 and the input fields D123 and D124 by the first user. Specifically, control unit 204 of first user terminal 20 generates information related to corrections D127 and D128 based on information of cancellation objects D121, D122 and input fields D123, D124 arranged in document data D12. Corrections D127 and D128 are display fields that present information (text information) indicating the content of the corrections made by the first user in document data D12. For example, when the position where the cancel object D121 is placed overlapping is line A of the document data D12, the number of characters in the text of the document data D12 where the cancel object D121 is placed overlapping (the number of characters in the document data D12 cancelled by the cancel object D121) is B characters, and the number of characters in the string (text information) entered in the input field D123 is C characters, the control unit 204 of the first user terminal 20 displays a string such as "Line A, character B deleted, character C added" in the correction location D127. This makes it possible to present the user with notations indicating the corrections or revisions made (deletion of XX character on line XX, addition of XX character on line XX, etc.) depending on the content of the corrections. The user can intuitively confirm what corrections have been made.

[0097] The first user can check the contents of the cancellation objects D121, D122, input fields D123, D124, stamp fields D125, D126, and corrections D127, D128 arranged in the document data D12, and can correct the object information as necessary.

[0098] <Send process> In step S505, the first user selects the send button D13 by operating the input device 206 of the first user terminal 20. As a result, a request for executing a correction confirmation process for confirming the correction contents with other users for the contract information identified in step S502 is transmitted to the server 10.

[0099] The contract correction unit 1051 of the server 10 executes a correction notification step of notifying the content of the correction operation accepted in the correction acceptance step to a user other than the first user, such as the second user or the approver user. Specifically, the contract correction unit 1051 of the server 10 searches for a document ID in the document table 1014 based on the document ID included in the request, and obtains a creator ID. The contract correction unit 1051 of the server 10 searches for a user ID in the user table 1012 based on the creator ID, and obtains an email address (creator email address). The contract correction unit 1051 of the server 10 searches for a document ID in the confirmation table 1015 based on the document ID included in the request, and obtains a confirmer email address. The contract correction unit 1051 of the server 10 sends a message to the creator email address and the checker email address requesting confirmation of the contract information corrected by the first user. The message may be sent via any information transmission means such as a chat service, instead of email addresses. The email address of the user who corrected the contract information (first user in this disclosure) may be excluded from the destination email addresses. This is because the first user is the user who corrected the contract information, and the execution of the correction confirmation process may be omitted. The message includes URL (Uniform Resource Locator) information including a correction ID for identifying the correction information. The URL may directly include the correction ID, or may include information such as a character string obtained by arbitrarily encrypting the correction ID, or a character string that can identify the correction ID by referring to a table (not shown). The URL may also include information for identifying the person who checks the correction (the person who checks the correction, the destination of the message) in the correction check process.

[0100] In step S505, the contract correction unit 1051 of the server 10 executes a correction notification step of notifying multiple users other than the first user of the contents of the correction operation accepted in the correction acceptance step, in the approval order when the contract document was agreed upon. Specifically, when there are multiple confirmer email addresses, the contract correction unit 1051 of the server 10 may send a message requesting confirmation of the corrected contract information in the order of confirmation in the confirmation order of the confirmation table 1015. Note that when the creator email address is included in the message destination, the contract correction unit 1051 of the server 10 sends the message to that creator email address before or after the confirmer email address. The execution order of the correction confirmation process may be stored and managed using a table such as the confirmation table 1015 in the contract confirmation process already described. The contract correction unit 1051 of the server 10 excludes the email address of the user (the first user in this disclosure) who corrected the contract information from the creator email address and the verifier email address, and sends a message to the creator email address and the verifier email address in accordance with the approval order. When the message destination includes the creator email address and multiple verifyer email addresses, the contract correction unit 1051 of the server 10 executes a correction confirmation process, which will be described later, in the order in which the messages are received. Each time each user executes the correction confirmation process, the contract correction unit 1051 of the server 10 transmits a message to the creator email address and verifyer email address in the next confirmation order. As a result, if a need arises to correct a contract document concluded between multiple users, the corrections can be approved via the same approval route as when the contract document was agreed upon.

[0101] The contract correction unit 1051 of the server 10 executes an approver presenting step of presenting user candidates including the second user to the first user as user candidates related to the approver of the correction operation accepted in the correction accepting step. The contract correction unit 1051 of the server 10 executes an approver selection step of accepting, from the first user, a selection of an approver user from the user candidates presented in the approver presentation step. Specifically, the contract correction unit 1051 of the server 10 searches for a document ID in the document table 1014 based on the document ID included in the request, and obtains a creator ID. The contract correction unit 1051 of the server 10 searches for a user ID in the user table 1012 based on the creator ID, and obtains an email address (creator email address). The contract correction unit 1051 of the server 10 searches for a document ID in the confirmation table 1015 based on the document ID included in the request, and obtains a confirmer email address. The contract correction unit 1051 of the server 10 transmits the creator email address and the verifier email address to the first user terminal 20. The contract correction unit 1051 of the server 10 may transmit a user other than the creator email address and the verifier email address to the first user terminal 20. For example, the contract correction unit 1051 of the server 10 may include an email address (administrator email address) of a user related to the administrator of the group to which the user related to the creator email address and the verifier email address belongs (a user identified by the administrator ID in the group table 1013). The control unit 204 of the first user terminal 20 displays and presents a list of the received email addresses on the display 2081 of the first user terminal 20. Note that the email address of the user who corrected the contract information (the first user in this disclosure) may be excluded from the email addresses. This is because the first user is the user who corrected the contract information, and the execution of the correction confirmation process may be omitted. The first user operates the input device 206 of the first user terminal 20 to select one or more users for whom the correction confirmation process described below is to be executed from the displayed list of email addresses. Note that the configuration may be such that the order of the correction confirmation process (confirmation order) can be assigned to one or more users. The execution order of the correction confirmation process may be stored and managed using a table such as the confirmation table 1015 in the contract confirmation process already described. For example, the first user does not necessarily need to select all the creator email addresses and the verifying email addresses. For example, the first user may select only one or more users (e.g., administrators) who have a certain approval authority in the group to which the creator and verifying user belong. The control unit 204 of the first user terminal 20 transmits the email addresses selected by the first user to the server 10. The contract correction unit 1051 of the server 10 transmits a message to the selected email address or email addresses requesting confirmation of the corrected contract information.

[0102] The message transmission in step S505 may be configured to execute the same process as the request for confirmation of the contract information in step S106 of the contract confirmation process.

[0103] The contract correction unit 1051 of the server 10 stores the document ID, first user ID 2011, destination email address of the message (including the creator's email address, the checker's email address, the administrator's email address, etc., and also information regarding the order of confirmation such as the confirmation order of the correction confirmation process) included in the request, and object information placed in the document data D12 in the document ID, user ID, correction confirmation data, and correction data items of a new record in the correction table 1021, respectively. This allows the document information and the correction information to be stored in association with each other.

[0104] <Correction confirmation process> In step S506, a process of checking the correction information by the second user (correction checking process) will be disclosed as an example. The correction checking process is executed by each of the correction checkers to whom the message was sent in step S505 already described.

[0105] The second user who is to be the correction confirmer can select the URL described in the received message by operating the input device 306 of the second user terminal 30 or the like, and thereby open the web page specified by the URL using the browser application of the second user terminal 30. As a result, the second user terminal 30 transmits a request to the server 10 to execute the correction confirmation process.

[0106] The contract correction unit 1051 of the server 10 searches the correction ID item of the correction table 1021 based on the correction ID included in the request, and acquires the correction information. Also, the contract correction unit 1051 of the server 10 searches the document ID item of the document table 1014 based on the document ID included in the correction information, and acquires the contract information. The contract correction unit 1051 of the server 10 generates a correction confirmation processing page based on the received request, and transmits it to the second user terminal 30. The control unit 304 of the second user terminal 30 displays the received correction confirmation processing page on the display 3081 of the second user terminal 30. 20 is an example of a correction confirmation screen in the correction confirmation process. Correction confirmation page D2 is displayed on display 3081 of second user terminal 30. Correction confirmation page D2 includes document data D22 and an Agree button D23. In addition, in document data D22, cancellation objects D221, D222, input fields D223, D224, stamp fields D225, D226, and corrections D227, D228 arranged by the first user based on the correction data included in the correction information are displayed.

[0107] The contract correction unit 1051 of the server 10 executes a correction approval step in which, in response to notification to a user other than the first user, such as a second user or an approver user, in the correction notification step, an approval operation is received from a user other than the first user, such as a second user or an approver user. Specifically, the second user checks the contents of the document data D22, the cancellation objects D221, D222, the input fields D223, D224, the seal fields D225, D226, and the corrections D227, D228. The second user can input information indicating a seal into the seal fields D225 and D226 by operating the input device 306 of the second user terminal 30. Alternatively, the input fields D223 and D224 may be configured to be capable of accepting input from the second user. In this case, the input information is stored in the correction data field in association with information indicating that the second user has input the information. When the second user approves (agrees with) the correction content, the second user presses the agree button D23 by operating the input device 306 of the second user terminal 30. Note that when the second user does not approve the correction content, the second user does not press the agree button D23. In this disclosure, the correction confirmation process by the second user has been described as an example, but if the correction confirmer includes an approver user such as an administrator, the approver user will similarly press the consent button D23 by operating his or her own information processing terminal. The control unit 304 of the second user terminal 30 transmits a request including a document ID indicating approval of the correction information including the correction ID to the server 10. Upon receiving the request, the contract correction unit 1051 of the server 10 searches the correction ID item in the correction table 1021 based on the received document ID, and stores the information of the second user included in the correction confirmation data in association with information indicating that the second user has executed the correction confirmation process. This stores that the second user has approved (agreed) the correction information.

[0108] The contract correction unit 1051 of the server 10 executes a correction approval step of accepting approval operations from a plurality of users excluding the first user in the approval order when the contract document was agreed upon. Specifically, when multiple correction checkers are assigned information regarding the order of checking, etc., the multiple correction checkers execute the correction check process in order. When the correction check process by one correction checker is executed, a message is sent to the next correction checker, who then executes the correction check process. When it is determined that the correction check processes by all correction checkers have been executed, it is determined that the correction check process in step S506 is completed, and the storage process in step S507 is executed.

[0109] <Corrective Memory Processing> When the correction confirmation process has been performed by all the correction confirmers, the contract correction unit 1051 of the server 10 executes a correction storage process.

[0110] The contract correction unit 1051 of the server 10 executes a correction creating step of creating a corrected contract document by correcting the contract document stored in the contract storing step, in response to the correction operation accepted in the correction accepting step. Specifically, the contract correction unit 1051 of the server 10 creates new document data (corrected contract document) by arranging the cancellation objects D221, D222, input fields D223, D224, stamp fields D225, D226, and correction points D227, D228 that were placed in the document data D22 in the document data D22.

[0111] The contract correction unit 1051 of the server 10 executes a signature attachment step of associating the correction content related to the correction operation accepted in the correction acceptance step with the contract document, attaching an electronic signature to the correction content, and storing the correction content. The signature attachment step executes a step of associating the correction content with the contract document, attaching an electronic signature to the correction content, and storing the correction content in response to accepting an approval operation from a user other than the first user, such as the second user or the approver user, in the correction approval step. Specifically, the contract correction unit 1051 of the server 10 associates the document data D22, and the cancellation objects D221, D222, input fields D223, D224, seal fields D225, D226, and correction points D227, D228 arranged in the document data D22, and stores them in the document data item of the document table 1014 to which the electronic signature has been added. The contract correction unit 1051 of the server 10 may store the corrected contract document in the document data item of the document table 1014. As a result, the contract document related to the contract information stored in the document data in the document table 1014 is updated.

[0112] The contract correction unit 1051 of the server 10 executes a correction storage step of storing the corrected contract document created in the correction creation step and the contract document before correction stored in the contract storage step in association with each other. The contract correction unit 1051 of the server 10 may update (overwrite) the items of the document data with the corrected contract information to which the electronic signature has been added, or may store the contract information before the correction in a separate storage device (not shown). The corrected contract information and the contract information before the correction may be stored in association with each other. In this case, the signature providing step provides an electronic signature to the corrected contract document stored in the correction storage step and the contract document before the correction, and then stores them.

[0113] The contract correction unit 1051 of the server 10 may include in the electronic signature any of the following information: document ID, the first user's email address, the second user's email address, approval date and time, confirmation date and time, authentication method for the approval date and time, authentication method for the confirmation date and time, input data value for each input item, consent (approval) of the first user, second user, timestamp, etc. As a result, the contract correction unit 1051 of the server 10 adds a digital signature indicating that the second user has approved the conclusion of the contract in the contract information to the contract information, and stores the digital signature. This makes it possible to prevent a third party from impersonating or tampering with the contract information.

[0114] In step S507, the signature providing step executes a step of associating the correction content with the contract document, providing an electronic signature, and storing the electronic signature in response to the approval operation being accepted from a plurality of users other than the first user in the correction approval step. Specifically, the correction confirmation process in step S506 may be configured to be executed excluding the user (first user) who corrected the contract information. In this case, the correction storage process is executed in response to the execution of the correction confirmation process by one or more correction confirmers excluding the first user. In addition, the user who corrected the contract information (first user) may be included in the correction confirmation process in step S506. In this case, the correction storage process is executed in response to the execution of the correction confirmation process by one or more correction confirmers including the first user.

[0115] As a result, in the signature affixing step, the cancellation object accepted in the cancellation step and the input accepted in the correction input step are associated with the contract document, and an electronic signature is affixed thereto and stored. As a result, the signature providing step associates the input received in the correcting and sealing step with the contract document, provides an electronic signature, and stores the input.

[0116] <Reflection contract creation process> In step S507, the contract correction unit 1051 of the server 10 executes a reflection creation step of creating a reflected contract document that reflects the correction contents of the contract document stored in the contract storage step in response to the correction operation accepted in the correction acceptance step. Specifically, the contract correction unit 1051 of the server 10 creates a reflected contract document (clean version, plain number) based on the document data D22 and the contents of the cancellation objects D221, D222, input fields D223, and D224 arranged in the document data D22, in which the object information (correction objects) used during correction operations such as cancellation objects, correction input fields, and correction stamp fields, in which the contents of the correction information are reflected, are not arranged and the correction contents are reflected in the main text. The contract correction unit 1051 of the server 10 deletes the character strings at the positions where the cancellation objects D221, D222 are arranged from the document data 22, and inserts the input information entered in the input fields D223, D224 at the positions where the input fields D223, D224 are arranged. Also, it deletes all the object information related to the corrections such as the arranged cancellation objects D221, D222, the input fields D223, D224, the stamp fields D225, D226, and the correction points D227, D228. As a result, the contract correction unit 1051 of the server 10 generates a clean version of document data (reflected contract document) in which no object information is arranged and in which the correction contents such as cancellation and insertion are reflected in the main text. The contract correction unit 1051 of the server 10 stores the reflected contract document in the clean data item of the target record in the correction table 1021.

[0117] The signature providing step executes a step of storing the reflected contract document created in the reflection creating step without providing an electronic signature to the reflected contract document. Specifically, the contract correction unit 1051 of the server 10 may store the reflected contract document in the clean data item without attaching a digital signature to it. In addition, since the reflected contract document is a contract document in which the correction contents are reflected in the main text and does not include the contents of the correction operation, there is no need to attach an electronic signature to the reflected contract document. As a result, the reflected contract document can be easily utilized without attaching an electronic signature.

[0118] The contract correction unit 1051 of the server 10 executes a search creation step of creating a search index based on the reflected contract document created in the reflection creation step. Specifically, the contract correction unit 1051 of the server 10 may refer to the clean data items in the correction table 1021 and create a search index for document search. A search index is a data structure for quickly accessing specific keywords or phrases within a document. A search index for document search is an index for quickly searching documents related to a search query (keywords or phrases) entered by a user from a large amount of document data. A search index stores information such as the location and frequency of each word within a document, as well as information about related documents, allowing a search engine to quickly identify and present documents relevant to a user's query. Note that, for contract information for which the contract correction process has not been performed, a search index may be created based on the document data items in document table 1014. In other words, contract correction unit 1051 of server 10 creates a search index by referring to the document data items in document table 1014 for contract information for which the document ID is not in correction table 1021, and by referring to the clean data items in correction table 1021 for contract information for which the document ID is in correction table 1021. In addition, when there are multiple correction information records in the correction table 1021 for one contract information (when multiple contract document correction processes have been executed), a search index may be created based on the clean data items of the latest correction information record (excluding the clean data items of older correction information records). This allows the user to search for contract information based on the contents of the latest contract document that reflects the correction information.

[0119] The contract correction unit 1051 of the server 10 executes a search presentation step of presenting search results based on the search index created in the search creation step in response to a search operation. Specifically, any user including the first user and the second user can search for the contract information stored in the document table 1014 and the clean data stored in the correction table 1021 by referring to the search index using a search query. The contract correction unit 1051 of the server 10 transmits the searched clean data to the first user terminal 20. The control unit 204 of the first user terminal 20 displays and presents the received clean data on the display 2081 of the first user terminal 20. 21 is an example of a screen of a reflected contract document. A contract document presentation page D3 is displayed on the display 2081 of the first user terminal 20. The contract document presentation page D3 includes a display area D32 for clean data or document data. When the contract information to be displayed includes clean data, the control unit 204 of the first user terminal 20 displays the latest clean data in the display area D32. When the contract information to be displayed does not include clean data, the control unit 204 of the first user terminal 20 displays document data in the display area D32. This makes it possible to search for, display, and present contract documents based on the contents of the latest contract document that reflects the corrections (reflected contract document).

[0120] <Basic computer hardware configuration> 22 is a block diagram showing the basic hardware configuration of a computer 90. The computer 90 at least includes a processor 901, a main storage device 902, an auxiliary storage device 903, and a communication IF 991 (interface). These are electrically connected to each other by a communication bus 921.

[0121] The processor 901 is hardware for executing an instruction set described in a program, and is composed of an arithmetic unit, a register, a peripheral circuit, and the like.

[0122] The main memory device 902 is for temporarily storing programs, data to be processed by the programs, etc. For example, it is a volatile memory such as a DRAM (Dynamic Random Access Memory).

[0123] The auxiliary storage device 903 is a storage device for saving data and programs, such as a flash memory, a hard disk drive (HDD), a magneto-optical disk, a CD-ROM, a DVD-ROM, or a semiconductor memory.

[0124] The communication IF 991 is an interface for inputting and outputting signals for communicating with other computers via a network using a wired or wireless communication standard. The network is composed of the Internet, a LAN, various mobile communication systems constructed by wireless base stations, etc. For example, the network includes 3G, 4G, 5G mobile communication systems, LTE (Long Term Evolution), wireless networks that can connect to the Internet via a specified access point (e.g., Wi-Fi (registered trademark)), etc. In the case of wireless connection, communication protocols include, for example, Z-Wave (registered trademark), ZigBee (registered trademark), Bluetooth (registered trademark), etc. In the case of wired connection, the network also includes a network that is directly connected by a USB (Universal Serial Bus) cable or the like.

[0125] It should be noted that the computer 90 can be virtually realized by distributing all or part of each hardware configuration among multiple computers 90 and connecting them together via a network. In this way, the computer 90 is a concept that includes not only a computer 90 housed in a single housing or case, but also a virtualized computer system.

[0126] <Basic functional configuration of computer 90> A description will now be given of the functional configuration of a computer realized by the basic hardware configuration (FIG. 22) of a computer 90. The computer comprises at least the functional units of a control unit, a storage unit, and a communication unit.

[0127] The functional units of the computer 90 can also be realized by distributing all or part of the functional units among multiple computers 90 connected to each other via a network. The computer 90 is a concept that includes not only a single computer 90 but also a virtualized computer system.

[0128] The control unit is realized by the processor 901 reading out various programs stored in the auxiliary storage device 903, expanding the programs in the main storage device 902, and executing processes according to the programs. The control unit can realize functional units that perform various information processing depending on the type of program. In this way, the computer is realized as an information processing device that performs information processing.

[0129] The storage unit is realized by a main storage device 902 and an auxiliary storage device 903. The storage unit stores data, various programs, and various databases. Furthermore, the processor 901 can secure a storage area corresponding to the storage unit in the main storage device 902 or the auxiliary storage device 903 in accordance with a program. Furthermore, the control unit can cause the processor 901 to execute processes of adding, updating, and deleting data stored in the storage unit in accordance with the various programs.

[0130] The term database refers to a relational database, which is used to manage sets of data called masters and tables in a tabular format structurally defined by rows and columns, by associating them with each other. In a database, a table is called a table or master, a column in a table is called a column, and a row in a table is called a record. In a relational database, relationships between tables and masters can be set and associated. Usually, a column that serves as a primary key for uniquely identifying a record is set in each table and each master, but setting a primary key in a column is not essential. The control unit can cause the processor 901 to add, delete, or update records in a specific table or master stored in the storage unit according to various programs. Furthermore, by storing data, various programs, and various databases in the storage unit, it can be considered that the information processing device and information processing system according to the present disclosure have been manufactured.

[0131] In addition, the database and master in this disclosure may include any data structure (such as a list, a dictionary, an associative array, or an object) in which information is structurally defined. The data structure also includes data that can be considered as a data structure by combining data with a function, class, method, or the like written in any programming language.

[0132] The communication unit is realized by the communication IF 991. The communication unit realizes a function of communicating with other computers 90 via a network. The communication unit can receive information transmitted from other computers 90 and input the information to the control unit. The control unit can cause the processor 901 to execute information processing on the received information in accordance with various programs. In addition, the communication unit can transmit information output from the control unit to other computers 90.

[0133] <Additional Notes> The matters described in the above embodiments will be supplemented below.

[0134] (Appendix 1) A program having a processor and a memory unit, for providing a computer with a service related to a contract document that is the subject of an agreement between parties, wherein the processor executes a contract storage step (S305) for storing a contract document related to a contract agreed upon between multiple users, a correction acceptance step (S504) for accepting correction operations to the contract content of the contract document stored in the contract storage step, and a signature assignment step (S507) for associating the correction content related to the correction operation accepted in the correction acceptance step with the contract document, assigning an electronic signature to the correction content, and storing it. This allows corrections to be made to an electronic contract that has already been concluded between multiple parties. In addition, the content of the corrections made can be associated with the contract document, and a digital signature can be added and stored. For example, even if an electronic contract concluded between multiple parties contains an error, it can be corrected without having to conclude a new electronic contract.

[0135] (Appendix 2) The correction accepting step (S504) includes a cancellation step of accepting from a user an operation to place a cancellation object indicating the cancellation of part of the contract content over a part of the contract document, a correction placing step of placing a correction input field capable of accepting input from the user near the cancellation object placed in the cancellation step, and a correction input step of accepting input from the user into the correction input field placed in the correction placing step, and the signature assigning step (S507) includes a step of associating the cancellation object accepted in the cancellation step and the input accepted in the correction input step with the contract document, assigning an electronic signature to them, and storing them. This allows the user to cancel part of the contract document by placing the cancel object at the part of the contract document that he or she wishes to cancel without performing complicated operations. Also, the user can add text or the like to the contract document by entering it in the correction input field. Even if an electronic contract concluded between multiple parties contains an error, it is possible to correct only the necessary parts without having to conclude a new electronic contract.

[0136] (Appendix 3) The correction acceptance step (S504) includes a stamp placement step of placing a correction stamp field capable of accepting stamping operations from one or more users near the correction input field placed in the correction placement step, and a correction stamping step of accepting input from one or more users into the correction stamp field placed in the correction placement step, and the signature assignment step (S507) includes a step of associating the input accepted in the correction stamping step with the contract document, assigning an electronic signature to it, and storing it, the program described in Appendix 2. This allows the corrected contract document to be approved by one or more users. In this case, by making it possible to accept a seal operation near the correction, the experience of correcting a contract document, which has traditionally been done with paper contract documents, can be realized electronically. The user can correct the contract document without feeling uncomfortable.

[0137] (Appendix 4) The program according to claim 1, wherein the processor executes a correction part presentation step (S504) of presenting information indicating the correction parts to the contents of the contract document based on the correction operation accepted in the correction acceptance step. This makes it possible to present the user with notations indicating the corrections or revisions made (deletion of XX character on line XX, addition of XX character on line XX, etc.) depending on the content of the corrections. The user can intuitively confirm what corrections have been made.

[0138] (Appendix 5) A program described in Appendix 1, wherein the contract storage step (S305) is a step for storing the contract document agreed upon between the first user and the second user, the correction acceptance step (S504) is a step for accepting a correction operation to the contents of the contract document from the first user, and the processor executes a correction notification step (S505) for notifying the second user of the contents of the correction operation accepted in the correction acceptance step, and a correction approval step (S506) for accepting an approval operation from the second user in response to the notification to the second user in the correction notification step, and the signature assignment step (S507) is a step for associating the correction content with the contract document, assigning an electronic signature, and storing the correction content in response to accepting the approval operation from the second user in the correction approval step. As a result, if a correction becomes necessary in a contract document concluded between a first user and a second user, the contract document can be appropriately corrected without complex circulation procedures, etc., by one user making a correction and the other user approving the correction operation.

[0139] (Appendix 6) The program described in Appendix 1, wherein the contract storage step (S305) is a step of storing the contract document agreed upon between the first user and the second user, the correction receiving step (S504) is a step of receiving a correction operation for the contents of the contract document from the first user, and the processor executes an approver presentation step (S505) of presenting user candidates including the second user to the first user as user candidates for the approver of the correction operation received in the correction receiving step, an approver selection step (S505) of receiving from the first user a selection of an approver user from the user candidates presented in the approver presentation step, a correction notification step (S505) of notifying the approver user of the contents of the correction operation received in the correction receiving step, and a correction approval step (S506) of receiving an approval operation from the approver user in response to the notification to the approver user in the correction notification step, and the signature assignment step (S507) is a step of associating the correction content with the contract document, assigning an electronic signature, and storing the correction in response to receiving the approval operation from the approver user in the correction approval step. This allows the first user to easily select one or more approver users, including the second user, when a correction becomes necessary in a contract document concluded between a first user and a second user.

[0140] (Appendix 7) A program described in Appendix 1, wherein the contract storage step (S305) is a step of storing a contract document agreed upon between multiple users including the first user, the correction receiving step (S504) is a step of receiving a correction operation to the contents of the contract document from the first user, and the processor executes a correction notification step (S505) of notifying multiple users excluding the first user of the contents of the correction operation received in the correction receiving step in the approval order when the contract document was agreed upon, and a correction approval step (S506) of receiving approval operations from multiple users excluding the first user in the approval order when the contract document was agreed upon, and the signature assignment step (S507) is a step of associating the correction contents with the contract document, assigning an electronic signature to it, and storing it in response to receiving approval operations from multiple users excluding the first user in the correction approval step. As a result, if a need arises to correct a contract document concluded between multiple users, the corrections can be approved via the same approval route as when the contract document was agreed upon.

[0141] (Appendix 8) A program described in Appendix 1, in which a processor executes a correction creation step (S507) of creating a corrected contract document by correcting the contract document stored in the contract storage step in accordance with the correction operation accepted in the correction acceptance step, and a correction storage step (S507) of storing the corrected contract document created in the correction creation step in association with the contract document before correction stored in the contract storage step. This makes it possible to store the contract document before the correction and the contract document after the correction in association with each other.

[0142] (Appendix 9) The program according to appendix 8, wherein the signature providing step (S507) is a step of providing an electronic signature to the corrected contract document stored in the correction storage step and the contract document before the correction, and storing them. As a result, in addition to the digital signature 1 already attached to the contract document before the correction, the digital signature 2 is further attached to the corrected contract document and stored.

[0143] (Appendix 10) The program described in Appendix 1, in which a processor executes a reflection creation step (S507) of creating a reflected contract document that reflects the correction content of the contract document stored in the contract storage step in accordance with the correction operation accepted in the correction acceptance step. This makes it possible to generate a contract document (clean version, plain version) in which the correction content is reflected in the main text, without placing object information (correction objects) used during correction operations such as cancellation objects, correction input fields, and correction stamp fields, depending on the correction operations performed by the user. When the user checks or refers to the contents of the contract document, the user can comfortably check the reflected contract document in which no correction object is placed.

[0144] (Appendix 11) The program according to claim 10, wherein the signature providing step (S507) is a step of storing the reflected contract document created in the reflection creating step without providing an electronic signature to the reflected contract document. The reflected contract document is a contract document in which the correction contents are reflected in the main text, and does not include the contents of the correction operation, so there is no need to affix an electronic signature. This means that reflected contract documents can be easily utilized without the need for electronic signatures.

[0145] (Appendix 12) A program as described in Appendix 10, in which a processor executes a search creation step (S507) of creating a search index based on the reflected contract document created in the reflection creation step, and a search presentation step (S507) of presenting search results based on the search index created in the search creation step in response to a search operation. This makes it possible to use the reflected contract document as an index when searching for contract documents, etc. Users can make corrections without re-entering an electronic contract, and can search for contract documents based on the contents of the contract document that reflects the corrections (reflected contract document).

[0146] (Appendix 13) A method implemented on a computer having a processor and a memory, the processor performing all the steps performed in the invention according to any one of claims 1 to 12. This allows corrections to be made to an electronic contract that has already been concluded between multiple parties. In addition, the content of the corrections made can be associated with the contract document, and a digital signature can be added and stored. For example, even if an electronic contract concluded between multiple parties contains an error, it can be corrected without having to conclude a new electronic contract.

[0147] (Appendix 14) An information processing device comprising a control unit and a memory unit, wherein the control unit executes all of the steps executed in the invention according to any one of Supplementary Note 1 to Supplementary Note 12. This allows corrections to be made to an electronic contract that has already been concluded between multiple parties. In addition, the content of the corrections made can be associated with the contract document, and a digital signature can be added and stored. For example, even if an electronic contract concluded between multiple parties contains an error, it can be corrected without having to conclude a new electronic contract.

[0148] (Appendix 15) A system comprising means for performing all the steps performed in any one of the inventions according to appendix 1 to appendix 12. This allows corrections to be made to an electronic contract that has already been concluded between multiple parties. In addition, the content of the corrections made can be associated with the contract document, and a digital signature can be added and stored. For example, even if an electronic contract concluded between multiple parties contains an error, it can be corrected without having to conclude a new electronic contract. [Explanation of symbols]

[0149] 1 System, 10 Server, 101 Memory unit, 104 Control unit, 106 Input device, 108 Output device, 20 First user terminal, 201 Memory unit, 204 Control unit, 206 Input device, 208 Output device, 30 Second user terminal, 301 Memory unit, 304 Control unit, 306 Input device, 308 Output device

Claims

1. A program comprising a processor and a storage unit, the program providing a service related to a contract document to be agreed upon between parties to a computer, The processor, a contract storage step of storing a contract document relating to a contract agreed upon between a plurality of users; a correction receiving step of receiving a correction operation for the contract content of the contract document stored in the contract storing step; a signature assignment step of assigning an electronic signature to the correction content regarding the correction operation accepted in the correction acceptance step in association with the contract document and storing the correction content; A program that executes.

2. The correction acceptance step includes: a cancellation step of receiving an operation from a user to place a cancellation object, which indicates that a part of the contract content is to be cancelled, on a part of the contract document; a correction arrangement step of arranging a correction input field capable of receiving an input from the user in the vicinity of the cancellation object arranged in the cancellation step; a correction input step of accepting an input from the user into the correction input field arranged in the correction arrangement step; Including, the signature providing step includes a step of associating the cancellation object accepted in the cancellation step and the input accepted in the correction input step with the contract document, providing an electronic signature thereto, and storing the electronic signature thereto. The program according to claim 1.

3. The correction acceptance step includes: a stamp arranging step of arranging a correction stamp field capable of receiving a stamping operation from one or more users in the vicinity of the correction input field arranged in the correction arranging step; a correction stamping step of accepting input from the one or more users into the correction stamping field arranged in the correction arrangement step; Including, The signing step includes a step of associating the input received in the correcting and sealing step with the contract document, signing the input with an electronic signature, and storing the electronic signature. The program according to claim 2.

4. The processor, a correction part presenting step of presenting information indicating a correction part to the content of the contract document based on the correction operation accepted in the correction accepting step; Execute The program according to claim 1.

5. The contract storage step is a step of storing the contract document agreed upon between the first user and the second user, the correction receiving step is a step of receiving the correction operation for the content of the contract document from the first user, The processor, a correction notification step of notifying the second user of the content of the correction operation accepted in the correction acceptance step; a correction approval step of accepting an approval operation from the second user in response to the notification to the second user in the correction notification step; Run The signature providing step is a step of, in response to receiving the approval operation from the second user in the correction approval step, associating the correction content with the contract document, providing an electronic signature to the correction content, and storing the electronic signature. The program according to claim 1.

6. The contract storage step is a step of storing the contract document agreed upon between the first user and the second user, the correction receiving step is a step of receiving the correction operation for the content of the contract document from the first user, The processor, an approver presenting step of presenting user candidates including the second user to the first user as user candidates related to the approver of the correction operation accepted in the correction accepting step; an approver selection step of accepting, from the first user, a selection of an approver user from among the user candidates presented in the approver presentation step; a correction notification step of notifying the approver user of the content of the correction operation accepted in the correction acceptance step; a correction approval step of accepting an approval operation from the approver user in response to the notification to the approver user in the correction notification step; Run The signature providing step is a step of, in response to receiving the approval operation from the approver user in the correction approval step, associating the correction content with the contract document, providing an electronic signature to the correction content, and storing the electronic signature. The program according to claim 1.

7. the contract storage step is a step of storing the contract document agreed upon between a plurality of users including a first user, the correction receiving step is a step of receiving the correction operation for the content of the contract document from the first user, The processor, a correction notification step of notifying a plurality of users other than the first user of the content of the correction operation accepted in the correction acceptance step in the approval order when the contract document was agreed upon; a correction approval step of accepting approval operations from a plurality of users other than the first user in the approval order when the contract document was agreed upon; Run The signature providing step is a step of providing and storing an electronic signature associated with the content of the correction to the contract document in response to the approval operation being received from a plurality of users other than the first user in the correction approval step. The program according to claim 1.

8. The processor, a correction creating step of creating a corrected contract document by correcting the contract document stored in the contract storing step in accordance with the correction operation accepted in the correction accepting step; a correction storage step of storing the corrected contract document created in the correction creation step and the contract document before the correction stored in the contract storage step in association with each other; Execute The program according to claim 1.

9. The signature providing step is a step of providing electronic signatures to the corrected contract document stored in the correction storage step and the contract document before the correction, and storing the electronic signatures. The program according to claim 8.

10. The processor, a correction creation step of creating a reflected contract document that reflects the correction content of the contract document stored in the contract storage step in response to the correction operation accepted in the correction acceptance step; Execute The program according to claim 1.

11. The signature providing step is a step of storing the reflected contract document created in the reflection creating step without providing an electronic signature to the reflected contract document. The program according to claim 10.

12. The processor, a search creation step of creating a search index based on the reflected contract document created in the reflection creation step; a search presentation step of presenting search results based on the search index created in the search creation step in response to a search operation; Execute The program according to claim 10.

13. A method implemented on a computer having a processor and a memory, the processor performing all of the steps performed in any of the inventions according to claims 1 to 12.

14. 13. An information processing apparatus comprising a control unit and a storage unit, the control unit executing all steps executed in the invention according to any one of claims 1 to 12.

15. A system comprising means for performing all the steps performed in any one of claims 1 to 12.

Images