JP2024057139A - Electronic contract program, information processing apparatus, method of producing information processing system, and information processing method - Google Patents

Abstract

To provide an electronic contract program which allows a user of an electronic contract service to browse an electronic contract comfortably in a display mode according to an information processing terminal in use, an information processing apparatus, a method for producing an information processing system, and an information processing method.SOLUTION: An electronic contract program causes a computer equipped with a processor and a storage unit to execute electronic contract procedures between different organizations. The processor executes: a contract receiving step of receiving, from a first user, a contract document related to a contract in a page layout; a contract storage step of storing the contract document received in the contract receiving step; a contract presentation step of presenting the contract document stored in the contract storage step to a second user in a second layout which is different from the layout; and a contract approval step of receiving, from the second user, an approval operation for the contract document presented in the contract presentation step.SELECTED DRAWING: Figure 12

Description

This disclosure relates to an electronic contract program, an information processing device, an information processing system, and an information processing method.

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

JP 2017-10096 A

In electronic contract procedures between multiple users, it is common for the contracting parties to review and conclude contract documents laid out in A4 or other page units. In recent years, there has been an issue that the screens of portable information processing terminals such as smartphones, which have become widely used, are small and users of electronic contract services are unable to comfortably view electronic contracts.
Therefore, the present disclosure has been made to solve the above-mentioned problems, and its purpose is to provide technology that allows users of electronic contract services to comfortably view electronic contracts in a display format that suits the information processing terminal they are using.

An electronic contract program for causing a computer having a processor and a storage unit to execute electronic contract procedures between different organizations, in which the processor executes a contract acceptance step for accepting from a first user a contract document relating to a contract laid out on a page-by-page basis, a contract storage step for storing the contract document accepted in the contract acceptance step, a contract presentation step for presenting to a second user the contract document stored in the contract storage step in a second layout different from the first layout, and a contract approval step for accepting from the second user an approval operation for the contract document presented in the contract presentation step.

According to the present disclosure, users of electronic contract services can comfortably view electronic contracts in a display format that suits the information processing terminal they are using.

FIG. 2 is a block diagram showing the functional configuration of the system 1. FIG. 2 is a block diagram showing the functional configuration of the server 10. FIG. 2 is a block diagram showing a functional configuration of a first user terminal 20. FIG. 2 is a block diagram showing a functional configuration of a second user terminal 30. FIG. 13 is a diagram showing the data structure of a user table 1012. FIG. 11 is a diagram showing the data structure of a group table 1013. FIG. 10 is a diagram showing the data structure of a document table 1014. FIG. 11 is a diagram showing the data structure of a confirmation table 1015. FIG. 10 is a diagram showing the data structure of an input item table 1016. FIG. 13 is a diagram showing the data structure of a contract group table 1017. 13 is a flowchart showing the operation of a contract creation process. 13 is a flowchart showing the operation of a contract confirmation process. 13 is a screen example showing the operation of a contract creation process. 13 is a screen example showing a confirmation request message notified to the second user terminal 30. 13 is a first screen example showing the operation of the contract confirmation process. 13 is a second screen example showing the operation of the contract confirmation process. 13 is a third example of a screen showing the operation of the contract confirmation process. 13 is a fourth example of a screen showing the operation of the contract confirmation process. 13 is an example of a screen showing a signing completion message notified to the first user terminal 20. FIG. 2 is a block diagram showing the basic hardware configuration of a computer 90.

Embodiments of the present disclosure will be described below with reference to the drawings. In all figures describing the embodiments, common components are given the same reference numerals, and repeated explanations will be omitted. Note that the following embodiments do not unduly limit the contents of the present disclosure described in the claims. Furthermore, not all components shown in the embodiments are necessarily essential components of the present disclosure. Furthermore, each figure is a schematic diagram, and is not necessarily a precise illustration.

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

Each information processing device is configured by a computer equipped with an arithmetic unit 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, explanations that overlap with the basic hardware configuration and basic functional configuration of the computer described later will be omitted.

<Configuration of Server 10>
The server 10 is an information processing device that provides an electronic contract conclusion service between a plurality of users. The server 10 is an information processing device that provides a service of storing and managing contract information concluded between a plurality of users.
The server 10 includes a memory unit 101 and a control unit 104 .

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

The application program 1011 is a program that causes the control unit 104 of the server 10 to function as each functional unit.

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

The user ID is an item for storing user identification information for identifying a user. The user identification information is an item for which a unique value is set for each user.
The user name is an item for storing the name of the user. The user name may be set to any character string such as a nickname instead of a name.
The email address is an item for storing the email address of the user.
The group ID is an item for storing group identification information of a group to which a user belongs. Groups are defined by a group table 1013, which will be described later, and a user may belong to multiple groups.

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

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

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

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

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

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

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

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

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

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

<Configuration of 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, and a contract confirmation unit 1043. The control unit 104 executes an application program 1011 stored in the storage unit 101, thereby realizing each functional unit.

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

The contract creation unit 1042 executes the contract creation process. Details will be described later.

The contract confirmation unit 1043 executes the contract confirmation process. Details will be described later.

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

<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 .

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 user with the services disclosed herein. The first user ID 2011 includes information such as a session ID that is temporarily assigned by the server 10 when identifying the user using the first user terminal 20.

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

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

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

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

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

<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 .

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 user with the services disclosed herein. The second user ID 3011 includes information such as a session ID that is temporarily assigned by the server 10 to identify the user who is using the second user terminal 30.

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

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

<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 .

<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 .

<Operation of System 1>
Each process of the system 1 will be described below.
FIG. 11 is a flowchart showing the operation of the contract creation process.
FIG. 12 is a flowchart showing the operation of the contract confirmation process.
FIG. 13 is a screen example showing the operation of the contract creation process.
FIG. 14 is an example of a screen showing a confirmation request message sent to the second user terminal 30. As shown in FIG.
FIG. 15 is an example of a first screen showing the operation of the contract confirmation process.
FIG. 16 is a second example of a screen showing the operation of the contract confirmation process.
FIG. 17 is a third example of a screen showing the operation of the contract confirmation process.
FIG. 18 is a fourth example of a screen showing the operation of the contract confirmation process.
FIG. 19 is an example of a screen showing a signing completion message sent to the first user terminal 20. As shown in FIG.

In this disclosure, the contract creation process and contract confirmation process on server 10 are described below.

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

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

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

<Details of contract creation process>
In step S101, the contract creation unit 1042 of the server 10 accepts contract information to be the subject of a contract between the creator and the verifying party from the creator. The contract creation unit 1042 of the server 10 executes a contract acceptance step of accepting, from the first user, a contract document relating to a contract in which the number of lines per page and the number of characters per line are specified and which is laid out on a page-by-page basis.
The contract preparation unit 1042 of the server 10 executes a contract acceptance step of accepting, from the first user, a contract document relating to a contract that is laid out on a page-by-page basis.
Specifically, the first user operates the input device 206 of the first user terminal 20 and creates 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 the contract information can include such document data. The contract document received from the first user is document data that is laid out on a page-by-page basis, with the number of lines and the number of characters per line specified. For example, document data that is laid out on A4 size with 40 characters per line and 36 lines per page can be considered.
The first user operates the input device 206 of the first user terminal 20 and transmits the created document data and the first user ID 2011 to the server 10. The contract creation unit 1042 of the server 10 accepts the received first user ID 2011 and document data, and stores them in the creator ID and document data items of a new record in the document table 1014, respectively. As a result, the contract creation unit 1042 of the server 10 stores the new contract information in the document table 1014.

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

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

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

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

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

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

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

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

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

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

Input items 532, 533, and 534 are drawn as drawing objects on screen 50 for creating contract information. In input items 532 and 533, the user identification information "USER-B" of the user who has selected and set to input the input item is drawn as the assignment, and the item "Text" is drawn as the input item type. In input item 534 related to stamping, the user identification information "USER-C" of the user who has selected and set to stamp is drawn as the assignment, and the item "Stamp" is drawn as the input item type.

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

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

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

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

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

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

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

<Contract Information Display Process (First Example)>
In step S303, the contract confirmation unit 1043 of the server 10 executes a contract presenting step of presenting the contract document stored in the contract storing step to the second user in a second layout different from the page-by-page layout.
The contract presentation step executes a step of presenting the contract document to the second user with a number of lines per page that differs from the number of lines in the page-based layout or a number of characters per line that differs from the number of characters in the page-based layout, depending on the second user terminal of the second user.

15 is an example of a first screen of a confirmation screen showing the operation of the contract confirmation process. The confirmation screen 70 for approving the contract information, which is displayed on the display 3081 of the second user terminal 30, includes a status 710 showing the current creation status of the contract information, a contract information display area 730, document data 731, input items 732, 733, 734, 735, 736, and an Agree button 740.
If the second user terminal 30 is a PC or the like, the display 3081 of the second user terminal 30 is large enough to display the contract document in a page-by-page layout, and therefore the document data 731 is presented to the second user in the page-by-page layout accepted in step S101 of the contract creation process.

16 is a second example of the confirmation screen showing the operation of the contract confirmation process. The document data 731 displayed on the confirmation screen 70 is presented to the second user in a second layout according to the size of the display 3081 of the second user terminal 30, rather than the page-by-page layout accepted in step S101 of the contract creation process.
If the second user terminal 30 is a smartphone or the like, the display 3081 of the second user terminal 30 is not large enough to display the contract document in a page-by-page layout, so the document data 731 is presented to the second user in a second layout that differs from the page-by-page layout accepted in step S101 of the contract creation process.

Specifically, the display 3081 of the second user terminal 30 presents the second user with a confirmation screen 70 for accepting an operation to approve the contract information. The confirmation screen 70 includes a thumbnail 760 and a keyword input field 770.
The second user checks and approves the document data 731 displayed on the display 3081 of the second user terminal 30. The confirmation screen 70 presented to the second user may be configured to be presented to the second user in a language notation specified for the checker, based on the language information stored in the language data item of the record of the second user in the confirmation table 1015.

Specifically, the contract confirmation unit 1043 of the server 10 extracts text data of the contract document included in the acquired contract information, lays out the text data with the number of characters per line according to the size of the display 3081 of the second user terminal 30, and displays the text data as document data 731 on the display 3081 of the second user terminal 30. The document data 731 displayed on the display 3081 of the second user terminal 30 does not need to be displayed in page units, and may be configured to be displayed by scrolling or the like across the entire contract document. The second user can vertically scroll the document data 731 by executing an operation such as swiping or flicking on the touch device of the second user terminal 30. The document data 731 may be configured to be scrollable horizontally.
This allows the second user to comfortably view the electronic contract in a display format that suits the information processing terminal that the second user is using.

In step S303, the contract presentation step executes a step of presenting the contract document laid out on a page-by-page basis to the second user together with the contract document presented in the second layout. The contract presentation step executes a step of presenting a page including a presentation portion of the contract document presented to the second user in the second layout as the contract document laid out on a page-by-page basis.
Specifically, on the display 3081 of the second user terminal 30, the contract document is displayed in thumbnail 760 in the page-by-page layout accepted in step S101 of the contract creation process, superimposed on the document data 731. The thumbnail 760 displays pages including clauses, articles, etc., which are the same as the presented locations of the clauses, articles, etc. of the contract document displayed in the document data 731, in the page-by-page layout. In the present disclosure, the thumbnail 760 is configured to display one page of the contract document, but multiple pages of the contract document may be displayed side by side in multiple thumbnails 760.
This allows the second user to comfortably view the document data 731 in a display format suited to the information processing terminal he or she is using while checking thumbnail images of the contract document laid out on a page-by-page basis.

<Search process (first embodiment)>
In step S303, the contract confirmation unit 1043 of the server 10 executes a search step of accepting a keyword from the second user.
Specifically, the second user can input any keyword into a keyword input field 770 displayed on the confirmation screen 70. The keyword may be extracted from the contract document by morphological analysis or the like, and the extracted keyword may be presented to the second user as an input candidate, and the selection may be accepted.

In step S303, the contract presentation step includes a step of presenting the page including the keyword received in the search step as a contract document laid out on a page-by-page basis, and a step of presenting to the second user a portion of the contract document presented in the second layout that corresponds to the keyword received in the search step in a manner different from other portions.
including.
Specifically, in document data 731 displayed on confirmation screen 70, the keyword entered in keyword input field 770 is presented in display form 771 in which the location of the search keyword is highlighted, bolded, underlined, or the like in the contract document presented in the second layout. Also, in document data 731 displayed on confirmation screen 70, wording relating to clauses or provisions that do not include the keyword entered in keyword input field 770 may not be displayed, and only wording relating to clauses or provisions that include the keyword entered in keyword input field 770 may be displayed.
This allows the second user to comfortably view the electronic contract. Furthermore, the thumbnail 760 displays the page of the contract document that contains the keyword entered in the keyword entry field 770. A configuration may be adopted in which multiple pages are displayed side by side as multiple thumbnails 760. If the pages do not fit on the confirmation screen 70, a configuration may be adopted in which multiple thumbnails 760 are selectively displayed by scrolling.
This allows the second user to input a search keyword and comfortably view the electronic contract in a display mode in which the search keyword portion is highlighted, bolded, underlined, etc. in the document data 731 presented in the second layout while checking thumbnails 760 of the contract document laid out in page units including the search keyword. Also, the second user can efficiently check only the wording related to clauses or provisions including the search keyword, without checking the wording related to clauses or provisions not including the search keyword in the document data 731 presented in the second layout.

<Search process (second embodiment)>
In step S303, the contract confirmation unit 1043 of the server 10 executes a search step of receiving position information regarding the positions of the contracting parties of the contract document from the second user.
Specifically, the second user can input position information related to the position of the contracting parties of the contract document in the keyword input field 770 displayed on the confirmation screen 70. Position information is information related to the position and role of each contracting party when a contract is concluded between multiple contracting parties such as a trustor, a trustee, a seller, and a buyer. Position information may be extracted from position information, etc. included in the contract document by morphological analysis or the like, and the position information may be presented to the second user as an input candidate and selected.

In step S303, the contract presentation step includes a step of presenting the page including the position information received in the search step as a contract document laid out on a page-by-page basis, and a step of presenting to the second user a portion of the contract document presented in the second layout that corresponds to the position information received in the search step in a manner different from other portions.
including.
Specifically, in the document data 731 displayed on the confirmation screen 70, the keyword input in the keyword input field 770 is presented in a display mode 771 in which the position information in the contract document presented in the second layout is highlighted, bolded, underlined, or the like. Also, in the document data 731 displayed on the confirmation screen 70, wording relating to clauses or provisions that do not include the position information input in the keyword input field 770 may not be displayed, and only wording relating to clauses or provisions that include the position information input in the keyword input field 770 may be displayed.
This allows the second user to comfortably view the electronic contract. Furthermore, the thumbnail 760 displays the page of the contract document that includes the position information entered in the keyword input field 770. A configuration may be adopted in which multiple pages are displayed side by side as multiple thumbnails 760. If the pages do not fit on the confirmation screen 70, a configuration may be adopted in which multiple thumbnails 760 are selectively displayed by scrolling.
This allows the second user to input position information and check thumbnails 760 of the contract document laid out on a page-by-page basis including the position information, while comfortably viewing the electronic contract in a display mode in which the search keyword locations are highlighted, bolded, underlined, etc. in the document data 731 presented in the second layout. Also, the second user can efficiently check only the wording related to clauses or provisions including position information, without checking the wording related to clauses or provisions not including position information in the document data 731 presented in the second layout.

<Contract Information Display Process (Second Embodiment)>
In step S303, a contract presentation step is executed in which the portions of the contract document where the input objects received in the input placement step are placed (clauses or clauses) are presented to the second user in a layout that is substantially identical to the page-by-page layout, and the portions of the contract document where the input objects received in the input placement step are not placed (clauses or clauses) are presented to the second user in a second layout.

17 is a third example of a confirmation screen showing the operation of the contract confirmation process. The document data 731 displayed on the confirmation screen 70 is presented to the second user in a second layout according to the size of the display 3081 of the second user terminal 30, rather than the page-by-page layout accepted in step S101 of the contract creation process.
In the third screen example, an area 790 in which input items 732, 733, 734, 735, and 736 are arranged in the document data 731 is presented on the display 3081 of the second user terminal 30 in a layout similar to the page-by-page layout accepted in step S101 of the contract creation process. On the other hand, an area in which no input items are arranged is presented to the second user in a second layout according to the size of the display 3081 of the second user terminal 30.

Specifically, in the document data 731 displayed on the confirmation screen 70, the location 790 (clause or provision) where the input items 732, 733, 734, 735, 736, etc. are arranged is displayed on the display 3081 of the second user terminal 30 in the same layout as the page-by-page layout, rather than in a layout that corresponds to the size of the display 3081 of the second user terminal 30.
As a result, when a first user sets input fields in a contract document, the second user can check the contract document in the same layout as the page unit layout when the first user set the input fields in the contract document for the portion (clause or article) in which the input fields are placed in the contract document. In other words, there is no layout collapse for the portion (clause or article) in which the input fields are placed in the contract document, and the second user can check the contract document with the same content as the layout when the first user set the input fields. This makes it possible to avoid discrepancies in understanding of the contract document between the first user and the second user due to layout collapse.

<Contract Information Display Process (Third Embodiment)>
In step S303, the contract presentation step may include a step of presenting the location where the input object is placed (clause or provision) to the second user in a layout that is approximately the same as the page-by-page layout before accepting an approval operation for the contract document in the contract approval step.
Specifically, when the second user presses the consent button 740 displayed on the confirmation screen 70 by operating the input device 306 of the second user terminal 30, the location (clauses or clauses) of the input fields 732, 733, 734, 735, 736, etc. in the document data 731 displayed on the confirmation screen 70 may be displayed on the display 3081 of the second user terminal 30 in the same layout as the page-by-page layout, rather than in a layout that corresponds to the size of the display 3081 of the second user terminal 30.
As a result, when a first user sets input fields in a contract document, a second user can check the contract document in the same page layout as the first user set the input fields in the contract document before approving the contract document, thereby avoiding discrepancies in understanding of the contract document between the first user and the second user due to layout collapse.

<Contract information display process (fourth embodiment)>

In step S303, the contract presentation step includes a step of presenting one clause or clause out of all clauses or provisions contained in the contract document stored in the contract storage step by displaying it on the second user terminal screen of the second user, and a step of presenting another clause or clause in place of the one clause or clause by displaying it on the second user terminal screen of the second user in response to an input operation by the second user.
The contract presentation step includes a step of displaying, on the second user terminal screen, other clauses or provisions associated with one clause or provision displayed on the second user terminal screen together with the one clause or provision.

18 is a fourth example of a confirmation screen showing the operation of the contract confirmation process. The confirmation screen 70 for approving the contract information, which is displayed on the display 3081 of the second user terminal 30, includes a wording 780 relating to a clause or provision included in the contract document, a wording 781 relating to a clause or provision that quotes the wording 780, and a wording 782 relating to a clause or provision that the wording 780 quotes.
The control unit 304 of the second user terminal 30 extracts the contract document for each wording such as a clause or article, and displays each wording on the display 3081 of the second user terminal 30.
This allows the second user to check one clause or clause of the contract document on the screen of the second user terminal. Even if the second user terminal is a small portable information processing terminal such as a smartphone, the second user can comfortably view the electronic contract by switching the screen to display each clause or clause.
The second user can switch the content of the displayed wording 780 to the wording before or after the contract document by performing an input operation such as tapping, flicking, or swiping on the touch device of the second user terminal 30, and proceed with reading the contract document. For example, when a wording 1 is displayed on the display 3081 of the second user terminal 30, if the second user taps the left end of the display 3081 or swipes leftward, the wording displayed on the screen is switched to the clause or article before the wording 1. Similarly, if the second user taps the right end of the display 3081 or swipes rightward, the wording displayed on the screen is switched to the clause or article after the wording 1. Note that, by selecting a wording 780, etc., the second user can display other wordings 781, 782 associated with the wording 780 by reference, citation, being cited, etc. on the display 3081 of the second user terminal 30.

The contract presentation step may include a step of displaying, on the second user terminal screen, a clause or clause of another contract document that is equivalent or similar to a clause or clause displayed on the second user terminal screen, together with the clause or clause.
Specifically, when the second user selects the wording 780 or the like on the confirmation screen 70 for approving the contract information displayed on the display 3081 of the second user terminal 30, the control unit 304 of the second user terminal 30 transmits a request to the server 10 to search for the wording of other contract documents that are equivalent or similar. The contract confirmation unit 1043 of the server 10 searches the document data items of the document table 1014 based on the received wording 780, and searches for the wording of other contract documents that are equivalent or similar to the wording 780. Note that the contract confirmation unit 1043 of the server 10 may divide the contract document stored in the document data of the document table 1014 in advance into clause or article wordings, and index them in a manner that allows searching by any wording by morphological analysis or the like. This allows the contract confirmation unit 1043 of the server 10 to quickly search for the wording of other contract documents that are equivalent or similar to the wording 780 based on the received wording 780.
Note that the term "equivalent or similar" may be determined as being equivalent or similar to a predetermined similarity or more based on a measure such as the cosine similarity of the text related to the term. Alternatively, the term "equivalent or similar" may be determined as being equivalent or similar to a predetermined similarity or more by analyzing the contents such as the meanings of the rights and obligations between the contracting parties stipulated in the term.
In addition, the control unit of the second user terminal 30 may display clauses or provisions of other equivalent or similar contract documents on the display 3081 of the second user terminal 30, as in the wording 781 and 782 of FIG.

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

In step S305, the contract confirmation unit 1043 of the server 10 executes a contract approval step of accepting an approval operation for the contract document presented in the contract presentation step from the second user. The contract approval step includes a step of storing information on the second layout presented to the second user in the contract presentation step in association with the contract document.
Specifically, the contract confirmation unit 1043 of the server 10 accepts an instruction from the second user to agree and approve the conclusion of the contract for the contract information accepted from the first user. The second user checks the contract information and input data displayed on the display 3081 of the second user terminal 30, and if the second user agrees or accepts the contents, operates the input device 306 of the second user terminal 30 and presses the Agree button 740 displayed on the confirmation screen 70 for confirming the contract information, thereby executing a process of transmitting a request including the document ID, information identifying the second user, and input data for each input item entered in step S305 to the server 10. The information identifying the second user may be the second user ID 3011.

The contract confirmation unit 1043 of the server 10 stores information indicating that the second user has confirmed the contract information based on the received request. Specifically, the contract confirmation unit 1043 of the server 10 searches the confirmation table 1015 based on the received document ID and information identifying the second user, and stores a value of True in the confirmation flag field of the record. For example, when the information identifying the second user is an email address, the contract confirmation unit 1043 searches the document ID and confirmer email address fields of the confirmation table 1015, and stores a value of True in the confirmation flag field of the record. When the information identifying the second user is user identification information, the contract confirmation unit 1043 searches the document ID and confirmer email address fields of the confirmation table 1015 based on the email address of the second user identified by searching the user ID field of the user table 1012, and stores a value of True in the confirmation flag field of the record.
The contract confirmation unit 1043 of the server 10 stores the received input data in the input data item of the input item table 1016 specified by the input item ID associated with the input data. As a result, in step S305, the input data entered by the second user is stored as input item information in the input item table 1016.

Furthermore, the contract confirmation unit 1043 of the server 10 stores information regarding the second layout presented to the second user in step S303 in association with the contract document, in association with the document data in the document table 1014. Specifically, the number of characters per line in the second layout and the screen size of the display 3081 of the second user terminal 30 in the second layout are stored.
This allows the second layout information, which is the presentation format of the contract document to the second user, to be stored when the first user provides input fields in the contract document. For example, when a discrepancy occurs in the understanding of the contract document concluded between the first user and the second user, it is possible to confirm in what layout the second user confirmed and approved the contract document. The second user can confirm whether or not a misunderstanding occurred in the understanding of the contract document by checking the contract document laid out in the second layout.

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

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

Figure 19 is an example screen showing a message notified to the first user terminal 20. The message screen 80 displayed on the display 2081 of the first user terminal 20 includes information about a message 81 and a URL 82 that includes a document ID for identifying contract information.

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

In step S305, after the contract approval step, the contract confirmation unit 1043 of the server 10 executes a second contract presentation step of presenting the contract document stored in the contract storage step to the first user in a second layout.
Specifically, the first user can open a web page specified by a URL included in the received message using a browser application of the first user terminal 20. The first user terminal 20 refers to the contract information and transmits a request for inquiry to the server 10. The contract confirmation unit 1043 of the server 10 refers to the contract information, generates a web page for inquiry, and transmits it to the first user terminal 20.

The control unit 204 of the first user terminal 20 presents the acquired contract document on the display 2081 of the first user terminal 20 in the same layout as the second layout presented on the display 3081 of the second user terminal 30 in step S303.
This allows the second user to check the contract document in what layout it was confirmed by the second user, and after the second user has approved the contract document, the contract document is presented to the first user in the second layout, and if there are no problems with the contents of the contract document presented in the second layout, the first user performs a confirmation operation.

In step S305, the contract confirmation unit 1043 of the server 10 executes a contract confirmation step of accepting, from the first user, a confirmation operation for the contract document presented in the second layout in the second contract presentation step.
The first user operates the input device 206 of the first user terminal 20, and if there are no problems with the contents of the contract document laid out in the second layout presented on the display 2081 of the first user terminal 20, he/she presses the ``Confirm'' button displayed on the display 2081 of the first user terminal 20 and performs a confirmation operation on the contract document.
If there is a problem with the contents of the contract document laid out in the second layout, the second user may be notified of this.

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

Specifically, the contract confirmation unit 1043 of the server 10 searches the user ID or email address item in the user table 1012 based on the user ID or email address to obtain the group ID item. The contract confirmation unit 1043 of the server 10 searches the group ID item in the group table 1013 based on the obtained group ID item, obtains the administrator ID item, identifies a user with authority equivalent to an administrator based on the administrator ID by searching the user ID in the user table 1012, and sends a message notifying that the contract confirmation process has been completed.

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

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

The processor 901 is hardware for executing a set of instructions written in a program. The processor 901 is composed of an arithmetic unit, registers, peripheral circuits, etc.

The main memory device 902 is used to temporarily store programs and data processed by the programs. For example, it is a volatile memory such as a DRAM (Dynamic Random Access Memory).

The auxiliary storage device 903 is a storage device for saving data and programs. For example, it is a flash memory, a hard disk drive (HDD), a magneto-optical disk, a CD-ROM, a DVD-ROM, a semiconductor memory, etc.

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

The computer 90 can be realized virtually by distributing all or part of each hardware configuration across multiple computers 90 and connecting them together via a network. In this way, the concept of computer 90 includes not only a computer 90 housed in a single housing or case, but also a virtualized computer system.

<Basic Functional Configuration of Computer 90>
A description will now be given of the functional configuration of a computer realized by the basic hardware configuration (FIG. 20) of a computer 90. The computer includes at least the functional units of a control unit, a storage unit, and a communication unit.

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

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

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

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

In addition, the databases and masters in this disclosure may include any data structure (such as a list, dictionary, associative array, or object) 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.

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

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

(Appendix 1)
An electronic contract program for causing a computer having a processor and a memory unit to execute electronic contract procedures between different organizations, wherein the processor executes a contract acceptance step (S101) of accepting a contract document relating to a contract laid out on a page basis from a first user, a contract storage step (S101) of storing the contract document accepted in the contract acceptance step, a contract presentation step (S303) of presenting the contract document stored in the contract storage step to a second user in a second layout different from the layout, and a contract approval step (S305) of accepting an approval operation for the contract document presented in the contract presentation step from the second user.
This allows the second user to comfortably view the electronic contract in a display format that suits the information processing terminal that the second user is using.

(Appendix 2)
An electronic contract program as described in Appendix 1, wherein the contract acceptance step (S101) is a step of accepting a contract document in which the number of lines per page and the number of characters per line are specified, and the contract presentation step (S303) is a step of presenting the contract document to a second user with a number of lines per page different from the number of lines or a number of characters different from the number of characters per line, depending on the second user terminal of the second user.
This allows the second user to comfortably view the electronic contract in a display format that suits the information processing terminal that the second user is using.

(Appendix 3)
The contract presentation step (S303) is a step of presenting the contract document laid out on a page-by-page basis to the second user together with the contract document presented in the second layout, and the contract presentation step (S303) is a step of presenting a page including the presentation portion of the contract document presented to the second user in the second layout as the contract document laid out on a page-by-page basis, the electronic contract program described in Appendix 1.
This allows the second user to comfortably view the electronic contract in a display format suited to the information processing terminal he or she is using while checking thumbnail images, etc., of the contract document laid out on a page-by-page basis.

(Appendix 4)
An electronic contract program as described in Appendix 3, comprising a search step (S303) in which the processor receives keywords from a second user, and a contract presentation step (S303) including a step of presenting pages including the keywords received in the search step as a contract document laid out on a page-by-page basis, and a step of presenting to the second user, among the contract document presented in the second layout, the portion corresponding to the keyword received in the search step in a manner different from other portions.
This allows the second user to input a search keyword and check thumbnail images, etc., of the contract document laid out on a page-by-page basis containing the search keyword, while comfortably viewing the electronic contract in a display format in which the search keyword is highlighted, bolded, underlined, or otherwise emphasized in the contract document presented in the second layout.

(Appendix 5)
An electronic contract program as described in Appendix 3, comprising a search step (S303) in which the processor receives from a second user position information relating to the positions of the contracting parties to the contract document, and a contract presentation step (S303) including a step of presenting pages including the position information received in the search step as a contract document laid out on a page-by-page basis, and a step of presenting to the second user, among the contract document presented in the second layout, a portion including the position information received in the search step in a manner different from other portions.
This allows the second user to input position information regarding the positions of the contracting parties to the contract document, and thereby enable him or her to comfortably view the electronic contract while checking thumbnail images, etc., of the contract document laid out on a page-by-page basis including the position information, and with the position information displayed in the contract document presented in the second layout in an emphasized manner, such as by highlighting, making it bold, or underlining it.

(Appendix 6)
An electronic contract program as described in Appendix 1, in which a processor executes an input arrangement step (S103) in which the processor accepts from the first user the arrangement of input objects for the contract document accepted in the contract acceptance step, and a contract presentation step (S303) in which the parts of the contract document in which the input objects accepted in the input arrangement step are arranged are presented to the second user in a layout that is substantially identical to the layout on a page basis, and the parts of the contract document in which the input objects accepted in the input arrangement step are not arranged are presented to the second user in a second layout.
As a result, when a first user sets input fields in a contract document, the second user can check the contract document in the same layout as the page unit layout when the first user set the input fields in the contract document for the parts of the contract document where the input fields are arranged. In other words, there is no layout collapse for the parts of the contract document where the input fields are arranged, and the second user can check the contract document with the same content as the layout when the first user set the input fields. This makes it possible to avoid discrepancies in understanding of the contract document between the first user and the second user due to layout collapse.

(Appendix 7)
The electronic contract program described in Appendix 6, wherein the contract presentation step (S303) is a step of presenting the location where the input object is placed to the second user in a layout substantially identical to the page-by-page layout before accepting an approval operation for the contract document in the contract approval step.
As a result, when a first user sets input fields in a contract document, a second user can check the contract document in the same page layout as the first user set the input fields in the contract document before approving the contract document, thereby avoiding discrepancies in understanding of the contract document between the first user and the second user due to layout collapse.

(Appendix 8)
An electronic contract program as described in Appendix 1, in which a processor executes an input arrangement step (S103) of accepting from a first user the arrangement of input objects for the contract document accepted in the contract acceptance step, and a contract presentation step (S303) of presenting to a second user clauses or provisions in the contract document in which the input objects accepted in the input arrangement step are arranged in a layout that is substantially identical to the layout on a page basis, and presenting to a second user clauses or provisions in the contract document in which the input objects accepted in the input arrangement step are not arranged in a second layout.
As a result, when a first user sets input fields in a contract document, the second user can check the clauses or provisions in which the input fields are arranged in the contract document in the same layout as the page-by-page layout when the first user set the input fields in the contract document. In other words, the clauses or provisions in which the input fields are arranged in the contract document are not distorted in layout, and the second user can check the contract document in the same content as the layout when the first user set the input fields. This makes it possible to avoid discrepancies in understanding of the contract document between the first user and the second user due to layout distortion.

(Appendix 9)
The electronic contract program described in Appendix 8, wherein the contract presentation step (S303) is a step of presenting the clause or clause in which the input object is placed to the second user in a layout substantially identical to the page-by-page layout before accepting an approval operation for the contract document in the contract approval step.
As a result, when a first user sets input fields in a contract document, a second user can check the contract document in the same page layout as the first user set the input fields in the contract document before approving the contract document, thereby avoiding discrepancies in understanding of the contract document between the first user and the second user due to layout collapse.

(Appendix 10)
An electronic contract program as described in Appendix 1, comprising an input arrangement step (S103) in which a processor accepts from a first user the arrangement of input objects for the contract document accepted in the contract acceptance step, and a contract approval step (S305) in which information regarding the second layout presented to the second user in the contract presentation step is stored in association with the contract document.
This allows the second layout information, which is the presentation format of the contract document to the second user, to be stored when the first user provides input fields in the contract document. For example, when a discrepancy occurs in the understanding of the contract document concluded between the first user and the second user, it is possible to confirm in what layout the second user confirmed and approved the contract document. The second user can confirm whether or not a misunderstanding occurred in the understanding of the contract document by checking the contract document laid out in the second layout.

(Appendix 11)
An electronic contract program as described in Appendix 10, in which a processor executes, after the contract approval step, a second contract presentation step (S305) of presenting the contract document stored in the contract storage step to the first user in a second layout, and a contract confirmation step (S305) of accepting a confirmation operation from the first user regarding the contract document presented in the second layout in the second contract presentation step.
This allows the contract document to be presented to the first user in a second layout after the second user has approved the contract document, and if there are no problems with the contents of the contract document presented in the second layout, the first user can perform a confirmation operation.

(Appendix 12)
The contract presentation step (S303) includes a step of presenting one clause or provision out of all clauses or provisions contained in the contract document stored in the contract storage step by displaying it on the second user terminal screen of the second user, and a step of presenting another clause or provision in place of the one clause or provision by displaying it on the second user terminal screen of the second user in response to an input operation by the second user, in the electronic contract program described in Appendix 1.
This allows the second user to check one clause or clause of the contract document on the screen of the second user terminal. Even if the second user terminal is a small portable information processing terminal such as a smartphone, the second user can comfortably view the electronic contract by switching the screen to display each clause or clause.

(Appendix 13)
The contract presentation step (S303) is a step of displaying other clauses or provisions associated with one clause or provision displayed on the second user terminal screen together with the one clause or provision, in the electronic contract program described in Appendix 12.
This allows the second user, when switching between screens for each clause or provision, to also check other clauses or provisions that are associated with that clause or provision by reference, citation, being cited, etc. Even if the second user terminal is a small portable information processing terminal such as a smartphone, the second user can comfortably view the electronic contract.

(Appendix 14)
The contract presentation step (S303) is a step of displaying, on the second user terminal screen, clauses or provisions of other contract documents that are equivalent or similar to the clause or provision displayed on the second user terminal screen, together with the clause or provision displayed on the second user terminal screen, in the electronic contract program described in Appendix 12.
This allows the second user to check clauses or clauses of other contract documents that are equivalent or similar to the clause or clause when switching between screens for each clause or clause. Even if the second user terminal is a small portable information processing terminal such as a smartphone, the second user can comfortably view the electronic contract.

(Appendix 15)
An information processing device comprising a processor and a memory unit, wherein the processor executes an electronic contract program described in any one of Supplementary Notes 1 to 13.
This allows the second user to comfortably view the electronic contract in a display format that suits the information processing terminal that the second user is using.

(Appendix 16)
A manufacturing method for an information processing system including an information processing device having a processor and a memory unit, wherein the processor executes an electronic contract program described in any one of Appendices 1 to 13.
This allows the second user to comfortably view the electronic contract in a display format that suits the information processing terminal that the second user is using.

(Appendix 17)
An information processing method executed by a computer having a processor and a memory unit, wherein the computer executes an electronic contract program described in any one of Supplements 1 to 13.
This allows the second user to comfortably view the electronic contract in a display format that suits the information processing terminal that the second user is using.

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

Claims (17)

An electronic contract program for causing a computer having a processor and a storage unit to execute electronic contract procedures between different organizations,
The processor,
a contract receiving step of receiving, from a first user, a contract document relating to a contract laid out on a page-by-page basis;
a contract storage step of storing the contract document accepted in the contract acceptance step;
a contract presentation step of presenting the contract document stored in the contract storage step to a second user in a second layout different from the first layout;
a contract approval step of accepting an approval operation for the contract document presented in the contract presentation step from the second user;
An electronic contracting program that implements the above. the contract acceptance step is a step of accepting the contract document in which the number of lines per page and the number of characters per line are specified,
the contract presentation step is a step of presenting the contract document to the second user with a number of lines per page different from the number of lines or a number of characters per line different from the number of characters, depending on a second user terminal of the second user;
2. The electronic contract program of claim 1. the contract presentation step is a step of presenting the contract document laid out on a page-by-page basis to the second user together with the contract document presented in the second layout,
The contract presentation step is a step of presenting a page including a presentation portion of the contract document presented to the second user in the second layout as the contract document laid out on a page-by-page basis.
2. The electronic contract program of claim 1. The processor,
a searching step of accepting a keyword from the second user;
The contract presentation step includes:
presenting the pages including the keywords received in the search step as the contract document laid out on a page-by-page basis;
presenting to the second user a portion of the contract document presented in the second layout that corresponds to the keyword received in the search step in a manner different from other portions of the contract document;
including,
4. The electronic contract program according to claim 3. The processor,
a searching step of receiving, from the second user, position information regarding the positions of the contracting parties of the contract document;
The contract presentation step includes:
presenting the page including the position information received in the search step as the contract document laid out on a page-by-page basis;
presenting to the second user a portion of the contract document presented in the second layout, the portion including the position information received in the search step, in a manner different from other portions;
including,
4. The electronic contract program according to claim 3. The processor,
an input arrangement step of accepting, from the first user, an arrangement of an input object for the contract document accepted in the contract acceptance step;
Run
The contract presentation step includes:
presenting to the second user a portion of the contract document in which the input object accepted in the input arrangement step is arranged in a layout substantially identical to the layout in page units;
a portion of the contract document in which the input object accepted in the input arrangement step is not arranged is presented to the second user in the second layout;
The steps are:
2. The electronic contract program of claim 1. The contract presentation step is a step of presenting to the second user a location where the input object is arranged in a layout substantially identical to the layout in units of pages before an approval operation for the contract document is accepted in the contract approval step.
7. The electronic contract program according to claim 6. The processor,
an input arrangement step of accepting, from the first user, an arrangement of an input object for the contract document accepted in the contract acceptance step;
Run
The contract presentation step includes:
presenting to the second user the clause or clause in which the input object accepted in the input arrangement step is arranged in the contract document in a layout substantially identical to the layout in page units;
a clause or a provision in the contract document in which the input object accepted in the input arrangement step is not arranged is presented to the second user in the second layout;
The steps are:
2. The electronic contract program of claim 1. the contract presentation step is a step of presenting to the second user, before an approval operation for the contract document is accepted in the contract approval step, a clause or a clause in which the input object is arranged, in a layout substantially identical to the layout in units of pages.
9. The electronic contract program according to claim 8. The processor,
an input arrangement step of accepting, from the first user, an arrangement of an input object for the contract document accepted in the contract acceptance step;
The contract approval step includes a step of storing information about the second layout presented to the second user in the contract presentation step in association with the contract document.
2. The electronic contract program of claim 1. The processor,
a second contract presentation step of presenting the contract document stored in the contract storage step to the first user in the second layout after the contract approval step;
a contract confirmation step of accepting a confirmation operation for the contract document presented in the second layout in the second contract presentation step from the first user;
Execute
The electronic contract program according to claim 10. The contract presentation step includes:
presenting, by displaying on a second user terminal screen of the second user, one clause or article among all clauses or articles included in the contract document stored in the contract storage step;
presenting another clause or article by displaying it on a second user terminal screen of the second user in place of the one clause or article in response to an input operation of the second user;
including,
2. The electronic contract program of claim 1. The contract presentation step is a step of displaying, on the second user terminal screen, another clause or clause associated with one clause or clause displayed on the second user terminal screen together with the one clause or clause.
13. The electronic contract program of claim 12. The contract presentation step is a step of displaying, on the second user terminal screen, a clause or clause of another contract document that is equivalent or similar to the one clause or clause displayed on the second user terminal screen, together with the one clause or clause.
13. The electronic contract program of claim 12. An information processing device including a processor and a storage unit,
The processor executes an electronic contract program according to any one of claims 1 to 13.
Information processing device. A method for manufacturing an information processing system including an information processing device having a processor and a storage unit,
The processor executes an electronic contract program according to any one of claims 1 to 13.
A method for manufacturing an information processing system. An information processing method executed by a computer including a processor and a storage unit,
The computer executes an electronic contract program according to any one of claims 1 to 13.
Information processing methods.