Function verification method and device, electronic equipment, storage medium and computer program product

Abstract

The embodiment of the invention provides a certificate verification method, a certificate verification device, electronic equipment, a chip, a storage medium and a computer program product. The method comprises the following steps: receiving a first operation; the first operation is used for importing a plurality of issues and indicating to verify the plurality of issues; the first operation is responded, a thread pool is called, and verification processing is carried out on the multiple issues in batches; wherein if a first issue in a first batch meets a first condition, the first issue is rejected from the first batch, and the first issue is put into a next batch for verification processing, so that issues which are abnormal opponent parties are verified in different batches; the first batch is a batch which is currently subjected to verification processing.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of auditing technology, and specifically to a confirmation verification method, a confirmation verification device, an electronic device, a storage medium, and a computer program product. Background Art

[0002] In the field of audit technology, there are often tens of thousands of confirmations in a single project. There is no efficient solution for verifying such a large number of confirmations. Summary of the invention

[0003] Embodiments of the present application provide a confirmation verification method, a confirmation verification device, an electronic device, a chip, a storage medium, and a computer program product.

[0004] The confirmation verification method provided in the embodiment of the present application includes:

[0005] Receiving a first operation; the first operation is used to import multiple letters and instruct to verify the multiple letters;

[0006] In response to the first operation, the thread pool is called to verify and process the multiple letters in batches; wherein, if the first letter in the first batch meets the first condition, the first letter is removed from the first batch and put into the next batch for verification and processing, so that the letters from abnormal counterparties are verified in different batches; the first batch is the batch currently being verified and processed.

[0007] The letter confirmation verification device provided in the embodiment of the present application comprises:

[0008] Interaction module: used for receiving a first operation; the first operation is used for importing multiple letters and instructing to verify the multiple letters;

[0009] Processing module: used to respond to the first operation, call the thread pool, and verify and process the multiple letters in batches; wherein, if the first letter in the first batch meets the first condition, the first letter will be removed from the first batch and put into the next batch for verification and processing, so that the letters of abnormal counterparties are verified in different batches; the first batch is the batch currently being verified and processed.

[0010] The electronic device provided in the embodiment of the present application includes: a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute any letter of confirmation verification method provided in the embodiment of the present application.

[0011] The chip provided in the embodiment of the present application includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes any confirmation verification method provided in the embodiment of the present application.

[0012] The storage medium provided in the embodiments of the present application is used to store a computer program, and the computer program enables a computer to execute any confirmation verification method provided in the embodiments of the present application.

[0013] The computer program product provided in the embodiments of the present application includes a computer program, which, when executed by a processor, implements any of the confirmation verification methods provided in the embodiments of the present application.

[0014] Through the letter of confirmation verification method provided in the embodiment of the present application, the thread pool is called to verify the letters in batches, and an efficient letter of confirmation verification method is provided for a large number of letters of confirmation. In addition, a first condition is set so that the letters sent by abnormal counterparties are verified through different batches, so that abnormal records are recorded only once, thereby avoiding doubling of abnormal records and avoiding waste of resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0016] Figure 1 A schematic diagram of the basic process of confirmation provided in the embodiment of the present application;

[0017] Figure 2 A schematic diagram of the implementation flow of the confirmation verification method provided in the embodiment of the present application;

[0018] Figure 3 A schematic diagram of an asynchronous task page provided in an embodiment of the present application;

[0019] Figure 4 A schematic diagram of the process of sending a letter for verification provided in an embodiment of the present application;

[0020] Figure 5 A logical diagram of comparing the letter provided in the embodiment of the present application with the enterprise employee list of the project issuer (the company corresponding to the project);

[0021] Figure 6 A schematic diagram of the reply verification process provided in the embodiment of the present application;

[0022] Figure 7 A schematic diagram of the document comparison process provided in the embodiment of the present application;

[0023] Figure 8A schematic diagram of a document comparison page provided in an embodiment of the present application;

[0024] Fig. 9 A schematic diagram of a verification process for a verification exception type of "inconsistent mailing addresses for reply letters from the same letter recipient" provided in an embodiment of the present application;

[0025] Fig.10 A schematic diagram of a judgment page for an exception type of "addresses of different letter recipients are similar or repeated" provided in an embodiment of the present application;

[0026] Fig.11 A schematic diagram of the user rights allocation process provided in the embodiment of the present application;

[0027] Fig.12 A schematic diagram of a page for importing a mailing list provided in an embodiment of the present application;

[0028] Fig.13 A schematic diagram of the detailed list of other confirmation letters provided in the embodiments of the present application;

[0029] Fig.14 A schematic diagram of the detailed list of customers, suppliers and accounts receivable confirmation provided in the embodiment of the present application;

[0030] Fig.15 A schematic diagram of the detailed list of the bank confirmation letter provided in the embodiment of the present application;

[0031] Fig.16 A schematic diagram of a page for citing external abnormal history evidence provided in an embodiment of the present application;

[0032] Fig.17 A schematic diagram of a report management page provided in an embodiment of the present application;

[0033] Fig.18 A schematic diagram of a page for uploading metadata of objective documents of a confirmation provided in an embodiment of the present application;

[0034] Fig.19 A schematic diagram of the file archiving process provided in the embodiment of the present application;

[0035] Fig. 20 A schematic diagram of the structure of the confirmation verification device provided in the embodiment of the present application;

[0036] Fig.21 A schematic structural diagram of an electronic device provided in an embodiment of the present application;

[0037] Fig. 22 A schematic structural diagram of a chip provided in an embodiment of the present application. DETAILED DESCRIPTION

[0038] The following will describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0039] It should be noted that in the embodiments of the present application, the term "and / or" is only a description of the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the embodiments of the present application, the character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0040] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between two items, or an association relationship between the two items, or a relationship between indication and being indicated, configuration and being configured, and the like.

[0041] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all belong to the protection scope of the embodiments of the present application.

[0042] Confirmation is the process by which a certified public accountant obtains and evaluates audit evidence through statements directly from a third party on relevant information and existing conditions in order to obtain information about items that affect the financial statements or related disclosures.

[0043] The current confirmation verification has problems such as the business processes of various project teams sending letters are not unified and standardized, the confirmation templates are not unified and standardized, the confirmation process is difficult to control and track, there are many repetitive operations, the receiving, sending and following up of letters occupy a lot of resources, and the operational efficiency is low; it is difficult to identify the authenticity of the reply subject (especially if the subject is an individual); there is a risk of fraud in traditional mailing confirmations, and offline express confirmations do not have a unique identification code and may be tampered with or replaced; it is difficult and inefficient to track the logistics track of the confirmation, and the logistics track of both the confirmation mailer and the reply letter needs to be tracked offline, and the delivery status cannot be obtained in time, and some express logistics tracks cannot be queried after a period of time; the reply letter is easy to lose and difficult to find. After the confirmation is sent, it needs to be manually tracked and updated offline, which makes it easy for the confirmation to be lost, and it needs to be archived offline, which is not convenient for future retrieval.

[0044] For the verification of letters sent in confirmation letters, there are requirements of "large quantity", "speed requirements" and "verification needs to be accurate", and there is currently no efficient solution.

[0045] refer to Figure 1 , Figure 1 The basic flow chart of the confirmation provided in the embodiment of the present application is as follows: Figure 1 As shown, after the project team imports the confirmation template to batch prepare letters or creates a single confirmation form to generate a confirmation record, it will conduct an abnormality check on the letter information. If no abnormality is found, it will be directly approved by the project leader and enter the letter preparation stage. If an abnormality is found, the project team will verify and fill in the abnormal explanation, and then submit it to the project leader for approval before entering the letter preparation environment. At this time, the project team will hand over the generated confirmation attachment printout to the enterprise for stamping|signing for authorization, and finally send it to the confirmation center by express delivery, and the confirmation center will independently send the letter and receive the reply letter (the project team will go to the letter-receiving unit for confirmation and record the relevant drafts). After the confirmation center receives the company's stamped letter, it will enter the system, arrange for express delivery (or mail) to send the letter, receive the reply letter from the letter-receiving unit, conduct an abnormality check on the reply letter, and record it in the system. Finally, the confirmation center will archive the letter.

[0046] Figure 2 A schematic diagram of the implementation flow of the confirmation verification method provided in the embodiment of the present application is as follows: Figure 2 As shown, the method comprises the following steps:

[0047] Step 201: Receive a first operation; the first operation is used to import multiple letters and instruct to verify the multiple letters.

[0048] Here, multiple letters can be multiple letters within a project.

[0049] The first operation is that the user imports multiple letters, instructing to verify the multiple letters. For example, the basic information of the confirmation letter includes the investment banking project information in the investment banking business system, including batch records of project type, project stage, letter sending stage, letter sending year, project number, project team members and project leader information, confirmation stage, project name and other information. For an investment banking project, there can be multiple basic information of confirmation letters (i.e., multiple batches) based on the letter sending year, letter sending stage, and project stage, and there can be multiple confirmation records under each basic information of confirmation letter.

[0050] Step 202: In response to the first operation, the thread pool is called to verify and process the multiple letters in batches; wherein, if the first letter in the first batch meets the first condition, the first letter is removed from the first batch and put into the next batch for verification and processing, so that the letters of abnormal counterparties are verified in different batches; the first batch is the batch currently being verified and processed.

[0051] In the embodiment of the present application, the thread pool includes multiple threads. The sent letters are put into the thread pool in batches for verification, and the asynchronous thread is started for processing. After that, the user can view the verification results on the asynchronous task page. Figure 3 , Figure 3 A schematic diagram of an asynchronous task page provided in an embodiment of the present application.

[0052] For example, a thread pool of 20 threads is set at the beginning of the verification to provide concurrent and multi-threaded processing. In actual application, other numbers of thread pools may also be set, and the embodiment of the present application does not limit this.

[0053] There are requirements for letter verification such as "large volume", "speed requirements" and "accurate verification". For example, for the verification items of "duplicate recipients in different units", "duplicate contact information in different units", "similar or duplicate addresses in different units", "inconsistent recipients in the same unit", "inconsistent contact information in the same unit" and "inconsistent addresses in the same unit", each thread will check the letter currently being verified, which will involve comparison and verification of counterparty information of other letters with the same project or the same basic information of the letter (that is, this batch of letters submitted in this batch).

[0054] If all the letters to be processed are simply put into the thread pool for parallel processing, and if a batch of records contains a counterparty letter with the same information that is also being verified in another thread running at the same time, each will find the corresponding other letter (i.e. the counterparty letter) and be recorded as a verification exception, ultimately doubling the number of exception records.

[0055] Here, the verification of abnormalities refers to some abnormal information found by checking and verifying the relevant contents of the letters and replies during the confirmation process. According to the abnormality type, it is divided into "recipients of different lettered units are repeated", "contact information of different lettered units is repeated", "addresses of different lettered units are similar or repeated", "recipients of the same lettered unit are inconsistent", "contact information of the same lettered unit is inconsistent", "address of the same lettered unit is inconsistent", "name of the lettered unit is abnormal", "address of the lettered unit is abnormal", "email address of the lettered unit is abnormal", "mail address of the lettered unit is abnormal", "mail address of the lettered unit is inconsistent with the address of the lettered unit", "sender of the letter is inconsistent with the recipient of the lettered unit", "sender's phone number of the lettered unit is inconsistent with the recipient's phone number of the lettered unit", "stamping is not in compliance with regulations (official seal / financial seal / banking business seal)", "stamping unit of the lettered unit is inconsistent with the confirmed unit", "mail address of the lettered unit is inconsistent with the mailbox of the lettered unit", "response letter result is inconsistent", etc., all of which need to be verified during the confirmation process. The letter sent is compared with other letters in turn according to the abnormality type. If a letter sent that meets these problems is found, an abnormal record will be generated, including the corresponding abnormality type and the corresponding multiple letters sent.

[0056] An abnormal counterparty refers to a letter in an abnormal record. For example, to determine whether two or more addresses with different descriptions correspond to the same unit (Room XXX, No. XX, a certain street in a certain city in a certain province, Room XX, Building XX, a certain street in a certain city in a certain province), because the recipient of a letter will only write one recipient address, so if there are two or more addresses that match the abnormal situation related to the address in the verification abnormality, then the letters corresponding to these addresses are called abnormal counterparties to each other in this abnormal record, that is, for a specific verification abnormality type, there should not be a single record, there must be another one or more corresponding letters, and these letters are abnormal counterparties to each other.

[0057] Therefore, the embodiment of the present application sets a first condition, and for the batch currently being verified, the letters that meet the first condition are removed from the batch currently being verified and verified in the next batch.

[0058] Exemplary, reference Figure 4 , Figure 4 The flowchart of the letter verification provided in the embodiment of the present application first finds out 50 letters that have not been processed, then traverses these 50 records in order, removes the records with abnormal counterparties, and puts the letters without abnormal counterparties into the thread pool for concurrent verification; puts the verification information of the first record into the cache, and the verification information includes: "recipient name, recipient phone number, name of the letter-receiving unit, and receiving address of the letter-receiving unit"; then directly puts it into a thread to start processing and verification, and the second record will compare the verification information of this letter with the information in the cache one by one, without involving the corresponding verification. If there is an abnormality in the verification, it will be put into the second thread for processing and verification. If a corresponding verification abnormality is found, for example, the recipients are different, but the recipient information (name, mobile phone number) is the same or the recipients' addresses are the same, it means that there is an abnormality, and it will be skipped directly. The following letter will not be processed in this batch. This is because the thread of the corresponding record that has initiated the verification process will find the record with the corresponding verification abnormality during the verification process. If two letters with related abnormalities are processed in the same batch at the same time, they will find each other as the abnormal counterparty, and the final abnormal records will be doubled. Similarly, after all 50 records in this batch are traversed and all triggered threads have completed processing, the next batch of 50 letters to be processed will be found. The letters that were skipped in the previous batch will be found in the next batch, avoiding the problem of missed processing.

[0059] Based on this, in an optional implementation manner of the present application, the calling thread pool verifies and processes the multiple letters in batches; wherein, if the first letter in the first batch meets the first condition, the first letter is removed from the first batch and placed in the next batch for verification, including:

[0060] For the unverified outgoing letters, a preset number of outgoing letters are selected as the first batch for verification;

[0061] For the first outgoing letter in the first batch, the verification information of the first outgoing letter is put into a cache, and the first outgoing letter is put into a thread for verification;

[0062] For each of the other outgoing letters in the first batch, a first process is performed until each outgoing letter in the first batch completes the first process; the first process includes:

[0063] Compare the verification information of the outgoing letter with the verification information in the cache;

[0064] If there is an abnormality, the letter is judged to meet the first condition, and the letter is removed from the first batch and put into the next batch for verification;

[0065] If there is no abnormality, the verification information of the sent letter is put into the cache, and the sent letter is put into an idle thread for verification.

[0066] By using batches, conditional concurrent processing of multiple threads, and accurate processing by each thread, we can achieve relative speed and absolute business accuracy, which not only ensures fast and accurate data processing, but also ensures stable verification and prevents memory overflow problems.

[0067] In terms of verifying abnormal details, for example, "the recipients of the same letter-receiving unit are inconsistent, the contact information of the same letter-receiving unit is inconsistent, and the address of the same letter-receiving unit is inconsistent", securities investment banks also have the concept of projects, which need to be compared with the most recent corresponding records under the same project, with a wider comparison scope; securities investment banks also require that the submitted confirmation record information needs to be compared with the employee list of the issuer to verify whether there is any duplication of recipients or contact information;

[0068] Therefore, in the thread, in addition to comparing the letter sent with other letters sent, you can also compare the letter sent with the last letter sent by the corresponding unit of the letter, and compare the letter sent with the corporate employee list of the project issuer (the company corresponding to the project) to improve the accuracy of the letter verification.

[0069] refer to Figure 5 , Figure 5This is a logical diagram for comparing the letter provided in the embodiment of the present application with the corporate employee roster of the project issuer (the company corresponding to the project). If there is a duplication between the recipient of the letter and the corporate employee roster of the project issuer (the company corresponding to the project), an exception is prompted and an exception explanation needs to be filled in.

[0070] Based on this, in an optional implementation manner of the present application, the verification process in the thread includes:

[0071] Compare the letter with other letters in the multiple letter issuance records; and / or compare the letter with the last letter issued by the corresponding unit of the letter; and / or compare the letter with the employee list of the project issuer.

[0072] In the present application examples, reference Figure 6 , Figure 6 The reply verification process diagram provided in the embodiment of the present application can also be processed by the thread pool. Considering that the confirmation center receives the reply letters and enters them one by one, when the user enters a reply letter, an asynchronous reply information verification task is triggered through the system event mechanism, and the "reply sender's name, contact information, mailing address" and other information are compared with the information when the letter was sent, and abnormal records are made for the discrepant data. That is, by dispersing tasks and processing them one by one, the pressure of verification is reduced, and the smooth generation of the final verification result is guaranteed.

[0073] Based on this, in an optional implementation manner of the present application, the method further includes:

[0074] receiving a second operation; the second operation is used to import a reply letter and instruct to verify the reply letter;

[0075] In response to the second operation, the reply letter is compared and verified with the corresponding letter to obtain a verification result of the reply letter.

[0076] Both the outgoing letter and the reply letter include documents. When a reply letter is received, in addition to verifying the sender, recipient, address and other verification information, it is also necessary to compare the reply document with the outgoing letter document to ensure the correctness of the reply document. Manual comparison is labor-intensive and it is difficult to guarantee the correctness of the comparison results.

[0077] refer to Figure 7 , Figure 7 A schematic diagram of the document comparison process provided in the embodiment of the present application is shown in FIG. Figure 7 As shown, document comparison includes the following steps:

[0078] Step 701: Upload.

[0079] The user scans and uploads the document.

[0080] Step 702: Verify whether the document meets the requirements.

[0081] Determine whether the document is an outgoing letter document or a reply letter document. If it is an outgoing letter document or a reply letter document, execute step 703; if it is not an outgoing letter document or a reply letter document, do not perform the comparison process;

[0082] Step 703: Obtain the chapter tree of the letter-sending document.

[0083] Here, if the document uploaded by the user is a reply document, the chapter tree of the corresponding outgoing document is obtained from the database.

[0084] If the document uploaded by the user is a letter document, the letter document will be parsed and the chapter tree corresponding to the letter document will be constructed and saved for subsequent reply letter comparison; if the letter document is not a PDF document, the letter document can be converted into a PDF document and then the chapter tree can be constructed, for example, converting a Word document into a PDF document.

[0085] Step 704: Document comparison.

[0086] The document includes text and / or table, and the comparison includes two parts, the first part is the document comparison, and the second part is the table comparison.

[0087] Document comparison can use the difflib module that comes with Python. The classes and methods provided by the difflib module are used to perform differential comparison of sequences. It can compare files and generate differential result text or differential comparison pages in HTML format. As a built-in library of Python, it has powerful text comparison functions. The text comparison algorithm is used to compare text files and generate difference reports. Compare the text under the chapter tree, and take the highest similarity pair as the difference comparison. If it is less than the threshold, it is added or missing.

[0088] Similarity can be calculated using the following formula: Similarity = 2.0*M / T (M represents the number of characters that can match the two strings, and T represents the total number of characters)

[0089] Table comparison can be divided into three categories: equal number of rows and columns; equal number of rows but unequal number of columns; equal number of columns but unequal number of rows. The steps of table comparison are: (1) Determine whether the table data in the two documents are consistent; (2) Determine whether the page numbers of the two tables are less than or equal to 5 pages; (3) Determine whether the two tables are similar tables. If one or more of the following three conditions are met, the two tables are judged to be similar tables: a) the number of rows is equal, the number of columns is equal, the similarity of the first row is greater than or equal to 0.85, and the similarity of the first column is greater than or equal to 0.80; b) the number of rows differs by less than or equal to 3 rows, the number of columns is equal, the similarity of the first column is greater than or equal to 0.85, and the similarity of the first row is greater than or equal to 0.75; c) the number of rows is equal, the number of columns differs by less than or equal to 2 columns, the similarity of the first row is greater than or equal to 0.85, and the similarity of the first column is greater than or equal to 0.65. (4) Obtain the data of the table difference points. If the similarity of each row of the two tables is greater than 0.80 and the row number difference is less than or equal to 3, then perform a comparison and obtain the remaining multiple rows and columns of data. The table comparison algorithm compares a row or the entire table as a unit. This is passed as a unit to the difflib module to obtain the similarity. After obtaining all the similarities, compare whether the similarity meets the requirements.

[0090] refer to Figure 8 , Figure 8 This is a schematic diagram of a document comparison page provided in an embodiment of the present application. Users can refer to the comparison results and retain the comparison information.

[0091] In an optional implementation manner of the present application, the reply letter includes: a document, and the comparison and verification of the reply letter with the outgoing letter corresponding to the reply letter includes:

[0092] Comparing the text of the document in the reply record with the text of the document in the corresponding outgoing record to obtain a text comparison result;

[0093] The table of the document in the reply record is compared with the table of the document in the corresponding outgoing record to obtain a table comparison result.

[0094] This application uses the intelligent document comparison function to automatically traverse qualified reply letters for all reply letters that have been entered and confirmed by the project team, and trigger a content difference comparison between the receipt document and the reply document in each record, so that the confirmation center staff can see the difference between the content of the two documents, the receipt and the reply, through the left and right layout of the page, and simultaneously provide multiple confirmation items for the confirmation center staff to confirm one by one for quality inspection and leave traces. It replaces the original quality inspection method that requires downloading or previewing two files first, then manually checking the differences, and then confirming the differences. It greatly reduces the workload of the confirmation center staff and improves the speed and accuracy of quality inspection business processing.

[0095] In the embodiment of the present application, the verification anomaly types in the letter verification process include one or more of the following: "recipients of different correspondent units are repeated", "contact information of different correspondent units is repeated", "addresses of different correspondent units are similar or repeated", "recipients of the same correspondent unit are inconsistent", "contact information of the same correspondent unit is inconsistent", "address of the same correspondent unit is inconsistent", "name of the correspondent unit is abnormal", "address of the correspondent unit is abnormal", "email address of the correspondent unit is abnormal", "reply mail address is inconsistent with address of the correspondent unit", "reply sender is inconsistent with recipient of the correspondent unit", "reply sender's phone number is inconsistent with recipient's phone number of the correspondent unit", "stamping is not compliant (official seal / finance seal / banking seal)", "reply stamp unit is inconsistent with confirmed unit", "reply email address is inconsistent with email address of the correspondent unit", "reply result is inconsistent", "reply mail address of the same correspondent unit is inconsistent", etc. In the letter verification process, the process of determining whether multiple addresses are the same is included. In the related technology, for the several addresses involved, only the inclusion and exclusion judgment is made in the text. If there is an inclusion relationship, the addresses are judged to be different. Different street descriptions for the same address will also be erroneously reported as abnormalities, which increases a large number of invalid false alarms and requires additional means to further eliminate them.

[0096] An embodiment of the present application provides a method for determining whether addresses are the same. First, it is determined whether there is a containment and being contained relationship among multiple address texts. If there is no containment and being contained relationship, it is determined that the multiple addresses are different. If there is a containment and being contained relationship, it is determined whether the multiple address texts exist in different addresses belonging to the same unit marked by artificial dimensions. If so, it is determined that the multiple addresses are the same. If not, it is determined whether the distance between the multiple addresses is greater than a preset distance. If the distance between the multiple addresses is greater than the preset distance, it is determined that the multiple addresses are different. If the distance between the multiple addresses is less than or equal to the preset distance, it is determined that the multiple addresses are the same, that is, the multiple addresses are similar or repeated.

[0097] In the embodiment of the present application, the longitude and latitude of multiple addresses can be obtained, and the judgment is made based on the distance between the longitude and latitude of the multiple addresses. Exemplarily, the preset distance is set to 100 meters.

[0098] refer to Fig. 9 , Fig. 9 The verification process diagram for the verification exception type of "the same letter recipient's reply mailing address is inconsistent" provided in the embodiment of the present application is as follows, Fig. 9 As shown, the following steps are included:

[0099] Step 901: Determine whether there is a containment relationship between two addresses.

[0100] Determine whether the address texts of the return mailing addresses of two confirmation letters of the same correspondence recipient have a containment and being contained relationship. If so, it is determined that the return mailing addresses of the two confirmation letters are the same and the exception does not apply. If not, execute step 902.

[0101] Step 902: Determine whether the two addresses exist in manually maintained different addresses belonging to the same unit.

[0102] If the address text of the reply mailing address of two confirmation letters for the same addressed unit exists in the manually maintained different addresses belonging to the same unit, then the reply mailing addresses of the two confirmation letters are judged to be the same and the exception does not occur; if the address text of the reply mailing address of two confirmation letters for the same addressed unit does not exist in the manually maintained different addresses belonging to the same unit, execute step 903.

[0103] Step 903: Determine whether the distance between the two addresses is greater than 100 meters.

[0104] If it is less than 100 meters, the reply mailing addresses of the two confirmation letters are judged to be the same and the exception does not occur; if it is greater than 100 meters, the reply mailing addresses of the two confirmation letters are judged to be the same and the exception occurs.

[0105] Step 904: Generate verification results.

[0106] Generate verification results based on abnormal judgment results.

[0107] refer to Fig.10 , Fig.10 The schematic diagram of the judgment page for the exception type of "similar or repeated addresses of different units being notified" provided in the embodiment of the present application includes the exception content, the unit being notified, the serial number, the confirmation status, the exception description, etc., and also includes the "exceptional description supporting draft". When an exception occurs, the person in charge needs to explain the exception and upload a draft file supporting the exception description to enhance the credibility of the exception description.

[0108] Based on this, in an optional implementation manner of the present application, the process of sending a letter for verification or replying a letter for verification includes address verification, and the process of determining whether the addresses are the same is as follows:

[0109] Determine whether there is a containment relationship between multiple addresses;

[0110] If there is no inclusion relationship, it is determined that the multiple addresses are not the same; or, if there is an inclusion relationship, it is determined whether the multiple addresses are different addresses belonging to the same unit marked by manual dimensions;

[0111] If the multiple addresses are different addresses belonging to the same unit marked by artificial dimensions, determining that the multiple addresses are the same; or, if the multiple addresses are different addresses belonging to the same unit marked by artificial dimensions, determining whether the distance between the multiple addresses is greater than a preset distance;

[0112] If the distance between the multiple addresses is greater than a preset distance, it is determined that the multiple addresses are different; or if the distance between the multiple addresses is less than or equal to the preset distance, it is determined that the multiple addresses are the same.

[0113] By accessing the map software to obtain the longitude and latitude of each address, and then calculating the relative distance to determine whether it is the same address, for example, if the distance between two addresses is less than 100 meters, the two addresses are determined to be the same address, so that multiple addresses with different text descriptions (for example, one is the street of the west gate and the other is the street of the east gate, the text descriptions are different, but they are actually the same unit) will no longer be identified as abnormal.

[0114] Maintain some commonly used mapping relationships between the receiving addresses of the letter recipients and their reply mailing addresses (some banks have a unified confirmation center to process reply confirmations, so the reply address is not necessarily the receiving address of the letter recipient). In this way, when multiple different receiving addresses of the same bank (such as branch banks) correspond to the same reply mailing address, they will be identified as normal data and will no longer be judged as abnormal.

[0115] The embodiment of the present application reduces abnormal false alarms by refining the address comparison logic.

[0116] refer to Fig.11 , Fig.11 A flowchart of user rights allocation provided in an embodiment of the present application is shown in FIG. Fig.11 As shown, the following steps are included:

[0117] Step 1101: Receive a login operation.

[0118] The user performs a login operation and determines whether the user login operation exists. If so, execute step 1102; if not, return to the login page.

[0119] Step 1102: Determine the login account type.

[0120] If the login account is an employee of the audit company or a partner,

[0121] Step 1103: Assign roles and permissions to the logged-in user.

[0122] If the login account is an employee of the audit company, the internal employee roles and permissions of the audit company are obtained and allocated to the login user; if the login account is an employee of a partner, such as the unit being sent a letter, the partner employee roles and permissions are obtained and allocated to the login user.

[0123] By connecting to the company's internal employee account interface and performing daily incremental synchronization, the company's own employee accounts are initialized and subsequently maintained. By marking accounts for classification, support for external partner accounts is added. The relevant partner accounts can be manually created by the administrator or person in charge and the relevant functional permissions can be opened; for the company's own employee accounts, the corresponding confirmation basic information and relevant functional permissions of the relevant project personnel are automatically opened by connecting to the audit unit. When a person logs in to the system, the account type will be automatically determined. If it is a partner account, it will automatically guide it to the electronic confidentiality agreement signing page to fill in the relevant information, so as to achieve the distinction and maintenance of different permission accounts for the company's own employees and partner employees. By (automatically + manually) configuring the corresponding roles (administrator, project leader, project member, department head, confirmation center, internal control department personnel), and then configuring the menu permissions for the roles, fine-grained management of accounts and permissions in the system can be achieved.

[0124] Based on this, in an optional implementation manner of the present application, the method further includes:

[0125] Receive login operations and determine the account type of the logged-in user;

[0126] If the account type of the logged-in user is an internal user, obtain the role of the internal user and provide the logged-in user with permissions corresponding to the role of the internal user;

[0127] If the account type of the logged-in user is an external user, the role of the external user is obtained, and permissions corresponding to the role of the external user are provided to the logged-in user.

[0128] In the embodiment of the present application, a letter making service is also provided, and the user can make a letter in the letter making service interface. Fig.12 , Fig.12 A schematic diagram of a page for importing a mailing list provided in an embodiment of the present application, such as Fig.12 As shown, users can select the confirmation letter classification, which includes one or more of the following: customer, supplier and accounts receivable confirmation letters, bank confirmation letters and other confirmation letters. It supports adding corresponding types of confirmation letters by importing from Excel templates and creating new pages.

[0129] refer to Fig.13 , Fig.13 A detailed schematic diagram of a list of other confirmation letters provided in the embodiments of this application, such as Fig.13As shown, the list details of other confirmation letters include: whether it is a material confirmation, whether it is a contract confirmation, whether it is overseas, etc.

[0130] refer to Fig.14 , Fig.14 A detailed schematic diagram of the list of customers, suppliers and accounts receivable provided in the embodiment of the present application, such as Fig.14 As shown, the list details of the confirmation of customers, suppliers and accounts receivable include: unit serial number, whether overseas, transaction currency, account currency, etc., supporting multiple currencies and domestic + foreign situations. Correspondingly, according to the logic of sending letter verification exceptions and amount verification when replying after creating a new supplier account confirmation record, the corresponding business logic and verification logic are added.

[0131] refer to Fig.15 , Fig.15 A detailed diagram of the list of bank confirmation letters provided in the embodiment of the present application is shown in FIG. Fig.15 As shown, the details of the bank confirmation letter confirmation list include: "whether it is overseas, currency", supporting multiple currencies and domestic + foreign situations. Correspondingly, according to the logic of letter verification exceptions and amount verification at the time of reply after creating a new supplier account confirmation record, the corresponding business logic and verification logic are added.

[0132] Based on this, in an optional implementation manner of the present application, the method further includes:

[0133] Provide letter preparation services; the letter preparation services include one or more of the following: customer, supplier and current account confirmation letters, bank confirmation letters and other confirmation letters; among which,

[0134] The list of confirmations of customers, suppliers and accounts receivable includes one or more of the following: unit serial number, whether it is overseas, transaction currency, and current account currency;

[0135] The list of bank confirmation letters includes: whether it is overseas and / or currency;

[0136] The list of other confirmation letters includes one or more of the following: whether it is a material confirmation, whether it is a contract confirmation, and whether it is overseas.

[0137] refer to Fig.16 , Fig.16 A schematic diagram of a page for citing external abnormal history evidence provided in an embodiment of the present application, such as Fig.16 As shown, to facilitate user operation, in actual application, for external exceptions with the same letter-receiving unit and the same exception type, users can directly reference the previous status to process the exception evidence associated with the records of sent letters and replied letters, without having to re-upload the relevant verification exception explanation evidence each time.

[0138] refer to Fig.17 , Fig.17 A schematic diagram of the report management page provided in the embodiment of the present application, such as Fig.16 As shown, in terms of data statistics, the securities firm's confirmation center is more concerned about the "express fee list" because it operates independently, while the investment bank's quality control is more concerned about the "verification exception list, reply verification exception", the project team is more concerned about the "letter receipt exception", and the company is more concerned about the "confirmation statistical report". The confirmation verification method provided in the embodiment of the present application can generate the data statistics table required by the user according to the user's actual requirements.

[0139] In the process of sending and receiving letters of confirmation, express delivery of confirmation documents may cause problems such as express loss and omission. If the relevant information is stored on the blockchain during the process of sending and receiving letters, disputes between different institutions in the process of sending and receiving letters can be effectively avoided. The embodiment of the present application configures three links: confirmation details, express letter sending, and express reply letter, including multiple fields such as confirmation serial number, letter receiving unit, letter sending express number, reply letter file, etc., and the chain is stored in sequence according to the timestamp of the business occurrence, and the hash value of each link is stored on the chain to ensure the security, reliability, compliance and traceability of data in the process of letter of confirmation circulation, meet the compliance requirements of industry supervision, avoid risks such as information tampering and denial, and effectively enhance the trust between the various institutions involved in the circulation of letters of confirmation. The blockchain platform can issue a credible electronic data storage report for the stored data online.

[0140] refer to Fig.18 , Fig.18 The schematic diagram of the page for uploading the objective document metadata of the letter of confirmation provided by the embodiment of the present application, by accessing the blockchain platform, the metadata of the files of the archived letter of confirmation involving the objective contents such as express delivery and letter of confirmation attachments in the letter of confirmation process are called through the interface of the blockchain system, and the chain operation is performed. Through the hash calculation program provided by the blockchain evidence storage platform, the letter of confirmation management system can automatically perform hash operations on electronic data such as express delivery bills and reply documents, and upload them to the blockchain electronic evidence storage platform for evidence after the corresponding hash value is formed. If there are legal disputes and other situations, you can also apply for the judicial appraisal center and the notary office to issue evidence for this evidence content through the evidence storage platform. When applying for judicial issuance of evidence data, you only need to upload the original file again, and compare the recalculated file hash value with the original value on the chain. After ensuring the consistency of the file, the judicial end can issue documents such as notarial certificates to provide comprehensive and effective information certificates for relevant stakeholders.

[0141] In the embodiments of the present application, message passing, transaction management, load balancing, etc. can be processed through application middleware, document creation, editing, collaboration and other functions can be processed through WPS document service, data query, storage update, and backup can be achieved through database, and the tools required to compile, debug and run Java applications can be implemented using Openjdk8. The deployment, configuration and management of applications can be achieved through containerization and cloud platforms.

[0142] In the embodiment of the present application, the documents uploaded by the user can also be stored. Fig.19 , Fig.19 This is a schematic diagram of the file archiving process provided by the embodiment of this application. Fig.19 As shown, file archiving includes the following steps:

[0143] Step 1901: Receive a user's file upload operation.

[0144] Users can upload files through the browser page.

[0145] Step 1902: Temporarily store the file.

[0146] When receiving the file upload operation from the user, the uploaded file is temporarily stored and a globally unique uuid is generated for the file.

[0147] Step 1903: Determine whether the record has been made in the database.

[0148] If the file has been recorded in the database, execute step 1905; if the file has not been recorded in the database, execute step 1904.

[0149] Step 1904: Record the file through the database.

[0150] Add a new file record in the file table of the database and generate the corresponding uuid.

[0151] Step 1905: Store the file via the file storage server.

[0152] Rename the file to its corresponding uuid and store it in the file storage server.

[0153] The uploaded files themselves rely on the file table association in the database, which is closely integrated with the business, and implements access control at the system function level (only people in the same project can see it, or people in the confirmation center can view all files). File storage, upload, and download are implemented based on this file storage logic.

[0154] Fig. 20 A schematic diagram of the structure of the confirmation verification device provided in the embodiment of the present application is shown in FIG. Fig. 20 As shown, the confirmation verification device provided in the embodiment of the present application includes:

[0155] Interaction module: used for receiving a first operation; the first operation is used for importing multiple letters and instructing to verify the multiple letters;

[0156] Processing module: used to respond to the first operation, call the thread pool, and verify and process the multiple letters in batches; wherein, if the first letter in the first batch meets the first condition, the first letter will be removed from the first batch and put into the next batch for verification and processing, so that the letters of abnormal counterparties are verified in different batches; the first batch is the batch currently being verified and processed.

[0157] In an embodiment of the present application, the processing module is used to extract a preset number of letters from unverified letters as the first batch for verification; for the first letter in the first batch, the verification information of the first letter is placed in a cache, and the first letter is placed in a thread for verification; for each of the other letters in the first batch, a first processing is performed until each letter in the first batch completes the first processing process; the first processing includes: comparing the verification information of the letter with the verification information in the cache; if there is an abnormality, judging that the letter meets the first condition, removing the letter from the first batch, and placing it in the next batch for verification processing; if there is no abnormality, placing the verification information of the letter in a cache, and placing the letter in an idle thread for verification.

[0158] In an embodiment of the present application, the interaction module is used to receive a second operation; the second operation is used to import a reply letter and instruct verification of the reply letter; the processing module is used to respond to the second operation, compare and verify the reply letter with the corresponding letter, and obtain the verification result of the reply letter.

[0159] In an embodiment of the present application, the reply letter includes: a document; the processing module: is used to compare the text of the document in the reply letter record with the text of the document in the corresponding letter record to obtain a text comparison result; compare the table of the document in the reply letter record with the table of the document in the corresponding letter record to obtain a table comparison result.

[0160] In an embodiment of the present application, the process of letter verification or reply verification includes address verification, and the processing module is used to determine whether there is an inclusion relationship between multiple addresses; if there is no inclusion relationship, determine that the multiple addresses are not the same; or, if there is an inclusion relationship, determine whether the multiple addresses are different addresses belonging to the same unit marked by artificial dimensions; if the multiple addresses are different addresses belonging to the same unit marked by artificial dimensions, determine that the multiple addresses are the same; or, if the multiple addresses are not different addresses belonging to the same unit marked by artificial dimensions, determine whether the distance between the multiple addresses is greater than a preset distance; if the distance between the multiple addresses is greater than the preset distance, determine that the multiple addresses are not the same; or, if the distance between the multiple addresses is less than or equal to the preset distance, determine that the multiple addresses are the same.

[0161] In an embodiment of the present application, the interaction module is used to receive a login operation and determine the account type of the logged-in user; the processing module is used to obtain the role of the internal user if the account type of the logged-in user is an internal user, and provide the logged-in user with permissions corresponding to the role of the internal user; if the account type of the logged-in user is an external user, obtain the role of the external user, and provide the logged-in user with permissions corresponding to the role of the external user.

[0162] In an embodiment of the present application, the interactive module is used to provide letter preparation services; the letter confirmation categories in the letter preparation services include one or more of the following: customer, supplier and current account confirmation letters, bank confirmation letters and other confirmation letters; wherein the list of customer, supplier and current account confirmation letters includes one or more of the following: unit serial number, whether overseas, transaction currency, current account currency; the list of bank confirmation letters includes: whether overseas and / or currency; the list of other confirmation letters includes one or more of the following: whether it is a major confirmation, whether it is a contract confirmation, and whether it is overseas.

[0163] Those skilled in the art should understand that Fig. 20 The implementation functions of each module in the letter confirmation verification device shown can be understood by referring to the relevant description of the aforementioned method. Fig. 20 The functions of each module in the letter confirmation verification device shown can be implemented by a program running on a processor, or by a specific logic circuit.

[0164] Fig.21 It is a schematic structural diagram of an electronic device 2100 provided in an embodiment of the present application. Fig.21 The electronic device 2100 shown includes a processor 2110, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0165] Alternatively, if Fig.21As shown, the electronic device 2100 may further include a memory 2120. The processor 2110 may call and run a computer program from the memory 2120 to implement the method in the embodiment of the present application.

[0166] The memory 2120 may be a separate device independent of the processor 2110 , or may be integrated into the processor 2110 .

[0167] Alternatively, if Fig.21 As shown, the electronic device 2100 may further include a transceiver 2130, and the processor 2110 may control the transceiver 2130 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.

[0168] The transceiver 2130 may include a transmitter and a receiver. The transceiver 2130 may further include an antenna, and the number of antennas may be one or more.

[0169] The electronic device 2100 can specifically be a confirmation and verification device in an embodiment of the present application, and the electronic device 2100 can implement the corresponding processes implemented by the confirmation and verification device in each method of the embodiment of the present application, which will not be described again here for the sake of brevity.

[0170] Illustratively, an embodiment of the present application further provides a computer program product, including a computer program, which can be executed by the processor 2110 of the electronic device 2100 to complete the steps of any of the aforementioned methods.

[0171] Fig. 22 It is a schematic structural diagram of the chip of an embodiment of the present application. Fig. 22 The chip 2200 shown includes a processor 2210, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0172] Alternatively, if Fig. 22 As shown, the chip 2200 may further include a memory 2220. The processor 2210 may call and run a computer program from the memory 2220 to implement the method in the embodiment of the present application.

[0173] The memory 2220 may be a separate device independent of the processor 2210 , or may be integrated into the processor 2210 .

[0174] Optionally, the chip 2200 may further include an input interface 2230. The processor 2210 may control the input interface 2230 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0175] Optionally, the chip 2200 may further include an output interface 2240. The processor 2210 may control the output interface 2240 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0176] The chip can be applied to the electronic device 2100 in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the electronic device 2100 in the various methods of the embodiment of the present application, which will not be described here for the sake of brevity.

[0177] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0178] It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and performed. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, and other mature storage media in the art. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0179] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0180] It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.

[0181] The present application also provides a storage medium for storing a computer program. The storage medium can be applied to the electronic device 2100 in the present application, and the computer program enables the computer to execute the corresponding process implemented by the electronic device 2100 in each method of the present application, which will not be described in detail for the sake of brevity.

[0182] Those of ordinary skill in the art will appreciate that the modules and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0183] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.

[0184] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0185] In addition, each functional module in each embodiment of the present application may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.

[0186] If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or an electronic device 2100, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0187] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A confirmation verification method, characterized in that: The method comprises: Receiving a first operation; the first operation is used to import multiple letters and instruct to verify the multiple letters; In response to the first operation, the thread pool is called to verify and process the multiple letters in batches; wherein, if the first letter in the first batch meets the first condition, the first letter is removed from the first batch and put into the next batch for verification and processing, so that the letters from abnormal counterparties are verified in different batches; the first batch is the batch currently being verified and processed.

2. The method according to claim 1, characterized in that The calling thread pool verifies and processes the multiple letters in batches; wherein, if the first letter in the first batch meets the first condition, the first letter is removed from the first batch and put into the next batch for verification, including: For the unverified outgoing letters, a preset number of outgoing letters are selected as the first batch for verification; For the first outgoing letter in the first batch, the verification information of the first outgoing letter is put into a cache, and the first outgoing letter is put into a thread for verification; For each of the other outgoing letters in the first batch, a first process is performed until each outgoing letter in the first batch completes the first process; the first process includes: Compare the verification information of the outgoing letter with the verification information in the cache; If there is an abnormality, the letter is judged to meet the first condition, and the letter is removed from the first batch and put into the next batch for verification; If there is no abnormality, the verification information of the sent letter is put into the cache, and the sent letter is put into an idle thread for verification.

3. The method according to claim 1, characterized in that Also includes: receiving a second operation; the second operation is used to import a reply letter and instruct to verify the reply letter; In response to the second operation, the reply letter is compared and verified with the corresponding letter to obtain a verification result of the reply letter.

4. The method according to claim 3, characterized in that The outgoing letter includes: a document, and the comparison and verification of the reply letter with the outgoing letter corresponding to the reply letter includes: Compare the text of the document in the reply record with the text of the corresponding document of the outgoing letter to obtain a text comparison result; The table of the document in the reply record is compared with the table of the corresponding document of the outgoing letter to obtain a table comparison result.

5. The method according to any one of claims 1 to 4, characterized in that The process of letter verification or reply verification includes address verification. The process of determining whether the addresses are the same is as follows: Determine whether there is a containment relationship between multiple addresses; If there is no inclusion relationship, it is determined that the multiple addresses are not the same; or, if there is an inclusion relationship, it is determined whether the multiple addresses are different addresses belonging to the same unit marked by manual dimensions; If the multiple addresses are different addresses belonging to the same unit marked by artificial dimensions, determining that the multiple addresses are the same; or, if the multiple addresses are different addresses belonging to the same unit marked by artificial dimensions, determining whether the distance between the multiple addresses is greater than a preset distance; If the distance between the multiple addresses is greater than a preset distance, it is determined that the multiple addresses are different; or if the distance between the multiple addresses is less than or equal to the preset distance, it is determined that the multiple addresses are the same.

6. The method according to any one of claims 1 to 4, characterized in that Also includes: Receive login operations and determine the account type of the logged-in user; If the account type of the logged-in user is an internal user, obtain the role of the internal user and provide the logged-in user with permissions corresponding to the role of the internal user; If the account type of the logged-in user is an external user, the role of the external user is obtained, and permissions corresponding to the role of the external user are provided to the logged-in user.

7. A confirmation verification device, characterized in that: The device comprises: Interaction module: used for receiving a first operation; the first operation is used for importing multiple letters and instructing to verify the multiple letters; Processing module: used to respond to the first operation, call the thread pool, and verify and process the multiple letters in batches; wherein, if the first letter in the first batch meets the first condition, the first letter will be removed from the first batch and put into the next batch for verification and processing, so that the letters of abnormal counterparties are verified in different batches; the first batch is the batch currently being verified and processed.

8. An electronic device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the confirmation verification method as described in any one of claims 1 to 6.

9. A storage medium, characterized in that: Used to store a computer program, wherein the computer program enables a computer to execute the confirmation verification method as described in any one of claims 1-6.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, it implements the confirmation verification method as described in any one of claims 1 to 6.

Images