Program, method, information processing apparatus, and system

Abstract

To provide a program, a method, an information processing apparatus, and a system for supporting confirmation of a contract document described in a language unfamiliar to a user.SOLUTION: In a computer equipped with a processor and a storage unit, a program for use in a task related to a contract document concluded between a first user and a second user causes the processor to execute a contract document confirmation process, the process including: a contract receiving step of receiving a contract document related to a contract, from the first user; and a presentation step of presenting, to the second user, a translated contract document together with the contract document received in the contract receiving step.SELECTED DRAWING: Figure 15

Description

[Technical field]

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

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

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

[0004] In electronic contract procedures between multiple users, there is a problem that it is necessary to carry out contract procedures for contract documents written in a language that is unfamiliar to the users themselves. Therefore, the present disclosure has been made to solve the above problem, and its purpose is to provide a technology that supports the confirmation of a contract document written in a language that is unfamiliar to the user. [Means for solving the problem]

[0005] A program having a processor and a memory unit, and used on a computer for work related to a contract document to be concluded between a first user and a second user, wherein the processor executes a contract acceptance step of accepting a contract document related to a contract from the first user, and a presentation step of presenting a translation of the contract document to the second user together with the contract document accepted in the contract acceptance step. Effect of the Invention

[0006] According to the present disclosure, it is possible to assist in the confirmation of contract documents written in a language that is unfamiliar to the contracting parties. [Brief description of the drawings]

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

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

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

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

[0011] <Server 10 Configuration> The server 10 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 storage unit 101 and a control unit 104 .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0026] <Configuration of the control unit 104 of the server 10> The control unit 104 of the server 10 includes a user registration control unit 1041, a contract creation unit 1042, 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0044] <System 1 Operation> 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 a screen example showing the operation of the contract confirmation process. FIG. 16 is an example of a screen showing a conclusion completion message sent to the first user terminal 20. In FIG.

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

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

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

[0048] <Outline of contract creation process> The contract creation process is a series of processes in which the creator creates electronic contract information, sets the reviewer 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, presents a translation of the electronic contract information, and sends the electronic contract information to the set reviewer.

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

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

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

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

[0053] In step S102, the contract preparation unit 1042 of the server 10 executes a checker addition step of adding a third user determined according to the description language of the contract document accepted in the contract acceptance step to checkers of the contract document. Specifically, the contract preparation unit 1042 of the server 10 identifies the description language (English, Japanese, Chinese, etc.) of the contract document based on the contract information received in step S101. The description language may be identified by pattern matching using predetermined keywords, machine learning, deep learning, or any artificial intelligence system. The contract creation unit 1042 of the server 10 searches for items such as language (supported language) (not shown) in the user table 1012, etc., based on the identified description language, to identify users associated with the language. Specifically, it identifies users who can handle tasks such as reviewing contract documents in the description language. The contract creation unit 1042 of the server 10 stores the email address, document ID, and supported language of the identified user or users (third users) in the items of confirmer email address, document ID, and language data in the confirmation table 1015, respectively, and stores the contract information in association with the email address of the third user (third email address). Note that the confirmation table 1015 may be configured to store the contract information in association with the user identification information of the third user, instead of the third email address. Also, the contract creation unit 1042 of the server 10 may transmit the user IDs and user names of the identified one or more users to the first user terminal 20, and the control unit 204 of the first user terminal 20 may display and present the received one or more user IDs and user names as candidates for checkers (checker candidates) on the display 2081 of the first user terminal 20. The first user may select one or more checkers as necessary from the checker candidates presented on the display 2081 of the first user terminal 20, and store them in the confirmation table 1015.

[0054] The step of adding a confirmer is not essential. In addition, in the present disclosure, the first user sets the third user, but this is not limited to the above. For example, a third user who can handle tasks such as reviewing contract documents in a description language in an organization to which the second user belongs may be added as a checker according to the second user assigned as a checker by the first user. The addition may be performed automatically. In addition, the assignment of the third user to the verifying party does not have to be performed in step S102, and the third user may be assigned to the verifying party at any timing, such as after the contract information is sent in step S107 and after the access by the second user is accepted in step S301 of the contract verification process.

[0055] The first user may set the language and access code of the second user and store them in association with the email address of the second user. At this time, a value of 1 is stored in the confirmation order field of confirmation table 1015. In step S102, the first user may be able to select and set multiple users to be the confirmers. In this case, the value of the confirmation order field of the users to be the confirmers is incremented by one and stored according to the selection order. This sets the circulation order of the confirmers in the contract confirmation process described later. Note that setting the circulation order is not essential.

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

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

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

[0059] In step S106, the contract preparation unit 1042 of the server 10 executes a second presentation step of presenting to the first user the contract document translated together with the contract document accepted in the contract acceptance step. Specifically, the contract preparation unit 1042 of the server 10 generates translation data by translating the contract information based on the received contract information. Specifically, the contract preparation unit 1042 of the server 10 translates the text content of the document data included in the contract information based on the contract information by using any machine learning model, deep learning model, artificial intelligence model, external machine translation service, or the like. The contract creation unit 1042 of the server 10 is configured to translate the contract information received in step S101 into a language (language data) supported by the second user set by the first user in step S102. The contract creation unit 1042 of the server 10 may generate multiple pieces of translation data for multiple supported languages ​​corresponding to multiple second users. Furthermore, the contract creation unit 1042 of the server 10 may generate translation data by translating the accepted contract information into a predetermined language (Japanese, English, Chinese) based on the contract information. The contract creation unit 1042 of the server 10 searches the document table 1014 based on the document ID and stores the generated translation data in the translation data field of the record identified. As a result, the contract information accepted in step S101 and the translation data obtained by translating the contract information are stored in association with each other.

[0060] The contract creation unit 1042 of the server 10 transmits the generated translation data to the first user terminal 20. The control unit 204 of the first user terminal 20 displays the received translation data on the display 2081 of the first user terminal 20. This allows the first user to check the translation data obtained by translating the contract information to be presented to the second user before transmitting the translation data to the second user. Note that, when multiple second users are set as checkers, the contract information may be presented in a manner that allows each of the translation data translated into the languages ​​supported by the multiple second users to be selected. Note that processing such as term highlighting, which is executed in the translation presentation process (step S304) in the contract confirmation process described later, may also be provided to the first user. In addition, in the present disclosure, a configuration in which translation data is presented to the first user before the contract information is transmitted has been disclosed as an example, but the present invention is not limited to this. For example, the first user may be able to check the translation data after the contract creation process is completed, before the contract confirmation process is completed, or at any other timing.

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

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

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

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

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

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

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

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

[0069] <Outline of contract confirmation process> The contract confirmation process is a series of steps that include accepting access from the confirmer, presenting the confirmer with a confirmation screen that displays the contract information, presenting a translation of the electronic contract information, accepting input data for the input fields from the confirmer, and accepting data regarding confirmation of the contract information from the confirmer.

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

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

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

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

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

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

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

[0077] <Translated text presentation processing> In step S304, the contract confirmation unit 1043 of the server 10 executes a presentation step of presenting to the second user the contract document accepted in the contract acceptance step, as well as a translation of the contract document. Specifically, the contract confirmation unit 1043 of the server 10 transmits the translation data included in the contract information to the second user terminal 30. The control unit 304 of the second user terminal 30 displays and presents the received translation data on the display 3081 of the second user terminal 30. If a third user is designated as the verifying party, the translation of the contract document is presented to the third user.

[0078] In the present disclosure, a configuration in which translation data is generated in step S106 of the contract creation process has been described as an example, but a configuration in which translation data is generated during the translation presentation process may also be used. Specifically, the contract confirmation unit 1043 of the server 10 may generate translation data by translating the contract information into a language specified based on the language information stored in the language data field of the record of the second user in the confirmation table 1015. In this case, translation data is generated for each of one or more second users who execute the contract confirmation process. Note that the generation of the translation data is similar to that in step S106 of the contract creation process, and therefore a detailed description thereof will be omitted. The contract confirmation unit 1043 of the server 10 stores the generated translation data in the translation data field of the contract information record of the document table 1014 identified in step S302. In this case, step S106 in the contract creation process may be omitted.

[0079] 15 is an example of a confirmation screen showing the operation of the contract confirmation process. A confirmation screen 70 for approving the contract information, which is displayed on the display 3081 of the second user terminal 30, displays a status 710 showing the current creation status of the contract information, a contract information display area 730, document data 731, input items 732, 733, 734, 735, 736, an Agree button 740, translation data 750, and terms 751, 752. The control unit 304 of the second user terminal 30 displays the contract document (document data 731) and the translation of the contract document (translation data 750) on the display 3081 of the second user terminal 30. Note that the configuration does not necessarily require that the contract document and the translation of the contract document are displayed together.

[0080] In step S304, the presenting step includes a step of presenting to the second user a screen capable of accepting an input operation indicating agreement in the agreement accepting step. Specifically, the control unit 304 of the second user terminal 30 displays the contract document (document data 731), a translation of the contract document (translation data 750), and an Agree button 740 on the display 3081 of the second user terminal 30. By pressing the Agree button 740, the second user can agree to or consent to the contents of the presented contract document. When a third user is designated as the confirmer, a screen capable of accepting an input operation indicating that confirmation has been made is also presented to the third user.

[0081] <Term highlighting> In step S304, the contract confirmation unit 1043 of the server 10 executes a term selection step of accepting, from the second user, a selection of terms included in at least one of the contract document and the translation presented to the second user in the presentation step. The presenting step includes a step of presenting, in an identifiable manner, a portion of the contract document or a translation that corresponds to the term, based on the term accepted in the term selection step. Specifically, the second user operates the input device 306 of the second user terminal 30 to select and identify a term 751 included in the document data 731. The control unit 304 of the second user terminal 30 transmits information identifying the selected term 751 to the server 10. The contract confirmation unit 1043 of the server 10 receives the selected term 751 and identifies a term 752 in the translation data 750 that corresponds to the term 751. Specifically, the term 752 can be identified using a machine learning model, a deep learning model, any artificial intelligence model, or the like. The contract confirmation unit 1043 of the server 10 transmits the identified term 752 to the second user terminal 30. The control unit 304 of the second user terminal 30, based on the received term 752, highlights the term 752 included in the translation data 750 in a distinguishable manner using a predetermined color such as bold, underline, or red, a different font, or the like. Note that the second user can select terms included in translation data 750, instead of terms included in document data 731. In this case, the second user operates input device 306 of second user terminal 30 to select and specify term 752 included in translation data 750. In this case, control unit 304 of second user terminal 30 highlights term 751 included in document data 731 in an identifiable manner.

[0082] In step S305, 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.

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

[0084] 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 S306, the input data entered by the second user is stored as input item information in the input item table 1016.

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

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

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

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

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

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

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

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

[0093] <Basic computer hardware configuration> 17 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.

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

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

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

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

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

[0099] <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. 17) of a computer 90. The computer comprises at least the functional units of a control unit, a storage unit, and a communication unit.

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

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

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

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

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

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

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

[0107] (Appendix 1) A program having a processor and a memory unit, used on a computer for work related to a contract document to be concluded between a first user and a second user, the program executing a contract acceptance step (S101) in which the processor accepts a contract document related to a contract from the first user, and a presentation step (S304) in which the processor presents a translation of the contract document to the second user together with the contract document accepted in the contract acceptance step. This allows the second user to check the contract document by referring to the translation, even if the second user is not familiar with the language in which the contract document uploaded by the first user is written.

[0108] (Appendix 2) The program according to claim 1, further comprising: a processor executing a second presentation step (S106) of presenting to the first user a translation of the contract document together with the contract document accepted in the contract acceptance step. This allows the first user to check the translation of the contract document that he or she uploaded that will be presented to the second user.

[0109] (Appendix 3) A program described in Appendix 1, wherein the processor executes an agreement acceptance step (S306) of accepting, from the second user, an input operation indicating agreement to the contract document presented in the presentation step, and the presentation step (S304) includes a step of presenting to the second user a screen capable of accepting an input operation indicating agreement in the agreement acceptance step. This allows the second user to check the contract document by referring to the translation, and also allows the second user to agree to the contract document by referring to the translation. Even if the second user is not familiar with the language in which the contract document uploaded by the first user is written, the second user can appropriately agree to the contract document.

[0110] (Appendix 4) A program as described in Appendix 1, wherein the processor executes a term selection step (S304) of accepting from the second user a selection of a term contained in at least one of the contract document or the translation presented to the second user in the presentation step, and the presentation step (S304) includes a step of presenting, in an identifiable manner, a portion of the other of the contract document or the translation that corresponds to the term based on the term accepted in the term selection step. This allows the second user to select a term in either the contract document or the translation and have the corresponding part of the term highlighted in the other, making it easy to check how the selected term has been translated or what term the selected term is a translation of.

[0111] (Appendix 5) A program having a processor and a memory unit, the program being used on a computer for work related to a contract document concluded between a first user and a second user, the program executing a contract acceptance step (S101) in which the processor accepts a contract document related to a contract from the first user, and a verifyer addition step (S102) in which a third user, determined according to the description language of the contract document accepted in the contract acceptance step, is added to the verifyers of the contract document. This allows the second user to add a third user who can handle contract documents written in a language that the second user is not familiar with, even if the second user is not familiar with the language in which the contract document uploaded by the first user is written, as a reviewer. Even if the second user is not familiar with the language in which the contract document uploaded by the first user is written, the second user can appropriately respond to the contract document.

[0112] (Appendix 6) The program described in Appendix 5, in which a processor executes a confirmation receiving step (S306) of receiving an input operation from a third user indicating that the contract document received in the contract receiving step has been confirmed, and a confirmation storage step (S306) of storing information indicating confirmation of the contract document received in the confirmation receiving step from the third user in association with the contract document received in the contract receiving step. This makes it possible to store information indicating that the third user has confirmed the contract document in association with the contract document, thereby leaving a record that the contract document has been confirmed by a person capable of reading and understanding the contract document.

[0113] (Appendix 7) The program described in Appendix 6, wherein the processor executes a presentation step (S304) of presenting to a third user a translation of the contract document together with the contract document accepted in the contract acceptance step, the presentation step (S304) including a step of presenting to the third user a screen capable of accepting an input operation indicating confirmation in the confirmation acceptance step. This allows a third user to check the contract document using the translation as a reference.

[0114] (Appendix 8) A method implemented on a computer having a processor and a memory, the processor performing all of the steps performed in the invention according to any one of appendices 1 to 7. This allows the second user to check the contract document by referring to the translation, even if the second user is not familiar with the language in which the contract document uploaded by the first user is written.

[0115] (Appendix 9) An information processing device comprising a control unit and a memory unit, wherein the control unit executes all of the steps executed in the invention according to any one of Supplementary Note 1 to Supplementary Note 7. This allows the second user to check the contract document by referring to the translation, even if the second user is not familiar with the language in which the contract document uploaded by the first user is written.

[0116] (Appendix 10) A system comprising means for performing all the steps performed in any of the inventions according to appendix 1 to appendix 7. This allows the second user to check the contract document by referring to the translation, even if the second user is not familiar with the language in which the contract document uploaded by the first user is written. [Explanation of symbols]

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

Claims

1. A program for use in a business relating to a contract document to be concluded between a first user and a second user, the program comprising: a processor; and a storage unit, the program being installed in a computer; The processor, a contract receiving step of receiving a contract document relating to a contract from the first user; a presentation step of presenting to the second user a translation of the contract document together with the contract document accepted in the contract acceptance step; A program that executes.

2. The processor, a second presentation step of presenting to the first user the translation of the contract document together with the contract document accepted in the contract acceptance step; Execute The program according to claim 1.

3. The processor, an agreement receiving step of receiving, from the second user, an input operation indicating agreement with the contract document presented in the presentation step; Run The presenting step includes a step of presenting to the second user a screen capable of accepting an input operation indicating agreement in the agreement accepting step. The program according to claim 1.

4. The processor, a term selection step of accepting, from the second user, a selection of a term included in at least one of the contract document and the translation presented to the second user in the presentation step; Run the presenting step includes a step of presenting, in an identifiable manner, a portion of the contract document or the translation that corresponds to the term, based on the term accepted in the term selection step; The program according to claim 1.

5. A program for use in a business relating to a contract document to be concluded between a first user and a second user, the program comprising: a processor; and a storage unit, the program being installed in a computer; The processor, a contract receiving step of receiving a contract document relating to a contract from the first user; a confirmer adding step of adding a third user determined according to a description language of the contract document accepted in the contract accepting step to a confirmer of the contract document; Execute program.

6. The processor, a confirmation receiving step of receiving an input operation from the third user indicating that the third user has confirmed the contract document received in the contract receiving step; a confirmation storage step of storing information indicating a confirmation of the contract document received from the third user in the confirmation receiving step in association with the contract document received in the contract receiving step; Execute The program according to claim 5.

7. The processor, a presentation step of presenting to the third user a translation of the contract document together with the contract document accepted in the contract acceptance step; Run The presenting step includes a step of presenting to the third user a screen capable of accepting an input operation indicating that the confirmation has been made in the confirmation accepting step. The program according to claim 6.

8. A method implemented on a computer having a processor and a memory, the processor performing all of the steps performed in any one of claims 1 to 7.

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

10. A system comprising means for executing all the steps performed in any one of claims 1 to 7.

Images