WO2020062661A1

WO2020062661A1 - Method, device and apparatus for verifying consistency of contract data and storage medium

Info

Publication number: WO2020062661A1
Application number: PCT/CN2018/123279
Authority: WO
Inventors: 马玉芳
Original assignee: 平安科技（深圳）有限公司
Priority date: 2018-09-28
Filing date: 2018-12-25
Publication date: 2020-04-02
Also published as: CN109656931B; CN109656931A

Abstract

Disclosed are a method, device and apparatus for verifying consistency of contract data and a storage medium. The method comprises: when a contract verifying instruction is received, a target version number in the contract verifying instruction is obtained, and a standard contract template corresponding to the target version number is obtained from a preset database (S10); a target contract currently to be verified is obtained and compared with the standard contract template, so as to judge whether the target contract matches the standard contract template (S20); and if the target contract does not match the standard contract template, a reminding message on inconsistent contract information is generated and displayed, so as to remind a user that the target contract is abnormal (S30). The method automatically compares the target contract to be verified with the standard contract template of the corresponding version to verify contract and remind a contract abnormality, thereby avoiding economic losses caused by inconsistency of electronic versions, and improving the verification efficiency and the user experience by avoiding manual verification.

Description

Method, device, equipment and storage medium for verifying contract data consistency Ranch

This application claims the priority of a Chinese patent application filed on September 28, 2018 with the Chinese Patent Office, application number 201811140354.0, and the invention name as "Confirmation Method, Device, Equipment, and Storage Medium for Contract Data Consistency" Incorporated by reference.

Technical field

The present application relates to the field of computer communication technology, and in particular, to a method, an apparatus, a device, and a computer-readable storage medium for verifying contract data consistency.

Background technique

With the continuous development of the economy, the number of contracts signed in commercial activities has increased dramatically. In order to improve convenience, traditional paper contracts have gradually been replaced by electronic contracts. However, when the electronic contract is reviewed by each audit node, the contract format or content may be modified, and multiple different versions of the contract may be generated. Different nodes store different versions of contracts, which can easily lead to disordered contract information. For example, the contract information and the contract information that is finally passed through the final review are inconsistent, which causes confusion in contract management and economic losses. Therefore, how to solve the problem of inconsistent versions of electronic contracts in the prior art has become a technical problem to be solved urgently.

Summary of the Invention

The main purpose of this application is to provide a method, a device, a device, and a computer-readable storage medium for verifying the consistency of contract data, which aims to solve the technical problem of inconsistent versions of electronic contracts in the prior art.

In order to achieve the above purpose, this application provides a method for verifying the consistency of contract data. The method for verifying the consistency of contract data includes the following steps:

When receiving the contract verification instruction, obtaining a target version number in the contract verification instruction, and obtaining a standard contract template corresponding to the target version number in a preset database;

Obtaining a current target contract to be verified, comparing the target contract with the standard contract template, and determining whether the target contract matches the standard contract template;

If the target contract does not match the standard contract template, a reminder message with inconsistent contract information is generated and displayed to remind the user that there is an abnormality in the target contract.

Optionally, when receiving the contract verification instruction, acquiring the target version number in the contract verification instruction, and before the step of acquiring a standard contract template corresponding to the target version number in a preset database, the method further includes:

When receiving a contract template uploaded by a user, adding a corresponding first version number to the contract template according to a preset identification rule;

Importing the contract template into an audit chain according to a preset audit process, so that each audit node in the audit chain reviews the contract template;

When a modification of the contract template is detected, adding a corresponding second version number to the modified contract template;

The contract template added with the first version number and the contract template added with the second version number are stored in the preset database.

Optionally, the step of storing the contract template added with the first version number and the contract template added with the second version number to the preset database includes:

Encrypting the contract template added with the first version number and the contract template added with the second version number according to a preset user key;

Storing the encrypted contract template added with the first version number and the contract template added with the second version number in a preset database of the blockchain platform, and sending the preset user key to user terminal.

Optionally, when receiving the contract verification instruction, obtaining the target version number in the contract verification instruction, and obtaining a standard contract template corresponding to the target version number in a preset database includes:

When receiving the contract verification instruction, obtaining a target version number and a user key in the contract verification instruction;

Obtain a contract template corresponding to the target version number in a preset database of the blockchain platform as a standard contract template, and decrypt the standard contract template according to the user key.

Optionally, if the target contract does not match the standard contract template, generating and displaying a reminder message that the contract information is inconsistent to remind the user that the target contract is abnormal, after the step, the method further includes:

Acquiring a target contract version number in the target contract, and determining whether the target contract version number is consistent with the target version number;

If the target contract version number is inconsistent with the target version number, the target contract is replaced with the standard contract template, and a corresponding replacement reminder message is generated and displayed according to the target version number and the target contract version number.

Optionally, after the step of obtaining a target contract version number in the target contract and determining whether the target contract version number is consistent with the target version number, the method further includes:

If the target contract version number is consistent with the target version number, different content in the target contract is modified according to the standard contract template, and corresponding content is generated and displayed according to the different content and the revised content. Correct the reminder message.

Optionally, after the step of obtaining a target contract to be verified, comparing the target contract with the standard contract template, and determining whether the target contract matches the standard contract template, the method further includes:

If the target contract matches the standard contract template, a reminder message for contract verification completion is generated and displayed to remind the user that the contract content of the target contract is verified correctly.

In addition, in order to achieve the above object, the present application further provides a device for verifying the consistency of contract data. The device for verifying the consistency of contract data includes: Ranch

A template obtaining module, configured to obtain a target version number in the contract verification instruction when the contract verification instruction is received, and obtain a standard contract template corresponding to the target version number in a preset database;

A contract comparison module, configured to obtain a current target contract to be verified, compare the target contract with the standard contract template, and determine whether the target contract matches the standard contract template;

The abnormality reminding module is configured to generate and display a reminder message that the contract information is inconsistent if the target contract does not match the standard contract template, so as to remind the user that the target contract is abnormal.

In addition, in order to achieve the above-mentioned object, the present application further provides a contract data consistency verification device, where the contract data consistency verification device includes a processor, a memory, and can be stored on the memory and can be used by the processor The executed contract data consistency verification program, wherein when the contract data consistency verification program is executed by the processor, the steps of the method for verifying contract data consistency as described above are implemented.

In addition, in order to achieve the above object, the present application also provides a computer-readable storage medium, wherein the computer-readable storage medium stores a verification program for the consistency of contract data, wherein the verification program for the consistency of contract data is When implemented, the steps of the method for verifying the consistency of contract data as described above.

This application provides a method for verifying the consistency of contract data, that is, when a contract verification instruction is received, the target version number in the contract verification instruction is obtained, and a standard contract template corresponding to the target version number is obtained in a preset database. Obtaining the current target contract to be verified, comparing the target contract with the standard contract template, and determining whether the target contract matches the standard contract template; if the target contract matches the standard contract template; If they do not match, a warning message with inconsistent contract information is generated and displayed to remind the user that the target contract is abnormal. In the above manner, this application uses the standard contract template to automatically compare the target contract to be verified with the corresponding version of the standard contract template for contract verification. When there is an abnormality in the contract information, a contract abnormality alert is provided to avoid economic losses caused by inconsistent versions of the electronic contract, without manual verification, and improving verification efficiency and user experience.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of a hardware structure of a device for verifying contract data consistency involved in a solution according to an embodiment of the present application; FIG.

2 is a schematic flowchart of a first embodiment of a method for verifying contract data consistency of an application;

3 is a schematic flowchart of a second embodiment of a method for verifying contract data consistency of an application;

4 is a schematic flowchart of a third embodiment of a method for verifying contract data consistency of an application;

FIG. 5 is a schematic diagram of functional modules of a first embodiment of a device for verifying contract data consistency in this application.

The implementation, functional features and advantages of the purpose of this application will be further described with reference to the embodiments and the drawings.

detailed description

It should be understood that the specific embodiments described herein are only used to explain the application, and are not used to limit the application.

The method for verifying the consistency of contract data involved in the embodiment of the present application is mainly applied to a device for verifying the consistency of contract data. The device for verifying the consistency of contract data may be a device with display and processing functions such as a PC, a portable computer, or a mobile terminal.

Referring to FIG. 1, FIG. 1 is a schematic diagram of a hardware structure of a contract data consistency verification device involved in a solution of an embodiment of the present application. In the embodiment of the present application, the contract data consistency verification device may include a processor 1001 (for example, a CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. The communication bus 1002 is used to implement connection and communication between these components. The user interface 1003 may include a display and an input unit such as a keyboard. The network interface 1004 may optionally include a standard wired interface and a wireless interface. (Such as the WI-FI interface); the memory 1005 can be a high-speed RAM memory or a stable memory (non-volatile memory), such as a disk memory, the memory 1005 may optionally be a storage device independent of the foregoing processor 1001.

Those skilled in the art can understand that the hardware structure shown in FIG. 1 does not constitute a limitation on the verification device of the contract data consistency, and may include more or less components than shown in the figure, or combine some components, or be different Of the components.

With continued reference to FIG. 1, the memory 1005 as a computer-readable storage medium in FIG. 1 may include an operating system, a network communication module, and a verification program for consistency of contract data.

In FIG. 1, the network communication module is mainly used to connect to the server and perform data communication with the server; and the processor 1001 can call the verification procedure of the contract data consistency stored in the memory 1005 and execute the contract data consistency provided by the embodiment of this application. Sexual verification methods.

The embodiment of the present application provides a method for verifying the consistency of contract data.

Referring to FIG. 2, FIG. 2 is a schematic flowchart of a first embodiment of a method for verifying contract data consistency in this application.

In this embodiment, the method for verifying contract data consistency includes the following steps:

Step S10, When receiving the contract verification instruction, obtaining a target version number in the contract verification instruction, and obtaining a standard contract template corresponding to the target version number in a preset database;

At present, when the electronic contract is reviewed by various review nodes, the contract format or content may be modified, and multiple different versions of the contract may be generated. Different nodes have different versions of contracts stored, which can easily lead to inconsistencies between the signed contract and the final audited contract information, which can easily lead to management confusion and economic loss.

In this embodiment, in order to avoid the problem of inconsistent versions of electronic contracts, by providing a method for verifying the consistency of contract data, the target contract is verified by using a standard contract template corresponding to the target version number. Specifically, the contract verification instruction may be triggered by a user through a contract verification function button in the client, or may be automatically triggered when a user uploads a contract operation. When the contract verification instruction is received, the contract verification instruction is parsed to obtain a target version number in the contract verification instruction. The target version number is the corresponding contract version number specified in each business link. For example, the first version node in the review chain, that is, the contract version number used in the format review link is the first version number. The contract used when signing the contract The version number is the second version number. The target version number may be manually selected or manually input by the user, or the contract version number corresponding to each business link may be pre-associated in advance, and the system automatically obtains the corresponding version number as the target version number according to the current business link. Then according to the target version number corresponding to the contract verification instruction, a standard contract template to be used in the current business link is obtained in a preset database. The preset database is a contract corresponding to each version number, and each version contract is associated with a corresponding business link and / or version number.

Step S20: Obtain a current target contract to be verified, compare the target contract with the standard contract template, and determine whether the target contract matches the standard contract template.

In this embodiment, when the standard contract template is determined, a target contract that needs to be verified currently is obtained. The target contract is compared with the standard contract template. The comparison process may be performed according to a preset comparison process. For example, according to the page number, text format, and text content comparison process. That is, first determine whether the page number of the target contract is consistent with the page number of the standard contract template, then determine whether the text format on each page number in the target contract is consistent with the corresponding text format of the standard contract template, and finally determine whether the page number in the target contract Whether the text content of is consistent with the text content of the standard contract template. If the comparison results summarized in the comparison process according to the comparison process are consistent, it is determined that the target contract matches the standard contract template; otherwise, it is determined that the target contract does not match the target contract.

In step S30, if the target contract does not match the standard contract template, a reminder message with inconsistent contract information is generated and displayed to remind the user that there is an abnormality in the target contract.

In this embodiment, when it is determined that the target contract does not match the standard contract template, if the number of page numbers of the target contract and the standard contract template is detected to be inconsistent, or the text format in the target contract and the standard contract template is detected When there is an inconsistency, a corresponding reminder message may be generated according to the inconsistency, and the reminder message is sent to the corresponding management end, so that the management end can confirm whether to correct the inconsistency. In a specific embodiment, when the server detects that the target contract is inconsistent with the standard contract template, the server may modify the target contract. Alternatively, when the server receives the correction instruction fed back by the management end, according to the content in the standard contract template, the server corrects inconsistent content in the target contract. In order to make it easier for users to understand the amendment content corresponding to the contract in a timely manner, correction reminder information is generated according to the contract content before the amendment and the contract content after the amendment, such as a comparison screenshot before and after the amendment, or a revised text before and after the amendment, and the amendment reminder information is sent. Go to the management side for users to view.

Further, after step S20, the method further includes:

In this embodiment, if the target contract is compared with the standard contract template and the format and content of the target contract are consistent with the standard contract template, the verification of the target contract is normal. . A reminder message that the contract verification is complete or that the target contract is abnormal can be generated so that the user can continue to perform business operations according to the target contract.

This embodiment provides a method for verifying contract data consistency, that is, when a contract verification instruction is received, a target version number in the contract verification instruction is obtained, and a standard contract corresponding to the target version number is obtained in a preset database. Template; obtain the current target contract to be verified, compare the target contract with the standard contract template, and determine whether the target contract matches the standard contract template; if the target contract matches the standard contract If the templates do not match, a reminder message with inconsistent contract information is generated and displayed to remind the user that the target contract is abnormal. In the above manner, this application uses the standard contract template to automatically compare the target contract to be verified with the corresponding version of the standard contract template for contract verification. When there is an abnormality in the contract information, a contract abnormality alert is provided to avoid economic losses caused by inconsistent versions of the electronic contract, without manual verification, and improving verification efficiency and user experience.

Referring to FIG. 3, FIG. 3 is a schematic flowchart of a second embodiment of a method for verifying contract data consistency in this application.

Based on the embodiment shown in FIG. 2, in this embodiment, before step S10, the method further includes:

Step S41: When a contract template uploaded by a user is received, a corresponding first version number is added to the contract template according to a preset identification rule;

In this embodiment, a user may upload a contract template to the system, and the contract template may be an original contract, a modified contract, or a final version of a contract that has been approved. When receiving a contract template uploaded by a user, the contract template is added with a corresponding first version number according to a preset identification rule. The preset identification rule may be adding a version number according to a current time, or selecting a current number as a first version number from a preset contract number as required.

Step S42: Introducing the contract template into the review chain according to a preset review process, so that each review node in the review chain reviews the contract template;

In this embodiment, the contract template added with the version number is passed into the review chain for review, that is, the contract template is formatted or text-verified according to a preset review process corresponding to the contract. The contract template may be transferred to a corresponding review node corresponding reviewer system, so that the corresponding reviewer can review the content or terms of the contract template.

Step S43: When a modification of the contract template is detected, a corresponding second version number is added to the modified contract template;

In this embodiment, if a modification instruction triggered by the reviewer's operation is detected, the modification instruction is triggered by the reviewer's modification operation on the contract template when the reviewer has checked out the contract template for abnormal problems. instruction. Add the second version number to the modified contract template according to the preset identification rule. In a specific embodiment, if the next node reviewer continues to modify the contract template corresponding to the second version number, the modified contract template is added with a third version number according to the preset identification rule. By analogy, different modified contract templates are added with different contract version numbers.

In step S44, the contract template added with the first version number and the contract template added with the second version number are stored in the preset database.

In this embodiment, each version number is associated with its corresponding contract template, and each version number is associated with its corresponding contract template and stored in the preset database for subsequent invocation.

Further, the step S44 specifically includes:

S441. Encrypt the contract template added with the first version number and the contract template added with the second version number according to a preset user key;

In this embodiment, in order to ensure the security of the contract template, each version of the contract template is stored on the blockchain. Specifically, each version number and the corresponding contract template are encrypted according to a preset user key, such as a random code or other encrypted identification.

S442. Store the encrypted contract template added with the first version number and the contract template added with the second version number in a preset database of the blockchain platform, and store the preset user key. Send to the client.

In this embodiment, after the contract template is encrypted, the encrypted version numbers and corresponding contract templates are stored in a preset database in the blockchain according to a preset storage path, which is convenient for subsequent contract templates. Call safely. The preset user key used during encryption is then sent to the user terminal, where the user terminal may be a terminal for storing the user key used for each encryption. In a specific embodiment, the preset user key may also be stored in a corresponding key storage list. When a user needs to perform contract verification in real time, a corresponding user key can be obtained from the key storage list, so as to generate a corresponding contract verification instruction according to the user key and a target contract version number.

Referring to FIG. 4, FIG. 4 is a schematic flowchart of a third embodiment of a method for verifying contract data consistency of the present application.

Based on the embodiment shown in FIG. 2 above, in this embodiment, after step S30, the method further includes:

Step S51: Obtain a target contract version number in the target contract, and determine whether the target contract version number is consistent with the target version number;

In this embodiment, when it is detected that the target contract is inconsistent with the standard contract template, in order to timely correct the abnormal information of the target contract, it is first determined whether the target contract version number of the target contract is in addition to the target version number. Other version numbers.

Step S52: If the target contract version number is not consistent with the target version number, replace the target contract with the standard contract template, and generate and display a corresponding replacement reminder according to the target version number and the target contract version number. Message.

In this embodiment, if the target contract is a contract with another version number, that is, the target contract is a wrong version number contract, the standard contract template corresponding to the target version number may be directly replaced with the wrong target contract.

In step S53, if the target contract version number is consistent with the target version number, different content in the target contract is modified according to the standard contract template, and generated based on the different content and the revised content. The corresponding correction reminder message is displayed.

In this embodiment, if the target contract version number is consistent with the target version number, that is, the target contract is not a wrong version number contract, then an exception in the target contract is made according to the standard content in the standard contract template. Contents are amended. Then, corresponding reminder messages are generated according to the contents before and after the amendment so that the user can understand the contents of the revised contract and confirm the contents of the amendment.

In addition, the embodiment of the present application also provides a device for verifying the consistency of contract data.

Referring to FIG. 5, FIG. 5 is a schematic diagram of functional modules of a first embodiment of a device for verifying contract data consistency of the present application.

In this embodiment, the contract data consistency verification device includes:

A template obtaining module 10 is configured to obtain a target version number in the contract verification instruction when receiving a contract verification instruction, and obtain a standard contract template corresponding to the target version number in a preset database;

A contract comparison module 20, configured to obtain a current target contract to be verified, compare the target contract with the standard contract template, and determine whether the target contract matches the standard contract template;

The abnormality reminding module 30 is configured to generate and display a reminder message that the contract information is inconsistent if the target contract does not match the standard contract template, to remind the user that there is an abnormality in the target contract.

Further, the apparatus for verifying contract data consistency further includes:

The verification completion reminding module is configured to generate and display a contract verification completion reminding message if the target contract matches the standard contract template to remind the user that the contract content of the target contract is correct.

A first identification module, configured to add a corresponding first version number to the contract template according to a preset identification rule when a contract template uploaded by a user is received;

A contract review module, configured to pass the contract template into the review chain according to a preset review process, so that each review node in the review chain reviews the contract template;

A second identification module, configured to add a corresponding second version number to the modified contract template when a modification of the contract template is detected;

The template storage module is configured to store the contract template added with the first version number and the contract template added with the second version number to the preset database.

Further, the template storage module further includes:

An encryption unit, configured to encrypt the contract template added with the first version number and the contract template added with the second version number according to a preset user key;

A storage unit, configured to store the encrypted contract template added with the first version number and the contract template added with the second version number into a preset database of a blockchain platform, and store the preset The user key is sent to the client.

Wherein, each module in the above-mentioned contract data consistency verification device corresponds to each step in the above-mentioned embodiment of the method for verifying contract data consistency, and its functions and implementation processes are not repeated here one by one.

In addition, an embodiment of the present application further provides a computer-readable storage medium.

The computer-readable storage medium of the present application stores a contract data consistency verification program. When the contract data consistency verification program is executed by a processor, the steps of the method for verifying contract data consistency are implemented.

The method implemented when the procedure for verifying the consistency of contract data is implemented may refer to various embodiments of the method for verifying the consistency of contract data in this application, and details are not described herein again.

It should be noted that, in this article, the terms "including", "including" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or system including a series of elements includes not only those elements, It also includes other elements not explicitly listed, or elements inherent to such a process, method, article, or system. Without more restrictions, an element limited by the sentence "including a ..." does not exclude the existence of other identical elements in the process, method, article, or system that includes the element.

The above-mentioned serial numbers of the embodiments of the present application are merely for description, and do not represent the superiority or inferiority of the embodiments.

Through the description of the above embodiments, those skilled in the art can clearly understand that the methods in the above embodiments can be implemented by means of software plus a necessary universal hardware platform, and of course, also by hardware, but in many cases the former is better. Implementation. Based on such an understanding, the technical solution of this application that is essentially or contributes to the existing technology can be embodied in the form of a software product. The computer software product is stored in a storage medium (such as ROM / RAM) as described above. , Magnetic disk, optical disc), including a number of instructions to enable a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in the embodiments of this application.

The above are only preferred embodiments of the present application, and thus do not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made by using the contents of the specification and drawings of the present application, or directly or indirectly used in other related technical fields Are included in the scope of patent protection of this application.

Claims

A method for verifying contract data consistency, which is characterized in that the method for verifying contract data consistency includes the following steps:

When receiving the contract verification instruction, obtaining a target version number in the contract verification instruction, and obtaining a standard contract template corresponding to the target version number in a preset database;

Obtaining a current target contract to be verified, comparing the target contract with the standard contract template, and determining whether the target contract matches the standard contract template;

If the target contract does not match the standard contract template, a reminder message with inconsistent contract information is generated and displayed to remind the user that there is an abnormality in the target contract.
The method for verifying the consistency of contract data according to claim 1, wherein when receiving a contract verification instruction, the target version number in the contract verification instruction is obtained, and the target is obtained in a preset database. Before the steps of the standard contract template corresponding to the version number, it also includes:

When receiving a contract template uploaded by a user, adding a corresponding first version number to the contract template according to a preset identification rule;

Importing the contract template into an audit chain according to a preset audit process, so that each audit node in the audit chain reviews the contract template;

When a modification of the contract template is detected, adding a corresponding second version number to the modified contract template;

The contract template added with the first version number and the contract template added with the second version number are stored in the preset database.
The method for verifying contract data consistency according to claim 2, wherein the contract template to which the first version number is added and the contract template to which the second version number is added are stored in the pre- The steps for setting up the database include:

Encrypting the contract template added with the first version number and the contract template added with the second version number according to a preset user key;

Storing the encrypted contract template added with the first version number and the contract template added with the second version number in a preset database of the blockchain platform, and sending the preset user key to user terminal.
The method for verifying the consistency of contract data according to claim 3, wherein when receiving the contract verification instruction, the target version number in the contract verification instruction is obtained, and the target is obtained in a preset database. The steps for a standard contract template for a version number include:

When receiving the contract verification instruction, obtaining a target version number and a user key in the contract verification instruction;

Obtain a contract template corresponding to the target version number in a preset database of the blockchain platform as a standard contract template, and decrypt the standard contract template according to the user key.
The method for verifying the consistency of contract data according to claim 1, wherein if the target contract does not match the standard contract template, generating and displaying a reminder message of inconsistent contract information to remind the user After describing the abnormal steps in the target contract, it also includes:

Acquiring a target contract version number in the target contract, and determining whether the target contract version number is consistent with the target version number;

If the target contract version number is inconsistent with the target version number, the target contract is replaced with the standard contract template, and a corresponding replacement reminder message is generated and displayed according to the target version number and the target contract version number.
The method for verifying the consistency of contract data according to claim 5, wherein the acquiring the target contract version number in the target contract, and determining whether the target contract version number is consistent with the target version number After the steps, it also includes:

If the target contract version number is consistent with the target version number, different content in the target contract is modified according to the standard contract template, and corresponding content is generated and displayed according to the different content and the revised content. Correct the reminder message.
The method for verifying the consistency of contract data according to claim 1, wherein the acquisition of a target contract to be verified currently, comparing the target contract with the standard contract template, and judging the target contract After the step of matching with the standard contract template, the method further includes:

If the target contract matches the standard contract template, a reminder message for contract verification completion is generated and displayed to remind the user that the contract content of the target contract is verified correctly. Ranch
A contract data consistency verification device, characterized in that the contract data consistency verification device includes:

A template obtaining module, configured to obtain a target version number in the contract verification instruction when the contract verification instruction is received, and obtain a standard contract template corresponding to the target version number in a preset database;

A contract comparison module, configured to obtain a current target contract to be verified, compare the target contract with the standard contract template, and determine whether the target contract matches the standard contract template;

The abnormality reminding module is configured to generate and display a reminder message that the contract information is inconsistent if the target contract does not match the standard contract template, so as to remind the user that the target contract is abnormal.
The contract data consistency verification device according to claim 8, wherein the contract data consistency verification device further comprises:

A first identification module, configured to add a corresponding first version number to the contract template according to a preset identification rule when a contract template uploaded by a user is received;

A contract review module, configured to pass the contract template into the review chain according to a preset review process, so that each review node in the review chain reviews the contract template;

A second identification module, configured to add a corresponding second version number to the modified contract template when a modification of the contract template is detected;

The template storage module is configured to store the contract template added with the first version number and the contract template added with the second version number to the preset database.
The apparatus for verifying contract data consistency according to claim 9, wherein the template storage module further comprises:

An encryption unit, configured to encrypt the contract template added with the first version number and the contract template added with the second version number according to a preset user key;

A storage unit, configured to store the encrypted contract template added with the first version number and the contract template added with the second version number into a preset database of a blockchain platform, and store the preset The user key is sent to the client.
The apparatus for verifying contract data consistency according to claim 10, wherein the template obtaining module is further configured to:

When receiving the contract verification instruction, obtaining a target version number and a user key in the contract verification instruction;

Obtain a contract template corresponding to the target version number in a preset database of the blockchain platform as a standard contract template, and decrypt the standard contract template according to the user key.
The contract data consistency verification device according to claim 8, wherein the contract data consistency verification device further comprises:

The verification completion reminding module is configured to generate and display a contract verification completion reminding message if the target contract matches the standard contract template to remind the user that the contract content of the target contract is correct.
A contract data consistency verification device, characterized in that the contract data consistency verification device includes a processor, a memory, and a contract data consistency stored in the memory and executable by the processor. The verification program, wherein when the contract data consistency verification program is executed by the processor, the steps of the method for verifying the contract data consistency according to claim 1 are implemented.
A contract data consistency verification device, characterized in that the contract data consistency verification device includes a processor, a memory, and a contract data consistency stored in the memory and executable by the processor. The verification program, wherein when the verification program of the contract data consistency is executed by the processor, the steps of the method for verifying the consistency of the contract data according to claim 2 are implemented.
A contract data consistency verification device, characterized in that the contract data consistency verification device includes a processor, a memory, and a contract data consistency stored in the memory and executable by the processor. The verification program, wherein when the verification procedure for the consistency of the contract data is executed by the processor, the steps of the method for verifying the consistency of the contract data according to claim 3 are implemented.
A contract data consistency verification device, characterized in that the contract data consistency verification device includes a processor, a memory, and a contract data consistency stored in the memory and executable by the processor. The verification program, wherein when the contract data consistency verification program is executed by the processor, the steps of the method for verifying the contract data consistency according to claim 4 are implemented.
A computer-readable storage medium, characterized in that a contract data consistency verification program is stored on the computer-readable storage medium, wherein when the contract data consistency verification program is executed by a processor, the claim is implemented as claimed Steps of the method for verifying the consistency of contract data as described in 1.
A computer-readable storage medium, characterized in that a contract data consistency verification program is stored on the computer-readable storage medium, wherein when the contract data consistency verification program is executed by a processor, the claim is implemented as claimed Steps of the method for verifying the consistency of contract data as described in 2.
A computer-readable storage medium, characterized in that a contract data consistency verification program is stored on the computer-readable storage medium, wherein when the contract data consistency verification program is executed by a processor, the claim is implemented as claimed Steps of the method for verifying the consistency of contract data as described in 3.
A computer-readable storage medium, characterized in that a contract data consistency verification program is stored on the computer-readable storage medium, wherein when the contract data consistency verification program is executed by a processor, the claim is implemented as claimed Steps of the method for verifying contract data consistency as described in 4.