Contract management program, information processing device, method for manufacturing information processing system, information processing method

Abstract

This invention provides a contract management program, an electronic contract program, an information processing device, an information processing system, and an information processing method for organizing and managing evidence, forms, and other documents related to specified electronic contracts in association with contract documents. [Solution] A contract management program for causing a computer, which comprises a processor and a memory unit, to store electronic contract documents, wherein the processor executes a contract storage step of storing a plurality of contract documents relating to a contract; a document reception step S601 of receiving document data different from contract documents from a user; a contract selection step S603 of selecting one or more contract documents from the plurality of contract documents stored in the contract storage step to associate the document data received in the document reception step; and a document association step S604 of storing the document data received in the document reception step in association with the one or more contract documents selected in the contract selection step.

Description

Technical Field

[0001] The present disclosure relates to a contract management program, an electronic contract program, an information processing apparatus, an information processing system, and an information processing method.

Background Art

[0002] With the development and spread of computer technology, documents that have hitherto been in paper form are being digitized. For example, it is conceivable to manage documents such as contract documents that require the signatures and seals of the parties in electronic data. Patent Document 1 discloses an information processing system for digital contracts including a creator terminal, a checker terminal, and a contract document management server.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] There is a problem that evidentiary documents, forms, and other documents related to a predetermined electronic contract cannot be organized and managed in association with the contract document. Therefore, the present disclosure has been made to solve the above problems, and an object thereof is to provide a technique for organizing and managing evidentiary documents, forms, and other documents related to a predetermined electronic contract in association with the contract document.

Means for Solving the Problems

[0005] A contract management program for causing a computer having a processor and a memory unit to store electronic contract documents, wherein the processor executes a contract storage step of storing multiple contract documents relating to a contract; a document reception step of receiving document data from a user that is different from a contract document; a contract selection step of selecting one or more contract documents from the multiple contract documents stored in the contract storage step to associate the document data received in the document reception step; and a document association step of storing the document data received in the document reception step in association with the one or more contract documents selected in the contract selection step. [Effects of the Invention]

[0006] According to this disclosure, evidence, forms, and other documents related to a specified electronic contract can be organized and managed in association with the contract document. [Brief explanation of the drawing]

[0007] [Figure 1] This is a block diagram showing the functional configuration of System 1. [Figure 2] This block diagram shows the functional configuration of Server 10. [Figure 3] This is a block diagram showing the functional configuration of the first user terminal 20. [Figure 4] This is a block diagram showing the functional configuration of the second user terminal 30. [Figure 5] This is a diagram showing the functional configuration of mail server 40. [Figure 6] This diagram shows the data structure of user table 1012. [Figure 7] This diagram shows the data structure of group table 1013. [Figure 8] This diagram shows the data structure of document table 1014. [Figure 9] This diagram shows the data structure of confirmation table 1015. [Figure 10] This diagram shows the data structure of input item table 1016. [Figure 11] It is a diagram depicting the data structure of the contract group table 1017. [Figure 12] It is a diagram depicting the data structure of the negotiation record table 1018. [Figure 13] It is a diagram depicting the data structure of the document table 1019. [Figure 14] It is a flowchart showing the operation of the contract creation process (first embodiment). [Figure 15] It is a flowchart showing the operation of the contract confirmation process (second embodiment). [Figure 16] It is a flowchart showing the operation of the communication process. [Figure 17] It is a flowchart showing the operation of the contract creation process. [Figure 18] It is a flowchart showing the operation of the contract confirmation process. [Figure 19] It is a flowchart showing the operation of the document storage process. [Figure 20] It is an example screen showing the operation of the contract creation process. [Figure 21] It is an example screen showing the confirmation request message notified to the second user terminal 30. [Figure 22] It is an example screen showing the operation of the contract confirmation process. [Figure 23] It is an example screen showing the conclusion completion message notified to the first user terminal 20. [Figure 24] It is an example screen showing the conclusion completion message notified to the first user terminal 20. [Figure 25] It is a block diagram showing the basic hardware configuration of the computer 90.

Modes for Carrying Out the Invention

[0008] The embodiments of this disclosure will be described below with reference to the drawings. In all the drawings illustrating the embodiments, common components are denoted by the same reference numerals, and repeated explanations are omitted. The following embodiments are not intended to unduly limit the content of this disclosure as described in the claims. Not all components shown in the embodiments are necessarily essential components of this disclosure. Also, each drawing is a schematic diagram and is not necessarily a strict illustration.

[0009] <Configuration of System 1> System 1 in this disclosure is an information processing system for realizing a service that stores and manages contract information concluded between multiple users. System 1 comprises information processing devices, including a server 10, a first user terminal 20, a second user terminal 30, and a mail server 40, all connected via network N. Figure 1 is a block diagram showing the functional configuration of System 1. Figure 2 is a block diagram showing the functional configuration of server 10. Figure 3 is a block diagram showing the functional configuration of the first user terminal 20. Figure 4 is a block diagram showing the functional configuration of the second user terminal 30. Figure 5 is a block diagram showing the functional configuration of the mail server 40.

[0010] Each information processing device consists of a computer equipped with an arithmetic unit and a memory device. The basic hardware configuration of the computer and the basic functional configuration of the computer realized by said hardware configuration will be described later. For each of the server 10, first user terminal 20, second user terminal 30, and mail server 40, explanations that overlap with the basic hardware configuration and basic functional configuration of the computer described later will be omitted.

[0011] <Server 10 Configuration> Server 10 is an information processing device that provides electronic contract conclusion services between multiple users. Server 10 is an information processing device that provides services for storing and managing contract information concluded between multiple users. The server 10 includes a storage unit 101 and a control unit 104.

[0012] <Configuration of the storage unit 101 of server 10> The storage 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, a negotiation record table 1018, and a document table 1019.

[0013] The application program 1011 is a program that causes the control unit 104 of the server 10 to function as individual functional units.

[0014] User table 1012 is a table that stores and manages information about member users (hereinafter referred to as "users") who use the service. When a user registers to use the service, their information is stored in a new record in user table 1012. This will enable users to utilize the services provided in this disclosure. Note that users utilizing the services under this disclosure do not necessarily need to be registered in user table 1012. User table 1012 is a table with User ID as the primary key and containing columns for User ID, Username, Email Address, and Group ID. Figure 6 shows the data structure of user table 1012.

[0015] The User ID is an item that stores user identification information to identify a user. User identification information is an item that is set to a unique value for each user. The username field is used to store the user's real name. However, the username can also be a nickname or any other string of characters. The email address field is where the user's email address is stored. The Group ID is an item that stores the group identification information of the group to which the user belongs. Groups are defined by the Group Table 1013 described later, and a user may belong to multiple groups.

[0016] Group table 1013 is a table that stores and manages information about the groups to which a user belongs (group information). A group can be any group to which a user belongs, such as a corporation, company, club, organization, or department within a company. Group table 1013 is a table with Group ID as the primary key and containing columns for Group ID, Group Name, and Administrator ID. Figure 7 shows the data structure of group table 1013.

[0017] The Group ID is an item that stores group identification information used to identify a group. This group identification information is a unique value assigned to each group. The group name is an item that stores the name of the group. The group name can be set to any string. The Administrator ID is an item that stores the user identification information of users who have administrator privileges within a group. Users with administrator privileges can arbitrarily define and set administrator IDs for users who have a certain level of status or authority or higher within a group such as an organization.

[0018] Document table 1014 is a table for storing and managing information (contract information) related to electronic contracts exchanged between the creator and the recipient. Document table 1014 is a table with Document ID as the primary key and containing columns for Document ID, Email Address, Chat ID, Document Data, and Creator ID. Figure 8 shows the data structure of document table 1014.

[0019] The Document ID is an item that stores document identification information used to identify contract information. The document identification information is an item with a unique value assigned to each piece of contract information. The email address field is used to store the email address associated with the contract information. The Chat ID is an item that stores chat identification information associated with the contract information. Chat identification information includes user identification information (User ID) in any chat service. Document data is an item that stores contract information (binary or text data) of contract documents related to the conclusion of a contract. Specifically, document data includes data in any data format such as PDF (Portable Document Format), Word, and XML (Extensible Markup Language). The Creator ID is a field that stores user identification information to identify the user who created the contract information.

[0020] Confirmation table 1015 is a table that stores and manages information (confirmer information) including the email address of the user who will be confirming the contract information. Confirmation table 1015 is a table that has columns for document ID, confirmation order, confirmer email address, confirmation flag, language data, access code, and date and time. Figure 9 shows the data structure of confirmation table 1015.

[0021] The document ID is an item that stores the document identification information of the contract information to be reviewed by the verifier. The "Verification Order" field stores information about the order in which contract information is reviewed by the reviewers. The contract information stored by the creator is circulated to the reviewers in the order of the verification order, and verification is performed accordingly. The verifier email address field stores the email address of the person who verifies the contract information. The verifier email address does not need to be registered in advance to use the services related to this disclosure. In other words, the verifier email address does not need to be included in user table 1012. The confirmation flag is an item that stores confirmation identification information to determine whether the confirmation procedure for contract information has been completed by the verifier. When the confirmation of contract information is completed by the verifier, information indicating that the confirmation has been completed, such as a value of True, is stored in the confirmation flag item. Language data is an item that stores information about the verifier's language (language information). The access code is an item that stores the access code set for the verifier. The date and time field stores the date and time when the verifier performed the contract information verification procedure. Specifically, it stores the date and time when the verification identification information was stored in the verification flag field.

[0022] The input item table 1016 is a table that stores and manages information about input items associated with electronic contract information (input item information). Input item table 1016 is a table that has columns for input item ID, document ID, inputter ID, input data, input rules, and date and time. Figure 10 shows the data structure of the input item table 1016.

[0023] The input field ID is an item that stores input field identification information used to identify an input field. The document ID is an item that stores the document identification information of the electronic contract information to which the input field is associated. The Inputter ID is a field that stores the user identification information or email address of the person who entered the data into the input field. Specifically, the Inputter ID stores the Creator ID, the email address of the user identified by the Creator ID, and the Confirmer's email address. Input data is an item that stores the input data entered by the user into the input fields. An input rule field is an item that stores information about the input rules for an input item. Input rules can store information about data types such as date, datetime, text, and integer, as well as, for strings, the number of characters, regular expressions for strings, and other arbitrary input rules for any input item. The date and time field stores the date and time when the user entered data into the input field.

[0024] The contract group table 1017 is a table for storing and managing information about 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, cabinets may be called groups, tags, labels, etc. The contract group table 1017 is a table that has columns for document ID and cabinet ID. Figure 11 shows the data structure of the contract group table 1017.

[0025] The document ID is an item that stores document identification information used to identify contract information. The cabinet ID stores cabinet identification information to identify a cabinet. The cabinet ID is classification information used to manage and classify contract information.

[0026] The negotiation record table 1018 is a table for storing and managing information related to negotiation records (negotiation record information). The negotiation record table 1018 is a table that has columns for document ID and negotiation data. Figure 12 shows the data structure of negotiation record table 1018.

[0027] The document ID is an item that stores document identification information used to identify contract information. Negotiation data is an item that stores data such as negotiation records and negotiation history during contract signing. Negotiation data can include any binary data such as email files (eml files), text files (txt files), various document creation application files (files editable with Word, Excel, PowerPoint, etc.), PDFs, and image files (png, jpeg). Negotiation data may also be stored in a manner that allows identification of multiple negotiation records and negotiation history data by date, etc.

[0028] Document table 1019 is a table for storing and managing information about document data other than contract documents (document information). Document table 1019 is a table that has columns for document ID and document data. Figure 13 shows the data structure of document table 1019.

[0029] The document ID is an item that stores document identification information used to identify contract information. Document data is an item that stores document data separate from contract documents. Document data includes any document data such as quotations, invoices, receipts, delivery notes, acceptance certificates, amendment contracts, and individual contracts. Document data also includes any binary data such as email files (eml files), text files (txt files), various document creation application files (files editable with Word, Excel, PowerPoint, etc.), PDFs, and image files (png, jpeg).

[0030] <Configuration of the control unit 104 of 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 document storage unit 1044. The control unit 104 realizes each functional unit by executing the application program 1011 stored in the storage unit 101.

[0031] The user registration control unit 1041 processes information of users who wish to use the services related to this disclosure and stores it in the user table 1012. Information stored in the user table 1012 is obtained when a user opens a web page operated by the service provider from any information processing terminal, enters information into a designated input form, and sends it to the server 10. The user registration control unit 1041 stores the received information in a new record in the user table 1012, and user registration is completed. As a result, users stored in the user table 1012 can use the service. Prior to the registration of user information in the user table 1012 by the user registration control unit 1041, the service provider may perform a prescribed review and restrict whether or not the user can use the service. The user ID can be any string or number that can identify the user, and may be any string or number desired by the user, or the user registration control unit 1041 may automatically set any string or number.

[0032] The contract creation unit 1042 executes the contract creation process (first embodiment). Details will be described later.

[0033] The contract verification unit 1043 executes the contract verification process (second embodiment). Details will be described later.

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

[0035] <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.

[0036] The first user ID 2011 is the user's account ID. 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 services related to this disclosure to the user. The first user ID 2011 includes information such as a session ID that is temporarily assigned by the server 10 to identify the user using the first user terminal 20.

[0037] The application program 2012 may be pre-stored in the memory unit 201, or it may be configured to be downloaded from a web server operated by the service provider via a communication interface. Application Program 2012 includes applications such as web browser applications. Application program 2012 includes an interpreted programming language such as JavaScript (registered trademark) that runs on a web browser application stored on the first user terminal 20.

[0038] <Configuration of the control unit 204 of the first user terminal 20> The control unit 204 of the first user terminal 20 comprises an input control unit 2041 and an output control unit 2042. The control unit 204 realizes each functional unit by executing an application program 2012 stored in the storage unit 201.

[0039] <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.

[0040] <Configuration of 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.

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

[0042] <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.

[0043] The second user ID 3011 is the 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 services related to this disclosure to the user. The second user ID 3011 includes information such as a session ID that is temporarily assigned by the server 10 to identify the user using the second user terminal 30.

[0044] The application program 3012 may be pre-stored in the memory unit 301, or it may be configured to be downloaded from a web server operated by the service provider via a communication interface. Application program 3012 includes applications such as web browser applications. The application program 3012 includes an interpreted programming language such as JavaScript (registered trademark) that is executed on a web browser application stored on the second user terminal 30.

[0045] <Configuration of the control unit 304 of the second user terminal 30> The control unit 304 of the second user terminal 30 comprises an input control unit 3041 and an output control unit 3042. The control unit 304 realizes each functional unit by executing an application program 3012 stored in the storage unit 301.

[0046] <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.

[0047] <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.

[0048] <Configuration of mail server 40> The mail server 40 is a server that handles sending and receiving emails when multiple users communicate via email. Note that the mail server 40 does not need to be a single server; a different server may be provided for each user (e.g., first user, second user). The mail server 40 can be an SMTP server (Simple Mail Transfer Protocol), a POP3 server (Post Office Protocol), an IMAP server (Internet Message Access Protocol), etc. Users can send emails to other users and receive emails addressed to them by other users through the mail server by operating the mail application installed on their terminal. Examples of mail applications include Gmail, Outlook, and Thunderbird. The mail server 40 includes a storage unit 401 and a control unit 404.

[0049] <Configuration of the storage unit 401 of the mail server 40> The storage unit 401 of the mail server 40 includes an application program 4011.

[0050] Application program 4011 is a program that causes the control unit 404 of the mail server 40 to function as a functional unit.

[0051] <Configuration of the control unit 404 of the mail server 40> The control unit 404 of the mail server 40 includes a mail control unit 4041. The control unit 404 realizes each functional unit by executing the application program 4011 stored in the storage unit 401.

[0052] <System 1 operation> The following describes each process in System 1. Figure 14 is a flowchart showing the operation of the contract creation process (first embodiment). Figure 15 is a flowchart showing the operation of the contract verification process (second embodiment). Figure 16 is a flowchart showing the operation of the communication process. Figure 17 is a flowchart showing the operation of the contract creation process (second embodiment). Figure 18 is a flowchart showing the operation of the contract verification process. Figure 19 is a flowchart showing the operation of the document storage process. Figure 20 shows an example screen illustrating the operation of the contract creation process. Figure 21 is an example screen showing a confirmation request message notified to the second user terminal 30. Figure 22 shows an example screen illustrating the operation of the contract verification process. Figure 23 is an example screen showing the completion message notified to the first user terminal 20. Figure 24 is an example screen showing the completion message notified to the first user terminal 20.

[0053] In this disclosure, the contract creation process (first embodiment), contract verification process (second embodiment), and document storage process in server 10 are described below.

[0054] <Contract creation process (first example)> The contract creation process (first embodiment) is a process in which the creator creates electronic contract information and sends it to the verifier.

[0055] Figure 20 is an example screen showing the operation of the contract creation process (first embodiment). The screen 50 for creating contract information, displayed on the display 2081 of the first user terminal 20, shows a status 510 indicating the current status of contract information creation, buttons 521, 522, and 523 for specifying input items, a contract information display area 530, document data 531, input items 532, 533, and 534, a send button 540, and an exchange document registration button 550.

[0056] <Overview of the contract creation process (first example)> The contract creation process (first embodiment) is a series of processes in which the creator creates electronic contract information, sets the recipient (verifier) ​​of the electronic contract information, sets the input fields for the electronic contract information, sets the input rules for the input fields, receives input data for the input fields from the creator, the user stores negotiation data, which contains negotiation records and negotiation history related to the conclusion of the contract, in association with the created electronic contract information, and sends the electronic contract information to the designated verifier.

[0057] <Details of the contract creation process (first example)> In step S101, the contract creation unit 1042 of the server 10 executes a generation step that generates records to store in association with contract documents in the contract storage step. In step S101, the first user, who will be the creator, operates the input device 206 of the first user terminal 20 to enter a URL to execute the contract creation process (first embodiment) in the browser application of the first user terminal 20 and open a web page (contract creation page). The first user enters the first user ID 2011, password, etc., to log in to the service. As a result, the first user terminal 20 sends a request to the server 10 to execute the contract creation process (first embodiment). The first user operates the input device 206 of the first user terminal 20 and presses a button on the contract creation page, such as the "New Contract" button, to create a new record that associates and stores the contract document, and sends a request to the server 10. When the contract creation unit 1042 of server 10 receives a request, it creates and stores a new record in the document table 1014. The document ID is assigned by incrementing an arbitrary document ID.

[0058] In step S101, the contract creation unit 1042 of the server 10 executes a destination storage step to store destination information associated with the record generated in the generation step.

[0059] The recipient memory step involves storing recipient information for a given email address. Specifically, the contract creation unit 1042 of server 10 generates a new email address and stores it in the email address field of the newly created record in document table 1014. Preferably, the email address is unique for each document ID. The email address domain may be a domain owned by the operator of the electronic contract service related to this disclosure, or it may be any email address. For example, it may be a domain managed by the organization to which the first user belongs. The username, account name, and local part of the generated email address may include a newly assigned document ID. This ensures that each generated email address is unique for each document ID. In this disclosure, the generated email address is described as an example of an email address that can receive emails on the mail server 40 managed by the operator of the electronic contract service related to this disclosure.

[0060] The destination storage step involves storing destination information relating to predetermined identification information. Specifically, the contract creation unit 1042 of server 10 generates a new user ID (chat ID) for the chat service and stores it in the chat ID field of the newly created record in document table 1014. Preferably, the chat ID is unique for each document ID. The generated chat ID may include a newly assigned document ID. This ensures that the generated chat ID is unique for each document ID.

[0061] In step S102, the contract creation unit 1042 of the server 10 executes a contract storage step that stores the contract document relating to the contract received from the first user. 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 can be in any data format, such as PDF (Portable Document Format), Word, or XML (Extensible Markup Language), and can be included in the contract information. The first user operates the input device 206 of the first user terminal 20 and sends the created document data and the first user ID 2011 to the server 10. The contract creation unit 1042 of the server 10 receives the first user ID 2011 and the document data and stores them in the creator ID and document data fields of the record identified by the document ID assigned in step S101 of 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, associated with the destination information generated and stored in step S101.

[0062] The screen 50 for creating contract information displays the document data 531 stored in the document table 1014.

[0063] In step S103, the first user operates the input device 206 of the first user terminal 20 to select and identify the user who will be the verifier (recipient) of the contract information. In this disclosure, the first user selects and identifies the second user as the recipient. The first user operates the input device 206 of the first user terminal 20 to enter the email address of the second user, who will act as the verifier, and sends 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 verifier email address and document ID fields of the verification table 1015, respectively, and stores the contract information in association with the second user's email address. The first user may also set the language and access code of the second user and store them in association with the second user's email address. At this time, the value 1 is stored in the "Confirmation Order" field of the confirmation table 1015. In step S103, the first user may select and set multiple users to be confirmers. In this case, the value in the "Confirmation Order" field of the users to be confirmers is incremented by one according to the selection order and stored. This sets the circulation order of the confirmers in the contract confirmation process (second embodiment) described later. Note that setting the circulation order is not mandatory.

[0064] In step S104, the first user operates the input device 206 of the first user terminal 20 to set the input items for the contract information. Specifically, the first user operates the input device 206 of the first user terminal 20 to set multiple input fields for the contract information created and stored in step S102. The input fields can be any fields, such as a stamp field for stamping seal data, an input field for entering text data such as signature data, a checkbox field for selecting check items, and a date field for entering the date. The first user operates the input device 206 on the first user terminal 20 and sends a request to the server 10 to add an input item. When the contract creation unit 1042 of the server 10 receives the request, it stores the document ID of the contract information in the document ID of the new record in the input item table 1016. In this way, the newly added input item information is stored in association with the contract information. The first user can store multiple input item information in association with the contract information.

[0065] In step S105, the first user sets input rules for each input item to be added. The first user specifies the input rules for each input item information set in step S104 by operating the input device 206 of the first user terminal 20 and sends 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 input item information in the input item table 1016. This allows input rules to be set for each input item.

[0066] In step S106, the contract creation unit 1042 of the server 10 receives input data for multiple input items entered by the first user. Specifically, the first user inputs input data for each input item set in step S105 by operating the input device 206 of the first user terminal 20. For example, the first user may input data for a number used to manage contract information, such as a reference number within the group to which they belong, into the input item where a management number is set. The first user may also input data for the date of the contract signing of the contract information into the input item where a contract signing date is set. Once the first user has finished inputting data into the input items, they send the input item ID and input data for each input item to the server 10. The contract creation unit 1042 of server 10 receives and accepts the input item ID and input data for each input item. The contract creation unit 1042 of server 10 stores the received input data in the input data field of the input item information in the input item table 1016, which is identified 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.

[0067] <Retrieving Exchange Document Data> In step S107, the contract creation unit 1042 of the server 10 executes a document acquisition step in which it acquires exchange document data from the first user, which is exchanged between one party and the other party that perform contract procedures when concluding a contract, unlike contract documents.

[0068] <Acquisition of exchanged document data (first embodiment)> In step S107, the document acquisition step performs the step of acquiring exchange document data based on a file containing exchange document data received from the first user. Specifically, the first user operates the input device 206 of the first user terminal 20 and presses the exchange document registration button 550 displayed on the screen 50 for creating contract information. This causes a file selection dialog for selecting exchange document data to be sent to the server 10 to appear on the display 2081 of the first user terminal 20. The first user operates the input device 206 of the first user terminal 20 and, in the file selection dialog, selects exchange document data, which differs from contract documents and is exchanged between one party and the other party that perform contract procedures when concluding a contract. The control unit 204 of the first user terminal 20 sends (uploads) the selected exchange document data to the server 10. The contract creation unit 1042 of server 10 receives and accepts the exchange document data from the first user terminal 20.

[0069] <Acquisition of exchanged document data (second embodiment)> In step S107, the document acquisition step may also be performed to acquire exchange document data based on a URL that identifies the exchange document data received from the first user. Specifically, the first user may operate the input device 206 of the first user terminal 20 and press the exchange document registration button 550 displayed on the screen 50 for creating contract information, thereby displaying a file selection dialog on the display 2081 of the first user terminal 20, which includes a URL input field for entering a URL that identifies the exchange document data to be sent to the server 10. The first user operates the input device 206 of the first user terminal 20 and enters a URL in the URL input field of the file selection dialog that identifies the exchange document data, which is different from the contract document and is exchanged between one party and the other party that are performing the contract procedures when concluding the contract. The control unit 204 of the first user terminal 20 sends the entered URL to the server 10. The contract creation unit 1042 of server 10 receives a URL from the first user terminal 20, retrieves the exchange document data from the URL, and accepts it.

[0070] <Acquisition of exchanged document data (third embodiment)> Based on the exchange document data obtained through the exchange document data acquisition (first embodiment) and the exchange document data acquisition (second embodiment), a process may be executed to acquire other exchange document data that should be associated with the contract document in the same way as said exchange document data. In step S107, the control unit 204 of the first user terminal 20 executes a second document acquisition step in which it acquires second exchange document data related to the exchange document data based on the destination information contained in the exchange document data acquired in the document acquisition step. Specifically, if the exchange document data acquired by the exchange document data acquisition (first embodiment) or the exchange document data acquisition (second embodiment) is a file containing destination information such as an email file, the control unit 204 of the first user terminal 20 searches for other files stored in the storage unit 201 of the first user terminal 20 based on the destination information and acquires the files included in the search results as exchange document data.

[0071] For example, the second document retrieval step involves searching for and retrieving second exchange document data that contains the same destination information as the exchange document data. Specifically, if the exchange document data acquired by the exchange document data acquisition (first embodiment) or the exchange document data acquisition (second embodiment) is a file containing destination information such as an email file, the control unit 204 of the first user terminal 20 searches the storage unit 201 of the first user terminal 20 for other files with the same destination information as said destination information, and acquires the files included in the search results as exchange document data.

[0072] In step S107, the control unit 204 of the first user terminal 20 executes a second document acquisition step in which it acquires second exchange document data related to the exchange document data based on the subject information contained in the exchange document data acquired in the document acquisition step. Specifically, if the exchange document data acquired by the exchange document data acquisition (first embodiment) or the exchange document data acquisition (second embodiment) is a file containing subject information such as an email file, the control unit 204 of the first user terminal 20 searches the storage unit 201 of the first user terminal 20 for other files with subject information identical or similar to the subject information, and acquires the files included in the search results as exchange document data. Identical or similar subjects may be determined based on a measure such as the cosine similarity between texts. Alternatively, the identity or similarity of subjects may be determined by excluding strings such as "Re:" and "Fw:" that are added when replying or forwarding from the subject.

[0073] The contract creation unit 1042 of server 10 executes a presentation step in which it presents the second exchange document data acquired in the second document acquisition step as candidate documents to the first user for selection. Specifically, the control unit 204 of the first user terminal 20 may be configured to display other files acquired in the exchange document data acquisition (third embodiment) as candidate documents for exchange document data on the display 2081 of the first user terminal 20.

[0074] The related step involves storing the candidate documents selected by the first user in association with the contract documents stored in the contract storage step. Specifically, the first user operates the input device 206 of the first user terminal 20 to select and identify exchange document data to be stored in association with contract information from the candidate documents displayed on the display 2081 of the first user terminal 20. The control unit 204 of the first user terminal 20 transmits the selected exchange document data to the server 10. The contract creation unit 1042 of the server 10 acquires the received exchange document data. This allows only the exchange document data that the first user has reviewed and selected to be stored in association with contract information. This ensures that the system receives suggestions for exchange document data to be stored in association with contract information without any omissions, while avoiding the storage of unnecessary exchange document data.

[0075] In this disclosure, the configuration is disclosed such that the exchange document data acquisition (third embodiment) process is executed by the control unit 204 of the first user terminal 20, but the disclosure is not limited to this. For example, by setting access rights to the mail server etc. used by the first user for the contract creation unit 1042 of the server 10, the contract creation unit 1042 of the server 10 may search the mail server for email files etc. sent and received by the first user and execute the exchange document data acquisition (third embodiment) process. Similarly, by setting access rights to the chat service etc. used by the first user for the contract creation unit 1042 of the server 10, the contract creation unit 1042 of the server 10 may search the chat service etc. sent and received by the first user and execute the exchange document data acquisition (third embodiment) process.

[0076] <Acquisition of Exchange Document Data (Fourth Embodiment)> In step S107, the contract creation unit 1042 of the server 10 performs a importance calculation step to determine the importance of candidate document data exchanged between one party and the other party performing contract procedures during contract conclusion, which differs from the contract document itself, in relation to the contract procedures. The importance calculation step is a step to calculate the importance of the candidate document data based on the files contained in the candidate document data. Specifically, the contract creation unit 1042 of server 10 accesses the mail server, chat service, etc., used by the first user and obtains multiple candidate document data such as email data and chat messages sent and received by the first user. The contract creation unit 1042 of server 10 calculates the importance of each of the obtained candidate document data and stores the candidate document data in association with its importance. The contract creation unit 1042 of server 10 calculates the importance of candidate document data that contains information highly relevant to contract procedures from among the acquired candidate document data. For example, the contract creation unit 1042 of server 10 calculates the importance of acquired candidate document data that includes supporting documents such as contracts, quotations, invoices, and receipts as attached files. The contract creation unit 1042 of server 10 also calculates the importance of acquired candidate document data that contains specific terms such as amounts and legal terms. The importance level may be a value that indicates the relevance to the contract document stored in the contract storage step. For example, the contract creation unit 1042 of server 10 calculates a higher importance level for documents containing textual information such as the contract name and reference number of the contract document stored in the contract storage step.

[0077] The control unit 204 of the first user terminal 20 executes a candidate presentation step in which it presents one or more candidate document data to the first user based on the importance level calculated in the importance calculation step. Specifically, the contract creation unit 1042 of the server 10 transmits multiple stored candidate document data to the first user terminal 20. The control unit 204 of the first user terminal 20 arranges the received candidate document data in order of importance and displays it on the display 2081 of the first user terminal 20, presenting it to the first user. The control unit 204 of the first user terminal 20 may also be configured to present candidate document data with an importance level of or higher than a predetermined value, or a predetermined number of candidate document data in descending order of importance. This allows the first user to view only the candidate document data with high importance without having to review the candidate document data with low importance.

[0078] The control unit 204 of the first user terminal 20 performs a candidate selection step in which it receives a selection operation from the first user for a predetermined candidate document data from one or more candidate document data presented in the candidate presentation step. Specifically, the first user selects a predetermined candidate document data from among multiple candidate document data displayed on the display 2081 of the first user terminal 20 by operating the input device 206 of the first user terminal 20.

[0079] The document acquisition step is the step of acquiring the predetermined candidate document data selected in the candidate selection step as exchange document data. The control unit 204 of the first user terminal 20 sends the selected candidate document data to the server 10. The contract creation unit 1042 of the server 10 acquires the received candidate document data as exchange document data.

[0080] In step S107, the contract creation unit 1042 of the server 10 performs an associated step in which it stores the exchange document data acquired in the document acquisition step in association with the contract document stored in the contract storage step. Specifically, the contract creation unit 1042 of server 10 stores the document ID assigned in step S101 and the acquired exchange document data in the document ID and negotiation data fields of the negotiation record table 1018, respectively. This ensures that the acquired exchange document data is stored in association with the contract document.

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

[0082] In step S108, the contract creation unit 1042 of the server 10 sends a message to the second user notifying them that a request for confirmation of contract information has been sent by the first user. Specifically, the contract creation unit 1042 of the server 10 searches the confirmation order column in the confirmation table 1015 and identifies the user who will be the first confirmer (first confirming user) with the smallest value stored in the confirmation order column. In this disclosure, the first confirming user is, for example, the second user. The contract creation unit 1042 of the server 10 sends a message to the second user's email address notifying them that a request for confirmation of contract information has been sent by the first user, via email or other means of communication. The message sent to the second user will include information about a URL (Uniform Resource Locator) containing a document ID to identify the contract information. The URL may directly contain the document ID, or it may contain information such as an encrypted string of the document ID, or a string that can identify the document ID by referring to an unillustrated table. The URL may also contain information to identify the second user. For example, if the second user has not registered for the service related to this disclosure, the URL must contain information to identify the second user.

[0083] If the first user sets an access code for the second user, the first user will communicate the access code to the second user via email or other means. This ensures that even if the message sent to the second user is intercepted by a third party, the third party cannot execute the contract verification process (second embodiment) unless they obtain the access code.

[0084] Figure 21 is an example 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 a message 61 and information about a URL 62 containing a document ID for identifying contract information.

[0085] <Variation> If the first user selects and sets multiple verifiers in step S103, the configuration may allow different input field information to be set independently for each of the multiple verifiers in step S104. For example, if the first user sets two users, the second user and the ninth user, as verifiers, the input fields for the contract start date and contract end date may be set for the second user, and the input field for the contract signing date may be set for the ninth user. In this case, in the contract confirmation process described later (second embodiment), the second user can input data for the contract start date and contract end date, but cannot input data for the contract signing date. On the other hand, the ninth user cannot input data for the contract start date and contract end date, but can input data for the contract signing date. The configuration may also allow multiple verifiers to be selected and set for a single input field.

[0086] On screen 50 for creating contract information, input fields 532, 533, and 534 are drawn as drawing objects. For input fields 532 and 533, the user identification information "USER-B" of the user who has been selected and set to input the input field is drawn as the assignment, and the input field type is drawn as "Text". For input field 534 related to stamping, the user identification information "USER-C" of the user who has been selected and set to stamp is drawn as the assignment, and the input field type is drawn as "Stamp".

[0087] <Contract Verification Process (Second Example)> The contract verification process (second embodiment) is a process in which the verifier confirms the contents of the electronic contract information received from the creator.

[0088] <Overview of the contract verification process (second example)> The contract confirmation process (second embodiment) is a series of processes that accepts access from the confirmer, presents the confirmer with a confirmation screen displaying the contract information, accepts input data for the input fields from the confirmer, and accepts data from the confirmer regarding the confirmation of the contract information.

[0089] <Details of the contract verification process (second example)> In step S301, the second user, who will act as the verifier, can open the webpage specified by the URL by operating the input device 306 of the second user terminal 30 and selecting the URL contained in the received message, thereby opening the webpage specified by the URL in the browser application of the second user terminal 30. As a result, the second user terminal 30 sends a request to the server 10 to execute the contract verification process (second embodiment).

[0090] If the second user's record in the verification table 1015 contains an access code field, the system can request the second user to enter an access code and then compare the entered access code with the access code stored in the second user's record in the verification table 1015 to perform authentication for the second user. Specifically, server 10 sends an input screen for authenticating the access code to the second user terminal 30. The second user operates the input device 306 on the second user terminal 30, enters the access code, and sends it to server 10. The contract confirmation unit 1043 of server 10 determines whether the received access code matches the access code stored in the second user's record in the confirmation table 1015. If they match, the contract confirmation process (second embodiment) continues. If they do not match, the contract confirmation process (second embodiment) is terminated. Note that the authentication process using the access code may be omitted.

[0091] The contract verification unit 1043 of server 10 searches the document ID field in document table 1014 based on the document ID included in the received request and obtains contract information. The contract verification unit 1043 of server 10 searches the document ID field in verification table 1015 based on the document ID included in the received request and obtains verifier information. The contract verification unit 1043 of server 10 searches the document ID field in input item table 1016 based on the document ID included in the received request and obtains input item information associated with the contract information.

[0092] In step S302, the contract verification 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 based on identification information for identifying the second user included in the URL. If the second user has not registered for the service related to this disclosure, it is necessary to identify the second user from the URL. For example, the URL may include information for identifying the second user, such as the second user's email address or user ID.

[0093] In step S303, the contract confirmation unit 1043 of the server 10 generates a confirmation screen based on the acquired contract information, verifier information (information identifying the second user), and input item information, and sends it to the second user terminal 30.

[0094] Specifically, the display 3081 of the second user terminal 30 presents the second user with a confirmation screen that accepts an operation to approve the contract information. The second user confirms and approves the contract information displayed on the display 3081 of the second user terminal 30. Furthermore, the confirmation screen presented to the second user may be configured to display the screen in the language specified to the verifier, based on the language information stored in the language data field of the second user's record in confirmation table 1015.

[0095] Figure 22 shows an example of a confirmation screen illustrating the operation of the contract confirmation process (second embodiment). The confirmation screen 70 for approving contract information, displayed on the display 3081 of the second user terminal 30, displays a status 710 indicating the current status of contract information creation, a contract information display area 730, document data 731, input items 732, 733, 734, 735, 736, and an agreement button 740.

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

[0097] In step S305, the contract verification unit 1043 of the server 10 performs a presentation step in which it presents to the second user the exchange document data that was stored in association with the contract document in the related step, before the second user approves the contract document. Specifically, the second user checks the contract information and input data displayed on the display 3081 of the second user terminal 30. If they wish to check the negotiation data, they operate the input device 306 of the second user terminal 30 and press the negotiation data viewing button 750 displayed on the confirmation screen 70 for checking the contract information. The control unit 304 of the second user terminal 30 sends a request to the server 10 to view the negotiation data, including the document ID. The contract confirmation unit 1043 of the server 10 searches the document ID item in the negotiation record table 1018 based on the received document ID and retrieves one or more negotiation data. The contract confirmation unit 1043 of the server 10 sends the retrieved one or more negotiation data to the second user terminal 30. The control unit 304 of the second user terminal 30 displays the received one or more negotiation data on the display 3081 of the second user terminal 30. This allows the second user to review negotiation data, such as negotiation records and negotiation history, before agreeing to and approving the conclusion of the contract information received from the first user, as described later. For example, if another user tries to deceive the second user into concluding a contract by impersonating the first user, the second user can more easily detect the other user's fraudulent activity by reviewing the negotiation data.

[0098] In step S305, 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 based on the contract information received from the first user. The second user confirms the contract information and input data displayed on the display 3081 of the second user terminal 30. If the second user agrees to or accepts the contents, they operate the input device 306 of the second user terminal 30 and press the consent button 740 displayed on the confirmation screen 70 for confirming the contract information. This causes the server 10 to execute a process that sends a request containing the document ID, information identifying the second user, and the input data for each input item entered in step S305. The information identifying the second user may also be the second user ID 3011. The contract verification unit 1043 of server 10 stores information indicating that the second user has confirmed the contract information based on the received request. Specifically, the contract verification unit 1043 of server 10 searches the verification table 1015 based on the received document ID and information identifying the second user, and stores the value of True in the verification flag field of the record. For example, if the information identifying the second user is an email address, it searches the document ID and verifier email address fields in the verification table 1015 and stores the value of True in the verification flag field of the record. If the information identifying the second user is user identification information, it searches the document ID and verifier email address fields in the verification table 1015 based on the email address of the second user identified by searching the user ID field in user table 1012, and stores the value of True in the verification flag field of the record. The contract confirmation unit 1043 of server 10 stores the received input data in the input data item of input item table 1016, which is identified 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 input item table 1016.

[0099] The contract verification unit 1043 of server 10 determines that the contract verification process (second embodiment) has been performed by all verifiers. Specifically, the contract verification unit 1043 of server 10 determines that the contract verification process (second embodiment) has been performed by all verifiers if the verification flag in the verifier's record in the verification table 1015 is set to True. When the contract verification unit 1043 of server 10 has completed the contract verification process (second embodiment) by all verifiers, it sends a message to the first user notifying them that the contract verification process (second embodiment) has been completed. Similarly, the contract verification unit 1043 of server 10 may also send a message to the second user notifying them that the contract verification process (second embodiment) has been completed.

[0100] Specifically, the contract verification unit 1043 of server 10 sends a message to the first user's email address via email or other means of communication notifying them that the second user has completed the verification of the contract information. In other words, it notifies the first user that the second user has approved the conclusion of the contract. As a result, the first user can 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 endpoint containing a document ID to identify the contract information.

[0101] Figure 23 is an example 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 a message 81 and information about a URL 82 containing a document ID for identifying contract information.

[0102] Similarly, the contract confirmation unit 1043 of server 10 may use a chat service (not shown) or the like to send a message notifying the second user that they have completed the 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 endpoint containing a document ID to identify the contract information.

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

[0104] If multiple users are set as verifiers, the contract verification unit 1043 of server 10 may send a message to all verifiers except the user who last executed the contract verification process (second embodiment) to notify them that the contract verification process (second embodiment) has been completed. This allows all verifiers to receive notification that the contract verification process (second embodiment) has been completed by all verifiers. Furthermore, the contract verification unit 1043 of the server 10 may send a message to a user with administrator-level privileges in a group to which multiple verifiers belong, notifying them that the contract verification process (second embodiment) has been completed. Messages can also be sent via email, chat services, etc. This allows the administrator of the group to which the user responsible for verification belongs to be notified that the contract verification process (second embodiment) has been completed.

[0105] Specifically, the contract verification unit 1043 of server 10 retrieves the group ID item by searching the user ID or email address item in user table 1012 based on the user ID or email address. Based on the retrieved group ID item, the contract verification unit 1043 of server 10 retrieves the group ID item in group table 1013, retrieves the administrator ID item, identifies a user with administrator-level privileges by searching the user ID in user table 1012 based on the administrator ID, and sends a message notifying that the contract verification process (second embodiment) has been completed.

[0106] <Electronic signature processing> Step S305 may include an electronic signature process. In response to the 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 stores the contract information received from the first user with an electronic signature indicating that the conclusion of the contract information has been approved. Specifically, the contract verification unit 1043 of server 10 attaches an electronic signature to the contract information and stores it based on the received request. Based on the document ID, the contract verification unit 1043 of server 10 searches the document ID field in the document table 1014 and retrieves the contract information. The contract verification unit 1043 of server 10 affixes an electronic signature to the acquired contract information and stores it in the document data item of the document table 1014. The contract verification unit 1043 of server 10 may update (overwrite) the document data item with the electronically signed contract information, or it may store the contract information before the electronic signature was added in a separate storage device (not shown). The contract verification unit 1043 of server 10 may include any of the following information in the electronic signature: document ID, email address of the first user, email address of the second user, 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 values ​​for each input item, consent (approval) of the first user and the second user, and a timestamp. As a result, the contract verification unit 1043 of the server 10 stores the contract information with an electronic signature indicating that the second user has approved the conclusion of the contract. This prevents impersonation or tampering of the contract information by a third party.

[0107] <Contact Processing> Communication processing is the process of contacting the other party to a contract. Generally, users communicate with the other party, including negotiating contract terms, prior to concluding a contract. Communication between contracting parties continues even after the contract is concluded. Communication can be carried out using any means of communication, such as email, chat services (Slack, Chatwork, LINE WORKS, etc.), and social networking services (SNS). In this disclosure, communication between a first user and a second user is used as an example, but the explanation is not limited to this. The communication process can be applied to communication between any users.

[0108] <Overview of communication processing> The communication process involves a series of operations including entering the recipient's address, creating and editing the communication content (exchange document data such as messages), sending it, and storing the received exchange document data. The recipient's address includes an email address or identification information associated with a specified document ID.

[0109] <Details of communication processing> The details of the communication process are explained below.

[0110] In step S501, the first user operates the input device 206 of the first user terminal 20 to launch the mailer application. The first user operates the input device 206 of the first user terminal 20 to create a new email message or to reply to a predetermined email. At this time, the first user includes the email address generated in step S101 of the contract creation process (first embodiment) in the recipient field of the email. The email address may be included in either CC (Carbon Copy) or BCC (Back Carbon Copy), but it is preferable to include it in CC because if it is set in BCC, the email address will not be included in the reply from the recipient. This makes it possible to store the content of the created email or the reply email in association with the contract information identified by that email address.

[0111] Similarly, the first user may operate the input device 206 of the first user terminal 20 to open the website of a predetermined chat service using a web browser or the like. The first user operates the input device 206 of the first user terminal 20 to create a new chat message or to reply to a predetermined chat message. At this time, the first user includes the chat ID (identification information) generated in step S101 of the contract creation process (first embodiment) in the recipient (also called a mention, etc.) of the chat message. This makes it possible to store the content of the created chat message or the chat message being replied to in association with the contract information identified by the chat ID.

[0112] In step S502, the first user operates the input device 206 of the first user terminal 20 to edit the email message, chat message from the chat service, etc., created in step S501. Specifically, the first user inputs and edits the message subject and body text, and attaches other files to the message.

[0113] In step S503, the first user operates the input device 206 of the first user terminal 20 to send the email message, chat message from the chat service, etc., that was edited in step S502 to the recipient specified in step S501. Specifically, the first user can send an email message by operating the input device 206 of the first user terminal 20 and pressing the "Send" button or the like displayed in the mailer application. The first user can send a chat message by operating the input device 206 of the first user terminal 20 and pressing the "Send" button or the like displayed on the chat service screen.

[0114] In step S504, the document acquisition step performs the step of acquiring exchange document data, which includes destination information stored in the destination storage step, from a server identified based on the destination information.

[0115] The document retrieval step involves retrieving exchange document data, including a specified email address, from a mail server capable of receiving emails from that specified email address. Specifically, the control unit 104 of server 10 sends a request to retrieve the email file that has arrived at mail server 40. The mail control unit 4041 of mail server 40 sends the email file stored in the storage unit 401 of mail server 40 to server 10. Note that the storage unit 401 of mail server 40 contains the email file sent by the first user in step S503. The email file also contains the email address set by the first user in step S501 as recipient information.

[0116] The control unit 104 of server 10 searches the email address field in document table 1014 based on the email address included in the recipient information of the received email file and obtains the document ID. Based on the obtained document ID, the control unit 104 of server 10 searches the document ID field in negotiation record table 1018 and stores the email file in the negotiation data field of the identified record. If there is no record for the obtained document ID in negotiation record table 1018, a new record is created and the email file is stored in the negotiation data field of that record.

[0117] The document retrieval step involves retrieving exchange document data, which includes predetermined identification information as the destination, from a predetermined chat service based on the predetermined identification information. Specifically, the control unit 104 of server 10 sends a request to retrieve chat messages that have arrived at the chat service. The chat service sends the received chat messages to server 10. In addition, the chat service sends the chat messages sent by the first user in step S503 to server 10. Furthermore, the chat message includes the chat ID set for the first user in step S501 as recipient information.

[0118] The control unit 104 of server 10 searches the document table 1014 for the chat ID field based on the chat ID included in the recipient information of the received chat message and retrieves the document ID. Based on the retrieved document ID, the control unit 104 of server 10 searches the negotiation record table 1018 for the document ID field and stores the chat message in the negotiation data field of the identified record. If there is no record for the retrieved document ID in the negotiation record table 1018, a new record is created and the chat message is stored in the negotiation data field of that record.

[0119] <Retrieval of exchange document data (modified example)> The electronic contract service relating to this disclosure may acquire exchange document data by the following methods other than step S107 of the contract document creation process and the communication process, and store it in association with contract information.

[0120] The document retrieval step executes a step to retrieve the exchange document data subject to classification operations, based on the classification operations performed on the exchange document data by the first user. Specifically, the first user operates the input device 206 of the first user terminal 20 to launch any mail application such as Gmail, Outlook, or Thunderbird that is pre-stored on the first user terminal 20. The mail application has a predetermined add-on installed for linking with the electronic contract service related to this disclosure, and is configured to send predetermined requests to the API (Application Programming Interface) provided by the electronic contract service related to this disclosure. The first user operates the input device 206 of the first user terminal 20 to classify a designated email document in a mailer application into a designated classification folder, classification directory, etc. The classification folders are labeled with labels such as contract documents and business projects, and are associated with a designated document ID. Similarly, the first user operates the input device 206 of the first user terminal 20 to assign predetermined classification tags, etc., to a predetermined email document in the mailer application. The classification tags are labels such as contract documents and business projects, and are associated with predetermined document IDs.

[0121] The related step involves storing the exchange document data in association with the contract documents identified by the classification operation. Specifically, the control unit of the first user terminal 20 sends a request to the server 10 containing the classified email document and a predetermined document ID. The contract creation unit 1042 of the server 10 stores the received document ID and email document in the document ID and negotiation data fields of the negotiation record table 1018, respectively. The control unit of the first user terminal 20 sends a request to the server 10 containing an email document with a classification tag and a predetermined document ID. The contract creation unit 1042 of the server 10 stores the received document ID and email document in the document ID and negotiation data fields of the negotiation record table 1018, respectively. Thus, it is also acceptable to configure the system to store exchange document data in association with contract information through classification operations such as those performed by mailers.

[0122] In this disclosure, the contract creation process (second embodiment), contract verification process (second embodiment), and document storage process in server 10 are described below.

[0123] <Contract creation process (second example)> The contract creation process (second embodiment) is a process in which the creator creates electronic contract information and sends it to the verifier.

[0124] Figure 20 shows an example screen illustrating the operation of the contract creation process (second embodiment). The screen 50 for creating contract information, displayed on the display 2081 of the first user terminal 20, shows a status 510 indicating the current status of contract information creation, 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.

[0125] <Overview of the contract creation process (second example)> The contract creation process (second embodiment) is a series of processes in which the creator creates electronic contract information, sets the recipient (the verifier) ​​of the electronic contract information, sets the input fields for the electronic contract information, sets the input rules for the input fields, receives input data for the input fields from the creator, and sends the electronic contract information to the set verifier. In conjunction with the execution of multiple contract creation processes by one or more users (second embodiment), the contract creation unit 1042 of the server 10 executes a contract storage step that stores multiple contract documents related to the contract.

[0126] <Details of the contract creation process (second example)> In step S201, the contract creation unit 1042 of the server 10 receives contract information from the creator that is to be concluded between the creator and the verifier. 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 can be in any data format, such as PDF (Portable Document Format), Word, or XML (Extensible Markup Language), and can be included in the contract information. The first user operates the input device 206 of the first user terminal 20 and sends the created document data and the first user ID 2011 to the server 10. The contract creation unit 1042 of the server 10 receives the first user ID 2011 and the document data and stores them in the creator ID and document data fields of the 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.

[0127] The screen 50 for creating contract information displays the document data 531 stored in the document table 1014.

[0128] In step S202, the first user operates the input device 206 of the first user terminal 20 to select and identify the user who will be the verifier (recipient) of the contract information. In this disclosure, the first user selects and identifies the second user as the recipient. The first user operates the input device 206 of the first user terminal 20 to enter the email address of the second user, who will act as the verifier, and sends 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 S201 in the verifier email address and document ID fields of the verification table 1015, respectively, and stores the contract information in association with the second user's email address. The first user may also set the language and access code of the second user and store them in association with the second user's email address. At this time, the value 1 is stored in the "Confirmation Order" field of the confirmation table 1015. In step S202, the first user may select and set multiple users to be confirmers. In this case, the value in the "Confirmation Order" field of the users to be confirmers is incremented by one according to the selection order and stored. This sets the circulation order of the confirmers in the contract confirmation process (second embodiment) described later. Note that setting the circulation order is not mandatory.

[0129] In step S103, the first user operates the input device 206 of the first user terminal 20 to set the input items for the contract information. Specifically, the first user operates the input device 206 of the first user terminal 20 to set multiple input fields for the contract information created and stored in step S201. The input fields can be any fields, such as a stamp field for stamping seal data, an input field for entering text data such as signature data, a checkbox field for selecting check items, and a date field for entering the date. The first user operates the input device 206 on the first user terminal 20 and sends a request to the server 10 to add an input item. When the contract creation unit 1042 of the server 10 receives the request, it stores the document ID of the contract information in the document ID of the new record in the input item table 1016. In this way, the newly added input item information is stored in association with the contract information. The first user can store multiple input item information in association with the contract information.

[0130] In step S204, the first user sets input rules for each input item to be added. The first user specifies the input rules for each input item information set in step S103 by operating the input device 206 of the first user terminal 20 and sends 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 input item information in the input item table 1016. This allows input rules to be set for each input item.

[0131] In step S205, the contract creation unit 1042 of the server 10 receives input data for multiple input items entered by the first user. Specifically, the first user inputs input data for each input item set in step S204 by operating the input device 206 of the first user terminal 20. For example, the first user may input data for a number used to manage contract information, such as a reference number within the group to which they belong, into the input item where a management number is set. The first user may also input data for the date of the contract signing of the contract information into the input item where a contract signing date is set. Once the first user has finished inputting data into the input items, they send the input item ID and input data for each input item to the server 10. The contract creation unit 1042 of server 10 receives and accepts the input item ID and input data for each input item. The contract creation unit 1042 of server 10 stores the received input data in the input data field of the input item information in the input item table 1016, which is identified 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.

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

[0133] In step S206, the contract creation unit 1042 of the server 10 sends a message to the second user notifying them that a request for confirmation of contract information has been sent by the first user. Specifically, the contract creation unit 1042 of the server 10 searches the confirmation order column in the confirmation table 1015 and identifies the user who will be the first confirmer (first confirming user) with the smallest value stored in the confirmation order column. In this disclosure, the first confirming user is, for example, the second user. The contract creation unit 1042 of the server 10 sends a message to the second user's email address notifying them that a request for confirmation of contract information has been sent by the first user, via email or other means of communication. The message sent to the second user will include information about a URL (Uniform Resource Locator) containing a document ID to identify the contract information. The URL may directly contain the document ID, or it may contain information such as an encrypted string of the document ID, or a string that can identify the document ID by referring to an unillustrated table. The URL may also contain information to identify the second user. For example, if the second user has not registered for the service related to this disclosure, the URL must contain information to identify the second user.

[0134] If the first user sets an access code for the second user, the first user will communicate the access code to the second user via email or other means. This ensures that even if the message sent to the second user is intercepted by a third party, the third party cannot execute the contract verification process (second embodiment) unless they obtain the access code.

[0135] Figure 21 is an example 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 a message 61 and information about a URL 62 containing a document ID for identifying contract information.

[0136] <Variation> If the first user selects and sets multiple verifiers in step S202, the configuration may allow different input field information to be set independently for each of the multiple verifiers in step S103. For example, if the first user sets two users, the second user and the ninth user, as verifiers, the input fields for the contract start date and contract end date may be set for the second user, and the input field for the contract signing date may be set for the ninth user. In this case, in the contract confirmation process described later (second embodiment), the second user can input data for the contract start date and contract end date, but cannot input data for the contract signing date. On the other hand, the ninth user cannot input data for the contract start date and contract end date, but can input data for the contract signing date. The configuration may also allow multiple verifiers to be selected and set for a single input field.

[0137] On screen 50 for creating contract information, input fields 532, 533, and 534 are drawn as drawing objects. For input fields 532 and 533, the user identification information "USER-B" of the user who has been selected and set to input the input field is drawn as the assignment, and the input field type is drawn as "Text". For input field 534 related to stamping, the user identification information "USER-C" of the user who has been selected and set to stamp is drawn as the assignment, and the input field type is drawn as "Stamp".

[0138] <Contract Verification Process (Second Example)> The contract verification process (second embodiment) is a process in which the verifier confirms the contents of the electronic contract information received from the creator.

[0139] <Overview of the contract verification process (second example)> The contract confirmation process (second embodiment) is a series of processes that accepts access from the confirmer, presents the confirmer with a confirmation screen displaying the contract information, accepts input data for the input fields from the confirmer, and accepts data from the confirmer regarding the confirmation of the contract information.

[0140] <Details of the contract verification process (second example)> In step S401, the second user, who will act as the verifier, can open the webpage specified by the URL by operating the input device 306 of the second user terminal 30 and selecting the URL contained in the received message, thereby opening the webpage specified by the URL in the browser application of the second user terminal 30. As a result, the second user terminal 30 sends a request to the server 10 to execute the contract verification process (second embodiment).

[0141] If the second user's record in the verification table 1015 contains an access code field, the system can request the second user to enter an access code and then compare the entered access code with the access code stored in the second user's record in the verification table 1015 to perform authentication for the second user. Specifically, server 10 sends an input screen for authenticating the access code to the second user terminal 30. The second user operates the input device 306 on the second user terminal 30, enters the access code, and sends it to server 10. The contract confirmation unit 1043 of server 10 determines whether the received access code matches the access code stored in the second user's record in the confirmation table 1015. If they match, the contract confirmation process (second embodiment) continues. If they do not match, the contract confirmation process (second embodiment) is terminated. Note that the authentication process using the access code may be omitted.

[0142] The contract verification unit 1043 of server 10 searches the document ID field in document table 1014 based on the document ID included in the received request and obtains contract information. The contract verification unit 1043 of server 10 searches the document ID field in verification table 1015 based on the document ID included in the received request and obtains verifier information. The contract verification unit 1043 of server 10 searches the document ID field in input item table 1016 based on the document ID included in the received request and obtains input item information associated with the contract information.

[0143] In step S402, the contract verification 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 based on identification information for identifying the second user included in the URL. If the second user has not registered for the service related to this disclosure, it is necessary to identify the second user from the URL. For example, the URL may include information for identifying the second user, such as the second user's email address or user ID.

[0144] In step S403, the contract confirmation unit 1043 of the server 10 generates a confirmation screen based on the acquired contract information, verifier information (information identifying the second user), and input item information, and sends it to the second user terminal 30.

[0145] Specifically, the display 3081 of the second user terminal 30 presents the second user with a confirmation screen that accepts an operation to approve the contract information. The second user confirms and approves the contract information displayed on the display 3081 of the second user terminal 30. Furthermore, the confirmation screen presented to the second user may be configured to display the screen in the language specified to the verifier, based on the language information stored in the language data field of the second user's record in confirmation table 1015.

[0146] Figure 22 shows an example of a confirmation screen illustrating the operation of the contract confirmation process (second embodiment). The confirmation screen 70 for approving contract information, displayed on the display 3081 of the second user terminal 30, displays a status 710 indicating the current status of contract information creation, a contract information display area 730, document data 731, input items 732, 733, 734, 735, 736, and an agreement button 740.

[0147] In step S404, the contract confirmation unit 1043 of the server 10 receives input for one or more input fields of contract information. Specifically, the second user operates the input device 306 of the second user terminal 30 to input data to input items 732, 733, 734, and 735 set in the contract information. In this disclosure, input item 736 is not assigned to input by the second user, so it is visually indicated that the second user cannot input data for that item.

[0148] In step S405, 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 based on the contract information received from the first user. The second user confirms the contract information and input data displayed on the display 3081 of the second user terminal 30. If the second user agrees to or accepts the contents, they operate the input device 306 of the second user terminal 30 and press the consent button 740 displayed on the confirmation screen 70 for confirming the contract information. This causes the server 10 to execute a request that includes the document ID, information identifying the second user, and the input data for each input item entered in step S405. The information identifying the second user may also be the second user ID 3011. The contract verification unit 1043 of server 10 stores information indicating that the second user has confirmed the contract information based on the received request. Specifically, the contract verification unit 1043 of server 10 searches the verification table 1015 based on the received document ID and information identifying the second user, and stores the value of True in the verification flag field of the record. For example, if the information identifying the second user is an email address, it searches the document ID and verifier email address fields in the verification table 1015 and stores the value of True in the verification flag field of the record. If the information identifying the second user is user identification information, it searches the document ID and verifier email address fields in the verification table 1015 based on the email address of the second user identified by searching the user ID field in user table 1012, and stores the value of True in the verification flag field of the record. The contract confirmation unit 1043 of server 10 stores the received input data in the input data item of input item table 1016, which is identified by the input item ID associated with the input data. As a result, in step S405, the input data entered by the second user is stored as input item information in input item table 1016.

[0149] The contract verification unit 1043 of server 10 determines that the contract verification process (second embodiment) has been performed by all verifiers. Specifically, the contract verification unit 1043 of server 10 determines that the contract verification process (second embodiment) has been performed by all verifiers if the verification flag in the verifier's record in the verification table 1015 is set to True. When the contract verification unit 1043 of server 10 has completed the contract verification process (second embodiment) by all verifiers, it sends a message to the first user notifying them that the contract verification process (second embodiment) has been completed. Similarly, the contract verification unit 1043 of server 10 may also send a message to the second user notifying them that the contract verification process (second embodiment) has been completed.

[0150] Specifically, the contract verification unit 1043 of server 10 sends a message to the first user's email address via email or other means of communication notifying them that the second user has completed the verification of the contract information. In other words, it notifies the first user that the second user has approved the conclusion of the contract. As a result, the first user can 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 endpoint containing a document ID to identify the contract information.

[0151] Figure 23 is an example 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 a message 81 and information about a URL 82 containing a document ID for identifying contract information.

[0152] Similarly, the contract confirmation unit 1043 of server 10 may use a chat service (not shown) or the like to send a message notifying the second user that they have completed the 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 endpoint containing a document ID to identify the contract information.

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

[0154] If multiple users are set as verifiers, the contract verification unit 1043 of server 10 may send a message to all verifiers except the user who last executed the contract verification process (second embodiment) to notify them that the contract verification process (second embodiment) has been completed. This allows all verifiers to receive notification that the contract verification process (second embodiment) has been completed by all verifiers. Furthermore, the contract verification unit 1043 of the server 10 may send a message to a user with administrator-level privileges in a group to which multiple verifiers belong, notifying them that the contract verification process (second embodiment) has been completed. Messages can also be sent via email, chat services, etc. This allows the administrator of the group to which the user responsible for verification belongs to be notified that the contract verification process (second embodiment) has been completed.

[0155] Specifically, the contract verification unit 1043 of server 10 retrieves the group ID item by searching the user ID or email address item in user table 1012 based on the user ID or email address. Based on the retrieved group ID item, the contract verification unit 1043 of server 10 retrieves the group ID item in group table 1013, retrieves the administrator ID item, identifies a user with administrator-level privileges by searching the user ID in user table 1012 based on the administrator ID, and sends a message notifying that the contract verification process (second embodiment) has been completed.

[0156] <Electronic signature processing> Step S405 may include an electronic signature process. In response to the instruction to approve the conclusion of the contract received from the second user in step S405, the contract confirmation unit 1043 of the server 10 stores the contract information received from the first user with an electronic signature indicating that the conclusion of the contract information has been approved. Specifically, the contract verification unit 1043 of server 10 attaches an electronic signature to the contract information and stores it based on the received request. Based on the document ID, the contract verification unit 1043 of server 10 searches the document ID field in the document table 1014 and retrieves the contract information. The contract verification unit 1043 of server 10 affixes an electronic signature to the acquired contract information and stores it in the document data item of the document table 1014. The contract verification unit 1043 of server 10 may update (overwrite) the document data item with the electronically signed contract information, or it may store the contract information before the electronic signature was added in a separate storage device (not shown). The contract verification unit 1043 of server 10 may include any of the following information in the electronic signature: document ID, email address of the first user, email address of the second user, 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 values ​​for each input item, consent (approval) of the first user and the second user, and a timestamp. As a result, the contract verification unit 1043 of the server 10 stores the contract information with an electronic signature indicating that the second user has approved the conclusion of the contract. This prevents impersonation or tampering of the contract information by a third party.

[0157] <Document storage processing> Document storage processing is the process of storing document data selected by the user, associating it with contract information.

[0158] <Overview of Document Storage Processing> Document storage processing is a series of processes in which the user selects document data to be stored, the system proposes candidate contract documents to the user that can be associated with the document data, the user selects one or more contract information from the candidate contract documents to be associated with the document data, and the system stores the document data in association with the one or more contract information selected by the user. In this disclosure, the document storage process is described by a first user as an example, but is not limited to this. The document storage process can be performed by any user.

[0159] <Details of document storage processing> The details of the document storage process are described below.

[0160] In step S601, the document storage unit 1044 of the server 10 executes a document reception step in which it receives document data from the user that is different from the contract document stored in the contract creation process (second embodiment).

[0161] Figure 24 shows an example screen illustrating the operation of the document storage process. The document storage screen D10, displayed on the display 2081 of the first user terminal 20, for storing document data includes a document registration button D101 and a contract document selector D102. By selecting the icons D1021A, D1021B, and D1021C displayed for each contract document D102A, D102B, and D1021C in the contract document selector D102 using the checkboxes D1022A, D1022B, and D1022C, the contract documents associated with each icon can be displayed on the display 2081 of the first user terminal 20.

[0162] Specifically, the first user operates the input device 206 of the first user terminal 20 to enter a URL for executing the document storage process in the browser application of the first user terminal 20 and open a web page (document storage screen). The first user enters the first user ID 2011, password, etc., to log in to the service. As a result, the first user terminal 20 sends a request to the server 10 to execute the document storage process.

[0163] The first user operates the input device 206 of the first user terminal 20 and presses the document registration button D101 displayed on the document storage screen D10, which causes a file selection dialog for selecting document data to send to the server 10 to appear on the display 2081 of the first user terminal 20. The first user operates the input device 206 of the first user terminal 20 and selects document data different from the contract document stored in the contract creation process (second embodiment) in the file selection dialog. The document data includes any document data such as quotations, invoices, receipts, delivery notes, acceptance certificates, amendment contracts, and individual contracts. The control unit 204 of the first user terminal 20 transmits the selected document data to the server 10. The document storage unit 1044 of server 10 receives and accepts the selected document data.

[0164] <Candidate Proposal Processing (First Example)> In step S602, the document storage unit 1044 of the server 10 executes a candidate proposal step in which, based on the document data received in the document reception step, it proposes to the user one or more candidate contract documents from among the multiple contract documents stored in the contract storage step for selection. Specifically, the document storage unit 1044 of the server 10 analyzes the document data received in step S601, searches the document data in the document table 1014 based on the file name of the document data, strings contained in the document data, etc., and obtains a document ID. For example, it searches the document data in the document table 1014 based on the reference number that identifies the contract document contained in the file name of the document data, the title of the contract document, the reference number that identifies the contract document contained in the strings of the document data, etc., and obtains a document ID for one or more contract information. For example, it searches the document table 1014 for the names of the contracting parties, such as individual names, company names, organization names, group names, etc., contained in the strings of the document data, and obtains a document ID for one or more contract information.

[0165] <Candidate Proposal Processing (Second Example)> In step S602, the document storage unit 1044 of the server 10 executes a candidate suggestion step in which it proposes to the user one or more candidate contract documents from among the multiple contract documents stored in the contract storage step in which the user has previously been involved in contract procedures. Specifically, the document storage unit 1044 of the server 10 searches the user ID column in the user table 1012 based on the first user ID 2011 received from the first user terminal 20, and obtains the first email address of the first user. The document storage unit 1044 of server 10 searches the creator ID field in document table 1014 based on the first user ID 2011 and retrieves the document ID. Similarly, the document storage unit 1044 of server 10 searches the confirmer email address field in confirmation table 1015 based on the first email address and retrieves the document ID. This retrieves the document IDs for one or more contract records in which the first user has previously been involved as a creator or confirmer in contract procedures.

[0166] The candidate proposal step may involve presenting the user with one or more candidate contract documents in which the user has previously been involved in contract procedures, arranged in chronological order of contract signing date, for the user to select from. Specifically, in the candidate proposal processing (second embodiment), the document storage unit 1044 of the server 10 sorts the document IDs of one or more acquired contract information in order of the contract signing date of the contract information identified by the document ID, from newest to oldest. By sorting the document IDs in reverse chronological order, candidate contract documents can be presented to the first user in the order in which they were most recently signed. Candidate contract documents can be conveniently presented to the first user in order of contract signing date.

[0167] <Candidate Proposal Processing (Third Example)> In step S602, the document storage unit 1044 of the server 10 executes a candidate suggestion step in which it proposes to the user one or more candidate contract documents that can be selected by comparing the date information contained in the document data received in the document reception step with the date information contained in multiple contract documents stored in the contract storage step. The date information contained in the document data is the date information specified in the document data, obtained by user input operations or by parsing the string contained in the document data. The date information contained in the contract document is the date information specified in the contract document, obtained by user input operations or by parsing the string contained in the contract document. Specifically, the document storage unit 1044 of the server 10 analyzes the document data received in step S601 and extracts and obtains date-related information (date information) such as the billing date, receipt date, delivery date, and acceptance date contained in the strings, etc., within the document data. In addition to date information, the document storage unit 1044 of the server 10 may also extract and obtain date attribute information (date attribute information) related to the billing date, receipt date, delivery date, and acceptance date. The date attribute information may be specified based on the type of document data, such as invoices, receipts, delivery notes, acceptance certificates, change agreements, and individual contracts. Furthermore, the document storage unit 1044 of the server 10 may be configured to acquire and identify date information and date attribute information based on input operations by the first user, without relying on analysis of document data. For example, the first user operates the input device 206 of the first user terminal 20, inputs date information and date attribute information for each date into a predetermined input field, and sends it to the server 10. The document storage unit 1044 of the server 10 receives and acquires the date information and date attribute information from the first user terminal 20. The document storage unit 1044 of the server 10 searches for contract information by comparing the acquired date information and date attribute information with date information (date information) such as billing date, receipt date, delivery date, and acceptance date contained in the string of the contract document in the document data of the document table 1014. Specifically, if the document data is a delivery note and contains date information relating to the delivery date (first date), the server searches for contract documents in the document data of the document table 1014 that include the first date as the delivery date and obtains the document ID of one or more contract documents.

[0168] Furthermore, the date information and date attribute information of contract documents in the document data of document table 1014 may be information identified in advance by analyzing the string of characters in the contract documents by the control unit 104 of server 10. Alternatively, the date information and date attribute information of contract documents in the document data of document table 1014 may be information obtained based on input operations by users involved in the conclusion of the contract documents, other administrators, etc., without relying on analysis of the document data. Document data is stored in document table 1014, associated with each date information and date attribute information.

[0169] In step S602, the document storage unit 1044 of the server 10 transmits the document IDs of one or more acquired contract information to the first user terminal 20. The display 2081 of the first user terminal 20 presents the received one or more document IDs as candidate contract documents on the contract document selector D102, allowing the first user to select them. The first user can select one or more contract documents D102A, D102B, D102C displayed on the contract document selector D102 using the checkboxes D1022A, D1022B, D1022C by operating the input device 206 of the first user terminal 20.

[0170] In step S603, the document storage unit 1044 of the server 10 executes a contract selection step in which it selects one or more contract documents from among a plurality of contract documents stored in the contract storage step that associate with the document data received in the document reception step. The contract selection step executes a step in which the user selects one or more contract documents from the one or more candidate contract documents proposed to the user in the candidate proposal step. Specifically, the first user selects one or more contract documents D102A, D102B, D102C displayed on the contract document selector D102 using checkboxes D1022A, D1022B, D1022C by operating the input device 206 of the first user terminal 20. The first user may select multiple contract documents D102A, D102B, D102C. The control unit 204 of the first user terminal 20 transmits the document IDs of the selected one or more contract documents to the server 10.

[0171] In step S604, the document storage unit 1044 of the server 10 performs a document association step in which it stores the document data received in the document reception step in association with one or more contract documents selected in the contract selection step. Specifically, the document storage unit 1044 of the server 10 stores the document data received in step S601 in the document data and document ID fields of the document table 1019 for each of the one or more document IDs received in step S602. As a result, the document data received in step S601 is stored in association with the one or more document IDs received in step S602.

[0172] In step S604, the document storage unit 1044 of the server 10 performs a stakeholder identification step to identify one or more involved users who were involved in the contract procedures of one or more contract documents stored in association in the document-related step. Specifically, the document storage unit 1044 of the server 10 searches the document ID field in the document table 1014 based on the one or more document IDs received in step S602 and obtains the creator ID. Based on the obtained creator ID, it searches the user ID field in the user table 1012 and obtains the creator's email address. Similarly, based on one or more document IDs, it searches the document ID field in the confirmation table 1015 and obtains the confirmer's email address. This allows the system to obtain and identify the email addresses of one or more involved users who were involved in the creation or confirmation of the contract procedures for the contract document identified by the one or more document IDs received in step S602. Note that the one or more involved users include any user designated as a related party by the creator or confirmor, in addition to those involved in the creation and confirmation of the contract procedures for the contract document, such as those involved in content confirmation.

[0173] In step S604, the document storage unit 1044 of the server 10 executes a stakeholder notification step in which it notifies one or more involved users identified in the stakeholder identification step that document data has been stored in association with one or more contract documents in the document-related step. Specifically, the document storage unit 1044 of the server 10 sends an email to the acquired email address of the involved user, containing a message indicating that document data has been stored in association with contract information in which the involved user was previously involved in concluding a contract.

[0174] In step S604, the document storage unit 1044 of the server 10 executes an authorization setting step in which it sets the access rights for the document data stored in the document-related step based on the access rights for one or more contract documents stored in association. Specifically, the document storage unit 1044 of the server 10 obtains the viewing rights for one or more document IDs received in step S602 from a column in the document table 1014 that stores viewing rights (not shown). The document storage unit 1044 of the server 10 sets the viewing rights for the document IDs in the document table 1019 that are stored in association with the one or more document IDs. If multiple contract information is associated with one document data, multiple viewing rights corresponding to each of the multiple contract information may be set in the viewing rights for the document data, or the strictest or the lenient viewing rights among the multiple viewing rights corresponding to each of the multiple contract information may be set.

[0175] In the document storage process, document data stored in association with contract information can be referenced by users of the electronic contract service related to this disclosure when they want to check the contract documents included in the contract information. For example, a first user operates the input device 206 of the first user terminal 20 and sends a request to the server 10 to refer to contract information. The control unit 104 of the server 10 retrieves document data relating to the contract document from the document table 1014, and at the same time, searches the document ID item in the document table 1019 based on the document ID of the retrieved document data and retrieves the document data associated with the document ID. The control unit 104 of the server 10 sends the retrieved document data and document data to the first user terminal 20. The control unit 204 of the first user terminal 20 displays the retrieved document data and document data in an associated manner on the display 2081 of the first user terminal 20. For example, the first user can download the document data by selecting the document data displayed on the display 2081 of the first user terminal 20.

[0176] In step S604, a calculation step is performed to calculate evaluation index values ​​for one or more contract documents based on document data stored in association with one or more contract documents in the document-related steps. Specifically, the document storage unit 1044 of server 10 refers to the document table 1019 and retrieves document data associated with one or more contract documents (document IDs). The document storage unit 1044 of server 10 analyzes the document data associated with a given contract document and calculates a contract score (evaluation index value) for that given contract document. • The contract score may also be the number of document data associated with a given contract document. The contract score may be calculated by pre-determining points for each document data associated with a given contract document, based on the type of document (e.g., quotation, invoice, receipt, delivery note, acceptance certificate, amendment contract, individual contract), and summing the predetermined number of points for each document data associated with that document. • The contract score may also be an evaluation index value calculated based on the amounts stated in quotations, invoices, receipts, delivery slips, etc. For example, the larger the amount in the document data associated with a given contract document, the higher the value of the evaluation index may be. The document storage unit 1044 of server 10 stores the calculated contract score in association with the document ID of the specified contract document in the document table 1014. The control unit 104 of server 10 calculates the evaluation index value of the contract document and may present it to the user if the evaluation index value is lower than a predetermined value or higher than a predetermined value.

[0177] In step S604, a calculation step is performed to calculate evaluation index values ​​for the contracting parties of one or more contract documents based on document data stored in association with one or more contract documents in the document-related steps. Specifically, the document storage unit 1044 of server 10 refers to the document table 1019 and retrieves document data associated with one or more contract documents (document IDs). The document storage unit 1044 of server 10 analyzes the document data associated with a given contract document and calculates a credit score (evaluation index value) for the contracting parties of that given contract document. • A credit score may also be the number of document data associated with one or more contractual documents in which a contracting party has been involved in the proceedings. • The credit score may be calculated by pre-determining points for each type of document, such as quotations, invoices, receipts, delivery notes, acceptance certificates, amendment agreements, and individual contracts, and summing the predetermined number of points for each document data associated with one or more contract documents in which the contracting parties were involved in the process. • The credit score may also be an evaluation index value calculated based on the amounts stated in quotations, invoices, receipts, delivery slips, etc. For example, the larger the amount of document data associated with one or more contractual documents in which a contracting party was involved in the process, the higher the evaluation index value may be. The document storage unit 1044 of server 10 stores the calculated credit score in association with the user ID of the contracting party in the user table 1012. The control unit 104 of server 10 may retrieve the credit score of the contracting party from the user table 1012 during contract creation processing, contract confirmation processing, etc., and present it to the user performing the contract creation processing, contract confirmation processing, etc. For example, it may be presented when the credit score of the contracting party is lower than a predetermined value or when the evaluation index value is higher than a predetermined value. This allows the user to proceed with the contract procedure while taking into account the credit score of the contracting party.

[0178] Furthermore, the calculation of evaluation index values ​​may be configured to be performed at any arbitrary time and at predetermined intervals.

[0179] <Basic Computer Hardware Configuration> Figure 25 is a block diagram showing the basic hardware configuration of computer 90. Computer 90 comprises at least a processor 901, main memory 902, auxiliary storage 903, and a communication interface IF991. These are electrically connected to each other by a communication bus 921.

[0180] The processor 901 is hardware for executing the instruction set written in a program. The processor 901 consists of an arithmetic unit, registers, peripheral circuits, etc.

[0181] Main memory 902 is used to temporarily store programs and data processed by programs, etc. For example, it is a volatile memory such as DRAM (Dynamic Random Access Memory).

[0182] Auxiliary storage device 903 refers to a storage device for saving data and programs. Examples include flash memory, HDD (Hard Disc Drive), magneto-optical disk, CD-ROM, DVD-ROM, and semiconductor memory.

[0183] The IF991 communication interface is an interface for inputting and outputting signals for communication with other computers via a network using wired or wireless communication standards. A network consists of various mobile communication systems, such as the internet, LANs, and wireless base stations. For example, a network includes 3G, 4G, and 5G mobile communication systems, LTE (Long Term Evolution), and wireless networks that can connect to the internet via designated access points (e.g., Wi-Fi®). When connecting wirelessly, communication protocols include, for example, Z-Wave®, ZigBee®, and Bluetooth®. When connecting via a wired connection, the network also includes connections made directly via USB (Universal Serial Bus) cables, etc.

[0184] Furthermore, by distributing all or part of each hardware configuration across multiple computers 90 and connecting them to each other via a network, a computer 90 can be virtually realized. Thus, the concept of computer 90 includes not only a computer 90 housed in a single enclosure or case, but also a virtualized computer system.

[0185] <Basic Functional Configuration of Computer 90> The functional configuration of the computer realized by the basic hardware configuration of computer 90 (Figure 25) will be explained. The computer comprises at least one functional unit: a control unit, a memory unit, and a communication unit.

[0186] Furthermore, the functional units of computer 90 can also be realized by distributing all or part of each functional unit across multiple computers 90 interconnected via a network. The concept of computer 90 includes not only a single computer 90 but also a virtualized computer system.

[0187] The control unit is realized when the processor 901 reads various programs stored in the auxiliary storage device 903, loads them into the main memory device 902, and executes processing according to those programs. The control unit can realize various functional units that perform information processing depending on the type of program. In this way, the computer is realized as an information processing device that performs information processing.

[0188] The memory unit is implemented by the main memory 902 and the auxiliary memory 903. The memory unit stores data, various programs, and various databases. The processor 901 can also reserve memory areas corresponding to the memory unit in the main memory 902 or the auxiliary memory 903 according to the program. The control unit can also cause the processor 901 to perform operations such as adding, updating, and deleting data stored in the memory unit according to the various programs. Furthermore, by storing data, various programs, and various databases in the memory unit, the information processing device and information processing system related to this disclosure can be considered to have been manufactured.

[0189] A database, specifically a relational database, is used to manage and link together tabular data sets called masters, which are structurally defined by rows and columns. In a database, tables are called tables, masters are called masters, the columns of tables are called columns, and the rows of tables are called records. In a relational database, relationships can be established and linked between tables and masters. Typically, each table and master has a primary key column to uniquely identify records, but setting a primary key column is not mandatory. The control unit can instruct the processor 901 to add, delete, or update records in specific tables and masters stored in the memory unit, according to various programs.

[0190] Furthermore, the databases and masters in this disclosure may include any data structures (lists, dictionaries, associative arrays, objects, etc.) in which information is structurally defined. Data structures also include data that can be considered as data structures by combining data with functions, classes, methods, etc., written in any programming language.

[0191] The communication unit is implemented by the communication IF991. The communication unit provides the functionality to communicate with other computers 90 via the network. The communication unit can receive information transmitted from other computers 90 and input it to the control unit. The control unit can cause the processor 901 to perform information processing on the received information according to various programs. The communication unit can also transmit information output from the control unit to other computers 90.

[0192] <Note> The details described in each of the above embodiments are noted below.

[0193] (Note 1) A contract management program for storing an electronic contract document in a computer having a processor and a storage unit. The processor executes a contract storage step (S201) of storing a plurality of contract documents related to a contract, a document reception step (S601) of receiving document data different from the contract document from a user, and a contract selection step (S603) of selecting one or more contract documents from the plurality of contract documents stored in the contract storage step and associating the document data received in the document reception step. The program also includes a document association step (S604) of storing the document data received in the document reception step in association with the one or more contract documents selected in the contract selection step. This enables the organization and management of document data such as vouchers, forms, and other documents related to a specific electronic contract by associating them with the contract document.

[0194] (Appendix 2) The contract management program according to Appendix 1, where the processor executes a candidate proposal step (S602) of proposing to the user one or more candidate contract documents from the plurality of contract documents stored in the contract storage step based on the document data received in the document reception step, and the contract selection step (S603) is a step where the user selects one or more contract documents from the one or more candidate contract documents proposed to the user in the candidate proposal step. This allows the user to easily associate and store the document data with the contract document related to the document data, enabling the organization and management of the document data by associating it with the contract document.

[0195] (Appendix 3) The contract management program according to Appendix 2, where the candidate proposal step (S602) is a step of analyzing the document data received in the document reception step and proposing to the user one or more candidate contract documents selectably based on the file name of the document data or the character string included in the document data. This allows users to easily associate and store document data with the contract documents associated with that document data. Document data can be organized and managed in relation to contract documents.

[0196] (Note 4) The contract management program as described in Appendix 1, wherein the processor performs a candidate suggestion step (S602) in which the user is offered one or more candidate contract documents from among a plurality of contract documents stored in the contract storage step in which the user has previously been involved in contract procedures, and the contract selection step (S603) is a step in which the user selects one or more contract documents from the one or more candidate contract documents suggested to the user in the candidate suggestion step. This allows users to remember document data in relation to contract documents they have previously been involved with. Document data can be organized and managed in association with contract documents.

[0197] (Note 5) The candidate proposal step (S602) is a step in the contract management program described in Appendix 4, in which the user proposes one or more candidate contract documents in which the user has previously been involved in contract procedures, arranged in order of contract signing date, for the user to select. This allows users to associate and store document data, and receive candidate contract documents in chronological order of contract signing dates based on contracts they have been involved with in the past. Users can easily organize and manage document data by associating it with contract documents.

[0198] (Note 6) The contract management program as described in Appendix 1, wherein the processor performs a candidate proposal step (S602) in which it proposes to the user one or more candidate contract documents that can be selected by comparing the date information contained in the document data received in the document reception step with the date information contained in a plurality of contract documents stored in the contract storage step, and the contract selection step (S603) is a step in which the user selects one or more contract documents from the one or more candidate contract documents proposed to the user in the candidate proposal step. This allows users to receive suggestions for contract documents to which document data should be associated, based on the date information of the document data, and to easily organize and manage the document data in association with the contract documents.

[0199] (Note 7) In the candidate proposal step (S602), the date information contained in the document data is the date information specified in the document data, obtained by user input or by parsing the string contained in the document data, as described in Appendix 6 of the contract management program. This allows users to receive suggestions for contract documents to which document data should be associated, based on the date information of the document data, and to easily organize and manage the document data in association with the contract documents.

[0200] (Note 8) The contract management program described in Appendix 1, wherein the processor performs a stakeholder identification step (S604) in which it identifies one or more involved users who were involved in the contract procedures for one or more contract documents stored in association with each other in a document-related step, and a stakeholder notification step (S604) in which it notifies one or more involved users identified in the stakeholder identification step that document data has been stored in association with one or more contract documents in a document-related step. This allows users involved in the contract procedures for a contract document to receive notifications when document data is associated with that contract document. They can also confirm that document data has been associated with the contract document.

[0201] (Note 9) A contract management program as described in Appendix 1, wherein the processor performs an authorization setting step (S604) in which it sets the access rights to document data stored in a document-related step based on the access rights to one or more contract documents stored in association. This makes it easy to set access permissions for document data stored in association with contract documents.

[0202] (Note 10) A contract management program as described in Appendix 1, wherein the processor performs a calculation step (S604) in which it calculates evaluation index values ​​for one or more contract documents based on document data stored in association with one or more contract documents in a document-related step. This allows for the calculation of evaluation index values ​​for contract documents based on document data stored in association with the contract documents. Contract documents can then be scored.

[0203] (Note 11) A contract management program as described in Appendix 1, wherein the processor performs a calculation step (S604) of calculating evaluation index values ​​for the contracting parties of one or more contract documents based on document data stored in association with one or more contract documents in a document-related step. This allows for the calculation of evaluation index values ​​related to the contracting parties in a contract document, based on document data stored in association with the contract document. It also enables the scoring of the creditworthiness of the contracting parties.

[0204] (Note 12) An information processing device comprising a processor and a memory unit, wherein the processor executes a contract management program described in any of the appendices 1 to 11. This allows document data such as supporting documents, forms, and other documents related to a specified electronic contract to be organized and managed in association with the contract document.

[0205] (Note 13) A method for manufacturing an information processing system, comprising an information processing device having a processor and a memory unit, wherein the processor executes a contract management program described in any of the appendices 1 to 11. This allows document data such as supporting documents, forms, and other documents related to a specified electronic contract to be organized and managed in association with the contract document.

[0206] (Note 14) An information processing method executed by a computer including a processor and a storage unit, wherein the computer executes a contract management program described in any one of Appendices 1 to 11. Thereby, document data such as certificates, forms, and other documents related to a predetermined electronic contract can be sorted and managed in association with the contract document.

Explanation of Signs

[0207] 1 System, 10 Server, 101 Storage Unit, 104 Control Unit, 106 Input Device, 108 Output Device, 20 First User Terminal, 201 Storage Unit, 204 Control Unit, 206 Input Device, 208 Output Device, 30 Second User Terminal, 301 Storage Unit, 304 Control Unit, 306 Input Device, 308 Output Device

Claims

1. A contract management program for causing a computer, which comprises a processor and a memory unit, to store electronic contract documents, The aforementioned processor, A contract storage step that stores multiple contract documents related to the contract, A document reception step that receives document data from the user that is different from the aforementioned contract document, A contract selection step involves associating the document data received in the document reception step with one or more contract documents from the plurality of contract documents stored in the contract storage step, A document-related step involves storing the document data received in the document reception step in association with the one or more contract documents selected in the contract selection step, A contract management program that executes this process.

2. The aforementioned processor, A candidate proposal step in which, based on the document data received in the document reception step, one or more candidate contract documents are proposed to the user for selection from among the multiple contract documents stored in the contract storage step, Execute, The contract selection step is a step in which the user selects one or more contract documents from the one or more candidate contract documents proposed to the user in the candidate proposal step. The contract management program according to claim 1.

3. The candidate proposal step involves analyzing the document data received in the document reception step and proposing one or more candidate contract documents to the user for selection based on the file name or string contained in the document data. The contract management program according to claim 2.

4. The aforementioned processor, A candidate suggestion step in which, from among the plurality of contract documents stored in the contract storage step, one or more candidate contract documents in which the user has previously been involved in contract procedures are suggested to the user for selection, Execute, The contract selection step is a step in which the user selects one or more contract documents from the one or more candidate contract documents proposed to the user in the candidate proposal step. The contract management program according to claim 1.

5. The candidate proposal step involves presenting the user with one or more candidate contract documents in which the user has previously been involved in contract procedures, arranged in order of contract signing date, for the user to select from. The contract management program according to claim 4.

6. The aforementioned processor, A candidate proposal step which proposes to the user one or more candidate contract documents that are identified by comparing the date information contained in the document data received in the document reception step with the date information contained in the plurality of contract documents stored in the contract storage step, Execute, The contract selection step is a step in which the user selects one or more contract documents from the one or more candidate contract documents proposed to the user in the candidate proposal step. The contract management program according to claim 1.

7. In the candidate proposal step, the date information contained in the document data is the date information specified in the document data, obtained by user input or by parsing the string contained in the document data. The contract management program according to claim 6.

8. The aforementioned processor, A related step involves identifying one or more involved users who were involved in the contract procedures of the one or more contract documents stored in association with the aforementioned document-related step, A stakeholder notification step in which the one or more involved users identified in the stakeholder identification step are notified that the document data has been stored in association with the one or more contract documents in the document-related step, Execute The contract management program according to claim 1.

9. The aforementioned processor, A permission setting step in which the access rights for the document data stored in the document-related step are set based on the access rights for the one or more contract documents stored in association with it, Execute The contract management program according to claim 1.

10. The aforementioned processor, A calculation step in which, based on the document data stored in association with the one or more contract documents in the document-related step, an evaluation index value for the one or more contract documents is calculated; Execute The contract management program according to claim 1.

11. The aforementioned processor, A calculation step in which, based on the document data stored in association with the one or more contract documents in the document-related step, an evaluation index value for the contracting parties of the one or more contract documents is calculated; Execute The contract management program according to claim 1.

12. An information processing device comprising a processor and a memory unit, The processor executes the contract management program according to any one of claims 1 to 11. Information processing device.

13. A method for manufacturing an information processing system including an information processing device comprising a processor and a memory unit, The processor executes the contract management program according to any one of claims 1 to 11. A method for manufacturing information processing systems.

14. An information processing method performed by a computer comprising a processor and a memory unit, The computer executes the contract management program according to any one of claims 1 to 11. Information processing methods.

Images