Online contract system and program

Abstract

To provide an online contract system and a program that can easily redo contract conclusion even if there is an error in a completion process of contract data at a receiving side.SOLUTION: In an online contract system and a program, a contract server 1 duplicates contract data and stores duplicated contract data when transmitting the contract data to a receiving side terminal 3, when a return instruction requesting correction of completed contract data from a transmitting side is input at a transmitting side terminal 2, transmits a correction instruction message from the transmitting side terminal 2 and the duplicated contract data to the receiving side terminal 3, and performs re-request to redo contract conclusion.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] The present invention relates to an online contract system, and particularly to an online contract system and a program that can easily re-conclude a contract.

Background Art

[0002] [Conventional Technology] In a conventional online contract system using the cloud, the sender, who is one of the parties to the contract conclusion, creates electronic contract document data on the cloud, transmits the contract document data to the receiver, who is the other party to the contract conclusion, the receiver completes the contract document data and performs the conclusion work, replies to the sender, and the sender confirms and performs the conclusion completion work.

[0003] [Related Technology] In addition, as related prior art, there are Japanese Patent Application Laid-Open No. 2011-118845, "Contract Support System with Fixed Fee Display" (Patent Document 1), and Japanese Patent Application Laid-Open No. 2001-265980, "Production Service Providing Apparatus and Production Service Providing Method" (Patent Document 2).

[0004] Patent Document 1 shows a contract support system in which a customer can know a definite moving fee from a computer and conclude a contract for a moving work request at the definite fee. Patent Document 2 shows a production service providing apparatus that performs from a production request to contract conclusion and work completion.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0006] However, conventional online contract systems had a problem: if the recipient made an error in their work, the sender had to recreate the contract data from scratch and send it to the recipient, making the process of re-contracting cumbersome.

[0007] Patent documents 1 and 2 do not describe a configuration that allows for easy re-contracting if there is an error in the contract data completion process on the receiving end.

[0008] This invention has been made in view of the above circumstances, and aims to provide an online contract system and program that allows for easy re-contracting even if there is an error in the contract data completion process on the receiving end. [Means for solving the problem]

[0009] The present invention, which solves the problems of the above-mentioned conventional example, is an online contract system having a contract server that performs online contracts via a network, wherein the contract server is It has a memory unit and intervenes between the transmitting terminal and the receiving terminal to manage the data transmitted and received between the transmitting terminal and the receiving terminal. When sending contract data created on the sending terminal to the receiving terminal, the contract data is duplicated and sent as duplicate contract data. In the memory The receiving terminal memorizes the contract data and sends the completed contract data back to the sending terminal. When doing so, the completed contract data is stored in the memory unit. And when the sending terminal receives an instruction to return the completed contract data, the correction instruction message received from the sending terminal and Stored in the memory unit The system is characterized by transmitting the copied contract data to the receiving terminal.

[0010] The present invention relates to the online contract system described above, in which the contract server, when a rejection instruction is entered for contract data at the receiving terminal or a rejection instruction is entered for completed contract data at the sending terminal, Stored in the memory unit The copy contract data can be modified. The modified copy of the contract data is stored in the memory unit. And from the sending terminal Message requesting renegotiation Entered And,Corrected copy contract data as revised contract data , a message requesting re-signing and revised contract data The revised contract data is sent to the receiving terminal and duplicated as duplicated revised contract data. In the memory It is characterized by its ability to remember.

[0011] In the above-mentioned online contract system, when the contract server receives an instruction from the transmitting terminal that the contract has been concluded regarding the completed contract data completed on the receiving terminal, it confirms the completed contract data as a concluded contract. Store in the memory unit It is characterized by the following.

[0012] In the above-mentioned online contract system, the contract server transmits the transmission settings information before transmitting the contract data. In the memory Save it and on the sending terminal Setting information in the memory unit It is characterized by being searchable.

[0013] The present invention is characterized in that, in the above-mentioned online contract system, the contract server performs a preview of the contract on the receiving terminal to allow the recipient to confirm the input contents in writing before signing and agreeing.

[0014] The present invention is a computer program that operates on a contract server that performs online contracts via a network, wherein the contract server is It acts as an intermediary between the transmitting terminal and the receiving terminal, managing the data transmitted and received between the transmitting and receiving terminals. When sending contract data created on the sending terminal to the receiving terminal, the contract data is duplicated and sent as duplicate contract data. In the memory The receiving terminal memorizes the contract data and sends the completed contract data back to the sending terminal. When doing so, the completed contract data is stored in the memory unit. And when the sending terminal receives an instruction to return the completed contract data, the correction instruction message received from the sending terminal and Stored in the memory unit It is characterized by its function to transmit the copied contract data to the receiving terminal.

[0015] In the above program, the contract server is activated when a rejection instruction is entered at the receiving terminal for the contract data, or when a rejection instruction is entered at the transmitting terminal for the completed contract data. Stored in the memory unitEnable the modification of the contract document data The modified copy of the contract data is stored in the memory unit. and, from the transmitting terminal Message requesting renegotiation inputted And, the corrected contract document data as the corrected contract data , a message requesting re-signing and revised contract data transmit it to the receiving terminal and function to copy the corrected contract data as the copied corrected contract data In the memory and store it. It is characterized in that

[0016] In the present invention, in the above program, when an instruction for completion of conclusion is inputted at the transmitting terminal for the completed contract document data completed at the receiving terminal, the contract server functions to finalize the completed contract document data as the concluded contract Store in the memory unit It is characterized in that

Effect of the Invention

[0017] According to the present invention, when the contract server transmits the contract document data created at the transmitting terminal to the receiving terminal, it copies the contract document data as the copied contract document data It has a memory unit and intervenes between the transmitting terminal and the receiving terminal to manage the data transmitted and received between the transmitting terminal and the receiving terminal. and stores it, returns the completed contract document data completed at the receiving terminal to the transmitting terminal In the memory and, when an instruction for reversion is inputted at the transmitting terminal for the completed contract document data, as an online contract system that transmits the message of the correction instruction inputted from the transmitting terminal and When doing so, the completed contract data is stored in the memory unit. the copied contract document data to the receiving terminal, the transmitting terminal can easily redo the contract conclusion by transmitting the copied contract document data and the message of the correction instruction to the receiving terminal without having to recreate the contract document data from the beginning. There is an effect Stored in the memory unit

Brief Description of the Drawings

[0018] [Figure 1] It is a schematic configuration diagram of this system [Figure 2] It is an explanatory diagram showing the contract request / normal conclusion process [Figure 3] It is an explanatory diagram showing the reversion process [Figure 4] It is an explanatory diagram showing the rejection process ​ [Figure 5] This is a schematic diagram showing an example of the display screen on the sending terminal. [Modes for carrying out the invention]

[0019] Embodiments of the present invention will be described with reference to the drawings. [Summary of the Embodiment] An online contract system according to an embodiment of the present invention (this system) will be described with reference to the drawings. This system allows the sender to request the recipient to conclude a contract using contract data created on the cloud. The contract server sends the contract data from the sender to the recipient, but temporarily duplicates it during transmission. Once the recipient agrees to and signs the contract, and the sender confirms and completes the conclusion process, the duplicated contract data is finalized as the concluded contract. If the sender requests a revision, the system sends a revision instruction message and the duplicated contract data to the recipient, requesting a re-contract conclusion. This allows the sender to easily re-contract without having to recreate the contract data from scratch, simply by sending the duplicated contract data and revision instruction message to the recipient.

[0020] [This system: Figure 1] This system will be explained with reference to Figure 1. Figure 1 is a schematic diagram of the system's configuration. As shown in Figure 1, this system consists of a contract server 1, a sending terminal 2, a receiving terminal 3, and a network 4. Each component of this system will be described in detail below.

[0021] [Contract Server 1] Contract Server 1 controls the conclusion of online contracts in the cloud and implements the contract request / successful conclusion process, rejection process, and other optional processes described later. The contract server 1 comprises a control unit 11, a storage unit 12, and an interface unit 13. The contract server 1 implements the means for executing the above process by having the control unit 11 read and execute the processing program stored in the memory unit 12.

[0022] Furthermore, the memory unit 12 stores information about the parties to the contract, contract data, and copies thereof. The party information includes email addresses for sending and receiving contract data, mobile phone numbers for SMS (Short Message System), and, if the user is a user of this system, registration information such as user ID and login password. Interface unit 13 is an interface that connects to network 4.

[0023] [Sending terminal 2] The sending terminal 2 is the terminal of one of the parties to the contract (sender / contract requester), and is expected to be a personal computer (PC), smartphone, or tablet. The user of the transmitting terminal 2 is a user of the online contract for this system, and their user ID and login password for this system are stored in the storage unit 12.

[0024] [Receiving terminal 3] Receiving terminal 3 is the terminal of the other party to the contract (recipient / acceptor), and is expected to be a personal computer (PC), smartphone, or tablet. The user of receiving terminal 3 may be a user of this system's online contract, but may not be.

[0025] [Network 4] Network 4 uses the internet, but data transmission and reception are encrypted.

[0026] [Processing in this system: Figures 2-4] Next, the processing in this system will be explained with reference to Figures 2 to 4. Figure 2 is an explanatory diagram showing the contract request and successful conclusion process, Figure 3 is an explanatory diagram showing the return process, and Figure 4 is an explanatory diagram showing the rejection process. The processes handled by this system include contract request and successful conclusion processing, return processing, and rejection processing.

[0027] [Contract Request Processing: Figure 2] The contract request process involves the contract requester (sender) creating contract data on the sending terminal 2 and sending that contract data to the receiving terminal 3 to request the conclusion of the contract. Specifically, the sending terminal 2 logs into the system of the contract server 1 and creates contract data using the contract creation workflow. This contract data is then uploaded to the contract server 1 and stored in the storage unit 12, and subsequently sent to the receiving terminal 3. For transmission to the receiving terminal 3, an email is sent from the contract server 1 to the receiving terminal 3, and the terminal 3 accesses the URL (Uniform Resource Locator) indicated in that email to receive the contract data.

[0028] In detail, the contract server 1 receives the contract data created at the sending terminal 2 (S1), duplicates the contract data (S2), stores it in the storage unit 12 as duplicated contract data, and transmits the contract data to the receiving terminal 3 (S3).

[0029] The contract data sent to the receiving terminal 3 is then filled in by the recipient with their name and other details, approved with an electronic seal (signed and agreed), and the completed contract data (completed contract data) is uploaded to the contract server 1 (S4). Subsequently, the contract server 1 sends (replies to) the sending terminal 2 (S5). The completed contract data is stored in the storage unit 12 of the contract server 1.

[0030] [Normal fastening process] In the case of a successful contract signing process, the sending terminal 2 refers to the completed contract data returned and verifies it. If there are no problems, the "Complete Contract Signing" button on the screen shown in Figure 5 is pressed (S6), and the completed contract data is confirmed as completed contract data and stored in the storage unit 12. The status indicating that the completed contract data needs to be reviewed is called "requires review status."

[0031] [Screen displayed on the sending terminal 2: Figure 5] The display screen on the sending terminal 2 when the completed contract data is reviewed will be explained with reference to Figure 5. Figure 5 is a schematic diagram showing an example of the display screen on the sending terminal. When the sending terminal 2 confirms the completed contract data with a status requiring verification, buttons for "Return," "Reject," and "Complete Contract" are displayed at the bottom, as shown in Figure 5, and a message input field is displayed at the top.

[0032] The "Return" button executes the return process described later, the "Reject" button executes the rejection process described later, and the "Complete Contract" button completes the contract signing as described above. Furthermore, the message input field is used to enter a message requesting revisions in the case of a return process, and a message requesting re-signing in the case of a rejection process.

[0033] [Return process: Figure 3] The return process involves the sender terminal 2 reviewing the returned completed contract data. If, upon review, the completed contract data is found to be incomplete, the sender enters a message requesting corrections and a request for re-signing the contract (such as a message requesting corrections) into the message input field on the screen (as shown in Figure 5) (S7). When the "Return" button is pressed (S8), a confirmation message (confirmation dialog) stating "We will ask the recipient to re-enter the information" is displayed on the screen. If the sender selects "OK", the contract server 1 sends the correction instructions and other messages along with the duplicated contract data to the receiving terminal 3 (S9, S10). During this transmission, the duplicated contract data is further duplicated and stored in the storage unit 12. In this context, the copied contract data is data that has not been entered or modified by the recipient.

[0034] Furthermore, situations where the completed contract data is incomplete include errors in the input content, such as entering the name of the person handling the matter when the representative's name should be entered, and errors in the attached files, such as attaching an insurance card when a driver's license with a photograph should be attached. Furthermore, in the case of a renewed request for contract signing, the expiration date of the request email is reset and a new one is set.

[0035] The receiving terminal 3 then receives messages such as correction instructions and the duplicated contract data, and performs input into the duplicated contract data according to the messages to create the completed contract data (completed duplicated contract data).

[0036] Then, the receiving terminal 3 uploads the completed copy contract data to the contract server 1 (S11), the contract server 1 sends (replies) the completed contract data to the sending terminal 2 (S12), the sending terminal 2 verifies the completed copy contract data and presses the "Contract Complete" button, at which point the contract is successfully concluded. If further deficiencies are found, the user presses the "Return" button again to perform the return process.

[0037] [Rejection process: Figure 4] The rejection process involves the sender terminal 2 reviewing the completed contract data returned from the receiving terminal 3 and checking it under the "requires confirmation" status. If an error is found in the contract creation on the sending side, it will need to be recreated.

[0038] In this case, the sender terminal 2 presses the "Reject" button on its screen, and then presses the "Copy" button (not shown) (S13) to read the copied contract data stored in the storage unit 12 and display it on the sender terminal 2's screen.

[0039] The sending terminal 2 is made capable of modifying the duplicated contract data (S14), and is prompted to input a message requesting the re-signing of the contract (S15). Upon the sender's instruction to send, the contract server 1 sends the re-signing request message and the modified contract data (modified contract data) to the receiving terminal 3 (S16, S17). The contract server 1 also duplicates the modified contract data and stores it in the storage unit 12 as duplicated modified contract data. On the sending terminal 2, it is also acceptable to create the contract data from scratch by pressing the "Reject" button on the screen and not the "Duplicate" button.

[0040] Then, the receiving terminal 3 uploads the completed contract data (completed revised contract data) based on the revised contract data to the contract server 1 (S18), and the contract server 1 sends the completed revised contract data to the sending terminal 2 (S19).

[0041] On the sending terminal 2, the completed and revised contract data is checked with a status requiring confirmation. If there are no problems, the "Contract Complete" button is pressed, and the contract is concluded. If there are any problems during the verification process on the sending terminal 2, the "Return" or "Reject" button is pressed, and the process described above is repeated. Furthermore, the "Reject" button is also displayed on the screen of the receiving terminal 3. If the recipient notices an error in the contract, they can press the "Reject" button to send a message from the receiving terminal 3 to the sending terminal 2 requesting corrections, prompting the sending terminal 2 to make the necessary corrections.

[0042] [Application Example 1: Transmission Information Storage Function] One application example of this system is the function for saving transmitted information. The transmission information storage function saves the transmission format settings (transmission information) on the contract server 1 before the sending terminal 2 sends the contract data to the receiving terminal 3. This makes the transmission information searchable, and allows it to be retrieved and reused via search when needed.

[0043] The information sent includes the recipient's address, SMS phone number, expiration date, and optional settings such as electronic signature or digital signature. This transmission information saving function makes it easy to send contract data to recipients who have previously received it, using the same transmission format.

[0044] [Application Example 2: Customizable Input Field Layout] Another application example of this system is the ability to customize the arrangement of input fields. The input field layout customization function allows the sending terminal 2 to adjust (customize) the layout of input fields, etc., before sending, for either template contract data or user-created contract data.

[0045] Specifically, it allows you to fine-tune the position of the text box (the area where text is entered), adjust the width of the text box, wrap text that overflows the text box, and set the alignment of the text reflected in the text box to left / right, center, or justified. Furthermore, it allows users to change the font and font size of the entered text, adjust the margins, and display guides to align multiple input fields. The sending terminal 2 can improve the appearance of the contract by arbitrarily adjusting the arrangement of input items, etc.

[0046] [Application Example 3: Document Preview Function] One application example of this system is a document preview function. The document preview function allows the recipient, who is the user of the receiving terminal 3, to preview the document to confirm how the content entered into the contract data on the receiving terminal 3 is reflected in the written contract before completing the signing and agreement. The recipient can use the preview function to check the contents they have entered in the written contract, allowing them to sign and agree with confidence.

[0047] [Effects of the embodiment] According to this system, when the contract server 1 sends contract data to the receiving terminal 3, it duplicates the contract data and stores it as duplicated contract data. When the sending terminal 2 receives a request for corrections to the completed contract data from the sending side, the sending terminal 2 sends a message with the correction instructions and the duplicated contract data to the receiving terminal 3, thereby requesting a re-contract signing. This has the effect of making it easy to redo the contract signing by sending the duplicated contract data and the correction instruction message to the receiving terminal 3 without having to recreate the contract data from scratch. [Industrial applicability]

[0048] The present invention is suitable for an online contract system and program that allows for easy re-contracting even if there is an error in the contract data completion process on the receiving end. [Explanation of Symbols]

[0049] 1...Contract server, 2...Sending terminal, 3...Receiving terminal, 4...Network, 11...Control unit, 12...Storage unit, 13...Interface unit

Claims

1. An online contract system having a contract server that performs online contracts via a network, The online contract system is characterized in that the contract server includes a storage unit and intervenes between a transmitting terminal and a receiving terminal to manage data transmitted and received between the transmitting terminal and the receiving terminal, and when the transmitting terminal sends contract data created by the transmitting terminal to the receiving terminal, it duplicates the contract data and stores it in the storage unit as duplicated contract data, when the receiving terminal returns completed contract data that has been completed from the contract data to the transmitting terminal, it stores the completed contract data in the storage unit, and when the transmitting terminal receives an instruction to return the completed contract data, it sends the correction instruction message received from the transmitting terminal and the duplicated contract data stored in the storage unit to the receiving terminal.

2. The online contract system according to claim 1, characterized in that when the contract server receives a rejection instruction for the contract data from the receiving terminal or a rejection instruction for the completed contract data from the transmitting terminal, it makes the duplicate contract data stored in the storage unit modifiable and stores the modified duplicate contract data in the storage unit, and when a message requesting re-signing is received from the transmitting terminal, it sends the message requesting re-signing and the modified contract data to the receiving terminal as modified contract data, and also duplicates the modified contract data and stores it in the storage unit as duplicate modified contract data.

3. The online contract system according to claim 1 or 2, characterized in that when the contract server receives an instruction from the transmitting terminal that the contract has been completed, it confirms the completed contract data as a concluded contract and stores it in the storage unit.

4. The online contract system according to claim 1 or 2, characterized in that the contract server stores transmission setting information in the storage unit before transmitting contract data, and the transmitting terminal can retrieve the setting information in the storage unit.

5. The online contract system according to claim 1 or 2, characterized in that the contract server performs a preview of the contract in writing for the recipient terminal to confirm the input contents before signing and agreeing.

6. A computer program that runs on a contract server that handles online contracts via a network, The program is characterized in that the contract server interposes between the transmitting terminal and the receiving terminal to manage the data transmitted and received between the transmitting terminal and the receiving terminal, and when the transmitting terminal sends contract data created by the transmitting terminal to the receiving terminal, it duplicates the contract data and stores it in the storage unit as duplicate contract data, when the receiving terminal returns completed contract data that has been completed from the contract data to the transmitting terminal, it stores the completed contract data in the storage unit, and when the transmitting terminal receives an instruction to return the completed contract data, it transmits the correction instruction message received from the transmitting terminal and the duplicate contract data stored in the storage unit to the receiving terminal.

7. The program according to claim 6, characterized in that when the receiving terminal inputs an instruction to reject the contract data or when the transmitting terminal inputs an instruction to reject the completed contract data, the contract server makes the duplicate contract data stored in the storage unit modifiable and stores the modified duplicate contract data in the storage unit, and when the transmitting terminal inputs a message requesting re-signing, the modified duplicate contract data is used as modified contract data, and the message requesting re-signing and the modified contract data are sent to the receiving terminal, and the modified contract data is duplicated and stored in the storage unit as duplicate modified contract data.

8. The program according to claim 6 or 7, characterized in that when the sending terminal receives an instruction that the contract has been concluded regarding the completed contract data completed at the receiving terminal, the contract server is configured to confirm the completed contract data as a concluded contract and store it in the storage unit.

Images