WO2020062661A1 - Procédé, dispositif et appareil de vérification de cohérence de données de contrat et support d'enregistrement - Google Patents

Procédé, dispositif et appareil de vérification de cohérence de données de contrat et support d'enregistrement Download PDF

Info

Publication number
WO2020062661A1
WO2020062661A1 PCT/CN2018/123279 CN2018123279W WO2020062661A1 WO 2020062661 A1 WO2020062661 A1 WO 2020062661A1 CN 2018123279 W CN2018123279 W CN 2018123279W WO 2020062661 A1 WO2020062661 A1 WO 2020062661A1
Authority
WO
WIPO (PCT)
Prior art keywords
contract
target
template
version number
data consistency
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2018/123279
Other languages
English (en)
Chinese (zh)
Inventor
马玉芳
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ping An Technology Shenzhen Co Ltd
Original Assignee
Ping An Technology Shenzhen Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ping An Technology Shenzhen Co Ltd filed Critical Ping An Technology Shenzhen Co Ltd
Publication of WO2020062661A1 publication Critical patent/WO2020062661A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management

Definitions

  • 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.
  • 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.
  • 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:
  • 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 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:
  • 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 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:
  • obtaining the target version number in the contract verification instruction 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:
  • the method further includes:
  • 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 further includes:
  • 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.
  • 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;
  • 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.
  • FIG. 2 is a schematic flowchart of a first embodiment of a method for verifying contract data consistency of an application
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 2 is a schematic flowchart of a first embodiment of a method for verifying contract data consistency in this application.
  • 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;
  • 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.
  • the target contract is verified by using a standard contract template corresponding to the target version number.
  • 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.
  • 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.
  • 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 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 3 is a schematic flowchart of a second embodiment of a method for verifying contract data consistency in this application.
  • 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;
  • 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.
  • 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.
  • 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;
  • 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.
  • the modified contract template is added with a third version number according to the preset identification rule.
  • 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.
  • step S44 specifically includes:
  • each version of the contract template is stored on the blockchain.
  • 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.
  • 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.
  • 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.
  • FIG. 4 is a schematic flowchart of a third embodiment of a method for verifying contract data consistency of the present application.
  • 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;
  • 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.
  • the standard contract template corresponding to the target version number may be directly replaced with the wrong target contract.
  • 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.
  • the target contract version number is consistent with the target version number, that is, the target contract is not a wrong version number contract
  • 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.
  • the embodiment of the present application also provides a device for verifying the consistency of contract data.
  • 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.
  • 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 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.
  • the apparatus for verifying contract data consistency further includes:
  • 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
  • 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
  • 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.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Human Resources & Organizations (AREA)
  • Operations Research (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Data Mining & Analysis (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

L'invention concerne un procédé, un dispositif et un appareil permettant de vérifier la cohérence de données de contrat, ainsi qu'un support d'enregistrement. Le procédé comprend les étapes suivantes : lorsqu'une instruction de vérification de contrat est reçue, un numéro de version cible dans l'instruction de vérification de contrat est obtenu et un modèle de contrat standard correspondant au numéro de version cible est obtenu à partir d'une base de données prédéfinie (S10); un contrat cible actuellement à vérifier est obtenu et comparé au modèle de contrat standard, de façon à déterminer si le contrat cible correspond au modèle de contrat standard (S20); et si le contrat cible ne correspond pas au modèle de contrat standard, un message de rappel sur des informations de contrat incohérentes est généré et affiché, de façon à rappeler à un utilisateur que le contrat cible est anormal (S30). Le procédé compare automatiquement le contrat cible à vérifier avec le modèle de contrat standard de la version correspondante pour vérifier le contrat et rappeler une anomalie de contrat, ce qui permet d'éviter des pertes économiques provoquées par une incohérence de versions électroniques et d'améliorer l'efficacité de vérification et l'expérience d'utilisateur en évitant une vérification manuelle.
PCT/CN2018/123279 2018-09-28 2018-12-25 Procédé, dispositif et appareil de vérification de cohérence de données de contrat et support d'enregistrement Ceased WO2020062661A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811140354.0A CN109656931B (zh) 2018-09-28 2018-09-28 合同数据一致性的核实方法、装置、设备及存储介质
CN201811140354.0 2018-09-28

Publications (1)

Publication Number Publication Date
WO2020062661A1 true WO2020062661A1 (fr) 2020-04-02

Family

ID=66110028

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/123279 Ceased WO2020062661A1 (fr) 2018-09-28 2018-12-25 Procédé, dispositif et appareil de vérification de cohérence de données de contrat et support d'enregistrement

Country Status (2)

Country Link
CN (1) CN109656931B (fr)
WO (1) WO2020062661A1 (fr)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110222692A (zh) * 2019-05-21 2019-09-10 深圳壹账通智能科技有限公司 一种合同校验方法及相关设备
CN110363646A (zh) * 2019-06-19 2019-10-22 平安普惠企业管理有限公司 单证异常排查方法、装置、设备和存储介质
CN110288601A (zh) * 2019-08-08 2019-09-27 中国盲文出版社 盲文读物印制质量自动检查系统、方法和计算机可读介质
CN111539694B (zh) * 2020-04-29 2023-10-20 重庆忽米网络科技有限公司 基于区块链记录贡献与身份标识的协同工作方法及系统
CN113065323B (zh) * 2021-03-17 2022-09-23 平安普惠企业管理有限公司 合同模板数据的导入方法、装置、设备以及存储介质
CN117114603A (zh) * 2023-08-07 2023-11-24 广州锦成信息技术有限公司 电子图纸单轨制管理方法、装置、存储介质以及设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103064660A (zh) * 2011-10-21 2013-04-24 镇江金软计算机科技有限责任公司 一种基于数组技术的电子合同版本控制方法
WO2017145063A1 (fr) * 2016-02-22 2017-08-31 Tata Consultancy Services Limited Procédé et système de gestion de contrat dans un marché de données
CN107480950A (zh) * 2017-08-15 2017-12-15 天津大学 自动审核系统及方法
CN107608958A (zh) * 2017-09-07 2018-01-19 湖南湘君奕成信息技术有限公司 基于条款统一建模的合同文本风险信息挖掘方法和系统
CN107870927A (zh) * 2016-09-26 2018-04-03 上海泓智信息科技有限公司 文件评估方法和装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103136317A (zh) * 2011-11-29 2013-06-05 北京建龙重工集团有限公司 工程管理系统工程合同在线审批信息化实现方法
CN105184503A (zh) * 2015-09-24 2015-12-23 北京华通伟业科技发展有限公司 合同管理系统和使用合同管理系统执行合同管理的方法
CN105610578B (zh) * 2016-01-25 2019-05-03 杭州复杂美科技有限公司 区块链信息存证及隐私保护方法
CN106980604B (zh) * 2017-03-30 2019-12-31 理光图像技术（上海）有限公司 合同内容校阅装置
CN107463545A (zh) * 2017-06-21 2017-12-12 杭州大搜车汽车服务有限公司 一种在线合同文档的生成方法、电子设备及存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103064660A (zh) * 2011-10-21 2013-04-24 镇江金软计算机科技有限责任公司 一种基于数组技术的电子合同版本控制方法
WO2017145063A1 (fr) * 2016-02-22 2017-08-31 Tata Consultancy Services Limited Procédé et système de gestion de contrat dans un marché de données
CN107870927A (zh) * 2016-09-26 2018-04-03 上海泓智信息科技有限公司 文件评估方法和装置
CN107480950A (zh) * 2017-08-15 2017-12-15 天津大学 自动审核系统及方法
CN107608958A (zh) * 2017-09-07 2018-01-19 湖南湘君奕成信息技术有限公司 基于条款统一建模的合同文本风险信息挖掘方法和系统

Also Published As

Publication number Publication date
CN109656931B (zh) 2024-07-05
CN109656931A (zh) 2019-04-19

Similar Documents

Publication Publication Date Title
WO2020062661A1 (fr) Procédé, dispositif et appareil de vérification de cohérence de données de contrat et support d'enregistrement
WO2020062658A1 (fr) Procédé et appareil de génération de contrat, dispositif et support de stockage
WO2020147383A1 (fr) Procédé, dispositif et système d'examen et d'approbation de processus utilisant un système de chaîne de blocs, et support de stockage non volatil
WO2020029585A1 (fr) Procédé et dispositif de modélisation de fédération de réseau neuronal faisant intervenir un apprentissage par transfert et support d'informations
WO2021003975A1 (fr) Procédé de test d'interface de passerelle, dispositif terminal, support de stockage et appareil
WO2020015067A1 (fr) Procédé d'acquisition de données, dispositif, équipement et support de stockage
WO2020224246A1 (fr) Procédé et appareil de gestion de données fondée sur une chaîne de blocs, dispositif et support d'informations
WO2020119115A1 (fr) Procédé, dispositif, appareil de vérification de données, et support de stockage
WO2020147385A1 (fr) Procédé et appareil d'entrée de données, terminal et support d'informations lisible par ordinateur
WO2021003956A1 (fr) Procédé, appareil et dispositif de gestion d'informations de produit et support d'enregistrement
WO2020087978A1 (fr) Procédé, appareil et dispositif de génération de modèle de vérification des contrôles des risques, et support d'informations
WO2020087981A1 (fr) Procédé et appareil de génération de modèle d'audit de contrôle de risque, dispositif, et support de stockage lisible
WO2020015064A1 (fr) Procédé de traitement de défaillance de système, appareil, dispositif et support d'informations
WO2020062642A1 (fr) Procédé, dispositif et équipement à base de chaîne de blocs pour signer des documents électroniques, et support d'informations
WO2019024485A1 (fr) Procédé et dispositif de partage de données, et support de stockage lisible par ordinateur
WO2020233089A1 (fr) Procédé et appareil de création de jeu de test, terminal et support de stockage lisible par ordinateur
WO2019024126A1 (fr) Procédé de gestion d'informations de connaissance basé sur une chaîne de blocs, et terminal et serveur
WO2019174090A1 (fr) Procédé, appareil et dispositif de commande de partage de fichier de capture d'écran, et support de stockage informatique
WO2020253120A1 (fr) Procédé, système et dispositif d'enregistrement de page web, et support de stockage informatique
WO2021027134A1 (fr) Procédé, appareil et dispositif de stockage de données et support d'enregistrement informatique
WO2020233073A1 (fr) Procédé, dispositif et appareil de traitement de test d'environnement de chaîne de blocs, et support de stockage
WO2020107591A1 (fr) Procédé, appareil, dispositif de limitation de double assurance et support d'informations lisible
WO2020119369A1 (fr) Procédé, appareil et dispositif de positionnement de défaut de fonctionnement et de maintenance informatique intelligent, et support de stockage lisible
WO2020019405A1 (fr) Procédé, dispositif, appareil de surveillance de base de données et support d'informations informatique
WO2020042464A1 (fr) Procédé, appareil et dispositif d'interaction de données, et support d'informations lisible

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18934847

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18934847

Country of ref document: EP

Kind code of ref document: A1