CN110599276B - Bill reimbursement method, device and equipment and computer storage medium - Google Patents

Bill reimbursement method, device and equipment and computer storage medium Download PDF

Info

Publication number
CN110599276B
CN110599276B CN201910936215.7A CN201910936215A CN110599276B CN 110599276 B CN110599276 B CN 110599276B CN 201910936215 A CN201910936215 A CN 201910936215A CN 110599276 B CN110599276 B CN 110599276B
Authority
CN
China
Prior art keywords
bill
reimbursement
ticket
reimbursed
request
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.)
Active
Application number
CN201910936215.7A
Other languages
Chinese (zh)
Other versions
CN110599276A (en
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.)
Tencent Technology Shenzhen Co Ltd
Original Assignee
Tencent Technology Shenzhen Co 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 Tencent Technology Shenzhen Co Ltd filed Critical Tencent Technology Shenzhen Co Ltd
Priority to CN201910936215.7A priority Critical patent/CN110599276B/en
Priority to CN201910730645.3A priority patent/CN110458562B/en
Publication of CN110599276A publication Critical patent/CN110599276A/en
Application granted granted Critical
Publication of CN110599276B publication Critical patent/CN110599276B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/382Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3829Payment protocols; Details thereof insuring higher security of transaction involving key management
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce, e.g. shopping or e-commerce
    • G06Q30/04Billing or invoicing, e.g. tax processing in connection with a sale

Abstract

The application discloses a bill reimbursement method, a bill reimbursement device, a bill reimbursement equipment and a computer storage medium, relates to the technical field of computers, and is used for providing a parallel bill reimbursement mode, reducing the possibility of repeated reimbursement of bills and improving reimbursement efficiency. The method comprises the following steps: responding to a bill reimbursement operation instruction of requesting reimbursement on a plurality of bills to be reimbursed by a bill holding user, and respectively sending bill reimbursement requests to bill reimbursement systems of reimbursement enterprises designated for the bills to be reimbursed; and sending a ticket data transfer request to the block chain nodes, and respectively transferring the holding authority of each to-be-reimbursed ticket from the ticket holding user to the reimbursement enterprises appointed for each to-be-reimbursed ticket by requesting the block chain nodes; and acquiring the reimbursement result of each to-be-reimbursed bill according to the bill reimbursement response message which is sent by each bill reimbursement system and carries the reimbursement result of the to-be-reimbursed bill.

Description

Bill reimbursement method, device and equipment and computer storage medium
The invention relates to a divisional application of an invention application with application date of 2019, 08.08.08 and application number of 201910730645.3, and named as a bill reimbursement method, a device and equipment and a computer storage medium.
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, and a device for reimbursing bills and a computer storage medium.
Background
At present, the bill reimbursement mainly comprises two reimbursement modes, wherein one mode is an online reimbursement mode, a user needs to obtain a printed paper bill from a merchant after purchasing commodities, or the printed paper bill is printed by the user after obtaining an electronic bill and then taken to an reimbursement enterprise for reimbursement, and more manpower and resources are needed in the online reimbursement mode.
However, in the online reimbursement method, there may be a case of reimbursement, for example, a user submits one invoice to two reimbursement enterprises to reimburse the invoice at different units, and certainly, the case of reimbursement of a bill is obviously not allowed, so how to prevent reimbursement of a bill is a problem to be solved at present.
Disclosure of Invention
The embodiment of the application provides a bill reimbursement method, a bill reimbursement device, a bill reimbursement equipment and a computer storage medium, and is used for providing a bill reimbursement mode and reducing the possibility of repeated reimbursement of bills.
In one aspect, a method for reimbursing a bill is provided, and is applied to a terminal device, and the method includes:
responding to a bill reimbursement operation instruction of a bill holding user, and sending a bill reimbursement request to a bill reimbursement system of a reimbursement enterprise; the ticket reimbursement request carries an identification mark of a ticket to be reimbursed, and is used for requesting the ticket reimbursement system to reimburse the ticket to be reimbursed; and
sending a ticket data transfer request to a block link point to request the block link point to transfer the holding authority of the to-be-reimbursed ticket from the ticket holding user to the reimbursement enterprise; the block chain node stores the to-be-reimbursed bill;
and outputting the reimbursement result of the to-be-reimbursed bill according to a bill reimbursement response message which is sent by the bill reimbursement system and carries the reimbursement result of the to-be-reimbursed bill.
Optionally, the issuing operation instruction is used to instruct issuing of a plurality of tickets for one transaction, where the first issuing request includes a first issuing sub-request corresponding to each ticket to be issued, and then the sending of the first issuing request to an issuing system of an issuing enterprise includes:
and respectively generating first invoicing sub-requests corresponding to the to-be-invoiced bills according to the invoicing information and the money amount of the to-be-invoiced bills, and sending the first invoicing sub-requests to the invoicing system.
Optionally, when the ticket to be reimbursed includes a plurality of sub-tickets, the method further includes:
and respectively generating reimbursement requests for the sub-bills according to reimbursement enterprises selected by the bill holding users for the sub-bills, and sending the reimbursement requests to bill reimbursement systems of the corresponding reimbursement enterprises.
Optionally, the reimbursing according to the ticket data of the to-be-reimbursed ticket, and sending a ticket reimbursement response message carrying a reimbursement result to the terminal device, includes:
when the reimbursement of the to-be-reimbursed bill is completed, adding indication information indicating that the to-be-reimbursed bill has been reimbursed in bill data of the to-be-reimbursed bill;
and carrying the reimbursement result and the bill data including the indication information in the bill reimbursement response message and sending the bill reimbursement response message to the terminal equipment.
In one aspect, a method for reimbursing bills is provided, which is applied to a bill reimbursement system of an reimbursement enterprise, and the method includes:
receiving a bill reimbursement request sent by terminal equipment; the ticket reimbursement request carries an identification of a to-be-reimbursed ticket, and is used for requesting reimbursement of the to-be-reimbursed ticket;
acquiring bill data of the bill to be reimbursed from the block link points according to the identification marks; the ticket data of the to-be-reimbursed ticket is obtained by searching the ticket data of the to-be-reimbursed ticket in which the authority of the to-be-reimbursed ticket is possessed by the reimbursement enterprise according to the identification mark after the ticket data of the to-be-reimbursed ticket is transferred to the reimbursement enterprise from the ticket holding user by the block link point;
and reimbursing according to the bill data of the bill to be reimbursed, and sending a bill reimbursement response message carrying reimbursement results to the terminal equipment.
In one aspect, a method for reimbursing bills is provided, and is applied to a blockchain node, and the method includes:
in response to the bill transfer request, transferring the holding authority of the to-be-reimbursed bill from the bill holding user to the reimbursement enterprise;
in response to a bill acquisition request sent by a bill reimbursement system of the reimbursement enterprise, searching bill data of the bill to be reimbursed from the bill data of the reimbursement enterprise with authority according to an identification mark carried by the bill acquisition request;
and sending the bill data of the bill to be reimbursed to the bill reimbursement system so that the bill reimbursement system reimburses the bill according to the bill data of the bill to be reimbursed.
In one aspect, a device for reimbursing bills is provided, and is applied to a terminal device, the device includes:
the system comprises a first sending unit, a second sending unit and a third sending unit, wherein the first sending unit is used for responding to a bill reimbursement operation instruction of a bill holding user and sending a bill reimbursement request to a bill reimbursement system of a reimbursement enterprise; the ticket reimbursement request carries an identification mark of a ticket to be reimbursed, and is used for requesting the ticket reimbursement system to reimburse the ticket to be reimbursed; sending a ticket data transfer request to a block chain node to request the block chain node to transfer the holding authority of the to-be-reimbursed ticket from the ticket holding user to the reimbursement enterprise; the block chain node stores the to-be-reimbursed bill;
and the acquisition unit is used for acquiring the reimbursement result of the to-be-reimbursed bill according to a bill reimbursement response message which is sent by the bill reimbursement system and carries the reimbursement result of the to-be-reimbursed bill.
Alternatively to this, the first and second parts may,
the first sending unit is also used for responding to the invoicing operation instruction and sending a first invoicing request to an invoicing system of an invoicing enterprise, wherein the invoicing request carries invoicing information required by an invoicing bill;
the obtaining unit is further used for obtaining an invoicing result according to the invoicing response message sent by the invoicing system; and the billing response message is generated according to a billing result returned by the block chain node after the billing system sends a second billing request to the block chain node according to the billing information.
Optionally, the invoicing operation instruction is used to instruct to issue multiple tickets for one transaction, where the first invoicing request includes a first invoicing sub-request corresponding to each to-be-issued ticket, and the first sending unit is specifically configured to:
and respectively generating first invoicing sub-requests corresponding to the to-be-invoiced bills according to the invoicing information and the money amount of the to-be-invoiced bills, and sending the first invoicing sub-requests to the invoicing system.
Optionally, the to-be-reimbursed ticket includes a sub-ticket split from an issued ticket;
the first sending unit is further configured to send a ticket splitting request to the block link point in response to a splitting operation instruction of the ticket holding user for the issued ticket, where the ticket splitting request carries an identification of the issued ticket and splitting instruction information, and is used to request that the initial ticket to be split is split into at least two sub-tickets according to the instruction of the splitting instruction information;
the acquiring unit is further configured to acquire the ticket data of the at least two sub-tickets obtained through splitting according to a ticket splitting response message sent by the block chain node when the ticket splitting is successful, the identification mark of each sub-ticket is generated based on the ticket content of each sub-ticket obtained through splitting, and the other ticket contents except the ticket amount in the ticket content of each sub-ticket are the same as the initial ticket.
Optionally, the apparatus further comprises a determining unit;
the determining unit is used for responding to a selection operation instruction of the ticket holding user for selecting the to-be-reimbursed ticket from at least two sub-tickets, and determining the selected sub-ticket as the to-be-reimbursed ticket.
Optionally, when the ticket to be issued includes a plurality of sub-tickets, the first sending unit is further configured to:
and respectively generating reimbursement requests for the sub-bills according to reimbursement enterprises selected by the bill holding users for the sub-bills, and sending the reimbursement requests to bill reimbursement systems of the corresponding reimbursement enterprises.
Alternatively to this, the first and second parts may,
the first sending unit is further configured to send a ticket query request to a ticket query device in response to a ticket query operation instruction of the ticket-holding user, where the ticket query request carries a user identifier of the ticket-holding user;
the acquisition unit is also used for acquiring a bill query result according to the bill query response message sent by the bill query equipment; the bill query device stores the incidence relation between the user identification and the identification, and the bill query result comprises bill data acquired from the block chain node according to the identification obtained by querying after the bill query device queries the identification associated with the user identification according to the incidence relation.
Optionally, the first sending unit is specifically configured to:
when a bill data acquisition request of the bill reimbursement system is received, sending the bill transfer request to the block chain nodes; alternatively, the first and second electrodes may be,
sending the bill transfer request to the block link point through the bill reimbursement system; and when acquiring authorization indication information for authorizing the holding permission of the to-be-reimbursed bill to be transferred, the bill reimbursement system sends the bill transfer request to the block chain node according to the authorization indication information.
In one aspect, a bill reimbursement device is provided, which is applied to a bill reimbursement system of a reimbursement enterprise, and the device comprises:
the receiving unit is used for receiving a bill reimbursement request sent by the terminal equipment; the ticket reimbursement request carries an identification of a to-be-reimbursed ticket, and is used for requesting reimbursement of the to-be-reimbursed ticket;
the second acquisition unit is used for acquiring bill data of the to-be-reimbursed bill from the block link point according to the identification mark; the ticket data of the to-be-reimbursed ticket is obtained by searching the ticket data of the to-be-reimbursed ticket in which the authority of the to-be-reimbursed ticket is possessed by the reimbursement enterprise according to the identification mark after the ticket data of the to-be-reimbursed ticket is transferred to the reimbursement enterprise from the ticket holding user by the block link point;
and the bill reimbursement unit is used for reimbursing the bill data of the bill to be reimbursed and sending a bill reimbursement response message carrying a reimbursement result to the terminal equipment.
Optionally, the ticket reimbursement unit is specifically configured to:
when the reimbursement of the to-be-reimbursed bill is completed, adding indication information indicating that the to-be-reimbursed bill has been reimbursed in bill data of the to-be-reimbursed bill;
and carrying the reimbursement result and the bill data including the indication information in the bill reimbursement response message and sending the bill reimbursement response message to the terminal equipment.
Optionally, the apparatus further includes a second sending unit, configured to:
if the to-be-reimbursed bill is successfully reimbursed, sending a reimbursed bill storage request to the blockchain node, wherein the reimbursed bill storage request is used for requesting the blockchain node to store bill data including indication information indicating reimbursed of the to-be-reimbursed bill.
In one aspect, a ticket reimbursement device is provided, which is applied in a blockchain node, and the device includes:
the bill transfer unit is used for responding to the bill transfer request and transferring the holding authority of the bill to be reimbursed from the bill holding user to the reimbursement enterprise;
the bill searching unit is used for responding to a bill acquisition request sent by a bill reimbursement system of the reimbursement enterprise, and searching bill data of the bill to be reimbursed from the bill data of the reimbursement enterprise with authority according to an identification mark carried by the bill acquisition request;
and the third sending unit is used for sending the bill data of the bill to be reimbursed to the bill reimbursement system so as to enable the bill reimbursement system to reimburse the bill according to the bill data of the bill to be reimbursed.
Optionally, the device further includes a bill splitting unit and an identifier generating unit;
the bill splitting unit is used for responding to a bill splitting request sent by the terminal equipment and splitting the issued bill into at least two sub-bills according to the indication of splitting indication information carried by the bill splitting request; the bill contents of each sub-bill are the same as the initial bill except the bill surface sum;
the identification generation unit is used for generating the identification of each sub-bill according to the bill content of each sub-bill;
the third sending unit is further configured to carry the ticket data of the at least two sub-tickets in a ticket splitting response message, and send the ticket data to the terminal device; the ticket data includes an identification and a ticket content.
In one aspect, a computer device is provided, comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the method of the above aspect when executing the program.
In one aspect, a computer-readable storage medium is provided that stores processor-executable instructions for performing the method of the above aspect.
In the embodiment of the application, the bills are stored in the block chain nodes, when the user initiates invoice reimbursement, when submitting a bill reimbursement request to an reimbursement enterprise, the user also requests the block chain nodes to transfer the right of possession of the bill to be reimbursed to the reimbursement enterprise from the bill holding user, so that after the transfer, the bill holding user does not have the right of possession of the bill to be reimbursed any more, namely after the reimbursement request is submitted by the user, the bill to be reimbursed is not owned by the user any more, and then the user can not reimburse the bill to be reimbursed any more, thereby effectively reducing the possibility of occurrence of the repeated reimbursement situation.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only the embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a schematic view of an application scenario provided in an embodiment of the present application;
fig. 2 is a schematic view of another application scenario provided in the embodiment of the present application;
FIG. 3 is a schematic flow chart of an issuing order provided by an embodiment of the present application;
FIG. 4 is a schematic diagram illustrating an operation of a user applying for an invoice provided in an embodiment of the present application;
FIG. 5 is a schematic flow chart illustrating a method for reimbursing bills according to an embodiment of the present disclosure;
FIG. 6 is a schematic diagram of an interface for a ticket query according to an embodiment of the present application;
fig. 7 is a schematic diagram of a ticket query result page 1 and a ticket splitting page provided in the embodiment of the present application;
FIG. 8 is a schematic diagram illustrating a user selecting a cancellation ticket according to an embodiment of the present application;
FIG. 9 is a schematic diagram of another user selection of a cancellation ticket according to an embodiment of the present application;
FIG. 10 is a schematic diagram illustrating operation of a ticketing user for reimbursing multiple tickets according to an embodiment of the present application;
FIG. 11 is a schematic flow chart illustrating the process of applying for reimbursing a ticket according to an embodiment of the present application;
FIG. 12 is a schematic flow chart illustrating an exemplary embodiment of a method for applying for reimbursing a ticket;
FIG. 13 is a schematic flow chart illustrating a process for applying for reimbursing a ticket according to an embodiment of the present application;
FIG. 14 is a schematic flow chart illustrating a process for applying for reimbursing a sub-ticket according to an embodiment of the present application;
FIG. 15 is a schematic view of a process for applying multiple reimbursement agencies to reimburse multiple tickets respectively according to an embodiment of the present application;
fig. 16 is a schematic structural diagram of a ticket reimbursement device according to an embodiment of the present application;
FIG. 17 is a schematic structural diagram of another instrument reimbursement device according to an embodiment of the present application;
FIG. 18 is a schematic structural diagram of a ticket reimbursement apparatus according to an embodiment of the present application;
fig. 19 is a schematic structural diagram of a computer device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions in the embodiments of the present application will be described clearly and completely with reference to the accompanying drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application. In the present application, the embodiments and features of the embodiments may be arbitrarily combined with each other without conflict. Also, while a logical order is shown in the flow diagrams, in some cases, the steps shown or described may be performed in an order different than here.
For the convenience of understanding the technical solutions provided by the embodiments of the present application, some key terms used in the embodiments of the present application are explained first:
a bill: the voucher is made according to a certain specified form and displays the voucher with the obligation of paying money, namely, the voucher can be used as a transaction voucher when a transaction occurs. Generally, the bill may include tax invoice, financial bill (such as medical bill) or business bill, etc., the invoice is generally the business certificate issued and collected by the unit and the individual in purchasing and selling goods, providing or receiving services and doing other business activities, and is the original basis for accounting; the medical ticket is a consumption certificate issued by a medical institution after the medical institution consumes the medical ticket; the business ticket is an unsecured short-term ticket issued by a financial company or an enterprise and used for financing by a ticket issuer; of course, the ticket in the embodiment of the present application may also refer to other types of tickets that can be found and reimbursed for an enterprise, for example, a ticket issued inside an enterprise, and the like.
The ticket holding user: refers to the user who owns the ticket, i.e., the user who initiated the ticket reimbursement process.
A reimbursement mechanism: the ticket issuing system refers to enterprises or government institutions and the like for which ticket holding users request to reimburse tickets to be reimbursed. For example, for invoices, the reimbursement agency is generally the company noted in the top-up of the invoice, or for medical tickets, the reimbursement agency is generally an insurance company or a government agency, etc.
An invoicing mechanism: refers to an organization such as a merchant, an enterprise, or a medical institution that issues invoices to users.
Block Chain (Block Chain): or called distributed data record book, is a chain data structure formed by combining data blocks (blocks) in a certain sequence in a sequential connection mode, and is a distributed book which is guaranteed to be not falsified and forged in a cryptology mode. The block is used for recording information related to one or more events in the invoice flow, for example, an event may refer to processes of storing a bill, transferring the bill, splitting the bill, storing a reimbursement result of the bill, and the like.
Block chain node: refers to a computing device participating in transaction processing in a blockchain network, such as a computer, a mobile phone, a desktop, a server or a server cluster, or a single computer or a part of a server, for example, a virtual machine, may be used as a node in the blockchain network. For example, each block link node may be in the form of a virtual machine cluster, that is, a part of each block link node is divided from multiple physical machines to serve as a virtual machine, and collectively function as a block link node.
The Unspent Transaction Output (UTXO) model: in the UTXO model, a transaction represents a change of the UTXO set, each transaction costs (spread) an input and produces an output (output), and the output produced is the "unspent transaction output", i.e., the UTXO. For the UTXO model, the maximum characteristic is that the UTXO model does not exist after the transaction, that is, after the transaction occurs, the content before the transaction does not exist, and for the ticket transfer process, the UTXO model may be regarded as one transaction, and the ticket to be reimbursed is an input of the transaction, and after the transaction, the ticket to be reimbursed is transferred to the reimbursement institution, and the ticket to be reimbursed of the ticket holder does not exist.
In addition, the term "and/or" herein is only one kind of association relationship describing an associated object, and means that there may be three kinds of relationships, for example, a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" in this document generally indicates that the preceding and following related objects are in an "or" relationship unless otherwise specified. Furthermore, references to "first" or "second", etc. herein are only used to distinguish between similar items and not to describe a particular order or sequence.
The bill reimbursement generally refers to a process that a user pays money in advance and then reimburses the money in a reimbursement mechanism, and the reimbursement mechanism compensates the paid money for the user. Generally, a bill is allowed to be reimbursed because an online reimbursement service generally uses reimbursement software or a reimbursement web page to perform an electronic reimbursement process, but in the current online reimbursement method, because a more effective duplication checking mechanism does not exist, repeated reimbursement may occur, and a certain risk is brought to financial processing and the like of a reimbursement institution, thereby causing property loss of the reimbursement institution.
The applicant analyzes the prior art and finds that, in the prior art, because electronic bills are generally owned or stored by ticket-holding users, and the ticket-holding users submit the electronic bills to be reimbursed by themselves during reimbursement, when reimbursement mechanisms for reimbursement requested by the ticket-holding users are different, the reimbursement mechanisms cannot know that the electronic bills are possibly reimbursed by another enterprise, and reimburse the electronic bills for the ticket-holding users according to a normal reimbursement process, so that a situation of repeated reimbursement is generated. Therefore, in order to prevent the user from conducting repeated reimbursement, the ticket owned by the user needs to be destroyed after reimbursement of the user, and in view of the characteristics of the block chain UTXO model, that is, the characteristics that the ticket does not exist after transaction, the UTXO model can be applied to the reimbursement of the ticket, that is, after reimbursement, the ticket of the user does not exist or the user does not have the authority of the ticket, so that the occurrence of repeated reimbursement is prevented.
Based on the above analysis and consideration, the embodiment of the present application provides a method for reimbursement of bills, in which electronic bills are stored uniformly by block link points, when reimbursement is not performed, a user holding a bill can have the right of possession of the electronic bill, for the user holding a bill, one electronic bill can be regarded as an asset of the user, when the user requests reimbursement, the user needs to request the block link points to transfer the right of possession of the reimbursement bill to the reimbursement mechanism, that is, the user can deal the reimbursement bill to the reimbursement mechanism once initiating reimbursement, conceivably, after reimbursement is completed, the user holding a bill no longer has the right of possession of the reimbursement bill, and cannot use the reimbursement bill that has been reimbursed again, thereby effectively reducing the possibility of reimbursement of bills, the property safety of the reimbursement mechanism is improved.
In addition, considering that a ticket holder may want to request the same electronic ticket to reimburse for different institutions, for example, the user purchases medical insurance of different insurance companies, and the amount of the medical invoice issued by the medical institution may be on one electronic ticket and cannot be provided to two insurance companies for reimbursement, in this embodiment of the application, the ticket holder may request the block link point to split a ticket into a plurality of sub-tickets in advance before submitting the reimbursement request, and the ticket content of the sub-ticket is the same as the original ticket before splitting except the amount of the ticket, so that the ticket holder may select the sub-ticket needing reimbursement after submitting the reimbursement request and initiate the reimbursement application to the corresponding reimbursement institution.
In the embodiment of the application, in order to improve the efficiency of bill reimbursement, for the sub-bills obtained by splitting, the ticket holding user can also initiate reimbursement application to the reimbursement mechanism in parallel, namely, the ticket holding user selects the sub-bills required to be reimbursed when initiating the application, selects the reimbursement mechanism corresponding to each sub-bill, and after submitting the reimbursement request, the corresponding reimbursement request can be respectively initiated to each reimbursement mechanism, so that the parallel reimbursement of the sub-bills is realized, the operation required for reimbursement of the bills of the user is simplified, and the efficiency of bill reimbursement is.
After introducing the design concept of the embodiment of the present application, some simple descriptions are provided below for application scenarios to which the technical solution of the embodiment of the present application can be applied, and it should be noted that the application scenarios described below are only used for describing the embodiment of the present application and are not limited. In a specific implementation process, the technical scheme provided by the embodiment of the application can be flexibly applied according to actual needs.
Please refer to fig. 1, which is an application scenario to which the technical solution in the embodiment of the present application can be applied, and in the scenario, the application scenario may include a terminal device 101, an invoice reimbursement system device 102, a block link point 103, and an invoicing system device 104.
The terminal device 101 may be a mobile phone, a Personal Computer (PC), a tablet computer (PAD), a Personal Digital Assistant (PDA), a notebook computer, or an intelligent wearable device (e.g., an intelligent watch and an intelligent bracelet). Terminal device 101 may include, among other things, one or more processors 1011, memory 1012, I/O interfaces 1013, and a display panel 1014. The memory 1012 of the terminal device 101 may store program instructions of the ticket reimbursement method provided in the embodiment of the present application, and when the program instructions are executed by the processor 1011, the program instructions can be used to implement the functions of the ticket reimbursement method described above and display a corresponding display page on the display panel 1014.
The terminal device 101 may be installed with an application provided by a billing mechanism, a reimbursement mechanism, or the like, or may open a website provided by the billing mechanism, the reimbursement mechanism, or the like, and the application or the website may include a function of a method to be executed by the terminal device in the method for reimbursement of bills provided by the embodiment of the present application, so that a user may initiate billing or reimbursement of bills by using the method to be executed by the terminal device in the method for reimbursement of bills provided by the embodiment of the present application through the application or the website.
It should be noted that, although only one terminal device 101 is shown in fig. 1, in an actual application, there may be many terminal devices 101 installed with the application or capable of opening the website, and therefore, the terminal device 101 may be any one of the terminal devices 101.
The billing system device 104 may be a device of a billing authority and the billing system device 104 may include one or more processors 1041, memory 1042, I/O interface 1043, and the like. The memory 1042 may store program instructions of a method to be executed by the billing system in the ticket reimbursement method provided in the embodiment of the present application, that is, the user makes a ticket, and when the processor 1041 executes the program instructions, the method to be executed by the billing system in the ticket reimbursement method provided in the embodiment of the present application may be implemented, so as to help the user make a ticket. In addition, the billing system device 104 may be configured with a database, which may be used to store information such as the identification of the bill (e.g., unique identification of the invoice) obtained from the tax authority, and information such as the billing history processed for each user.
In the billing system device 104, an application related to billing is installed or a website related to billing is opened, and when a billing request initiated by the terminal device 101 is received, the billing request is processed by using the billing processing logic of the application or the website, so that necessary information required for billing is provided to the blockchain node 103 for billing, or after the billing is completed, the billed ticket is provided to the blockchain node 103 for storage.
In the blockchain network, a plurality of node devices are included, and functions of the node devices may be identical, or each node device may have different division of labor, for example, part of the node devices are used for recording of ticket circulation, and part of the node devices are used for storing tickets, or part of the node devices can simultaneously implement recording of ticket circulation and storing of tickets. The block chain node 103 may be any node device in a block chain network, and the block chain node 103 may include one or more processors 1031, a memory 1032, and I/O interfaces 1033, etc. The memory 1032 may store program instructions of a method to be executed by the block chain node in the ticket reimbursement method provided in the embodiment of the present application, that is, when the program instructions are executed by the processor 1031, the method to be executed by the block chain node in the ticket reimbursement method provided in the embodiment of the present application may be implemented.
In the billing process, the block chain node 103 may obtain and store the invoiced ticket from the billing system device 104; alternatively, the blockchain node 103 may obtain necessary information required for making a ticket from the billing system device 104, thereby making a ticket based on the information and storing it.
The invoice reimbursement system device 102 may be a device of a reimbursement authority, and the invoice reimbursement system device 102 may include, among other things, one or more processors 1021, memory 1022, and I/O interfaces 1023. The memory 1022 may store program instructions of a method to be executed by the invoice reimbursement system in the bill reimbursement method provided in the embodiment of the present application, that is, a reimbursement bill of a user, and when being executed by the processor 1021, the method to be executed by the invoice reimbursement system in the bill reimbursement method provided in the embodiment of the present application may be implemented, so as to help the user reimburse the bill. In addition, the invoice reimbursement system 102 may also be configured with a database that may be used to store reimbursement-related audit information, ticketed customer information, and reimbursement history processed for each customer.
In the invoice reimbursement system device 102, an application related to invoice reimbursement is installed or a website related to invoice reimbursement is opened, and when a invoice reimbursement request initiated by the terminal device 101 is received, the invoice reimbursement request can be processed by using invoice reimbursement processing logic of the application or the website (that is, a function implemented by the invoice reimbursement system in the invoice reimbursement method provided in the embodiment of the present application), so as to complete reimbursement of the invoice.
In the bill reimbursement process, the block chain node 103 may transfer the right of possession of the to-be-reimbursed bill from the ticket holding user to the reimbursement mechanism based on the request of the terminal device 101 or the invoice reimbursement system device 102, so that the reimbursement mechanism can obtain the to-be-reimbursed bill for reimbursement, and the ticket holding user loses the right of possession of the to-be-reimbursed bill after the transfer, thereby failing to perform secondary reimbursement, and preventing the occurrence of repeated reimbursement.
The devices that need to communicate with each other may be communicatively connected through one or more networks 105, where the network 105 may be a wired network, or may also be a WIreless network, for example, the WIreless network may be a mobile cellular network, or may be a WIreless-Fidelity (WIFI) network, and certainly, other possible networks may also be used, which is not limited in this embodiment.
Referring to fig. 2, another application scenario to which the technical solution in the embodiment of the present application can be applied is shown, and in the scenario, the application scenario may include a terminal device 201, an invoice reimbursement system device 202, an invoicing system device 203, a tax authority device 204, and a block chain node 205.
As for the circulation flows of issuing or reimbursing bills and the like, generally, the circulation flows need to be monitored by relevant monitoring agencies (such as a tax bureau and the like), each circulation flow of bills needs to be monitored by the tax agency equipment 204, correspondingly, the block chain network can also be provided by the tax agency and used for executing circulation operations of issuing bills and storing bills and the like, and each operation performed on bills in the block chain node, such as the operation of issuing bills, transferring invoices or splitting bills and the like, needs to be accessed through an interface provided by the tax agency equipment 204, namely, needs to be forwarded through the tax agency equipment 204. The terminal device 201, the invoice reimbursement system device 202, the invoicing system device 203, and the block chain node 205 may all correspond to the terminal device 101, the invoice reimbursement system device 102, the invoicing system device 104, and the block chain node 103 in the application scenario shown in fig. 1 in sequence, and therefore, the functions that can be implemented by the above devices may correspond to the devices shown in fig. 1 in sequence, and the difference is that the interaction with the block chain node 205 needs to be performed by the taxation mechanism device 204, so the functions that can be implemented by the above devices may refer to the description of the embodiment part shown in fig. 1, and are not described herein again.
The tax administration device 204 may set a management scope according to the layout of the tax system in each region, for example, a provincial tax administration is generally used to manage tax-related affairs in province, and then the bill affairs belonging to a reimbursement institution or an invoicing institution in province may be forwarded through the provincial tax administration device, or a city tax administration is generally used to manage tax-related affairs in city, and then the bill affairs belonging to a reimbursement institution or an invoicing institution in city may be forwarded through the city tax administration device.
The network for communication among the terminal device 201, the invoice reimbursement system device 202, the invoicing system device 203, and the tax administration device 204 may be the same as the network for communication among the tax administration device 204 and the block link point 205, for example, both may be a mobile cellular network or a wired network, of course, the network for communication among the terminal device 201, the invoice reimbursement system device 202, the invoicing system device 203, and the tax administration device 204 may be the same as the network for communication among the tax administration device 204 and the block link point 205, for example, the network for communication among the terminal device 201, the invoice reimbursement system device 202, the invoicing system device 203, and the tax administration device 204 may be a wide area network, and the network for communication among the tax administration device 204 and the block link point 205 may be a local area network inside the tax administration system.
Of course, the method provided in the embodiment of the present application is not limited to be used in the application scenario shown in fig. 1 or fig. 2, and may also be used in other possible application scenarios, and the embodiment of the present application is not limited. Functions that can be implemented by each device in the application scenario shown in fig. 1 or fig. 2 will be described together in the following method embodiment, and will not be described in detail herein.
In the embodiment of the application, before the reimbursement of the ticket, a general user needs to apply for issuing the ticket to the issuing organization, so that the reimbursement can be performed based on the issued ticket. Therefore, before describing the ticket reimbursement method of the embodiments of the present application, a description will be given of the process of issuing a ticket. As shown in fig. 3, a flow diagram for billing a user for a billing agency is shown.
Step 301: the terminal equipment sends a first billing request to a billing system of the billing mechanism, and the billing system equipment receives the first billing request.
In the embodiment of the application, after the user conducts the transaction or the consumption, the user can request the invoicing mechanism to invoice for the invoicing mechanism according to an invoicing mode provided by the invoicing mechanism (namely, a merchant or a business where the user conducts the transaction or the consumption).
Specifically, if the user performs the transaction on line, a button for issuing a bill is generally provided when the transaction occurs or after the transaction is completed, and the user can enter a bill issuing interface to perform a subsequent invoice issuing process by operating the button for issuing the bill. Fig. 4 is a schematic diagram illustrating an operation of applying for issuing a bill for a user, and fig. 4 illustrates an example of requesting a merchant to issue an invoice after purchasing a commodity through an online shopping platform. In the order detail page, the user can check the detailed content of the transaction order and the invoicing button for applying invoicing, and after the user operates the invoicing button, the user can enter the invoicing information filling page.
In the invoicing information filling page, the user may fill in necessary invoicing information, such as information of the invoice type, the invoice heading, the invoice content, the information of the invoice taker, and the like, and certainly, other possible information may also be included, which is not limited in this application embodiment. The invoice types can generally comprise electronic common invoices and value-added tax special invoices; the invoice head-up can be a person or a unit generally, and when the invoice needs to be reimbursed, the invoice head-up is a reimbursement mechanism (namely a reimbursement enterprise) generally; the invoice content can generally comprise commodity details, commodity types and the like and is used for indicating commodity related information; the information of the payee is generally information of a user holding the invoice, and the information of the payee may include, for example, a user identifier (such as an identification number) of the payee and a contact manner (such as a mobile phone number or a mailbox) of the payee, and the information of the payee may be used to notify the payee according to the information of the payee after the invoice is issued, or the information of the payee is associated with the issued invoice, so that the subsequent payee may query the invoice in its name by the own user information.
After the user fills the billing information, the user can operate the 'submit' button to issue the billing process, correspondingly, the terminal device can detect the billing operation of the user and inform the online shopping platform application of the billing operation, the online shopping platform can respond to the billing operation instruction and send a first billing request to the billing system device, and the first billing request can carry billing information required by the billing bill, namely information filled in the billing information filling page by the user.
Certainly, when the transaction is performed on line, the user can request the transaction party to make a bill in the transaction process besides requesting the transaction party to make a bill after the transaction is successful, for example, the user applies for the other party to make an electronic bill in the process of initiating a transaction application.
Specifically, if the user performs the transaction on line, the billing request may be initiated on line. For example, a merchant of offline transaction can provide an entrance of an invoicing page such as an invoicing two-dimensional code or an invoicing applet code, and a user can enter the invoicing page after scanning the invoicing two-dimensional code or the invoicing applet code, and can initiate an invoicing request after filling in invoicing information; alternatively, the user may also enter a merchant website or application requesting invoicing.
In this embodiment of the application, in order to facilitate subsequent reimbursement of the user, the user may further request the billing mechanism to make a plurality of tickets for the one-time transaction, where the total amount of the plurality of tickets is the total amount of the one-time transaction, correspondingly, the billing operation instruction of the user is used to instruct to make a plurality of tickets for the one-time transaction, and the generated first billing request may include a first billing sub-request corresponding to each ticket to be made. Specifically, when the user fills in the billing information, the billing information of each to-be-billed bill of the to-be-billed bills to be billed can be respectively filled, so that the first billing sub-requests corresponding to the to-be-billed bills are respectively generated according to the billing information and the amount of money of the to-be-billed bills, and are sent to the billing system.
Step 302: and the billing system equipment sends a second billing request to the block chain node, and the block chain node receives the second billing request.
In the embodiment of the application, after the billing system device of the billing mechanism receives the first billing request, billing can be performed for the user based on the billing information request block chain node carried by the first billing request.
Specifically, when an issuing authority claims a ticket from a tax authority in advance, when issuing an electronic ticket, the issuing authority claims an identification section, usually a ticket, that is, a ticket code issued to the issuing authority can only be used by the issuing authority for issuing the ticket. Thus, after the invoicing system device receives the first invoicing request, the invoicing information in the first invoicing request can be verified, for example, whether the commodity is consistent with the commodity in the order requesting the invoicing or whether the user-selected type of ticket can be issued or not, when the verification is passed, one of the ticket identifications can be distributed to the first invoicing request from the claimed identification section, a second invoicing request is generated based on the invoicing information carried by the first invoicing request and the distributed ticket identification, and the generated second invoicing request is sent to the block chain node.
Specifically, when the billing organization does not claim the ticket in advance, the ticket identifier cannot be allocated to the received first billing request, so after the billing system device receives the first billing request and verifies the first billing request, the billing system device may generate a second billing request based on the billing information carried in the first billing request, and send the generated second billing request to the block chain node.
In practical application, the invoicing system device sends the second invoicing request to the block chain node, and the invoicing request can be sent to the block chain node by the invoicing system device through the tax mechanism device. When the billing system equipment does not distribute the bill identification, the bill identification can be distributed through the tax institution equipment, and the billing information carried in the second billing request and the distributed bill identification are sent to the block chain node.
The ticket identifier is used to uniquely identify a ticket, for example, in the case of an invoice, the ticket identifier may be a unique identification code of the invoice.
The billing system device may send a second billing request to a blockchain node in the blockchain network. Generally, a blockchain node here may be any blockchain node in a blockchain network, and may also be a blockchain node in fixed communication connection with an invoicing system device.
In the embodiment of the application, when a user applies for making a plurality of bills for one transaction, the billing system equipment can respectively process the first sub-billing requests corresponding to the plurality of bills, that is to say, the processing process of each first sub-billing request is the same as that of the first billing request; of course, the processing can also be performed separately and forwarded to the blockchain node for processing.
Step 303: the blockchain node issues the ticket for the user based on the second billing request.
In this embodiment, the block link point may issue a ticket for the user based on the billing information and the like carried by the second billing request, that is, bill the user.
Specifically, when the second billing request carries the allocated ticket identifier, the blockchain node issues the ticket for the user, and the billing information and the ticket identifier may be used as the ticket data of the ticket and stored in the blockchain.
Specifically, the block link point may be used as a bill storage device approved by the tax authority, and also may refer to a bill from the tax authority in advance, and if the second billing request does not carry the distributed bill identifier, then the block link node issues the bill for the user, and the block link node may distribute the bill identifier for the bill with the opening tool, and link up the billing information and the bill identifier as the bill data of the bill, that is, store the bill in the block link.
When a block link point links the bill content, it is generally required that the block link point broadcasts the bill content to other nodes in a block link network, and when the block link points achieve consensus through a consensus mechanism, a block is generated based on the bill content and linked to the previous block to form a block chain. When generating a block based on the ticket content, in order to facilitate subsequent operations such as verification or query on the ticket content, a hash (hash) value is generally generated according to the ticket content and used as an identification identifier of the ticket, and when subsequently verifying or querying the ticket, verification or query can be performed according to the identification identifier. Of course, the ticket may also include other extended contents (i.e., contents not included in the actual contents of the ticket), such as the reimbursement status of the ticket or reimburseable money amount, and may also generate a hash value based on all the contents corresponding to the ticket.
Step 304: and the block chain node sends a first billing response message to the billing system equipment, and the billing system equipment receives the first billing response message.
In the embodiment of the application, after the block link node links the ticket data of the ticket, a first billing response message can be returned to the billing system equipment to notify the billing system equipment that the link is successfully linked. The first billing response message can also carry information such as identification marks of the invoiced bills.
Of course, when the block link point fails to link the ticket data of the ticket, a first ticket issuing response message may also be returned to the billing system device to notify the billing system device of the link failure.
Step 305: and the billing system equipment sends a second billing response message to the terminal equipment, and the terminal equipment receives the second billing response message.
In this embodiment, the billing system device may return a second billing response message to the terminal device to notify that the ticket has been issued and the uplink is successful. The second billing response message may also carry information such as the identification of the invoiced ticket, so that the terminal device may prompt the user to view the identification after receiving the second billing response message.
In the embodiment of the present application, after the bill has been issued, the user holding the bill, that is, the user holding the bill, may apply for reimbursement by using the issued bill, and the following description will be specifically directed to the process of reimbursement of the bill. Fig. 5 is a schematic flow chart of ticket reimbursement.
Step 501: the terminal equipment sends a bill query request to the bill query equipment, and the bill query equipment receives the bill query request.
In the embodiment of the application, when a user wants to query a bill, the following query modes can be provided:
first query mode
When the bill inquiring equipment for inquiring the bills is arranged, the bill holding user can inquire all the bills under the name of the user through the bill inquiring equipment. After the user makes a bill, the bill query device can associate the identification mark of the made bill with the user mark and store the association relation between the user mark and the identification mark, and when the user wants to query the bill owned by the user, the user mark of the user can be provided for query.
Specifically, the bill query device may correspond to a dedicated bill query APP or a bill query website, or provide a query interface for other applications, so that the user may query the own bill through the bill query APP or the bill query website, or query the own bill through the query interface of other applications. Fig. 6 is a schematic diagram of an interface for ticket query. Fig. 6 shows an interface diagram of query by a ticket query APP and query by a public number query entry.
When the user inquires through the bill inquiry APP, the user can enter an inquiry page in the bill inquiry APP and select to inquire the bill, so that the user enters the bill inquiry page on the right side in the figure 6. Similarly, when the user queries through the public number query entry, the user may expand the public number query menu and select the ticket query function in the query menu, thereby entering the ticket query page illustrated on the right side in fig. 6.
In the bill query page, a user can input information related to bill query and operate a query button, correspondingly, the terminal equipment can detect the operation of the user and send a corresponding query operation instruction to a bill query APP or an application where a public account is located, so that a corresponding bill query request is generated based on the query operation instruction and is sent to the bill query equipment. The information related to the ticket query may include a type of the ticket, a type of a user identifier (such as a mobile phone number or an identification number) used for querying the ticket, and a specific user identifier.
In this embodiment, the function of the ticket query device may be associated with a tax authority, for example, the ticket query device may be a device belonging to the tax authority, and in a possible implementation, the ticket query device may be a device of the tax authority or a blockchain node in a blockchain network.
Second query mode
After the user knows the identification mark of the bill, the user can directly inquire the bill corresponding to the identification mark through the identification mark. When inquiring through this kind of mode, the user can directly send out the bill inquiry to block chain link point through terminal equipment, and need not to inquire equipment with the help of the bill, of course, also can send out the bill inquiry to block chain link point through bill inquiry equipment.
Step 502: the bill inquiring equipment inquires the identification associated with the user identification.
In the embodiment of the application, the association relation between the user identification and the identification is stored in the bill query device, so that when the bill query device receives a bill query request, the identification associated with the user identification can be queried according to the user identification carried in the bill query request. Of course, when the user specifies the screening condition of the ticket to be queried, for example, the user specifies to query a specific type of ticket, the ticket querying device may also screen the identification obtained by the query.
Step 503: the bill inquiry equipment sends a bill data inquiry request to the block chain nodes, and the block chain nodes receive the bill data inquiry request.
In the embodiment of the application, because the bill data of the bill is stored in the block chain node, the bill query device can generate the bill data query request according to the identification mark obtained by query, and send the bill data query request to the block chain node, so as to obtain the bill data corresponding to each identification mark from the block chain node.
Step 504: and the block chain node sends a bill data query response message to the bill query device, and the bill query device receives the bill data query response message.
Step 505: and the bill query equipment sends a bill query response message to the terminal equipment, and the terminal equipment receives the bill query response message.
In the embodiment of the application, the block link points can inquire corresponding bill data according to the identification marks, carry the inquired bill data in the bill inquiry response message and send the bill inquiry response message to the bill inquiry equipment, and when the bill inquiry equipment receives the bill inquiry response message, can carry the bill data in the bill inquiry response message and return the bill data to the terminal equipment.
After the terminal device obtains the bill data obtained by query, the bill data can be output on a bill query result page so as to be convenient for a user to view. Fig. 7 is a schematic diagram of a ticket query result page 1 and a ticket splitting page. In the bill query result page 1, the bill abstract of each bill obtained by query can be displayed, and when a user wants to query complete bill data, the user can operate a 'check bill' button or operate a corresponding area of the bill to be checked, so as to check detailed data of the bill.
Step 506: the terminal equipment sends a ticket data splitting request to the block chain nodes, and the block chain nodes receive the ticket data splitting request.
In the embodiment of the application, considering the situation that a ticket holding user may want to request the same electronic ticket to reimburse for different institutions, for example, the user purchases medical insurance of different insurance companies, and the amount of medical invoices issued by the medical institutions may be on one electronic ticket and cannot be provided for two insurance companies to reimburse for reimburse, based on the situation, in the embodiment of the application, the ticket holding user may request a block link point to split one ticket into a plurality of sub-tickets in advance before submitting a reimbursement request.
Specifically, when a bill is to be split for holding a bill, the 'splitting bill' button of the bill to be split can be operated in the bill query result page 1, so that the bill splitting page is entered. In the bill splitting page, a bill holding user can select the splitting number and input information such as the amount of money of each sub-bill, and after the input is finished, a 'splitting confirmation' button is operated, so that the terminal equipment responds to a splitting operation instruction of the bill holding user for the issued bill and sends a bill data splitting request to the block chain link points, wherein the bill splitting request carries the identification mark and the splitting indication information of the issued bill, the identification mark of the issued bill is the identification mark of the bill needing to be split selected by the user, and the splitting indication information is the information such as the splitting number and the amount of money of each sub-bill input by the user.
In fig. 7, two sub-tickets obtained by splitting are specifically taken as an example, and certainly, in practical application, a ticket holding user can select the number of sub-tickets to be split according to the own requirement, which is not limited in the embodiment of the present application.
Step 507: and splitting the initial bill into at least two sub-bills according to the indication of the splitting indication information by the block chain link points.
In the embodiment of the application, the initial bill refers to a bill before splitting, and correspondingly, after the initial bill is split, a plurality of sub-bills can be obtained.
After the block chain node receives the bill splitting request, the initial bill can be split according to the indication of the splitting indication information carried by the bill splitting request, and at least two sub-bills are obtained. The process of splitting the initial bill by the block link point can be regarded as a transaction process, the initial bill is output into at least two sub-bills when the transaction is input, and the block link point can be stored again based on the identification marks of the sub-bills obtained by splitting. The bill contents of each sub-bill are the same as the original bill except the bill surface amount, and the block link points can generate the identification marks of each sub-bill according to the bill contents of each sub-bill obtained by splitting, that is, the bill contents of the sub-bills are the same as the original bill in terms of information such as bill unique marks and the like, the only difference is the bill surface amount, and the sum of the bill surface amounts of each sub-bill is the bill surface amount of the original bill.
The identification may be, for example, a hash value generated based on the content of the ticket.
Based on the characteristics of the UTXO model of the block chain, after the splitting is completed, the initial bill does not exist substantially, and the situation that the user can use the initial bill to reimburse the bill and reimburse the bill repeatedly is avoided.
Step 508: and the block chain node sends a bill splitting response message to the terminal equipment, and the terminal equipment receives the bill splitting response message.
When the bill splitting is completed, the block chain node can carry the bill data of at least two sub-bills obtained by splitting in the bill splitting response message and send the bill data to the terminal equipment, and after the terminal equipment receives the bill splitting response message, the bill data of the at least two sub-bills can be displayed on a display interface for a user to check.
Of course, the split sub-note can be actually regarded as an independent note, and the sub-note can also be split to obtain the sub-note of the sub-note.
It should be noted that, in the embodiment of the present application, the steps 506 to 508 are not essential steps, and may be selected according to actual requirements in practical applications. For example, when the user does not need to reimburse for the sub-ticket, the ticket splitting may not be performed.
Step 509: and the terminal equipment generates a bill reimbursement request based on the to-be-reimbursed bill selected by the bill holding user.
In the embodiment of the application, after the terminal equipment receives the bill splitting response message, the bill data of at least two sub-bills can be displayed on the bill query result page. As shown in fig. 8 and 9, both are schematic views of a user selecting a ticket to be issued.
Fig. 8 and 9 illustrate the presentation of the ticket data of two different sub-tickets, respectively.
Specifically, as shown in the ticket query result page 2 in fig. 8, after the ticket is split, a status display of the ticket may be added in the ticket query result page 2 to prompt the user of the status of the ticket, for example, as shown in the ticket query result page 2, the status of the ticket 1 is "split", that is, the ticket 1 is successfully split, and the status of the ticket 2 is "issued", that is, the ticket 2 is successfully issued, but is not split. When the ticket holder wants to make a ticket reimbursement, the ticket to be reimbursed can be selected to enter a ticket reimbursement page.
Here, the example of the ticket holder reimbursing the ticket 1 in the ticket query result page 2 will be described.
As shown in the ticket reimbursement page 1 in fig. 8, when the user only wants to reimburse the sub-ticket 1 in the ticket 1, the user can select only the sub-ticket 1, that is, only the sub-ticket 1 is used as the ticket to be reimbursed, and after the user inputs the corresponding reimbursement mechanism, the user operates the "reimbursement" button to initiate the reimbursement request. Specifically, the terminal device may detect a selection operation instruction of the ticket-holding user, determine the selected sub-ticket as a to-be-reimbursed ticket, and generate a ticket reimbursement request for the to-be-reimbursed ticket according to the reimbursement enterprise selected by the ticket-holding user in response to the ticket reimbursement operation instruction of the ticket-holding user. The ticket reimbursement request may carry an identification of the ticket to be reimbursed, so that the reimbursement institution may determine the ticket to be reimbursed by the ticket holder, and of course, may also carry other information, such as reimbursement institution information.
As shown in the ticket reimbursement page 2 in fig. 8, when the user only wants to reimburse a plurality of sub-tickets in the ticket 1, the user can select the plurality of sub-tickets, for example, the sub-ticket 1 and the sub-ticket 2 are selected in the ticket reimbursement page 2, and after the user inputs the reimbursement mechanisms corresponding to the sub-tickets, the user operates the "reimbursement" button to initiate a reimbursement request. Specifically, the terminal device may detect a selection operation instruction of the ticket holding user, determine the selected sub-tickets as the to-be-reimbursed tickets, that is, the sub-ticket 1 and the sub-ticket 2, and generate a ticket reimbursement request for each to-be-reimbursed ticket according to the reimbursement enterprise selected by the ticket holding user for each to-be-reimbursed ticket in response to the ticket reimbursement operation instruction of the ticket holding user, that is, may generate the ticket reimbursement request 1 and the ticket reimbursement request 2. The ticket reimbursement request corresponding to each sub-ticket can carry the identification mark of the corresponding sub-ticket, so that the reimbursement mechanism can determine the ticket reimbursed by the ticket holder.
Specifically, as shown in the ticket query result page 3 in fig. 9, after the ticket is split, a sub-ticket may be displayed as an independent ticket in the ticket query result page 3. In order to facilitate the ticket holder to distinguish the tickets, the reimburseable amount of each ticket can be displayed in the ticket query result page 3. As shown in the bill query result page 3, the bill unique codes of the sub-bill 1 and the sub-bill 2 are the same, but the reimburseable amount is different, so that the user holding the bill can distinguish the bills according to the reimburseable amount.
When the ticket holder wants to make a ticket reimbursement, the ticket to be reimbursed can be selected to enter a ticket reimbursement page.
For example, when the user wants to submit a cancellation for ticket 1, then sub-ticket 1 can be selected to enter ticket cancellation page 3, and ticket cancellation page 3 can show that "the sub-ticket amount is 60", and after inputting the corresponding cancellation mechanism in ticket cancellation page 3, operate the "cancellation" button to initiate a cancellation request. The terminal equipment can detect the selection operation instruction of the ticket holding user, determine the selected sub-ticket as the to-be-reimbursed ticket, respond to the ticket reimbursement operation instruction of the ticket holding user, and generate a ticket reimbursement request for the to-be-reimbursed ticket according to the reimbursement enterprise selected by the ticket holding user.
Or, when the user wants to reimburse the ticket 2, the user may select the ticket 2 to enter the ticket reimbursement page 4, and the ticket reimbursement page 4 may display "the ticket amount is 500" and operate the "reimbursement" button to initiate a reimbursement request after inputting the corresponding reimbursement mechanism in the ticket reimbursement page 4. The terminal equipment can detect the selection operation instruction of the ticket holding user, determine the selected ticket as the ticket to be reimbursed, respond to the ticket reimbursement operation instruction of the ticket holding user, and generate a ticket reimbursement request for the ticket to be reimbursed according to the reimbursement enterprise selected by the ticket holding user.
As shown in fig. 10, the operation of reimbursing a plurality of tickets for the ticket holder is schematically illustrated. When a ticket holder wants to simultaneously claim a plurality of tickets, a plurality of tickets can be selected in the ticket query result page 3, and the sub-ticket 1 and the sub-ticket 2 are selected as shown in 10. Specifically, the bill query result page 3 can initially display a bill selection box, and a user holding the bill can directly operate the selection box to select the bill; or, the ticket query result page 3 may not display the ticket selection frame initially, and after the ticket holding user performs a predetermined operation on the selection frame, for example, long-time pressing, the selection frame is displayed in the ticket query result page 3, and the ticket holding user operates the selection frame to select the ticket. After the ticket holding user selects the ticket, the operation of applying for reimbursement can be carried out, the terminal equipment can detect the selection operation instruction of the ticket holding user, the selected ticket is determined as the ticket to be reimbursed, the terminal equipment jumps to the ticket reimbursement page 5, and after the ticket holding user can input reimbursement mechanisms corresponding to the tickets in the ticket reimbursement page 5, the terminal equipment operates a reimbursement button to initiate a reimbursement request. The terminal equipment can respond to the bill reimbursement operation instruction of the ticket holding user and respectively generate a bill reimbursement request for each to-be-reimbursed bill according to the reimbursement enterprise selected by the ticket holding user for each to-be-reimbursed bill.
Step 510: the terminal equipment sends a bill reimbursement request to the bill reimbursement system, and the bill reimbursement system equipment receives the bill reimbursement request.
After the terminal device generates the ticket reimbursement request, the generated ticket reimbursement request can be sent to the ticket reimbursement system.
When the ticket holder selects only one ticket to be reimbursed, the ticket reimbursement request can be sent to a ticket reimbursement system of a reimbursement mechanism selected for the ticket by the ticket holder, as shown in a ticket reimbursement page 1 in fig. 8, the terminal equipment can send the ticket reimbursement request to a ticket reimbursement system of an enterprise A to request the enterprise A to reimburse the amount of the ticket 1 for the ticket holder; when the ticket checking user selects a plurality of tickets to be checked out, the ticket checking request can be respectively sent to the ticket checking system of the checking mechanism selected by the ticket checking user for each ticket, as shown in a ticket checking page 2 in fig. 8, the terminal device can respectively send the ticket checking requests of the sub-ticket 1 and the sub-ticket 2 to the ticket checking system of the enterprise a and the ticket checking system of the enterprise B, so as to respectively request the enterprise a to check out the amount of the ticket 1 for the ticket checking user and request the enterprise B to check out the amount of the ticket 2 for the ticket checking user, thereby realizing parallel checking out of the tickets and improving the ticket checking efficiency.
Step 511: the terminal equipment sends a ticket data transfer request to the block chain nodes, and the block chain nodes receive the ticket data transfer request.
In the embodiment of the present application, the terminal device sends a ticket transfer request to the block link node, and may include various embodiments.
First mode
Step 5111: and the terminal equipment sends a ticket data transfer request to the block chain nodes.
As shown in step 5111 in fig. 5, the terminal may send a ticket reimbursement request to the ticket reimbursement system before sending the ticket reimbursement request to the ticket reimbursement system, or the terminal may send a ticket transfer request to the blockchain node actively after sending the ticket reimbursement request to the ticket reimbursement system to request the blockchain node to transfer the right of possession of the ticket to be reimbursed from the ticket holder to the reimbursement authority.
Second mode
Step 5112: and the terminal equipment receives a bill data acquisition request sent by the bill reimbursement system equipment.
Step 5113: and the terminal equipment sends a ticket data transfer request to the block chain nodes.
After the terminal device sends the ticket reimbursement request to the ticket reimbursement system, as shown in steps 5112 and 5113 in fig. 5, since the ticket reimbursement system device does not possess the right of holding the ticket to be reimbursed, the ticket reimbursement system device may send the ticket data acquisition request to the terminal device, or alternatively, the ticket reimbursement system device may attempt to acquire the ticket content of the ticket to be reimbursed to the block link point, and send the ticket data acquisition request to the terminal device when the ticket content acquisition fails. The terminal device may send a ticket transfer request to the block link point after receiving the ticket content acquisition request, so as to request the block link point to transfer the right of possession of the to-be-reimbursed ticket from the ticket holding user to the reimbursement mechanism.
In the first mode or the second mode, after the right of possession of the to-be-reimbursed ticket is transferred successfully, the block link point may send a response message indicating that the transfer is successful to the terminal device, so that the terminal device may notify the ticket reimbursement system device to start executing a subsequent reimbursement process.
Third mode
Step 5114: and the terminal equipment sends authorization indication information to the bill reimbursement system.
Step 5115: the bill reimbursement system equipment sends a bill transfer request to the block link points.
As shown in steps 5114 and 5115 in fig. 5, the terminal device may send authorization indication information authorizing to transfer the right of holding of the to-be-reimbursed ticket to the ticket reimbursement system at the same time or after sending the ticket reimbursement request to the ticket reimbursement system, so that when the ticket reimbursement system device obtains the authorization indication information, it may send a ticket data transfer request to the block link point according to the authorization indication information to request the block link point to transfer the right of holding of the to-be-reimbursed ticket from the ticket holding user to the reimbursement mechanism.
The authorization indication information can be carried in the bill reimbursement request and sent to the bill reimbursement system.
In a third mode, after the ownership of the transfer to-be-reimbursed bill is successful, the block link point may directly send a response message indicating that the transfer is successful to the bill reimbursement system device.
In this embodiment of the present application, step 511 and step 510 do not have a substantial precedence relationship, and in practical applications, step 511 and step 510 may be executed in a precedence order, for example, step 511 is executed first, or step 510 is executed first, or step 511 and step 510 may also be executed simultaneously, which is not limited in this embodiment of the present application.
In the embodiment of the application, the process that the block link point transfers the holding authority of the to-be-reimbursed bill from the bill holding user to the reimbursement mechanism can also be regarded as a one-time transaction process, namely, the to-be-reimbursed bill can be regarded as an asset of the bill holding user, and then the transfer process is a process that the bill holding user transacts the to-be-reimbursement bill to the reimbursement mechanism. Whereas in the blockchain, the ticketing users and the reimbursement authorities are usually represented by addresses, the transfer process is the process of trading the reimbursement instruments from the device address of the ticketing user to the device address of the reimbursement authority.
Step 512: the bill reimbursement system equipment sends a bill acquisition request to the block link points, and the block link points receive the bill acquisition request.
In the embodiment of the application, when the bill reimbursement system device reimburses the bill, the bill data of the to-be-reimbursed bill needs to be acquired, so that the bill data is audited, and after the bill is transferred, namely the to-be-reimbursed bill is transferred to the reimbursement mechanism from the bill holding user, the reimbursement mechanism has the holding authority of the to-be-reimbursed bill, namely the reimbursement mechanism can acquire the bill data of the to-be-reimbursed bill from the block chain link point, so that the bill reimbursement system device can send a bill data acquisition request to the block chain link point to acquire the bill data of the to-be-reimbursed. The ticket acquiring request can carry the identification of the ticket to be reimbursed.
Step 513: and searching the bill data of the bill to be reimbursed according to the identification mark by the block chain node.
In the embodiment of the application, after receiving the bill acquisition request sent by the bill reimbursement system device, the block chain node can respond to the bill acquisition request and search the bill data of the bill to be reimbursed from the bill data of the authority possessed by the reimbursement enterprise according to the identification mark carried by the bill acquisition request.
Step 514: and the block chain link point sends the bill data of the bill to be reimbursed to the bill reimbursement system equipment.
Step 515: and the bill reimbursement system equipment reimburses the bills according to the bill data of the bills to be reimbursed.
In the embodiment of the application, the bill reimbursement system equipment can audit the bill to be reimbursed according to the bill data of the bill to be reimbursed so as to determine whether the bill to be reimbursed is reimbursed. For example, the ticket reimbursement system device can audit whether the consumption of the ticket to be reimbursed is within the reimbursement range, whether the reimbursement amount exceeds the amount that can be reimbursed by the ticket holder, and the like.
Step 516: the bill reimbursement system equipment sends a bill reimbursement response message to the terminal equipment, and the terminal equipment receives the bill reimbursement response message.
In the embodiment of the application, after the ticket reimbursement system device audits and reimburses the to-be-reimbursed ticket, a ticket reimbursement response message carrying a reimbursement result can be returned to the terminal device, and the reimbursement result is used for indicating whether reimbursement is successful or not.
Specifically, in order to indicate that the ticket to be reimbursed has been reimbursed more definitely, when the reimbursement of the ticket to be reimbursed is completed, the method may further include adding indication information indicating that the ticket to be reimbursed has been reimbursed in ticket data of the ticket to be reimbursed, and sending the reimbursement result and the ticket data including the indication information to the terminal device together with the ticket reimbursement response message. If the user does not need to leave the reimbursed bill as a stub, the reimbursed bill does not need to be returned to the terminal equipment.
The indication information may be that the reimburseable amount is 0, that is, a bill with an amount of 0 is returned to the user, or the indication information may be that the bill status is reimbursed.
In the embodiment of the application, if the to-be-reimbursed bill is successfully reimbursed, the reimbursed bill storage request is sent to the block link point, and the reimbursed bill storage request is used for requesting the block link point to store bill data including indication information indicating reimbursed of the to-be-reimbursed bill.
In the embodiment of the application, the billing mechanism bills or the reimbursement mechanism reimburses the invoice and is not limited to the billing mechanism or the reimbursement mechanism, and the invoice can be issued by a government or other mechanisms and can be set according to actual conditions.
The following describes a scheme of the embodiment of the present application with a specific example of ticket reimbursement.
Referring to FIG. 11, a flow chart of a method for applying for reimbursing a ticket for a user is shown.
Step 1101: and the terminal equipment sends a ticket data transfer request to the block chain link point based on the to-be-reimbursed ticket selected by the ticket holding user.
Step 1102: and the block chain node informs the terminal equipment of a bill transfer response message indicating successful transfer.
Step 1103: and the terminal equipment sends a bill reimbursement request to a bill reimbursement system of the block link point reimbursement mechanism.
The ticket reimbursement request carries the identification of the ticket to be reimbursed.
Step 1104: and the bill reimbursement system equipment sends a bill acquisition request to the block link points.
Step 1105: and the block chain node sends the bill data of the bill to be reimbursed to the bill reimbursement system equipment.
Step 1106: and the bill reimbursement system equipment reimburses the bills according to the bill data of the bills to be reimbursed.
Step 1107: and the bill reimbursement system equipment returns a bill reimbursement response message to the terminal equipment.
Wherein, the ticket reimbursement response message can carry the data of the ticket with the amount of zero.
Referring to FIG. 12, another flow diagram is shown for a user applying for reimbursing a ticket.
Step 1201: and the terminal equipment sends a ticket reporting and selling request to the block chain link points based on the to-be-reported ticket selected by the ticket holding user.
The ticket reimbursement request carries the identification of the to-be-reimbursed ticket and authorization indication information for authorizing the transfer of the holding authority of the to-be-reimbursed ticket.
Step 1202: the bill reimbursement system equipment sends a bill transfer request to the block link points.
Step 1203: and the block chain node informs the bill reimbursement system equipment of a bill transfer response message indicating successful transfer.
Step 1204: and the bill reimbursement system equipment sends a bill acquisition request to the block link points.
Step 1205: and the block chain node sends the bill data of the bill to be reimbursed to the bill reimbursement system equipment.
Step 1206: and the bill reimbursement system equipment reimburses the bills according to the bill data of the bills to be reimbursed.
Step 1207: and the bill reimbursement system equipment returns a bill reimbursement response message to the terminal equipment.
Wherein, the ticket reimbursement response message can carry the data of the ticket with the amount of zero.
Referring to FIG. 13, another flow diagram for a user applying for reimbursing a ticket is shown.
Step 1301: and the terminal equipment sends a ticket reporting and selling request to the block chain link points based on the to-be-reported ticket selected by the ticket holding user.
The ticket reimbursement request carries the identification of the ticket to be reimbursed.
Step 1302: and the bill reimbursement system equipment sends a bill data acquisition request to the terminal equipment.
Step 1303: and the terminal equipment sends a ticket data transfer request to the block chain link point based on the to-be-reimbursed ticket selected by the ticket holding user.
Step 1304: and the block chain node informs the terminal equipment of a bill transfer response message indicating successful transfer.
Step 1305: and the bill reimbursement system equipment sends a bill acquisition request to the block link points.
The bill reimbursement system equipment can send a bill acquisition request to the block link points when receiving the indication of the terminal equipment; or periodically send a ticket acquisition request to the block link point to attempt to acquire ticket data for the pending ticket from the block link point.
Step 1306: and the block chain node sends the bill data of the bill to be reimbursed to the bill reimbursement system equipment.
Step 1307: and the bill reimbursement system equipment reimburses the bills according to the bill data of the bills to be reimbursed.
Step 1308: and the bill reimbursement system equipment returns a bill reimbursement response message to the terminal equipment.
Wherein, the ticket reimbursement response message can carry the data of the ticket with the amount of zero.
Please refer to fig. 14, which is a flow chart illustrating a sub-ticket for a user application.
Step 1401: and the terminal equipment sends a ticket data splitting request to the block chain link point based on the issued ticket selected by the ticket holding user.
Step 1402: the block chain link point divides the issued bill into at least two sub-bills.
Step 1403: and the block chain node informs the terminal equipment of a bill splitting response message indicating successful splitting.
Step 1404: and the terminal equipment sends a ticket data transfer request to the block chain link point based on the to-be-reimbursed ticket selected by the ticket holding user.
Wherein, the ticket to be reimbursed here is one of the at least two sub-tickets.
Step 1405: and the block chain node informs the terminal equipment of a bill transfer response message indicating successful transfer.
Step 1406: and the terminal equipment sends a bill reimbursement request to a bill reimbursement system of the block link point reimbursement mechanism.
The ticket reimbursement request carries the identification of the ticket to be reimbursed.
Step 1407: and the bill reimbursement system equipment sends a bill acquisition request to the block link points.
Step 1408: and the block chain node sends the bill data of the bill to be reimbursed to the bill reimbursement system equipment.
Step 1409: and the bill reimbursement system equipment reimburses the bills according to the bill data of the bills to be reimbursed.
Step 1410: and the bill reimbursement system equipment returns a bill reimbursement response message to the terminal equipment.
Wherein, the ticket reimbursement response message can carry the data of the ticket with the amount of zero.
Please refer to fig. 15, which is a schematic flow chart illustrating a process of applying for a plurality of reimbursement agencies to reimburse a plurality of tickets respectively for a user.
Step 1501: and the terminal equipment sends a ticket data splitting request to the block chain link point based on the issued ticket selected by the ticket holding user.
Here, the ticket splitting request splits the issued ticket into a sub-ticket a and a sub-ticket B.
Step 1502: the block chain link point divides the issued bill into a sub-bill A and a sub-bill B.
Step 1503: and the block chain node informs the terminal equipment of a bill splitting response message indicating successful splitting.
The bill splitting response message can carry bill data with the sub-bill A and the sub-bill B, the bill data can comprise identification marks and bill contents, the other bill contents except the bill outlet amount of the sub-bill A and the sub-bill B are identical, and the identification marks of the sub-bill A and the sub-bill B can be generated according to the bill contents of the sub-bill A and the sub-bill B respectively.
Step 1504: and the terminal equipment sends a ticket data transfer request to the block chain nodes.
Wherein the ticket transfer request is for requesting that sub-ticket a be transferred to enterprise a and that sub-ticket B be transferred to enterprise B.
Step 1505: and the block chain node informs the terminal equipment of a bill transfer response message indicating successful transfer.
Step 1506: and the terminal equipment respectively generates bill reimbursement requests for the sub-bills.
That is, the ticket transfer request a is generated based on the business a selected for the sub ticket a, and the ticket transfer request B is generated based on the business B selected for the sub ticket B.
Step 1507: and the terminal equipment sends the bill transfer request A to a bill reimbursement system A of the enterprise A.
The bill transfer request A carries the identification of the sub-bill A.
Step 1508: the bill reimbursement system A equipment sends a bill acquisition request A to the block link points.
Step 1509: and the block chain node sends the bill data of the sub-bill A to the bill reimbursement system A equipment.
Step 1510: and the bill reimbursement system A equipment reimburses the bills according to the bill data of the sub-bills A.
Step 1511: and the bill reimbursement system A equipment returns a bill reimbursement response message A to the terminal equipment.
Wherein, the ticket reimbursement response message A can carry the ticket data of the sub-ticket A with the amount of zero.
Step 1512: and the terminal equipment sends the bill transfer request B to a bill reimbursement system B of the enterprise B.
Wherein, the bill transfer request B carries the identification of the sub-bill B.
Step 1513: and the bill reimbursement system B equipment sends a bill acquisition request B to the block link points.
Step 1514: and the block chain node sends the bill data of the sub-bill B to the bill reimbursement system B equipment.
Step 1515: and the bill reimbursement system B equipment reimburses the bills according to the bill data of the sub-bills B.
Step 1516: and the bill reimbursement system B equipment returns a bill reimbursement response message B to the terminal equipment.
Wherein, the ticket reimbursement response message can carry the ticket data of the sub-ticket B with the amount of zero.
The processes of steps 1507 to 1511 are performed in parallel with the processes of steps 1512 to 1516.
In summary, the bill reimbursement method provided in the embodiment of the present application utilizes the characteristics of the UTXO model that the bill to be reimbursed does not exist after the transaction, and transfers the bill to be reimbursed to the reimbursement mechanism when reimbursement is performed, so that the user holding the bill cannot perform secondary reimbursement, and one bill is over-submitted or multiple-submitted in the house. And a note can be split into a plurality of small-amount notes to be simultaneously reimbursed, so that reimbursement efficiency is improved.
Referring to fig. 16, based on the same inventive concept, an embodiment of the present application further provides a ticket reimbursement apparatus 160, applied to a terminal device, including:
a first sending unit 1601, configured to send a ticket reimbursement request to a ticket reimbursement system of a reimbursement enterprise in response to a ticket reimbursement operation instruction of a ticket holder; the ticket reimbursement request carries an identification mark of a to-be-reimbursed ticket, and is used for requesting the ticket reimbursement system to reimburse the to-be-reimbursed ticket; sending a ticket data transfer request to the block chain nodes to request the block chain nodes to transfer the holding authority of the to-be-reimbursed ticket from the ticket holding user to the reimbursement enterprise; wherein, the block chain link point stores the bills to be reimbursed;
the obtaining unit 1602, configured to obtain a reimbursement result of a to-be-reimbursed bill according to a bill reimbursement response message that is sent by a bill reimbursement system and carries a reimbursement result of the to-be-reimbursed bill.
Alternatively to this, the first and second parts may,
the first sending unit 1601 is further configured to send a first invoicing request to an invoicing system of an invoicing enterprise in response to the invoicing operation instruction, where the invoicing request carries invoicing information required by an invoicing ticket;
the obtaining unit 1602, configured to obtain an invoicing result according to the invoicing response message sent by the invoicing system; and the billing response message is generated according to the billing result returned by the block chain node after the billing system sends the second billing request to the block chain node according to the billing information.
Optionally, the invoicing operation instruction is used to instruct to issue multiple tickets for one transaction, and the first invoicing request includes a first invoicing sub-request corresponding to each ticket to be issued, then the first sending unit 1601 is specifically configured to:
and respectively generating first invoicing sub-requests corresponding to the to-be-invoiced bills according to the invoicing information and the money amount of the to-be-invoiced bills, and sending the first invoicing sub-requests to the invoicing system.
Optionally, the ticket to be reimbursed includes a sub-ticket split from the issued ticket;
the first sending unit 1601 is further configured to send a ticket data splitting request to the block link point in response to a splitting operation instruction of a ticket holding user for an issued ticket, where the ticket splitting request carries an identification of the issued ticket and splitting instruction information, and is used to request that an initial ticket to be split is split into at least two sub-tickets according to the instruction of the splitting instruction information;
the obtaining unit 1602 is further configured to obtain the ticket data of at least two sub-tickets obtained through splitting according to a ticket splitting response message sent by the block chain node when the ticket splitting is successful, where an identification identifier of each sub-ticket is generated based on the ticket content of each sub-ticket obtained through splitting, and other ticket contents except the ticket amount in the ticket content of each sub-ticket are the same as the initial ticket.
Optionally, the apparatus further comprises a determining unit 1603;
the determination unit 1603 is configured to determine the selected sub-ticket as the reimbursement ticket in response to a selection operation instruction of the ticket holding user to select the reimbursement ticket from the at least two sub-tickets.
Optionally, when the ticket to be reimbursed includes a plurality of sub-tickets, the first sending unit 1601 is further configured to:
and respectively generating reimbursement requests for the sub-bills according to reimbursement enterprises selected by the bill holding users for the sub-bills, and sending the reimbursement requests to bill reimbursement systems of the corresponding reimbursement enterprises.
Alternatively to this, the first and second parts may,
the first sending unit 1601 is further configured to send a ticket query request to the ticket query device in response to a ticket query operation instruction of the ticket-holding user, where the ticket query request carries a user identifier of the ticket-holding user;
the obtaining unit 1602, configured to obtain a ticket query result according to a ticket query response message sent by the ticket query device; the bill query device stores the association relationship between the user identifier and the identification identifier, and the bill query result comprises bill data acquired from the block chain node according to the identification identifier obtained by querying after the bill query device obtains the identification identifier associated with the user identifier according to the association relationship.
Optionally, the first sending unit 1601 is specifically configured to:
when a bill data acquisition request of a bill reimbursement system is received, a bill data transfer request is sent to a block link point; alternatively, the first and second electrodes may be,
sending a bill transfer request to the block link points through a bill reimbursement system; when the bill reimbursement system acquires authorization indication information of the holding authority of the bill to be reimbursed, a bill transfer request is sent to the block link points according to the authorization indication information.
The apparatus may be configured to execute the method related to the terminal device side in the embodiments shown in fig. 3 to fig. 15, and therefore, for functions and the like that can be realized by each functional module of the apparatus, reference may be made to the description of the embodiments shown in fig. 3 to fig. 15, which is not described in detail. The determination unit 1603 is not an optional functional unit and is therefore shown in fig. 16 by a dotted line.
Referring to fig. 17, based on the same inventive concept, an embodiment of the present application further provides a ticket reimbursement device 170, applied to a ticket reimbursement system of a reimbursement enterprise, the device including:
a receiving unit 1701 for receiving a ticket reimbursement request sent by a terminal device; the ticket reimbursement request carries an identification mark of a to-be-reimbursed ticket, and is used for requesting reimbursement of the to-be-reimbursed ticket;
a second obtaining unit 1702, configured to obtain, according to the identification, ticket data of the to-be-reimbursed ticket from the block link point; the ticket data of the to-be-reimbursed ticket is obtained by searching the ticket data of the to-be-reimbursed ticket with the authority limit according to the identification mark after the ticket data of the to-be-reimbursed ticket is transferred to the reimbursement enterprise from the ticket holding user for the block link point;
and a ticket reimbursement unit 1703, configured to reimburse the ticket data of the ticket to be reimbursed, and send a ticket reimbursement response message carrying a reimbursement result to the terminal device.
Optionally, the ticket reimbursement unit 1703 is specifically configured to:
when the reimbursement of the to-be-reimbursed bill is completed, adding indication information for indicating that the to-be-reimbursed bill has been reimbursed in bill data of the to-be-reimbursed bill;
and carrying the reimbursement result and the bill data including the indication information in a bill reimbursement response message and sending the bill reimbursement response message to the terminal equipment.
Optionally, the apparatus further comprises a second sending unit 1704, configured to:
and if the to-be-reimbursed bill is successfully reimbursed, sending a reimbursed bill storage request to the block link point, wherein the reimbursed bill storage request is used for requesting the block link point to store bill data comprising indication information indicating reimbursed of the to-be-reimbursed bill.
The device may be configured to execute the method related to the ticket reimbursement system side in the embodiments shown in fig. 3 to 15, and therefore, for functions and the like that can be realized by each functional module of the device, reference may be made to the description of the embodiments shown in fig. 3 to 15, which is not described in detail. The second sending unit 1704 is not an essential functional unit, and is shown by a dotted line in fig. 17.
Referring to fig. 18, based on the same inventive concept, an embodiment of the present application further provides a ticket reimbursement apparatus 1801, applied to a blockchain node, including:
a bill transfer unit 1801, configured to transfer, in response to a bill transfer request, a right of possession of a to-be-reimbursed bill from a bill holding user to a reimbursement enterprise;
the bill searching unit 1802 is used for responding to a bill acquisition request sent by a bill reimbursement system of a reimbursement enterprise, and searching bill data of a bill to be reimbursed from the bill data of the reimbursement enterprise with authority according to an identification mark carried by the bill acquisition request;
a third sending unit 1803, configured to send the ticket data of the ticket to be reimbursed to the ticket reimbursement system, so that the ticket reimbursement system reimburses the ticket according to the ticket data of the ticket to be reimbursed.
Optionally, the apparatus further includes a ticket splitting unit 1804 and an identifier generating unit 1805;
the bill splitting unit 1804 is configured to split the issued bill into at least two sub-bills according to an indication of splitting indication information carried in the bill splitting request, in response to the bill splitting request sent by the terminal device; the bill contents of each sub-bill are the same as the initial bill except the bill surface amount;
an identifier generating unit 1805, configured to generate an identifier of each sub-ticket according to the ticket content of each sub-ticket;
a third sending unit 1803, further configured to carry the ticket data of the at least two sub-tickets in the ticket splitting response message, and send the ticket data to the terminal device; the ticket data includes an identification and a ticket content.
The device may be configured to execute the method related to the block link point side in the embodiment shown in fig. 3 to 15, and therefore, for functions and the like that can be realized by each functional module of the device, reference may be made to the description of the embodiment shown in fig. 3 to 15, which is not described in detail. Note that the ticket splitting unit 1804 and the identification generation unit 1805 are not indispensable functional units, and are shown by broken lines in fig. 17.
Referring to fig. 19, based on the same technical concept, an embodiment of the present application further provides a computer device 190, which may include a memory 1901 and a processor 1902.
The memory 1901 is used for storing computer programs executed by the processor 1902. The memory 1901 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required for at least one function, and the like; the storage data area may store data created according to use of the computer device, and the like. The processor 1902, may be a Central Processing Unit (CPU), or a digital processing unit, etc. The specific connection medium between the memory 1901 and the processor 1902 is not limited in this embodiment. In the embodiment of the present application, the memory 1901 and the processor 1902 are connected by a bus 1903 in fig. 19, the bus 1903 is represented by a thick line in fig. 19, and the connection manner between other components is only schematically illustrated and is not limited thereto. The bus 1903 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 19, but it is not intended that there be only one bus or one type of bus.
The memory 1901 may be a volatile memory (volatile memory), such as a random-access memory (RAM); the memory 1901 may also be a non-volatile memory (non-volatile memory) such as, but not limited to, a read-only memory (rom), a flash memory (flash memory), a Hard Disk Drive (HDD) or a solid-state drive (SSD), or the memory 1901 may be any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory 1901 may be a combination of the above memories.
A processor 1902, configured to execute the method according to the embodiment shown in fig. 3 to fig. 15 when the computer program stored in the memory 1901 is called.
In some possible embodiments, various aspects of the methods provided herein may also be implemented in the form of a program product including program code for causing a computer device to perform the steps of the methods according to various exemplary embodiments of the present application described above in this specification when the program product is run on the computer device, for example, the computer device may perform the methods according to the embodiments shown in fig. 3-15.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims (11)

1. A bill reimbursement method is applied to terminal equipment and comprises the following steps:
responding to a bill reimbursement operation instruction of requesting reimbursement on a plurality of bills to be reimbursed by a bill holding user, and respectively sending bill reimbursement requests to bill reimbursement systems of reimbursement enterprises designated for the bills to be reimbursed; the bill reimbursement system can acquire corresponding bill data of the bills to be reimbursed from the bills with the authority stored in the block link points through the identification marks; and
sending a bill transfer request to the blockchain nodes to request the blockchain nodes to transfer the holding authority of each to-be-reimbursed bill from the bill holding user to an reimbursement enterprise appointed for each to-be-reimbursed bill; wherein the blockchain node stores the plurality of tickets to be reimbursed;
and acquiring the reimbursement result of each to-be-reimbursed bill according to the bill reimbursement response message which is sent by each bill reimbursement system and carries the reimbursement result of the to-be-reimbursed bill.
2. The method of claim 1, wherein the plurality of backout tickets include sub-tickets split from issued tickets, the method further comprising, prior to a ticketing operation indication to back out the plurality of backout tickets in response to a ticketing user's request:
responding to a splitting operation instruction of the ticket holding user for the issued ticket, sending a ticket splitting request to the block chain node, wherein the ticket splitting request carries an identification mark of an initial ticket to be split and splitting instruction information and is used for requesting to split the initial ticket into at least two sub-tickets according to the instruction of the splitting instruction information;
acquiring bill data of at least two sub-bills obtained by splitting according to a bill splitting response message sent by the block chain node when the bill is successfully split; the bill data comprises identification marks and bill contents, the identification marks of the sub-bills are generated based on the bill contents of the sub-bills obtained through splitting, and the bill contents of the sub-bills are the same as the initial bills except for the bill surface amount.
3. The method of claim 2, wherein after obtaining the ticket data of at least two sub-tickets obtained by splitting according to the ticket splitting response message sent by the blockchain node when the ticket splitting is successful, the method further comprises:
displaying bill data of the bill with the authority possessed by the bill holding user on a display page, wherein the bill with the authority possessed by the bill holding user comprises the at least two sub-bills;
in response to a selection operation instruction of the ticket holding user for selecting a to-be-printed ticket from tickets of which the ticket holding user has authority, determining the selected ticket as the to-be-printed ticket; the selected bills comprise one or more of the undisassembled bills and/or one or more of the at least two sub-bills.
4. The method of claim 3, wherein displaying ticket data for tickets to which the ticketing user has rights on a display page comprises:
displaying the current state of each bill on a display page; alternatively, the first and second electrodes may be,
and displaying the reimburseable amount of each bill on the display page.
5. The method of claim 1, wherein the method further comprises:
responding to a bill query operation instruction of the bill holding user, and sending a bill query request to the block link points, wherein the bill query request carries an identification mark of a bill to be queried;
acquiring a bill query result according to a bill query response message sent by the block chain node; and the bill query result is obtained by searching the block link points from the bills which the bill-holding user has the authority according to the identification marks.
6. A bill reimbursement method is applied to a blockchain node, and comprises the following steps:
in response to the bill transfer request, respectively transferring the holding authority of each to-be-reimbursed bill from the bill holding user to the reimbursement enterprises designated for each to-be-reimbursed bill;
in response to a bill acquisition request sent by a bill reimbursement system of each reimbursement enterprise, searching a corresponding bill to be reimbursed from bills with authority of the reimbursement enterprise according to an identification mark carried by the bill acquisition request;
and sending the searched bill data of the bill to be reimbursed to the corresponding bill reimbursement system so that each bill reimbursement system reimburses the bill according to the received bill data of the bill to be reimbursed.
7. The method of claim 6, wherein the method further comprises:
responding to a bill splitting request sent by a terminal device, and carrying out transaction of an initial bill corresponding to an identification mark carried by the bill splitting request according to an indication of splitting indication information carried by the bill splitting request; the transaction is a process of acquiring at least two sub-bills through the initial bill transaction owned by the bill-holding user, and after the transaction is completed, the bill-holding user loses the holding authority of the initial bill.
8. A bill reimbursement device is applied to terminal equipment and comprises:
the system comprises a first sending unit, a second sending unit and a third sending unit, wherein the first sending unit is used for responding to a bill reimbursement operation instruction of a bill reimbursement user requesting reimbursement of a plurality of bills to be reimbursed and respectively sending bill reimbursement requests to a bill reimbursement system of a reimbursement enterprise designated for each bill to be reimbursed; the bill reimbursement system can acquire corresponding bill data of the bills to be reimbursed from the bills with the authority stored in the block link points through the identification marks; and sending a ticket data transfer request to the block chain nodes to request the block chain nodes to transfer the holding authority of each to-be-reimbursed ticket from the ticket holding user to the reimbursement enterprises designated for each to-be-reimbursed ticket; the block chain node stores the to-be-reimbursed bill;
the first acquisition unit is used for acquiring the reimbursement result of each to-be-reimbursed bill according to the bill reimbursement response message which is sent by each bill reimbursement system and carries the reimbursement result of the to-be-reimbursed bill.
9. A bill reimbursement device, applied to a blockchain node, comprising:
the bill transfer unit is used for responding to the bill transfer request and respectively transferring the holding authority of each bill to be reimbursed from the bill holding user to the reimbursement enterprises appointed for each bill to be reimbursed;
the bill searching unit is used for responding to bill acquisition requests sent by bill reimbursement systems of reimbursement enterprises and searching corresponding bills to be reimbursed from the bills with authority of the reimbursement enterprises according to identification marks carried by the bill acquisition requests;
and the second sending unit is used for sending the searched bill data of the bill to be reimbursed to the corresponding bill reimbursement system so that each bill reimbursement system reimburses the bill according to the received bill data of the bill to be reimbursed.
10. A computer device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor,
the processor, when executing the program, implements the method of any of claims 1-5 or 6-7.
11. A computer-readable storage medium having stored thereon processor-executable instructions,
the processor-executable instructions, when executed by a processor, are for implementing a method as claimed in any one of claims 1 to 5 or 6 to 7.
CN201910936215.7A 2019-08-08 2019-08-08 Bill reimbursement method, device and equipment and computer storage medium Active CN110599276B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201910936215.7A CN110599276B (en) 2019-08-08 2019-08-08 Bill reimbursement method, device and equipment and computer storage medium
CN201910730645.3A CN110458562B (en) 2019-08-08 2019-08-08 Bill reimbursement method, device and equipment and computer storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910936215.7A CN110599276B (en) 2019-08-08 2019-08-08 Bill reimbursement method, device and equipment and computer storage medium

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
CN201910730645.3A Division CN110458562B (en) 2019-08-08 2019-08-08 Bill reimbursement method, device and equipment and computer storage medium

Publications (2)

Publication Number Publication Date
CN110599276A CN110599276A (en) 2019-12-20
CN110599276B true CN110599276B (en) 2021-07-06

Family

ID=68485506

Family Applications (2)

Application Number Title Priority Date Filing Date
CN201910936215.7A Active CN110599276B (en) 2019-08-08 2019-08-08 Bill reimbursement method, device and equipment and computer storage medium
CN201910730645.3A Active CN110458562B (en) 2019-08-08 2019-08-08 Bill reimbursement method, device and equipment and computer storage medium

Family Applications After (1)

Application Number Title Priority Date Filing Date
CN201910730645.3A Active CN110458562B (en) 2019-08-08 2019-08-08 Bill reimbursement method, device and equipment and computer storage medium

Country Status (1)

Country Link
CN (2) CN110599276B (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111275462A (en) * 2020-01-22 2020-06-12 腾讯科技(深圳)有限公司 Bill verification method and device based on block chain network and storage medium
CN111260488A (en) * 2020-01-23 2020-06-09 腾讯科技(深圳)有限公司 Data processing method and device and readable storage medium
CN111444209A (en) * 2020-03-25 2020-07-24 腾讯科技(深圳)有限公司 Data processing method, device, equipment and medium based on block chain

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106600394A (en) * 2016-12-29 2017-04-26 百望电子发票数据服务有限公司 Method and system for reimbursement recording of electronic proof
CN106952153A (en) * 2017-03-13 2017-07-14 广东网金控股股份有限公司 A kind of method of charging out based on block chain
CN106952124A (en) * 2017-03-16 2017-07-14 北京牛链科技有限公司 Electronic bill management system and method based on distribution book keeping operation
CN107451874A (en) * 2017-07-27 2017-12-08 武汉天喻信息产业股份有限公司 Electronic invoice integrated conduct method and system based on block chain
CN108648066A (en) * 2018-04-28 2018-10-12 济南浪潮高新科技投资发展有限公司 A kind of managing bill system and method based on block chain
CN109191219A (en) * 2018-08-13 2019-01-11 腾讯科技(深圳)有限公司 About the data processing method of electronic bill, device, storage medium and equipment
CN109165957A (en) * 2018-08-14 2019-01-08 海南高灯科技有限公司 Invoice data method of charging out, system and relevant device based on block chain
CN110428292B (en) * 2018-08-16 2021-05-11 深圳市智税链科技有限公司 Electronic bill generating method, electronic bill generating device, storage medium and computer equipment
CN109165943A (en) * 2018-08-20 2019-01-08 腾讯科技(深圳)有限公司 About the data processing method of electronic bill, device, storage medium and equipment
CN109325812A (en) * 2018-08-24 2019-02-12 深圳市智税链科技有限公司 About the data processing method of electronic bill, device, storage medium and equipment
CN109241772A (en) * 2018-09-07 2019-01-18 腾讯科技(深圳)有限公司 Invoice block chained record method, apparatus, block chain gateway server and medium
CN110009435A (en) * 2018-12-25 2019-07-12 阿里巴巴集团控股有限公司 Based on the invoice method of charging out and device of block chain, electronic equipment

Also Published As

Publication number Publication date
CN110458562B (en) 2021-05-18
CN110599276A (en) 2019-12-20
CN110458562A (en) 2019-11-15

Similar Documents

Publication Publication Date Title
CN110599276B (en) Bill reimbursement method, device and equipment and computer storage medium
US20160005021A1 (en) System for accepting a first account for making payment for a transaction and paying for the transaction with funds from a second account
US20120084135A1 (en) System and method for tracking transaction records in a network
WO2019100308A1 (en) Business trip reimbursement method, system, storage medium and terminal
KR20190028517A (en) Distributing digital assets by transactional devices
WO2001071452A2 (en) Method and apparatus for facilitating online payment transactions in a network-based transaction facility using multiple payment instruments
GB2507722A (en) Document management system taking actions based on extracted data
JP2013246480A (en) Factoring entrepreneur device and discount transaction method for electronic credit
RU2572430C1 (en) System for payment-communication relationships in bank
KR20170058887A (en) A Method For Multi-Offering An Estimate
JP2005100208A (en) Insurance business support system
US20200204553A1 (en) Method, apparatus and computer program product for exchanging messages across a network
US9135614B2 (en) System and method for managing issuance of financial accounts
CN110599273B (en) Data processing method, data processing device, node equipment and storage medium
JP6934030B2 (en) Information processing device and information processing method
KR20200079931A (en) Method for issuing and authenticating an elelcrtonic ticket based on block chain network
US20190213574A1 (en) Prepaid multinational program
US20210117970A1 (en) Corroborating data to verify transactions
JP2018169794A (en) Transaction information collation system
CN111563814A (en) Information processing method, device and system and electronic equipment
CN110622189A (en) Efficient method and system for providing digital receipts
KR20030064347A (en) Method to handle guarantee process for electronic commerce
CN110599176A (en) Data processing method and device based on block chain, storage medium and node equipment
JP2002230362A5 (en)
KR101080081B1 (en) Certification system of business entity using a internet-biz identification number and method thereof

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 40018123

Country of ref document: HK

SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant