Electronic ticket query processing method and apparatus

Abstract

Embodiments of the present specification provide an electronic bill query processing method and device, wherein the electronic bill query processing method comprises: performing bill query according to bill code input by query, reading bill key information of the queried electronic bill based on the queried electronic bill, querying a bill chain containing a bill node corresponding to the queried electronic bill according to the bill key information, querying at least one target bill node associated with the bill node in the bill chain, and obtaining electronic bills corresponding to the at least one target bill node and transaction vouchers mapped by the target bill node as query output of the query input.

Description

[0001] This patent application is a divisional application of Chinese patent application No. 2023104523799, filed on April 21, 2023, entitled "Electronic Invoice Inquiry and Processing Method and Apparatus". Technical Field

[0002] This document relates to the field of data processing technology, and in particular to an electronic invoice query and processing method and apparatus. Background Technology

[0003] With the development of internet technology and the increasing activity of economic activities, more and more companies are choosing to issue electronic invoices in their economic activities. Electronic invoices are convenient to carry, easy to submit, and not easily lost, which greatly facilitates the financial work of companies. However, as electronic invoices become more and more popular, their number is also increasing, making their processing more and more difficult. This places higher demands on the processing methods for electronic invoices. Summary of the Invention

[0004] This specification provides one or more embodiments of an electronic invoice query processing method, comprising: querying an electronic invoice based on an input invoice code, and reading key information of the queried electronic invoice; querying an invoice chain containing the invoice node corresponding to the electronic invoice based on the key information; querying at least one target invoice node associated with the invoice node in the invoice chain; establishing the association between the invoice node and the target invoice node based on the document association relationship between the transaction document mapped by the invoice node and the associated transaction document mapped by the associated invoice node; and obtaining the electronic invoice corresponding to the at least one target invoice node and the mapped transaction document as the query output of the query input.

[0005] This specification provides one or more embodiments of an electronic invoice query processing device, comprising: an invoice key information reading module configured to perform an invoice query based on an input invoice code and read the key information of the queried electronic invoice; an invoice chain query module configured to query an invoice chain containing the invoice node corresponding to the electronic invoice based on the key information; a target invoice node query module configured to query at least one target invoice node associated with the invoice node in the invoice chain; the association between the invoice node and the target invoice node is established based on the document association relationship between the transaction certificate mapped by the invoice node and the associated transaction certificate mapped by the associated invoice node; and a query result output module configured to obtain the electronic invoice corresponding to the at least one target invoice node and the mapped transaction certificate as the query input and the query output.

[0006] This specification provides one or more embodiments of an electronic bill query processing device, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: perform a bill query based on a bill code input from a query input, and read key bill information of the queried electronic bill; based on the key bill information, query a bill chain containing the bill node corresponding to the electronic bill; query at least one target bill node associated with the bill node in the bill chain; the association between the bill node and the target bill node is established based on the document association relationship between the transaction voucher mapped by the bill node and the associated transaction voucher mapped by the associated bill node; and obtain the electronic bill corresponding to the at least one target bill node and the mapped transaction voucher as the query input and query output.

[0007] This specification provides one or more embodiments of a storage medium for storing computer-executable instructions, which, when executed by a processor, implement the following process: querying a bill based on an input bill code, and reading key information of the queried electronic bill. Based on the key information, querying a bill chain containing the bill node corresponding to the electronic bill. Querying at least one target bill node associated with the bill node within the bill chain. The association between the bill node and the target bill node is established based on the document association relationship between the transaction voucher mapped to the bill node and the associated transaction voucher mapped to the associated bill node. Obtaining the electronic bill corresponding to the at least one target bill node and the mapped transaction voucher as the query output. Attached Figure Description

[0008] To more clearly illustrate the technical solutions in one or more embodiments or prior art of this specification, the drawings used in the description of the embodiments or prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. Figure 1 A schematic diagram illustrating the implementation environment of an electronic invoice query and processing method provided in one or more embodiments of this specification; Figure 2 A flowchart of an electronic invoice query and processing method provided for one or more embodiments of this specification; Figure 3 A schematic diagram of a bill chain provided for one or more embodiments of this specification; Figure 4 A flowchart illustrating a processing method for a tax inquiry scenario provided in one or more embodiments of this specification; Figure 5 A flowchart illustrating a processing method for an audit query scenario provided in one or more embodiments of this specification; Figure 6 A schematic diagram of an embodiment of an electronic invoice query and processing device provided in one or more embodiments of this specification; Figure 7 This is a schematic diagram of the structure of an electronic ticket query and processing device provided in one or more embodiments of this specification. Detailed Implementation

[0009] To enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of this document.

[0010] The electronic invoice query processing method provided in this embodiment or one or more embodiments can be applied to the implementation environment of electronic invoice query. (Refer to...) Figure 1 The implementation environment includes at least server 101. Server 101 can be a single server or a server cluster consisting of several servers, or a cloud server of a cloud computing platform. Server 101 is used to query electronic bills based on the input bill code, and to query and output electronic bills associated with the electronic bill and corresponding transaction vouchers based on the electronic bill.

[0011] The implementation environment may also include an electronic invoice database 102, which stores data packets of electronic invoices and invoice chains containing invoice nodes. Server 101 can read key information of electronic invoices from the electronic invoice database 102, and server 101 can also send a query command containing the invoice chain of the corresponding invoice nodes to the electronic invoice database 102 based on the key information of the invoices. The electronic invoice database 102 may also be deployed on server 101.

[0012] In addition, the electronic bills stored in the electronic bill database can also be stored at the issuer or the recipient of the electronic bill. The server 101 can read the data packets of the electronic bills from the issuer or the recipient for electronic bill query processing.

[0013] In this implementation environment, during the electronic invoice query process, server 101 queries the electronic invoice based on the input invoice code and reads the key information of the queried electronic invoice. Based on the key information, it queries the invoice chain containing the invoice node corresponding to the electronic invoice. In the queried invoice chain, it queries at least one target invoice node associated with the invoice node, obtains the electronic invoice and the mapped transaction voucher corresponding to at least one target invoice node, and uses the electronic invoice and the mapped transaction voucher as the query input and query output. This allows the electronic invoice queryer to query electronic invoices and transaction vouchers related to the electronic invoice corresponding to the input invoice code, thereby improving the efficiency of electronic invoice query.

[0014] This specification provides one or more embodiments of an electronic invoice query and processing method, as follows: Reference Figure 2 The electronic invoice query processing method provided in this embodiment specifically includes steps S202 to S208.

[0015] Step S202: Perform a bill query based on the bill code entered in the query, and read the key information of the electronic bill found in the query.

[0016] The invoice code mentioned in this embodiment refers to the unique identification information carried by the electronic invoice for querying electronic invoice information. Based on the invoice code input by the querying party, the data packet corresponding to the electronic invoice with that invoice code is retrieved. Through this data packet, the fields corresponding to the invoice information of the electronic invoice can be retrieved. The invoice code can be the electronic invoice's QR code, invoice code, invoice number, or the code corresponding to the invoice image. The key invoice information refers to at least one field corresponding to the invoice information retrieved from the electronic invoice, such as the field corresponding to the invoice issuer's name and / or the field corresponding to the invoice recipient's name.

[0017] Optionally, the invoice code can be entered by the auditing institution or the tax authority through a query interface; that is, the electronic invoice querying party can be an auditing institution or a tax authority.

[0018] In practice, the system searches for invoices based on the input invoice code. After finding the electronic invoice corresponding to the invoice code, it reads the key information of the electronic invoice. Specifically, when the invoice queryer inputs an invoice code, the system processes the query based on the input invoice code using a query algorithm, outputs a data packet of the electronic invoice corresponding to the invoice code, and reads the key information of the electronic invoice from the corresponding fields of the invoice information in the data packet.

[0019] In addition, during the process of reading the key information of the electronic invoices, different electronic invoice query parties may use different fields corresponding to the invoice information as key information. In this regard, the key information of the invoice can be determined to make the reading of key information of the invoice more accurate.

[0020] In the specific execution process, when reading the key information of the electronic invoice, the electronic invoice queryer can select the key information of the invoice based on the read information. The key information of the invoice can be determined through the interaction of the control. For example, the electronic invoice queryer can trigger the selection of the invoice issuer name as the key information of the invoice through the control. Then, the field corresponding to the invoice issuer name of the queried electronic invoice will be read and the field corresponding to the invoice issuer name will be used as the key information of the invoice. Alternatively, at least one piece of bill information can be pre-set as key bill information. For example, the recipient's name can be pre-set as key bill information. That is, the field corresponding to the recipient's name of the queried electronic bill can be read and the field corresponding to the recipient's name can be used as key bill information. Alternatively, the key information of the invoice can be determined based on the type of institution that queries the electronic invoice. Corresponding fields of the invoice information can be set as key information based on different institution types. For example, the key information of the invoice corresponding to the auditing institution can be set as the name of the invoice issuer in advance. When the auditing institution queries the invoice, the field corresponding to the name of the invoice issuer of the queried electronic invoice can be read and the field corresponding to the name of the invoice issuer can be used as the key information of the invoice.

[0021] Step S204: Based on the key information of the bill, query the bill chain containing the bill node corresponding to the electronic bill.

[0022] The bill chain described in this embodiment is a chain composed of one or more bill nodes and one or more transaction vouchers for the bill nodes. Each bill node records a corresponding field for at least one piece of information about the electronic bill; that is, there is a one-to-one correspondence between the bill node and the electronic bill. This at least one piece of information can be the name of the issuer and / or the name of the payee. The transaction voucher can be a transaction order and / or an electronic transaction contract. Optionally, among the transaction parties recorded in at least one bill subject field of the electronic bill corresponding to a bill node in the bill chain, there must be at least one identical transaction party. For example, in the bill node's bill chain for Company A, the name of Company A must be present in the field corresponding to the name of the issuer of the electronic bill. That is, if the name of Company A is present in the field corresponding to the name of the issuer of all electronic bills corresponding to bill nodes in the bill chain, then the data chain is Company A's data chain.

[0023] In addition, the bill chain may contain one or more bill redirection nodes, which can be used to redirect to the bill chain of the transaction participant to which the bill redirection node belongs.

[0024] In this blockchain, a mapping relationship can be established between bill nodes and transaction vouchers. This mapping relationship can be based on the correspondence between the electronic bills corresponding to the bill nodes and the transaction vouchers. For example, Figure 3 The mobile phone sales invoice a corresponding to the invoice node 301 shown is issued based on the mobile phone sales order 302. Therefore, a mapping relationship is established between invoice node 301 and mobile phone sales order 302.

[0025] Furthermore, the transaction certificates mapped by the bill nodes in the bill chain can have certificate association relationships. These certificate association relationships can be established based on the circulation correspondence between the transaction objects recorded in the transaction certificates; or based on the preparation relationship between the transaction objects recorded in the transaction certificates; or based on the contractual dependency relationship between the transaction certificates.

[0026] In addition, the document association can also be the relationship between transaction objects recorded on the transaction document; optionally, the document association between the transaction documents mapped by any two document nodes in the document chain includes at least one of the following: the buying and selling circulation relationship of the transaction objects recorded on the transaction document, and the use preparation relationship of the transaction objects recorded on the transaction document. Further, regarding the buying and selling circulation relationship and the use preparation relationship of the transaction objects; optionally, the buying and selling circulation relationship includes a buying circulation relationship and a selling circulation relationship, and the use preparation relationship includes a preparation input relationship and a preparation output relationship.

[0027] In practical applications, to establish the document association relationship between transaction vouchers mapped to bill nodes in a bill chain, a matching process can be performed on the transaction objects recorded in the transaction vouchers mapped to any two bill nodes in the bill chain. This allows the establishment of the document association relationship between the transaction objects based on the matching process. In one optional implementation of this embodiment, the following operation is performed on any two bill nodes in the bill chain: Extract the preparation information of the first transaction object recorded in the transaction certificate record mapped by the first bill node, and the preparation information of the second transaction object recorded in the transaction certificate record mapped by the second bill node; If a matching relationship is detected between the preparation information of the first transaction object and the preparation information corresponding to the second transaction, then a document association relationship is established between the transaction documents mapped by the two bill nodes. In another scenario, if no matching relationship is detected between the preparation information of the first transaction object and the preparation information corresponding to the second transaction, no processing is required.

[0028] Specifically, for any two bill nodes in the bill chain, the preparation information of the first transaction object recorded in the transaction certificate mapped by the first bill node is extracted, and the preparation information of the second transaction object recorded in the transaction certificate mapped by the second bill node is extracted. The preparation information of the first transaction object and the preparation information of the second transaction object are matched. If the preparation relationship of the preparation information of the first transaction object and the preparation information of the second transaction object is confirmed to match, it indicates that there is a preparation matching relationship between the preparation information of the first transaction object and the preparation information of the second transaction object, and the certificate association relationship between the transaction certificate mapped by the first bill node and the transaction certificate mapped by the second bill node is established.

[0029] For example, in such Figure 3 In the bill chain of the mobile phone manufacturer shown, the manufacturing information of the mobile phone battery recorded in the mobile phone battery sales contract 304 mapped by bill node 303 is extracted, and the manufacturing relationship of the battery cell recorded in the battery cell sales contract mapped by bill node 305 is extracted. The manufacturing relationship matching processing of the mobile phone battery and the battery cell is performed. The manufacturing relationship matching is confirmed, and the voucher association relationship between the mobile phone battery sales contract 304 mapped by bill node 303 and the battery cell sales contract 306 mapped by bill node 305 is established.

[0030] In addition, the establishment of a certificate association between any two bill nodes in the bill chain can also be achieved by detecting the contractual dependency relationship of the electronic transaction contracts mapped to any two bill nodes in the bill chain. In another optional implementation provided in this embodiment, the following operation is performed for any two bill nodes in the bill chain: Check whether the transaction object of the electronic transaction contract record mapped by the first bill node is the same as the transaction object of the electronic transaction contract record mapped by the second bill node; If not, then no action needs to be taken; If so, detect whether there is a contractual dependency relationship between the electronic transaction contract mapped by the first bill node and the electronic transaction contract mapped by the second bill node. If so, establish a certificate association relationship between the transaction certificates of the two bill nodes.

[0031] If it does not exist, no action needs to be taken.

[0032] Specifically, for any two bill nodes in the bill chain, the transaction object of the electronic transaction contract record mapped by the first bill node is extracted, and the transaction object of the electronic transaction contract record mapped by the second bill node is extracted. It is then checked whether the transaction object of the electronic transaction contract record mapped by the first bill node is the same as that of the electronic transaction contract record mapped by the second bill node. If they are the same, it is then checked whether there is a contractual dependency relationship between the electronic transaction contracts mapped by the first bill node and the electronic transaction contracts mapped by the second bill node. If so, the document association relationship between the transaction vouchers mapped by the first bill node and the transaction vouchers mapped by the second bill node is established. The contractual dependency relationship can be a parent-child contract relationship or a partial delivery / supply contract relationship under the same contract.

[0033] In addition, it can also detect whether there is an order dependency relationship between the transaction orders mapped between any two bill nodes. If so, it establishes a certificate association relationship between the transaction certificates mapped between the two bill nodes.

[0034] For example, in such Figure 3 In the bill chain of the mobile phone manufacturer shown, the transaction object of the mobile phone sales parent contract record 308 mapped by bill node 307 is extracted, and the transaction object of the mobile phone sales sub-contract 310 recorded by bill node 309 is extracted. The transaction object of the sales contracts mapped by bill nodes 307 and 309 is mobile phones. It is detected that the sales sub-contract 308 is a sub-contract of the sales parent contract 310. The voucher association relationship between the mobile phone sales parent contract 308 mapped by bill node 307 and the mobile phone sales sub-contract 310 mapped by bill node 309 is established.

[0035] It should be noted that the two methods provided above for establishing the certificate association relationship between transaction certificates mapped to any two bill nodes in the bill chain can be combined to make the query results of the electronic bill query party more targeted. For example: extract the preparation information of the first transaction object recorded in the transaction certificate mapped to the first bill node, and the preparation information of the second transaction object recorded in the transaction certificate mapped to the second bill node; detect whether there is a preparation matching relationship between the preparation information of the first transaction object and the preparation information corresponding to the second transaction; if so, detect whether there is a contractual dependency relationship between the electronic transaction contract mapped to the first bill node and the electronic transaction contract mapped to the second bill node; if so, establish the certificate association relationship between the transaction certificates mapped to any two bill nodes.

[0036] In addition, the bill nodes in the bill chain can also have associated relationships. Optionally, the association between the bill node and the target bill node is established based on the certificate association relationship between the transaction certificate mapped by the bill node and the associated transaction certificate mapped by the associated bill node.

[0037] In practice, based on the key information of the queried electronic invoice, the system queries for the invoice chain containing the corresponding invoice node. Specifically, the query process can be performed by searching for at least one invoice chain corresponding to the recipient's name, then searching for the invoice node corresponding to the electronic invoice within that chain, and finally selecting the invoice chain containing the corresponding invoice node.

[0038] In practical applications, for newly signed transaction vouchers or newly issued electronic bills, it is also necessary to construct bill nodes in the bill chain so that the bill chain can be updated and supplemented. In one optional implementation of this embodiment, any bill node in the bill chain is constructed in the following way: Upon detecting a payment or collection instruction from the transacting party for the transaction voucher, a node for configuring a bill is created in the bill chain; The transaction certificate obtained through the first data interface is associated with the bill node to be configured; After the electronic bill of the transaction certificate is generated, the bill node to be configured is initialized based on the bill information of the electronic bill of the transaction certificate, so as to obtain the bill node corresponding to the electronic bill of the transaction certificate.

[0039] Specifically, after detecting a payment or receipt instruction from the transacting party for a transaction voucher, a bill node to be configured is created in the bill chain. The first data interface is called to obtain the transaction voucher, and the transaction voucher is associated with the bill node to be configured. After the electronic bill of the transaction voucher is generated, the bill node to be configured is initialized based on the bill information of the electronic bill of the transaction order, and the bill node corresponding to the electronic bill of the transaction voucher is obtained.

[0040] For example, in such Figure 3 In the bill chain of the mobile phone manufacturer shown, after the payment instruction of mobile phone sales order 302 is detected, a bill node to be configured is created in the bill chain of the mobile phone manufacturer. After the mobile phone sales invoice a is generated, the bill node to be configured is initialized based on the invoice information of mobile phone sales invoice a, and the bill node 301 corresponding to mobile phone sales order 302 is obtained.

[0041] Step S206: Query at least one target bill node associated with the bill node in the bill chain.

[0042] In specific implementation, based on the above-mentioned bill chain, at least one bill node that is associated with the bill node corresponding to the queried electronic bill is searched in the bill chain, and the at least one bill node associated with the above-mentioned bill node is taken as the target bill node.

[0043] Based on the construction of any one of the bill nodes in the aforementioned bill chain, in practical applications, the document association relationship between the transaction certificate mapped to any one of the bill nodes in the constructed bill chain and the associated transaction certificate of the associated bill node can be established through the circulation correspondence relationship of the circulation batch information of the transaction object in the transaction certificate. In an optional implementation provided in this embodiment, the document association relationship between the transaction certificate mapped to the bill node and the associated transaction certificate mapped to the associated bill node is established in the following way: Obtain the circulation batch information of the transaction object of the transaction certificate submitted through the second data interface; If there is a circulation correspondence between the circulation batch information and the transaction object of the related transaction voucher mapped by the related bill node, then establish a voucher association relationship between the transaction voucher of the bill node and the related transaction voucher of the related bill node. If there is no corresponding circulation relationship between the circulation batch information and the transaction object of the related transaction voucher mapped to the related bill node, no processing is required.

[0044] Specifically, after the construction of the bill nodes in the aforementioned bill chain is completed, the transaction vouchers are obtained through the second data interface. The transaction object and circulation batch information of the transaction object in the transaction voucher are extracted. If there is a circulation correspondence between the circulation batch information and the transaction object of the related transaction voucher mapped by the related bill node, a voucher association relationship is established between the transaction voucher of the bill node and the related transaction voucher of the related bill node. The bill node is associated with the target bill node through the voucher association relationship between the transaction voucher of the bill node and the related transaction voucher of the related bill node. After detecting the instruction to obtain the circulation batch information of the transaction object of the transaction voucher, the second data interface can obtain the circulation batch information from the transaction party. The circulation batch can be the sales batch and / or the preparation batch.

[0045] Furthermore, by establishing a document association relationship based on the circulation correspondence of the circulation batch information of the transaction object in the transaction document, it is also possible to obtain the preparation batch information and / or sales batch information of the transaction object of the transaction order submitted through the second data interface; if the preparation batch information has a preparation dependency relationship with the transaction object of the transaction document mapped by the target bill node, then a document association relationship is established between the bill node and the target bill node.

[0046] Based on the construction of any one of the bill nodes in the bill chain, in practical applications, the document association relationship between the transaction certificate mapped to any one bill node in the bill chain and the related transaction certificate of the associated bill node can also be established through the preparation relationship between the transaction object in the transaction certificate and the related transaction object in the associated transaction. In another optional implementation provided in this embodiment, the document association relationship between the transaction certificate mapped to the bill node and the related transaction certificate mapped to the associated bill node is established in the following way: Extract the purpose information of the transaction object from the electronic transaction contract record mapped by the bill node; Based on the usage information and the related electronic transaction contract records mapped by the related bill nodes, the preparation information of the related transaction objects is determined to establish the preparation relationship between the transaction objects and the related transaction objects. If the preparation relationship is a preset preparation relationship, then establish a certificate association relationship between the electronic transaction contract of the bill node and the associated electronic transaction contract of the associated bill node; If the preparation relationship is not the preset preparation relationship, no processing is required.

[0047] Specifically, after the construction of the bill nodes in the aforementioned bill chain is completed, the purpose information of the transaction objects in the electronic transaction contract records mapped by the bill nodes is extracted. Based on this purpose information and the preparation information of the related transaction objects in the related electronic transaction contract records mapped by the related bill nodes, the preparation relationship between the transaction objects and the related transaction objects is determined. If the preparation is a preset preparation relationship, it indicates that the transaction objects of the electronic transaction contract of the bill node and the transaction objects of the related electronic transaction contract of the related bill node are in a preset preparation relationship. The document association relationship between the transaction voucher of the bill node and the related transaction voucher of the related bill node is established. The purpose information can be manufacturing information and / or usage information.

[0048] Furthermore, regarding the method of establishing a document association relationship between transaction objects in transaction vouchers and related transaction objects in related transaction vouchers, the preparation information of transaction objects in the electronic transaction contract records mapped by the bill node can also be extracted; based on the preparation information and the preparation information of related transaction objects in the related electronic transaction contract records mapped by the related bill node, the preparation relationship between the transaction object and the related transaction object can be determined; if the preparation relationship is a preset preparation relationship, then the document association relationship between the bill node and the related bill can be established.

[0049] It should be noted that, based on the construction method of the bill nodes in the aforementioned bill chain, the establishment of the certificate association relationship between the transaction certificate mapped by the bill node and the related transaction certificate mapped by the associated bill node can also be achieved by using the certificate association relationship establishment method of any two transaction certificates mapped by the bill nodes in the aforementioned bill chain, as well as a combination thereof. Furthermore, regarding the certificate association relationship between the electronic transaction contract and / or transaction order mapped by the bill node and the related electronic transaction contract and / or related transaction order mapped by the associated bill node, the two certificate association establishment methods provided above can also be combined to establish more targeted certificate association relationships. For example: obtaining the circulation batch information of the transaction object of the transaction order submitted through the second data interface; detecting whether there is a circulation correspondence between the circulation batch information and the transaction object of the related transaction certificate mapped by the associated bill node; if so, extracting the preparation information of the transaction object recorded in the electronic transaction contract mapped by the bill node; detecting whether the preparation relationship between the preparation information and the preparation information of the related transaction object recorded in the related electronic transaction contract mapped by the associated bill node is a preset preparation relationship; and then establishing the certificate association relationship between the bill node and the associated bill.

[0050] Furthermore, the establishment of the certificate association relationship between any two bill nodes mapped in the above-mentioned bill chain can also be achieved by using the method of establishing and combining the certificate association relationship between the transaction certificate mapped by the above-mentioned bill node and the related transaction certificate mapped by the related bill node.

[0051] In the case where the document association relationship between any two document nodes in the document chain includes the buying and selling circulation relationship of the transaction object recorded in the transaction document and / or the usage preparation relationship of the transaction object recorded in the transaction document, in an optional implementation of this embodiment, for querying at least one target document node associated with a document node in the document chain, querying at least one target document node associated with the document node in the document chain includes: The transaction object mapped to the transaction certificate record of the candidate bill node in the bill chain is used as the candidate transaction object; The candidate transaction objects are detected to have a buying and selling relationship and / or a use preparation relationship with the transaction certificate records mapped to the bill node. The candidate bill node to which the transaction certificate of the detected candidate transaction object belongs is taken as the target bill node.

[0052] Specifically, the transaction objects recorded in the transaction vouchers mapped by the candidate bill nodes in the bill chain are extracted, and these transaction objects are used as candidate transaction objects. The transaction objects recorded in the transaction vouchers mapped by the bill nodes are extracted, and the buying and selling circulation relationship and / or circulation preparation relationship between the transaction objects and the candidate transaction objects are detected. If a relationship exists, the candidate bill nodes corresponding to the transaction vouchers of the candidate transaction objects with the relationship are queried, and these candidate bill nodes are used as target bill nodes. The candidate bill nodes can be at least one bill node in the bill chain other than the bill node corresponding to the queried electronic bill.

[0053] For example, in such Figure 3 In the bill chain of the mobile phone manufacturer shown, if the bill node corresponding to the electronic bill found above is bill node 301, the transaction object of the transaction voucher mapped by bill nodes 303, 305, 307 and 309 in the bill chain is extracted. The transaction object of the mobile phone sales order 302 mapped by bill node 301 is extracted. It is detected that the mobile phone recorded in the mobile phone sales order 302 has a sales circulation relationship with the mobile phone sales parent contract 308, and it is detected that the mobile phone recorded in the mobile phone sales order 302 has a preparation input relationship with the mobile phone battery recorded in the mobile phone battery sales contract 304. The bill node 307 corresponding to the mobile phone sales parent contract 308 and the bill node 303 corresponding to the mobile phone battery sales contract 304 are queried, and bill nodes 303 and 307 are taken as target bill nodes.

[0054] Furthermore, when querying at least one target bill node associated with a bill node in the bill chain, the query can also be performed based on the contractual dependency relationship of the electronic transaction contract mapped to the bill node. In one optional implementation of this embodiment, querying at least one target bill node associated with the bill node in the bill chain includes: The candidate bill nodes in the bill chain that have a contractual dependency relationship with the candidate electronic transaction contracts mapped to the candidate bill nodes are selected as the target bill nodes.

[0055] Specifically, the candidate electronic transaction contracts mapped to the candidate electronic transaction contracts in the bill chain are extracted, and the electronic transaction contracts mapped to the bill nodes are extracted. The existence of a contractual dependency relationship between the candidate electronic transaction contracts and the electronic transaction contracts is detected. If a dependency relationship exists, the candidate electronic transaction contract corresponding to the candidate electronic transaction contract that has a contractual dependency relationship with the electronic transaction contract is queried, and the candidate electronic transaction contract is used as the target bill node.

[0056] For example, in such Figure 3In the bill chain of the mobile phone manufacturer shown, if the bill node corresponding to the above-queried electronic bill is bill node 307, extract the electronic transaction contracts mapped by bill nodes 301, 303, 305, and 309 in the bill chain, extract the mobile phone sales parent contract 308 mapped by bill node 307, detect that there is a contractual dependency relationship between the mobile phone sales sub-contract 310 and the mobile phone sales parent contract 308, query the bill node 307 corresponding to the mobile phone sales parent contract 308, and take bill node 307 as the target bill node.

[0057] Step S208: Obtain the electronic bill and the mapped transaction certificate corresponding to the at least one target bill node as the query output of the query input.

[0058] In practice, for each target bill node found, at least one electronic bill corresponding to the target bill node and at least one transaction certificate mapped to the target bill node are obtained as the query output of the above query input. Specifically, for each target bill node found, the electronic bill corresponding to the at least one target bill node and the transaction certificate mapped to the at least one target bill node are extracted, and the electronic bill corresponding to the at least one target bill node and the transaction certificate mapped to the at least one target bill node are used as the output of the query input.

[0059] Furthermore, regarding the query output, the query results can be set to include only the electronic invoice or the transaction voucher corresponding to the target invoice node; alternatively, the electronic invoice querying party can select at least one piece of information from the electronic invoice corresponding to the target invoice node as the query output through interactive controls, allowing the electronic invoice querying party to choose the query results; or, the query output can be preset based on the type of organization of the electronic invoice querying party, for example: if the electronic invoice querying party is a tax authority, the electronic invoice corresponding to the target invoice node can be used as the query output; if the electronic invoice querying party is an auditing institution, the transaction order and electronic contract corresponding to the target invoice node can be used as the query output.

[0060] In practical applications, when there are multiple cooperating parties or multiple cooperating entities in a transaction, the electronic bill inquiry party may need to query the transaction bills of the cooperating parties' bill nodes. This can be achieved by setting bill jump nodes in the bill chain, allowing the electronic bill inquiry party to query the transaction bills of the bill nodes in the transaction participants' bill chains. Optionally, the bill chain also includes bill jump nodes of the transaction participants' bills mapped to each bill node. Accordingly, in an optional implementation provided in this embodiment, it further includes: If a redirect query command is detected for the redirect node, the system will redirect to the bill chain of the transaction participant to which the redirect node belongs. Extract the associated transaction vouchers of the corresponding bill nodes in the bill chain of the transaction participants as the query output of the query input.

[0061] Specifically, upon detecting a jump instruction for a transaction participant's bill jump node in an electronic transaction contract mapped to a bill node, the system jumps to the bill chain of the transaction participant to which the bill jump node belongs. In this bill chain, the system queries the associated transaction certificate of the bill node corresponding to the bill jump node and uses the associated transaction certificate as the query input and the query output.

[0062] For example, in such Figure 3 In the bill chain of the mobile phone manufacturer shown, when a jump instruction is detected for the bill jump node 311 of the transaction participant, the system jumps to the bill chain of the mobile phone transaction participant, queries the electronic transaction contract mapped by the bill node in the bill chain of the mobile phone transaction participant, and outputs the query with the electronic transaction contract as the query input.

[0063] In summary, the one or more electronic bill query processing methods provided in this embodiment, after the electronic bill queryer inputs the bill code, perform a bill query based on the input bill code, read the key bill information in the data packet of the queried electronic bill, and then query the bill chain through the key bill information, thereby improving the convenience of electronic bill query. Regarding the bill chain query process, based on the key bill information, the method queries the bill chain containing the bill node corresponding to the electronic bill, queries at least one target bill node associated with the bill node corresponding to the electronic bill in the bill chain, and then uses the obtained electronic bill corresponding to the target bill node and the mapped transaction voucher as the query input and output results. This allows the electronic bill queryer to query the electronic bill and transaction voucher in the bill chain using the input bill code, improving the query efficiency of the electronic bill queryer. Furthermore, it also allows the electronic bill queryer to select key bill information according to their own needs, improving the targeting of the query. Furthermore, electronic invoices can connect upstream and downstream enterprises of products, making the circulation and production relationships of products clearer and easier to query electronic invoices and transaction vouchers. In addition, they can also be connected to tax authorities to process electronic invoices, enabling tax authorities to carry out their work more efficiently.

[0064] The following description uses the application of the electronic invoice query and processing method provided in this embodiment in a tax inquiry scenario as an example to further illustrate the electronic invoice query and processing method provided in this embodiment. (See also...) Figure 4The electronic invoice query and processing method applied to tax inquiry scenarios includes the following steps.

[0065] Step S402: Based on the invoice code entered by the tax authority through the query interface, perform an invoice query and read the name of the recipient of the queried goods purchase invoice.

[0066] Prior to this, after detecting the payment or receipt instructions from the transacting party for the transaction order, a bill node to be configured is created in the bill chain. The transaction order obtained through the payment application interface is associated with the bill node to be configured. After the electronic bill for the transaction order is generated, the bill node to be configured is initialized based on the bill information of the electronic bill for the transaction order, obtaining the bill node corresponding to the electronic bill for the transaction order. If it exists, the voucher association relationship between the transaction order of the bill node and the associated transaction order of the associated bill node is established.

[0067] Alternatively, extract the purpose information of the transaction objects from the transaction order records mapped to the bill node. Based on the purpose information and the preparation information of the related transaction objects in the related transaction order records mapped to the associated bill node, determine the preparation relationship between the transaction objects and the related transaction objects. If the preparation relationship is a preset preparation relationship, then establish the voucher association relationship between the transaction order of the bill node and the related transaction order of the associated bill node.

[0068] Step S404: Based on the name of the invoice recipient, query the invoice chain containing the invoice node corresponding to the purchase invoice for the goods.

[0069] Step S406: Query the transaction order records mapped by the candidate bill nodes in the bill chain as candidate transaction commodities.

[0070] The association between a bill node and a target bill node in the bill chain is established based on the buying and selling circulation relationship of the transaction orders mapped to the bill node and the related transaction orders mapped to the related bill node.

[0071] Step S408: Detect candidate transaction commodities that have a buying and selling relationship with the transaction order records mapped to the bill node, and take the candidate bill node corresponding to the transaction order of the detected candidate transaction commodity as the target bill node.

[0072] Step S410: Obtain the electronic invoice and transaction order corresponding to the target bill node as the query input and output.

[0073] Step S412: A jump query instruction for the bill jump node of the transaction order is detected, and the jump is made to the bill chain of the transaction participant to which the bill jump node belongs.

[0074] Step S414: Extract the associated electronic transaction contract of the corresponding bill node in the bill chain of the transaction participants as the query input and query output.

[0075] The following description uses the application of an electronic invoice query and processing method provided in this embodiment in an audit query scenario as an example to further illustrate the electronic invoice query and processing method provided in this embodiment. (See also...) Figure 5 The electronic invoice query and processing method applied to audit query scenarios includes the following steps.

[0076] Step S502: Based on the invoice code entered by the auditing agency through the query interface, perform invoice query and read the name of the invoice issuer of the service sales invoice found in the query.

[0077] Prior to this, the preparation information of the first transaction object in the electronic transaction contract record mapped by the first bill node, and the preparation information of the second transaction object in the electronic transaction contract record mapped by the second bill node are extracted. If a preparation matching relationship is detected between the preparation information of the first transaction object and the preparation information corresponding to the second transaction, then a certificate association relationship is established between the electronic transaction contracts mapped by the first bill node and the electronic transaction contracts mapped by the second bill node.

[0078] Alternatively, check whether the transaction object recorded in the electronic transaction contract mapped by the first bill node is the same as the transaction object recorded in the electronic transaction contract recorded by the second bill node. If so, check whether there is a contractual dependency relationship between the electronic transaction contracts mapped by the first bill node and the electronic transaction contracts mapped by the second bill node. If so, establish a certificate association relationship between the electronic transaction contracts mapped by the first bill node and the electronic transaction contracts mapped by the second bill node.

[0079] Step S504: Based on the invoice issuer's name, query the bill chain containing the bill node corresponding to the service sales invoice.

[0080] Step S506: Query the candidate electronic transaction contracts mapped to the candidate electronic transaction contracts in the bill chain that have a contractual dependency relationship with the electronic transaction contracts mapped to the bill nodes, and select the candidate bill nodes as the target bill nodes.

[0081] The association between a bill node and a target bill node is established based on the document association relationship between the transaction documents mapped to the bill node and the related transaction documents mapped to the related bill node.

[0082] Step S508: Obtain the electronic invoice and the mapped electronic transaction contract corresponding to the target bill node as the query input and query output.

[0083] This manual provides an embodiment of an electronic invoice query and processing device as follows: In the above embodiments, an electronic invoice query and processing method is provided, and correspondingly, an electronic invoice query and processing device is also provided, which will be described below with reference to the accompanying drawings.

[0084] Reference Figure 6 The diagram illustrates an embodiment of an electronic invoice query and processing device provided in this embodiment.

[0085] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0086] This embodiment provides an electronic invoice query and processing device, including: The invoice key information reading module 602 is configured to perform invoice queries based on the invoice code entered in the query, and read the key information of the queried electronic invoices; The bill chain query module 604 is configured to query the bill chain containing the bill nodes corresponding to the electronic bill based on the key information of the bill; The target bill node query module 606 is configured to query at least one target bill node associated with the bill node in the bill chain; the association between the bill node and the target bill node is established based on the document association relationship between the transaction certificate mapped by the bill node and the associated transaction certificate mapped by the associated bill node. The query result output module 608 is configured to obtain the electronic bills and mapped transaction vouchers corresponding to the at least one target bill node as the query input and output the query result.

[0087] This manual provides an embodiment of an electronic invoice query and processing device as follows: Corresponding to the electronic invoice query and processing method described above, based on the same technical concept, one or more embodiments of this specification also provide an electronic invoice query and processing device, which is used to execute the electronic invoice query and processing method provided above. Figure 7 This is a schematic diagram of the structure of an electronic ticket query and processing device provided in one or more embodiments of this specification.

[0088] This embodiment provides an electronic invoice query and processing device, comprising: like Figure 7As shown, electronic ticket inquiry and processing devices can vary significantly due to differences in configuration or performance. They may include one or more processors 701 and a memory 702, with the memory 702 storing one or more application programs or data. The memory 702 can be temporary or persistent storage. The application programs stored in the memory 702 may include one or more modules (not shown), each module including a series of computer-executable instructions from the electronic ticket inquiry and processing device. Furthermore, the processor 701 may be configured to communicate with the memory 702, executing the series of computer-executable instructions stored in the memory 702 on the electronic ticket inquiry and processing device. The electronic ticket inquiry and processing device may also include one or more power supplies 703, one or more wired or wireless network interfaces 704, one or more input / output interfaces 705, one or more keyboards 706, etc.

[0089] In one specific embodiment, the electronic invoice query processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the electronic invoice query processing device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following: Search for invoices based on the invoice code entered in the query, and read the key information of the electronic invoices found in the query. Based on the key information of the invoice, query the invoice chain containing the invoice node corresponding to the electronic invoice; In the bill chain, query at least one target bill node associated with the bill node; the association between the bill node and the target bill node is established based on the document association relationship between the transaction document mapped by the bill node and the associated transaction document mapped by the associated bill node; The query output is obtained by taking the electronic bill and the mapped transaction certificate corresponding to the at least one target bill node as the query input.

[0090] This specification provides an example of a storage medium as follows: In accordance with the above-described electronic invoice query and processing method, and based on the same technical concept, one or more embodiments of this specification also provide a storage medium.

[0091] The storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed by a processor, implement the following process: Search for invoices based on the invoice code entered in the query, and read the key information of the electronic invoices found in the query. Based on the key information of the invoice, query the invoice chain containing the invoice node corresponding to the electronic invoice; In the bill chain, query at least one target bill node associated with the bill node; the association between the bill node and the target bill node is established based on the document association relationship between the transaction document mapped by the bill node and the associated transaction document mapped by the associated bill node; The query output is obtained by taking the electronic bill and the mapped transaction certificate corresponding to the at least one target bill node as the query input.

[0092] It should be noted that the embodiments concerning storage media in this specification and the embodiments concerning electronic invoice query processing methods in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding methods described above, and the repeated parts will not be described again.

[0093] The various embodiments in this specification are described in a progressive manner. For the same or similar parts between the various embodiments, please refer to each other. Each embodiment focuses on describing the differences from other embodiments. For example, the device embodiment, equipment embodiment, and storage medium embodiment are all similar to the method embodiment, so the description is relatively simple. For reading the relevant content of the device embodiment, equipment embodiment, and storage medium embodiment, please refer to the description of the method embodiment.

[0094] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0095] In the 1930s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many improvements to the methodology today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that an improvement to the methodology cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program and "integrate" a digital system onto a PLD themselves, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must also be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0096] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0097] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0098] For ease of description, the above apparatus is described by dividing it into various functional units. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in one or more software and / or hardware.

[0099] Those skilled in the art will understand that one or more embodiments of this specification can be provided as a method, system, or computer program product. Therefore, one or more embodiments of this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0100] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0101] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0102] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable apparatus for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0103] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0104] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0105] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0106] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0107] One or more embodiments of this specification can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. One or more embodiments of this specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0108] The above description is merely an embodiment of this document and is not intended to limit the scope of this document. Various modifications and variations can be made to this document by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this document should be included within the scope of the claims of this document.

Claims

1. A method for processing electronic invoice inquiries, comprising: Search for invoices based on the invoice code entered in the query, and read the key information of the electronic invoices found in the query. Based on the key information of the invoice, query the invoice chain containing the invoice node corresponding to the electronic invoice; In the bill chain, query at least one target bill node associated with the bill node; The association between the bill node and the target bill node is established based on the buying and selling circulation relationship or the usage preparation relationship between the transaction objects recorded in the transaction vouchers mapped by the bill node and the associated bill node respectively. The electronic tickets corresponding to the at least one target ticket node obtained are used as the query input and the query output result.

2. The electronic invoice query and processing method according to claim 1, wherein the invoice nodes in the invoice chain are constructed in the following manner: Upon detecting a payment or receipt instruction from the transacting party for the transaction voucher, a node for configuring a bill is created in the bill chain; The transaction certificate obtained through the first data interface is associated with the bill node to be configured; After the electronic bill of the transaction certificate is generated, the bill node to be configured is initialized based on the bill information of the electronic bill of the transaction certificate, so as to obtain the bill node corresponding to the electronic bill of the transaction certificate.

3. The electronic invoice query and processing method according to claim 1, for any two invoice nodes in the invoice chain, performs the following operations: Extract the preparation information of the first transaction object recorded in the transaction certificate record mapped by the first bill node, and the preparation information of the second transaction object recorded in the transaction certificate record mapped by the second bill node; If a matching relationship is detected between the preparation information of the first transaction object and the preparation information of the second transaction object, then a certificate association relationship is established between the transaction certificates mapped by the two bill nodes.

4. The electronic invoice query processing method according to claim 1, for any two invoice nodes in the invoice chain, performs the following operations: Check whether the transaction object of the electronic transaction contract record mapped by the first bill node is the same as the transaction object of the electronic transaction contract record mapped by the second bill node; If so, detect whether there is a contractual dependency relationship between the electronic transaction contract mapped by the first bill node and the electronic transaction contract mapped by the second bill node. If so, establish a certificate association relationship between the transaction certificates of the two bill nodes.

5. The electronic bill inquiry and processing method according to claim 1, wherein the buying and selling circulation relationship includes a buying circulation relationship and a selling circulation relationship; and the usage preparation relationship includes a preparation input relationship and a preparation output relationship.

6. The electronic invoice query processing method according to claim 5, wherein querying at least one target invoice node associated with the invoice node in the invoice chain comprises: The transaction object mapped to the transaction certificate record of the candidate bill node in the bill chain is used as the candidate transaction object; The candidate transaction objects are detected to have a buying and selling relationship and / or a use preparation relationship with the transaction certificate records mapped to the bill node. The candidate bill node corresponding to the transaction certificate of the detected candidate transaction object is taken as the target bill node.

7. The electronic bill query processing method according to claim 1, wherein querying at least one target bill node associated with the bill node in the bill chain includes: The candidate bill nodes in the bill chain that have a contractual dependency relationship with the candidate electronic transaction contracts mapped to the candidate bill nodes are selected as the target bill nodes.

8. In the electronic bill query processing method according to claim 1, at least one identical transacting party is recorded in at least one bill subject field of the electronic bill corresponding to the bill node of the bill chain.

9. The electronic bill query and processing method according to claim 1, wherein the bill chain further includes bill jump nodes of the transaction participants of the transaction vouchers mapped by each bill node; If a redirect query command is detected for the redirect node, the system will redirect to the bill chain of the transaction participant to which the redirect node belongs. Extract the associated transaction vouchers of the corresponding bill nodes in the bill chain of the transaction participants as the query output of the query input.

10. The electronic invoice query processing method according to claim 1, wherein the invoice code is input by an auditing institution or a tax authority through a query interface.

11. An electronic invoice query and processing device, comprising: The invoice key information reading module is configured to perform invoice queries based on the invoice code entered in the query, and read the key information of the queried electronic invoices; The bill chain query module is configured to query the bill chain containing the bill nodes corresponding to the electronic bill based on the key information of the bill; The target bill node query module is configured to query at least one target bill node associated with the bill node in the bill chain; The association between the bill node and the target bill node is established based on the buying and selling circulation relationship or the usage preparation relationship between the transaction objects recorded in the transaction vouchers mapped by the bill node and the associated bill node respectively. The query result output module is configured to use the electronic tickets corresponding to the at least one target ticket node as the query input as the query output result.

12. An electronic invoice query and processing device, comprising: processor; And, a memory configured to store computer-executable instructions, which, when executed, cause the processor to: Search for invoices based on the invoice code entered in the query, and read the key information of the electronic invoices found in the query. Based on the key information of the invoice, query the invoice chain containing the invoice node corresponding to the electronic invoice; In the bill chain, query at least one target bill node associated with the bill node; The association between the bill node and the target bill node is established based on the buying and selling circulation relationship or the usage preparation relationship between the transaction objects recorded in the transaction vouchers mapped by the bill node and the associated bill node respectively. The electronic tickets corresponding to the at least one target ticket node obtained are used as the query input and the query output result.

13. A storage medium for storing computer-executable instructions, which, when executed by a processor, perform the following process: Search for invoices based on the invoice code entered in the query, and read the key information of the electronic invoices found in the query. Based on the key information of the invoice, query the invoice chain containing the invoice node corresponding to the electronic invoice; In the bill chain, query at least one target bill node associated with the bill node; The association between the bill node and the target bill node is established based on the buying and selling circulation relationship or the usage preparation relationship between the transaction objects recorded in the transaction vouchers mapped by the bill node and the associated bill node respectively. The electronic tickets corresponding to the at least one target ticket node obtained are used as the query input and the query output result.

Images