CN110599267B

CN110599267B - Electronic invoice issuing method and device, computer readable storage medium and computer equipment

Info

Publication number: CN110599267B
Application number: CN201910871790.3A
Authority: CN
Inventors: 郑罗海; 张建俊; 秦青; 戴传兵; 陈湖佳; 农高明; 陈金龙; 蔡弋戈
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2019-09-16
Filing date: 2019-09-16
Publication date: 2024-06-25
Anticipated expiration: 2039-09-16
Also published as: CN110599267A

Abstract

The application relates to an electronic invoice billing method, an electronic invoice billing device, a computer readable storage medium and computer equipment, wherein the method comprises the following steps: receiving an electronic invoice parallel invoicing request, wherein the electronic invoice parallel invoicing request carries a parallel invoicing number, and generating corresponding original invoices according to the parallel invoicing number; acquiring each invoice identifier corresponding to each original invoice from the existing issuable invoice identifier section, and acquiring each billing information corresponding to each invoice identifier; parallelly consensus each invoice identification and each corresponding billing information; when the parallel consensus of each invoice identification and each corresponding invoice information passes, generating an electronic invoice of the parallel invoice number according to each invoice identification and each corresponding invoice information, and writing the electronic invoice into the block. The scheme provided by the application greatly improves the billing performance of the block chain electronic invoice.

Description

Electronic invoice issuing method and device, computer readable storage medium and computer equipment

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method and apparatus for electronic invoice billing, a computer readable storage medium, and a computer device.

Background

In the traditional invoice business, invoice assets belong to tax bureaus, and an invoicing service provider needs to take invoices (including online taking and offline taking) from the tax bureaus to execute the invoicing capability. With the development of blockchain technology, electronic invoices are being invoiced using blockchains.

However, in the current use of blockchains for invoicing, the invoicing node needs to acquire an asset from the tax office node (the amount of the asset is determined by the tax office according to rules, for example, the invoicing node takes 100 invoices, one invoice is one asset)), and then the invoicing node can perform the invoicing operation. Because the blockchain is the asset transfer process during invoicing, namely a serial action, the invoicing performance of the blockchain electronic invoice is extremely low.

Disclosure of Invention

Based on the above, it is necessary to provide an electronic invoice issuing method, an electronic invoice issuing device, a computer readable storage medium and computer equipment aiming at the technical problem that the issuing performance of a blockchain electronic invoice is extremely low.

An electronic invoice billing method, comprising:

Receiving an electronic invoice parallel invoicing request, wherein the electronic invoice parallel invoicing request carries a parallel invoicing number, and generating corresponding original invoices according to the parallel invoicing number;

acquiring each invoice identifier corresponding to each original invoice from the existing issuable invoice identifier section, and acquiring each billing information corresponding to each invoice identifier;

Parallelly consensus each invoice identification and each corresponding billing information;

When the parallel consensus of each invoice identification and each corresponding invoice information passes, generating an electronic invoice of the parallel invoice number according to each invoice identification and each corresponding invoice information, and writing the electronic invoice into the block.

An electronic invoice billing device, comprising:

the original invoice generation module is used for receiving an electronic invoice parallel invoicing request, wherein the electronic invoice parallel invoicing request carries the parallel invoicing number, and each corresponding original invoice is generated according to the parallel invoicing number;

The information acquisition module is used for acquiring each invoice identifier corresponding to each original invoice from the existing issueable invoice identifier section and acquiring each billing information corresponding to each invoice identifier;

the parallel consensus module is used for parallelly consensus each invoice identifier and each corresponding invoice information;

And the invoice writing module is used for generating an electronic invoice of parallel billing number according to each invoice identifier and each corresponding billing information when the parallel consensus of each invoice identifier and each corresponding billing information passes, and writing the electronic invoice into the block.

A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the program:

A computer readable storage medium having stored thereon a computer program which, when executed by a processor, causes the processor to perform the steps of:

According to the electronic invoice billing method, the electronic invoice billing device, the computer readable storage medium and the computer equipment, the block chain node independently generates each original invoice of the parallel billing number, acquires each invoice identification and each billing information corresponding to each original invoice, and parallelly consensus each invoice identification and each corresponding billing information; when the parallel consensus of each invoice identification and the corresponding billing information passes, generating an electronic invoice of parallel billing number according to each invoice identification and each billing information, and writing the electronic invoice into a block, so that a block chain node can bill the electronic invoice in parallel in a block chain, the constraint of atomic operation is eliminated, and the billing performance of the block chain electronic invoice is improved.

Drawings

FIG. 1 is an application environment diagram of an electronic invoice method in one embodiment;

FIG. 2 is a flow diagram of a method of electronic invoice in one embodiment;

FIG. 3 is a flow diagram of generating a issuable invoice identification section in one embodiment;

FIG. 4 is a flow diagram of sharing respective invoice identifications and corresponding respective billing information in one embodiment;

FIG. 5 is a flow chart illustrating the sharing of the successful results of each match in one embodiment;

FIG. 6 is a flow diagram of matching recipient identifications in one embodiment;

FIG. 7 is a schematic diagram of a flow of prohibiting invoicing of an invoicing node in an embodiment

FIG. 8 is a schematic diagram of a conventional electronic invoice flow in one embodiment;

FIG. 9 is a schematic diagram of an electronic invoice flow in accordance with one embodiment of the present application;

FIG. 10 is a block diagram of an electronic invoice means in one embodiment;

FIG. 11 is a block diagram of a computer device in one embodiment.

Detailed Description

The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.

FIG. 1 is a diagram of an application environment for a method of electronic invoice invoicing in one embodiment. Referring to fig. 1, the electronic invoice issuing method is applied to an electronic invoice issuing system. The electronic invoice billing system includes a terminal 102, a server 104, blockchain nodes 106 in the blockchain, and other blockchain nodes. The terminal 102 and the blockchain node 106 are connected by a network, and the server 104 and the blockchain node 106 are connected by a network. The terminal 102 may be a desktop terminal or a mobile terminal, and the mobile terminal may be at least one of a mobile phone, a tablet computer, a notebook computer, and the like. The blockchain node 106 may be implemented as a stand-alone server or as a cluster of servers. The server 104 may be implemented as a stand-alone server or as a server cluster including a plurality of servers.

Specifically, the blockchain node 106 receives an electronic invoice parallel billing request sent by the terminal 102 or the server 104, where the electronic invoice parallel billing request carries a parallel billing number, and generates each corresponding original invoice according to the parallel billing number. The blockchain node 106 obtains each invoice identifier corresponding to each original invoice from the existing issuable invoice identifier section, and obtains each billing information corresponding to each invoice identifier. The blockchain node 106 concurrently shares each invoice identification with corresponding each billing information. When the parallel consensus of each invoice identification and corresponding each billing information passes, the blockchain node 106 generates an electronic invoice of the parallel billing number according to each invoice identification and corresponding each billing information, and writes the electronic invoice into the block.

As shown in FIG. 2, in one embodiment, an electronic invoice method is provided. The present embodiment is mainly exemplified by the application of the method to the blockchain node in fig. 1. Referring to fig. 2, the electronic invoice issuing method specifically includes the following steps:

S202, receiving an electronic invoice parallel invoicing request, wherein the electronic invoice parallel invoicing request carries the parallel invoicing number, and generating corresponding original invoices according to the parallel invoicing number.

The blockchain refers to a serial transaction record which is connected in series by means of cryptography and guarantees non-falsifiability and non-falsifiability, and the effective transaction record of the distributed storage characteristic enables the serial connection of the distributed account book node based on a formula algorithm and an encryption algorithm, so that a novel architecture mode of the capability of permanent checking is provided. The parallel invoicing number refers to the number of electronic invoices that need to be issued in parallel. The number may be any number. The original invoice refers to an original blank invoice, and the blank invoice has no invoice identification and specific invoice information. The invoice identification is used for uniquely identifying the invoice, can be a character string, a number and the like, and consists of a fixed invoice code and an invoice number. The billing information refers to information required for billing an electronic invoice, such as a receiver identification, a billing amount, and the like.

Specifically, the block chain link point receives an electronic invoice parallel invoicing request, wherein the electronic invoice parallel invoicing request carries the parallel invoicing number, and each corresponding original invoice is generated according to the parallel invoicing number. I.e., the blockchain node can issue assets itself, and the number of issued assets is controlled by the blockchain node itself. .

In one embodiment, the blockchain node is a vendor server when the vendor server has access to the blockchain. For example, the seller may be an enterprise and the enterprise server may be accessed into the blockchain. At this time, the block chain node of the enterprise server receives an electronic invoice parallel invoicing request sent by the terminal, the electronic invoice parallel invoicing request carries the parallel invoicing number, and each corresponding original invoice is generated according to the parallel invoicing number.

In one embodiment, when the seller cannot access the blockchain, the seller can authorize the proxy platform to make an invoice, and the blockchain node is the proxy platform server. For example, the seller may be a computer in a convenience store, a server in a small and medium-sized enterprise, or the like, and cannot access the blockchain. At this time, an electronic invoice needs to be issued by using the proxy platform server. The proxy platform server may be a server that proxies electronic invoice invoices, such as a micro-letter server, a payment treasury server, or the like. The seller registers account numbers in the tax office platform in advance, uses account numbers and passwords to log in the tax office platform, selects a proxy platform for issuing electronic invoices, and establishes a corresponding relation between the proxy platform and the seller when the tax office platform server receives a proxy request of the seller, so that the proxy platform server can replace the seller to issue electronic invoices. At this time, the proxy server blockchain node receives an electronic invoice parallel invoicing request sent by the middle and small enterprise server, the electronic invoice parallel invoicing request carries a parallel invoicing number, and the proxy server blockchain node generates corresponding original invoices according to the parallel invoicing number.

S204, each invoice identification corresponding to each original invoice is obtained from the existing issuable invoice identification section, and each billing information corresponding to each invoice identification is obtained.

Wherein, the existing issuable invoice identification section refers to an invoice identification section which generates an issuable original invoice in advance according to the intelligent contract. The issuable invoice identification section may be periodically generated according to a smart contract and stored in a blockchain node local cache. For example, existing issuable invoice identification sections are invoice identifications between 0000 and 1000.

Specifically, the blockchain node obtains each invoice identification corresponding to each original invoice from the existing issuable invoice identification section, wherein each invoice identification cannot be repeated and is unused. And acquiring each billing information corresponding to each invoice identifier. And obtaining invoice identification and billing information corresponding to each original invoice.

In one embodiment, each invoice identification in the issuable invoice identification section is marked as used when the corresponding electronic invoice is generated.

S206, parallelly consensus each invoice identification and each corresponding invoice information.

The consensus refers to a consensus mechanism in a blockchain, and the consensus mechanism is verification and confirmation of a transaction in a short time through voting of special nodes. In the application, the parallel verification and the parallel confirmation of each invoice identification and each invoice information are performed.

Specifically, the blockchain node simultaneously carries out parallel consensus on invoice identifications of the parallel invoices and blockchains transmitted by corresponding invoicing information to obtain a consensus result of each invoice identification and corresponding invoicing information.

And S208, when the parallel consensus of each invoice identification and each corresponding invoice information passes, generating an electronic invoice of the parallel invoice number according to each invoice identification and each corresponding invoice information, and writing the electronic invoice into the block.

Specifically, when the parallel consensus of each invoice identification and each corresponding invoice information passes, generating an electronic invoice of the parallel invoice number according to each invoice identification and each corresponding invoice information, and writing the electronic invoice into the block.

In the electronic invoice invoicing method, the blockchain node autonomously generates each original invoice of the parallel invoicing number, acquires each invoice identification and each invoicing information corresponding to each original invoice, and parallelly and commonly recognizes each invoice identification and each corresponding invoicing information; when the parallel consensus of each invoice identification and the corresponding billing information passes, generating an electronic invoice of parallel billing number according to each invoice identification and each billing information, and writing the electronic invoice into a block, so that a block chain node can bill the electronic invoice in parallel in a block chain, the constraint of atomic operation is eliminated, and the billing performance of the block chain electronic invoice is improved.

In one embodiment, as shown in fig. 3, before step S202, that is, before receiving an electronic invoice parallel issue request, the electronic invoice parallel issue request carries a parallel issue number, and before generating each corresponding original invoice according to the parallel issue number, the method further includes the steps of:

S302, receiving an original invoice acquisition request, wherein the original invoice acquisition request carries an invoicing node identifier, and calling an issuing asset intelligent contract according to the original invoice acquisition request.

S304, the intelligent contract of the issuing asset generates an issuable invoice identification section according to the invoicing node identification, and the issuable invoice identification section is stored.

The invoicing node identifier is used for identifying the node needing to issue the electronic invoice. The server of the node can be a blockchain node or a common server. The issuing asset intelligence contract is used for controlling invoice identifications available to the invoicing nodes corresponding to the invoicing node identifications.

Specifically, the block link point receives an original invoice acquisition request, the original invoice acquisition request carries an invoicing node identifier, an issuing asset intelligent contract is called according to the original invoice acquisition request, the issuing asset intelligent contract generates an issuable invoice identifier section according to the invoicing node identifier, namely, an original invoice is generated, and the issuable invoice identifier section is stored. The original invoice refers to a blank invoice in which invoice specific information is not written.

In one embodiment, the issuing asset intelligent contract can be called regularly, the generated issuable invoice identification section is stored in a local cache, and the issuable invoice identification section can be directly obtained from the local cache when in use, so that the efficiency is improved.

In the embodiment, the issuable invoice identification section is generated by calling the intelligent contract of the issuing asset, and the issuable invoice identification section is stored, namely, the issuing node is controlled to issue the invoice identification of the electronic invoice, so that the issuing node is prevented from issuing an invoice at will.

In one embodiment, as shown in fig. 4, step S204, that is, the concurrent consensus of each invoice identification and each billing information, includes the steps of:

S402, broadcasting each invoice identification and corresponding each billing information to other blockchain nodes in parallel.

Specifically, the block chain link simultaneously broadcasts each invoice identifier and corresponding each invoice information to other block chain nodes, namely, simultaneously broadcasts the electronic invoices of the parallel invoices to other block chain nodes for common identification verification. Equivalent to concurrent consensus verification of multiple transactions.

S404, receiving a common passing broadcast returned by other block chain nodes, wherein the common passing refers to confirmation of each invoice identifier and corresponding each billing information by the other block chain nodes.

Specifically, the blockchain node receives a consensus passing broadcast returned by other blockchain nodes, wherein the consensus passing refers to verification and confirmation of each invoice identifier and corresponding each billing information by the other blockchain nodes. That is, after receiving the consensus broadcast of each invoice identifier and each corresponding invoice information, the other block chain nodes broadcast the verification and confirmation passing information to the block chain after the verification and confirmation passing information is passed, so that the block chain nodes receive the consensus passing broadcast returned by the other block chain nodes.

S406, calculating the number of block chain nodes for confirming each invoice identifier and each corresponding invoice information, and obtaining a parallel consensus passing result when the number of block chain link points meets the consensus condition.

The consensus condition is that a preset number of block chain link points in the block chain full network node pass through consensus.

Specifically, the block chain link points calculate the number of block chain nodes confirmed for each invoice identifier and each corresponding invoice information, and when the number of block chain link points meets the consensus condition, namely when the number of block chain link points passing through each invoice identifier and each corresponding invoice information meet the consensus condition, a parallel consensus passing result for each invoice identifier and each corresponding invoice information is obtained.

In the above embodiment, by broadcasting each invoice identifier and corresponding each billing information to other blockchain nodes in parallel, receiving a consensus passing broadcast returned by other blockchain nodes, calculating the number of blockchain nodes for confirming each invoice identifier and corresponding each billing information, and obtaining a parallel consensus passing result when the number of blockchain nodes meets a consensus condition. The constraint that the prior blockchain can only realize serial consensus when consensus is realized on the transaction is eliminated (after the completion of the consensus of one transaction, the next transaction can be realized). The block chain is enabled to realize parallel consensus on each invoice identification and each corresponding invoice information, so that the invoice performance of the block chain electronic invoice is greatly improved.

In one embodiment, as shown in fig. 5, step S204, which is to parallelly consensus each invoice identification and corresponding each billing information, includes the steps of:

S502, calling an invoicing intelligent contract, determining invoicing conditions according to the invoice identifications, and matching the invoicing conditions with the invoicing information.

Wherein the invoicing intelligence contract is used to control uncontrolled invoicing of blockchain nodes. The invoicing condition refers to a condition capable of issuing an electronic invoice, and may include whether the invoicing party is a corresponding proxy service provider, whether the invoicing amount exceeds a maximum amount, whether the invoicing receiver is a receivable party, whether the invoicing party is not an belief-losing party, and the like.

Specifically, the blockchain node invokes an invoicing intelligent contract, the invoicing intelligent contract obtains corresponding invoicing node identifiers according to the invoice identifiers, determines corresponding invoicing conditions according to the invoicing node identifiers, and matches the invoicing conditions with the invoicing information. For example, the agent service providers in the billing conditions are matched with the agent service providers in the billing information, whether the agent service providers are consistent is judged, and when the agent service providers are consistent, the agent service providers in the billing information are the agent service providers corresponding to the billing node identifiers. The receiver identification in the invoicing condition can be matched with the receiver identification in the invoicing information, whether the receiver identification is consistent or not is judged, and when the receiver identification is consistent, the receiver identification for invoicing is the receiver identification of the electronic invoice. And the billing node identification which is not in confidence loss in the billing condition is matched with the billing node identification in the billing information, so that whether the billing node identification is consistent is judged, and when the billing node identification is consistent, the billing node corresponding to the billing node identification is not a confidence loss party.

And S504, when each billing information is successfully matched with the billing conditions, each successful matching result is obtained, and each successful matching result is identified together.

S506, determining the number of block chain nodes through which the corresponding consensus of each successful matching result passes, and obtaining the consensus passing result when the number of block chain link points meets the consensus condition.

Specifically, when each billing information is successfully matched with the billing conditions, each successful matching result is obtained, namely each billing information has a corresponding matching result. Broadcasting each successful matching result to the block chain full network node, and carrying out consensus through a consensus algorithm. Among them, consensus algorithms include PoW (workload certification algorithm), poS (rights certification algorithm), PBFT (practical bayer fault tolerance algorithm), and so on. And then when receiving the passing of the consensus confirmation broadcast by other block chain nodes, determining the number of the block chain nodes which pass through the consensus corresponding to each successful matching result, and when the number of the block chain nodes meets the consensus condition, obtaining the consensus passing result.

In one embodiment, when the billing information fails to match with the billing conditions, a matching failure result is obtained, a corresponding billing identifier is obtained according to the billing information which fails to match, and the matching failure result, the billing information and the corresponding billing identifier are returned to the billing party.

In the above embodiment, the billing condition is determined according to each invoice identifier by calling the billing intelligent contract, the billing condition is matched with each billing information, and when each billing information is successfully matched with the billing condition, each matching success result is commonly identified, so as to obtain a commonly-identified passing result, namely, the billing of the blockchain node is controlled through the billing intelligent contract, so that the billing behavior of the blockchain node can be controlled, and abnormal billing of the blockchain node is prevented.

In one embodiment, as shown in fig. 6, step S402, that is, invoking an invoicing intelligent contract, where the invoicing intelligent contract determines an invoicing condition according to each invoice identifier, and matches the invoicing condition with each invoicing information, includes:

S602, the intelligent invoicing contract determines an invoicing node identifier according to each invoice identifier, and determines each receiver identifier capable of invoicing according to the invoicing node identifier.

Wherein the recipient identification is used to identify the recipient of the electronic invoice. The recipient is a consumer. May be an individual, business, etc.

Specifically, the intelligent invoicing contract can obtain an issuable invoice identification section where the invoice identification is located according to the invoice identification, determine an invoicing node identification according to the discoverable invoice identification section, and find corresponding receiver identifications capable of invoicing from invoicing conditions according to the invoicing node identification.

S604, determining each target receiver identification from each billing information, and matching each target receiver identification with each receiver identification capable of billing.

S606, when the identification of each receiving party capable of making an invoice is consistent with the identification of each target receiving party, a successful matching result is obtained.

The target receiver identifier is used for identifying a receiver of the electronic invoice in the billing information, and can be a name, a character string, a number and the like. The recipient is a consumer, which may be a person, business, or the like.

Specifically, the blockchain node determines the identification of each target receiver from each billing information, and then obtains the identification of the receiver to be billed in each billing information. And matching each target receiver identifier with each receiver identifier which can be invoiced in the invoicing conditions. When the target receiver identifications are consistent with the receiver identifications capable of making an invoice, the fact that the target receiver identifications exist in the receiver identifications capable of making an invoice is indicated, and at the moment, a successful matching result is obtained.

In the above embodiment, by matching each target receiver identifier in each billing information with each receiver identifier that can be billed, when each target receiving identifier exists in each receiver identifier that can be billed, a successful matching result is obtained, and the blockchain node can be controlled to bill to the receiver corresponding to each receiver identifier that can be billed.

In one embodiment, as shown in fig. 7, the electronic invoice issuing method further includes:

S702, when the invoice identification and the billing information are in parallel common pass, sending each invoice identification and each billing information to the tax office server so that the tax office server counts the electronic invoice information, and when the electronic invoice information triggers a preset early warning rule, sending a request for prohibiting billing to the block chain link, wherein the billing request carries the billing node identification.

The electronic invoice information refers to information obtained according to electronic invoices in a blockchain, and for example, the electronic invoice information can include the number of electronic invoices issued by an issuing node corresponding to the issuing node identifier in a period of time. And the method can further comprise the step of identifying the corresponding billing node billing total amount in a period of time. It may also be that the number and name of the recipient identifications are included in the electronic invoice over a period of time. The preset early warning rule refers to an early warning rule of presetting an electronic invoice billing risk, and the early warning rule can be that the number of electronic invoices which are billed by billing nodes corresponding to the billing node identification exceeds a preset number in a period of time, the total amount of the invoices which are billed by the billing nodes exceeds a preset early warning value in a period of time, the number and the name of the receiver identification in the electronic invoice are abnormal in a period of time, and the like.

Specifically, when the consensus of each invoice identification and corresponding each billing information is passed, the block link point sends each invoice identification and each billing information to the tax office server, namely, each time after the consensus is successful, the electronic invoice is sent to the tax office server. The tax office server can obtain the electronic invoice sent by each billing node, count the electronic invoice information corresponding to each billing node, and send a request for prohibiting billing to the block chain link when the electronic invoice information of the billing node triggers a preset early warning rule, wherein the request for billing carries the identification of the billing node.

S704, receiving an invoicing prohibition request sent by the tax office server, calling an invoicing prohibition intelligent contract according to the invoicing prohibition request, and prohibiting the corresponding invoicing node from invoicing according to the invoicing node identification.

The intelligent contract for prohibiting the invoicing is used for limiting the invoicing node corresponding to the invoicing node identifier to issue the asset and issuing the electronic invoice.

Specifically, the block chain link point receives an invoice prohibition request sent by the tax office server, calls an invoice prohibition intelligent contract according to the invoice prohibition request, and prohibits the corresponding invoice node from issuing assets and performing electronic invoice invoicing according to the invoice node identification.

In one embodiment, an early warning monitoring system is arranged in a tax office server, a blockchain consensus node is monitored in real time, when the consensus node passes through each consensus, the tax office server synchronizes electronic invoices, then counts electronic invoice information of each invoicing node according to the synchronized electronic invoices, when a statistics result triggers an early warning rule, sends an invoicing prohibition request to a blockchain link point, the blockchain link point receives the invoicing prohibition request sent by the tax office server, calls an invoicing prohibition intelligent contract according to the invoicing prohibition request, and the invoicing prohibition intelligent contract prohibits the corresponding invoicing node from invoicing the electronic invoices according to the invoicing node identification.

In the embodiment, the rule making and controlling capability of the block chain electronic invoice system can be obtained by the tax office server through the early warning system and the intelligent contract, so that the supervision capability of the tax office server on the electronic invoice is improved, and any invoicing of an invoicing node is prevented.

In one embodiment, before receiving the electronic invoice parallel invoicing request, the electronic invoice parallel invoicing request carries the parallel invoicing number, and each corresponding original invoice is generated according to the parallel invoicing number, the method further comprises:

Receiving an intelligent contract deployment request, wherein the intelligent contract deployment request carries an invoicing intelligent contract, an asset intelligent contract and an invoicing prohibition intelligent contract, and deploying the invoicing intelligent contract, the asset intelligent contract and the invoicing restriction intelligent contract into a blockchain according to the intelligent contract deployment request.

Where a smart contract is a collection of pieces of code and data, it may be deployed to run on a blockchain network. The smart contract is interpreted by the virtual machine into bytecode for execution.

Specifically, the block chain link point receives an intelligent contract deployment request sent by the tax office server, wherein the intelligent contract deployment request carries an invoicing intelligent contract, an issuing asset intelligent contract and an invoicing prohibition intelligent contract, and compiles corresponding intelligent contract codes into virtual machine byte codes according to the intelligent contract deployment request, the issuing asset intelligent contract and the invoicing restriction intelligent contract call compiler, then sends the virtual machine byte codes to the block chain network through an interface, and writes the virtual machine byte codes into the block chain block after verification of the block chain network. At this point, the invoicing smart contracts, the issuing asset smart contracts, and the invoicing constraint smart contracts are deployed into the blockchain. The corresponding generated smart contract address may then be used to invoke the corresponding smart contract.

In the embodiment, the intelligent contracts for making an invoice, the intelligent contracts for issuing assets and the intelligent contracts for prohibiting making an invoice are obtained in advance, and the intelligent contracts are deployed into the blockchain, so that the intelligent contracts can be directly called from the blockchain in use, the efficiency is improved, and the intelligent contracts are convenient to use.

In one particular embodiment, in a traditional invoice service, the invoice asset belongs to a tax bureau, and the billing service needs to take an invoice (including on-line and off-line) to the tax bureau in order to perform the billing capability. Based on this background, the blockchain electronic invoice gets the electronic invoice circulation process as shown in fig. 8. In fig. 8, when an invoicing enterprise makes an invoice, an asset needs to be first taken from the tax office (the amount of the asset is determined by the tax office according to rules, for example, 100 invoices are taken, and one invoice is an asset). Then, the invoicing operation can be executed by the invoicing enterprises, 1 is reduced for every invoice asset, and the invoicing can not be performed any more after the invoice asset is reduced to 0, and the tax office is required to get the asset again. In the blockchain, the above-mentioned billing process has a great performance bottleneck, and since the decreasing number of assets of the billing enterprise needs to maintain the operation atomicity, the billing operation in the blockchain, i.e. asset transfer, is a serial action, resulting in extremely low billing performance of the blockchain electronic invoice.

And the present application is directed to mapping electronic invoices onto asset releases of blockchain technology. According to the characteristic of the blockchain, the asset issuing can get rid of the constraint of the atomic operation, so that an invoicing enterprise can execute the invoicing operation concurrently, and the invoicing performance of the electronic invoice is greatly improved. As shown in FIG. 9, in the embodiment of the application, the electronic invoice flow schematic diagram is that the issuing enterprise can issue the assets autonomously, so that the flow of the issuing enterprise to get the invoice assets from the tax office is simplified. The method specifically comprises the following steps:

The tax office server makes an invoicing intelligent contract, issues an asset intelligent contract and prohibits the invoicing intelligent contract, sends the made invoicing intelligent contract, the issued asset intelligent contract and the prohibited invoicing intelligent contract to the blockchain node, and deploys the invoicing intelligent contract, the issued asset intelligent contract and the prohibited invoicing intelligent contract to the blockchain node.

The invoicing enterprise node is a blockchain node, and periodically invokes the issuing asset intelligent contract to generate an issueable invoice identification section and store the issueable invoice identification section in a local cache. And the issuing enterprise receives an electronic invoice asset issuing request, wherein the electronic invoice asset issuing request carries an asset issuing number, generates corresponding original invoices according to the parallel issuing number, acquires invoice identifications corresponding to the original invoices from the existing issueable invoice identification section, and acquires the issuing information corresponding to the invoice identifications. And carrying out parallel consensus on each invoice identification and each corresponding invoice information, namely calling an invoice intelligent contract by each invoice enterprise node, determining an invoice condition according to each invoice identification, matching the invoice condition with each invoice information, obtaining a successful matching result when each invoice information is successfully matched with the invoice condition, carrying out consensus on the successful matching result, each invoice identification and each corresponding invoice information, determining the number of block chain nodes passing through the consensus, obtaining a consensus passing result when the number of block chain links meets the consensus condition, then generating an electronic invoice of the asset issuing number according to each invoice identification and each corresponding invoice information, and writing the electronic invoice into a block.

The consumer can search the corresponding electronic invoice from the blockchain, and reimburse the electronic invoice at the reimbursement enterprise blockchain link point. After the electronic invoice is reimbursed, the reimbursed enterprise blockchain node also sends the reimbursed electronic invoice to the tax bureau blockchain node for reimbursement, so that the circulation of the electronic invoice is completed.

It should be understood that, although the steps in the flowcharts of fig. 2-7 are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps of fig. 2-7 may include multiple sub-steps or stages that are not necessarily performed at the same time, but may be performed at different times, nor does the order in which the sub-steps or stages are performed necessarily occur in sequence, but may be performed alternately or alternately with at least a portion of other steps or sub-steps or stages of other steps.

In one embodiment, as shown in FIG. 10, there is provided an electronic invoice billing apparatus 1000, comprising:

the original invoice generation module 1002 is configured to receive an electronic invoice parallel billing request, where the electronic invoice parallel billing request carries a parallel billing number, and generate corresponding original invoices according to the parallel billing number;

the information obtaining module 1004 is configured to obtain each invoice identifier corresponding to each original invoice from the existing issuable invoice identifier section, and obtain each billing information corresponding to each invoice identifier;

a parallel consensus module 1006, configured to parallelly consensus each invoice identifier and corresponding each billing information;

And the invoice writing module 1008 is configured to generate an electronic invoice of a parallel billing number according to each invoice identifier and each corresponding billing information when the parallel consensus of each invoice identifier and each corresponding billing information passes, and write the electronic invoice into the block.

In one embodiment, the electronic invoice billing apparatus 1000 further includes:

The contract calling module is used for receiving an original invoice acquisition request, wherein the original invoice acquisition request carries an invoicing node identifier, and calling an intelligent contract for issuing assets according to the original invoice acquisition request;

And the section generating module is used for generating a issueable invoice identification section according to the invoicing node identification by the issuing asset intelligent contract and storing the issueable invoice identification section.

In one embodiment, the parallel consensus module 1006 is further configured to broadcast each invoice identification and corresponding each billing information to other blockchain nodes in parallel; receiving a consensus passing broadcast returned by other block chain nodes, wherein the consensus passing refers to confirmation of each invoice identifier and corresponding each billing information by the other block chain nodes; and calculating the number of block chain nodes for confirming each invoice identifier and each corresponding invoice information, and obtaining a parallel consensus passing result when the number of block chain nodes meets the consensus condition.

In one embodiment, the parallel consensus module 1006 is further configured to invoke an invoicing intelligent contract, and the invoicing intelligent contract determines an invoicing condition according to each invoice identifier, and matches the invoicing condition with each invoicing information; when each billing information is successfully matched with billing conditions, each successful matching result is obtained, and each successful matching result is identified; and determining the number of block chain nodes through which the matching success results correspond to the consensus, and obtaining the consensus passing result of each matching success result when the number of block chain link points meets the consensus condition.

In one embodiment, the parallel consensus module 1006 is further configured to determine an invoicing node identifier according to each invoice identifier, and determine each receiver identifier that can be invoiced according to the invoicing node identifier; determining the identification of each target receiver from each billing information, and matching the identification of each target receiver with the identification of each receiver capable of billing; and when the identification of each receiving party capable of making an invoice is consistent with the identification of each target receiving party, obtaining a successful matching result.

The information sending module is used for sending each invoice identifier and each corresponding invoice information to the tax office server when the parallel consensus of each invoice identifier and each corresponding invoice information passes, so that the tax office server counts the electronic invoice information, and sending an invoice forbidden request to the block chain link point when the electronic invoice information triggers a preset early warning rule, wherein the invoice forbidden request carries an invoice node identifier;

the billing prohibition module is used for receiving the billing prohibition request sent by the tax office server, calling the billing prohibition intelligent contract according to the billing prohibition request, and prohibiting the corresponding billing node from billing according to the billing node identification.

the contract deployment module is used for receiving an intelligent contract deployment request, wherein the intelligent contract deployment request carries an invoicing intelligent contract, an asset intelligent contract is issued and an invoicing intelligent contract is forbidden, and the invoicing intelligent contract, the asset intelligent contract is issued and the invoicing constraint intelligent contract is deployed into the blockchain according to the intelligent contract deployment request.

FIG. 11 illustrates an internal block diagram of a computer device in one embodiment. The computer device may specifically be the blockchain node 106 in fig. 1. As shown in fig. 11, the computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a method of electronic invoice invoicing.

It will be appreciated by those skilled in the art that the structure shown in FIG. 11 is merely a block diagram of some of the structures associated with the present inventive arrangements and is not limiting of the computer device to which the present inventive arrangements may be applied, and that a particular computer device may include more or fewer components than shown, or may combine some of the components, or have a different arrangement of components.

In one embodiment, the electronic invoice means provided by the present application may be implemented in the form of a computer program, which may be run on a computer device as shown in fig. 11. The memory of the computer device may store various program modules that make up the electronic invoice means, such as the original invoice generation module 1002, the information acquisition module 1004, the parallel consensus module 1006, and the invoice writing module 1008 shown in fig. 10. The computer program of each program module causes the processor to carry out the steps in the electronic invoice method of each embodiment of the application described in the specification.

For example, the computer apparatus shown in fig. 11 may perform step S202 through the original invoice generation module 1002 in the electronic invoice arrangement as shown in fig. 10. The computer device may perform step S204 through the information acquisition module 1004. The computer device may perform step S206 through the parallel consensus module 1006. The computer device may perform step S208 via invoice write module 1008.

In one embodiment, a computer device is provided that includes a memory and a processor, the memory storing a computer program that, when executed by the processor, causes the processor to perform the steps of the electronic invoice method described above. The steps of the electronic invoice issuing method herein may be the steps of the electronic invoice issuing method of each embodiment described above.

In one embodiment, a computer readable storage medium is provided, storing a computer program which, when executed by a processor, causes the processor to perform the steps of the electronic invoice method described above. The steps of the electronic invoice issuing method herein may be the steps of the electronic invoice issuing method of each embodiment described above.

Those skilled in the art will appreciate that all or part of the processes in the methods of the above embodiments may be implemented by a computer program for instructing relevant hardware, where the program may be stored in a non-volatile computer readable storage medium, and where the program, when executed, may include processes in the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in embodiments provided herein may include non-volatile and/or volatile memory. The nonvolatile memory can include Read Only Memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (SYNCHLINK) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), among others.

The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.

The foregoing examples illustrate only a few embodiments of the application and are described in detail herein without thereby limiting the scope of the application. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of protection of the present application is to be determined by the appended claims.

Claims

1. An electronic invoice billing method, comprising:

receiving an electronic invoice asset issuing request, wherein the electronic invoice asset issuing request carries an asset issuing number, and generating corresponding original invoices according to the asset issuing number;

Acquiring each invoice identifier corresponding to each original invoice from an existing issuable invoice identifier section, and acquiring each invoicing information corresponding to each invoice identifier, wherein the issuable invoice identifier section is generated by regularly calling an issuing asset intelligent contract by an issuing enterprise node;

And parallelly consensus the invoice identifications and the corresponding invoice information, wherein the method comprises the following steps of: broadcasting the invoice identifications and the corresponding invoice information to other block chain nodes in parallel, and obtaining a parallel consensus passing result when the number of block chain link points confirmed for the invoice identifications and the corresponding invoice information meets a consensus condition;

when the invoice identification and the corresponding invoice information are commonly passed in parallel, generating an electronic invoice of the asset issuing number according to the invoice identification and the corresponding invoice information, and writing the electronic invoice into a block.

2. The method of claim 1, wherein prior to the receiving an electronic invoice parallel issue request, the electronic invoice parallel issue request carrying a parallel issue number, generating corresponding respective original invoices according to the parallel issue number, further comprising:

receiving an original invoice acquisition request, wherein the original invoice acquisition request carries an invoicing node identifier, and calling an intelligent contract for issuing assets according to the original invoice acquisition request;

and the issuing asset intelligent contract generates an issuable invoice identification section according to the invoicing node identification, and stores the issuable invoice identification section.

3. The method of claim 1, wherein the parallelly consensus of the respective invoice identifications and the corresponding respective invoice information comprises:

Broadcasting the invoice identifications and the corresponding invoice information to other block chain nodes in parallel;

receiving a common passing broadcast returned by the other blockchain nodes, wherein the common passing refers to confirmation of the other blockchain nodes on the invoice identifications and the corresponding invoice information;

And calculating the number of block chain nodes confirmed by the invoice identifications and the corresponding invoice information, and obtaining a parallel consensus passing result when the number of block chain link points meets a consensus condition.

4. The method of claim 1, wherein the parallelly consensus of the respective invoice identifications and the corresponding respective invoice information comprises:

Calling an invoicing intelligent contract, wherein the invoicing intelligent contract determines invoicing conditions according to the invoice identifications, and matches the invoicing conditions with the invoicing information;

When the billing information is successfully matched with the billing conditions, obtaining each successful matching result, and consensus the successful matching results;

And determining the number of block chain nodes through which the matching success results correspond to the consensus, and obtaining the consensus passing result of the matching success results when the number of block chain link points meets the consensus condition.

5. The method of claim 4, wherein the invoking the invoicing intelligent contract, the invoicing intelligent contract determining an invoicing condition based on the respective invoice identification, matching the invoicing condition with the respective invoicing information, comprises:

The intelligent invoicing contract determines invoicing node identifiers according to the invoice identifiers and determines various receiver identifiers capable of invoicing according to the invoicing node identifiers;

Determining each target receiver identifier from the billing information, and matching each target receiver identifier with each receiver identifier capable of billing;

and when the identification of each receiver capable of making an invoice is consistent with the identification of each target receiver, obtaining a successful matching result.

6. The method according to claim 1, wherein the method further comprises:

When the invoice identifications and the corresponding invoice information are in parallel consensus, sending the invoice identifications and the invoice information to a tax office server so that the tax office server counts electronic invoice information, and when the electronic invoice information triggers a preset early warning rule, sending an invoice prohibition request to a block chain link point, wherein the invoice prohibition request carries an invoice node identification;

receiving an invoicing prohibition request sent by the tax office server, calling an invoicing prohibition intelligent contract according to the invoicing prohibition request, and prohibiting the corresponding invoicing node from invoicing according to the invoicing node identification.

7. The method of claim 1, wherein prior to the receiving an electronic invoice parallel issue request, the electronic invoice parallel issue request carrying a parallel issue number, generating corresponding respective original invoices according to the parallel issue number, further comprising:

Receiving an intelligent contract deployment request, wherein the intelligent contract deployment request carries an invoicing intelligent contract, an issuing asset intelligent contract and an invoicing prohibition intelligent contract, and deploying the invoicing intelligent contract, the issuing asset intelligent contract and the invoicing restriction intelligent contract into a blockchain according to the intelligent contract deployment request.

8. An electronic invoice billing device, the device comprising:

The system comprises an original invoice generation module, a processing module and a processing module, wherein the original invoice generation module is used for receiving an electronic invoice parallel invoicing request, the electronic invoice parallel invoicing request carries a parallel invoicing number, and each corresponding original invoice is generated according to the parallel invoicing number;

the information acquisition module is used for acquiring each invoice identifier corresponding to each original invoice from the existing issueable invoice identifier section and acquiring each invoicing information corresponding to each invoice identifier, wherein the issueable invoice identifier section is generated by regularly calling an issuing asset intelligent contract by an issuing enterprise node;

the parallel consensus module is used for parallelly consensus the invoice identifications and the corresponding invoice information, and comprises the following steps: broadcasting the invoice identifications and the corresponding invoice information to other block chain nodes in parallel, and obtaining a parallel consensus passing result when the number of block chain link points confirmed for the invoice identifications and the corresponding invoice information meets a consensus condition;

And the invoice writing module is used for generating the electronic invoice of the parallel billing number according to each invoice identifier and each corresponding billing information when the parallel consensus of each invoice identifier and each corresponding billing information passes, and writing the electronic invoice into a block.

9. The apparatus of claim 8, wherein the apparatus further comprises:

And the section generating module is used for generating a issueable invoice identification section according to the issuing asset intelligent contract and storing the issueable invoice identification section.

10. The apparatus of claim 8, wherein the parallel consensus module is further configured to broadcast the respective invoice identifications and the corresponding respective billing information in parallel to other blockchain nodes; receiving a common passing broadcast returned by the other blockchain nodes, wherein the common passing refers to confirmation of the other blockchain nodes on the invoice identifications and the corresponding invoice information; and calculating the number of block chain nodes confirmed by the invoice identifications and the corresponding invoice information, and obtaining a parallel consensus passing result when the number of block chain link points meets a consensus condition.

11. The apparatus of claim 8, wherein the parallel consensus module is further configured to invoke an invoicing intelligence contract that determines an invoicing condition based on the respective invoice identification, and matches the invoicing condition with the respective invoicing information; when the billing information is successfully matched with the billing conditions, obtaining each successful matching result, and consensus the successful matching results; and determining the number of block chain nodes through which the matching success results correspond to the consensus, and obtaining the consensus passing result of the matching success results when the number of block chain link points meets the consensus condition.

12. The apparatus of claim 11, wherein the parallel consensus module is further configured to determine an invoicing node identifier from the respective invoice identifier and determine a respective recipient identifier that is invocable from the invoicing node identifier; determining each target receiver identifier from the billing information, and matching each target receiver identifier with each receiver identifier capable of billing; and when the identification of each receiver capable of making an invoice is consistent with the identification of each target receiver, obtaining a successful matching result.

13. The apparatus of claim 8, wherein the apparatus further comprises:

The information sending module is used for sending the invoice identifications and the corresponding invoice information to a tax office server when the invoice identifications and the corresponding invoice information are parallelly and commonly recognized to pass, so that the tax office server counts the electronic invoice information, and sending an invoice prohibition request to a block chain link point when the electronic invoice information triggers a preset early warning rule, wherein the invoice prohibition request carries an invoice node identification;

and the billing prohibition module is used for receiving the billing prohibition request sent by the tax office server, calling a billing prohibition intelligent contract according to the billing prohibition request, and prohibiting the corresponding billing node from billing according to the billing prohibition node identification.

14. The apparatus of claim 8, wherein the apparatus further comprises:

The contract deployment module is used for receiving an intelligent contract deployment request, wherein the intelligent contract deployment request carries the invoicing intelligent contract, the issuing asset intelligent contract and the intelligent contract forbidden to issue, and deploys the invoicing intelligent contract, the issuing asset intelligent contract and the invoicing constraint intelligent contract into a blockchain according to the intelligent contract deployment request.

15. A computer readable storage medium storing a computer program which, when executed by a processor, causes the processor to perform the steps of the method of any one of claims 1 to 7.

16. A computer device comprising a memory and a processor, the memory storing a computer program that, when executed by the processor, causes the processor to perform the steps of the method of any of claims 1 to 7.