JP2024002548A - Contract management program, information processing apparatus, information processing system, information processing method, and information processing terminal - Google Patents

Abstract

To store and manage evidence information, such as invoices, receipts, estimates, reports, identity verification documents, or seal certificates, in electronic contract procedures between multiple users, in association with relevant contract information.SOLUTION: A contract management program causes a computer including a processor and a storage unit to store electronic contract procedures between users. The processor executes: a contract storage step of storing contract information; an evidence receiving step of receiving evidence information related to evidence documents; and an evidence storage step of specifying one or more pieces of contract information on the basis of the evidence information received in the evidence receiving step and storing the evidence information in association with the specified one or more pieces of contract information.SELECTED DRAWING: Figure 19

Description

The present disclosure relates to a contract management program, an information processing device, an information processing system, an information processing method, and an information processing terminal.

With the development and spread of computer technology, documents that were previously paper-based are being digitized. For example, it is being considered that documents such as contracts that require the signatures and seals of the parties involved will be managed using electronic data.
Patent Document 1 discloses an information processing system regarding digital contracts that includes a creator terminal, a confirmer terminal, and a contract management server.

JP2017-10096

In electronic contract procedures between multiple users, record and manage evidence information such as invoices, receipts, estimates, reports, identity verification documents, and seal certificates by linking them with related contract information. There are issues that we have not been able to solve.
Therefore, the present disclosure has been made to solve the above-mentioned problems, and the purpose is to store evidence information such as invoices, receipts, estimates, reports, identity verification documents, seal certificates, etc. The purpose is to provide technology that stores and manages information in association with contract information.

A contract management program for storing electronic contract procedures between users in a computer, comprising a processor and a storage unit, the processor having a contract storage step for storing contract information, and a contract storage step for storing voucher information regarding voucher documents. Execute a document reception step in which the document is received, and a document storage step in which one or more contract information is specified based on the document information received in the document reception step, and the document information is stored in association with the identified one or more contract information. Contract management program.

According to the present disclosure, it is possible to store and manage evidence information such as invoices, receipts, estimates, reports, identification documents, and seal certificates in association with related contract information.

1 is a block diagram showing the functional configuration of system 1. FIG. 1 is a block diagram showing the functional configuration of a server 10. FIG. 2 is a block diagram showing the functional configuration of a first user terminal 20. FIG. 3 is a block diagram showing the functional configuration of a second user terminal 30. FIG. 3 is a diagram showing a data structure of a user table 1012. FIG. 3 is a diagram showing the data structure of a group table 1013. FIG. 3 is a diagram showing the data structure of a document table 1014. FIG. 3 is a diagram showing a data structure of a confirmation table 1015. FIG. 3 is a diagram showing the data structure of an input item table 1016. FIG. 3 is a diagram showing the data structure of a contract group table 1017. FIG. 3 is a diagram showing the data structure of a voucher table 1018. FIG. 3 is a flowchart showing the operation of contract creation processing. 3 is a flowchart showing the operation of contract confirmation processing. 3 is a flowchart showing the operation of evidence storage processing. This is an example screen showing the operation of contract creation processing. This is an example of a screen showing a confirmation request message notified to the second user terminal 30. This is an example screen showing the operation of contract confirmation processing. It is an example of a screen showing a conclusion completion message notified to the first user terminal 20. This is an example of a screen for presenting total information regarding evidence information. 2 is a block diagram showing the basic hardware configuration of a computer 90. FIG.

Embodiments of the present disclosure will be described below with reference to the drawings. In all the figures explaining 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 content of the present disclosure described in the claims. Furthermore, not all components shown in the embodiments are essential components of the present disclosure. Furthermore, each figure is a schematic diagram and is not necessarily strictly illustrated.

<System 1 configuration>
A 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 such as 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. As shown in FIG.
FIG. 2 is a block diagram showing the functional configuration of the server 10.
FIG. 3 is a block diagram showing the functional configuration of the first user terminal 20. As shown in FIG.
FIG. 4 is a block diagram showing the functional configuration of the second user terminal 30.

Each information processing device is composed of a computer including 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. Regarding each of the server 10, the first user terminal 20, and the second user terminal 30, explanations that overlap with the basic hardware configuration of the computer and the basic functional configuration of the computer, which will be described later, will be omitted.

<Configuration of server 10>
The server 10 is an information processing device that provides electronic contract conclusion services between multiple 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 section 101 and a control section 104.

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

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

The user table 1012 is a table that stores and manages information about member users (hereinafter referred to as users) who use the service. When a user registers to use a 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 in the present disclosure, users who use services do not necessarily need to be registered in the user table 1012.
The user table 1012 is a table having 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.

The user ID is an item that stores user identification information for identifying a user. The user identification information is an item in which a unique value is set for each user.
The user name is an item that stores the user's name. The user name may be any character string such as a nickname instead of a full name.
The email address is an item that stores the user's email address.
Group ID is an item that stores 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 the user's approval conclusion. For a user who has the authority to approve the conclusion of a contract (authorization authority), information such as True that has the authority to approve the conclusion of the contract is stored. On the other hand, for a user who does not have the authority to approve the conclusion of a contract, information such as False, blank, or a null value that does not have the authority to approve the conclusion of the contract is stored.
A configuration may also be adopted in which approval authority can be set according to contract information. For example, a configuration may be adopted in which user A has approval authority for specific contract information A but does not have approval authority for specific contract information B.
It may also be configured such that approval authority can be set according to the type of contract information (contract information type) such as a non-disclosure agreement, joint research contract, or contract. For example, a configuration may be adopted in which user A has the authority to approve non-disclosure agreements, but not authority to approve contract contracts.
In addition, a configuration may be adopted in which authority information of multiple levels (levels, ranks) is stored depending on the department, government office, etc. to which the user belongs. For example, information such as C for temporary employees, B for general employees, A for managers, and S for executives is stored in the approval authority field, and depending on the contract type information, contract amount, etc., (For example, a configuration may be adopted in which only a user who has approval authority such as A or above for a non-disclosure agreement) can approve the conclusion of a contract.

The group table 1013 is a table that stores and manages information regarding groups to which users belong (group information). The group can be defined as any group to which the user belongs, such as a corporation, company, circle, organization, or department within a company.
The group table 1013 is a table having columns of group ID, group name, and administrator ID, with group ID as the primary key.
FIG. 6 is a diagram showing the data structure of the group table 1013.

Group ID is an item that stores group identification information for identifying a group. Group identification information is an item in which a unique value is set for each group.
Group name is an item that stores the name of the group. Any character string can be set for the group name.
The administrator ID is an item that stores 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 predetermined position or authority in a group such as an organization.

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

The document ID is an item that stores document identification information for identifying contract information. The document identification information is an item in which a unique value is set for each contract information.
Document data is an item that stores contract information (binary or text data). Specifically, the document data includes data in any data format such as PDF (Portable Document Format), Word, and XML (ExtenSible Markup Language).
This item stores the creator ID and user identification information for identifying the user who is the creator of the contract information.
The contract conclusion service name is an item that stores a character string for specifying the external contract conclusion service when the contract information is contract information imported and acquired from an external contract conclusion service. As the contract conclusion service name, the name of an external contract conclusion service, ID information for identifying the contract conclusion service name, etc. may be stored.

The confirmation table 1015 is a table for storing and managing information (confirmer information) including the email address of a user who is a confirmer of contract information.
The confirmation table 1015 is a table having columns of 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.

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

The input item table 1016 is a table that stores and manages information regarding input items (input item information) associated with 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.

The input item ID is an item that stores input item identification information for identifying the input item.
The document ID is an item that stores document identification information of electronic contract information with which an input item is associated.
The input person ID is an item that stores the user identification information or email address of the input person who inputs the input data for the input item. Specifically, the input user ID stores the creator ID, the email address of the user specified by the creator ID, the confirmer email address, and the like.
The input data is an item that stores input data input into an input item by an inputter.
The input rule is an item that stores input rule information regarding input rules for input items. Input rules include data types such as date, datetime, text, and integer, as well as any input items such as the number of characters for strings and regular expressions for strings. Input rule information regarding input rules can be stored.
The date and time is an item that stores the date and time when the input data was input into the input item by the inputter.

The contract group table 1017 is a table for storing and managing information regarding 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, tag, label, etc.
The contract group table 1017 is a table having columns of 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 that stores document identification information for identifying contract information.
The cabinet ID stores cabinet identification information for identifying the cabinet. The cabinet ID is classification information for managing and classifying contract information.

The voucher table 1018 is a table that stores and manages voucher information.
The voucher table 1018 is a table having columns of voucher ID, document ID, voucher image, and additional information.
FIG. 11 is a diagram showing the data structure of the evidence table 1018.

The voucher ID is an item that stores voucher identification information of voucher information.
The document ID is an item that stores document identification information.
The evidence image is an item that stores evidence images related to evidence. The evidence image is an image taken or scanned of the evidence. jpg,. bmp,. Image data in any format such as png can be stored.
Additional information is an item that stores additional information that is stored in association with evidence information.
The additional information includes document type information regarding the type of document specified by the document ID, such as a bill, a receipt, an estimate, a report, an identification document, a seal certificate, and the like.
The additional information includes information input by the user for each type of voucher. For example, if the evidence is a bill, it may include information such as the billing date, billing party, and billing amount. If the evidence is a receipt, it may include information such as the receipt date, payer, and receipt amount. If the voucher is a quotation, it may include information such as the quotation date, quotation amount, and expiration date. If the evidence is a report such as a performance report, it may include information such as the report date, number of units sold, number of units sold, amount of money, etc. If the evidence is an identification document such as a driver's license or health insurance card, it may include information such as the date of issue, expiration date, name, address, and other identification ID. If the evidence is a seal certificate or the like, information such as the date of issue and name may be included.
The additional information does not necessarily need to be input by the user, and the control unit 104 of the server 10 automatically inputs the information based on known machine learning, deep learning, artificial intelligence models, AI models, etc., without input operations by the user. It may also be configured to input. Alternatively, a configuration may be adopted in which the user inputs only part of the additional information, and other information is automatically input.

<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, a contract confirmation unit 1043, and a voucher storage unit 1044. The control unit 104 realizes each functional unit by executing the application program 1011 stored in the storage unit 101.

The user registration control unit 1041 performs a process of storing information of users who wish to use the service according to the present disclosure in the user table 1012.
Information stored in the user table 1012 is transmitted to the server 10 by a user opening a web page operated by a service provider from any information processing terminal, inputting information into a predetermined input form, and transmitting the information to the server 10 . The user registration control unit 1041 stores the received information in a new record of the user table 1012, and the user registration is completed. This allows the users stored in the user table 1012 to use the service.
Prior to the registration of user information in the user table 1012 by the user registration control unit 1041, the service provider may perform a predetermined examination to restrict whether or not the user can use the service.
The user ID may be any character string or number that can identify the user, and may be any character string or number desired by the user, or may be automatically set by the user registration control unit 1041. .

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

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

The evidence storage unit 1044 executes evidence storage processing. 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), a laptop PC, or a mobile terminal such as a smartphone or a tablet. Further, it may be a wearable terminal such as an HMD (Head Mount Display) or a wristwatch type terminal.
The first user terminal 20 includes a storage section 201, a control section 204, an input device 206, and an output device 208.

<Configuration of storage unit 201 of 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 service according to the present disclosure. Note that the first user ID 2011 includes information such as a session ID temporarily given by the server 10 to identify the user using the first user terminal 20.

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

<Configuration of control unit 204 of 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 realizes each functional unit by executing the application program 2012 stored in the storage unit 201.

<Configuration of input device 206 of 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 output device 208 of 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), a laptop PC, or a mobile terminal such as a smartphone or a tablet. Further, it may be a wearable terminal such as an HMD (Head Mount Display) or a wristwatch type terminal.
The second user terminal 30 includes a storage section 301, a control section 304, an input device 306, and an output device 308.

<Configuration of storage unit 301 of 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 service according to the present disclosure to the user. Note that the second user ID 3011 includes information such as a session ID temporarily given by the server 10 to identify the user using the second user terminal 30.

The application program 3012 may be stored in advance in the storage unit 301, or may be downloaded from a web server operated by a service provider via a communication IF.
Application programs 3012 include applications such as web browser applications.
Application program 3012 includes an interpreted programming language, such as JavaScript®, executed on a web browser application stored on second user terminal 30.

<Configuration of control unit 304 of 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 realizes each functional unit by executing the application program 3012 stored in the storage unit 301.

<Configuration of input device 306 of 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 output device 308 of second user terminal 30>
The output device 308 of the second user terminal 30 includes a display 3081 and a speaker 3082.

<Configuration of external server 40>
The external server 40 is an information processing device operated by a business entity different from the business entity that operates the electronic contract conclusion service according to the present disclosure. The external server 40 includes a storage section 401 and a control section 404. Each component included in the external server 40 is the same as each component included in the server 10, so a detailed description thereof will be omitted.

<Configuration of storage unit 401 of external server 40>
The storage unit 401 of the external server 40 includes an application program 4011, a user table 4012, a group table 4013, a document table 4014, a confirmation table 4015, an input item table 4016, and a contract group table 1017.

<Configuration of control unit 404 of external server 40>
The control unit 404 of the external server 40 includes a user registration control unit 4041, a contract creation unit 4042, and a contract confirmation unit 4043. The control unit 404 realizes each functional unit by executing the application program 4011 stored in the storage unit 401.

<Operation of system 1>
Each process of the system 1 will be explained below.
FIG. 12 is a flowchart showing the operation of the contract creation process.
FIG. 13 is a flowchart showing the operation of the contract confirmation process.
FIG. 14 is a flowchart showing the operation of the evidence storage process.
FIG. 15 is an example of a screen showing the operation of the contract creation process.
FIG. 16 is an example of a screen showing a confirmation request message notified to the second user terminal 30.
FIG. 17 is a screen example showing the operation of the contract confirmation process.
FIG. 18 is an example of a screen showing a conclusion completion message notified to the first user terminal 20.
FIG. 19 is an example of a screen showing total information regarding evidence information.

In the present disclosure, contract creation processing and contract confirmation processing in the server 10 will be described below. The external server 40 can also execute similar contract creation processing and contract confirmation processing. The contract creation process and the contract confirmation process in the external server 40 are the same as the contract creation process and the contract confirmation process in the server 10, respectively, so a description thereof will be omitted.

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

FIG. 15 is an example of a screen showing the operation of the contract creation process. A screen 50 for creating contract information displayed on the display 2081 of the first user terminal 20 includes a status 510 indicating the current creation status of contract information, and 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 are displayed.

<Summary of contract creation process>
In the contract creation process, the creator creates electronic contract information, sets a confirmer to be the recipient of the electronic contract information, sets input items for the electronic contract information, sets input rules for the input items, and then the creator This is a series of processes in which input data for input items is received from , and electronic contract information is sent to the set confirmer.

<Details of contract creation process>
The details of the contract creation process will be explained below.

In step S101, the contract creation unit 1042 of the server 10 receives contract information from a creator to be the subject of a contract conclusion with a confirmer. The contract creation unit 1042 executes a contract storage step of storing contract information.
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 contract information can include document data in any data format such as PDF (Portable Document Format), Word, and XML (ExtenSible Markup Language).
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 receives the received first user ID 2011 and document data, and stores them in the creator ID and document data fields of a new record in the document table 1014, respectively. As a result, the contract creation unit 1042 of the server 10 stores new contract information in the document table 1014.

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

In step S102, the first user operates the input device 206 of the first user terminal 20, etc. to select and specify a user who will be the confirmer (receiver) of the contract information. In the present disclosure, it is assumed that the first user selects and specifies the second user as the recipient.
The first user operates the input device 206 of the first user terminal 20 and inputs the e-mail address of the second user who will be the confirmer, and transmits the e-mail address 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 confirmer email address and document ID fields of the confirmation table 1015, respectively, and stores the contract information and the document ID in the confirmation table 1015. It is stored in association with the second user's email address. Note that the first user may set the second user's language and access code, and store them in association with the second user's email address.
At this time, a value of 1 is stored in the confirmation order item of the confirmation table 1015. In step S102, the first user may be able to select and set a plurality of users to be confirmers. In this case, the value of the confirmation order item of the user who is the confirmer is incremented by one and stored in accordance with the selection order. This sets the order of circulation of confirmers in contract confirmation processing, which will be described later. Note that setting the circulation order is not essential.

In step S103, the first user operates the input device 206 of the first user terminal 20 and sets input items for the contract information.
Specifically, 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. Any input items can be set, such as a stamp field for stamping seal data, an input field for entering text data such as signature data, a check box field for selecting check items, and a date field for entering the date. .
The first user operates the input device 206 of the first user terminal 20 and transmits a request to add an input item to the server 10. Upon receiving the request, the contract creation unit 1042 of the server 10 stores the document ID of the contract information in 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. Note that the first user can store a plurality of 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 the input rule for each input item information set in step S103 by operating the input device 206 of the first user terminal 20, and transmits it to the server 10. The contract creation unit 1042 of the server 10 stores the received input rule in the input rule field of each input item information record in the input item table 1016. This allows input rules to be set for each input item.

In step S105, the contract creation unit 1042 of the server 10 receives input data for a plurality of input items input by the first user.
Specifically, the first user inputs input data for each input item set in step S104 by operating the input device 206 of the first user terminal 20 or the like. For example, the first user may input input data of a number for managing contract information such as a reference number for a group to which the first user belongs to an input item set with a management number. The first user may input input data of the contract conclusion date of the contract information into the input item in which the contract conclusion date is set. When the first user completes inputting the input data to 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 input 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 regarding the contract information.
Specifically, the first user transmits the contract information by operating the input device 206 of the first user terminal 20 and pressing the send button 540 displayed on the screen 50 for creating contract information. Send the request 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 the first user has sent a request to confirm the contract information. Specifically, the contract creation unit 1042 of the server 10 searches the confirmation order item in the confirmation table 1015, and selects the user (first confirmation user) who is the first confirmer with the smallest value stored in the confirmation order item. Identify. In the present disclosure, the first confirmed user is, for example, the second user. The contract creation unit 1042 of the server 10 sends a message to the second user's e-mail address, using communication means such as e-mail, to notify that the first user has sent a request to confirm the contract information.
The message notified to the second user includes URL (Uniform Resource Locator) information including a document ID for specifying 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 other character strings that can identify the document ID by referring to a table (not shown). good. Further, the URL may include information for identifying the second user. For example, if the second user has not registered for the service according to the present disclosure, it is necessary to include information for identifying the second user in the URL.

When the first user sets an access code for the second user, the first user separately conveys the access code to the second user by means such as e-mail. As a result, even if a third party obtains the message to be notified to the second user, the third party cannot execute the contract confirmation process unless the third party obtains the access code.

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

<Modified example>
When the first user selects and sets a plurality of confirmers in step S102, the first user may be configured to be able to independently set different input item information in step S103 for each of the plurality of confirmers. do not have. For example, when the first user sets two users, the second user and the ninth user, as confirmers, the input items for the contract start date and contract end date are set for the second user, and the contract is concluded. The input item for the day may be set for the ninth user. In this case, in the contract confirmation process described later, the second user can enter input data for the input fields of the contract start date and contract end date, but input data for the input field of the contract conclusion date. Can not do it. On the other hand, the ninth user cannot input data to the input items for the contract start date and contract end date, but can input input data for the input item for the contract conclusion date. A configuration may be adopted in which a plurality of confirmers can be selected and set in duplicate for one piece of input item information.

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

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

<Summary of contract confirmation process>
The contract confirmation process accepts access from the confirmer, presents the confirmer with a confirmation screen that displays contract information, receives input data for input items from the confirmer, and receives data related to confirming the contract information from the confirmer. This is a series of processes for accepting requests.

<Details of contract confirmation process>
The details of the contract confirmation process will be explained below.

In step S301, the second user who is the confirmer operates the input device 306 of the second user terminal 30 and selects the URL written in the received message, thereby using the browser application of the second user terminal 30. A web page specified by the URL can be opened. Thereby, the second user terminal 30 transmits a request to the server 10 to execute the contract confirmation process.

If the access code item is stored in the second user's record in the confirmation table 1015, the second user is requested to input the access code, and the entered access code and the second user's record in the confirmation table 1015 are By comparing the access code stored in the user's record, it is possible to perform 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, inputs the access code, and transmits 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, executes contract confirmation processing. continue. On the other hand, if they do not match, the contract confirmation process is canceled. 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 acquires 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 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 input item information associated with the contract information.

In step S302, the contract confirmation unit 1043 of the server 10 identifies the second user and acquires the second user's approval authority information. 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 the identification information for identifying the second user included in the URL. good. If the second user has not registered for 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 second user's email address, user ID, etc. as information for identifying the second user.

The contract confirmation unit 1043 of the server 10 searches the user ID item in the user table 1012 based on the user identification information of the specified second user, and acquires the second user's approval authority item. Note that in this disclosure, the second user's approval authority is stored in the user table 1012, but the second user's approval authority may be stored for each group to which the second user belongs, or may be stored for each group to which the second user belongs. It may be stored for each information or for each contract information type. The contract confirmation unit 1043 of the server 10 acquires the second user's approval authority information for the target contract information.
Further, if the second user has not registered as a user in the service according to the present disclosure, the process may be executed by regarding the second user as a user who does not have approval authority.

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), input item information, and confirmer approval authority information. 2 to the user terminal 30.

Specifically, the display 3081 of the second user terminal 30 presents the second user with a confirmation screen that accepts an operation to approve the contract information. The second user confirms and approves the contract information displayed on the display 3081 of the second user terminal 30.
Note that the confirmation screen presented to the second user is based on the language information stored in the language data item of the second user's record in the confirmation table 1015, and is displayed in the language specified for the confirmer by the second user. It is also possible to have a configuration in which the information is presented to the user.

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

Specifically, if the second user's approval authority information obtained in step S302 includes information that has the authority to approve the conclusion of the contract, the contract confirmation unit 1043 of the server 10 determines whether the second user has accepted the agreement. It is determined that the user is capable of approving the conclusion of the contract based on the contract information, a confirmation screen is presented to the second user, and the process proceeds to step S304.

On the other hand, if the second user is a user who cannot approve the conclusion of the contract based on the received contract information, the contract confirmation process ends.

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

In step S305, the contract confirmation unit 1043 of the server 10 receives an instruction from the second user to agree to and approve the conclusion of the contract based on the contract information received from the first user.
The second user confirms the contract information and input data displayed on the display 3081 of the second user terminal 30, and when agreeing or consenting to the contents, operates the input device 306 of the second user terminal 30, etc. By pressing the consent button 740 displayed on the confirmation screen 70 for confirming the contract information, a request including the document ID, information identifying the second user, and input data for each input item input in step S305 is sent. The process of transmitting to the server 10 is executed. 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 specifying the second user, and stores a value of True in the confirmation flag field of the record. For example, if the information specifying the second user is an email address, the document ID and confirmer email address items in the confirmation table 1015 are searched, and a value of True is stored in the confirmation flag item of the record. If the information that identifies the second user is user identification information, the document ID and confirmation information in the confirmation table 1015 are determined based on the email address of the second user identified by searching the user ID item in the user table 1012. The user's email address field is searched, and a value of True is stored 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. Thereby, in step S305, the input data input by the second user is stored as input item information in the input item table 1016.

The contract confirmation unit 1043 of the server 10 determines that the contract confirmation process has been executed by all confirmers having approval authority. Specifically, if a value of True is stored in the confirmation flag of the record of the confirmer who has approval authority in the confirmation table 1015, the contract confirmation unit 1043 of the server 10 performs the contract check by all confirmers who have approval authority. It is determined that the contract confirmation process has been executed. That is, the determination is made while ignoring the value of the confirmation flag of the record of a confirmer who does not have approval authority.
When the contract confirmation process is executed by all the confirmers having approval authority, the contract confirmation unit 1043 of the server 10 sends a message to the first user notifying that the contract confirmation process is completed. Note that, similarly, the contract confirmation unit 1043 of the server 10 may send a message to the second user notifying that the contract confirmation process has been completed.

Specifically, the contract confirmation unit 1043 of the server 10 sends a message to the first user's email address to notify that the second user has completed confirmation of the contract information, using a communication means such as email. That is, 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 contract has been concluded with the second user.
The message to be notified to the first user may include information on a URL that is an endpoint that includes a document ID for specifying contract information.

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

Similarly, the contract confirmation unit 1043 of the server 10 sends a message notifying that the second user has completed confirmation of the contract information, including a mention to the first user, using a chat service (not shown) or the like. You may do so. That is, 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 contract has been concluded with the second user.
The message to be notified to the first user may include information on a URL that is an endpoint that includes a document ID for specifying contract information.
Note that chat services include Slack, chatwork, Microsoft Teams, LINE WORKS, and the like.

The first user can use the browser application of the first user terminal 20 to open the web page specified by the URL included in the received message. 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 sends it to the first user terminal 20. The first user can obtain the document data included in the contract information by downloading or the like from the web page screen displayed on the display 2081 of the first user terminal 20.

If multiple users are set as confirmers, the contract confirmation unit 1043 of the server 10 informs the user other than the last user who executed the contract confirmation process that the contract confirmation process has been completed. You may also send a message to notify you. Thereby, the user corresponding to the confirmer can also receive a notification that execution of the contract confirmation process has been completed by all confirmers.
Further, the contract confirmation unit 1043 of the server 10 may send a message notifying that the contract confirmation process has been completed to a user who has authority equivalent to an administrator in a group to which a plurality of confirmers belong.
Note that the message may be sent via email, chat service, or the like. In addition to email, email also includes message services such as SMS (Short Message Service) that are sent via a telephone number.
Thereby, the administrator of the group to which the user who is the confirmer belongs can receive notification that execution of the contract confirmation process has been completed.

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 of the group table 1013 based on the acquired group ID item, acquires the administrator ID item, and, based on the administrator ID, identifies the person who corresponds to the administrator. An authorized user is identified by searching the user ID in the user table 1012, and a message is sent to notify that the contract confirmation process has been completed.

<Electronic signature processing>
Step S305 may include electronic signature processing. In response to the instruction to approve the contract conclusion received from the second user in step S305, the contract confirmation unit 1043 of the server 10 indicates, in the contract information received from the first user, that the contract conclusion of the contract information is approved. Add and store an electronic signature.
Specifically, the contract confirmation unit 1043 of the server 10 adds and stores an electronic signature to the contract information based on the received request. The contract confirmation unit 1043 of the server 10 searches the document ID item in the document table 1014 based on the document ID and acquires contract information.
The contract confirmation unit 1043 of the server 10 adds an electronic 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) items of document data with the contract information to which the electronic signature has been added, or may store the contract information before the electronic signature has been added in a separate storage device (not shown). I don't mind if you do.
The contract confirmation unit 1043 of the server 10 includes the document ID, the first user's email address, the second user's email address, approval date and time, confirmation date and time, authentication method of approval date and time, authentication method of confirmation date and time, and input items in the electronic signature. Any information such as the value of input data for each user, consent (approval) of the first user and second user, and a time stamp may be included.
As a result, the contract confirmation unit 1043 of the server 10 stores the contract information with an electronic signature indicating that the second user has approved the conclusion of the contract information. It is possible to prevent impersonation or falsification of contract information by a third party.

<Contract management processing>
The contract management process is a process of acquiring, storing, and managing contract information stored in an external electronic contract service.

<Overview of contract management processing>
The contract management process is a process in which an e-mail indicating that a contract conclusion has been completed in an external electronic contract service is received, contract information attached to the e-mail is received, and the information is stored in association with the external electronic contract service.

<Details of contract management processing>
By operating the input device 206 of the first user terminal 20, the first user receives an email containing a message notifying that the contract confirmation process is completed, which was received from the external server 40 in step S305 of the contract confirmation process. will be forwarded to a predetermined email address for executing contract management processing according to the present disclosure.
Document data of the contract information for which contract confirmation processing has been completed in the external server 40 may be attached to the message. The message may include an endpoint such as a URL for specifying contract information for which contract confirmation processing has been completed in the external server 40.

The control unit 104 of the server 10 acquires contract information stored in one or more external contract management servers, and stores the acquired contract information in association with the one or more external contract management servers.
Specifically, the control unit 104 of the server 10 receives and receives document data attached to a message. Furthermore, if the message includes an endpoint for specifying contract information in the external server 40, the endpoint is accessed, document data is acquired, and the document data is accepted.
The control unit 104 of the server 10 associates the received document data with the contract conclusion service name specified based on the external server 40 and stores it in the document data and contract conclusion service name fields of the document table 1014. Note that the document ID is automatically incremented and numbered.

<Evidence memory processing>
The evidence storage process is a process of storing evidence information received from the user. In the present disclosure, evidence storage processing using the first user terminal 20 will be described as an example, but the evidence storage processing may be configured to be executed from any information processing terminal other than the second user terminal 30. Further, a configuration may be adopted in which any user other than the first user and the second user can execute the process.

<Overview of evidence memory processing>
Voucher storage processing is a series of processes that accepts voucher information from the user, identifies the contract information that is the basis of the voucher information, presents the user with an input screen according to the voucher information, and stores the voucher information in association with the contract information. It is.

<Details of evidence memory processing>
The details of the evidence storage process will be explained below.

In step S501, the voucher storage unit 1044 executes a voucher reception step for receiving voucher information regarding voucher documents. The evidence receiving step is a step of receiving evidence information from a user via a communication means.
Specifically, the first user starts the mail application stored in the storage unit 201 of the first user terminal 20. The first user creates a new email by operating the input device 206 of the first user terminal 20, and documents such as invoices, receipts, estimates, reports, identification documents, and seal certificates. Attach evidence data such as PDF, Word, XML files, etc. in which the information is stored.
The first user operates the input device 206 of the first user terminal 20 to send a newly created email with the evidence data attached to a predetermined email address from which the server 10 receives the evidence data. An e-mail sent to a predetermined e-mail address is received and stored at a predetermined mail server that can be referenced by the server 10. The evidence storage unit 1044 of the server 10 accesses the mail server, obtains the email with the evidence data attached, and accepts the evidence data.

Note that the evidence does not necessarily have to be attached to the e-mail, and the e-mail may include a URL for acquiring the evidence, and the evidence data can be obtained by accessing the URL. In that case, the evidence storage unit 1044 of the server 10 acquires and accepts the evidence data by accessing the URL written in the received email.

In addition, if the first user receives an email with evidence data attached from an external billing service, etc., the first user should create a new email by duplicating the email and send the email with the evidence data attached. The server 10 transfers the document data to a predetermined e-mail address for receiving the document data.

In this case, the email application stored in the storage unit 201 of the first user terminal 20 may include an extended function (referred to as an add-on, an add-in, a plug-in, etc.) for transferring evidence information. In this case, an "evidence transfer button" for transferring the selected e-mail to the server 10 is displayed on the e-mail application screen.
The first user selects the email to be forwarded by operating the input device 206 of the first user terminal 20, and presses the "evidence transfer button" displayed on the email application screen to attach the evidence data. The server 10 can forward the received email to a predetermined email address for receiving the evidence data.
Thereby, the first user can forward the email with the evidence data attached to the predetermined email address from which the server 10 receives the evidence data, without having to input the address of the email. In other words, input errors by the first user can be prevented.
Note that an email containing evidence data that has already been transferred to the server 10 may not be selected as an email to be transferred. Similarly, the "evidence transfer button" displayed on the email application screen may not be pressed for emails that include evidence data that has already been transferred to the server 10. Thereby, it is possible to prevent the same evidence data from being sent redundantly to the server 10.

The means of communication does not have to be email, and any chat service may be used. The first user starts the browser application on the first user terminal 20 and accesses a predetermined chat service. By operating the input device 206 of the first user terminal 20, the first user creates and sends a new message with the evidence data attached and the server 10 as the destination (mention). The evidence storage unit 1044 of the server 10 detects that a message has been received from the chat service, acquires and accepts the evidence data by accessing the chat service.

In step S502, the evidence storage unit 1044 of the server 10 executes a contract specifying step of specifying one or more pieces of contract information that are the basis of the evidence information received in the evidence receiving step.
Specifically, the evidence storage unit 1044 of the server 10 analyzes character strings, image data, etc. included in the evidence data, and specifies document identification information such as the document ID of the contract information that is the basis of the evidence data. For example, if the evidence data is in PDF format, a character string such as "contract number: ○○○○" included in the data is identified, and the contract number "○○○○" is identified and used as the document ID. Identify. Note that the evidence storage unit 1044 of the server 10 may identify the document ID by referring to a table (not shown) in which contract numbers and document IDs are linked.
Note that the document ID may be specified by the first user's input operation based on the evidence data. Further, document IDs of trademark data having similar character strings, image data, etc. may be specified with reference to evidence data, document IDs, etc. specified by the first user in the past.

The contract identifying step includes identifying one or more pieces of contract information based on text information included in a message including evidence information received via the communication means.
Specifically, the evidence storage unit 1044 of the server 10 specifies document identification information such as the document ID of the contract information that is the basis of the evidence data by analyzing text information such as the subject and body of the email. For example, character strings such as "contract number: ○○○○" included in the subject and text of the email are identified, and the contract number "○○○○" is identified and specified as the document ID.
Similarly, when receiving voucher data via a chat service, by analyzing text information such as the message body to which the voucher data is attached, the document ID such as the document ID of the contract information that is the basis of the voucher data is identified. Identify information.

The method for identifying the document ID from the evidence data is not limited to the above method, and may be configured to infer the document ID using any inference model, machine learning model, deep learning model, artificial intelligence model, etc.

In step S503, the control unit 204 of the first user terminal 20 executes an input presentation step of presenting an input screen for inputting input information to the user, based on the evidence information received from the user.
Specifically, the evidence storage unit 1044 of the server 10 sends an email containing the URL of the input screen to the first user terminal 20 after the process of step S502 is completed. The first user selects the URL written in the email by operating the input device 206 of the first user terminal 20, and opens an input screen using the browser application.
Note that the evidence storage unit 1044 of the server 10 may send an email to the first user terminal 20 in which the URL of a different input screen is written for each type of evidence. In this case, the input screen displayed on the display 2081 of the first user terminal 20 is a different input screen for each type of voucher. For example, the following examples can be considered.
If the evidence data is an invoice, an input screen for entering the invoice date and invoice amount is displayed.
If the evidence data is a receipt, an input screen for entering the date of receipt, payer, and amount of receipt is displayed.
If the evidence data is an estimate, an input screen for entering the estimate date, estimate amount, and expiration date is displayed.
If the evidence data is a report such as a performance report, an input screen is displayed for entering the report date, number of units sold, number of units sold, and amount of money.
If the evidence data is an identification document such as a driver's license or health insurance card, an input screen for entering the date of issue, expiration date, name, address, and other identification ID is displayed.
If the evidence data is a seal certificate or the like, an input screen for entering the date of issue and name is displayed.
The first user inputs input data on the input screen displayed on the display 2081 of the first user terminal 20 and transmits it to the server 10.

In step S504, the evidence storage unit 1044 executes an evidence storage step in which the evidence information is stored in association with the one or more pieces of contract information specified in the contract identification step. The evidence storage step includes a step of storing the input information input via the screen in association with the evidence information.
Specifically, the evidence storage unit 1044 of the server 10 stores the acquired evidence data, the document ID specified in step S502, and the input data input by the first user in step S503 as the evidence image, document ID, and document ID of the evidence table 1018, respectively. It is stored in association with the additional information item. Note that the voucher ID is automatically incremented and numbered.

In step S504, the voucher storage step performs a step of storing the voucher information stored in the voucher storage step together with one or more pieces of contract information by adding an electronic signature to the voucher information.
Specifically, the evidence storage unit 1044 of the server 10 searches the document ID item of the document table 1014 based on the document ID specified in step S502 in the document table 1014, and acquires the contract information.
The evidence storage unit 1044 of the server 10 adds an electronic signature to the acquired contract information including information on the received evidence data, and stores it in the document data item of the document table 1014. Note that the evidence storage unit 1044 of the server 10 may update (overwrite) items of document data with contract information including voucher data to which an electronic signature has been attached, or store contract information (not shown separately) before including voucher data. It is also possible to store it in the storage device.

In step S504, the evidence receiving step includes a step of identifying one or more external contract management servers associated with one or more pieces of contract information identified based on the voucher information.
Specifically, the evidence storage unit 1044 of the server 10 searches the document ID in the document table 1014 based on the document ID specified in step S502, and obtains and specifies the contract conclusion service name item. Thereby, the evidence storage unit 1044 of the server 10 can specify one or more external contract conclusion services associated with the contract information specified based on the evidence data received in step S501. The evidence storage unit 1044 of the server 10 acquires the end point (URL) of the external contract management server (external server 40) by referring to a table (not shown) or the like based on the acquired external contract conclusion service name. The endpoint is, for example, a URL of an API (Application Programming Interface) provided by the external server 40, and by sending a predetermined request to the external server 40, it is possible to cause the external server 40 to execute a predetermined process. can.

In step S504, the voucher storage unit 1044 executes a sending step of transmitting a request to the identified one or more external contract management servers to store the voucher information in association with the contract information.
Specifically, the voucher storage unit 1044 of the server 10 transmits a request to the acquired endpoint of the external server 40 to store voucher data including the document ID and voucher data in association with the contract information.
Note that, for equivalent contract information, the document ID in the server 10 and the document ID in the external server 40 are usually different numbers or character strings. Therefore, when contract information is imported from an external contract conclusion service through contract management processing, the evidence storage unit 1044 of the server 10 stores document identification information for identifying the contract information in the external contract conclusion service. The document identification information, which is stored in advance in association with the document ID in table 1014 and is used to identify the contract information in the external contract conclusion service, is included in the request for storing the voucher data in association with the contract information. be able to. Note that in this disclosure, for the sake of explanation, the document ID in the server 10 and the document ID in the external server 40 of the same contract information are treated without distinction.
Upon receiving the request, the control unit 404 of the external server 40 searches the document ID in the document table 4014 based on the document ID included in the received request, identifies the contract information record, and identifies the contract information record with the identified contract information. It is stored in association with evidence data.
Thereby, the first user can automatically perform association in an external contract management service by simply transmitting evidence information to the contract management service. In other words, even if the first user uses many external contract management services, the first user can conveniently associate evidence information with contract information and manage it in a unified manner.

<Evidence aggregation process>
The evidence aggregation process is a process of aggregating the evidence information stored in the evidence storage process and presenting it to the user. In the present disclosure, evidence aggregation processing using the first user terminal 20 will be described as an example, but the evidence aggregation process may be configured to be executed from any information processing terminal other than the second user terminal 30. Further, a configuration may be adopted in which any user other than the first user and the second user can execute the process.

<Summary of evidence aggregation process>
The evidence aggregation process is a series of processes that acquires the evidence information stored in the evidence table 1018 through the evidence storage process, calculates the aggregation information for each associated contract information, and presents the calculated aggregation information to the user.

<Details of evidence aggregation processing>
A totalizing step is executed to calculate total information regarding one or more pieces of evidence information associated with each one or more pieces of contract information identified in the evidence storage step.
Specifically, the first user starts the browser application stored in the storage unit 201 of the first user terminal 20, inputs the URL for executing the evidence aggregation process, and opens the evidence aggregation page. The control unit 204 of the first user terminal 20 transmits a request to the server 10 to execute the evidence aggregation process.
The control unit 104 of the server 10 refers to the evidence table 1018 and obtains a plurality of evidence IDs, document IDs, and additional information items. The control unit 104 of the server 10 adds up additional information such as the number of voucher IDs (number of voucher information), billed amount, received amount, and estimated amount included in the additional information for each unique document ID that does not overlap, and calculates the document ID. Calculate the total billed amount, received amount, estimated amount, etc. for each item. Note that the control unit 104 of the server 10 may calculate the total amount of billed amounts, received amounts, estimated amounts, etc. for each predetermined period such as half a year, one year, three years, etc.
The control unit 104 of the server 10 transmits the calculated total information to the first user terminal 20.

The control unit 204 of the first user terminal 20 executes a presentation step of presenting the total information calculated in the totalization step.
Specifically, the input device 206 of the first user terminal 20 receives aggregated information regarding the evidence information received from the server 10, displays it via a display device such as the display 2081 of the first user terminal 20, and displays the aggregated information regarding the evidence information received from the server 10. present aggregated information.

FIG. 20 is an example of a screen displaying aggregated information regarding evidence information displayed on the display 2081 of the first user terminal 20. The screen D10 presented to the first user displays the contract name for specifying contract information, document IDs IDD101 and IDD111, and the number of pieces of voucher information for each voucher type D102 and D104 as aggregate information regarding voucher information associated with the document IDs. , D112, D114, if the evidence type is an invoice, etc., the total billed amount D103, D113, which is the sum of the billed amounts for each multiple invoices; if the evidence type is a receipt, etc., the total billed amount It includes the total receipt amount D105 and D115, which are the sum of the receipt amounts for each receipt.

<Basic hardware configuration of the computer>
FIG. 20 is a block diagram showing the basic hardware configuration of the 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 an instruction set written in a program. The processor 901 includes an arithmetic unit, registers, peripheral circuits, and the like.

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

The auxiliary storage device 903 is a storage device for storing data and programs. Examples include flash memory, HDD (Hard Disc Drive), magneto-optical disk, CD-ROM, DVD-ROM, and semiconductor memory.

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 various mobile communication systems constructed using the Internet, LAN, wireless base stations, and the like. For example, the network includes 3G, 4G, 5G mobile communication systems, LTE (Long Term Evolution), a wireless network (for example, Wi-Fi (registered trademark)) that can be connected to the Internet through a predetermined access point, and the like. When connecting wirelessly, communication protocols include, for example, Z-Wave (registered trademark), ZigBee (registered trademark), Bluetooth (registered trademark), and the like. In the case of a wired connection, the network includes a network that is directly connected using a USB (Universal Serial Bus) cable or the like.

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

<Basic functional configuration of computer 90>
The functional configuration of the computer realized by the basic hardware configuration of the computer 90 (FIG. 20) will be described. The computer includes at least functional units of a control section, a storage section, and a communication section.

Note that the functional units included in the computer 90 can also be implemented by distributing all or part of each functional unit to a plurality of computers 90 interconnected via a network. The computer 90 is a concept that 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, loading them into the main storage device 902, and executing processing according to the programs. The control unit can implement a functional unit that performs various information processing depending on the type of program. Thereby, 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. Further, 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 according to the program. Further, the control unit can cause the processor 901 to execute processing for adding, updating, and deleting data stored in the storage unit according to various programs.

A database refers to a relational database, which is used to manage a data set called a master, which is a tabular table whose structure is defined by rows and columns, in relation to each other. In a database, a table is called a table or a master, a table column is called a column, and a table row is called a record. In a relational database, you can set and associate relationships between tables and masters.
Usually, each table and each master is set with a column that serves as a primary key to uniquely identify a record, but it is not essential to set a primary key on a column. The control unit can cause the processor 901 to add, delete, or update records to a specific table or master stored in the storage unit according to various programs.

Note that the database and master in the present disclosure may include any data structure (list, dictionary, associative array, object, etc.) in which information is structurally defined. Data structures include data that can be considered as a data structure by combining data with functions, classes, methods, etc. written in any programming language.

The communication unit is realized by a 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 it to the control unit. The control unit can cause the processor 901 to execute information processing on the received information according to various programs. Further, the communication unit can transmit information output from the control unit to another computer 90.

<Additional notes>
The matters explained in each of the above embodiments are additionally described below.

(Additional note 1)
A contract management program for storing electronic contract procedures between users in a computer, comprising a processor and a storage unit, the processor includes a contract storage step (S101) for storing contract information, and a contract storage step (S101) for storing contract information; A voucher reception step (S501) that receives voucher information; and a voucher storage that specifies one or more pieces of contract information based on the voucher information received in the voucher information and stores the voucher information in association with the specified one or more pieces of contract information. A contract management program that executes step (S504).
As a result, evidence information such as invoices, receipts, estimates, reports, identification documents, and seal certificates can be stored and managed in association with related contract information. A contract management service that is convenient for users can be realized.

(Additional note 2)
The evidence storage step (S504) is a step of identifying one or more pieces of contract information that is the basis of the evidence information received in the evidence receiving step, and storing the evidence information in association with the identified one or more pieces of contract information. Contract management program described in Appendix 1.
This makes it possible to store and manage evidence information such as invoices, receipts, estimates, reports, personal identification documents, and seal certificates in association with the underlying contract information. A contract management service that is convenient for users can be realized.

(Additional note 3)
The contract management program according to appendix 1, wherein the evidence information is at least one of an invoice, a receipt, an estimate, a report, an identification document, and a seal certificate.
As a result, evidence information such as invoices, receipts, estimates, reports, identification documents, and seal certificates can be stored and managed in association with related contract information.

(Additional note 4)
The processor includes a totaling step of calculating aggregate information regarding one or more pieces of evidence information associated with each one or more pieces of contract information identified in the evidence storage step, and a presenting step of presenting the total information calculated in the totaling step. The contract management program described in Appendix 1 that executes.
Thereby, the user can receive the presentation of aggregated information regarding the evidence information, and can easily check the aggregated information for each contract information. For example, it is possible to check the aggregated results of billed amounts, received amounts, etc. for each contract. The user can conveniently check contract information.

(Appendix 5)
The contract management program according to appendix 1, wherein the evidence storage step (S504) is a step of storing the evidence information stored in the evidence storage step together with one or more pieces of contract information with an electronic signature attached thereto.
This allows the evidence information to be stored in association with the underlying contract information. It is possible to prevent falsification of contract information and evidence information.

(Appendix 6)
In the contract management program according to supplementary note 1, the evidence receiving step (S501) is a step of receiving evidence information from a user via a communication means.
This allows evidence information included in messages received from users via email, chat, etc. to be stored and managed in association with related contract information. For example, documents containing evidence information can be accepted as attachments to emails, chats, etc., and can be stored and managed in association with related contract information.

(Appendix 7)
The evidence storage step (S504) includes the step of specifying one or more pieces of contract information based on the text information included in the message containing evidence information received via the communication means in the evidence reception step, contract management described in Appendix 6. program.
Thereby, contract information can be specified more accurately based on the content of text information such as the email body included in an email received from a user or a chat message. For example, the text information may include a character string or the like for specifying contract information.

(Appendix 8)
The processor executes an input presentation step (S503) of presenting a screen for inputting input information to the user based on the evidence information received from the user, and the evidence storage step (S504) executes an input presentation step (S503) of presenting a screen for inputting input information to the user. 6. The contract management program according to appendix 6, comprising the step of storing input information inputted in association with voucher information.
Thereby, input information regarding evidence such as billed amount and receipt amount can be accepted and stored in association with the evidence information. Thereby, the additional information can be stored in association with the evidence information.

(Appendix 9)
The contract storage step is a step of acquiring contract information stored in one or more external contract management servers, and storing the acquired contract information in association with one or more external contract management servers, as described in Appendix 1. program.
As a result, even if the user is using another external contract management service, the contract information obtained from the external contract management service can be stored, and the received evidence information can be associated with the contract information. Can be memorized. The user can centrally manage contract information in the contract management service according to the present disclosure, including contract information concluded in other external contract management services.

(Appendix 10)
The processor identifies one or more external contract management servers based on the voucher information received in the voucher reception step, and stores the voucher information in association with the contract information in the identified one or more external contract management servers. The contract management program according to supplementary note 1, which executes the sending step (S502) of sending a request for.
If the user uses multiple external contract management services, it is necessary to identify which external contract management service stores the contract information that is the basis of the evidence in hand, which may be inconvenient. It was low. In the present disclosure, the user only needs to send evidence information to the contract management service, and association in an external contract management service can be automatically performed. In other words, even when a user uses many external contract management services, the user can conveniently associate evidence information with contract information and manage it in an integrated manner.

(Appendix 11)
The evidence receiving step (S504) includes a step of identifying one or more external contract management servers associated with the one or more contract information identified based on the evidence information, and the sending step (S504) includes the step of identifying one or more external contract management servers associated with the identified one or more contract information based on the evidence information. The contract management program according to appendix 10, including the step of transmitting a request to a plurality of external contract management servers to store voucher information in association with contract information.
As a result, the user can automatically perform association in an external contract management service by simply transmitting evidence information to the contract management service. The user can conveniently store and manage evidence information in association with contract information.

(Appendix 12)
An information processing apparatus comprising a processor and a storage unit, wherein the processor executes a contract management program according to any one of Supplementary Notes 1 to 11.
As a result, evidence information such as invoices, receipts, estimates, reports, identification documents, and seal certificates can be stored and managed in association with related contract information.

(Appendix 13)
An information processing system including an information processing device including a processor and a storage unit, wherein the processor executes a contract management program according to any one of Supplementary Notes 1 to 11.
As a result, evidence information such as invoices, receipts, estimates, reports, identification documents, and seal certificates can be stored and managed in association with related contract information.

(Appendix 14)
An information processing method executed by a computer including a processor and a storage unit, the computer executing a contract management program according to any one of appendices 1 to 11.
As a result, evidence information such as invoices, receipts, estimates, reports, identification documents, and seal certificates can be stored and managed in association with related contract information.

(Appendix 15)
An information processing terminal comprising a processor, a storage unit, and a display device, an acquisition step in which the processor acquires the total information calculated in the presentation step from an information processing device that executes the contract management program described in Appendix 4. and a presentation step of presenting the total information acquired in the acquisition step by displaying it on a display device.
As a result, evidence information such as invoices, receipts, estimates, reports, identification documents, and seal certificates can be stored and managed in association with related contract information. A contract management service that is convenient for users can be realized.

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 (15)

A contract management program for storing electronic contract procedures between users in a computer, comprising a processor and a storage unit,
The processor includes:
a contract storage step for storing contract information;
an evidence reception step for receiving evidence information regarding the evidence document;
a voucher storage step of specifying one or more pieces of contract information based on the voucher information received in the voucher receiving step, and storing the voucher information in association with the specified one or more contract information;
A contract management program that runs The evidence storage step is a step of identifying one or more pieces of contract information that is the basis of the evidence information received in the evidence receiving step, and storing the evidence information in association with the identified one or more pieces of contract information. be,
The contract management program according to claim 1. The evidence information is at least one of a bill, a receipt, an estimate, a report, an identification document, and a seal certificate;
The contract management program according to claim 1. The processor includes:
an aggregation step of calculating aggregate information regarding one or more pieces of evidence information associated with each of the one or more pieces of contract information identified in the evidence storage step;
a presentation step of presenting the aggregated information calculated in the aggregating step;
execute,
The contract management program according to claim 1. The evidence storage step is a step of storing the evidence information stored in the evidence storage step together with the one or more contract information with an electronic signature added thereto.
The contract management program according to claim 1. The evidence receiving step is a step of receiving the evidence information from the user via a communication means.
The contract management program according to claim 1. The evidence storage step includes a step of identifying the one or more pieces of contract information based on text information included in the message containing the evidence information received via the communication means in the evidence reception step.
The contract management program according to claim 6. The processor includes:
an input presentation step of presenting a screen for inputting input information to the user based on the evidence information received from the user;
Run
The evidence storage step includes a step of storing the input information input through the screen in association with the evidence information.
The contract management program according to claim 6. The contract storage step is a step of acquiring contract information stored in one or more external contract management servers, and storing the acquired contract information in association with the one or more external contract management servers.
The contract management program according to claim 1. The processor includes:
One or more external contract management servers are identified based on the evidence information received in the evidence acceptance step, and the evidence information is stored in association with the contract information in the identified one or more external contract management servers. a sending step of sending a request to
execute,
The contract management program according to claim 1. The evidence receiving step includes a step of identifying the one or more external contract management servers associated with the one or more contract information identified based on the evidence information,
The sending step includes sending the request for storing the evidence information in association with the contract information to the specified one or more external contract management servers.
The contract management program according to claim 10. An information processing device comprising a processor and a storage unit,
The processor executes the contract management program according to any one of claims 1 to 11.
Information processing device. An information processing system including an information processing device including a processor and a storage unit,
The processor executes the contract management program according to any one of claims 1 to 11.
Information processing system. An information processing method executed by a computer comprising a processor and a storage unit,
The computer executes the contract management program according to any one of claims 1 to 11.
Information processing method. An information processing terminal comprising a processor, a storage unit, and a display device,
The processor,
an acquisition step of acquiring the total information calculated in the presentation step from an information processing device that executes the contract management program according to claim 4;
a presenting step of presenting the total information acquired in the acquiring step by displaying it on the display device;
An information processing terminal that executes.