A blockchain-based overseas invoice authentication method, system, and storage medium

Through the blockchain-based multi-party authentication mechanism, the problem of difficulty in verifying overseas invoices has been solved, high-reliability authentication records and security enhancements have been achieved, ensuring the authenticity and rationality of invoice authentication.

CN114818007BActive Publication Date: 2025-10-10NOTTINGHAM (NINGBO FREE TRADE ZONE) BLOCKCHAIN CO LTD +1
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202210447064.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-04-26
Publication Date
2025-10-10
Estimated Expiration
2042-04-26

AI Technical Summary

Technical Problem

Overseas invoices are difficult to verify directly through a single, credible channel, making it difficult for tax authorities to effectively supervise and manage them, leading to loopholes and legal risks.

Method used

A blockchain-based overseas invoice authentication method is adopted to obtain and identify invoices and auxiliary certification information through the blockchain platform, use a multi-party authentication mechanism to verify the authenticity of the invoice, and record the authentication results on the blockchain to avoid centralized nodes and ensure that the results are credible and cannot be tampered with.

Benefits of technology

It improves the authenticity and reliability of overseas invoice authentication, enhances the security of the authentication process, prevents malicious users from obtaining private information, reduces repeated authentication operations, and improves the rationality and efficiency of invoice reimbursement.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114818007B_ABST
    Figure CN114818007B_ABST
Patent Text Reader

Abstract

The application relates to a blockchain-based overseas invoice authentication method and system and a storage medium, relates to the field of overseas invoice authentication, and comprises the following steps: obtaining to-be-authenticated invoice information and auxiliary proof information; identifying invoice data information and proof data information and screening out proof type information; determining proof access point information; sending request verification information and proof data information; receiving verification result information; if all the information is real data, updating the information into valid invoice information; if there is unverifiable information, updating the information into basically valid invoice information; and if there is false data, updating the information into invalid invoice information. The application improves the problem that it is difficult to find a single credible invoice signing or endorsement source for an overseas invoice, and has the effects of authenticating through multiple parties, finally forming a high-credibility authentication result in the blockchain for storage, and improving the authenticity and reliability of overseas invoice authentication.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of overseas invoice authentication, and in particular to a blockchain-based overseas invoice authentication method, system, and storage medium. Background Art

[0002] An invoice refers to any business receipt issued or received by any entity or individual when purchasing or selling goods, providing or receiving services, or engaging in other business activities. Invoices are often the primary basis for accounting and serve as a crucial basis for law enforcement inspections by auditing and tax authorities. For companies, invoices primarily serve as the basis for accounting and as expense receipts for tax payments. For employees, invoices are primarily used for expense reimbursement.

[0003] Overseas invoices, unlike domestic ones, require formal tax supervision. Sometimes they're just a shopping receipt, sometimes just a receipt. Once you've obtained an overseas invoice, have it signed by someone at your workplace, and you can file for reimbursement just like a regular domestic invoice.

[0004] Regarding the above-mentioned related technologies, the inventor believes that it is difficult to directly verify overseas invoices through a single credible channel, that is, it is difficult to find a single credible source of invoice signature or endorsement. At the same time, from the perspective of tax collection costs, it is difficult for tax authorities to fully and effectively supervise and manage all overseas invoices. There are certain loopholes and legal risks, and there is still room for improvement. Summary of the Invention

[0005] In order to improve the problem that overseas invoices are difficult to directly verify through a single trusted channel, that is, it is difficult to find a single trusted source of invoice signature or endorsement, this application provides a blockchain-based overseas invoice authentication method, system, storage medium and smart terminal.

[0006] First, this application provides a blockchain-based overseas invoice authentication method, which adopts the following technical solutions:

[0007] A blockchain-based overseas invoice authentication method, comprising:

[0008] Obtain the invoice information and supporting certification information submitted by the user in the preset blockchain;

[0009] Identify key data in the invoice information to be authenticated and the auxiliary certification information, define the key data corresponding to the invoice information to be authenticated as invoice data information, define the key data corresponding to the auxiliary certification information as certification data information, and filter out certification type information;

[0010] Performing a matching analysis based on the access point IP information and the certification type information stored in the preset access point database to determine the access point IP address corresponding to the certification type information, and defining the access point IP address as the certification access point information;

[0011] Sending the preset request verification information and certification data information to the access point IP address corresponding to the certification access point information;

[0012] Receiving verification result information sent back from the access point IP address corresponding to the certification access point information, the verification result information including data authenticity information, unverifiable information, and data false information;

[0013] If the verification results are all true, the invoice information to be verified will be updated to valid invoice information and packaged and stored in the blockchain;

[0014] If there is unverifiable information in the verification result information, the invoice information to be verified will be updated to basic valid invoice information and packaged and stored in the blockchain;

[0015] If there is false data in the verification result information, the invoice information to be verified will be updated to invalid invoice information and packaged and stored on the blockchain.

[0016] By adopting the above technical solution, the relevant auxiliary information of the invoice to be authenticated is uploaded to the blockchain and sent to the relevant parties for verification, thereby avoiding the existence of centralized nodes. Through multi-party authentication, a highly credible authentication result is finally formed in the blockchain for evidence storage. The results are recorded and cannot be tampered with at will, thereby improving the authenticity and reliability of overseas invoice authentication. On the other hand, the result returned at the corresponding node is only a confirmation or rejection, and the original data will not be returned, thereby preventing malicious users from obtaining other private information by submitting other information, thereby improving the security of the authentication process.

[0017] Optionally, when the verification result information contains false data or cannot be verified, the authentication method includes:

[0018] Obtain parameter values ​​in valid invoice information, basic valid invoice information, and invalid invoice information, define the parameter value corresponding to the valid invoice information as valid parameter information, define the parameter value corresponding to the basic valid invoice information as basic valid parameter information, and define the parameter value corresponding to the invalid invoice information as invalid parameter information;

[0019] Calculate the parameters and information based on the valid parameter information, the basic valid parameter information, and the invalid parameter information, and respectively calculate the proportion of the basic valid parameter information and the invalid parameter information in the parameters and information, define the proportion of the basic valid parameter information as the basic proportion information, and define the proportion of the invalid parameter information as the invalid proportion information;

[0020] determining whether the invalid proportion information is greater than the preset critical invalid proportion information;

[0021] If the invalid proportion information is greater than the preset critical invalid proportion information, recording the invalid invoice group information in the blockchain and triggering the invalid alarm information;

[0022] If the invalid proportion information is less than the preset critical invalid proportion information, determining whether the invalid parameter information is greater than the preset critical invalid numerical information;

[0023] If the invalid parameter information is greater than the preset critical invalid numerical information, recording the invalid invoice group information in the blockchain and triggering the invalid alarm information;

[0024] If the invalid parameter information is less than the preset critical invalid numerical information, determining whether the basic valid proportion information is greater than the preset critical basic valid proportion information;

[0025] If the basic valid proportion information is greater than the preset critical basic valid proportion information, recording the basic valid invoice group information in the blockchain and triggering the basic valid alarm information;

[0026] If the basic valid proportion information is less than the preset critical basic valid proportion information, determining whether the basic valid parameter information is greater than the preset critical basic valid numerical information;

[0027] If the basic valid parameter information is greater than the preset critical basic valid numerical information, recording the basic valid invoice group information in the blockchain and triggering the basic valid alarm information;

[0028] If the basic valid parameter information is less than the preset critical basic valid numerical information, recording the valid invoice group information and the basic valid proportion information in the blockchain.

[0029] By using the above technical solution, whether the critical value is exceeded is determined by calculating the amount and proportion of the basic valid invoice and the invalid invoice, so that the alarm is triggered when the critical value is exceeded to prevent the occurrence of malicious user false reporting of invoices for reimbursement, and the rationality of the invoice reimbursement is improved.

[0030] Optionally, another method for updating the to-be-authenticated invoice information to the valid invoice information and storing the to-be-authenticated invoice information in the blockchain includes:

[0031] performing matching analysis on the invoice record information and the invoice data information in all access points of the blockchain stored in the preset invoice database to determine the invoice record corresponding to the invoice data information, and defining the invoice record as the check invoice record information;

[0032] determining whether the check invoice record information exists;

[0033] If the check invoice record information exists, updating the to-be-authenticated invoice information to the valid invoice information and storing the to-be-authenticated invoice information in the blockchain;

[0034] If it does not exist, the verification request information and the certification data information are sent to the access point IP address corresponding to the certification access point information.

[0035] By adopting the above technical solution, when a user needs to deduct an invoice, by checking whether it has been authenticated in the blockchain, the invoice that has already been authenticated does not need to be authenticated again when deducting the invoice, reducing the repeated operation process of re-authentication and improving the efficiency of authentication.

[0036] Optionally, the method of updating the invoice information to be verified to valid invoice information and storing it in the blockchain includes:

[0037] Obtain the deducted invoice record information stored in the blockchain;

[0038] Determine whether the invoice information to be authenticated is consistent with the information of one of the deducted invoice records;

[0039] If the invoice information is consistent with one of the deducted invoice records, the invoice information to be verified will be updated to invalid invoice information;

[0040] If it is inconsistent with all the deducted invoice record information, the invoice information to be authenticated will be updated to the valid invoice information and when the user deducts, the deducted invoice record information corresponding to the valid invoice information will be uploaded at the certification access point information corresponding to the preset tax IP information.

[0041] By adopting the above technical solution, by checking whether the deduction has been made, it is prevented that malicious users use the same invoice to make repeated reimbursements, thereby improving the rationality of invoice reimbursement.

[0042] Optionally, when the invalid parameter information is less than the critical invalid value information and the basic valid parameter information is less than the critical basic valid value information, the method for converting the invoice information to be authenticated from one of the basic valid group invoice information and the invalid invoice group information into the valid invoice group information includes:

[0043] Obtain the resubmission information submitted by the user in the blockchain and send it to the access point IP address corresponding to the tax information in the blockchain;

[0044] Receiving the added result information sent back from the access point IP address corresponding to the tax information;

[0045] When the added result information is the preset allowed addition information, obtain the re-assistance proof information submitted by the user in the blockchain;

[0046] Identify key data in the re-assistance certification information, and define the key data corresponding to the re-assistance certification information as re-certification data information;

[0047] Filtering recertification type information from the recertification data information;

[0048] Performing a matching analysis based on the access point IP information and the re-certification type information stored in the access point database to determine the access point IP address corresponding to the re-certification type information, and defining the access point IP address as the re-certification access point information;

[0049] Determining whether the re-certification access point information is consistent with one of the certification access point information;

[0050] If it is consistent with one of the certification access point information, then determine whether the re-certification type information is consistent with the certification type information;

[0051] If it is consistent with the proof type information, the re-verification result information is received and the consistent proof type information is updated according to the re-verification result information, and then the invalid ratio information, invalid parameter information, basic valid ratio information and basic valid parameter information are calculated;

[0052] If it is inconsistent with the proof type information, the re-verification result information is received and the parameter and information, basic valid parameter information, invalid parameter information and re-verification result information are recalculated;

[0053] If it is inconsistent with any of the certification access point information, the re-verification result information is received and the parameter and information, basic valid parameter information, invalid parameter information and re-verification result information are recalculated;

[0054] When the recalculated invalid proportion information is less than the critical invalid proportion information, the invalid parameter information is less than the critical invalid numerical information, the basic valid proportion information is less than the critical basic valid proportion information, and the basic valid parameter information is less than the critical basic valid numerical information, the basic valid invoice group information or the invoice information to be authenticated corresponding to the invalid invoice group information is re-recorded in the blockchain as the valid invoice group information.

[0055] By adopting the above technical solution and adding auxiliary supporting documents, we can avoid the erroneous situation where real overseas invoices are rejected as invalid invoices due to insufficient or incorrect uploading of supporting documents at the beginning, thereby improving the reliability and accuracy of invoice authentication.

[0056] Optionally, the method for receiving re-verification result information includes:

[0057] Get the number of re-verification result information;

[0058] Determine whether the number of times information is greater than the number of times value corresponding to the preset trial number information;

[0059] If it is greater than the number of times corresponding to the trial number information, the invoice information to be authenticated will be updated to invalid invoice information;

[0060] If it is less than, the re-verification result information is received normally.

[0061] By adopting the above technical solution, the number of repeated submissions of the type corresponding to the same re-verification result information is limited, thereby preventing malicious users from repeatedly trying to obtain the final correct information, thereby improving the security of data transmission.

[0062] Optionally, the method of sending the certification data information to the access point IP address corresponding to the certification access point information after identifying the certification data information includes:

[0063] Performing a matching analysis based on the association type information stored in the preset association database and the invoice data information to determine the association type corresponding to the invoice data information, and defining the association type as first association type information;

[0064] Performing a matching analysis on the first association type information and the proof type information in the proof data information to determine the proof data information that matches successfully, and defining the proof data information as the first proof data information;

[0065] Filter out key data in the first certification data information that matches the type of the invoice data information, define the key data in the first certification data information as first key certification data information, and define the key data in the invoice data information as first approval key data information;

[0066] Determining whether the first key certification data information is consistent with the first approval key data information;

[0067] If the first certification data information is consistent with the first approval key data information, the first certification data information is sent to the corresponding certification access point information, the first certification data information is stored in the associated information library, and the certification data information other than the first certification data information is defined as the remaining certification data information;

[0068] Performing a matching analysis based on the association type information stored in the association database and the first certification data information to determine the association type corresponding to the first certification data information, and defining the association type as second association type information;

[0069] Performing a matching analysis on the second association type information and the proof type information in the remaining proof data information to determine the remaining proof data information that has successfully matched, and defining the remaining proof data information as the second proof data information;

[0070] Identifying key data in the first certification data information that matches the type of the second certification data information, defining the key data in the second certification data information as second key certification data information, and defining the key data in the first certification data information as second approval key data information;

[0071] Determine whether the second key certification data information is consistent with the second approval key data information;

[0072] If the second proof data information is consistent with the second approval key data information, the second proof data information is sent to the corresponding proof access point information, the second proof data information is stored in the associated information library, and the remaining proof data information is updated until there is no remaining proof data information or the remaining proof data information is not related to the previously matched proof data information. The remaining proof data information that is not related to the previously matched proof data information is defined as invalid proof data information;

[0073] Not sending verification request information to the certification access point information corresponding to the invalid certification data information;

[0074] If the invoice information is inconsistent with the second approval key data, the invoice information to be verified will be updated to invalid invoice information and packaged and stored in the blockchain;

[0075] If it is inconsistent with the first approved key data information, the invoice information to be authenticated will be updated to invalid invoice information and packaged and stored in the blockchain.

[0076] By adopting the above technical solution, by selecting the related information of the previous level step by step, and then preliminarily judging whether the relevant information on the two is consistent, some auxiliary proof information that does not conform to the related content can be automatically screened out, thereby reducing the workload of some verification nodes and improving the efficiency of invoice authentication.

[0077] Optional authentication methods when some parts of the invoice information to be authenticated are unrecognizable include:

[0078] Perform matching analysis on the complete data information and invoice data information stored in the preset complete database to determine the complete data corresponding to the invoice data information, and define the complete data as the current complete data information;

[0079] Calculate the missing data type information based on the current complete data information and invoice data information;

[0080] Matching and analyzing the missing type data information with the proof type information in any proof data information to determine the proof data information corresponding to the missing type data information, and defining the proof data information as missing proof information;

[0081] determine whether the missing proof information is stored in the association information library;

[0082] if stored in the association information library, determine whether the verification result information corresponding to the missing proof information is data real information;

[0083] if it is data real information, add the data corresponding to the real type data information in the missing proof information to the invoice data information;

[0084] if it is not data real information, update the to-be-authenticated invoice information to invalid invoice information and package it for storage in the blockchain;

[0085] if not stored in the association information library, update the to-be-authenticated invoice information to basic valid invoice information and package it for storage in the blockchain.

[0086] By adopting the above technical solution, when some data on the invoice is blurred and cannot be read, the missing data on the invoice is found from the auxiliary proof materials that have been confirmed as correct data, thereby making up the data at the blurred place and improving the intelligence of invoice authentication.

[0087] In a second aspect, the application provides a cross-border invoice authentication system based on a blockchain, which adopts the following technical solution:

[0088] A cross-border invoice authentication system based on a blockchain, comprising:

[0089] An information acquisition module for acquiring to-be-authenticated invoice information and auxiliary proof information submitted by a user in a preset blockchain;

[0090] A processing module connected to the information acquisition module and the identification module for information storage and processing;

[0091] An identification module for identifying key data in the to-be-authenticated invoice information and the auxiliary proof information, defining the key data corresponding to the to-be-authenticated invoice information as invoice data information, defining the key data corresponding to the auxiliary proof information as proof data information and screening out proof type information;

[0092] The processing module matches and analyzes the access point IP information and the proof type information stored in the preset access point database to determine the access point IP address corresponding to the proof type information, and defines the access point IP address as proof access point information;

[0093] A sending module connected to the processing module for sending the preset request verification information and the proof data information to the access point IP address corresponding to the proof access point information;

[0094] a receiving module connected to the processing module, configured to receive verification result information sent back from the access point IP address corresponding to the certification access point information, wherein the verification result information includes data authenticity information, unverifiable information, and data false information;

[0095] If the verification result information received by the receiving module is all true data, the processing module will update the invoice information to be verified to valid invoice information and package it up and store it in the blockchain;

[0096] If the receiving module receives verification results containing information that cannot be verified, the processing module updates the invoice information to be verified to basically valid invoice information and packages it up and stores it in the blockchain;

[0097] If the receiving module receives false data in the verification result information, the processing module will update the invoice information to be authenticated to invalid invoice information and package it up and store it in the blockchain.

[0098] By adopting the above technical solution, the relevant auxiliary information of the invoice to be authenticated is uploaded to the blockchain and sent to the relevant parties for verification, thereby avoiding the existence of centralized nodes. Through multi-party authentication, a highly credible authentication result is finally formed in the blockchain for evidence storage. The results are recorded and cannot be tampered with at will, thereby improving the authenticity and reliability of overseas invoice authentication. On the other hand, the result returned at the corresponding node is only a confirmation or rejection, and the original data will not be returned, thereby preventing malicious users from obtaining other private information by submitting other information, thereby improving the security of the authentication process.

[0099] On the third aspect, the present application provides a computer-readable storage medium that can store corresponding programs and is not easily tampered with.

[0100] A computer-readable storage medium adopts the following technical solution:

[0101] A computer-readable storage medium storing a computer program capable of being loaded by a processor and executing any of the above-mentioned blockchain-based overseas invoice authentication methods.

[0102] By adopting the above technical solution, the relevant auxiliary information of the invoice to be authenticated is uploaded to the blockchain and sent to the relevant parties for verification, thereby avoiding the existence of centralized nodes. Through multi-party authentication, a highly credible authentication result is finally formed in the blockchain for evidence storage. The results are recorded and cannot be tampered with at will, thereby improving the authenticity and reliability of overseas invoice authentication. On the other hand, the result returned at the corresponding node is only a confirmation or rejection, and the original data will not be returned, thereby preventing malicious users from obtaining other private information by submitting other information, thereby improving the security of the authentication process.

[0103] In summary, this application includes at least one of the following beneficial technical effects:

[0104] 1. Through multi-party authentication, a highly credible authentication result is ultimately formed and stored in the blockchain. The results are recorded and cannot be tampered with at will, improving the authenticity and reliability of overseas invoice authentication;

[0105] 2. The result returned at the corresponding node is only a confirmation or rejection, and the original data is not returned. This prevents malicious users from obtaining other private information by submitting other information, thereby improving the security of the authentication process;

[0106] 3. By finding the missing data on the corresponding invoice from the auxiliary supporting materials that have been confirmed as correct data, the ambiguous data can be filled in, thereby improving the intelligence of invoice authentication. BRIEF DESCRIPTION OF THE DRAWINGS

[0107] Figure 1 This is a flowchart of a blockchain-based overseas invoice authentication method in an embodiment of the present application.

[0108] Figure 2 This is a structural diagram of a blockchain-based overseas invoice authentication method in an embodiment of the present application.

[0109] Figure 3 This is a flowchart of the authentication method when there is false data information in the verification result information or the information cannot be verified in the embodiment of the present application.

[0110] Figure 4 This is a flowchart of another method for updating the invoice information to be authenticated to valid invoice information and storing it in the blockchain in an embodiment of the present application.

[0111] Figure 5 This is a flowchart of a method for updating the invoice information to be authenticated to valid invoice information and storing it in a blockchain in an embodiment of the present application.

[0112] Figure 6 It is a flowchart of a method for converting the invoice information to be authenticated from one of basic valid group invoice information and invalid invoice group information into valid invoice group information in an embodiment of the present application.

[0113] Figure 7 This is a flowchart of a method for receiving re-verification result information in an embodiment of the present application.

[0114] Figure 8 This is a flowchart of a method for sending proof data information to an access point IP address corresponding to proof access point information after identifying proof data information in an embodiment of the present application.

[0115] Figure 9This is a flowchart of the authentication method in an embodiment of the present application when some locations in the invoice information to be authenticated cannot be identified.

[0116] Figure 10 This is a module diagram of a blockchain-based overseas invoice authentication method in an embodiment of the present application. DETAILED DESCRIPTION

[0117] In order to make the purpose, technical solutions and advantages of this application more clear, the following Figure 1-10 It should be understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application.

[0118] The embodiments of the present invention are described in further detail below with reference to the accompanying drawings.

[0119] See also Figure 1 The embodiment of the present invention provides a blockchain-based overseas invoice authentication method. The main process of the blockchain-based overseas invoice authentication method is described as follows:

[0120] Step 100: Obtain the invoice information to be authenticated and the auxiliary certification information submitted by the user in the preset blockchain.

[0121] The blockchain is a pre-configured alliance chain, such as Figure 2 As shown, the entire blockchain platform includes multiple user access nodes, also known as public user access nodes. Other participating nodes, such as customs and judicial authorities, also participate. These nodes collaborate to form a consortium chain after prior approval. Public user access nodes are responsible for access by individual or organizational users, while other nodes are responsible for endorsement. Smart contracts configure different permissions and execution processes for different nodes. The invoice information to be authenticated is the overseas invoice information submitted by the user for authentication, such as a printed receipt or a receipt. Auxiliary verification information is indirect evidence used to verify the authenticity of the invoice, such as payment statements and shipping documents. This information is obtained by users uploading it to the blockchain from public user access nodes.

[0122] Step 101: Identify key data in the invoice information to be authenticated and the auxiliary certification information, define the key data corresponding to the invoice information to be authenticated as invoice data information, define the key data corresponding to the auxiliary certification information as certification data information, and filter out certification type information.

[0123] Invoice data information refers to key data on an invoice, such as the buyer, seller, amount, product name and category, and quantity. Proof data information refers to key data on supporting documentation, and proof type information refers to the type of documentation. Examples include the payee and payee, amount, and other information on a payment flow, or the product name and insured value on a freight bill. The identification and screening process involves ORC identifying the corresponding key data in text and numbers, and then the system filters the information for each identified type.

[0124] Step 102: Perform matching analysis based on the access point IP information and the certification type information stored in the preset access point database to determine the access point IP address corresponding to the certification type information, and define the access point IP address as the certification access point information.

[0125] The access point information is the IP address of the access point corresponding to the supporting materials, such as Figure 2 As shown, the customs declaration corresponds to the IP address of the customs access point. The database stores a mapping between certification access point information and certification type information. When establishing the blockchain, field personnel, using experience, common sense, and relevant searches, search and record the types of certification materials that may be issued by each blockchain access point. If no corresponding mapping is found during subsequent work, a request is sent to the system administrator, and the received results are recorded and stored in the database. When the system identifies the certification type information, it automatically searches the database for the corresponding certification access point information.

[0126] Step 103: Send the preset request verification information and certification data information to the access point IP address corresponding to the certification access point information.

[0127] The verification request requests the relevant party associated with the access point to review the certification data. Once the corresponding access point IP address and certification data are obtained, the corresponding information is sent to the access point IP address, requesting verification from the relevant party that certified the access point. This submission process is performed through MPC (Multi-Party Computation), which maximizes the protection of private information.

[0128] Step 104: Receive verification result information sent back from the access point IP address corresponding to the certification access point information, wherein the verification result information includes data authenticity information, verification failure information, and data false information.

[0129] Verification result information is information sent back by the access point to verify the verification result of the proof data information. Data authenticity information is information that proves that the relevant party corresponding to the access point information has verified the proof data information to be true. Unverifiable information is information that proves that the relevant party corresponding to the access point information cannot verify the authenticity of the proof data information. Data falsification information is information that proves that the relevant party corresponding to the access point information has verified the proof data information to be false. During the reception process, MPC only returns confirmation information and does not return the original data. This prevents malicious users from obtaining other private information by submitting additional data. The returned verification result is recorded by the access point and verified according to the smart contract.

[0130] Step 105: If the verification result information is all true data information, the invoice information to be verified will be updated to valid invoice information and packaged and stored on the blockchain.

[0131] Valid invoice information is information that has been verified as valid. When the verification results show that all information is authentic, it indicates a high probability that the invoice is valid and is certified as valid. The verifying node then submits the verification results to the blockchain and transmits them to other access points. After verification, the other access points use majority endorsement to package the relevant documents and hash values ​​onto the blockchain, completing the verification and on-chain of overseas invoices. Users can use these verified invoices to deduct tax credits, annotating the block information and invoice hash values, allowing for faster tax audits.

[0132] Step 106: If there is unverifiable information in the verification result information, the invoice information to be verified is updated to basic valid invoice information and packaged and stored on the blockchain.

[0133] Basic valid invoice information refers to invoices that cannot be verified using current proof. If the verification result contains unverifiable information, it means that the invoice under verification requires further verification. In this case, the result will be packaged and uploaded to the blockchain using a majority endorsement, along with the relevant documents and hash values, completing the verification and upload of overseas invoices to the blockchain.

[0134] Step 107: If there is false data in the verification result information, the invoice information to be verified will be updated to invalid invoice information and packaged and stored in the blockchain.

[0135] Invalid invoice information refers to invoices that are invalid after verification. If the verification result contains false information, it means that the invoice data is incorrect and the invoice is directly judged as invalid. Then, the result is also packaged with the relevant book and hash value using majority endorsement and uploaded to the chain, completing the overseas invoice authentication and chain.

[0136] Reference Figure 3When the verification result information contains false data or cannot be verified, the authentication method includes:

[0137] Step 200: Obtain parameter values ​​in valid invoice information, basic valid invoice information and invalid invoice information, define the parameter value corresponding to the valid invoice information as valid parameter information, define the parameter value corresponding to the basic valid invoice information as basic valid parameter information, and define the parameter value corresponding to the invalid invoice information as invalid parameter information.

[0138] Valid parameter information refers to the amount, quota, or other relevant data within valid invoice information. Basic valid invoice information refers to the amount, quota, or other relevant data within basic valid invoice information. Invalid parameter information refers to the amount, quota, or other relevant data within invalid invoice information. This information is obtained by using ORC to identify the corresponding data type, such as the amount or other relevant data type.

[0139] Step 201: Calculate parameters and information based on valid parameter information, basic valid parameter information, and invalid parameter information, and calculate the proportion of basic valid parameter information and invalid parameter information in the parameters and information respectively, define the proportion of basic valid parameter information as basic proportion information, and define the proportion of invalid parameter information as invalid proportion information.

[0140] The parameter sum information is the sum of the parameters corresponding to the amounts of valid parameter information, basic valid parameter information, and invalid parameter information. The basic percentage information is the percentage of the basic valid parameter information in the parameter sum information. The invalid percentage information is the percentage of the invalid parameter information in the parameter sum information. The parameter sum information is calculated by adding the three. The basic percentage information and invalid percentage information are calculated by dividing the basic valid parameter information by the parameter sum information and the invalid parameter information by the parameter sum information.

[0141] Step 202: Determine whether the invalidity ratio information is greater than a preset critical invalidity ratio information.

[0142] The critical invalidity ratio is a pre-set maximum percentage. When this percentage is exceeded, the percentage of invalid invoices is considered abnormal. This is a manually set value, such as 10%. The purpose of this judgment is to determine whether the proportion of the amount on invalid invoices is too high.

[0143] Step 221: If the invalid ratio is greater than the critical invalid ratio, it will be recorded as invalid invoice group information in the blockchain and an invalid alarm message will be triggered.

[0144] The invalid invoice group information is information defining the invoices of the batch or the invoices of the IP address of the public access point as invalid invoices. The invalid alarm information is information alarming when the invoices of the batch are all defined as invalid invoices. The triggering mode is direct text display and recording in the blockchain. If the critical invalid proportion information is greater, it means that the invalid invoice amount proportion of the invoices of the batch is too large at this time, which indicates a high possibility of false declaration, and the invoices of the batch are all defined as invalid invoice group information and an alarm is given.

[0145] Step 2022: If the critical invalid proportion information is less, it is determined whether the invalid parameter information is greater than the preset critical invalid numerical value information.

[0146] The critical invalid numerical value information is a maximum critical value of the corresponding amount of invalid invoices set in advance, that is, if the amount of invalid invoice information exceeds the value, it is abnormal and is artificially set, for example, 10,000. If the critical invalid proportion information is less, it means that the invalid invoice amount proportion at this time does not exceed the warning line, and it can be further determined whether the amount exceeds the critical invalid numerical value information.

[0147] Step 2031: If the critical invalid numerical value information is greater, it is recorded as invalid invoice group information in the blockchain and invalid alarm information is triggered.

[0148] If the critical invalid numerical value information is greater, it means that the total amount of the invalid invoices of the batch at this time is too large, which indicates a high possibility of false declaration, and the invoices of the batch are all defined as invalid invoice group information and an alarm is given.

[0149] The two judgments of the amount and the proportion can be performed synchronously, that is, when one of them exceeds, the invalid alarm information is triggered.

[0150] Step 2032: If the critical invalid numerical value information is less, it is determined whether the basic valid proportion information is greater than the preset critical basic valid proportion information.

[0151] If both the critical invalid numerical value information is less, it means that there is no invalid invoice group information at this time. The critical basic valid proportion information is a maximum critical value of the corresponding amount proportion of the basic valid invoices set in advance, that is, if the amount proportion of the basic valid invoice information exceeds the value, it is abnormal and is artificially set, for example, 30%. The purpose of the judgment is to determine whether the amount proportion of the basic valid invoice is too large.

[0152] Step 2041: If the critical basic valid proportion information is greater, it is recorded as basic valid invoice group information in the blockchain and basic valid alarm information is triggered.

[0153] The basically valid invoice group information defines all invoices submitted for reimbursement in this batch, or invoices submitted for reimbursement from this public access point's IP address, as basically valid invoices. The basically valid alarm information triggers an alarm when all invoices in this batch have been defined as basically valid. This is triggered by a direct text display and recorded in the blockchain. If the value exceeds the critical basically valid ratio, it indicates that the amount of basically valid invoices in this batch of reimbursement invoices exceeds a large percentage, indicating a high probability of unverifiable invoices being submitted. Therefore, all invoices in this batch are defined as basically valid invoices, and an alarm is triggered.

[0154] Step 2042: If it is less than the critical basic effective ratio information, determine whether the basic effective parameter information is greater than the preset critical basic effective value information.

[0155] The critical basic validity value information is a pre-set maximum threshold for the corresponding amount on a basically valid invoice. If the amount exceeds this threshold, the amount on the basically valid invoice is considered abnormal. This is a manually set value, for example, 100,000. If the amount is less than the critical basic validity ratio information, it means that the amount of the basically valid invoices at that time does not exceed the warning line, and it can also be determined whether the amount exceeds the critical basic validity value information.

[0156] Step 2051: If it is greater than the critical basic valid value information, it will be recorded in the blockchain as basic valid invoice group information and trigger basic valid alarm information.

[0157] If it is greater than the critical basic valid numerical information, it means that the total amount of this batch of basically valid invoices is too large, which means that there is a high possibility of unverifiable invoice declarations. In this case, all invoices in this batch will be defined as basically valid invoice group information and an alarm will be issued.

[0158] Step 2052: If it is less than the critical basic valid value information, it will be recorded in the blockchain as valid invoice group information and basic valid ratio information.

[0159] Valid invoice group information defines all invoices submitted for reimbursement in this batch or for reimbursement via the IP address of this public access point as valid invoices. If the number is less than , it indicates that the proportion of valid invoices does not exceed the critical ratio and amount, and the proportion of invalid invoices does not exceed the critical ratio and amount, indicating that the invoices are likely valid and are therefore defined as valid invoice group information.

[0160] Reference Figure 4 Another method for updating the invoice information to be verified to valid invoice information and storing it in the blockchain includes:

[0161] Step 300: Perform a matching analysis based on the invoice record information and invoice data information in all access points of the blockchain stored in the preset invoice database to determine the invoice record corresponding to the invoice data information, and define the invoice record as the verified invoice record information.

[0162] Verified invoice records are pre-stored invoice records on the blockchain, meaning they have been authenticated. The invoice database stores a mapping between invoice data and verified invoice records. This information is automatically stored by the system. When an invoice is first verified, the system automatically records the corresponding invoice record. This functionality is implemented using a hash value on the blockchain, meaning the system stores the hash value of the corresponding verification result.

[0163] Step 301: Determine whether the invoice record information exists.

[0164] The purpose of judgment is to determine whether there has been a record before, so as to reduce the workload of the relevant parties for verification.

[0165] Step 3011: If there is verified invoice record information, the invoice information to be verified is updated to valid invoice information and stored in the blockchain.

[0166] If it exists, it means that the verification is successful at this time, and there is no need to verify again. The invoice information to be verified is directly updated to the valid invoice information and stored in the blockchain.

[0167] Step 3012: If it does not exist, send the verification request information and certification data information to the access point IP address corresponding to the certification access point information.

[0168] If not, the authentication request information and authentication data information are sent to the access point IP address corresponding to the authentication access point information to request authentication.

[0169] Reference Figure 5 The method of updating the invoice information to be authenticated to valid invoice information and storing it in the blockchain includes:

[0170] Step 400: Obtain the deducted invoice record information stored in the blockchain.

[0171] The deducted invoice record information is the record of the deduction of the successfully authenticated invoice. The method of obtaining it is to call it from the blockchain.

[0172] Step 401: Determine whether the invoice information to be authenticated is consistent with the information of one of the deducted invoice records.

[0173] The purpose of the judgment is to determine whether the invoice to be certified has been completed.

[0174] Step 4011: If the invoice information to be verified is consistent with one of the deducted invoice records, the invoice information to be verified will be updated to invalid invoice information.

[0175] If the verification is completed, the invoice information to be verified can be directly updated to invalid invoice information to avoid duplicate reimbursement.

[0176] Step 4012: If it is inconsistent with all the deducted invoice record information, the invoice information to be authenticated will be updated to the valid invoice information and when the user deducts, the deducted invoice record information corresponding to the valid invoice information will be uploaded to the certification access point information corresponding to the preset tax IP information.

[0177] If there is any inconsistency, it means that the invoice to be certified has not been certified or reimbursed at this time. In this case, it can be recorded as a deducted invoice record after it meets the validity requirements and is reimbursed.

[0178] Reference Figure 6 When the invalid parameter information is less than the critical invalid value information and the basic valid parameter information is less than the critical basic valid value information, the method for converting the invoice information to be authenticated from one of the basic valid group invoice information and the invalid invoice group information into the valid invoice group information includes:

[0179] Step 500: Obtain the resubmission information submitted by the user in the blockchain and send it to the access point IP address corresponding to the tax information in the blockchain.

[0180] Resubmission information is information a user submits to verify the authenticity of their invoice. It can be in any format, such as text. Tax information is the IP address of the tax authority that submitted the invoice. The tax authority determines whether to allow a user to resubmit the invoice.

[0181] Step 501: Receive the addition result information sent back from the access point IP address corresponding to the tax information.

[0182] The added result information is the information uploaded by the IP address of the node corresponding to the tax information, indicating whether the added certificate is allowed.

[0183] Step 502: When the addition result information is the preset permission to add information, obtain the re-assistance certification information submitted by the user in the blockchain.

[0184] Re-supported certification information refers to supplementary certification documents submitted by users. Like supplementary certification information, it provides indirect evidence proving the authenticity of invoices, such as payment statements and shipping documents. Users can obtain this information by uploading it to the blockchain from a public user access point. Permitted additional information refers to information regarding user supplementary certification documents published by the tax administration at the user access point. If the "Permitted Additional Information" message indicates "Permitted Additional Information," the user is permitted to submit supplementary documentation.

[0185] Step 503: Identify the key data in the re-assisted certification information, and define the key data corresponding to the re-assisted certification information as re-certification data information.

[0186] The re-certification data information is the information of the key data in the re-assistance certification information. The identification process is to identify the corresponding key data into text and numbers through ORC.

[0187] Step 504: Filter out re-certification type information from the re-certification data information.

[0188] Information about the type of supporting documentation. For example, the payee and payee, amount in the payment flow, or the product name and insured value on the freight bill. The filtering method for re-supporting supporting documentation is text filtering.

[0189] Step 505: Perform matching analysis based on the access point IP information and the re-certification type information stored in the access point database to determine the access point IP address corresponding to the re-certification type information, and define the access point IP address as the re-certification access point information.

[0190] The re-certification access point information is actually the certification access point information corresponding to the re-certification type information. Therefore, when the re-certification type information is input in the form of certification type information, the corresponding access point IP address is automatically found from the database and output.

[0191] Step 506: Determine whether the re-certification access point information is consistent with one of the certification access point information.

[0192] The purpose of the judgment is to determine whether there has been a previous record.

[0193] Step 5061: If it is consistent with one of the certification access point information, determine whether the re-certification type information is consistent with the certification type information.

[0194] The purpose of the judgment is to determine whether the same proof type has been verified before.

[0195] Step 5062: If it is inconsistent with any certification access point information, then receive the re-verification result information and recalculate the parameter and information, basic proportion information and invalid proportion information based on the valid parameter information, basic valid parameter information, invalid parameter information and re-verification result information.

[0196] The re-verification result information is the result of the corresponding access point's authentication of the re-assisted certification information. If it is inconsistent with any of the certification access point information, it means that the content of the re-verification result information is different, indicating that the verification result information is not the same as the previous result. It needs to be added as additional content to the parameters and information, as well as the denominator of the basic percentage information and invalid percentage information.

[0197] Step 5071: If it is consistent with the proof type information, then receive the re-verification result information and update the consistent proof type information according to the re-verification result information, and then calculate the invalid ratio information, invalid parameter information, basic valid ratio information and basic valid parameter information.

[0198] If it is the proof type information, it means that this is a replacement of the auxiliary proof information that was previously verified. You only need to replace the auxiliary proof information that was previously verified with the current re-verification result information to calculate the invalid proportion information, invalid parameter information, basic valid proportion information and basic valid parameter information.

[0199] Step 5072: If it is inconsistent with the proof type information, the re-verification result information is received and the parameters and information, basic proportion information and invalid proportion information are recalculated based on the valid parameter information, basic valid parameter information, invalid parameter information and re-verification result information.

[0200] If it is different from the previous one, it means that although it is at the same verification access point, the verification content is different. This is the same as step 5062, which means that the verification result information at this time is not repeated with the previous result. It needs to be added as additional content to the parameters and information, as well as the denominator of the basic proportion information and the invalid proportion information.

[0201] Step 508: When the recalculated invalid proportion information is less than the critical invalid proportion information, the invalid parameter information is less than the critical invalid numerical information, the basic valid proportion information is less than the critical basic valid proportion information, and the basic valid parameter information is less than the critical basic valid numerical information, the basic valid invoice group information or the invoice information to be authenticated corresponding to the invalid invoice group information is re-recorded in the blockchain as the valid invoice group information.

[0202] After recalculation, it is re-determined whether the invalid proportion information, invalid parameter information, basic valid proportion information and basic valid parameter information all meet the requirements. If they all meet the requirements, the invoice information to be authenticated corresponding to the basic valid invoice group information or invalid invoice group information can be treated as valid invoice group information and packaged and uploaded to the blockchain.

[0203] Reference Figure 7 : The method for receiving re-verification result information includes:

[0204] Step 600: Obtain the number of re-verification result information.

[0205] The number of times the same re-verification result is triggered is recorded once.

[0206] Step 601: Determine whether the number of times information is greater than the number of times value corresponding to the preset trial number of times information.

[0207] The number of attempts is information about the number of attempts set in advance by the staff, and is set based on human experience, for example, 5 times.

[0208] Step 6011: If the number is greater than the number corresponding to the trial number information, the invoice information to be authenticated is updated to invalid invoice information.

[0209] When the number of times information is greater than the number of times corresponding to the trial number of times information, it means that the user has uploaded too many times. In order to avoid malicious users from repeatedly submitting and trying to test the correct data, the invoice information to be authenticated is directly updated to invalid invoice information.

[0210] Step 6012: If it is less than, the re-verification result information is received normally.

[0211] If it is less than the number of times corresponding to the trial number information, it means that the test can continue, the number of times information can continue to be received, and the re-verification result information can be received normally.

[0212] Reference Figure 8 The method of sending the certification data information to the access point IP address corresponding to the certification access point information after identifying the certification data information includes:

[0213] Step 700: Perform matching analysis based on the association type information and invoice data information stored in the preset association database to determine the association type corresponding to the invoice data information, and define the association type as first association type information.

[0214] The first associated category information is the type of supporting documentation directly associated with the invoice data. A database stores a mapping between invoice data and the first associated category information. This information is identified and recorded by personnel in this field, who attempt to compare all types of supporting documentation with invoice types based on their experience. When the system receives invoice data, it automatically searches the database for the corresponding first associated category information.

[0215] Step 701: Match and analyze the first association type information and the proof type information in the proof data information to determine the proof data information that matches successfully, and define the proof data information as the first proof data information.

[0216] The first certification data information is the certification data information that matches the first associated type information. The matching method is type matching, that is, when the types of the two are the same, the match is considered successful.

[0217] Step 702: Filter out key data in the first certification data information that matches the type of invoice data information, define the key data in the first certification data information as first key certification data information, and define the key data in the invoice data information as first approval key data information.

[0218] The first key verification data is the key data in the first verification data that matches the invoice data type, i.e., the information that directly verifies the authenticity of the invoice data. The first verification key data is the data on the invoice data whose authenticity is verified. The screening method is text comparison, that is, only those with the same text type are selected for screening.

[0219] Step 703: Determine whether the first key certification data information is consistent with the first approval key data information.

[0220] The purpose of the judgment is to confirm whether the data on the invoice is correct. If the invoice and the certificate data do not match, the application can be rejected without verification by the relevant parties.

[0221] Step 7031: If it is consistent with the first approval key data information, the first proof data information is sent to the corresponding proof access point information, the first proof data information is stored in the associated information library and the proof data information other than the first proof data information is defined as the remaining proof data information.

[0222] The associated information repository is the repository that stores the first certification data. The remaining certification data is the certification data other than the first certification data. If they are identical, this indicates that the self-verification is correct, and verification with the corresponding certification access point, i.e., a third party, is required.

[0223] Step 7032: If it is inconsistent with the first approved key data information, the invoice information to be authenticated will be updated to invalid invoice information and packaged and stored in the blockchain.

[0224] If they are different, it means that there are conflicts in the data itself, and the invoice can be rejected without verification by the relevant parties. The invoice information to be verified will be updated to invalid invoice information and packaged and stored on the blockchain.

[0225] Step 704: Perform matching analysis based on the association type information stored in the association database and the first certification data information to determine the association type corresponding to the first certification data information, and define the association type as second association type information.

[0226] The second associated category information is the type of supporting material associated with the first supporting data information. Similar to step 700, when the invoice data information is replaced with the first supporting data information, a corresponding associated category is generated. This category corresponds to the second associated category information. It should be noted that this category is not directly associated with the invoice itself. If it is directly associated with the invoice, it is directly defined as the first associated category information.

[0227] Step 705: Match and analyze the second association type information and the proof type information in the remaining proof data information to determine the remaining proof data information that has been successfully matched, and define the remaining proof data information as the second proof data information.

[0228] The second certification data information is the positive data information that successfully matches the positive category of the second associated category information in the remaining certification data information. The matching method is the same as step 701.

[0229] Step 706: Identify key data in the first proof data information that matches the type of the second proof data information, define the key data in the second proof data information as second key proof data information, and define the key data in the first proof data information as second approval key data information.

[0230] The second key verification data is the key data in the second verification data that matches the type of the first verification data, i.e., it can verify the authenticity of the data in the first verification data. The second verification key data is the data whose authenticity is verified in the first verification data. The screening method is text comparison, that is, only those with the same text type can be selected.

[0231] Step 707: Determine whether the second key certification data information is consistent with the second approval key data information.

[0232] The purpose of the judgment is to determine whether the data is the data on the first certification data information. If even the first certification data information and the second certification data information are inconsistent, the data can be rejected without verification by the relevant party.

[0233] Step 7071: If it is consistent with the second approval key data information, the second proof data information will be sent to the corresponding proof access point information, the second proof data information will be stored in the associated information library and the remaining proof data information will be updated until there is no remaining proof data information or the remaining proof data information is of a type that is not associated with the previous successfully matched proof data information, and the remaining proof data information of a type that is not associated with the previous successfully matched proof data information will be defined as invalid proof data information.

[0234] If it is consistent with the second approved key data information, it is consistent with step 7031 and will not be repeated here.

[0235] Invalid proof data refers to data that has no direct or indirect connection to the invoice data. After step 7071, the above-described step-by-step verification process is repeated until no proof data remains, or there is no remaining proof data that is unrelated to the previously matched proof data. At this point, the remaining positive data has no connection and, as verification is unnecessary, does not need to be sent.

[0236] Step 7072: If the invoice information to be authenticated is inconsistent with the second approval key data information, the invoice information to be authenticated will be updated to invalid invoice information and packaged and stored in the blockchain.

[0237] If they are different, it means that there are conflicts in the data itself, and the invoice can be rejected without verification by the relevant parties. The invoice information to be verified will be updated to invalid invoice information and packaged and stored on the blockchain.

[0238] Step 708: Do not send verification request information to the certification access point information corresponding to the invalid certification data information.

[0239] At this time, the remaining positive data information has no relevance, so it does not need to be sent for unnecessary verification operations.

[0240] Reference Figure 9 :If some parts of the invoice information to be authenticated cannot be identified, the authentication methods include:

[0241] Step 800: Perform matching analysis based on the complete data information and invoice data information stored in the preset complete database to determine the complete data corresponding to the invoice data information, and define the complete data as the current complete data information.

[0242] The current complete data information refers to the complete data that should exist on an invoice of that type, corresponding to the type information in the invoice data. The database stores the mapping between invoice data and the current complete data information, which is recorded by personnel in this field based on analysis, observation, and records of different invoice types in real life and online. When the system receives the invoice data information, it automatically filters the invoice type from the invoice data information and then searches the database for the corresponding current complete data information based on the invoice type. Furthermore, if the invoice type information cannot be identified, the user will be directly notified and the invoice data will be rejected.

[0243] Step 801: Calculate based on the current complete data information and invoice data information to determine the missing data type information.

[0244] Missing data type information refers to data types that cannot be identified in the invoice data information. The data types in the current complete data information are matched with the data types that can be identified in the invoice data information. If there are any data types that cannot be matched, they can be counted as missing data type information.

[0245] Step 802: Match and analyze the missing type data information with the proof type information in any proof data information to determine the proof data information corresponding to the missing type data information, and define the proof data information as missing proof information.

[0246] The missing proof information is the proof data information corresponding to the missing type data information. The matching method is text matching, that is, when the proof type of the missing proof information is known, the text is matched with the proof type information in the proof data information.

[0247] Step 803: Determine whether the missing proof information is stored in the associated information library.

[0248] The purpose of the judgment is to prove whether the information is related to the invoice information, that is, whether it is key data.

[0249] Step 8031: If it is stored in the associated information library, determine whether the verification result information corresponding to the missing proof information is the real data information.

[0250] If it exists, it means that it is key data and needs to be confirmed. The purpose of the judgment is to determine whether the corresponding auxiliary proof information is authentic data.

[0251] Step 8032: If it is not stored in the associated information library, the invoice information to be authenticated will be updated to basic valid invoice information and packaged and stored in the blockchain.

[0252] If it does not exist, there is no need to verify the authenticity of the missing proof information. Since the information cannot be confirmed, it is defined as the invoice information to be verified, updated to the basic valid invoice information and packaged and stored on the blockchain.

[0253] Step 8041: If the data is true, add the data corresponding to the actual type of data in the missing proof information to the invoice data information.

[0254] If the data is real, it means that the missing proof information corresponding to the invoice data information can be supplemented by the proof data information.

[0255] Step 8042: If the data is not authentic, the invoice information to be verified will be updated to invalid invoice information and packaged and stored in the blockchain.

[0256] If not, it means that the key data corresponding to the missing proof information is inaccurate. In this case, the invoice information to be authenticated can be updated to invalid invoice information and packaged and stored in the blockchain.

[0257] 1. Based on the same inventive concept, an embodiment of the present invention provides a blockchain-based overseas invoice authentication system, comprising:

[0258] Reference Figure 10 , a blockchain-based overseas invoice authentication system, including:

[0259] Information acquisition module 903, used to obtain the invoice information to be authenticated and the auxiliary certification information submitted by the user in the preset blockchain;

[0260] The processing module 901 is connected to the information acquisition module 903 and the identification module 906 and is used for storing and processing information;

[0261] The authentication module 904 is connected to the processing module 901 and is used for authentication when there is false data in the verification result information or the information cannot be verified;

[0262] The judging module 902 is connected to the processing module 901 and is used to judge whether the invalid ratio information is greater than the preset critical invalid ratio information;

[0263] The conversion module 905 is connected to the processing module 901 and is used to convert the invoice information to be authenticated from one of the basic valid group invoice information and the invalid invoice group information into the valid invoice group information;

[0264] Identification module 906, for identifying key data in the invoice information to be authenticated and the auxiliary certification information, defining the key data corresponding to the invoice information to be authenticated as invoice data information, defining the key data corresponding to the auxiliary certification information as certification data information, and filtering out certification type information;

[0265] The processing module 901 performs a matching analysis based on the access point IP information and the certification type information stored in the preset access point database to determine the access point IP address corresponding to the certification type information, and defines the access point IP address as the certification access point information;

[0266] The sending module 907 is connected to the processing module 901 and is used to send the preset request verification information and certification data information to the access point IP address corresponding to the certification access point information;

[0267] A receiving module 908 is connected to the processing module 901 and is configured to receive verification result information sent back from the access point IP address corresponding to the certification access point information, wherein the verification result information includes data authenticity information, verification failure information, and data false information;

[0268] If the verification result information received by the receiving module 908 is all true data information, the processing module 901 updates the invoice information to be verified to valid invoice information and packages it up and stores it in the blockchain;

[0269] If the receiving module 908 receives verification result information that contains unverifiable information, the processing module 901 updates the invoice information to be verified to basically valid invoice information and packages it up and stores it in the blockchain;

[0270] If the receiving module 908 receives false data in the verification result information, the processing module 901 updates the invoice information to be authenticated to invalid invoice information and packages it and stores it in the blockchain.

[0271] An embodiment of the present invention provides a computer-readable storage medium storing a computer program that can be loaded by a processor and executed by a blockchain-based overseas invoice authentication method.

[0272] Computer storage media include, for example, various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks, or optical disks.

[0273] Based on the same inventive concept, an embodiment of the present invention provides a smart terminal, including a memory and a processor, wherein the memory stores a computer program that can be loaded by the processor and execute a blockchain-based overseas invoice authentication method.

[0274] Those skilled in the art will clearly understand that for the sake of convenience and brevity, the division of the above-mentioned functional modules is only used as an example for illustration. In actual applications, the above-mentioned functions can be distributed and completed by different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. The specific working processes of the above-mentioned systems, devices, and units can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0275] The above are all preferred embodiments of the present application and are not intended to limit the scope of protection of this application. Unless otherwise stated, any feature disclosed in this specification (including the abstract and drawings) may be replaced by other equivalent or similar features. In other words, unless otherwise stated, each feature is merely an example of a series of equivalent or similar features.

Claims

1. A blockchain-based overseas invoice authentication method, characterized in that: include: Obtain the invoice information and supporting certification information submitted by the user in the preset blockchain; Identify key data in the invoice information to be authenticated and the auxiliary certification information, define the key data corresponding to the invoice information to be authenticated as invoice data information, define the key data corresponding to the auxiliary certification information as certification data information, and filter out certification type information; Performing a matching analysis based on the access point IP information and the certification type information stored in the preset access point database to determine the access point IP address corresponding to the certification type information, and defining the access point IP address as the certification access point information; Sending the preset request verification information and certification data information to the access point IP address corresponding to the certification access point information; Receiving verification result information sent back from the access point IP address corresponding to the certification access point information, the verification result information including data authenticity information, unverifiable information, and data false information; If the verification results are all true, the invoice information to be verified will be updated to valid invoice information and packaged and stored in the blockchain; If there is unverifiable information in the verification result information, the invoice information to be verified will be updated to basic valid invoice information and packaged and stored in the blockchain; If there is false data in the verification result information, the invoice information to be verified will be updated to invalid invoice information and packaged and stored in the blockchain; When the verification result information contains false data or cannot be verified, the authentication method includes: Obtain parameter values ​​in valid invoice information, basic valid invoice information, and invalid invoice information, define the parameter value corresponding to the valid invoice information as valid parameter information, define the parameter value corresponding to the basic valid invoice information as basic valid parameter information, and define the parameter value corresponding to the invalid invoice information as invalid parameter information; Calculate the parameter sum information based on the valid parameter information, the basic valid parameter information, and the invalid parameter information, and respectively calculate the proportion of the basic valid parameter information and the invalid parameter information in the parameter sum information. Define the proportion of the basic valid parameter information as the basic proportion information, and define the proportion of the invalid parameter information as the invalid proportion information. The parameter sum information is the sum of the parameters of the amounts corresponding to the valid parameter information, the basic valid parameter information, and the invalid parameter information. Determine whether the invalid ratio information is greater than the preset critical invalid ratio information; If the invalid ratio exceeds the critical value, it will be recorded as invalid invoice group information in the blockchain and trigger an invalid alarm message; If it is less than the critical invalid ratio information, then determine whether the invalid parameter information is greater than the preset critical invalid value information; If the value is greater than the critical invalid value, it will be recorded as invalid invoice group information in the blockchain and trigger an invalid alarm message; If it is less than the critical invalid value information, then determine whether the basic valid proportion information is greater than the preset critical basic valid proportion information; If it is greater than the critical basic validity ratio information, it will be recorded in the blockchain as basic valid invoice group information and trigger a basic validity alarm information; If it is less than the critical basic effective ratio information, then determine whether the basic effective parameter information is greater than the preset critical basic effective value information; If it is greater than the critical basic validity value information, it will be recorded in the blockchain as basic valid invoice group information and trigger a basic validity alarm information; If it is less than the critical basic valid numerical information, it will be recorded in the blockchain as valid invoice group information and basic valid proportion information.

2. The blockchain-based overseas invoice authentication method according to claim 1, characterized in that: Another method of updating the invoice information to be verified into valid invoice information and storing it in the blockchain includes: Performing a matching analysis based on the invoice record information and invoice data information stored in all access points of the blockchain in the preset invoice database to determine the invoice record corresponding to the invoice data information, and defining the invoice record as the verified invoice record information; Determine whether the invoice record information exists; If there is verified invoice record information, the invoice information to be verified will be updated to valid invoice information and stored in the blockchain; If it does not exist, the verification request information and the certification data information are sent to the access point IP address corresponding to the certification access point information.

3. The blockchain-based overseas invoice authentication method according to claim 2, characterized in that: The method for updating the invoice information to be verified to valid invoice information and storing it in the blockchain includes: Obtain the deducted invoice record information stored in the blockchain; Determine whether the invoice information to be authenticated is consistent with the information of one of the deducted invoice records; If the invoice information is consistent with one of the deducted invoice records, the invoice information to be verified will be updated to invalid invoice information; If it is inconsistent with all the deducted invoice record information, the invoice information to be authenticated will be updated to the valid invoice information and when the user deducts, the deducted invoice record information corresponding to the valid invoice information will be uploaded at the certification access point information corresponding to the preset tax IP information.

4. The blockchain-based overseas invoice authentication method according to claim 3 is characterized in that: When the invalid parameter information is less than the critical invalid value information and the basic valid parameter information is less than the critical basic valid value information, the method for converting the invoice information to be authenticated from one of the basic valid group invoice information and the invalid invoice group information into the valid invoice group information includes: Obtain the resubmission information submitted by the user in the blockchain and send it to the access point IP address corresponding to the tax information in the blockchain; Receiving the added result information sent back from the access point IP address corresponding to the tax information; When the added result information is the preset allowed addition information, obtain the re-assistance proof information submitted by the user in the blockchain; Identify key data in the re-assistance certification information, and define the key data corresponding to the re-assistance certification information as re-certification data information; Filtering recertification type information from the recertification data information; Performing a matching analysis based on the access point IP information and the re-certification type information stored in the access point database to determine the access point IP address corresponding to the re-certification type information, and defining the access point IP address as the re-certification access point information; Determining whether the re-certification access point information is consistent with one of the certification access point information; If it is consistent with one of the certification access point information, then determine whether the re-certification type information is consistent with the certification type information; If it is consistent with the proof type information, the re-verification result information is received and the consistent proof type information is updated according to the re-verification result information, and then the invalid ratio information, invalid parameter information, basic valid ratio information and basic valid parameter information are calculated; If it is inconsistent with the proof type information, the re-verification result information is received and the parameter and information, basic valid parameter information, invalid parameter information and re-verification result information are recalculated; If it is inconsistent with any of the certification access point information, the re-verification result information is received and the parameter and information, basic valid parameter information, invalid parameter information and re-verification result information are recalculated; When the recalculated invalid proportion information is less than the critical invalid proportion information, the invalid parameter information is less than the critical invalid numerical information, the basic valid proportion information is less than the critical basic valid proportion information, and the basic valid parameter information is less than the critical basic valid numerical information, the basic valid invoice group information or the invoice information to be authenticated corresponding to the invalid invoice group information is re-recorded in the blockchain as the valid invoice group information.

5. The blockchain-based overseas invoice authentication method according to claim 4 is characterized in that: Methods for receiving re-verification result information include: Get the number of re-verification result information; Determine whether the number of times information is greater than the number of times value corresponding to the preset trial number information; If it is greater than the number of times corresponding to the trial number information, the invoice information to be authenticated will be updated to invalid invoice information; If it is less than, the re-verification result information is received normally.

6. The blockchain-based overseas invoice authentication method according to claim 4 is characterized in that: The method of sending the certification data information to the access point IP address corresponding to the certification access point information after identifying the certification data information includes: Performing a matching analysis based on the association type information stored in the preset association database and the invoice data information to determine the association type corresponding to the invoice data information, and defining the association type as first association type information; Performing a matching analysis on the first association type information and the proof type information in the proof data information to determine the proof data information that matches successfully, and defining the proof data information as the first proof data information; Filter out key data in the first certification data information that matches the type of the invoice data information, define the key data in the first certification data information as first key certification data information, and define the key data in the invoice data information as first approval key data information; Determining whether the first key certification data information is consistent with the first approval key data information; If the first certification data information is consistent with the first approval key data information, the first certification data information is sent to the corresponding certification access point information, the first certification data information is stored in the associated information library, and the certification data information other than the first certification data information is defined as the remaining certification data information; Performing a matching analysis based on the association type information stored in the association database and the first certification data information to determine the association type corresponding to the first certification data information, and defining the association type as second association type information; Performing a matching analysis on the second association type information and the proof type information in the remaining proof data information to determine the remaining proof data information that has successfully matched, and defining the remaining proof data information as the second proof data information; Identifying key data in the first certification data information that matches the type of the second certification data information, defining the key data in the second certification data information as second key certification data information, and defining the key data in the first certification data information as second approval key data information; Determine whether the second key certification data information is consistent with the second approval key data information; If the second proof data information is consistent with the second approval key data information, the second proof data information is sent to the corresponding proof access point information, the second proof data information is stored in the associated information library, and the remaining proof data information is updated until there is no remaining proof data information or the remaining proof data information is not related to the previously matched proof data information. The remaining proof data information that is not related to the previously matched proof data information is defined as invalid proof data information; Not sending verification request information to the certification access point information corresponding to the invalid certification data information; If the invoice information is inconsistent with the second approval key data, the invoice information to be verified will be updated to invalid invoice information and packaged and stored in the blockchain; If it is inconsistent with the first approved key data information, the invoice information to be authenticated will be updated to invalid invoice information and packaged and stored in the blockchain.

7. The blockchain-based overseas invoice authentication method according to claim 6, characterized in that: If some parts of the invoice information to be authenticated cannot be identified, the authentication methods include: Perform matching analysis based on the complete data information and invoice data information stored in the preset complete database to determine the complete data corresponding to the invoice data information, and define the complete data as the current complete data information; Calculate the missing data type information based on the current complete data information and invoice data information; Matching and analyzing the missing type data information with the proof type information in any proof data information to determine the proof data information corresponding to the missing type data information, and defining the proof data information as missing proof information; Determine whether the missing proof information is stored in the associated information database; If it is stored in the associated information database, determine whether the verification result information corresponding to the missing proof information is the real data information; If the data is true, add the data corresponding to the confirmed type of data in the missing proof information to the invoice data; If the data is not authentic, the invoice information to be verified will be updated to invalid invoice information and packaged and stored in the blockchain; If it is not stored in the associated information database, the invoice information to be authenticated will be updated to basic valid invoice information and packaged and stored on the blockchain.

8. A blockchain-based overseas invoice authentication system, characterized by: The system is used to execute the blockchain-based overseas invoice authentication method according to any one of claims 1 to 7, comprising: The information acquisition module is used to obtain the invoice information to be authenticated and the auxiliary certification information submitted by the user in the preset blockchain; A processing module, connected to the information acquisition module and the identification module, for storing and processing information; An identification module is used to identify key data in the invoice information to be authenticated and the auxiliary certification information, define the key data corresponding to the invoice information to be authenticated as invoice data information, define the key data corresponding to the auxiliary certification information as certification data information, and filter out certification type information; The processing module performs a matching analysis based on the access point IP information and the certification type information stored in the preset access point database to determine the access point IP address corresponding to the certification type information, and defines the access point IP address as the certification access point information; A sending module, connected to the processing module, configured to send the preset request verification information and certification data information to the access point IP address corresponding to the certification access point information; a receiving module connected to the processing module, configured to receive verification result information sent back from the access point IP address corresponding to the certification access point information, wherein the verification result information includes data authenticity information, unverifiable information, and data false information; If the verification result information received by the receiving module is all true data, the processing module will update the invoice information to be verified to valid invoice information and package it up and store it in the blockchain; If the receiving module receives verification results containing information that cannot be verified, the processing module updates the invoice information to be verified to basically valid invoice information and packages it up and stores it in the blockchain; If the receiving module receives false data in the verification result information, the processing module will update the invoice information to be authenticated to invalid invoice information and package it up and store it in the blockchain.

9. A computer-readable storage medium, characterized in that A computer program is stored which can be loaded by a processor and executes a blockchain-based overseas invoice authentication method as described in any one of claims 1 to 7.

Citation Information

Patent Citations

  • Bill verification method and device, apparatus and storage medium

    CN113554029A