WO2020119302A1 - Procédé et appareil de création de facture basée sur une chaîne de blocs et dispositif électronique - Google Patents
Procédé et appareil de création de facture basée sur une chaîne de blocs et dispositif électronique Download PDFInfo
- Publication number
- WO2020119302A1 WO2020119302A1 PCT/CN2019/114222 CN2019114222W WO2020119302A1 WO 2020119302 A1 WO2020119302 A1 WO 2020119302A1 CN 2019114222 W CN2019114222 W CN 2019114222W WO 2020119302 A1 WO2020119302 A1 WO 2020119302A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- invoice
- creation
- issuer
- invoice creation
- quota
- 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.)
- Ceased
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
Definitions
- One or more embodiments of this specification relate to the technical field of terminals, and in particular, to a blockchain-based invoice creation method and device, and electronic equipment.
- Blockchain technology also known as distributed ledger technology, is an emerging technology in which several computing devices jointly participate in "bookkeeping" and jointly maintain a complete distributed database. Because blockchain technology is decentralized, open and transparent, each computing device can participate in database records, and data synchronization can be quickly performed between computing devices, using blockchain technology to build a decentralized system, and Various execution programs are included in the distributed database of the blockchain for automatic execution, which has been widely used in many fields.
- This specification provides a blockchain-based invoice creation method.
- the method includes:
- the invoice creation quota In response to the invoice creation request, determining whether the invoice creation quota corresponding to the invoice creation request is sufficient; wherein, the invoice creation quota is based on a credit evaluation of the invoice creation record of the invoice creation party The credit score of the invoice issuer is determined;
- the invoice creation logic declared in the preset smart contract is called to create a target invoice based on the invoice creation information.
- the determining whether the invoice creation quota of the invoice issuer corresponding to the invoice creation request is sufficient includes:
- performing a credit evaluation on the invoice creation record of the invoice issuer to obtain the credit score of the invoice issuer includes:
- the method further includes:
- the method further includes:
- the method further includes:
- the invoice creation quota of the issuer is dynamically updated.
- the trusted service of the third party includes a machine learning model deployed on the trusted service device of the third party.
- This specification also provides a blockchain-based invoice creation device, which includes:
- a first receiving module configured to receive an invoice creation request initiated by a user through a client; wherein the invoice creation request includes invoice creation information input by the user;
- a first determining module configured to determine whether the invoice creation quota of the invoice issuer corresponding to the invoice creation request is sufficient in response to the invoice creation request; wherein the invoice creation quota is based on the invoice for the invoice issuer Create a record and make a credit evaluation to determine the credit score of the invoice issuer;
- the creation module is used to call the invoice creation logic stated in the preset smart contract if the invoice creation quota of the invoice issuer is sufficient to create a target invoice based on the invoice creation information.
- the first determining module is specifically used to:
- the first determining module is specifically used to:
- the device further includes:
- a second receiving module configured to receive the credit score of the invoice issuer returned by the trusted service of the third party
- the second determination module is configured to call the amount determination logic declared in the smart contract to determine the invoice creation amount of the invoice issuer based on the credit score.
- the device further includes:
- the third receiving module is configured to receive the invoice creation quota of the invoice issuer determined based on the credit score of the invoice issuer returned by the trusted service of the third party.
- the device further includes:
- the evaluation module is configured to generate an invoice creation record corresponding to the target invoice after creating the target invoice, and perform a credit evaluation on the invoice issuer based on the invoice creation record to obtain a credit score, based on the credit The score dynamically updates the invoice creation quota of the invoice issuer.
- the trusted service of the third party includes a machine learning model deployed on the trusted service device of the third party.
- This specification also provides an electronic device, the electronic device includes:
- Memory for storing machine executable instructions
- the invoice creation quota In response to the invoice creation request, determining whether the invoice creation quota corresponding to the invoice creation request is sufficient; wherein, the invoice creation quota is based on a credit evaluation of the invoice creation record of the invoice creation party The credit score of the invoice issuer is determined;
- the invoice creation logic declared in the preset smart contract is called to create a target invoice based on the invoice creation information.
- the invoice issuer may be first checked for the invoice creation quota to confirm that the invoice issuer's invoice creation quota is sufficient , Create the invoice.
- users can create invoices in the blockchain on their own, instead of manually invoicing by the invoice issuer; on the other hand, compared with the commonly used method of manually setting the invoice creation quota, since it can be based on
- the invoice creation record of the invoice issuer determines the invoice creation quota of the invoice issuer, so it can save human resources and also improve the accuracy of the invoice creation quota.
- FIG. 1 is a flowchart of a blockchain-based invoice creation method shown in an exemplary embodiment of this specification
- FIG. 2 is a hardware structure diagram of an electronic device where an invoice creation device based on a blockchain is shown according to an exemplary embodiment of this specification;
- Fig. 3 is a block diagram of a blockchain-based invoice creation device shown in an exemplary embodiment of this specification.
- first, second, third, etc. may be used to describe various information in this specification, the information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
- first information may also be referred to as second information, and similarly, the second information may also be referred to as first information.
- word “if” as used herein may be interpreted as "when” or “when” or “in response to a determination”.
- the purpose of this manual is to provide a way to dynamically update the invoice creation quota based on the invoice issuer’s credit score, and when the user needs to create an invoice corresponding to the invoice issuer in the blockchain, the invoice issuer will first Perform an invoice creation quota check to create a technical solution for the invoice when it is determined that the invoice creation party’s invoice creation quota is sufficient.
- the client when a user needs to create an invoice in the blockchain, the client can initiate an invoice creation request for the invoice through the client.
- the node device in the blockchain After receiving the invoice creation request, the node device in the blockchain can respond to the invoice creation request.
- the invoice creation quota of the invoice issuer is limited.
- the node device may first determine whether the invoice creation quota of the invoice issuer corresponding to the invoice creation request is sufficient.
- the node device can call the invoice creation logic declared in the smart contract deployed on the blockchain to create the invoice based on the invoice creation information entered by the user in the invoice creation request .
- the node device may further generate an invoice creation record corresponding to the invoice, and perform a credit evaluation on the invoice issuer based on the invoice creation record to obtain the credit score of the invoice issuer.
- the credit score of the invoice issuer can be used to determine the invoice creation quota of the invoice issuer.
- the invoice issuer can be re-assessed for credit based on the invoice creation record corresponding to the newly created invoice, and the new credit score of the invoice issuer can be obtained and based on the new The credit score is used to re-determine the invoice creation quota of the invoice issuer, so the invoice creation quota of the invoice issuer can be dynamically updated.
- the invoice issuer may be first checked for the invoice creation quota to confirm that the invoice issuer's invoice creation quota is sufficient , Create the invoice.
- users can create invoices in the blockchain on their own, instead of manually invoicing by the invoice issuer; on the other hand, compared with the commonly used method of manually setting the invoice creation quota, since it can be based on
- the invoice creation record of the invoice issuer determines the invoice creation quota of the invoice issuer, so it can save human resources and also improve the accuracy of the invoice creation quota.
- FIG. 1 is a flowchart of a blockchain-based invoice creation method shown in an exemplary embodiment of this specification. This method can be applied to node devices in the blockchain, including the following steps:
- Step 102 Receive an invoice creation request initiated by a user through a client; wherein the invoice creation request includes invoice creation information input by the user;
- Step 104 In response to the invoice creation request, determine whether the invoice creation quota corresponding to the invoice creation request is sufficient; wherein, the invoice creation quota is credited based on the invoice creation record for the invoice issuing party The credit score of the invoice issuer obtained through evaluation is determined;
- Step 106 If the invoice creation quota of the invoice issuer is sufficient, then call the invoice creation logic declared in the preset smart contract to create a target invoice based on the invoice creation information.
- the blockchain described in this specification may specifically include any type of blockchain network; for example, in practical applications, any one of a public chain, a private chain, or an alliance chain may be used.
- the user when a user needs to create an invoice in the blockchain, the user can initiate a transaction for creating an invoice through the client used by the user, that is, an invoice creation request is initiated through the client.
- the narrow sense of the transaction refers to a value transfer issued by the user to the blockchain; for example, in the traditional Bitcoin blockchain network, the transaction can be a transfer initiated by the user in the blockchain.
- the generalized transaction refers to a piece of business data with business intent published by the user to the blockchain; for example, the operator can build an alliance chain based on actual business needs, relying on the alliance chain to deploy some other types that have nothing to do with value transfer Online business (for example, rental business, vehicle scheduling business, insurance claims business, credit service, medical service, etc.), and in this type of alliance chain, the transaction can be a business with business intent issued by the user in the alliance chain Message or business request.
- the user can enter the invoice creation information of the target invoice to be created through the invoice creation page provided by the client, for example: invoice issuer information, invoice recipient information, and the target invoice amount, etc.
- the invoice issuer information can include the invoice issuer’s taxpayer identification number
- the invoice receiver’s information can include the invoice recipient’s taxpayer identification number; if the user is the invoice recipient of the target invoice, the invoice recipient information The user's taxpayer identification number can be included.
- the client can generate the corresponding invoice creation request and send the invoice creation request to the node device in the blockchain.
- the node device in the blockchain After receiving the invoice creation request, the node device in the blockchain can respond to the invoice creation request.
- the invoice creation quota of the invoice issuer corresponding to the invoice creation request may be determined whether the invoice creation quota of the invoice issuer corresponding to the invoice creation request is sufficient.
- the taxpayer identification number of the invoice issuer is The invoice issuer corresponding to the invoice creation request. Subsequently, you can first determine whether the invoice creation quota of the invoice issuer is sufficient.
- the initial invoice creation quota of the invoice issuer may be determined based on the initial credit score of the invoice issuer.
- the node device may call the amount check logic declared in the smart contract deployed on the blockchain to determine whether the invoice creation amount of the invoice issuer is sufficient.
- the quota check logic may specifically be the program code (for example, some program methods or functions that can be called) that is declared in the smart contract and is related to the execution logic for checking the invoice creation quota of the invoice issuer.
- the node device may call a third-party trusted service and send the invoice creation request to the third-party trusted service.
- the third-party trusted service may be a program code that is deployed on the third-party trusted service device and is related to the execution logic of checking the invoice creation quota of the invoice issuer.
- the trusted service device of the third party may be a device in the intranet of the tax bureau, thereby improving data security.
- the trusted service of the third party can determine whether the invoice creation quota of the invoice issuer is sufficient, and return the determination result to the node device.
- the node device may determine whether the invoice creation quota of the invoice issuer is sufficient based on the determination result returned by the trusted service of the third party.
- the trusted service of the third party determines that the invoice issuer's invoice creation quota is sufficient, it returns the determination result that the invoice issuer's invoice creation quota is sufficient to the node device. After receiving the determination result, the node device may determine that the invoice creation party's invoice creation quota is sufficient. Alternatively, the trusted service of the third party may return the determination result that the invoice creation quota of the invoice issuer is insufficient when determining that the invoice creation quota of the invoice issuer is insufficient. After receiving the determination result, the node device may determine that the invoice creation quota of the invoice issuer is insufficient.
- the invoice creation logic declared in the smart contract deployed on the blockchain can be called to create the target invoice based on the invoice creation information entered by the user in the invoice creation request.
- invoice creation logic may specifically be the program code related to the execution logic for creating an invoice, which is declared in the smart contract.
- invoice creation quota of the invoice issuer may be determined based on the invoice issuer’s credit score, and the invoice issuer’s credit score may be based on the invoice issuer’s invoice creation record for the invoice issuer. Obtained by credit evaluation.
- a trusted service of a third party can be invoked, and the trusted service of the third party performs credit evaluation on the invoice issuer based on the invoice creation record of the invoice issuer, and obtains the credit score of the invoice issuer.
- the trusted service of the third party may be a machine learning model deployed on the 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.
- the pre-stored historical invoice creation record of the invoice issuer can be input into the evaluation system for evaluation, and a number of indicators for credit evaluation of the invoice issuer can be obtained.
- an invoice creation record corresponding to the target invoice can be further generated, and a credit evaluation of the invoice issuer can be performed based on the invoice creation record to obtain the credit score of the invoice issuer .
- the generated invoice creation record and the pre-stored historical invoice creation record of the invoice issuer can be input into the evaluation system for evaluation, and several indicators for credit evaluation of the invoice issuer can be obtained. Subsequently, a forecast sample can be constructed based on the obtained indicators and basic information in the invoice creation record, and the constructed forecast sample can be input into the credit evaluation model for credit evaluation to obtain the updated credit score of the invoice issuer.
- the relevant machine learning model for credit evaluation can be deployed in the blockchain (for example, as an execution logic declared in a smart contract), and then by calling the machine learning model deployed on the blockchain, the The invoice issuer conducts a credit evaluation, instead of calling a third-party trusted service to perform a credit evaluation on the invoice issuer.
- the credit invoice can be reassessed based on the invoice creation record corresponding to the target invoice, and the credit score of the invoice issuer can be updated.
- the credit score of the issuer can be updated dynamically.
- the trusted service of the third party may return the credit score of the invoice issuer to the node device.
- the node device may call the amount determination logic declared in the smart contract deployed in the blockchain to determine the invoice based on the credit score The invoice creation quota of the issuer, and dynamically update the invoice creation quota of the invoice issuer for quota checking based on the determined invoice creation quota.
- the quota determination logic may specifically be a program code declared in the smart contract and related to the execution logic for determining and updating the invoice creation quota of the invoice issuer.
- the node device may store the correspondence between the credit score and the invoice creation quota as shown in Table 1 below:
- the invoice issuer’s invoice can be determined according to the correspondence shown in Table 1 above
- the creation quota is the invoice creation quota 1.
- the node device may check whether the invoice creation quota of the invoice issuer is sufficient based on the invoice creation quota 1.
- the node device can further generate an invoice creation corresponding to the target invoice 1 Record and send the invoice creation record to the trusted service of the third party, so that the trusted service of the third party re-assess the credit of the invoice issuer based on the invoice creation record, and obtain a new Credit score and return to the node device.
- the invoice creation of the invoice issuer can be determined according to the correspondence shown in Table 2 above
- the quota is the invoice creation quota 2.
- the node device updates the invoice creation quota of the invoice issuer used for quota checking from the invoice creation quota 1 to the invoice creation quota 2, that is, the node device can check the invoice creation quota of the invoice issuer based on the invoice creation quota 2 Is it sufficient?
- the node device may also store the correspondence between the credit score interval and the invoice creation quota as shown in Table 2 below:
- the node device may check whether the invoice creation quota of the invoice issuer is sufficient based on the invoice creation quota 1.
- the node device can further generate an invoice creation corresponding to the target invoice 1 Record and send the invoice creation record to the trusted service of the third party, so that the trusted service of the third party re-assess the credit of the invoice issuer based on the invoice creation record, and obtain a new Credit score and return to the node device.
- the new credit score of the invoice issuer returned by the third-party trusted service received by the node device is credit score 2
- the invoice creation quota of the invoice issuer can be determined as the invoice creation quota 2.
- the node device updates the invoice creation quota of the invoice issuer used for quota checking from the invoice creation quota 1 to the invoice creation quota 2, that is, the node device can check the invoice creation quota of the invoice issuer based on the invoice creation quota 2 Is it sufficient?
- the smart contract used to check the invoice creation quota of the invoice issuer described above, the smart contract used to create the invoice, and the smart contract used to determine and update the invoice creation quota of the invoice issuer can be integrated into one
- the smart contract is deployed on the above-mentioned blockchain, and can also be deployed on the blockchain as two different smart contracts, which is not limited in this specification.
- the trusted service of the third party may also determine the invoice creation quota of the invoice issuing party based on the invoice issuing party’s credit score, and create the determined invoice issuing party’s invoice creation amount
- the quota is returned to the node device.
- the node device may dynamically update the invoice creation quota of the invoice issuer based on the received invoice creation quota.
- the credit score of the invoice issuer can be updated, so that the invoice issuer’s invoice creation limit can be updated based on the updated credit score, so the invoice issuer’s invoice
- the creation quota can be updated dynamically.
- the invoice issuer may be first checked for the invoice creation quota to confirm that the invoice issuer's invoice creation quota is sufficient , Create the invoice.
- users can create invoices in the blockchain themselves, and no longer need manual invoicing by the invoice issuer; on the other hand, compared with the commonly used method of manually setting the invoice creation quota, because The invoice creation record of the invoice issuer determines the invoice creation quota of the invoice issuer, so it can save human resources and also improve the accuracy of the invoice creation quota.
- this specification also provides an embodiment of the blockchain-based invoice creation device.
- the embodiment of the blockchain-based invoice creation device in this specification can be applied to electronic devices.
- the device embodiments may be implemented by software, or by hardware or a combination of hardware and software.
- software implementation as an example, as a logical device, it is formed by reading the corresponding computer program instructions in the non-volatile memory into the memory through the processor of the electronic device where it is located.
- this is a hardware structure diagram of the electronic equipment where the blockchain-based invoice creation device is located, except for the processor, memory, network interface, and non-easy
- the electronic device where the device is located in the embodiment usually creates the actual function based on the blockchain-based invoice, and may also include other hardware, which will not be repeated here.
- FIG. 3 is a block diagram of a blockchain-based invoice creation device shown in an exemplary embodiment of this specification.
- the device 30 can be applied to the electronic device shown in FIG. 2 and includes:
- the first receiving module 301 is configured to receive an invoice creation request initiated by a user through a client; wherein the invoice creation request includes invoice creation information input by the user;
- the first determination module 302 is configured to determine whether the invoice creation quota of the invoice issuer corresponding to the invoice creation request is sufficient in response to the invoice creation request; wherein the invoice creation quota is based on the The credit score of the invoice issuer obtained from the credit evaluation of the invoice creation record is determined;
- the creation module 303 is configured to call the invoice creation logic declared in the preset smart contract and create a target invoice based on the invoice creation information if the invoice creation quota of the invoice issuer is sufficient.
- the first determining module 302 may be specifically used to:
- the first determining module 302 may be specifically used to:
- the device 30 may further include:
- a second receiving module 304 configured to receive the credit score of the invoice issuer returned by the trusted service of the third party
- the second determination module 305 is configured to call the amount determination logic declared in the smart contract to determine the invoice creation amount of the invoice issuer based on the credit score.
- the device 30 may further include:
- the third receiving module 306 is configured to receive the invoice creation quota of the invoice issuer determined based on the credit score of the invoice issuer and returned by the trusted service of the third party.
- the device 30 may further include:
- the evaluation module 307 is configured to generate an invoice creation record corresponding to the target invoice after creating the target invoice, and perform a credit evaluation on the invoice issuer based on the invoice creation record to obtain a credit score, based on the The credit score dynamically updates the invoice creation quota of the invoice issuer.
- the trusted service of the third party may include a machine learning model deployed on the trusted service device of the third party.
- the relevant parts can be referred to the description of the method embodiments.
- the device embodiments described above are only schematic, wherein the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, may be located in one place, or It can also be distributed to multiple network modules. Some or all of the modules can be selected according to actual needs to achieve the objectives of the solution in this specification. Those of ordinary skill in the art can understand and implement without paying creative labor.
- the system, device, module or module explained in the above embodiments may be implemented by a computer chip or entity, or by a product with a certain function.
- a typical implementation device is a computer, and the specific form of the computer may be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email sending and receiving device, and a game control Desk, tablet computer, wearable device, or any combination of these devices.
- the electronic device includes: a processor and a memory for storing machine-executable instructions; wherein the processor and the memory are usually connected to each other through an internal bus.
- the device may also include an external interface to be able to communicate with other devices or components.
- the invoice creation quota In response to the invoice creation request, determining whether the invoice creation quota corresponding to the invoice creation request is sufficient; wherein, the invoice creation quota is based on a credit evaluation of the invoice creation record of the invoice creation party The credit score of the invoice issuer is determined;
- the invoice creation logic declared in the preset smart contract is called to create a target invoice based on the invoice creation information.
- the processor is also prompted to:
- the processor is also prompted to:
- the processor is also prompted to:
- the invoice creation quota of the issuer is dynamically updated.
- the trusted service of the third party may include a machine learning model deployed on the trusted service device of the third party.
Landscapes
- Business, Economics & Management (AREA)
- Development Economics (AREA)
- Accounting & Taxation (AREA)
- Engineering & Computer Science (AREA)
- Finance (AREA)
- Strategic Management (AREA)
- Marketing (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Economics (AREA)
- Theoretical Computer Science (AREA)
- Technology Law (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
L'invention concerne un procédé et un appareil de création de facture basée sur une chaîne de blocs et un dispositif électronique, le procédé consistant à : recevoir une demande de création de facture initiée par un utilisateur au moyen d'un terminal client, la demande de création de facture comprenant des informations de création de facture entrées par l'utilisateur (102) ; en réponse à la demande de création de facture, déterminer si le crédit de création de facture d'une partie émettrice de facture correspondant à la demande de création de facture est suffisant, le crédit de création de facture étant déterminé sur la base d'un score de crédit de la partie émettrice de reçu obtenu en effectuant une évaluation de crédit sur les enregistrements de création de facture de la partie émettrice de facture (104) ; si le crédit de création de facture de la partie émettrice de facture est suffisant, invoquer alors une logique de création de facture établie dans un contrat intelligent prédéfini et, sur la base des informations de création de facture, créer une facture cible (106).
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811519689.3 | 2018-12-12 | ||
| CN201811519689.3A CN110046944A (zh) | 2018-12-12 | 2018-12-12 | 基于区块链的发票创建方法和装置、电子设备 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2020119302A1 true WO2020119302A1 (fr) | 2020-06-18 |
Family
ID=67273660
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2019/114222 Ceased WO2020119302A1 (fr) | 2018-12-12 | 2019-10-30 | Procédé et appareil de création de facture basée sur une chaîne de blocs et dispositif électronique |
Country Status (3)
| Country | Link |
|---|---|
| CN (1) | CN110046944A (fr) |
| TW (1) | TW202022752A (fr) |
| WO (1) | WO2020119302A1 (fr) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110046944A (zh) * | 2018-12-12 | 2019-07-23 | 阿里巴巴集团控股有限公司 | 基于区块链的发票创建方法和装置、电子设备 |
| US10846765B2 (en) | 2019-07-31 | 2020-11-24 | Advanced New Technologies Co., Ltd. | Blockchain-based e-bill number application method, 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 |
| CN110473030B (zh) * | 2019-07-31 | 2021-03-23 | 创新先进技术有限公司 | 基于区块链的电子票据号码申领方法及装置、电子设备 |
| CN110458633B (zh) * | 2019-08-20 | 2022-04-01 | 东莞盟大集团有限公司 | 基于区块链技术的发票数据生成方法、系统和计算机设备 |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150081522A1 (en) * | 2013-08-01 | 2015-03-19 | Fundbox, Ltd. | System and method for automatically providing a/r-based lines of credit to businesses |
| CN108305106A (zh) * | 2018-01-31 | 2018-07-20 | 复旦大学 | 一种基于区块链的电子发票登记方法 |
| CN108961030A (zh) * | 2018-08-15 | 2018-12-07 | 腾讯科技(深圳)有限公司 | 关于电子票据的数据处理方法、装置、系统、介质和设备 |
| CN110046944A (zh) * | 2018-12-12 | 2019-07-23 | 阿里巴巴集团控股有限公司 | 基于区块链的发票创建方法和装置、电子设备 |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104463667A (zh) * | 2015-01-07 | 2015-03-25 | 税友软件集团股份有限公司 | 一种电子发票监管方法及系统 |
| WO2018071433A1 (fr) * | 2016-10-10 | 2018-04-19 | Escolhalegal, Llc | Systèmes, procédés et supports lisibles par machine pour la gestion de données et le traitement de paiement |
-
2018
- 2018-12-12 CN CN201811519689.3A patent/CN110046944A/zh active Pending
-
2019
- 2019-09-20 TW TW108134041A patent/TW202022752A/zh unknown
- 2019-10-30 WO PCT/CN2019/114222 patent/WO2020119302A1/fr not_active Ceased
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150081522A1 (en) * | 2013-08-01 | 2015-03-19 | Fundbox, Ltd. | System and method for automatically providing a/r-based lines of credit to businesses |
| CN108305106A (zh) * | 2018-01-31 | 2018-07-20 | 复旦大学 | 一种基于区块链的电子发票登记方法 |
| CN108961030A (zh) * | 2018-08-15 | 2018-12-07 | 腾讯科技(深圳)有限公司 | 关于电子票据的数据处理方法、装置、系统、介质和设备 |
| CN110046944A (zh) * | 2018-12-12 | 2019-07-23 | 阿里巴巴集团控股有限公司 | 基于区块链的发票创建方法和装置、电子设备 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110046944A (zh) | 2019-07-23 |
| TW202022752A (zh) | 2020-06-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2020119303A1 (fr) | Procédé et appareil de création de facture basés sur une chaîne de blocs et dispositif électronique | |
| WO2020119302A1 (fr) | Procédé et appareil de création de facture basée sur une chaîne de blocs et dispositif électronique | |
| US12475476B2 (en) | Closed-loop environment for efficient, accurate, and secure transaction processing | |
| EP3905178A1 (fr) | Procédé et appareil d'attribution de ressources basés sur une chaîne de blocs, et dispositif électronique | |
| US11102003B2 (en) | Ledger-independent token service | |
| TW202022857A (zh) | 基於區塊鏈的發票創建方法及裝置、電子設備 | |
| TWI734217B (zh) | 基於區塊鏈的發票沖紅方法及裝置和電子設備 | |
| TWI717660B (zh) | 資金流動報表生成方法及裝置和電子設備 | |
| WO2020119286A1 (fr) | Procédé et appareil de création de facture fondée sur une chaîne de blocs et dispositif électronique | |
| EP3905172B1 (fr) | Procédé et appareil d'annulation de facture fondés sur une chaîne de blocs et dispositif électronique | |
| CA3015566C (fr) | Systemes et methodes d'acceleration de traitement de donnees fonde sur une regle | |
| CN110033377A (zh) | 基于区块链的资产清分方法及装置、电子设备 | |
| US11222026B1 (en) | Platform for staging transactions | |
| WO2019033741A1 (fr) | Procédé, dispositif, support d'informations et appareil informatique de traitement de ressource de produit d'investissement | |
| CN119213732A (zh) | 针对基于网络的交换的网络级用户验证 | |
| US10810556B2 (en) | Systems and methods for managing receipts for payment account transactions | |
| CN119213731A (zh) | 针对基于网络的交换的网络级政策验证 | |
| US12493671B1 (en) | Systems and methods for a subscribable information locker | |
| US20230244859A1 (en) | System and method for automatically sharing verified user information across remote systems | |
| HK40121754A (zh) | 针对基於网络的交换的网络级政策验证 | |
| HK40121754B (zh) | 针对基於网络的交换的网络级政策验证 | |
| HK40121755A (zh) | 针对基於网络的交换的网络级用户验证 | |
| HK40121010B (zh) | 用於管理网络启用的安全码的系统、方法和计算平台 | |
| HK40121010A (zh) | 用於管理网络启用的安全码的系统、方法和计算平台 | |
| HK40011372B (zh) | 基於区块链的发票作废方法和装置、电子设备 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 19896714 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 19896714 Country of ref document: EP Kind code of ref document: A1 |