Program, information processing device, information processing method

Abstract

This program reduces user input work and minimizes input errors such as typos when editing and storing document management information. [Solution] A program for causing a computer, comprising a processor and a memory unit, to execute electronic contract procedures between users belonging to different organizations, wherein the program causes the processor to execute a contract information reception step for receiving contract information that is the subject of a contract to be concluded between a first user and a second user, an input data reception step for receiving input for one or more input items of the contract information received from the first user, and further causes the processor to execute a document management information storage step for storing the received input for one or more input items in association with the contract information as document management information for managing the contract information at the second user.

Description

Technical Field

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

Background Art

[0002] With the development and spread of computer technology, documents that used to be on paper are being digitized. For example, it is conceivable to manage documents such as contract documents that require the signatures and seals of the parties as electronic data. Patent Document 1 discloses a data storage destination restriction device that can restrict data storage destinations in units of user groups within a company. Patent Document 2 discloses an information processing system related to digital contracts including a creator terminal, a confirmation company terminal, and a contract document management server.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0004] In an electronic contract system, in the management of information related to electronic contracts (contract information), for the editing and storage of document management information for managing electronic contracts, such as management numbers, contract conclusion dates, contract expiration dates, etc., the user who manages the contract information needs to manually input, which is time-consuming and there are problems such as input errors such as incorrect input. Therefore, the present disclosure has been made to solve the above problems, and its purpose is to provide a technique for reducing input errors such as incorrect input while reducing the input work by the user in the editing and storage of document management information. [Means for solving the problem]

[0005] A program for causing a computer, comprising a processor and a memory unit, to execute electronic contract procedures between users belonging to different organizations, the program causing the processor to execute: a contract acceptance step of receiving contract information that is the subject of a contract to be concluded between a first user and a second user; an input acceptance step of receiving input from the first user for one or more input items of the contract information received in the contract acceptance step; and a second storage step of storing the input for one or more input items received in the input acceptance step as document management information for managing the contract information at the second user, associated with the contract information. [Effects of the Invention]

[0006] According to this disclosure, the amount of input work performed by users can be reduced when editing and storing document management information, and input errors such as incorrect entries can be reduced. [Brief explanation of the drawing]

[0007] [Figure 1] This is a diagram showing the overall configuration of information processing 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 diagram shows the data structure of user table 1012. [Figure 6] This diagram shows the data structure of group table 1013. [Figure 7] This diagram shows the data structure of document table 1014. [Figure 8] This diagram shows the data structure of confirmation table 1015. [Figure 9]It is a diagram showing the data structure of the input item table 1016. [Figure 10] It is a diagram showing the data structure of the document management table 1017. [Figure 11] It is a flowchart showing the operation of the contract document creation process. [Figure 12] It is a flowchart showing the operation of the contract document confirmation process. [Figure 13] It is a flowchart showing the operation of the document management information storage process (first embodiment). [Figure 14] It is a flowchart showing the operation of the document management information storage process (second embodiment). [Figure 15] It is an example screen showing the operation of the contract document creation process. [Figure 16] It is an example screen showing the message notified to the second user terminal 30. [Figure 17] It is an example screen showing the operation of the contract document confirmation process. [Figure 18] It is an example screen showing the operation of the document management information storage process. [Figure 19] It is a block diagram showing the basic hardware configuration of the computer 90.

Mode for Carrying Out the Invention

[0008] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In all the drawings for explaining the embodiments, the same reference numerals are given to common components, and repeated explanations are omitted. Note that the following embodiments do not unduly limit the content of the present disclosure described in the claims. Also, not all the components shown in the embodiments are essential components of the present disclosure. Also, each figure is a schematic diagram and is not necessarily drawn precisely.

[0009] <Configuration of the information processing system 1> The information processing system 1 in the present disclosure is an information processing system for realizing an electronic contract conclusion service among a plurality of users. Specifically, it is an information processing system for realizing an electronic contract conclusion service between a first user and a second user belonging to an organization different from the first user. The information processing system 1 includes information processing devices of a server 10, a first user terminal 20, a second user terminal 30, and a third user terminal 40, which are connected via a network N. FIG. 1 is a diagram showing the overall configuration of the information processing system 1. FIG. 2 is a block diagram showing the functional configuration of the server 10. FIG. 3 is a block diagram showing the functional configuration of the first user terminal 20. FIG. 4 is a block diagram showing the functional configuration of the second user terminal 30.

[0010] Each information processing device is composed of a computer including an arithmetic device and a storage device. The basic hardware configuration of the computer and the basic functional configuration of the computer realized by the hardware configuration will be described later. For each of the server 10, the first user terminal 20, and the second user terminal 30, descriptions overlapping with the basic hardware configuration of the computer and the basic functional configuration of the computer described later are omitted.

[0011] <Configuration of the server 10> The server 10 is an information processing device that provides an electronic contract conclusion service among a plurality of users. The server 10 includes a storage unit 101 and a control unit 104.

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

[0013] 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 allows the user to use the services related to this disclosure. 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 5 shows the data structure of user table 1012.

[0014] 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. A user may belong to multiple groups.

[0015] 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 6 shows the data structure of group table 1013.

[0016] 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 be arbitrarily defined and set as users who have a certain rank or level of authority within a group such as an organization. Multiple Administrator IDs may be set for each group.

[0017] 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, Document Data, and Creator ID. Figure 7 shows the data structure of document table 1014.

[0018] 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. Document data is an item that stores contract information (binary or text data). The Creator ID is a field that stores user identification information to identify the user who created the contract information.

[0019] 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, and date and time. Figure 8 shows the data structure of confirmation table 1015.

[0020] 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 beforehand 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. 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.

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

[0022] 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 contract information to which the input item 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. The role field stores role information related to the role of the input item. Role information can be set arbitrarily for each input item in the contract information, such as contract signing date, contract start date, contract end date, whether or not automatic renewal is enabled, termination notice deadline, management number, transaction amount, first user-defined information, and second user-defined information. 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.

[0023] The document management table 1017 is a table that stores and manages document management information for each user, such as creator and reviewer, to manage contract information that has been created or reviewed. The document management information includes bibliographic information related to the contract information, which is stored in association with the contract information. The document management table 1017 stores document management information related to contract information, associating it with user identification information such as the creator and reviewer. In other words, the document management information is linked to the contract information and is used to manage contract information independently for each user. In this disclosure, the document management information is stored in association with user identification information, but it may also be stored in association with the user's email address instead of user identification information. The document management table 1017 is a table that has columns for document ID, user ID, management number, contract signing date, contract start date, contract end date, automatic renewal status, termination notice deadline, transaction amount, first user-defined information, and second user-defined information. Figure 10 shows the data structure of the document management table 1017.

[0024] The document ID is an item that stores the document identification information of the contract information being managed. The User ID is an item that stores the user identification information of the user who manages the contract information. The management number is an item that stores a number used for managing contract information, such as a user's reference number. Users can manage contract information by setting different management numbers for each user for a single contract. The contract signing date is an item that stores information related to the contract signing date in the contract information. The contract start date is an item that stores information about the contract start date in the contract information. The contract end date is an item that stores information about the contract end date in the contract information. The "Automatic Renewal" field stores information regarding whether or not the contract information is automatically renewed. The cancellation notice deadline is an item that stores information regarding the cancellation notice deadline in the contract information. For example, the control unit 104 of server 10 periodically compares the cancellation notice deadline item in the document management table 1017 with the current date and time. If the current date and time have passed the cancellation notice deadline, it sends an email to the email address of the user identified by the user ID notifying them that the cancellation notice deadline for the contract information has arrived. The control unit 104 of server 10 may also be configured to notify the user that the cancellation notice deadline has arrived by means of a message, SMS, or voice call instead of email. The transaction amount is an item that stores information about the transaction amount in the contract information. The first user-defined information is an item that stores information about the first user-defined information for the user. The second user-defined information is an item that stores information about the second user-defined information for the user. Users can manage contract information by setting user-defined information that has arbitrary roles for that information. In this disclosure, there are two types of user-defined information: first user-defined information and second user-defined information. However, any number of user-defined information can be set for each piece of contract information.

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

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

[0027] <Configuration of the first user terminal 20> The first user terminal 20 is an information processing device operated by the first user who uses 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.

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

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

[0030] 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. The application program 2012 includes an interpreted programming language such as JavaScript® that is executed on a web browser application stored in the first user terminal 20.

[0031] <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 the first user ID 2011 stored in the storage unit 201.

[0032] <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 keyboard 2065.

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

[0034] <Configuration of the second user terminal 30> The second user terminal 30 is an information processing device operated by a second user utilizing 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.

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

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

[0037] 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. The application program 3012 includes an interpreted programming language such as JavaScript (registered trademark) that is executed on a web browser application stored in the second user terminal 30.

[0038] <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 the second user ID 3011 stored in the storage unit 301.

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

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

[0041] <Operation of Information Processing System 1> The following describes each process of Information Processing System 1. Figure 11 is a flowchart showing the operation of the contract creation process. Figure 12 is a flowchart showing the operation of the contract verification process. Figure 13 is a flowchart showing the operation of the document management information storage process (first embodiment). Figure 14 is a flowchart showing the operation of the document management information storage process (second embodiment). Figure 15 shows an example screen illustrating the operation of the contract creation process. Figure 16 shows an example screen displaying a message notified to the second user terminal 30. Figure 17 shows an example screen illustrating the operation of the contract verification process. Figure 18 shows an example screen illustrating the operation of the document management information storage process.

[0042] <Contract creation process> The contract creation process involves the creator creating contract information and sending it to the verifier. In this disclosure, the first user is the user who creates the contract information, and the second user is the user who verifies the contract information. It is possible to set multiple users as verifiers when creating contract information.

[0043] Figure 15 shows an example screen illustrating the operation of the contract creation process. The screen 50 displayed on the display 2081 of the first user terminal 20, which is used to create contract information, displays 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.

[0044] <Overview of the contract creation process> The contract creation process is a series of steps in which the creator creates the contract information, sets the recipients of the contract information, sets the input fields for the contract information, sets the input rules for the input fields, receives the input data for the input fields from the creator, and sends the contract information to the set recipients.

[0045] <Details of the contract creation process> In step S101, 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.

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

[0047] In step S102, the first user operates the input device 206 of the first user terminal 20 to select and set the user who will be the verifier of the contract information. In this disclosure, the first user selects and sets the second user as the verifier. 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. At this time, the value 1 is stored in the "Confirmation Order" field of the confirmation table 1015. In step S102, 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 described later. Note that setting the circulation order is not mandatory.

[0048] In step S103, the first user operates the input device 206 of the first user terminal 20 to set input items for contract information. For each of the one or more input items of contract information, the first user associates it with one or more items of document management information for managing 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 S101. 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.

[0049] The first user operates the input device 206 on the first user terminal 20 to set a role for the added input item information. Specifically, the first user operates the input device 206 on the first user terminal 20 to select one of the following as the role for the input item information: management number, contract signing date, contract start date, contract end date, automatic renewal status, termination notice deadline, transaction amount, first user-defined information, or second user-defined information, and sends it to the server 10. The server 10 stores the received role in the role field of the newly created record in the input item table 1016. As a result, the newly created input field information is associated with each item of the document management information in the document management table 1017 (management number, contract signing date, contract start date, contract end date, automatic renewal status, termination notice deadline, transaction amount, first user-defined information, second user-defined information).

[0050] In step S104, the contract creation unit 1042 of the server 10 sets input rules for one or more input fields of contract information based on the item attributes of one or more fields of document management information for managing contract information. Specifically, the contract creation unit 1042 of server 10 retrieves the input item ID and role included in the multiple input item information set in step S103. Based on the retrieved role, the contract creation unit 1042 of server 10 retrieves the item attributes set for each item in the document management table 1017. Note that each item of the document management information (management number, contract signing date, contract start date, contract end date, automatic renewal status, termination notice deadline, transaction amount, first user-defined information, second user-defined information) has item attributes such as data type (date, text, integer, etc.) and, if it is a string, string length set in advance. The contract creation unit 1042 of server 10 retrieves the item attributes for each role associated with the input item ID and stores them in the input rule field of the record identified by the input item ID in the input item table 1016. In other words, the contract creation unit 1042 of server 10 sets the input rules for each input item in the input item table 1016 based on the item attributes set for each item in the document management table 1017. This allows the first user to automatically set the input rules for each input item.

[0051] Furthermore, the system may be configured so that the first user can manually set input rules for each additional input item. The first user operates the input device 206 of the first user terminal 20 to specify the input rules for each input item information set in step S103 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 the input rules for each input item to be set manually.

[0052] In step S105, 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 S104 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 in the group to which they belong, into the input item where a management number is set as a role. 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 as a role. 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.

[0053] In step S106, the contract creation unit 1042 of the server 10 receives an instruction from the first user to request the second user to conclude a contract 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. When the contract creation unit 1042 of the server 10 receives the request, it sends a message to the second user notifying them that the first user has sent a request to confirm contract information. For example, the contract creation unit 1042 of the server 10 sends a message to the second user's email address notifying them that the first user has sent a request to confirm contract information 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.

[0054] Figure 16 shows an example screen displaying 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.

[0055] <Variation> If the first user selects and sets multiple verifiers in step S102, 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 third user, as verifiers, the role may set the input fields for the contract start date and contract end date for the second user, and the role may set the input field for the contract signing date for the third user. In this case, in the contract confirmation process described later, 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 third 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 the same input field information.

[0056] 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".

[0057] <Contract Verification Process> The contract verification process is the process by which a verifier confirms the contents of the contract information received from the creator.

[0058] <Overview of contract verification process> The contract verification process is a series of operations that involves receiving access from the verifier, presenting the verifier with a screen displaying the contract information, receiving input data from the verifier for the input fields, and receiving data from the verifier regarding the verification of the contract information.

[0059] <Details of contract verification process> In step S301, the second user can open the web page specified by the URL by operating the input device 306 or the like of the second user terminal 30 and selecting the URL contained in the received message, thereby opening the web page 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 confirmation process. 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.

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

[0061] The contract verification unit 1043 of server 10 generates a screen for verifying the contract information based on the acquired contract information, verifier information, and input item information, and sends it to the second user terminal 30.

[0062] In step S303, the display 3081 of the second user terminal 30 displays a screen for confirming the contract information received from the server 10. The second user confirms the contract information displayed on the display 3081 of the second user terminal 30.

[0063] Figure 17 shows an example screen illustrating the operation of the contract confirmation process. The screen 70 displayed on the display 3081 of the second user terminal 30, which is used to confirm contract information, displays the status 710 indicating the current status of contract information creation, the contract information display area 730, document data 731, input items 732, 733, 734, 735, 736, and an agreement button 740.

[0064] In step S304, 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.

[0065] In step S305, the contract confirmation unit 1043 of the server 10 receives an instruction from the second user to agree to conclude the contract as requested by 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 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 S304. 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 S304, the input data entered by the second user is stored as input item information in input item table 1016.

[0066] The contract verification unit 1043 of server 10 sends a message to the first user notifying them that the contract verification process is complete once all verifiers have completed the contract verification process. For example, the contract creation unit 1042 of server 10 sends a message to the first user's email address via email or other means notifying them that the second user has completed the verification of the contract information. The message sent to the first user includes information about a URL containing a document ID to identify the contract information. 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 performed the contract verification process, notifying them that the contract verification process is complete. This allows all verifiers to receive notification that the contract verification process has been completed by all verifiers. Furthermore, the contract verification unit 1043 of 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 has been completed. This allows the administrator in the group to which the verifiers belong to be notified that the contract verification process has been completed. The contract verification unit 1043 of server 10 retrieves the group ID item by searching the user ID or email address item in the user table 1012 based on the user ID or email address. Based on the retrieved group ID item, the contract verification unit 1043 of server 10 retrieves the group ID item in the group table 1013, retrieves the administrator ID item, identifies a user with administrator-level privileges by searching the user ID in the user table 1012 based on the administrator ID, and sends a message notifying them that the contract verification process has been completed.

[0067] <Document Management Information Storage Processing (First Embodiment)> The document management information storage process (first embodiment) is a process in which the creator stores the input data entered in the input item information into the document management information.

[0068] <Overview of Document Management Information Storage Processing (First Embodiment)> The document management information storage process (first embodiment) is a series of processes that accepts access from the creator, presents the creator with a screen for storing document management information, allows the creator to select from multiple input items to be stored in the document management information, and stores the selected input items in the document management information.

[0069] <Details of Document Management Information Storage Processing (First Embodiment)> In step S501, the second user operates the input device 306 of the second user terminal 30 to open a page via a browser application or the like that allows the server 10 to execute document management information storage processing. The second user may open a page that allows the server 10 to execute document management information storage processing by operating the input device 306 of the second user terminal 30 and entering a predetermined URL into a browser application. The second user may, during the contract verification process, open a page that allows the server 10 to execute the document management information storage process by selecting the URL contained in the message notified from the contract verification unit 1043 of the server 10. The second user may open the page by moving to the page provided by server 10 for executing the document management information storage process after confirming the contract information in step S305 of the contract confirmation process. In this case, if there are multiple users who are the confirmers, the configuration may be such that only the user who last performed the contract confirmation process opens the page provided by server 10 for executing the document management information storage process after the completion of the contract confirmation process.

[0070] In step S502, the first user inputs the document ID of the contract information to be processed by the document management information storage process (first embodiment) by operating the input device 206 of the first user terminal 20 and sends a request to the server 10. The document storage unit 1044 of the server 10 identifies the contract information and the first user based on the received document ID and the first user ID 2011 included in the request. Furthermore, the document storage unit 1044 of server 10 may identify the document ID and the first user based on the information contained in the URL entered or selected by the first user.

[0071] The document storage unit 1044 of server 10 searches the input item table 1016 for the document ID based on the identified document ID and retrieves input item information including the input item ID, input data, and role fields. Alternatively, the document storage unit 1044 of server 10 may also search the document table 1014 for the document ID based on the identified document ID and retrieve fields such as document data. The document storage unit 1044 of server 10 generates a screen for storing document management information based on the acquired input item ID, input data, and role, and sends it to the first user terminal 20.

[0072] In step S503, the display 3081 of the second user terminal 30 displays a screen for storing document management information received from the server 10.

[0073] In step S504, the document storage unit 1044 of the server 10 receives instructions from the second user regarding whether or not to store the inputs for multiple input items as document management information for managing contract information for the second user, in association with the contract information. The document storage unit 1044 of the server 10 may also receive instructions regarding whether or not to store the inputs for one or more input items included in the multiple input items as multiple items of document management information for managing contract information for the second user, in association with the contract information. Specifically, the second user operates the input device 306 of the second user terminal 30 to select the input items to be stored and reflected in the document management information from among the multiple input item information displayed in the list. If the multiple input item information displayed in the list contains input data that is inappropriate to store as the second user's document management information, the second user can choose not to store it as document management information, and can selectively not store some input data as document management information. The second user operates the input device 306 of the second user terminal 30, and once they have finished selecting the input item information to be stored and reflected in the document management information, they send a request to the server 10 that includes the document ID of the contract information and the input item IDs included in the input item information to be stored.

[0074] In step S505, the document storage unit 1044 of the server 10 stores the inputs for multiple input items received from the user as document management information for managing contract information for the second user, associating them with the contract information. The document storage unit 1044 of the server 10 stores the inputs for multiple input items received from the user in one or more items of the document management information for the second user associated with each input item. In response to instructions received from the user, the document storage unit 1044 of the server 10 stores the inputs for multiple input items received as document management information for managing contract information for the second user, associating them with the contract information. Specifically, the document storage unit 1044 of the server 10 searches for the input item ID in the input item table 1016 based on the input item ID received from the second user terminal 30, and retrieves multiple input data and role items. The document storage unit 1044 of server 10 determines, based on the role information, which of the document management information items (management number, contract signing date, contract start date, contract end date, automatic renewal status, termination notice deadline, transaction amount, first user-defined information, second user-defined information) the input data should be stored in. Specifically, the document storage unit 1044 of server 10 determines that the input data set in the management number, contract signing date, contract start date, contract end date, automatic renewal status, termination notice deadline, transaction amount, first user-defined information, and second user-defined information fields of the document management information should be stored in the management number, contract signing date, contract start date, contract end date, automatic renewal status, termination notice deadline, transaction amount, first user-defined information, and second user-defined information fields, respectively, for each role information. The document storage unit 1044 of server 10 stores the received document ID and the second user ID 3011 included in the request in the document ID and user ID fields of the new record in the document management table 1017, respectively. The document storage unit 1044 of server 10 stores the multiple input data and roles acquired in the respective fields of document management information in the record created in the document management table 1017, which are identified based on the role information.

[0075] Figure 18 shows an example screen illustrating the operation of the document management information storage process. The screen 80 for storing document management information, displayed on the display 3081 of the second user terminal 30, shows an apply button 811, an ignore button 812, and a close button 840. The second user operates the input device 306 of the second user terminal 30 and presses the apply button 811 to store the input data included in the corresponding input item information in each item of the document management information, which is identified based on the role information of the document management table 1017. For example, a second user can operate the input device 306 of the second user terminal 30 and press the apply button 811 located to the right of the contract start date to store the input data "2021 / 04 / 01" in the contract start date field of the document management table 1017. On the other hand, the second user can operate the input device 306 of the second user terminal 30 and press the ignore button 812 to skip the input data included in the corresponding input item information without storing it. Once the second user has finished pressing the Apply button 811 for all the input information they want to store in the document management table 1017, they can close screen 80 by pressing the Close button 840.

[0076] <Example 1> The second user can pre-store and configure settings for multiple input fields, such as "automatic reflection," "selective reflection," and "do not reflect," regarding the execution of document management information storage processing for each field. Furthermore, the second user may store and set configuration information for each item of the document management information (management number, contract signing date, contract start date, contract end date, automatic renewal status, termination notice deadline, transaction amount, first user-defined information, second user-defined information). In this case, the configuration information for multiple input item information may be stored and set by referring to the configuration information set for each item of the document management information based on the role information associated with each input item information. This allows a second user to automatically store specific input data from the one or more input data entered in the input fields as their own document management information.

[0077] The document storage unit 1044 of the server 10, according to the setting information set for the multiple input items it receives, receives instructions from the second user for input items where the setting information is the first setting, and stores the received instructions as document management information for managing contract information for the second user, associated with the contract information. For input items where the setting information is the second setting, it stores the information as document management information for managing contract information for the second user, associated with the contract information, without executing the instruction reception step.

[0078] Specifically, in S503, the screen for storing document management information displays input items that have been stored and set to "Select and Apply" as their setting information, out of the multiple input items received from server 10, while input items that have been stored and set to "Automatically Apply" or "Do not apply" as their setting information are not displayed on the screen. In step S504, the second user operates the input device 306 of the second user terminal 30 and selects the input item information to be stored and reflected in the document management information from the input item information that is stored and set as "Select and Reflect" in the list of displayed setting information. In step S505, the document storage unit 1044 of the server 10 stores, among the multiple input item information, the input item information that the second user has stored and set as "automatic reflection" as setting information, as document management information for managing the contract information of the second user, associated with the contract information. Specifically, for multiple input data and roles, it stores them in the respective fields of document management information identified based on the role information of the record created in the document management table 1017. The document storage unit 1044 of server 10 stores, among the multiple input item information, the input item information that the second user has stored and set as configuration information, in step S504 as document management information for managing contract information for the second user, associating it with the contract information. Specifically, for each of the selected input data and role, it stores them in the respective fields of document management information identified based on the role information in the record created in the document management table 1017. The document storage unit 1044 of server 10 does not store, as document management information for managing contract information for the second user, any input item information that the second user has stored and set to "do not reflect" as setting information.

[0079] <Modification 2> The system may receive instructions from an administrator associated with the second user regarding whether or not to store the inputs received from the user for multiple input fields as document management information for managing the contract information of the second user, in association with the contract information. The system may also be configured to store the inputs received from the user for multiple input fields as document management information for managing the contract information of the second user, in association with the contract information, in response to the instructions received from the administrator. In other words, the system may be configured so that a user other than the second user, such as an administrator, executes the document management information storage process (first embodiment).

[0080] <Variation 3> In the document management information storage process (first embodiment), the document storage unit 1044 of the server 10 may be configured to store inputs for multiple input items as document management information for managing contract information in the group to which the second user belongs. In this case, the document management table 1017 is configured to store and manage document management information associated with each group based on group identification information such as a group ID instead of a user ID. In this case, if there are multiple reviewers, the configuration may be such that only the user who performed the contract review process last can execute the document management information storage process (first embodiment). In other words, the configuration may be such that the information is stored and managed in the document management information only after all input data for the input fields has been entered and the contract review process has been performed by multiple reviewers. This prevents inaccurate data from being stored in the document management information by multiple reviewers.

[0081] <Document Management Information Storage Processing (Second Embodiment)> The document management information storage process (second embodiment) is a process in which the verifier stores the input data entered in the input item information into the document management information.

[0082] <Overview of Document Management Information Storage Processing (Second Embodiment)> The document management information storage process (second embodiment) is a series of processes that accepts access from a verifier, presents the verifier with a screen for storing document management information, allows the verifier to select from multiple input items to be stored in the document management information, and stores the selected input items in the document management information.

[0083] <Details of Document Management Information Storage Processing (Second Embodiment)> The document management information storage process (second embodiment) is the same as the document management information storage process (first embodiment), except that the user identified in step S502 of the document management information storage process (first embodiment) is the user who created the document, not the user who confirmed it. In each step, the process that overlaps with the document management information storage process (first embodiment) will be omitted from the explanation. Steps S701 to S703 are the same as steps S501 to S502 of the document management information storage process (first embodiment), so the explanation will be omitted.

[0084] In step S704, the document storage unit 1044 of the server 10 receives instructions from the first user regarding whether or not to store the inputs for multiple input items in association with contract information as document management information for managing contract information for the first user. The document storage unit 1044 of the server 10 may also receive instructions regarding whether or not to store the inputs for one or more input items included in the multiple input items in association with contract information as multiple items of document management information for managing contract information for the first user.

[0085] In step S705, the document storage unit 1044 of the server 10 stores the inputs for multiple input items received from the user as document management information for managing contract information for the first user, associating them with the contract information. The document storage unit 1044 of the server 10 stores the inputs for multiple input items received from the user in one or more items of the document management information for the first user associated with each input item. In response to instructions received from the user, the document storage unit 1044 of the server 10 stores the inputs for multiple input items received as document management information for managing contract information for the first user, associating them with the contract information.

[0086] <Document Management Information Storage Processing (Third Embodiment)> The document management information storage process (third embodiment) is a process in which a user with administrator-level authority in the group to which the first user and the second user belong stores the input data entered in the input item information into the document management information.

[0087] <Overview of Document Management Information Storage Processing (Third Embodiment)> The document management information storage process (third embodiment) is a series of processes that accepts access from an administrator, presents the administrator with a screen for storing document management information, allows the administrator to select from multiple input items to be stored in the document management information, and stores the selected input items in the document management information.

[0088] <Details of Document Management Information Storage Processing (Third Embodiment)> The document management information storage process (third embodiment) is the same as the document management information storage process (first embodiment) and the document management information storage process (second embodiment), except that the users identified in step S502 of the document management information storage process (first embodiment) and step S702 of the document management information storage process (second embodiment) are users of the administrator, rather than users of the creator and verifier, respectively. In each step, the explanation of processes that overlap with the document management information storage process (first embodiment) and the document management information storage process (second embodiment) will be omitted. In the document management information storage process (third embodiment), the document storage unit 1044 of the server 10 may be configured to store inputs for multiple input items as document management information for managing contract information for the second user or the first user, as stored by the administrator. In the document management information storage process (third embodiment), the document storage unit 1044 of the server 10 may be configured to store inputs for multiple input items as document management information for managing contract information in the group to which the second user or the first user belongs, by the administrator of the group to which the second user or the first user belongs. In this case, the document management table 1017 is configured to store and manage document management information for each group based on group identification information such as a group ID instead of a user ID. In this case, a user associated with a predetermined group ID in the user table 1012 may be configured to refer to or view the document management information in the document management table 1017 that is associated with that group ID.

[0089] <Regarding document management and information storage processing> The document management information storage process (first embodiment), document management information storage process (second embodiment), and document management information storage process (third embodiment) can be configured to be executed only after all reviewers have completed the contract review process, and not before. This allows the input data after all reviewers have completed the contract review process to be stored as document management information. The document management information storage process (first embodiment) may be configured to be executed after the first user completes the contract creation process (after the contract information is sent to the verifier). This allows the first user to manage the created contract information by referring to the document management information even before the verifier completes the contract verification process. The document management information storage process (second embodiment) may be configured to run after the second user has completed the contract verification process but before other verifiers have completed theirs. This allows verifiers to manage contract information they have verified by referring to the document management information even before all verifiers have completed their contract verification processes. Furthermore, the document management information storage process (first embodiment), the document management information storage process (second embodiment), and the document management information storage process (third embodiment) may be configured to be executed after the completion of the contract verification process by at least one verifier. This allows the user to refer to and manage the document management information even before the contract verification process by all verifiers is completed.

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

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

[0092] 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).

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

[0094] 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 built on the internet, LANs, wireless base stations, etc. 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.

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

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

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

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

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

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

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

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

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

[0104] (Note 1) A program comprising a processor and a memory unit, for causing a computer to execute electronic contract procedures between users belonging to different organizations, the program causing the processor to execute: a contract acceptance step (S101) for receiving contract information that is the subject of a contract to be concluded between a first user and a second user; an input acceptance step (S105) for receiving input from the first user for one or more input items of the contract information received in the contract acceptance step; and a second storage step (S505) for storing the input for one or more input items received in the input acceptance step in association with the contract information as document management information for managing the contract information at the second user. This allows the second user to reduce the amount of input work involved in editing and remembering their own document management information, while also reducing input errors such as typos.

[0105] (Note 2) The document management information for managing contract information is linked to the contract information and is information that allows the first user and the second user to manage the contract information independently, as described in Appendix 1. This allows the second user to reduce the amount of input work involved in editing and remembering their own document management information, while also reducing input errors such as typos.

[0106] (Note 3) The program is as described in either Appendix 1 or 2, wherein the program causes the processor to perform an association step (S103) which associates each of the one or more input items of contract information in the input reception step with one or more items of document management information for managing contract information, and the second storage step is a step (S505) which stores the inputs for the one or more input items received in the input reception step in one or more items of document management information for the second user associated with each input item. This allows the second user to reduce the amount of input work involved in editing and remembering their own document management information, while also reducing input errors such as typos.

[0107] (Note 4) The program is the program described in Appendix 3, which causes the processor to perform a setting step (S104) in which it sets input rules for one or more input fields of contract information based on the field attributes of one or more fields of document management information for managing the associated contract information in the relevant step. This allows input rules to be set for input fields based on document management information, thereby reducing input errors such as incorrect entries by the first and second users.

[0108] (Note 5) The program, as described in any of Appendix 1 to 4, includes a second storage step, which includes an instruction receiving step (S504) in which the second user instructs whether or not to store the input for one or more input items received in the input receiving step as document management information for managing contract information for the second user, associated with the contract information; and a step (S505) in which, in response to the instruction received in the instruction receiving step, the program stores the input for one or more input items received in the input receiving step as document management information for managing contract information for the second user, associated with the contract information. This allows a second user to choose whether or not to store the input data entered in the input fields as their own document management information. For example, if the input data contains data that is inappropriate to include in their own document management information, they can choose not to store it as such.

[0109] (Note 6) The instruction receiving step is a step (S504) in which the program receives an instruction on whether or not to store the inputs for one or more input items contained in one or more input items as one or more items of document management information for managing contract information for a second user, associated with the contract information, as described in Appendix 5. This allows a second user to store specific input data from one or more input data entries in an input field as their own document management information. For example, if some of the input data is inappropriate to include in their document management information, they can choose to specify only some of the input data and not store it in their document management information.

[0110] (Note 7) The program described in Appendix 6 includes, the second storage step, depending on the setting information set for one or more input items received in the input reception step, an instruction reception step to receive instructions from the second user for input items where the setting information is the first setting, and a step (S505) to store the received instructions in association with the contract information as document management information for managing the contract information for the second user, and a step (S505) to store the input items where the setting information is the second setting, in association with the contract information as document management information for managing the contract information for the second user, without executing the instruction reception step. This allows a second user to automatically store specific input data from the one or more input data entered in the input fields as their own document management information.

[0111] (Note 8) The program causes the processor to execute a request step (S106) in which it receives instructions from the first user to request the second user to conclude a contract regarding contract information, and an agreement step (S305) in which it receives instructions from the second user to agree to conclude the contract as requested by the first user in the request step, and the second storage step is a program described in any of the appendices 1 to 7 that is executed after the agreement step. This allows the second user to avoid storing input data in the document management information before an electronic contract has been concluded. It also prevents the storage of unconfirmed information prior to contract conclusion as document management information.

[0112] (Note 9) The program is one of the programs described in any of Appendix 1 to 8, which causes the processor to perform a first storage step (S705) in which it stores the inputs for one or more input items received in the input acceptance step in association with contract information as document management information for managing contract information for the first user. This allows the first user to reduce the amount of input work involved in editing and remembering their document management information, while also reducing input errors such as typos.

[0113] (Note 10) The program is one of the programs described in any of Appendix 1 to 9, which causes the processor to execute a second input acceptance step (S304) which accepts input from a second user for one or more input items of contract information accepted in the contract acceptance step, and a first storage step (S705) which stores the input for one or more input items accepted in the second input acceptance step in association with the contract information as document management information for managing the contract information of the first user. This allows the first user to reduce the amount of input work involved in editing and remembering their document management information, while also reducing input errors such as typos.

[0114] (Note 11) The first storage step is a program as described in Appendix 9 or 10 that causes a first user to perform a second instruction receiving step (S704) in which the program receives an instruction from the first user as to whether or not to store the input for one or more input items received in the second input receiving step as document management information for managing contract information for the first user, in association with contract information, and a step (S705) in which the program, in accordance with the instruction received in the second instruction receiving step, stores the input for one or more input items received in the second input receiving step as document management information for managing contract information for the first user, in association with contract information. This allows the first user to choose whether or not to store the input data entered in the input fields as their own document management information. For example, if the input data contains data that is inappropriate to include as their own document management information, they can choose not to store it as such.

[0115] (Note 12) The second storage step is a program as described in any of Appendix 1 to 11, which includes an administrator instruction receiving step that receives instructions from an administrator associated with a second user regarding whether or not to store the inputs for one or more input items received in the input reception step as document management information for managing contract information for the second user, associated with the contract information; and a step in the administrator instruction receiving step that, in response to the instructions received, stores the inputs for one or more input items received in the input reception step as document management information for managing contract information for the second user, associated with the contract information. This allows the first user to store specific input data from one or more input data entries in the input fields as their own document management information. For example, if some of the input data is inappropriate to include in their document management information, they can choose to specify only some of the input data and not store it in their document management information.

[0116] (Note 13) An information processing device comprising a processor and a memory unit for executing electronic contract procedures between users belonging to different organizations, wherein the information processing device causes the processor to execute a contract acceptance step (S101) for receiving contract information that is the subject of a contract to be concluded between a first user and a second user; an input acceptance step (S105) for receiving input from the first user for one or more input items of the contract information received in the contract acceptance step; and a second storage step (S505) for storing the input for one or more input items received in the input acceptance step in association with the contract information as document management information for managing the contract information at the second user. This allows the second user to reduce the amount of input work involved in editing and remembering their own document management information, while also reducing input errors such as typos.

[0117] (Note 14) An information processing method comprising a processor and a memory unit, for causing a computer to execute electronic contract procedures between users belonging to different organizations, wherein the processor is caused to execute: a contract acceptance step (S101) for receiving contract information that is the subject of a contract to be concluded between a first user and a second user; an input acceptance step (S105) for receiving input from the first user for one or more input items of the contract information received in the contract acceptance step; and a second storage step (S505) for storing the input for one or more input items received in the input acceptance step in association with the contract information as document management information for managing the contract information at the second user. This allows the second user to reduce the amount of input work involved in editing and remembering their own document management information, while also reducing input errors such as typos. [Explanation of symbols]

[0118] 1 Information processing 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 program comprising a processor and a memory unit, which causes a computer to execute electronic contract procedures between users belonging to different organizations, The program is provided to the processor: A contract acceptance step in which contract information subject to contract conclusion between the first user and the second user is received, An input reception step that receives input from the first user for one or more input fields of the contract information received in the contract reception step, A second storage step involves storing the inputs for the one or more input items received in the input acceptance step in association with the contract information as document management information for managing the contract information for the second user, A program that executes the command.

2. The document management information for managing the aforementioned contract information is associated with the aforementioned contract information and is information that allows the first user and the second user to manage the aforementioned contract information independently. The program according to claim 1.

3. The program is provided to the processor: A related step involves associating each of the one or more input fields of the contract information in the input acceptance step with one or more fields of document management information for managing the contract information, Make it run, The second storage step is to store the inputs for the one or more input items received in the input reception step in the one or more items of the document management information of the second user associated with each input item. The program according to any one of claims 1 to 2.

4. The program is provided to the processor: A setting step in which, based on the item attributes of one or more items of document management information for managing the associated contract information, input rules are set for each of the one or more input items of the contract information, The program according to claim 3 that causes to execute.

5. The second memory step is, An instruction receiving step in which the second user gives an instruction on whether or not to store the input for the one or more input items received in the input receiving step in association with the contract information as document management information for managing the contract information at the second user, In the instruction reception step, in response to the received instruction, the inputs for the one or more input items received in the input reception step are stored in association with the contract information as document management information for the second user to manage the contract information; A program according to any one of claims 1 to 4, including the program described in any one of claims 1 to 4.

6. The instruction receiving step is a step of receiving an instruction on whether or not to store the inputs for one or more input items included in the one or more input items as one or more items of document management information for managing the contract information by the second user, in association with the contract information. The program according to claim 5.

7. The second storage step is, In the input reception step, according to the setting information set for the one or more input items received, For input items that are first settings, the setting information includes an instruction receiving step that receives instructions from the second user, and, in accordance with the received instructions, a step that stores the information in association with the contract information as document management information for managing the contract information for the second user. With respect to the input items that are second settings, the setting information is stored in association with the contract information as document management information for managing the contract information by the second user, without executing the instruction reception step. including, The program according to claim 6.

8. The program is provided to the processor: A request step in which the first user instructs the second user to conclude a contract regarding contract information, The consent step involves receiving instructions from the second user to agree to the conclusion of the contract requested by the first user in the aforementioned request step, Make it run, The second storage step is performed after the agreement step. A program according to any one of claims 1 to 7.

9. The program is provided to the processor: A first storage step involves storing the inputs for the one or more input items received in the input acceptance step in association with the contract information as document management information for managing the contract information for the first user, To execute A program according to any one of claims 1 to 8.

10. The program is provided to the processor: A second input reception step that receives input from a second user for one or more input fields of the contract information received in the contract reception step, Make it run, The system executes a first storage step in which the inputs for the one or more input items received in the second input reception step are stored in association with the contract information as document management information for the first user to manage the contract information. The program according to any one of claims 1 to 9.

11. The first memory step is, A second instruction receiving step receives instructions from the first user regarding whether or not to store the input for the one or more input items received in the second input receiving step as document management information for managing the contract information for the first user, in association with the contract information. In the second instruction reception step, in response to the received instruction, the inputs for the one or more input items received in the second input reception step are stored in association with the contract information as document management information for managing the contract information for the first user. A program according to claim 9 or 10 that causes to execute.

12. The second memory step is, An administrator instruction receiving step that receives instructions from the administrator associated with the second user regarding whether or not to store the input for the one or more input items received in the input receiving step as document management information for managing the contract information for the second user, in association with the contract information; In the administrator instruction reception step, in response to the received instruction, the inputs for the one or more input items received in the input reception step are stored in association with the contract information as document management information for the second user to manage the contract information; A program according to any one of claims 1 to 11, including the program described in any one of claims 1 to 11.

13. An information processing device comprising a processor and a memory unit, for executing electronic contract procedures between users belonging to different organizations, The aforementioned processor, A contract acceptance step in which contract information subject to contract conclusion between the first user and the second user is received, An input reception step that receives input from the first user for one or more input fields of the contract information received in the contract reception step, A second storage step involves storing the inputs for the one or more input items received in the input acceptance step in association with the contract information as document management information for managing the contract information for the second user, An information processing device that executes an action.

14. An information processing method comprising a processor and a memory unit, for causing a computer to execute electronic contract procedures between users belonging to different organizations, The aforementioned processor, A contract acceptance step in which contract information subject to contract conclusion between the first user and the second user is received, An input reception step that receives input from the first user for one or more input fields of the contract information received in the contract reception step, A second storage step involves storing the inputs for the one or more input items received in the input acceptance step in association with the contract information as document management information for managing the contract information for the second user, An information processing method that enables execution of [the specified action].

Images