CN115018569A - Invoice issuing method, invoice reimbursement device and equipment based on block chain - Google Patents

Invoice issuing method, invoice reimbursement device and equipment based on block chain Download PDF

Info

Publication number
CN115018569A
CN115018569A CN202210593658.2A CN202210593658A CN115018569A CN 115018569 A CN115018569 A CN 115018569A CN 202210593658 A CN202210593658 A CN 202210593658A CN 115018569 A CN115018569 A CN 115018569A
Authority
CN
China
Prior art keywords
invoice
information
terminal
invoice information
reimbursement
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
Application number
CN202210593658.2A
Other languages
Chinese (zh)
Inventor
张�诚
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Bank of China Ltd
Original Assignee
Bank of China Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Bank of China Ltd filed Critical Bank of China Ltd
Priority to CN202210593658.2A priority Critical patent/CN115018569A/en
Publication of CN115018569A publication Critical patent/CN115018569A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/04—Billing or invoicing
    • 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
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063—Operations research, analysis or management
    • G06Q10/0635—Risk analysis of enterprise or organisation activities
    • 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
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/103—Workflow collaboration or project management
    • 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
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/12—Accounting
    • G06Q40/125—Finance or payroll
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06V—IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
    • G06V30/00—Character recognition; Recognising digital ink; Document-oriented image-based pattern recognition
    • G06V30/40—Document-oriented image-based pattern recognition
    • G06V30/41—Analysis of document content
    • G06V30/412—Layout analysis of documents structured with printed lines or input boxes, e.g. business forms or tables
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06V—IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
    • G06V30/00—Character recognition; Recognising digital ink; Document-oriented image-based pattern recognition
    • G06V30/40—Document-oriented image-based pattern recognition
    • G06V30/41—Analysis of document content
    • G06V30/416—Extracting the logical structure, e.g. chapters, sections or page numbers; Identifying elements of the document, e.g. authors

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Economics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • General Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Marketing (AREA)
  • Development Economics (AREA)
  • Computer Vision & Pattern Recognition (AREA)
  • Artificial Intelligence (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Multimedia (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Game Theory and Decision Science (AREA)
  • Educational Administration (AREA)
  • Technology Law (AREA)
  • Data Mining & Analysis (AREA)

Abstract

The embodiment of the specification discloses an invoice issuing method, an invoice reimbursement device and equipment based on a block chain. The method comprises the following steps: receiving billing information sent by a first terminal; verifying the authenticity of the billing information to obtain a verification result; if the checking result is passed, generating corresponding invoice information according to the invoicing information; storing the invoice information on a blockchain; and sending invoice information to the second terminal. The embodiment of the specification can check in the issuing and reimbursement process of the invoice, and error generation is reduced.

Description

Invoice issuing method, invoice reimbursement device and equipment based on block chain
Technical Field
The embodiment of the specification relates to the technical field of block chains, in particular to an invoice issuing method, an invoice reimbursement device and equipment based on the block chains.
Background
Invoices are business certificates issued and reimbursed in the purchase and sale of goods, the provision or receipt of services and other business activities undertaken. Invoices are frequently used in modern industrial, commercial and everyday economic activities.
Errors are easy to occur in the process of issuing and reimbursing invoices, and inconvenience is brought to the use of the invoices.
Disclosure of Invention
The embodiment of the specification provides an invoice issuing method, an invoice reimbursement device and invoice reimbursement equipment based on a block chain, so that verification is performed in the invoice issuing and reimbursement process, and errors are reduced. The technical scheme of the embodiment of the specification is as follows.
In a first aspect of embodiments of the present specification, there is provided a block chain-based invoicing method, including:
receiving billing information sent by a first terminal;
verifying the authenticity of the billing information to obtain a verification result;
if the checking result is passed, generating corresponding invoice information according to the invoicing information;
storing the invoice information on a blockchain;
and sending invoice information to the second terminal.
In a second aspect of the embodiments of the present specification, there is provided a method for invoice reimbursement based on a blockchain, including:
receiving invoice information sent by a terminal;
verifying the validity of the invoice information to obtain a verification result;
if the verification result is passed, the invoice information is subjected to reimbursement processing;
storing the reimbursement processing result on the blockchain;
and sending the reimbursement processing result to the terminal.
In a third aspect of embodiments of the present specification, there is provided a block chain-based invoicing apparatus, including:
the receiving unit is used for receiving the billing information sent by the first terminal;
the checking unit is used for checking the authenticity of the billing information to obtain a checking result;
the generating unit is used for generating corresponding invoice information according to the invoicing information if the verification result is that the invoice passes;
the storage unit is used for storing the invoice information on the block chain;
and the sending unit is used for sending the invoice information to the second terminal.
In a fourth aspect of embodiments of the present specification, there is provided a block chain-based invoice reimbursement apparatus, including:
the receiving unit is used for receiving invoice information sent by the terminal;
the checking unit is used for checking the validity of the invoice information to obtain a checking result;
the reimbursement unit is used for reimbursing the invoice information if the verification result is passed;
a storage unit for storing the reimbursement processing result on the block chain;
and the sending unit is used for sending the reimbursement processing result to the terminal.
In a fifth aspect of embodiments of the present specification, there is provided a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the method steps according to the first or second aspect when executing the computer program.
A sixth aspect of embodiments of the present specification provides a computer program product comprising a computer program which, when executed by a processor, performs the method steps of the first or second aspect.
According to the technical scheme provided by the embodiment of the specification, the authenticity of the invoice information can be verified in the invoice issuing process, so that the generation of errors is reduced. In addition, in the process of reimbursement of the invoice, the validity of the invoice information can be checked. The terminal does not need to actively inquire the validity of the invoice information in the invoice verification website, so that the reimbursement process of the invoice is simplified.
Drawings
In order to more clearly illustrate the embodiments of the present specification or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below, the drawings in the following description are only some embodiments described in the present specification, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a block diagram of a data processing system according to an embodiment of the present disclosure;
FIG. 2 is a flow chart illustrating a block chain based invoicing method in an embodiment of the present disclosure;
FIG. 3 is a flowchart illustrating a method for processing data based on a blockchain according to an embodiment of the present disclosure;
FIG. 4 is a flow chart illustrating a block chain based invoice reimbursement method in an embodiment of the present description;
FIG. 5 is a schematic structural diagram of a block chain-based invoicing apparatus in an embodiment of the present disclosure;
FIG. 6 is a schematic structural diagram of a block chain-based invoice reimbursement device in an embodiment of the present specification;
fig. 7 is a schematic structural diagram of a computer device in an embodiment of the present specification.
Detailed Description
The technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all of the embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments in the present specification without any inventive step should fall within the scope of protection of the present specification.
In the related art, in an invoicing scenario, a drawer provides billing information to a merchant. The merchant issues an invoice by accessing a server set by a government agency according to the invoice issuing information provided by the invoicer. The invoice issuing process is relatively independent, the authenticity of the invoice issuing information cannot be verified, and the situation that the invoice issuing information is wrong and further the invoice issuing is wrong can occur. In an invoice reimbursement scenario, the drawer provides invoice information to the business. Before an enterprise reimburses invoice information by accessing a server set by a government agency, the enterprise needs to actively go to an invoice verification website to inquire the validity of the invoice information, so that the reimbursement process is complicated.
The following description refers to specific terms used in describing the embodiments of the present disclosure.
5G: the 5th Generation mobile communication technology (5th Generation mobile networks or 5th Generation with less systems, 5th-Generation, 5G or 5G technology for short) is the latest Generation cellular mobile communication technology, and is also an extension following 4G (LTE-A, WiMax), 3G (UMTS, LTE) and 2G (gms) systems. The performance goals of 5G are high data rates, reduced latency, energy savings, reduced cost, increased system capacity, and large-scale device connectivity.
5G message: the 5G message is the upgrade of the short message service, is a basic telecommunication service of an operator, realizes the leap of service experience based on the IP technology, and has more supported media formats and richer expression forms.
Please refer to fig. 1. The embodiment of the specification provides a data processing system. The data processing system may include a user terminal and a blockchain network. The user terminal may be a purchaser-oriented terminal device. The purchaser may include a user or the like. The user terminal includes, but is not limited to, a smart phone, a tablet electronic device, a portable computer, a desktop computer, a smart wearable device, and the like. The blockchain network may include a plurality of node devices. The plurality of node devices may include an invoice issuing terminal, an invoice reimbursement terminal, a server, and the like. The invoice issuing terminal may be used to apply for issuing invoices to a server. The invoicing terminal may be set up by the seller. The seller may include merchants such as individual industrial merchants, business units, and the like. The invoice reimbursement terminal can be used for applying reimbursement invoices to the server. The invoice reimbursement terminal may be set up by a reimbursement party. The reimbursement party may include merchants such as individual industrial merchants, business units, and the like. The server may be configured to generate invoice information and reimburse the invoice information. The server may be set up by an associated government agency.
The invoice issuing terminal can acquire invoice issuing information; billing information may be sent to the server. The server can receive billing information; the authenticity of the invoicing information can be verified to obtain a verification result (hereinafter referred to as a first verification result); if the first check result is passed, corresponding invoice information can be generated according to the invoicing information; the invoice information can be stored on the blockchain; invoice information may be sent to the user terminal. The user terminal may receive invoice information. Therefore, the invoice information can be checked in the invoice issuing process, so that the generation of errors is reduced. And, because the blockchain has the characteristic of being not tampered, the reliability of the invoice information can be guaranteed by storing the invoice information on the blockchain.
The user terminal may send invoice information to the invoice reimbursement terminal. The invoice reimbursement terminal can receive invoice information; invoice information may be sent to the server. The server can receive invoice information; the validity of the invoice information can be checked to obtain a checking result (hereinafter referred to as a second checking result); if the second verification result is passed, reimbursement processing can be carried out on the invoice information to obtain a reimbursement processing result; reimbursement processing results may be stored on the blockchain; the reimbursement processing result may be sent to an invoice reimbursement terminal. The invoice reimbursement terminal can receive reimbursement processing results. Therefore, in the invoice reimbursement process, the server can check the invoice information. The invoice reimbursement terminal is not required to actively go to the invoice verification website to inquire the validity of the invoice information, and the invoice reimbursement process is simplified. Moreover, since the blockchain has the characteristic of being not tampered, the reliability of the reimbursement processing result can be guaranteed by storing the reimbursement processing result on the blockchain.
The embodiment of the specification provides an invoicing method based on a block chain. The method may be applied to a server. The server may be set up by a government agency. The server may join the blockchain network as a node device. The server may be one server, or may be a server cluster including a plurality of servers.
Please refer to fig. 2 and fig. 3. The method may include the following steps.
Step S11: receiving the billing information sent by the first terminal.
In some embodiments, the first terminal may comprise an invoicing terminal. The first terminal may comprise a personal computer, a server, or the like. The billing information may be used to invoice. The billing information may include purchaser data, seller data. The purchaser data may include the name of the purchaser, a taxpayer identification number, a contact (e.g., phone, mailbox), etc. The seller data may include the seller's name, taxpayer identification number, contact means (e.g., phone, mailbox), etc. Of course, the billing information may also include the name of the goods or services, the invoice amount, the invoice type, and the like.
In some embodiments, the first terminal may obtain billing information; billing information may be sent to the server. The first terminal may send billing information directly to the server. The server may receive billing information directly. Or, considering that the 5G has the characteristics of high data rate and low delay, the first terminal may further generate a first 5G message according to the billing information; a first 5G message may be sent to the server. The server may receive a first 5G message; the first 5G message may be parsed to obtain billing information. Specifically, the first terminal may encode the billing information in a 5G message according to a 5G message protocol, thereby obtaining a first 5G message. In practical application, the invoicing personnel can input the invoicing information at the first terminal. The first terminal may receive the input billing information. Alternatively, the user may input billing information at the user terminal. The user terminal can receive input billing information; billing information may be sent to the first terminal. The first terminal may receive billing information. Alternatively, the user may also enter partial billing information (e.g., purchaser data) at the user terminal. The user terminal can receive the partial billing information as first sub-billing information; the first sub-billing information may be transmitted to the first terminal. The first terminal can receive first sub-billing information; second sub-invoicing information (such as seller data) can be acquired from local; the billing information may be obtained from the first sub-billing information and the second sub-billing information.
Step S13: and checking the authenticity of the billing information to obtain a checking result.
In some embodiments, the billing information provided by the first terminal may be incorrect. The server may verify the authenticity of the billing information. The server stores a data set. The data set may include purchaser data and seller data. The server can verify the authenticity of the billing information through the data set. For example, the server may verify that the purchaser data is incorrect. Specifically, for example, the server may verify that the purchaser's name and the purchaser's taxpayer identification number are consistent. As another example, the server may verify that the seller data is incorrect. Specifically, for example, the server may check whether the name of the seller and the taxpayer identification number of the seller are consistent. And if the billing information is correct, the verification result is pass. And if the billing information is wrong, the checking result is that the billing information is not passed.
Step S15: and if the checking result is that the invoice passes, generating corresponding invoice information according to the invoice information.
In some embodiments, the invoice may comprise a value-added tax invoice. Of course, the invoice may also include other types of invoices, such as a train ticket, an airline ticket, a taxi invoice, a quota invoice, and the like. The invoice information may include buyer data, seller data. Of course, the invoice information may also include the name of the goods or service, the invoice amount, the invoice type, the invoice number, the invoice code, the invoicing date, the check code, the password, and the like. The invoice information may include an electronic invoice. Alternatively, the invoice information may also include an identification of the electronic invoice. The identification may be used to point to an electronic invoice. For example, the identification may include a link address of the electronic invoice, or the like. The electronic invoice can be obtained through the identification of the electronic invoice.
If the verification result is passed, the server can generate corresponding invoice information according to the invoice information.
Step S17: and storing the invoice information on the block chain.
In some embodiments, the server may store the invoice information on the blockchain. Due to the non-tampering characteristic of the block chain, the reliability of the invoice information can be guaranteed. And, also, the validity of invoice information is verified conveniently when reimbursing.
Step S19: and sending invoice information to the second terminal.
In some embodiments, the server may send the invoice information directly to the second terminal. The second terminal may receive the invoice information directly. Or, considering that 5G has the characteristics of high data rate and low delay, the server may further generate a second 5G message according to the invoice information; a second 5G message may be sent to the second terminal. The second terminal may receive a second 5G message; the second 5G message may be parsed to obtain invoice information. Specifically, the server may encode the invoice information in a 5G message according to a 5G message protocol, resulting in a second 5G message.
In some embodiments, the second terminal may comprise a user terminal. The billing information may include a contact address of the purchaser. The purchaser may hold the user terminal. Thus, the server may transmit invoice information to the user terminal through the contact of the purchaser. The user terminal may receive invoice information.
In some embodiments, the server may include a 5G message center, a verification module, an invoicing module, and a storage module. The 5G message center can receive a first 5G message sent by a first terminal; the first 5G message can be analyzed to obtain billing information; billing information may be sent to the verification module. The checking module can receive billing information; the authenticity of the billing information can be verified to obtain a verification result; if the verification result is passed, the invoice information can be sent to the invoice issuing module. The invoice issuing module can receive invoice issuing information; corresponding invoice information can be generated according to the invoicing information; invoice information may be sent to the 5G message center and the storage module, respectively. The 5G message center can receive invoice information; a second 5G message may be generated from the invoice information; a second 5G message may be sent to the second terminal. The storage module may receive invoice information; invoice information may be stored on the blockchain.
In some embodiments, the server may also send invoice information to the first terminal. The first terminal may receive invoice information.
In some embodiments, if the verification result is that the terminal fails, the server may further send a prompt message to the first terminal. The first terminal may receive a prompt. The prompt information is used for indicating that the ticket issuing information is wrong. The server may send the prompt message directly to the first terminal. The first terminal may directly receive the prompt message. Or, the server may further generate a third 5G message according to the prompt information; a third 5G message may be sent to the first terminal. The first terminal may receive a third 5G message; the third 5G message may be parsed to obtain the hint information.
The invoice issuing method based on the block chain in the embodiment of the specification can receive the invoice issuing information sent by the first terminal; the authenticity of the billing information can be verified to obtain a verification result; if the verification result is passed, corresponding invoice information can be generated according to the invoicing information; the invoice information can be stored on the blockchain; invoice information may be sent to the second terminal. Therefore, in the invoice issuing process, the authenticity of the invoice information can be checked, and the generation of errors is reduced. And due to the non-tampering characteristic of the block chain, the reliability of the invoice information can be guaranteed by storing the invoice information on the block chain.
The embodiment of the specification provides an invoicing method based on a block chain. The method may be applied to a server. The server may be set up by a government agency. The server may join the blockchain network as a node device. The server may be one server, or may be a server cluster including a plurality of servers.
Please refer to fig. 3 and 4. The method may include the following steps.
Step S21: receiving invoice information sent by the terminal.
In some embodiments, the terminal may comprise an invoice reimbursement terminal. The terminal may include a personal computer, a server, and the like. The invoice information may include buyer data, seller data. The invoice information may also include the name of the goods or services, invoice amount, invoice type, invoice number, invoice code, invoicing date, check code, password, etc.
In some embodiments, the invoice reimbursement terminal may obtain invoice information; invoice information may be sent to the server. The invoice reimbursement terminal can directly send invoice information to the server. The server may receive invoice information directly. Or, the invoice reimbursement terminal can also generate a first 5G message according to the invoice information; a first 5G message may be sent to the server. The server may receive a first 5G message; the first 5G message may be parsed to obtain invoice information. Specifically, the invoice reimbursement terminal may encode the invoice information in the 5G message according to the 5G message protocol, resulting in a first 5G message. In practical application, the reimburser can input invoice information at the invoice reimbursement terminal. The invoice reimbursement terminal can receive input invoice information. Alternatively, the user may enter invoice information at the user terminal. The user terminal can receive invoice information; invoice information may be sent to an invoice reimbursement terminal. The invoice reimbursement terminal can receive invoice information.
Step S23: and checking the validity of the invoice information to obtain a checking result.
In some embodiments, to prevent the problem of false invoices and invoice reimbursement, the server may check the validity of the invoice information. Specifically, the server may query whether the invoice information has been reimbursed through the blockchain. For example, the server may query whether a blockchain stores a reimbursement processing result corresponding to the invoice information. Or, the server can also adopt a preset algorithm to check the invoice information so as to check whether the invoice is a false invoice. And if the invoice information is valid, the verification result is passed. And if the invoice information is invalid, the verification result is failed.
Step S25: and if the verification result is that the invoice information passes, reimbursement processing is carried out on the invoice information.
Step S27: the reimbursement processing result is stored on the blockchain.
In some embodiments, if the verification result is passed, the server may perform reimbursement processing on the invoice information to obtain a reimbursement processing result; the reimbursement processing results may be stored on the blockchain. Due to the non-tampering characteristic of the block chain, the reliability of reimbursement processing results can be guaranteed. And, the problem of the second reimbursement of verification is also convenient. Wherein, the reimbursement processing result may include an reimbursement identifier. The reimbursement identifier is used for indicating that the invoice information is reimbursed.
Step S29: and sending the reimbursement processing result to the terminal.
In some embodiments, the terminal may comprise an invoice reimbursement terminal. The server can directly send the reimbursement processing result to the terminal. The terminal can directly receive the reimbursement processing result. Or, considering that 5G has the characteristics of high data rate and low delay, the server may further generate a second 5G message according to the reimbursement processing result; a second 5G message may be sent to the terminal. The terminal may receive a second 5G message; the second 5G message may be parsed to obtain a pinning result. Specifically, the server may encode the reimbursement processing result in the 5G message according to the 5G message protocol, thereby obtaining a second 5G message.
In some embodiments, the server may include a 5G message center, a verification module, an invoice reimbursement module, and a storage module. The 5G message center can receive a first 5G message sent by an invoice reimbursement terminal; the first 5G message can be analyzed to obtain invoice information; invoice information may be sent to the verification module. The verification module can receive invoice information; the validity of the invoice information can be checked to obtain a checking result; if the verification result is passed, the invoice information can be sent to the invoice reimbursement module. The invoice reimbursement module can receive invoice information; the invoice information can be subjected to reimbursement processing; the reimbursement processing result may be sent to the 5G message center and the storage module, respectively. The 5G message center can receive reimbursement processing results; a second 5G message may be generated according to the reimbursement processing result; a second 5G message may be sent to the invoice reimbursement terminal. The storage module can receive reimbursement processing results; the reimbursement processing results may be stored on a blockchain.
In some embodiments, if the verification result is that the terminal fails, the server may further send a prompt message to the terminal. The terminal may receive the prompt. The prompt information is used for indicating that the invoice information is wrong. The server can directly send prompt information to the terminal. The terminal can directly receive the prompt message. Or, the server may further generate a third 5G message according to the prompt information; a third 5G message may be sent to the terminal. The terminal may receive a third 5G message; the third 5G message may be parsed to obtain the hint information.
The invoice reimbursement method based on the block chain in the embodiment of the specification can receive invoice information sent by a terminal; the validity of the invoice information can be checked to obtain a checking result; if the verification result is passed, the invoice information can be subjected to reimbursement processing; the reimbursement processing results may be stored on a blockchain; the reimbursement processing result may be sent to the terminal. Therefore, in the invoice reimbursement process, the validity of the invoice information can be checked. The terminal does not need to actively inquire the validity of the invoice information in the invoice verification website, so that the reimbursement process of the invoice is simplified. And, through keeping the reimbursement processing result in the block chain, can guarantee the reliability of reimbursement processing result.
Please refer to fig. 5. The embodiment of the specification provides an invoicing device based on a block chain, which comprises the following units.
A receiving unit 31, configured to receive billing information sent by a first terminal;
the checking unit 33 is used for checking the authenticity of the ticket opening information to obtain a checking result;
the generating unit 35 is configured to generate corresponding invoice information according to the invoicing information if the verification result is that the invoice passes;
a storage unit 37, configured to store the invoice information on the blockchain;
and a sending unit 39, configured to send the invoice information to the second terminal.
Please refer to fig. 6. The embodiment of the specification provides an invoice reimbursement device based on a block chain, which comprises the following units.
A receiving unit 41, configured to receive invoice information sent by a terminal;
the checking unit 43 is used for checking the validity of the invoice information to obtain a checking result;
the reimbursement unit 45 is used for reimbursing the invoice information if the verification result is passed;
a storage unit 47 for storing the reimbursement processing result on the blockchain;
a sending unit 49, configured to send the reimbursement processing result to the terminal.
One embodiment of a computer apparatus of the present specification is described below. Fig. 7 is a hardware configuration diagram of the computer device in this embodiment. As shown in fig. 7, the computer device may include one or more processors (only one of which is shown), memory, and a transmission module. Of course, those skilled in the art will appreciate that the hardware configuration shown in fig. 7 is only an illustration, and does not limit the hardware configuration of the computer device. In practice the computer device may also comprise more or fewer component elements than those shown in fig. 7; or have a different configuration than that shown in fig. 7.
The memory may comprise high speed random access memory; alternatively, non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory may also be included. Of course, the memory may also comprise a remotely located network memory. The memory may be used to store program instructions or modules of application software, such as the program instructions or modules of the embodiments corresponding to fig. 2 or fig. 4 in this specification.
The processor may be implemented in any suitable way. For example, the processor may take the form of, for example, a microprocessor or processor and a computer-readable medium that stores computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, an embedded microcontroller, and so forth. The processor may read and execute the program instructions or modules in the memory.
The transmission module may be used for data transmission via a network, for example via a network such as the internet, an intranet, a local area network, a mobile communication network, etc.
This specification also provides one embodiment of a computer program product. The computer program product may include a computer storage medium. The computer storage medium includes, but is not limited to, a Random Access Memory (RAM), a Read-Only Memory (ROM), a Cache (Cache), a Hard Disk (HDD), a Memory Card (Memory Card), and the like. The computer storage medium stores computer program instructions. The computer program instructions when executed implement: the program instructions or modules of the embodiments corresponding to fig. 2 or fig. 4 in this specification.
It should be noted that, in the present specification, each embodiment is described in a progressive manner, and the same or similar parts in each embodiment may be referred to each other, and each embodiment focuses on differences from other embodiments. In particular, apparatus embodiments, computer device embodiments, and computer program product embodiments are substantially similar to method embodiments and therefore are described with relative ease, where reference may be made to some of the descriptions of the method embodiments. In addition, it is understood that one skilled in the art, after reading this specification document, may conceive of any combination of some or all of the embodiments listed in this specification without the need for inventive faculty, which combinations are also within the scope of the disclosure and protection of this specification.
In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain a corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, today, instead of manually manufacturing Integrated Circuit chips, such Programming is often implemented by "logic compiler" software, which is similar to the software compiler used in program development, but the original code before compiling is also written in a specific Programming Language, which is called Hardware Description Language (HDL), and the HDL is not just one kind, but many kinds, such as abel (advanced library Expression Language), ahdl (alternate Language Description Language), communication, CUPL (computer universal Programming Language), HDCal (dl) and jhd (Java Hardware Description Language), langva, Lola, myll, lam, lasm, harddl (runtime Description Language), vhh-Language, etc., which are currently used commonly. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
From the above description of the embodiments, it is clear to those skilled in the art that the present specification can be implemented by software plus necessary general hardware platform. Based on such understanding, the technical solutions of the present specification may be essentially or partially implemented in the form of software products, which may be stored in a storage medium, such as ROM/RAM, magnetic disk, optical disk, etc., and include instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments of the present specification.
The description is operational with numerous general purpose or special purpose computing system environments or configurations. For example: personal computers, server computers, hand-held or portable devices, tablet-type devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
This description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
While the specification has been described with examples, those skilled in the art will appreciate that there are numerous variations and permutations of the specification that do not depart from the spirit of the specification, and it is intended that the appended claims include such variations and modifications that do not depart from the spirit of the specification.

Claims (11)

1. A blockchain-based invoicing method, comprising:
receiving billing information sent by a first terminal;
verifying the authenticity of the billing information to obtain a verification result;
if the checking result is passed, generating corresponding invoice information according to the invoicing information;
storing the invoice information on a blockchain;
and sending invoice information to the second terminal.
2. The method of claim 1, wherein receiving billing information from the first terminal comprises:
receiving a first 5G message sent by a first terminal;
analyzing the first 5G message to obtain billing information;
the sending of the invoice information to the second terminal includes:
generating a second 5G message according to the invoice information;
and sending a second 5G message to the second terminal.
3. The method of claim 1, further comprising:
and if the checking result is that the ticket is not passed, sending prompt information to the first terminal, wherein the prompt information is used for indicating that the ticket issuing information is wrong.
4. A block chain-based invoice reimbursement method comprises the following steps:
receiving invoice information sent by a terminal;
verifying the validity of the invoice information to obtain a verification result;
if the checking result is that the invoice information passes, reimbursement processing is carried out on the invoice information;
storing the reimbursement processing result on the blockchain;
and sending the reimbursement processing result to the terminal.
5. The method of claim 4, wherein the receiving of invoice information from a terminal comprises:
receiving a first 5G message sent by a terminal;
analyzing the first 5G message to obtain invoice information;
the sending of the reimbursement processing result to the terminal includes:
generating a second 5G message according to the reimbursement processing result;
and sending a second 5G message to the terminal.
6. The method of claim 4, said verifying the validity of invoice information, comprising:
and inquiring whether the invoice information is reimbursed or not through the blockchain.
7. The method of claim 4, further comprising:
and if the verification result is that the invoice information is not passed, sending prompt information to the terminal, wherein the prompt information is used for indicating that the invoice information is wrong.
8. A blockchain-based invoicing apparatus comprising:
the receiving unit is used for receiving the billing information sent by the first terminal;
the checking unit is used for checking the authenticity of the billing information to obtain a checking result;
the generating unit is used for generating corresponding invoice information according to the invoicing information if the verification result is that the invoice passes;
the storage unit is used for storing the invoice information on the block chain;
and the sending unit is used for sending the invoice information to the second terminal.
9. A blockchain-based invoice reimbursement device, comprising:
the receiving unit is used for receiving invoice information sent by the terminal;
the checking unit is used for checking the validity of the invoice information to obtain a checking result;
the reimbursement unit is used for reimbursing the invoice information if the verification result is passed;
a storage unit for storing the reimbursement processing result on the block chain;
and the sending unit is used for sending the reimbursement processing result to the terminal.
10. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the method of any one of claims 1 to 7 when executing the computer program.
11. A computer program product comprising a computer program which, when executed by a processor, implements the method of any one of claims 1 to 7.
CN202210593658.2A 2022-05-27 2022-05-27 Invoice issuing method, invoice reimbursement device and equipment based on block chain Pending CN115018569A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210593658.2A CN115018569A (en) 2022-05-27 2022-05-27 Invoice issuing method, invoice reimbursement device and equipment based on block chain

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210593658.2A CN115018569A (en) 2022-05-27 2022-05-27 Invoice issuing method, invoice reimbursement device and equipment based on block chain

Publications (1)

Publication Number Publication Date
CN115018569A true CN115018569A (en) 2022-09-06

Family

ID=83071269

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210593658.2A Pending CN115018569A (en) 2022-05-27 2022-05-27 Invoice issuing method, invoice reimbursement device and equipment based on block chain

Country Status (1)

Country Link
CN (1) CN115018569A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117611363A (en) * 2023-10-25 2024-02-27 浙江爱信诺航天信息技术有限公司 Online verification method and medium for certificates

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117611363A (en) * 2023-10-25 2024-02-27 浙江爱信诺航天信息技术有限公司 Online verification method and medium for certificates

Similar Documents

Publication Publication Date Title
RU2419876C2 (en) Xml specification for electronic data interchange
US10572685B1 (en) Protecting sensitive data
CN110838071B (en) Policy data processing method, device and server
CN112163946A (en) Accounting processing method and device based on distributed transaction system
CN112463729B (en) Data file warehousing method and device, electronic equipment and medium
CN107133233B (en) Processing method and device for configuration data query
CN113435862B (en) Bill processing method and device based on mailbox
CN111159040A (en) Test data generation method, device, equipment and storage medium
CN106843818B (en) Business model generation method and device
CN114531289A (en) System interaction method based on artificial intelligence and related equipment
US11997216B2 (en) Systems and methods for maintaining secure, encrypted communications across distributed computer networks by linking cryptography-based digital repositories in order to perform blockchain operations in decentralized applications
CN112559024A (en) Method and device for generating transaction code change list
US20230306128A1 (en) Systems and methods for using secure, encrypted communications across distributed computer networks to provide variable resiliency when indexing blockchain states for performing blockchain operations in decentralized applications using cryptography-based digital repositories
CN112016028A (en) Information recording method and device, and information storage method, device and system
CN115018569A (en) Invoice issuing method, invoice reimbursement device and equipment based on block chain
CN113778725A (en) Data verification method and device
CN110046977B (en) Accounting method, accounting device and server
CN116993523A (en) Configurable account checking method, device, equipment and storage medium
CN111324645B (en) Block chain data processing method and device
CN109324838B (en) Execution method and execution device of single chip microcomputer program and terminal
US20230269085A1 (en) Systems and methods for using secure, encrypted communications across distributed computer networks to efficiently update cryptography-based digital repositories for performing blockchain operations in decentralized applications
US20230269086A1 (en) Systems and methods for using secure, encrypted communications across distributed computer networks to efficiently index blockchain states for performing blockchain operations in decentralized applications using cryptography-based digital repositories
CN115982254A (en) Database file conversion method, device, system, equipment and storage medium
CN113077241B (en) Approval processing method, device, equipment and storage medium
CN113535565B (en) Interface use case generation method, device, equipment and 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