CN110599267A - Electronic invoice billing method and device, computer readable storage medium and computer equipment - Google Patents
Electronic invoice billing method and device, computer readable storage medium and computer equipment Download PDFInfo
- Publication number
- CN110599267A CN110599267A CN201910871790.3A CN201910871790A CN110599267A CN 110599267 A CN110599267 A CN 110599267A CN 201910871790 A CN201910871790 A CN 201910871790A CN 110599267 A CN110599267 A CN 110599267A
- Authority
- CN
- China
- Prior art keywords
- invoice
- invoicing
- parallel
- information
- electronic
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 53
- 238000004590 computer program Methods 0.000 claims description 12
- 238000012790 confirmation Methods 0.000 claims description 9
- 238000012545 processing Methods 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 13
- 230000008569 process Effects 0.000 description 8
- 238000012795 verification Methods 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 3
- 230000002829 reductive effect Effects 0.000 description 3
- 230000001360 synchronised effect Effects 0.000 description 3
- 230000002159 abnormal effect Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 2
- 230000000670 limiting effect Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- GOLXNESZZPUPJE-UHFFFAOYSA-N spiromesifen Chemical compound CC1=CC(C)=CC(C)=C1C(C(O1)=O)=C(OC(=O)CC(C)(C)C)C11CCCC1 GOLXNESZZPUPJE-UHFFFAOYSA-N 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000006399 behavior Effects 0.000 description 1
- 230000002401 inhibitory effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/04—Billing or invoicing
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 carrying parallel invoicing numbers, and generating corresponding original invoices according to the parallel invoicing numbers; acquiring each invoice identifier corresponding to each original invoice from an existing invoiceable invoice identifier section, and acquiring each invoicing information corresponding to each invoice identifier; identifying each invoice mark and each corresponding invoice information in parallel; and when the invoice identifications and the corresponding invoice information are subjected to parallel common identification, generating electronic invoices with parallel invoice numbers according to the invoice identifications and the corresponding invoice information, and writing the electronic invoices into the blocks. The scheme that this application provided has greatly promoted the performance of making out an invoice of block chain electronic invoice.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for issuing an electronic invoice, a computer-readable storage medium, and a computer device.
Background
In the traditional invoice business, invoice assets belong to a tax bureau, and invoicing service providers need to draw invoices (including online drawing and offline drawing) from the tax bureau to execute invoicing capacity. As blockchain technology has evolved, electronic invoicing of invoices using blockchains has begun.
However, in the current billing using the block chain, the billing node needs to acquire an asset from the tax bureau node (the amount of the asset is determined by the tax bureau according to the rules, for example, the billing node draws 100 invoices, and one invoice is an asset), and then the billing node can perform the billing operation. Since the blockchain is an 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 this, it is necessary to provide an electronic invoice billing method, an electronic invoice billing apparatus, a computer-readable storage medium, and a computer device for solving the technical problem that the billing performance of a blockchain electronic invoice is extremely low.
An electronic invoice billing method comprising:
receiving an electronic invoice parallel invoicing request carrying parallel invoicing numbers, and generating corresponding original invoices according to the parallel invoicing numbers;
acquiring each invoice identifier corresponding to each original invoice from an existing invoiceable invoice identifier section, and acquiring each invoicing information corresponding to each invoice identifier;
identifying each invoice mark and each corresponding invoice information in parallel;
and when the invoice identifications and the corresponding invoice information are subjected to parallel common identification, generating electronic invoices with parallel invoice numbers according to the invoice identifications and the corresponding invoice information, and writing the electronic invoices into the blocks.
An electronic invoice issuing apparatus comprising:
the electronic invoice parallel invoicing system comprises an original invoice generating module, a data processing module and a data processing module, wherein the original invoice generating module is used for receiving an electronic invoice parallel invoicing request which carries parallel invoicing numbers and generating corresponding original invoices according to the parallel invoicing numbers;
the information acquisition module is used for acquiring each invoice identifier corresponding to each original invoice from the existing invoiceable invoice identifier section and acquiring each invoicing information corresponding to each invoice identifier;
the parallel consensus module is used for performing parallel consensus on each invoice identifier and each corresponding invoice information;
and the invoice writing module is used for generating electronic invoices with parallel invoicing numbers according to each invoice identifier and each corresponding invoicing information and writing the electronic invoices into the block when the invoice identifiers and the corresponding invoicing information pass through the parallel common identification.
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:
receiving an electronic invoice parallel invoicing request carrying parallel invoicing numbers, and generating corresponding original invoices according to the parallel invoicing numbers;
acquiring each invoice identifier corresponding to each original invoice from an existing invoiceable invoice identifier section, and acquiring each invoicing information corresponding to each invoice identifier;
identifying each invoice mark and each corresponding invoice information in parallel;
and when the invoice identifications and the corresponding invoice information are subjected to parallel common identification, generating electronic invoices with parallel invoice numbers according to the invoice identifications and the corresponding invoice information, and writing the electronic invoices into the blocks.
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:
receiving an electronic invoice parallel invoicing request carrying parallel invoicing numbers, and generating corresponding original invoices according to the parallel invoicing numbers;
acquiring each invoice identifier corresponding to each original invoice from an existing invoiceable invoice identifier section, and acquiring each invoicing information corresponding to each invoice identifier;
identifying each invoice mark and each corresponding invoice information in parallel;
and when the invoice identifications and the corresponding invoice information are subjected to parallel common identification, generating electronic invoices with parallel invoice numbers according to the invoice identifications and the corresponding invoice information, and writing the electronic invoices into the blocks.
According to the electronic invoice billing method, the electronic invoice billing device, the computer readable storage medium and the computer equipment, the block link points autonomously generate each original invoice with the parallel billing number, acquire each invoice identifier and each billing information corresponding to each original invoice, and perform parallel consensus on each invoice identifier and each corresponding billing information; when the invoice identifications and the corresponding invoicing information pass through the parallel common identification, the electronic invoices with the parallel invoicing number are generated according to the invoice identifications and the corresponding invoicing information, and the electronic invoices are written into the blocks, so that the block chain link points can issue the electronic invoices in parallel in the block chain, the constraint of atomic operation is eliminated, and the invoicing performance of the block chain electronic invoices is improved.
Drawings
FIG. 1 is a diagram of an environment in which the method for issuing electronic invoices is applied in one embodiment;
FIG. 2 is a schematic flow chart diagram illustrating a method for invoicing electronic invoices in one embodiment;
FIG. 3 is a schematic flow diagram illustrating the generation of a issuable invoice identification field in one embodiment;
FIG. 4 is a schematic flow chart illustrating the process of identifying invoice identifications and corresponding invoice information for an embodiment;
FIG. 5 is a flow diagram that illustrates the process of identifying the matching success results in one embodiment;
FIG. 6 is a flow diagram that illustrates matching recipient identifications, in one embodiment;
FIG. 7 is a flow diagram that illustrates the flow of inhibiting billing by a billing node in one embodiment;
FIG. 8 is a diagram of a conventional electronic invoice flow in one embodiment;
FIG. 9 is a schematic illustration of electronic invoice flow for the present application in one embodiment;
FIG. 10 is a block diagram showing the structure of an electronic invoice issuing apparatus according to an embodiment;
FIG. 11 is a block diagram of a computer device in one embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
FIG. 1 is a diagram of an application environment of the electronic invoice billing method in one embodiment. Referring to fig. 1, the electronic invoice billing method is applied to an electronic invoice billing system. The electronic invoice billing system includes a terminal 102, a server 104, block link points 106 in a block chain, and other block chain nodes. The terminal 102 and the block link point 104 are connected via a network, and the server 104 and the block link point 106 are connected via 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 an independent server or a server cluster comprised of multiple servers. The server 104 may also be implemented as a stand-alone server or as a server cluster comprising a plurality of servers.
Specifically, the block chain node 104 receives an electronic invoice parallel invoicing request sent by the terminal 102 or the server 104, where the electronic invoice parallel invoicing request carries a parallel invoicing number, and generates corresponding original invoices according to the parallel invoicing number. The block chain node 104 obtains each invoice identifier corresponding to each original invoice from the existing issuable invoice identifier section, and obtains each invoicing information corresponding to each invoice identifier. And the blockchain node 104 identifies each invoice identifier and each corresponding invoicing information in parallel. When the invoice identifications and the corresponding invoice information pass through the parallel common identification, the block chain node 104 generates electronic invoices with parallel invoice number according to the invoice identifications and the corresponding invoice information, and writes the electronic invoices into the blocks.
In one embodiment, as shown in FIG. 2, a method of electronic invoice billing is provided. This embodiment is mainly illustrated by applying this method to the block link points in fig. 1. Referring to fig. 2, the electronic invoice billing method specifically includes the following steps:
s202, receiving an electronic invoice parallel invoicing request carrying parallel invoicing numbers, and generating corresponding original invoices according to the parallel invoicing numbers.
The block chain is a serial transaction record which is connected in series by means of cryptography and can ensure that the serial transaction record can not be tampered and forged, and effective transaction records of distributed account book nodes are connected in series based on the characteristics of formula algorithm, encryption algorithm and distributed storage, so that a novel architecture mode of permanent checking capability is provided. The number of parallel invoices 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 does not have invoice identification and specific invoicing information. The invoice identifier 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 invoicing information refers to information required for issuing an electronic invoice, such as the identification of a receiver, the invoicing amount and the like.
Specifically, the block link points receive electronic invoice parallel invoicing requests, the electronic invoice parallel invoicing requests carry parallel invoicing numbers, and corresponding original invoices are generated according to the parallel invoicing numbers. That is, the block chain node can issue assets by itself, and the number of issued assets is controlled by the block chain node itself. .
In one embodiment, a block link point is a vendor server when the vendor server can access the block chain. For example, the seller may be an enterprise and the enterprise server may have access to the blockchain. And at the moment, the enterprise server block chain nodes receive the electronic invoice parallel invoicing request sent by the terminal, the electronic invoice parallel invoicing request carries the parallel invoicing number, and corresponding original invoices are 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 invoices, and the blockchain link point is the proxy platform server. For example, the seller may be a computer of a convenience store, a server of a small-medium enterprise, or the like, and cannot access the blockchain. At this time, the proxy platform server is required to be used for electronic invoice invoicing. The proxy platform server may be a server for proxy electronic invoice invoicing, such as a WeChat server, a Payment server, and the like. The seller registers an account number in a tax bureau platform in advance, logs in the tax bureau platform by using an account number password, selects a proxy platform for issuing electronic invoices, and establishes a corresponding relation between the proxy platform and the seller when a tax bureau platform server receives a seller proxy request, so that the proxy platform server can be used for issuing the electronic invoices instead of the seller. And at the moment, the block chain nodes of the proxy server receive the electronic invoice parallel invoicing request sent by the small and medium-sized enterprise servers, the electronic invoice parallel invoicing request carries the parallel invoicing number, and the block chain nodes of the proxy server generate corresponding original invoices according to the parallel invoicing number.
And S204, acquiring each invoice identifier corresponding to each original invoice from the existing issuable invoice identifier section, and acquiring each invoicing information corresponding to each invoice identifier.
The existing invoices can be issued with the identification section, which is generated in advance according to the intelligent contract and can issue original invoices. The issuable invoice identification field may be generated and stored into the block link point local cache periodically according to an intelligent contract. For example, the existing issuable invoice identifier field is an invoice identifier between 0000 and 1000.
Specifically, the blockchain node acquires each invoice identifier corresponding to each original invoice from an existing issuable invoice identifier section, wherein each invoice identifier cannot be repeated and is unused. And obtaining each invoice information corresponding to each invoice identification. Namely, the invoice identifier and the invoicing information corresponding to each original invoice are obtained.
In one embodiment, each invoice identification in the issuable invoice identification section is marked as used when the corresponding electronic invoice is generated.
And S206, identifying each invoice identification and each corresponding invoicing information in parallel.
The consensus refers to a consensus mechanism in a block chain, and the consensus mechanism is to complete verification and confirmation of a transaction in a short time through voting of a special node. In the present application, the parallel verification and the parallel confirmation of each invoice identification and each invoicing information are carried out.
Specifically, the block chain link points simultaneously carry out parallel consensus on invoice identifications of the parallel invoicing numbers and the block chains sent by the corresponding invoicing information, and obtain consensus results of each invoice identification and the corresponding invoicing information.
And S208, when the invoice identifications and the corresponding invoice information pass through the parallel common identification, generating electronic invoices with parallel invoice number according to the invoice identifications and the corresponding invoice information, and writing the electronic invoices into the blocks.
Specifically, when the invoice identifications and the corresponding invoice information pass through the parallel common identification, the electronic invoices with the number of the parallel invoices are generated according to the invoice identifications and the corresponding invoice information, and the electronic invoices are written into the blocks.
In the electronic invoice billing method, the block link points autonomously generate each original invoice with the number of the invoices in parallel, acquire each invoice identifier and each billing information corresponding to each original invoice, and identify each invoice identifier and each corresponding billing information in parallel; when the invoice identifications and the corresponding invoicing information pass through the parallel common identification, the electronic invoices with the parallel invoicing number are generated according to the invoice identifications and the corresponding invoicing information, and the electronic invoices are written into the blocks, so that the block chain link points can issue the electronic invoices in parallel in the block chain, the constraint of atomic operation is eliminated, and the invoicing performance of the block chain electronic invoices is improved.
In one embodiment, as shown in fig. 3, before step S202, that is, before receiving an electronic invoice parallel invoicing request, where the electronic invoice parallel invoicing request carries a parallel invoicing number, and before generating corresponding original invoices according to the parallel invoicing number, the method further includes the steps of:
s302, receiving an original invoice obtaining request, wherein the original invoice obtaining request carries an invoicing node identifier, and calling an issuing asset intelligent contract according to the original invoice obtaining request.
And S304, generating a dischargeable invoice identification section according to the invoicing node identification by the issued asset intelligent contract, and storing the dischargeable invoice identification section.
The invoicing node identification is used for identifying the node which needs to issue the electronic invoice. The server of the node can be a block chain node or a common server. And the issued asset intelligent contract is used for controlling the available invoice identifications of the invoicing nodes corresponding to the invoicing node identifications.
Specifically, the block link point receives an original invoice obtaining request, the original invoice obtaining request carries an invoicing node identifier, an issued asset intelligent contract is called according to the original invoice obtaining request, the issued asset intelligent contract generates an invoiceable invoice identifier section according to the invoicing node identifier, namely, an original invoice is generated, and the invoiceable invoice identifier section is stored. The original invoice is a blank invoice in which invoice specific information is not written.
In one embodiment, the issued asset intelligent contract can be called regularly, the generated issuable invoice identification section is stored in a local cache, and the generated 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 issued asset intelligent contract, and the issuable invoice identification section is stored, namely, the invoicing node is controlled to be capable of issuing the invoice identification of the electronic invoice, so that the invoicing node is prevented from optionally issuing the invoice.
In one embodiment, as shown in fig. 4, the step S204 of concurrently identifying the invoice identifications and the invoice information includes the steps of:
s402, broadcasting each invoice identification and each corresponding invoicing information to other block chain nodes in parallel.
Specifically, the block chain node broadcasts each invoice identifier and corresponding each invoicing information to other block chain nodes at the same time, that is, broadcasts the electronic invoices with the number of the parallel invoices to other block chain nodes at the same time for consensus verification. Corresponding to the concurrent consensus verification of multiple transactions.
And S404, receiving the consensus through broadcast returned by other block chain nodes, wherein the consensus through broadcast is the confirmation of each invoice identifier and corresponding each invoicing information by other block chain link points.
Specifically, the block link point receives the consensus pass broadcast returned by other block link points, and the consensus pass refers to the verification and confirmation of each invoice identifier and corresponding each invoicing information by other block link points. That is, other block link points receive the consensus broadcast of each invoice identifier and each corresponding invoice information, and after the verification and the confirmation are passed, other block link nodes broadcast the verification and the confirmation passing information to the block chain, so that the block link points receive the consensus passing broadcast returned by other block link points.
And S406, calculating the number of the block chain link points confirmed by each invoice identifier and each corresponding invoice information, and obtaining a parallel consensus result when the number of the block chain link points meets the consensus condition.
The consensus condition means that a preset number of block chain link points in the block chain whole network nodes pass through the consensus.
Specifically, the block link point calculates the number of block link points for confirming each invoice identifier and each corresponding invoice information, and when the number of block link points meets the consensus condition, that is, when the number of block link points for passing the consensus between each invoice identifier and the corresponding invoice information meets the consensus condition, the parallel consensus passing result for each invoice identifier and each corresponding invoice information is obtained.
In the above embodiment, each invoice identifier and each corresponding piece of invoicing information are broadcasted to other block chain nodes in parallel, the number of block chain link points confirmed for each invoice identifier and each corresponding piece of invoicing information is calculated by receiving the consensus through broadcast returned by other block chain link points, and when the number of block chain link points meets the consensus condition, a parallel consensus passing result is obtained. The method gets rid of the constraint that only serial consensus can be realized when the transaction is known in the traditional block chain (the next transaction can be known after one transaction is known). The block chain can identify the invoice identifications and the corresponding invoice information in parallel, and the invoice performance of the block chain electronic invoice is greatly improved.
In one embodiment, as shown in fig. 5, the step S204 of concurrently identifying each invoice id and corresponding each invoicing information includes the steps of:
and S502, calling an intelligent invoicing contract, determining invoicing conditions according to each invoice identifier by the intelligent invoicing contract, and matching the invoicing conditions with each invoicing information.
The intelligent contract for invoicing is used for controlling uncontrolled invoicing of the block chain nodes. The invoicing condition refers to a condition capable of issuing an electronic invoice, and may include whether an invoicing party is a corresponding agent facilitator, whether an invoicing amount exceeds a maximum limit, whether a receiving party of the invoicing is a receivable party, whether the invoicing party is a distrusted party, and the like.
Specifically, the block chain node calls an intelligent billing contract, the intelligent billing contract obtains corresponding billing node identifications according to the invoice identifications, corresponding billing conditions are determined according to the billing node identifications, and the billing conditions are matched with the billing information. For example, the agent facilitator in the billing condition is matched with the agent facilitator in the billing information, whether the agent facilitator is consistent or not is judged, and when the agent facilitator is consistent, the agent facilitator in the billing information is the agent facilitator corresponding to the billing node identifier. The receivable party 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 invoicing receiver identification is the receivable party identification of the electronic invoice. And matching the invoicing node identification which is not lost in the invoicing condition with the invoicing node identification in the invoicing information to judge whether the invoicing node identification is consistent, and when the invoicing node identification is consistent, indicating that the invoicing node corresponding to the invoicing node identification is not a lost party.
S504, when the matching of each invoicing information and the invoicing condition is successful, each matching success result is obtained, and the matching success results are identified together.
S506, determining the number of the block chain links which pass the consensus corresponding to each matching success result, and obtaining the consensus passing result when the number of the block chain links meets the consensus condition.
The consensus condition means that a preset number of block chain link points in the block chain whole network nodes pass through the consensus.
Specifically, when the invoicing information is successfully matched with the invoicing conditions, the matching result is obtained, namely each invoicing information has a corresponding matching result. And broadcasting each matching success result to the block chain whole network nodes, and performing consensus through a consensus algorithm. The consensus algorithm includes PoW (workload certification algorithm), PoS (equity certification algorithm), PBFT (practical byzantine fault-tolerant algorithm), and the like. And then when the common identification confirmation broadcasted by other block chain nodes is received, determining the number of the block chain links passing the common identification corresponding to each matching success result, and obtaining the common identification passing result when the number of the block chain links meets the common identification condition.
In one embodiment, when the matching of the invoicing information and the invoicing conditions fails, a matching failure result is obtained, a corresponding invoicing identifier is obtained according to the invoicing information with the matching failure, and the matching failure result, the invoicing information and the corresponding invoicing identifier are returned to the invoicer.
In the embodiment, the invoicing intelligent contract is called, the invoicing condition is determined according to each invoice identifier, the invoicing condition is matched with each invoicing information, when each invoicing information is successfully matched with the invoicing condition, the matching success results are identified together to obtain the identification passing result, namely the invoicing of the block chain node is controlled through the invoicing intelligent contract, so that the invoicing behavior of the block chain node can be controlled, and abnormal invoicing of the block chain node is prevented.
In one embodiment, as shown in fig. 6, step S402, invoking an intelligent billing contract, determining billing conditions according to the respective invoice identifications by the intelligent billing contract, and matching the billing conditions with the respective billing information includes:
and S602, determining an invoicing node identifier according to each invoice identifier by the intelligent invoicing contract, and determining each receiver identifier capable of invoicing according to the invoicing node identifier.
The receiver identification is used for identifying the receiver of the electronic invoice. The recipient is a consumer. May be an individual, a business, etc.
Specifically, the invoicing intelligent contract can obtain the issuable invoice identification section where the invoice identification is located according to the invoice identification, determine the invoicing node identification according to the discoverable invoice identification section, and search the corresponding invoiceable receiver identification from the invoicing conditions according to the invoicing node identification.
S604, determining each target receiver identification from each invoicing information, and matching each target receiver identification with each receiver identification capable of invoicing.
And S606, obtaining a matching success result when the identifiers of all the receivers capable of making out the invoice are consistent with the identifiers of all the targets.
The target receiver identification is used for identifying a receiver of the electronic invoice in the invoicing information, and can be a name, a character string, a number and the like. The recipient is a consumer, and may be an individual, a business, or the like.
Specifically, the block chain node determines each target receiver identification from each invoicing information, namely the receiver identification to be invoiced in each invoicing information. And matching each target receiver identification with each billable receiver identification in the billing condition. When the identification of each target receiver is consistent with the identification of each receiver capable of making an invoice, the identification of each target receiver exists in the identification of each receiver capable of making an invoice, and at the moment, a successful matching result is obtained.
In the above embodiment, by matching each target recipient identifier in each invoicing information with each recipient identifier capable of invoicing, when each target receiving identifier exists in each recipient identifier capable of invoicing, a successful matching result is obtained, and the block chain node can be controlled to invoice the recipients corresponding to each recipient identifier capable of invoicing.
In one embodiment, as shown in fig. 7, the electronic invoice issuing method further includes:
s702, when the invoice identification and the invoicing information pass through the parallel common identification, each invoice identification and each invoicing information are sent to a 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, an invoicing forbidding request is sent to block link points, wherein the invoicing request carries invoicing node identification.
The electronic invoice information refers to information obtained according to the electronic invoices in the block chain, and may include, for example, the number of electronic invoices issued by the invoicing node corresponding to the invoicing node identifier within a period of time. The method also can comprise that the billing node marks the corresponding billing node billing total amount in a period of time. And also the number and name of the recipient identification included in the electronic invoice over a period of time. The preset early warning rule refers to an early warning rule for presetting the risk of electronic invoice invoicing, the early warning rule can be that the number of electronic invoices issued by invoicing nodes corresponding to the invoicing node identification exceeds a preset number within a period of time, the total invoicing amount of the invoicing nodes exceeds a preset early warning value within a period of time, the number and the name of the receiver identification in the electronic invoice are abnormal within a period of time, and the like.
Specifically, when the common identification of each invoice label and each corresponding invoicing information passes, the block link point sends each invoice label and each invoicing information to the tax office server, namely, the electronic invoice is sent to the tax office server after the common identification is successful each time. The tax bureau server can obtain the electronic invoices sent by each invoicing node, count the electronic invoice information corresponding to each invoicing node, and send the invoicing forbidding request to the block link points when the electronic invoice information of the invoicing node triggers the preset early warning rule, wherein the invoicing request carries the invoicing node identification.
And S704, receiving the invoicing forbidding request sent by the tax office server, calling the invoicing forbidding intelligent contract according to the invoicing forbidding request, and forbidding the invoicing of the corresponding invoicing node according to the invoicing node identifier by the invoicing intelligent contract.
And the intelligent contract for forbidding invoicing is used for limiting the invoicing nodes corresponding to the invoicing node identification to issue the assets and performing electronic invoicing.
Specifically, the block link points receive invoicing forbidding requests sent by the tax bureau server, call invoicing forbidding intelligent contracts according to the invoicing forbidding requests, forbid the invoicing intelligent contracts to forbid corresponding invoicing nodes to issue assets according to invoicing node identifications and conduct electronic invoicing.
In one embodiment, an early warning monitoring system is arranged in a tax bureau server, block chain common identification nodes are monitored, when the common identification nodes pass common identification each time, the tax bureau server synchronizes electronic invoices, then electronic invoice information of each invoicing node is counted according to the synchronized electronic invoices, when a counting result triggers an early warning rule, an invoicing forbidding request is sent to the block chain nodes, the block chain nodes receive the invoicing forbidding request sent by the tax bureau server, an invoicing intelligent contract is called according to the invoicing request, and the invoicing intelligent contract forbids corresponding invoicing nodes to carry out electronic invoice invoicing according to invoicing node identification.
In the embodiment, the tax office server can obtain the rule making and control capacity of the block chain electronic invoice system through the early warning system and the intelligent contract, so that the supervision capacity of the tax office server on the electronic invoice is improved, and the invoicing node is prevented from optionally invoicing.
In one embodiment, before receiving an electronic invoice parallel invoicing request, where the electronic invoice parallel invoicing request carries a parallel invoicing number, and generating corresponding original invoices according to the parallel invoicing number, the method further includes:
receiving an intelligent contract deployment request, wherein the intelligent contract deployment request carries an intelligent contract for making an invoice, an intelligent contract for issuing an asset and an intelligent contract for forbidding making an invoice, and deploying the intelligent contract for making an invoice, the intelligent contract for issuing the asset and the intelligent contract for making an invoice into a block chain according to the intelligent contract deployment request.
The intelligent contract is a set of a piece of code and data, and can be deployed on a blockchain network to run. The intelligent contract is interpreted into byte codes by the virtual machine to be executed.
Specifically, the block link point receives an intelligent contract deployment request sent by a tax office server, the intelligent contract deployment request carries an intelligent contract for making out an invoice, an intelligent contract for issuing an asset and an intelligent contract for prohibiting making out an invoice, a compiler is called to compile corresponding intelligent contract codes into virtual machine byte codes according to the intelligent contract deployment request, the intelligent contract for issuing an asset and the intelligent contract for restricting making out an invoice, then the virtual machine byte codes are sent to the block link network through an interface, and the virtual machine byte codes are written into the block link block after being verified by the block link network. At this point, the invoicing intelligent contracts, the issued asset intelligent contracts, and the invoicing restriction intelligent contracts are deployed into the blockchain. Then correspondingly generating an intelligent contract address, and using the intelligent contract address can be calling the corresponding intelligent contract.
In the embodiment, the intelligent contracts are obtained in advance, the intelligent contracts for issuing the invoices, the intelligent contracts for forbidding the invoicing are obtained, and the intelligent contracts are deployed in the block chain, so that the intelligent contracts can be directly called from the block chain in use, the efficiency is improved, and the use is convenient.
In one specific embodiment, in the traditional invoice business, the invoice assets belong to the tax bureau, and the invoicing facilitator needs to receive invoices (including online and offline) from the tax bureau to execute the invoicing capability. Based on this background, the process of obtaining an electronic invoice flow is shown in fig. 8. In fig. 8, when the billing enterprise bills, an asset is first collected from the tax bureau (the number of assets is determined by the tax bureau according to rules, for example, 100 invoices are collected, and one invoice is an asset). Then, the invoicing enterprise can only execute invoicing operation, the assets can be reduced by 1 when each invoice is invoiced, the invoicing can not be carried out when the invoiced assets are reduced to 0, and the invoiced assets need to be collected by the tax bureau again. In the blockchain, the billing process has a great performance bottleneck, the operation atomicity needs to be kept due to the fact that the number of assets of a billing enterprise is reduced, and the billing operation in the blockchain, namely the asset transfer, is a serial action, so that the billing performance of the blockchain electronic invoice is extremely low.
The present application maps electronic invoices onto asset releases in blockchain technology. According to the block chain characteristic, the asset issuing can get rid of the constraint of atomic operation, so that the invoicing enterprise can execute invoicing operation concurrently, and the invoicing performance of the electronic invoice is greatly improved. As shown in fig. 9, which is a schematic diagram of the circulation of the electronic invoice in the embodiment of the present application, the invoicing enterprise may issue assets autonomously, which simplifies the process of the invoicing enterprise to obtain the invoice assets from the tax bureau. The method specifically comprises the following steps:
the tax bureau server formulates an intelligent contract for making out an invoice, an intelligent contract for issuing an asset and an intelligent contract for forbidding making out an invoice, and sends the formulated intelligent contract for making out an invoice, the intelligent contract for issuing an asset and the intelligent contract for forbidding making out an invoice to the block chain nodes, and the block chain nodes deploy the intelligent contract for making out an invoice, the intelligent contract for issuing an asset and the intelligent contract for forbidding making out an invoice to the block chain.
And the invoicing enterprise node is a block link node, and the issuing asset intelligent contract is called at regular time to generate an issuable invoice identification section and store the issuable invoice identification section in a local cache. The method comprises the steps that an invoicing enterprise receives an electronic invoice asset issuing request which carries an asset issuing line number, corresponding original invoices are generated according to the parallel invoicing line number, invoice identifications corresponding to the original invoices are obtained from an existing invoiceable invoice identification section, and invoicing information corresponding to the invoice identifications is obtained. The method comprises the steps of parallelly identifying each invoice mark and each corresponding invoicing information, namely calling an invoicing intelligent contract by an invoicing enterprise node, determining an invoicing condition according to each invoice mark by the invoicing intelligent contract, matching the invoicing condition with each invoicing information, obtaining a matching success result when each invoicing information is successfully matched with the invoicing condition, identifying the matching success result, each invoice mark and each corresponding invoicing information, determining the number of block chain links passing the consensus, obtaining the consensus result when the number of the block chain links meets the consensus condition, generating an electronic invoice of the number of asset issue lines according to each invoice mark and each corresponding invoicing information, and writing the electronic invoice into a block.
The consumer can search the corresponding electronic invoice from the block chain and reimburse the electronic invoice at the block chain link point of the reimbursement enterprise. And after the reimbursement of the electronic invoice is finished, the reimbursement enterprise block chain node also sends the reimbursed electronic invoice to the tax bureau block chain node for reimbursement of tax, and the circulation of the electronic invoice is finished.
It should be understood that although the various steps in the flowcharts of fig. 2-7 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2-7 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performance of the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternating with other steps or at least some of the sub-steps or stages of other steps.
In one embodiment, as shown in fig. 10, there is provided an electronic invoice issuing apparatus 1000 including:
the original invoice generating module 1002 is configured to receive an electronic invoice parallel invoicing request, where the electronic invoice parallel invoicing request carries parallel invoicing numbers, and generate corresponding original invoices according to the parallel invoicing numbers;
the information acquisition module 1004 is used for acquiring each invoice identifier corresponding to each original invoice from the existing issuable invoice identifier section and acquiring each invoicing information corresponding to each invoice identifier;
a parallel consensus module 1006, configured to perform parallel consensus on each invoice identifier and each corresponding invoice information;
and an invoice writing module 1008, configured to generate electronic invoices with parallel invoicing numbers according to each invoice identifier and corresponding each invoicing information, and write the electronic invoices into the block when the parallel common identification of each invoice identifier and corresponding each invoicing information passes.
In one embodiment, the electronic invoice issuing apparatus 1000 further includes:
the contract calling module is used for receiving an original invoice obtaining request, carrying an invoicing node identifier, and calling an issued asset intelligent contract according to the original invoice obtaining request;
and the section generation module is used for generating a section of the invoice identifier which can be issued according to the invoice node identifier by issuing the asset intelligent contract and storing the section of the invoice identifier which can be issued.
In one embodiment, the parallel consensus module 1006 is further configured to broadcast each invoice id and corresponding each invoicing information in parallel to other blockchain nodes; receiving a consensus pass broadcast returned by other block chain nodes, wherein the consensus pass is the confirmation of each invoice identifier and corresponding each invoicing information by other block chain link points; and calculating the number of the block chain link points confirmed for each invoice identification and each corresponding invoice information, and obtaining a parallel consensus result when the number of the block chain link points meets the consensus condition.
In one embodiment, the parallel consensus module 1006 is further configured to invoke an intelligent invoicing contract, where the intelligent invoicing contract determines invoicing conditions according to the invoice identifications, and matches the invoicing conditions with the invoicing information; when the invoicing information is successfully matched with the invoicing conditions, obtaining the matching success results, and identifying the matching success results; and determining the number of the block chain links which pass the consensus corresponding to each matching success result, and obtaining the consensus passing result of each matching success result when the number of the block chain links 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 invoiceable receiver identifier according to the invoicing node identifier; determining each target receiver identification from each invoicing information, and matching each target receiver identification with each receiver identification capable of invoicing; and when the identifiers of all receivers capable of making out the invoice are consistent with the identifiers of all the targets, obtaining a matching success result.
In one embodiment, the electronic invoice issuing apparatus 1000 further includes:
the information sending module is used for sending each invoice identifier and each corresponding invoice information to the tax bureau server when the invoice identifiers and the corresponding invoice information are subjected to parallel common identification so as to enable the tax bureau server to count the electronic invoice information, and sending an invoice forbidding request to the block link points when the electronic invoice information triggers a preset early warning rule, wherein the invoice forbidding request carries an invoice node identifier;
and the billing forbidding module is used for receiving the billing forbidding request sent by the tax office server, calling the billing forbidding intelligent contract according to the billing forbidding request, and forbidding the billing of the corresponding billing node according to the billing node identifier by the billing forbidding intelligent contract.
In one embodiment, the electronic invoice issuing apparatus 1000 further includes:
the contract deployment module is used for receiving an intelligent contract deployment request which carries an intelligent contract for making an invoice, an intelligent contract for issuing an asset and an intelligent contract for forbidding making an invoice, and deploying the intelligent contract for making an invoice, the intelligent contract for issuing the asset and the intelligent contract for restricting making an invoice into the block chain according to the intelligent contract deployment request.
FIG. 11 is a diagram illustrating an internal structure of a computer device in one embodiment. The computer device may specifically be block link point 104 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 comprises a nonvolatile 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 an operating system and computer programs in the non-volatile storage medium. 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 invoicing.
Those skilled in the art will appreciate that the architecture shown in fig. 11 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, the electronic invoice issuing apparatus provided herein may be implemented in the form of a computer program that is executable on a computer device such as that shown in fig. 11. The memory of the computer device may store various program modules constituting the electronic invoice issuing device, such as an original invoice generating module 1002, an information acquiring module 1004, a parallel consensus module 1006 and an invoice writing module 1008 shown in fig. 10. The computer program of each program module makes the processor execute the steps of the electronic invoice issuing method of each embodiment of the application described in the specification.
For example, the computer device shown in fig. 11 may execute step S202 through the original invoice generation module 1002 in the electronic invoice issuing apparatus shown in fig. 10. The computer device may perform step S204 through the information acquisition module 1004. The computer device may perform step S206 by the parallel consensus module 1006. The computer device may perform step S208 via the invoice write module 1008.
In one embodiment, a computer device is provided, comprising a memory and a processor, the memory storing a computer program which, when executed by the processor, causes the processor to perform the steps of the above-described electronic invoice invoicing method. Here, the steps of the electronic invoice issuing method may be the steps of the electronic invoice issuing method of each of the above embodiments.
In one embodiment, a computer readable storage medium is provided, storing a computer program that, when executed by a processor, causes the processor to perform the steps of the above-described electronic invoice invoicing method. Here, the steps of the electronic invoice issuing method may be the steps of the electronic invoice issuing method of each of the above embodiments.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a non-volatile computer-readable storage medium, and can include the processes of the embodiments of the methods described above when the program is executed. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile 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 DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present application. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
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 invoiceable invoice identifier section, and acquiring each invoicing information corresponding to each invoice identifier;
identifying each invoice mark and each corresponding invoice information in parallel;
and when the invoice identifications and the corresponding invoice information are identified in parallel and passed, generating the electronic invoice of the asset issuing line number according to the invoice identifications and the corresponding invoice information, and writing the electronic invoice into a block.
2. The method according to claim 1, wherein before the receiving the electronic invoice parallel invoicing request, the electronic invoice parallel invoicing request carrying parallel invoicing numbers, and generating corresponding original invoices according to the parallel invoicing numbers, the method further comprises:
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;
and the issued 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 according to claim 1, wherein said identifying in parallel each invoice id and each corresponding invoice information comprises:
broadcasting the invoice identifications and the corresponding invoice information to other block chain nodes in parallel;
receiving a consensus pass broadcast returned by the other block link points, wherein the consensus pass refers to confirmation of the other block link points on each invoice identification and each corresponding invoice information;
and calculating the number of the block chain link points confirmed for each invoice mark and each corresponding invoice information, and obtaining a parallel consensus result when the number of the block chain link points meets a consensus condition.
4. The method according to claim 1, wherein said identifying in parallel each invoice id and each corresponding invoice information comprises:
calling an intelligent invoicing contract, determining invoicing conditions according to the invoice identifications by the intelligent invoicing contract, and matching the invoicing conditions with the invoicing information;
when the invoicing information is successfully matched with the invoicing conditions, obtaining each matching success result, and identifying each matching success result;
and determining the number of the block chain links passing the consensus corresponding to each matching success result, and obtaining the consensus passing result of each matching success result when the number of the block chain links meets the consensus condition.
5. The method of claim 4, wherein invoking the intelligent contract for invoicing, the intelligent contract for invoicing determining invoicing conditions based on the respective invoice identifications, and matching the invoicing conditions to the respective invoicing information comprises:
the intelligent invoicing contract determines invoicing node identifications according to the invoice identifications, and determines receiver identifications capable of invoicing according to the invoicing node identifications;
determining each target receiver identification from each invoicing information, and matching each target receiver identification with each receiver identification capable of invoicing;
and when the identifiers of all the receivers capable of making the invoice are consistent with the identifiers of all the targets, obtaining a matching success result.
6. The method of claim 1, further comprising:
when the invoice identifications and the corresponding invoice information are identified in parallel and passed, the invoice identifications and the corresponding invoice information are sent to a tax office server so that the tax office server counts electronic invoice information, when the electronic invoice information triggers a preset early warning rule, an invoice forbidding request is sent to a block link point, and the invoice forbidding request carries an invoice node identification;
and receiving a request for forbidding invoicing sent by the tax office server, and calling an intelligent contract for forbidding invoicing according to the request for forbidding invoicing, wherein the intelligent contract for forbidding invoicing forbids invoicing of a corresponding invoicing node according to the invoicing node identifier.
7. The method according to claim 1, wherein before the receiving the electronic invoice parallel invoicing request, the electronic invoice parallel invoicing request carrying parallel invoicing numbers, and generating corresponding original invoices according to the parallel invoicing numbers, the method further comprises:
receiving an intelligent contract deployment request carrying the intelligent contract for making an invoice, the intelligent contract for issuing an asset and the intelligent contract for prohibiting making an invoice, and deploying the intelligent contract for making an invoice, the intelligent contract for issuing an asset and the intelligent contract for restricting making an invoice into a block chain according to the intelligent contract deployment request.
8. An electronic invoice issuing apparatus, characterised in that the apparatus comprises:
the system comprises an original invoice generating module, a receiving module and a processing module, wherein the original invoice generating module is used for receiving an electronic invoice parallel invoicing request which carries parallel invoicing numbers, and generating corresponding original invoices according to the parallel invoicing numbers;
the information acquisition module is used for acquiring each invoice identifier corresponding to each original invoice from the existing invoiceable invoice identifier section and acquiring each invoicing information corresponding to each invoice identifier;
the parallel consensus module is used for performing parallel consensus on each invoice identifier and each corresponding invoice information;
and the invoice writing module is used for generating the electronic invoices with the parallel invoicing number according to each invoice mark and the corresponding invoicing information when the invoice marks and the corresponding invoicing information are identified in parallel and pass, and writing the electronic invoices into the blocks.
9. A computer-readable storage medium, storing a computer program which, when executed by a processor, causes the processor to carry out the steps of the method according to any one of claims 1 to 7.
10. 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 according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910871790.3A CN110599267A (en) | 2019-09-16 | 2019-09-16 | Electronic invoice billing method and device, computer readable storage medium and computer equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910871790.3A CN110599267A (en) | 2019-09-16 | 2019-09-16 | Electronic invoice billing method and device, computer readable storage medium and computer equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110599267A true CN110599267A (en) | 2019-12-20 |
Family
ID=68859902
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910871790.3A Pending CN110599267A (en) | 2019-09-16 | 2019-09-16 | Electronic invoice billing method and device, computer readable storage medium and computer equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110599267A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111062766A (en) * | 2019-12-20 | 2020-04-24 | 中国银联股份有限公司 | Block chain-based electronic invoice issuing method and device |
| CN111160998A (en) * | 2020-04-02 | 2020-05-15 | 支付宝(杭州)信息技术有限公司 | Comment data processing method and device based on block chain and comment system |
| CN111242707A (en) * | 2020-01-21 | 2020-06-05 | 腾讯科技（深圳）有限公司 | Data processing method and device and readable storage medium |
| WO2021139544A1 (en) * | 2020-01-08 | 2021-07-15 | Alipay Labs (singapore) Pte. Ltd. | Methods and devices for mitigating invoice financing fraud |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109034924A (en) * | 2018-08-16 | 2018-12-18 | 腾讯科技（深圳）有限公司 | Electronic bill generation method, device, storage medium and computer equipment |
| CN109241772A (en) * | 2018-09-07 | 2019-01-18 | 腾讯科技（深圳）有限公司 | Invoice block chained record method, apparatus, block chain gateway server and medium |
| CN109785024A (en) * | 2019-01-04 | 2019-05-21 | 深圳壹账通智能科技有限公司 | Invoice data processing method, device, computer equipment and storage medium |
-
2019
- 2019-09-16 CN CN201910871790.3A patent/CN110599267A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109034924A (en) * | 2018-08-16 | 2018-12-18 | 腾讯科技（深圳）有限公司 | Electronic bill generation method, device, storage medium and computer equipment |
| CN109241772A (en) * | 2018-09-07 | 2019-01-18 | 腾讯科技（深圳）有限公司 | Invoice block chained record method, apparatus, block chain gateway server and medium |
| CN109785024A (en) * | 2019-01-04 | 2019-05-21 | 深圳壹账通智能科技有限公司 | Invoice data processing method, device, computer equipment and storage medium |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111062766A (en) * | 2019-12-20 | 2020-04-24 | 中国银联股份有限公司 | Block chain-based electronic invoice issuing method and device |
| WO2021139544A1 (en) * | 2020-01-08 | 2021-07-15 | Alipay Labs (singapore) Pte. Ltd. | Methods and devices for mitigating invoice financing fraud |
| CN111242707A (en) * | 2020-01-21 | 2020-06-05 | 腾讯科技（深圳）有限公司 | Data processing method and device and readable storage medium |
| CN111160998A (en) * | 2020-04-02 | 2020-05-15 | 支付宝(杭州)信息技术有限公司 | Comment data processing method and device based on block chain and comment system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109255084B (en) | Electronic bill query method, device, storage medium and computer equipment | |
| CN110633323B (en) | Service data storage method, device, storage medium and computer equipment | |
| CN110599267A (en) | Electronic invoice billing method and device, computer readable storage medium and computer equipment | |
| CN110442652B (en) | Cross-chain data processing method and device based on block chain | |
| CN109191272B (en) | Data processing method, device, storage medium and equipment for electronic bill | |
| CN110599266B (en) | Electronic bill data processing method and device, computer equipment and storage medium | |
| CN110232565B (en) | Resource clearing method, device, computer equipment and storage medium | |
| CN110633963B (en) | Electronic bill processing method, electronic bill processing device, computer readable storage medium and computer readable storage device | |
| CN110602239A (en) | Block chain information storage method and related equipment | |
| CN108985742B (en) | Transaction processing method and device and block chain system | |
| CN110599137A (en) | Electronic bill data processing method and device and computer equipment | |
| CN111506584B (en) | Block chain-based service data processing method and device and computer equipment | |
| CN111090581B (en) | Intelligent contract testing method, intelligent contract testing device, computer equipment and storage medium | |
| CN111191294B (en) | Single-node accounting method, system, equipment and storage medium based on block chain | |
| CN111209113B (en) | Resource allocation method, device, equipment and storage medium based on intelligent contract | |
| CN111507717B (en) | Data processing method, device, block node and computer readable storage medium | |
| CN111125773B (en) | Method, device, equipment and medium for processing customs declaration information based on block chain | |
| CN109656778A (en) | Data capture method, device, computer equipment and storage medium | |
| CN109460995B (en) | Financial certification method, device, computer equipment and storage medium | |
| CN110738471A (en) | bill management method based on block chain network and related equipment | |
| CN108366132B (en) | Method and device for managing service between servers, computer equipment and storage medium | |
| CN111488626A (en) | Data processing method, device, equipment and medium based on block chain | |
| CN110011796B (en) | Certificate updating method and device, computer equipment and storage medium | |
| CN111260475A (en) | Data processing method, block chain node point equipment and storage medium | |
| CN113626218A (en) | Data processing method, data processing device, storage medium and computer equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |