CN109949108A - Invoice creation method and device, electronic equipment based on block chain - Google Patents
Invoice creation method and device, electronic equipment based on block chain Download PDFInfo
- Publication number
- CN109949108A CN109949108A CN201811519702.5A CN201811519702A CN109949108A CN 109949108 A CN109949108 A CN 109949108A CN 201811519702 A CN201811519702 A CN 201811519702A CN 109949108 A CN109949108 A CN 109949108A
- Authority
- CN
- China
- Prior art keywords
- invoice
- party
- creation
- limit
- invoice creation
- 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 29
- 238000011156 evaluation Methods 0.000 claims abstract description 45
- 230000004044 response Effects 0.000 claims abstract description 8
- 238000010801 machine learning Methods 0.000 claims description 13
- 238000005516 engineering process Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 3
- 238000012546 transfer Methods 0.000 description 3
- 238000013210 evaluation model Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000012549 training Methods 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000007477 logistic regression Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Business, Economics & Management (AREA)
- Physics & Mathematics (AREA)
- Development Economics (AREA)
- Databases & Information Systems (AREA)
- General Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Strategic Management (AREA)
- Marketing (AREA)
- Finance (AREA)
- Economics (AREA)
- Computing Systems (AREA)
- Accounting & Taxation (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
This specification one or more embodiment provides a kind of invoice creation method and device, electronic equipment based on block chain, which comprises receives the invoice request to create that user is initiated by client；Wherein, the invoice request to create includes the invoice creation information of user's input；In response to the invoice request to create, determine whether the invoice creation amount of invoice issuing side corresponding with the invoice request to create is sufficient；If the invoice creation amount of the invoice issuing side is sufficient, the invoice creation logic stated in preset intelligent contract is called, information creating target invoice is created based on the invoice；And the invoice creation record for corresponding to the target invoice is generated, and credit scoring is obtained to invoice issuing side progress credit evaluation based on invoice creation record；Wherein, the credit scoring is used to determine the invoice creation amount of the invoice issuing side, carries out dynamic update with the invoice creation amount to the invoice issuing side.
Description
Technical Field
One or more embodiments of the present disclosure relate to the field of terminal technologies, and in particular, to a block chain-based invoice creation method and apparatus, and an electronic device.
Background
The block chain technology, also called distributed ledger technology, is an emerging technology in which several computing devices participate in "accounting" together, and a complete distributed database is maintained together. Because the blockchain technology has the characteristics of decentralization and openness, each computing device can participate in database recording, and data synchronization can be rapidly performed among the computing devices, a decentralization system is built by using the blockchain technology, and various execution programs are recorded in a distributed database of a blockchain to be automatically executed, so that the blockchain technology is widely applied in a plurality of fields.
Disclosure of Invention
The present specification provides a block chain-based invoice creation method, including:
receiving an invoice creation request initiated by a user through a client; wherein the invoice creation request comprises invoice creation information input by a user;
in response to the invoice creation request, determining whether an invoice creation quota of an invoice provider corresponding to the invoice creation request is sufficient;
if the invoice creating limit of the invoice issuing party is sufficient, calling invoice creating logic declared in a preset intelligent contract, and creating a target invoice based on the invoice creating information; and the number of the first and second groups,
generating an invoice creation record corresponding to the target invoice, and performing credit evaluation on the invoice issuing party based on the invoice creation record to obtain a credit score; the credit score is used for determining the invoice creation limit of the invoice issuing party so as to dynamically update the invoice creation limit of the invoice issuing party.
Optionally, the determining whether the invoice creation quota of the invoicing party corresponding to the invoice creation request is sufficient includes:
calling the limit checking logic declared in the intelligent contract to determine whether the invoice creation limit of the invoice issuing party corresponding to the invoice creation request is sufficient; or,
calling a trusted service of a third party, sending the invoice creation request to the trusted service of the third party, so that the trusted service of the third party determines whether the invoice creation quota of the invoice issuing party corresponding to the invoice creation request is sufficient, and receiving a determination result of whether the invoice creation quota of the invoice issuing party returned by the trusted service of the third party is sufficient.
Optionally, said performing a credit assessment on said invoice presenters based on said invoice creation record results in a credit score, comprising:
and calling a trusted service of a third party, sending the invoice creation record to the trusted service of the third party, and performing credit evaluation on the invoice issuing party by the trusted service of the third party based on the invoice creation record to obtain a credit score.
Optionally, the method further comprises:
receiving a credit score of the invoicing party returned by a trusted service of the third party;
calling a limit determination logic declared in the intelligent contract, determining an invoice creation limit of the invoice issuing party based on the credit score, and dynamically updating the invoice creation limit of the invoice issuing party based on the determined invoice creation limit.
Optionally, the method further comprises:
receiving an invoice creation limit of the invoicing party determined based on the credit score of the invoicing party returned by the trusted service of the third party;
and dynamically updating the invoice establishing limit of the invoice issuing party based on the received invoice establishing limit.
Optionally, the trusted service of the third party includes a machine learning model deployed on a trusted service device of the third party.
This specification also proposes a block chain-based invoice creation apparatus, the apparatus including:
the first receiving module is used for receiving an invoice creating request initiated by a user through a client; wherein the invoice creation request comprises invoice creation information input by a user;
the determining module is used for responding to the invoice creating request and determining whether the invoice creating limit of the invoice issuing party corresponding to the invoice creating request is sufficient;
the creating module is used for calling invoice creating logic declared in a preset intelligent contract and creating a target invoice based on the invoice creating information if the invoice creating limit of the invoice issuing party is sufficient; and the number of the first and second groups,
the evaluation module is used for generating an invoice creation record corresponding to the target invoice and performing credit evaluation on the invoice issuing party based on the invoice creation record to obtain a credit score; the credit score is used for determining the invoice creation limit of the invoice issuing party so as to dynamically update the invoice creation limit of the invoice issuing party.
Optionally, the determining module is specifically configured to:
calling the limit checking logic declared in the intelligent contract to determine whether the invoice creation limit of the invoice issuing party corresponding to the invoice creation request is sufficient; or,
calling a trusted service of a third party, sending the invoice creation request to the trusted service of the third party, so that the trusted service of the third party determines whether the invoice creation quota of the invoice issuing party corresponding to the invoice creation request is sufficient, and receiving a determination result of whether the invoice creation quota of the invoice issuing party returned by the trusted service of the third party is sufficient.
Optionally, the evaluation module is specifically configured to:
and calling a trusted service of a third party, sending the invoice creation record to the trusted service of the third party, and performing credit evaluation on the invoice issuing party by the trusted service of the third party based on the invoice creation record to obtain a credit score.
Optionally, the apparatus further comprises:
the second receiving module is used for receiving the credit score of the invoicing party returned by the trusted service of the third party;
and the first updating module is used for calling the quota determining logic declared in the intelligent contract, determining the invoice establishing quota of the invoice issuing party based on the credit score, and dynamically updating the invoice establishing quota of the invoice issuing party based on the determined invoice establishing quota.
Optionally, the apparatus further comprises:
the third receiving module is used for receiving the invoice creation limit of the invoicing party, which is determined based on the credit score of the invoicing party and returned by the trusted service of the third party;
and the second updating module is used for dynamically updating the invoice establishing limit of the invoice issuing party based on the received invoice establishing limit.
Optionally, the trusted service of the third party includes a machine learning model deployed on a trusted service device of the third party.
This specification also proposes an electronic device including:
a processor;
a memory for storing machine executable instructions;
wherein, by reading and executing machine-executable instructions stored by the memory corresponding to control logic for blockchain based invoice creation, the processor is caused to:
receiving an invoice creation request initiated by a user through a client; wherein the invoice creation request comprises invoice creation information input by a user;
in response to the invoice creation request, determining whether an invoice creation quota of an invoice provider corresponding to the invoice creation request is sufficient;
if the invoice creating limit of the invoice issuing party is sufficient, calling invoice creating logic declared in a preset intelligent contract, and creating a target invoice based on the invoice creating information; and the number of the first and second groups,
generating an invoice creation record corresponding to the target invoice, and performing credit evaluation on the invoice issuing party based on the invoice creation record to obtain a credit score; the credit score is used for determining the invoice creation limit of the invoice issuing party so as to dynamically update the invoice creation limit of the invoice issuing party.
In the above technical solution, when a user needs to create an invoice corresponding to an invoice issuer in a blockchain, an invoice creation amount check may be performed on the invoice issuer first, so that when the invoice creation amount of the invoice issuer is determined to be sufficient, the invoice is created, a corresponding invoice creation record is generated, subsequently, a credit evaluation may be performed on the invoice issuer based on the invoice creation record to obtain a credit score, and the invoice creation amount of the invoice issuer is dynamically updated based on the credit score. Compared with the common manual invoice establishing limit updating mode, the method has the advantages that the invoice establishing limit of the invoice issuing party can be dynamically updated based on the invoice establishing record of the invoice issuing party, so that the updating period of the invoice establishing limit can be shortened, and the correlation degree of the invoice establishing limit and the operation condition of the invoice issuing party is improved.
Drawings
FIG. 1 is a flow chart diagram illustrating a method for blockchain-based invoice creation in accordance with an exemplary embodiment of the present description;
fig. 2 is a hardware structure diagram of an electronic device where a blockchain-based invoice creation apparatus is located according to an exemplary embodiment of the present specification;
fig. 3 is a block diagram of an invoice creation apparatus based on a blockchain according to an exemplary embodiment of the present specification.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of one or more embodiments of the specification, as detailed in the claims which follow.
The terminology used in the description herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the description. As used in this specification and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, the first information may also be referred to as second information, and similarly, the second information may also be referred to as first information, without departing from the scope of the present specification. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
The technical scheme includes that the invoice creation limit of an invoice issuing party is dynamically updated based on credit score of the invoice issuing party, and when a user needs to create an invoice corresponding to the invoice issuing party in a blockchain, the invoice creation limit of the invoice issuing party is checked first, so that the invoice is created when the invoice creation limit of the invoice issuing party is determined to be sufficient.
In particular implementation, when a user needs to create an invoice in a blockchain, an invoice creation request for the invoice can be initiated through a client.
The node devices in the blockchain may respond to the invoice creation request after receiving the invoice creation request.
Typically, invoice presenters have a limited invoice creation limit. In this case, the node device may determine whether the invoice creation limit of the invoice provider corresponding to the invoice creation request is sufficient after receiving the invoice creation request.
If the invoice creator limit of the invoice provider is determined to be sufficient, the node device may invoke invoice creation logic declared in the intelligent contract deployed on the blockchain to create the invoice based on invoice creation information input by the user in the invoice creation request.
After completing the creation of the invoice, the node device may further generate an invoice creation record corresponding to the invoice, and perform credit evaluation on the invoicing party based on the invoice creation record to obtain a credit score of the invoicing party. Wherein the credit score of the invoicing party can be used to determine an invoice creation limit of the invoicing party.
After the new invoice is created every time, the credit evaluation can be carried out again on the invoice issuing party based on the invoice creation record corresponding to the newly created invoice, so that a new credit score of the invoice issuing party is obtained, and the invoice creation limit of the invoice issuing party is determined again based on the new credit score, so that the invoice creation limit of the invoice issuing party can be dynamically updated.
In the above technical solution, when a user needs to create an invoice corresponding to an invoice issuer in a blockchain, an invoice creation amount check may be performed on the invoice issuer first, so that when the invoice creation amount of the invoice issuer is determined to be sufficient, the invoice is created, a corresponding invoice creation record is generated, subsequently, a credit evaluation may be performed on the invoice issuer based on the invoice creation record to obtain a credit score, and the invoice creation amount of the invoice issuer is dynamically updated based on the credit score. Compared with the common manual invoice establishing limit updating mode, the method has the advantages that the invoice establishing limit of the invoice issuing party can be dynamically updated based on the invoice establishing record of the invoice issuing party, so that the updating period of the invoice establishing limit can be shortened, and the correlation degree of the invoice establishing limit and the operation condition of the invoice issuing party is improved.
The present specification is described below by way of specific examples.
Referring to fig. 1, fig. 1 is a flowchart illustrating a block chain based invoice creation method according to an exemplary embodiment of the present specification. The method can be applied to node equipment in a block chain, and comprises the following steps:
102, receiving an invoice creation request initiated by a user through a client; wherein the invoice creation request comprises invoice creation information input by a user;
104, responding to the invoice creation request, and determining whether the invoice creation limit of an invoice issuing party corresponding to the invoice creation request is sufficient;
step 106, if the invoice establishing limit of the invoice issuing party is sufficient, invoking invoice establishing logic declared in a preset intelligent contract, and establishing a target invoice based on the invoice establishing information; and the number of the first and second groups,
step 108, generating an invoice creation record corresponding to the target invoice, and performing credit evaluation on the invoice issuing party based on the invoice creation record to obtain a credit score; the credit score is used for determining the invoice creation limit of the invoice issuing party so as to dynamically update the invoice creation limit of the invoice issuing party.
The block chain described in this specification may specifically include any type of block chain network; for example, in practical applications, any one of a common chain, a private chain, or a federation chain may be employed.
In this embodiment, when the user needs to create an invoice in the blockchain, the user may initiate a transaction for creating the invoice through the client used by the user, that is, initiate an invoice creation request through the client.
The transactions in the blockchain are classified into narrow transactions and broad transactions. A narrowly defined transaction refers to a transfer of value issued by a user to a blockchain; for example, in a conventional bitcoin blockchain network, the transaction may be a transfer initiated by the user in the blockchain. The broad transaction refers to a piece of business data with business intention, which is issued to the blockchain by a user; for example, an operator may build a federation chain based on actual business requirements, relying on the federation chain to deploy some other types of online business unrelated to value transfer (e.g., a rental house business, a vehicle dispatching business, an insurance claim settlement business, a credit service, a medical service, etc.), and in such federation chain, the transaction may be a business message or a business request with a business intent issued by a user in the federation chain.
Specifically, the user may input invoice creation information of a target invoice to be created through an invoice creation page provided by the client, for example: invoice issuing party information, invoice receiving party information, the quota of the target invoice and the like. The information of the invoice issuing party can comprise a taxpayer identification number of the invoice issuing party, and the information of the invoice receiving party can comprise a taxpayer identification number of the invoice receiving party; assuming that the user is the invoice receiver of the target invoice, the invoice receiver information may include the taxpayer identification number of the user.
After the user completes the input of the invoice creation information, the client may generate a corresponding invoice creation request and send the invoice creation request to the node device in the blockchain.
The node devices in the blockchain may respond to the invoice creation request after receiving the invoice creation request.
Specifically, it may be determined whether the invoice creation limit of the invoicing party corresponding to the invoice creation request is sufficient.
For example, the taxpayer identification number of the invoicing party may be obtained from the invoice creation information input by the user in the invoice creation request, and the corresponding invoicing party is determined based on the taxpayer identification number, where the invoicing party is the invoicing party corresponding to the invoice creation request. Subsequently, whether the invoice establishing limit of the invoice issuing party is sufficient or not can be determined firstly.
It should be noted that, in this specification, the initial invoice creation limit of the invoicing party may be determined based on the initial credit score of the invoicing party.
In one embodiment shown, credit check logic declared in the intelligent contract deployed on the blockchain may be invoked by the node device to determine whether the invoice presenters' invoice creation credit is sufficient.
The credit check logic may be program code (for example, some program methods or functions available for calling) declared in the intelligent contract and related to the execution logic for checking the invoice creation credit of the invoice issuing party.
Alternatively, the node device may invoke a trusted service of a third party and send the invoice creation request to the trusted service of the third party. Wherein the trusted service of the third party may be program code associated with execution logic for checking an invoice creation limit of the invoice presenters deployed on the trusted service device of the third party. For example, the trusted service device of the third party may be a device in a tax office network, so that data security may be improved.
The trusted service of the third party may determine whether the invoice establishing limit of the invoicing party is sufficient and return the determination result to the node device. The node device may determine whether the invoice creation limit of the invoice presenters is sufficient based on a determination result returned by the trusted service of the third party.
Specifically, the trusted service of the third party may return a determination result that the invoice creation amount of the invoicing party is sufficient to the node device when determining that the invoice creation amount of the invoicing party is sufficient. The node device may determine that the invoice creation limit of the invoice issuer is sufficient after receiving the determination result. Or, the trusted service of the third party may return a determination result that the invoice creation amount of the invoicing party is insufficient to the node device when determining that the invoice creation amount of the invoicing party is insufficient. The node device may determine that the invoice creation limit of the invoice presenters is insufficient after receiving the determination result.
If the invoice creation limit of the invoice issuing party is determined to be sufficient, invoice creation logic declared in the intelligent contract deployed on the blockchain can be called, and a target invoice is created based on invoice creation information input by the user in the invoice creation request.
The invoice creation logic may be program code declared in the intelligent contract that is associated with the execution logic that creates the invoice.
It should be noted that the invoice creation limit of the invoicing party may be determined based on the credit score of the invoicing party, and the credit score of the invoicing party may be obtained by performing credit evaluation on the invoicing party based on the invoice creation record of the invoicing party.
In practical application, a trusted service of a third party can be called, and the trusted service of the third party performs credit evaluation on the invoicing party based on the invoice creation record of the invoicing party to obtain the credit score of the invoicing party.
The trusted service of the third party may be a machine learning model deployed on a trusted service device of the third party, and the machine learning model may be a machine learning model commonly used for credit evaluation, such as a logistic regression model.
On one hand, a machine learning model for credit evaluation deployed on trusted service equipment of a third party can be called, a pre-stored historical invoice creation record of the invoicing party is used as a training sample, and machine learning training is carried out to obtain an initial credit score of the invoicing party.
For example, a pre-stored historical invoice creation record of the invoicing party may be input into the evaluation system for evaluation, so as to obtain a plurality of indexes for performing credit evaluation on the invoicing party. Subsequently, a prediction sample can be constructed based on the obtained indexes and basic information in the historical invoice creation record, such as invoice issuer information, invoice acceptor information, the invoice amount, payment method, transaction article name, transaction place, transaction time and the like, and the constructed prediction sample is input to the credit evaluation model for credit evaluation, so as to obtain the initial credit score of the invoice issuer.
On the other hand, after the target invoice is created, an invoice creation record corresponding to the target invoice can be further generated, and the credit evaluation is performed on the invoice issuing party based on the invoice creation record, so as to obtain the credit score of the invoice issuing party.
For example, the generated invoice creation record and the pre-stored historical invoice creation record of the invoicing party can be input into the evaluation system for evaluation, and a plurality of indexes for performing credit evaluation on the invoicing party are obtained. Subsequently, a prediction sample can be constructed based on the obtained indexes and the basic information in the invoice creation record, and the constructed prediction sample is input into the credit evaluation model for credit evaluation, so that the updated credit score of the invoice issuer is obtained.
Of course, in addition to the credit assessment of the invoicing party by invoking the trusted service of the third party, in practical applications, the credit assessment of the invoicing party may also be performed by invoking the associated on-chain service.
For example, a relevant machine learning model for credit evaluation may be deployed in the blockchain (e.g., declared as executing logic in a smart contract), and the invoice presenters may be credit evaluated by invoking the machine learning model deployed on the blockchain, without requiring credit evaluation by invoking a trusted service of a third party.
Therefore, after the target invoice is created, the credit evaluation can be performed again on the invoice issuing party based on the invoice creation record corresponding to the target invoice, and the credit score of the invoice issuing party is updated, so that the credit score of the invoice issuing party can be dynamically updated.
In one illustrated embodiment, the trusted service of the third party may return the invoicing party's credit score to the node device. After receiving the credit score of the invoice issuing party returned by the trusted service of the third party, the node device may call a line determination logic declared in an intelligent contract deployed in the block chain, determine an invoice creation line of the invoice issuing party based on the credit score, and dynamically update the invoice creation line of the invoice issuing party for line checking based on the determined invoice creation line.
Wherein the quota determining logic may specifically be program code declared in the intelligent contract that is relevant to the execution logic that determines and updates the invoice establishing quota for the invoice presenters.
For example, the node device may store a correspondence between credit scores and invoice creation limits as shown in table 1 below:
| credit score 1 | Invoice establishing amount 1 |
| Credit score 2 | Invoice establishing amount 2 |
| …… | …… |
TABLE 1
Assuming that the initial value of the credit score of the invoicing party, which is returned by the trusted service of the third party and received by the node device, is the credit score 1, the invoice creation limit of the invoicing party can be determined to be the invoice creation limit 1 according to the corresponding relationship shown in table 1 above. Subsequently, the node apparatus may check whether the invoice creation limit of the invoice presenters is sufficient based on the invoice creation limit 1.
If the invoice creation amount of the invoice issuing party is determined to be sufficient based on the invoice creation amount 1, and therefore the target invoice 1 is created, after the creation of the target invoice 1 is completed, the node device may further generate an invoice creation record corresponding to the target invoice 1, and send the invoice creation record to the trusted service of the third party, so that the trusted service of the third party performs credit evaluation on the invoice issuing party again based on the invoice creation record, obtains a new credit score of the invoice issuing party, and returns the new credit score to the node device.
Assuming that the new credit score of the invoicing party returned by the trusted service of the third party received by the node device is credit score 2, the invoice creation limit of the invoicing party can be determined to be invoice creation limit 2 according to the corresponding relationship shown in table 2 above. Subsequently, the node device updates the invoice creation limit of the invoice presenters for limit checking from invoice creation limit 1 to invoice creation limit 2, that is, the node device may check whether the invoice creation limit of the invoice presenters is sufficient based on invoice creation limit 2.
Or, the node device may also store the correspondence between the credit scoring interval and the invoice creation limit as shown in table 2 below:
| credit score interval 1 | Invoice creation amountDegree 1 |
| Credit score Interval 2 | Invoice establishing amount 2 |
| …… | …… |
TABLE 2
Assuming that the initial value of the credit score of the invoice issuing party returned by the trusted service of the third party received by the node device is credit score 1, the credit score interval (assumed to be credit score interval 1) to which the credit score 1 belongs may be determined, and then the invoice creation limit of the invoice issuing party may be determined to be invoice creation limit 1 according to the corresponding relationship shown in table 2 above. Subsequently, the node apparatus may check whether the invoice creation limit of the invoice presenters is sufficient based on the invoice creation limit 1.
If the invoice creation amount of the invoice issuing party is determined to be sufficient based on the invoice creation amount 1, and therefore the target invoice 1 is created, after the creation of the target invoice 1 is completed, the node device may further generate an invoice creation record corresponding to the target invoice 1, and send the invoice creation record to the trusted service of the third party, so that the trusted service of the third party performs credit evaluation on the invoice issuing party again based on the invoice creation record, obtains a new credit score of the invoice issuing party, and returns the new credit score to the node device.
Assuming that the new credit score of the invoice issuing party returned by the trusted service of the third party received by the node device is credit score 2, the credit score interval (assumed to be credit score interval 2) to which the credit score 2 belongs may be determined, and then the invoice creation limit of the invoice issuing party may be determined to be invoice creation limit 2 according to the corresponding relationship shown in table 2 above. Subsequently, the node device updates the invoice creation limit of the invoice presenters for limit checking from invoice creation limit 1 to invoice creation limit 2, that is, the node device may check whether the invoice creation limit of the invoice presenters is sufficient based on invoice creation limit 2.
It should be noted that the above-described intelligent contract for checking the invoice creation amount of the invoice presenters, the intelligent contract for creating invoices, and the intelligent contract for determining and updating the invoice creation amount of the invoice presenters may be integrated into one intelligent contract to be deployed on the block chain, or may be deployed on the block chain as two different intelligent contracts, which is not limited in this specification.
In one embodiment, the trusted service of the third party may also determine the invoice creation limit of the invoicing party based on the credit score of the invoicing party, and return the determined invoice creation limit of the invoicing party to the node device. After receiving the invoice creation limit of the invoice issuing party returned by the trusted service of the third party, the node device may dynamically update the invoice creation limit of the invoice issuing party based on the received invoice creation limit.
The credit score of the invoice issuing party can be updated after the target invoice is created every time, so that the invoice creation limit of the invoice issuing party can be updated based on the updated credit score, and the invoice creation limit of the invoice issuing party can be dynamically updated.
In the above technical solution, when a user needs to create an invoice corresponding to an invoice issuer in a blockchain, an invoice creation amount check may be performed on the invoice issuer first, so that when the invoice creation amount of the invoice issuer is determined to be sufficient, the invoice is created, a corresponding invoice creation record is generated, subsequently, a credit evaluation may be performed on the invoice issuer based on the invoice creation record to obtain a credit score, and the invoice creation amount of the invoice issuer is dynamically updated based on the credit score. Compared with the common manual invoice establishing limit updating mode, the method has the advantages that the invoice establishing limit of the invoice issuing party can be dynamically updated based on the invoice establishing record of the invoice issuing party, so that the updating period of the invoice establishing limit can be shortened, and the correlation degree of the invoice establishing limit and the operation condition of the invoice issuing party is improved.
Corresponding to the embodiment of the method for creating the block chain-based invoice, the specification also provides an embodiment of a block chain-based invoice creating device.
The embodiment of the block chain-based invoice creation device in the specification can be applied to electronic equipment. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. Taking a software implementation as an example, as a logical device, the device is formed by reading, by a processor of the electronic device where the device is located, a corresponding computer program instruction in the nonvolatile memory into the memory for operation. From a hardware aspect, as shown in fig. 2, a hardware structure diagram of an electronic device where an invoice creating apparatus based on a block chain is located in this specification is shown, except for the processor, the memory, the network interface, and the nonvolatile memory shown in fig. 2, the electronic device where the apparatus is located in the embodiment may also include other hardware according to an actual function of creating the invoice based on the block chain, which is not described again.
Referring to fig. 3, fig. 3 is a block diagram of an invoice creation apparatus based on a blockchain according to an exemplary embodiment of the present disclosure. The apparatus 30 can be applied to the electronic device shown in fig. 2, and includes:
a first receiving module 301, configured to receive an invoice creation request initiated by a user through a client; wherein the invoice creation request comprises invoice creation information input by a user;
a determining module 302, configured to determine, in response to the invoice creation request, whether an invoice creation amount of an invoice issuer corresponding to the invoice creation request is sufficient;
a creating module 303, configured to invoke invoice creating logic declared in a preset intelligent contract if an invoice creating quota of the invoice issuing party is sufficient, and create a target invoice based on the invoice creating information; and the number of the first and second groups,
the evaluation module 304 is used for generating an invoice creation record corresponding to the target invoice, and performing credit evaluation on the invoice issuing party based on the invoice creation record to obtain a credit score; the credit score is used for determining the invoice creation limit of the invoice issuing party so as to dynamically update the invoice creation limit of the invoice issuing party.
In this embodiment, the determining module 302 may specifically be configured to:
calling the limit checking logic declared in the intelligent contract to determine whether the invoice creation limit of the invoice issuing party corresponding to the invoice creation request is sufficient; or,
calling a trusted service of a third party, sending the invoice creation request to the trusted service of the third party, so that the trusted service of the third party determines whether the invoice creation quota of the invoice issuing party corresponding to the invoice creation request is sufficient, and receiving a determination result of whether the invoice creation quota of the invoice issuing party returned by the trusted service of the third party is sufficient.
In this embodiment, the evaluation module 304 may specifically be configured to:
and calling a trusted service of a third party, sending the invoice creation record to the trusted service of the third party, and performing credit evaluation on the invoice issuing party by the trusted service of the third party based on the invoice creation record to obtain a credit score.
In this embodiment, the apparatus 30 may further include:
a second receiving module 305, configured to receive a credit score of the invoicing party returned by the trusted service of the third party;
the first updating module 306 is configured to invoke the quota determining logic declared in the intelligent contract, determine the invoice creation quota of the invoicing party based on the credit score, and dynamically update the invoice creation quota of the invoicing party based on the determined invoice creation quota.
In this embodiment, the apparatus 30 may further include:
a third receiving module 307, configured to receive an invoice creation limit of the invoicing party, which is determined based on a credit score of the invoicing party and returned by the trusted service of the third party;
and the second updating module 308 is configured to dynamically update the invoice creation limit of the invoice issuer based on the received invoice creation limit.
In this embodiment, the trusted service of the third party may include a machine learning model deployed on a trusted service device of the third party.
The implementation process of the functions and actions of each module in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, wherein the modules described as separate parts may or may not be physically separate, and the parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution in the specification. One of ordinary skill in the art can understand and implement it without inventive effort.
The systems, devices, modules or modules illustrated in the above embodiments may be implemented by a computer chip or an entity, or by an article of manufacture with certain functionality. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
Corresponding to the embodiment of the invoice creation method based on the blockchain, the specification further provides an embodiment of an electronic device. The electronic device includes: a processor and a memory for storing machine executable instructions; wherein the processor and the memory are typically interconnected by an internal bus. In other possible implementations, the device may also include an external interface to enable communication with other devices or components.
In this embodiment, the processor is caused to, by reading and executing machine executable instructions stored by the memory corresponding to control logic for blockchain based invoice creation:
receiving an invoice creation request initiated by a user through a client; wherein the invoice creation request comprises invoice creation information input by a user;
in response to the invoice creation request, determining whether an invoice creation quota of an invoice provider corresponding to the invoice creation request is sufficient;
if the invoice creating limit of the invoice issuing party is sufficient, calling invoice creating logic declared in a preset intelligent contract, and creating a target invoice based on the invoice creating information; and the number of the first and second groups,
generating an invoice creation record corresponding to the target invoice, and performing credit evaluation on the invoice issuing party based on the invoice creation record to obtain a credit score; the credit score is used for determining the invoice creation limit of the invoice issuing party so as to dynamically update the invoice creation limit of the invoice issuing party.
In this embodiment, the processor is caused to, by reading and executing machine executable instructions stored by the memory corresponding to control logic for blockchain based invoice creation:
calling the limit checking logic declared in the intelligent contract to determine whether the invoice creation limit of the invoice issuing party corresponding to the invoice creation request is sufficient; or,
calling a trusted service of a third party, sending the invoice creation request to the trusted service of the third party, so that the trusted service of the third party determines whether the invoice creation quota of the invoice issuing party corresponding to the invoice creation request is sufficient, and receiving a determination result of whether the invoice creation quota of the invoice issuing party returned by the trusted service of the third party is sufficient.
In this embodiment, the processor is caused to, by reading and executing machine executable instructions stored by the memory corresponding to control logic for blockchain based invoice creation:
and calling a trusted service of a third party, sending the invoice creation record to the trusted service of the third party, and performing credit evaluation on the invoice issuing party by the trusted service of the third party based on the invoice creation record to obtain a credit score.
In this embodiment, the processor is further caused to, by reading and executing machine executable instructions stored by the memory corresponding to control logic for blockchain based invoice creation:
receiving a credit score of the invoicing party returned by a trusted service of the third party;
calling a limit determination logic declared in the intelligent contract, determining an invoice creation limit of the invoice issuing party based on the credit score, and dynamically updating the invoice creation limit of the invoice issuing party based on the determined invoice creation limit.
The processor is further caused to, by reading and executing machine-executable instructions stored by the memory corresponding to control logic for blockchain-based invoice creation:
receiving an invoice creation limit of the invoicing party determined based on the credit score of the invoicing party returned by the trusted service of the third party;
and dynamically updating the invoice establishing limit of the invoice issuing party based on the received invoice establishing limit.
In this embodiment, the trusted service of the third party may include a machine learning model deployed on a trusted service device of the third party.
Other embodiments of the present disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This specification is intended to cover any variations, uses, or adaptations of the specification following, in general, the principles of the specification and including such departures from the present disclosure as come within known or customary practice within the art to which the specification pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the specification being indicated by the following claims.
It will be understood that the present description is not limited to the precise arrangements described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present description is limited only by the appended claims.
The above description is only for the purpose of illustrating the preferred embodiments of the one or more embodiments of the present disclosure, and is not intended to limit the scope of the one or more embodiments of the present disclosure, and any modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the one or more embodiments of the present disclosure should be included in the scope of the one or more embodiments of the present disclosure.
Claims (13)
1. A blockchain based invoice creation method, the method comprising:
receiving an invoice creation request initiated by a user through a client; wherein the invoice creation request comprises invoice creation information input by a user;
in response to the invoice creation request, determining whether an invoice creation quota of an invoice provider corresponding to the invoice creation request is sufficient;
if the invoice creating limit of the invoice issuing party is sufficient, calling invoice creating logic declared in a preset intelligent contract, and creating a target invoice based on the invoice creating information; and the number of the first and second groups,
generating an invoice creation record corresponding to the target invoice, and performing credit evaluation on the invoice issuing party based on the invoice creation record to obtain a credit score; the credit score is used for determining the invoice creation limit of the invoice issuing party so as to dynamically update the invoice creation limit of the invoice issuing party.
2. The method of claim 1, the determining whether an invoice creation quota of an invoicer corresponding to the invoice creation request is sufficient, comprising:
calling the limit checking logic declared in the intelligent contract to determine whether the invoice creation limit of the invoice issuing party corresponding to the invoice creation request is sufficient; or,
calling a trusted service of a third party, sending the invoice creation request to the trusted service of the third party, so that the trusted service of the third party determines whether the invoice creation quota of the invoice issuing party corresponding to the invoice creation request is sufficient, and receiving a determination result of whether the invoice creation quota of the invoice issuing party returned by the trusted service of the third party is sufficient.
3. The method of claim 1, the assessing credit to the invoicing party based on the invoice creation record resulting in a credit score, comprising:
and calling a trusted service of a third party, sending the invoice creation record to the trusted service of the third party, and performing credit evaluation on the invoice issuing party by the trusted service of the third party based on the invoice creation record to obtain a credit score.
4. The method of claim 3, further comprising:
receiving a credit score of the invoicing party returned by a trusted service of the third party;
calling a limit determination logic declared in the intelligent contract, determining an invoice creation limit of the invoice issuing party based on the credit score, and dynamically updating the invoice creation limit of the invoice issuing party based on the determined invoice creation limit.
5. The method of claim 3, further comprising:
receiving an invoice creation limit of the invoicing party determined based on the credit score of the invoicing party returned by the trusted service of the third party;
and dynamically updating the invoice establishing limit of the invoice issuing party based on the received invoice establishing limit.
6. The method of claim 1, the trusted service of the third party comprising a machine learning model deployed on a trusted service device of the third party.
7. An apparatus for blockchain-based invoice creation, the apparatus comprising:
the first receiving module is used for receiving an invoice creating request initiated by a user through a client; wherein the invoice creation request comprises invoice creation information input by a user;
the determining module is used for responding to the invoice creating request and determining whether the invoice creating limit of the invoice issuing party corresponding to the invoice creating request is sufficient;
the creating module is used for calling invoice creating logic declared in a preset intelligent contract and creating a target invoice based on the invoice creating information if the invoice creating limit of the invoice issuing party is sufficient; and the number of the first and second groups,
the evaluation module is used for generating an invoice creation record corresponding to the target invoice and performing credit evaluation on the invoice issuing party based on the invoice creation record to obtain a credit score; the credit score is used for determining the invoice creation limit of the invoice issuing party so as to dynamically update the invoice creation limit of the invoice issuing party.
8. The apparatus of claim 7, the determination module being specifically configured to:
calling the limit checking logic declared in the intelligent contract to determine whether the invoice creation limit of the invoice issuing party corresponding to the invoice creation request is sufficient; or,
calling a trusted service of a third party, sending the invoice creation request to the trusted service of the third party, so that the trusted service of the third party determines whether the invoice creation quota of the invoice issuing party corresponding to the invoice creation request is sufficient, and receiving a determination result of whether the invoice creation quota of the invoice issuing party returned by the trusted service of the third party is sufficient.
9. The apparatus of claim 7, the evaluation module to be specifically configured to:
and calling a trusted service of a third party, sending the invoice creation record to the trusted service of the third party, and performing credit evaluation on the invoice issuing party by the trusted service of the third party based on the invoice creation record to obtain a credit score.
10. The apparatus of claim 9, the apparatus further comprising:
the second receiving module is used for receiving the credit score of the invoicing party returned by the trusted service of the third party;
and the first updating module is used for calling the quota determining logic declared in the intelligent contract, determining the invoice establishing quota of the invoice issuing party based on the credit score, and dynamically updating the invoice establishing quota of the invoice issuing party based on the determined invoice establishing quota.
11. The apparatus of claim 9, the apparatus further comprising:
the third receiving module is used for receiving the invoice creation limit of the invoicing party, which is determined based on the credit score of the invoicing party and returned by the trusted service of the third party;
and the second updating module is used for dynamically updating the invoice establishing limit of the invoice issuing party based on the received invoice establishing limit.
12. The apparatus of claim 7, the trusted service of the third party comprising a machine learning model deployed on a trusted service device of the third party.
13. An electronic device, the electronic device comprising:
a processor;
a memory for storing machine executable instructions;
wherein, by reading and executing machine-executable instructions stored by the memory corresponding to control logic for blockchain based invoice creation, the processor is caused to:
receiving an invoice creation request initiated by a user through a client; wherein the invoice creation request comprises invoice creation information input by a user;
in response to the invoice creation request, determining whether an invoice creation quota of an invoice provider corresponding to the invoice creation request is sufficient;
if the invoice creating limit of the invoice issuing party is sufficient, calling invoice creating logic declared in a preset intelligent contract, and creating a target invoice based on the invoice creating information; and the number of the first and second groups,
generating an invoice creation record corresponding to the target invoice, and performing credit evaluation on the invoice issuing party based on the invoice creation record to obtain a credit score; the credit score is used for determining the invoice creation limit of the invoice issuing party so as to dynamically update the invoice creation limit of the invoice issuing party.
Priority Applications (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811519702.5A CN109949108A (en) | 2018-12-12 | 2018-12-12 | Invoice creation method and device, electronic equipment based on block chain |
| TW108134194A TWI709934B (en) | 2018-12-12 | 2019-09-23 | Block chain-based invoice creation method and device, and electronic equipment |
| PCT/CN2019/114231 WO2020119303A1 (en) | 2018-12-12 | 2019-10-30 | Blockchain-based invoice creation method and apparatus, and electronic device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811519702.5A CN109949108A (en) | 2018-12-12 | 2018-12-12 | Invoice creation method and device, electronic equipment based on block chain |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN109949108A true CN109949108A (en) | 2019-06-28 |
Family
ID=67006028
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811519702.5A Pending CN109949108A (en) | 2018-12-12 | 2018-12-12 | Invoice creation method and device, electronic equipment based on block chain |
Country Status (3)
| Country | Link |
|---|---|
| CN (1) | CN109949108A (en) |
| TW (1) | TWI709934B (en) |
| WO (1) | WO2020119303A1 (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110443660A (en) * | 2019-08-15 | 2019-11-12 | 上海天地汇供应链科技有限公司 | A kind of electronic invoice device, system and implementation method based on block chain |
| CN110458633A (en) * | 2019-08-20 | 2019-11-15 | 东莞市盟大塑化科技有限公司 | Invoice data generation method, system and computer equipment based on block chain technology |
| WO2020119303A1 (en) * | 2018-12-12 | 2020-06-18 | 阿里巴巴集团控股有限公司 | Blockchain-based invoice creation method and apparatus, and electronic device |
| CN111652663A (en) * | 2020-05-19 | 2020-09-11 | 中穗科技股份有限公司 | Agricultural product invoicing method and system based on block chain technology |
| US10846765B2 (en) | 2019-07-31 | 2020-11-24 | Advanced New Technologies Co., Ltd. | Blockchain-based e-bill number application method, apparatus, and electronic device |
| WO2021017439A1 (en) * | 2019-07-31 | 2021-02-04 | 创新先进技术有限公司 | Block chain-based electronic bill number application method and apparatus, and electronic device |
| WO2021120760A1 (en) * | 2019-12-20 | 2021-06-24 | 中国银联股份有限公司 | Method and device for issuing electronic invoice employing blockchain |
| US11049115B2 (en) | 2019-07-31 | 2021-06-29 | Advanced New Technologies Co., Ltd. | Blockchain-based bill write-off method, apparatus, electronic device, and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104463667A (en) * | 2015-01-07 | 2015-03-25 | 税友软件集团股份有限公司 | Electronic invoice supervision method and system |
| US20180101914A1 (en) * | 2016-10-10 | 2018-04-12 | Escolhalegal, Llc | Systems, methods and machine-readable mediums for data management and payment processing |
| CN108961030A (en) * | 2018-08-15 | 2018-12-07 | 腾讯科技（深圳）有限公司 | About the data processing method of electronic bill, device, system, medium and equipment |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10026082B2 (en) * | 2015-05-21 | 2018-07-17 | Mastercard International Incorporated | Method and system for linkage of blockchain-based assets to fiat currency accounts |
| CN106127578A (en) * | 2016-06-20 | 2016-11-16 | 深圳市淘淘谷信息技术有限公司 | A kind of block chain shows the method for marketable securities circulation |
| US20180165598A1 (en) * | 2016-12-09 | 2018-06-14 | Cognitive Scale, Inc. | Method for Providing Financial-Related, Blockchain-Associated Cognitive Insights Using Blockchains |
| CN108305106A (en) * | 2018-01-31 | 2018-07-20 | 复旦大学 | A kind of electronic invoice register method based on block chain |
| TWM561279U (en) * | 2018-02-12 | 2018-06-01 | 林俊良 | Blockchain system and node server for processing strategy model scripts of financial assets |
| CN108288222A (en) * | 2018-03-05 | 2018-07-17 | 数字乾元科技有限公司 | Property tax processing system and method based on block chain |
| CN108711099A (en) * | 2018-06-07 | 2018-10-26 | 深圳鑫宏图工业设计有限公司 | A kind of financial system management method, electronic equipment and storage medium |
| CN108985773A (en) * | 2018-07-13 | 2018-12-11 | 江苏恒宝智能系统技术有限公司 | A kind of payment accounts method for secure transactions and system based on block chain |
| CN109949108A (en) * | 2018-12-12 | 2019-06-28 | 阿里巴巴集团控股有限公司 | Invoice creation method and device, electronic equipment based on block chain |
-
2018
- 2018-12-12 CN CN201811519702.5A patent/CN109949108A/en active Pending
-
2019
- 2019-09-23 TW TW108134194A patent/TWI709934B/en active
- 2019-10-30 WO PCT/CN2019/114231 patent/WO2020119303A1/en active Application Filing
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104463667A (en) * | 2015-01-07 | 2015-03-25 | 税友软件集团股份有限公司 | Electronic invoice supervision method and system |
| US20180101914A1 (en) * | 2016-10-10 | 2018-04-12 | Escolhalegal, Llc | Systems, methods and machine-readable mediums for data management and payment processing |
| CN108961030A (en) * | 2018-08-15 | 2018-12-07 | 腾讯科技（深圳）有限公司 | About the data processing method of electronic bill, device, system, medium and equipment |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2020119303A1 (en) * | 2018-12-12 | 2020-06-18 | 阿里巴巴集团控股有限公司 | Blockchain-based invoice creation method and apparatus, and electronic device |
| US10846765B2 (en) | 2019-07-31 | 2020-11-24 | Advanced New Technologies Co., Ltd. | Blockchain-based e-bill number application method, apparatus, and electronic device |
| WO2021017439A1 (en) * | 2019-07-31 | 2021-02-04 | 创新先进技术有限公司 | Block chain-based electronic bill number application method and apparatus, and electronic device |
| US11049115B2 (en) | 2019-07-31 | 2021-06-29 | Advanced New Technologies Co., Ltd. | Blockchain-based bill write-off method, apparatus, electronic device, and storage medium |
| US11429983B2 (en) | 2019-07-31 | 2022-08-30 | Advanced New Technologies Co., Ltd. | Blockchain-based bill write-off method, apparatus, electronic device, and storage medium |
| CN110443660A (en) * | 2019-08-15 | 2019-11-12 | 上海天地汇供应链科技有限公司 | A kind of electronic invoice device, system and implementation method based on block chain |
| CN110458633A (en) * | 2019-08-20 | 2019-11-15 | 东莞市盟大塑化科技有限公司 | Invoice data generation method, system and computer equipment based on block chain technology |
| CN110458633B (en) * | 2019-08-20 | 2022-04-01 | 东莞盟大集团有限公司 | Invoice data generation method and system based on block chain technology and computer equipment |
| WO2021120760A1 (en) * | 2019-12-20 | 2021-06-24 | 中国银联股份有限公司 | Method and device for issuing electronic invoice employing blockchain |
| CN111652663A (en) * | 2020-05-19 | 2020-09-11 | 中穗科技股份有限公司 | Agricultural product invoicing method and system based on block chain technology |
| CN111652663B (en) * | 2020-05-19 | 2023-12-29 | 中穗科技股份有限公司 | Agricultural product invoice issuing method and system based on blockchain technology |
Also Published As
| Publication number | Publication date |
|---|---|
| TW202022753A (en) | 2020-06-16 |
| WO2020119303A1 (en) | 2020-06-18 |
| TWI709934B (en) | 2020-11-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109949108A (en) | Invoice creation method and device, electronic equipment based on block chain | |
| CN108389129B (en) | Transaction execution method and device based on block chain and electronic equipment | |
| CN110033244B (en) | Intelligent contract execution method and device based on block chain and electronic equipment | |
| CN108335206B (en) | Asset management method and device and electronic equipment | |
| CN109003078B (en) | Intelligent contract calling method and device based on block chain and electronic equipment | |
| CN110135844B (en) | Credit recording and inquiring method and device based on block chain and electronic equipment | |
| CN110046944A (en) | Invoice creation method and device, electronic equipment based on block chain | |
| US20210049617A1 (en) | Blockchain-based data verification method, apparatus, and electronic device | |
| CN110009489B (en) | Asset transfer method and device based on block chain and electronic equipment | |
| CN110046523B (en) | Intelligent contract checking method and device and electronic equipment | |
| CN110033377B (en) | Asset sorting method and device based on block chain and electronic equipment | |
| CN108416675A (en) | Assets management method and device, electronic equipment | |
| CN110020948B (en) | Asset tracing method and device based on block chain and electronic equipment | |
| US20220036350A1 (en) | Cross-border resource transfer authenticity verification method, device and electronic equipment | |
| CN110020936B (en) | Asset management method and device based on block chain and electronic equipment | |
| CN110046900B (en) | Invoice revocation method and device based on block chain and electronic equipment | |
| CN110060155B (en) | Intelligent contract execution method and device of block chain and electronic equipment | |
| CN110163691B (en) | Invoice creating method and device based on block chain and electronic equipment | |
| CN110163634B (en) | Refund method and device based on blockchain and electronic equipment | |
| CN110347545A (en) | A kind of test method and device of business platform cache policy | |
| CN112330181A (en) | Enterprise credit evaluation method and device based on block chain | |
| CN110009497B (en) | Block chain-based decision method and device and electronic equipment | |
| CN113778878A (en) | Interface testing method and device, electronic equipment and storage medium | |
| CN109345252A (en) | A kind of online trading control method, device and computer equipment | |
| CN112734543A (en) | Accounting processing method and device, computer equipment and storage medium |
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 | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20200924 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20200924 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant after: Advanced innovation technology Co.,Ltd. Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Applicant before: Alibaba Group Holding Ltd. |
|
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20190628 |