Method and related device for processing a sheet
By leveraging blockchain technology and smart contract logic, the problem of unprocessed requests from reimbursing companies in online invoice reimbursement has been solved, improving the success rate and efficiency of invoice compensation and ensuring that users can re-initiate the process after the timeout.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-04-27
- Publication Date
- 2026-03-20
AI Technical Summary
In online expense reimbursement, failure of the requesting company to process the reimbursement request leads to expense reimbursement failure and the inability to complete the reimbursement process. Existing technology cannot effectively solve this problem.
Using blockchain technology, the system receives compensation transactions from terminal devices, invokes smart contract logic, transfers the right to modify the bill to be compensated to the designated compensation company, and updates the bill based on the compensation company's results. The process continues until the timeout period, at which point the right is transferred to the bill holder, ensuring that the bill is returned to the user after the timeout to re-initiate the process.
This effectively avoids process stagnation caused by unprocessed invoices by the compensation company, improves the success rate and efficiency of invoice compensation, and ensures that users can obtain compensation results in a timely manner.
Smart Images

Figure CN111553781B_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of bill processing, and in particular to a bill processing method, a bill processing device, a bill processing equipment and a computer storage medium. BACKGROUND
[0002] Currently, there are two ways of bill compensation (i.e. bill reimbursement). One of them is offline reimbursement, which requires the user to take the paper bill or print out the electronic bill and go to the reimbursement enterprise for reimbursement. The offline reimbursement method requires more manpower and resources. Therefore, the other reimbursement method, i.e. online reimbursement, is more popular among users. In this method, the user can submit a reimbursement request online and submit the invoice to be reimbursed to the reimbursement enterprise, so as to go to the reimbursement enterprise for reimbursement without printing paper bills, which is more paper-saving and more environmentally friendly.
[0003] However, in the online reimbursement method, there may be a situation where the reimbursement enterprise does not process the reimbursement request. For example, the user submits an invoice to the bill reimbursement system of the reimbursement enterprise through blockchain technology, but the reimbursement enterprise has not processed the invoice, resulting in a failed reimbursement operation of the user and the failure to complete the bill reimbursement. Therefore, how to prevent the bill from not being reimbursed is a problem to be solved. SUMMARY
[0004] The embodiments of the present application provide a bill processing method and related equipment, which can improve the success rate of bill compensation.
[0005] In a first aspect, the embodiments of the present application provide a bill processing method applied to a blockchain node, which comprises:
[0006] receiving a compensation transaction sent by a terminal device in response to a bill compensation operation instruction of a bill holder, the compensation transaction carrying a to-be-compensated bill, a timeout time and a specified compensation enterprise;
[0007] in response to the compensation transaction, calling compensation processing logic declared in a smart contract, transferring the modification authority of the to-be-compensated bill to the specified compensation enterprise, and updating the to-be-compensated bill according to the compensation result returned by the compensation enterprise until the timeout time is reached, and the modification authority of the to-be-compensated bill is transferred to the bill holder.
[0008] Optionally, transferring the modification authority of the to-be-compensated bill to the specified compensation enterprise, and updating the to-be-compensated bill according to the compensation result returned by the compensation enterprise until the timeout time is reached, and the modification authority of the to-be-compensated bill is transferred to the bill holder, comprises:
[0009] According to the enterprise order, the modification right of the to-be-compensated ticket is transferred to the designated preceding compensation enterprise, and a compensation result returned by the preceding compensation enterprise is received;
[0010] When the current time is less than the timeout time, after the to-be-compensated ticket is updated according to the compensation result of the preceding compensation enterprise, the modification right of the updated to-be-compensated ticket is transferred to the designated following compensation enterprise according to the enterprise order, and a compensation result returned by the following compensation enterprise is received;
[0011] When the current time is equal to the timeout time, the to-be-compensated ticket is updated according to the compensation result of the preceding compensation enterprise, and the modification right of the to-be-compensated ticket is transferred to the ticket holder.
[0012] Optionally, the compensation result is a compensation ticket carrying compensation response information, the to-be-compensated ticket is updated according to the compensation result returned by the compensation enterprise, until the timeout time is reached, the modification right of the to-be-compensated ticket is transferred to the ticket holder, and the method comprises the following steps of:
[0013] Determining a ticket processing right of the compensation enterprise;
[0014] Determining whether the compensation enterprise exceeds the ticket processing right according to the ticket processing right, the compensation result returned by the compensation enterprise, and the to-be-compensated ticket;
[0015] When it is determined that the compensation enterprise does not exceed the ticket processing right, updating the to-be-compensated ticket according to the compensation result returned by the compensation enterprise is performed;
[0016] When it is determined that the compensation enterprise exceeds the ticket processing right, updating the to-be-compensated ticket according to the compensation result returned by the compensation enterprise is skipped.
[0017] Optionally, the method further comprises:
[0018] Obtaining a credit level of the designated compensation enterprise;
[0019] According to a corresponding relationship between the credit level and the timeout time, a timeout time corresponding to the designated compensation enterprise is determined.
[0020] In a second aspect, an embodiment of the present application provides a ticket processing method applied to a terminal device, and the method comprises the following steps of:
[0021] In response to the ticket compensation operation indication of the ticket holder, a compensation transaction is sent to the blockchain node, wherein the compensation transaction carries a to-be-compensated ticket, a preset waiting time length, and a designated compensation enterprise, and the compensation transaction is used to instruct the blockchain node to call compensation processing logic declared in a smart contract, to transfer modification authority of the to-be-compensated ticket to the designated compensation enterprise, and to update the to-be-compensated ticket according to a compensation result returned by the compensation enterprise until the timeout time is reached, and the modification authority of the to-be-compensated ticket is transferred to the ticket holder.
[0022] The to-be-compensated ticket sent by the blockchain node is received.
[0023] In a third aspect, an embodiment of the present application provides a ticket processing apparatus applied to a blockchain node, comprising:
[0024] A first receiving module is configured to receive a compensation transaction sent by a terminal device in response to a ticket compensation operation indication of a ticket holder, wherein the compensation transaction carries a to-be-compensated ticket, a timeout time, and a designated compensation enterprise.
[0025] A processing module is configured to, in response to the compensation transaction, call compensation processing logic declared in a smart contract, transfer modification authority of the to-be-compensated ticket to the designated compensation enterprise, and update the to-be-compensated ticket according to a compensation result returned by the compensation enterprise until the timeout time is reached, and the modification authority of the to-be-compensated ticket is transferred to the ticket holder.
[0026] Optionally, the apparatus further comprises:
[0027] A obtaining module is configured to obtain a credit level of the designated compensation enterprise.
[0028] A determining module is configured to determine a timeout time corresponding to the designated compensation enterprise according to a correspondence between credit levels and timeout times.
[0029] In a fourth aspect, an embodiment of the present application provides a ticket processing apparatus applied to a terminal device, comprising:
[0030] A sending module is configured to, in response to a ticket compensation operation indication of a ticket holder, send a compensation transaction to a blockchain node, wherein the compensation transaction carries a to-be-compensated ticket, a preset waiting time length, and a designated compensation enterprise, and the compensation transaction is used to instruct the blockchain node to call compensation processing logic declared in a smart contract, to transfer modification authority of the to-be-compensated ticket to the designated compensation enterprise, and to update the to-be-compensated ticket according to a compensation result returned by the compensation enterprise until the timeout time is reached, and the modification authority of the to-be-compensated ticket is transferred to the ticket holder.
[0031] The second receiving module is used to receive the compensation ticket sent by the blockchain node.
[0032] Fifthly, embodiments of the present invention provide a ticket processing device, including: a processor and a memory;
[0033] The processor is connected to a memory, wherein the memory is used to store program code, and the processor is used to call the program code to execute the ticket processing method described in the first or second aspect.
[0034] In a sixth aspect, embodiments of the present invention provide a computer storage medium storing a computer program, the computer program including program instructions, which, when executed by a processor, perform the ticket processing method described in the first or second aspect.
[0035] This invention, in its embodiments, receives a compensation transaction sent by a terminal device in response to a bill compensation operation instruction from a bill holder. The compensation transaction carries the bill to be compensated, the timeout period, and a designated compensation company. In response to the compensation transaction, the compensation processing logic declared in the smart contract is invoked, transferring the modification rights of the bill to be compensated to the designated compensation company. The bill to be compensated is updated based on the compensation result returned by the compensation company until the timeout period is reached, at which point the modification rights are transferred back to the bill holder. This effectively prevents the bill compensation process from stalling due to the compensation company's failure to process the bill. After the timeout period, the current bill to be compensated is returned to the bill holder, who can then re-initiate the compensation process for that bill, effectively improving the success rate and efficiency of bill compensation. Attached Figure Description
[0036] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0037] Figure 1 This is a schematic diagram of a block structure provided in an embodiment of the present invention;
[0038] Figure 2 This is a schematic diagram of a scenario for a ticket processing method provided in an embodiment of the present invention;
[0039] Figure 3 This is a flowchart illustrating a bill processing method provided in an embodiment of the present invention;
[0040] Figure 4 This is a flowchart illustrating a bill processing method provided in an embodiment of the present invention;
[0041] Figure 5 is a flowchart of a bill processing method provided by an embodiment of the present application;
[0042] Figure 6 is a structural diagram of a bill processing device provided by an embodiment of the present application;
[0043] Figure 7 is a structural diagram of a bill processing device provided by an embodiment of the present application;
[0044] Figure 8 is a structural diagram of a bill processing device provided by an embodiment of the present application. DETAILED DESCRIPTION
[0045] The technical solutions in the embodiments of the present application will be clearly and completely described in connection with the drawings in the embodiments of the present application.
[0046] It should be understood that the terms "comprise" and "have" and any variations thereof in the specification and claims of the present application and the drawings are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but can optionally include steps or units not listed, or can optionally include other steps or units inherent to the process, method, product or device.
[0047] In the present application, "embodiment" means that the specific features, structures or characteristics described in connection with the embodiment can be included in at least one embodiment of the present application. The phrase appears at various places in the specification does not necessarily refer to the same embodiment, nor is it mutually exclusive or alternative to other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described in the present application can be combined with other embodiments.
[0048] Bill: refers to a certificate made in accordance with certain prescribed forms and showing the obligation to pay money, that is, the bill can be used as a transaction certificate when a transaction occurs. Generally speaking, the bill can include a tax invoice, a financial bill (such as a medical bill) or a commercial bill, etc. The invoice is generally a business certificate issued and collected by units and individuals in the purchase and sale of goods, provision or acceptance of services, and other business activities, which is the original basis for accounting. The medical bill is generally a consumption certificate issued by a medical institution after consumption in a medical institution. The commercial bill is generally an unsecured short-term bill issued by a financial company or enterprise, which is used for the bill issuer to raise funds. Of course, the bill in the embodiments of the present application can also refer to other types of bills that can be reimbursed by enterprises, such as internal bills issued by enterprises, etc., which are not limited in the embodiments of the present application.
[0049] Ticket holder: refers to the user who owns the ticket, that is, the user who initiates the ticket compensation process.
[0050] Reimbursement agency: This refers to the company or government agency for which the invoice holder requests reimbursement for the invoices to be reimbursed. For example, for invoices, the reimbursement agency is generally the company listed on the invoice header; or for medical invoices, the reimbursement agency is generally an insurance company or government agency.
[0051] Blockchain, also known as a distributed data ledger, is a chain-like data structure that combines data blocks in a specific order, ensuring its immutability and tamper-proof nature through cryptographic means. A block records information related to one or more events in the circulation of an invoice. For example, an event could refer to the storage of the invoice, its transfer, the processing of compensation, or the storage of the compensation result.
[0052] See Figure 1 , Figure 1 This is an optional schematic diagram of the block structure provided in this embodiment of the invention. Each block includes the hash value of the transaction records stored in this block (the hash value of this block) and the hash value of the previous block. The blocks are connected through their hash values to form a blockchain. Additionally, the block may include information such as a timestamp when it was generated. A blockchain, in essence, is a decentralized database, a chain of data blocks linked together using cryptographic methods. Each data block contains relevant information used to verify the validity of the information (anti-counterfeiting) and to generate the next block.
[0053] A blockchain node is a computing device that participates in transaction processing within a blockchain network. This includes devices with computing capabilities such as computers, mobile phones, desktop computers, servers, or server clusters, or even a portion of a single computer or server, such as virtual machines. For example, blockchain nodes can be implemented using virtual machine clusters, where a portion of each physical machine is partitioned as a virtual machine to collectively perform the functions of a blockchain node. In a cloud environment, this can also be achieved through the combined efforts of multiple distributed computing devices. A blockchain network comprises numerous node devices, each with either identical or differentiated functions.
[0054] The smart contract is a computerized protocol capable of executing the terms of a contract through the code deployed on a shared ledger for execution when certain conditions are met, and the code is used to complete the automated transaction according to the actual business needs, for example, querying the logistics status of the goods purchased by the buyer, and transferring the electronic currency of the buyer to the address of the merchant after the buyer signs for the goods. Of course, the smart contract is not limited to executing the contract for the transaction, but also can execute the contract for processing the received information.
[0055] The terminal device can be a mobile phone, a personal computer (PC), a tablet computer (PAD), a personal digital assistant (PDA), a notebook computer, or a smart wearable device (such as a smart watch and a smart bracelet), and the like.
[0056] In the prior art, ticket compensation, that is, ticket reimbursement, generally refers to a process in which a user pays in advance, then goes to a compensation enterprise (i.e., a reimbursement agency) to claim reimbursement, and the compensation enterprise compensates the user for the paid amount. Online reimbursement business is generally an electronic reimbursement process using reimbursement software or a reimbursement webpage, but in the current online reimbursement method, when a reimbursement enterprise is slow to reimburse a ticket, the reimbursement process of the ticket will be forced to be interrupted, and the compensation for the ticket cannot be completed. Therefore, the present application provides a ticket processing method, which can return the current to-be-compensated ticket to the ticket holder when the timeout time is reached, and the ticket holder can reinitiate the compensation process for the to-be-compensated ticket, effectively improving the compensation success rate and efficiency of the ticket.
[0057] Please refer to Figure 2 , Figure 2 is a scene diagram of a ticket processing method provided by an embodiment of the application; Figure 2 In the embodiment, the terminal device 201 (such as a mobile phone), the compensation enterprise 203, and the blockchain node 204 can communicate with each other through a network. The network can be a wired network or a wireless network, for example, a mobile cellular network or a wireless fidelity (WIreless-Fidelity, WIFI) network, and can also be other possible networks, which are not limited in the embodiments of the present application. Taking the reimbursement of medical expenses of the user 202 as an example, the to-be-compensated ticket at this time is a medicine list issued by a hospital, as shown in Table 1, which includes the item name (i.e., the medicine name), the retail price of the medicine, the quantity of the medicine, and the corresponding amount of data. When the user 202 obtains the medicine list of Table 1, the user initiates the compensation process through the terminal device 201.
[0058] Table 1
[0059]
[0060] Specifically, the user 202 operates the terminal device 201 to initiate a compensation transaction to the blockchain, which carries a drug list, a desired time to complete compensation (i.e., a timeout time), and designated compensation enterprises (one or more). Taking the example of designating three insurance companies A, B, and C, different insurance companies compensate for the cost of drugs for different diseases, and the drug compensation ratios are different. The blockchain node 204 responds to the compensation transaction and transfers the modification authority of the drug list to the insurance company A in the order of the enterprises (assuming that the order of the enterprises is the input order of the enterprises, i.e., A, B, and C). After processing by the insurance company A, a first compensation result is generated. The insurance company A can compensate 50% of the cost of Cefaclor. The first compensation result is the drug list with compensation response information (corresponding to Cefaclor) added in the remarks column, as shown in Table 1. The insurance company A returns the first compensation result to the blockchain node 204. When it is determined that the desired time to complete compensation has not been reached, the blockchain node 204 updates the drug list according to the first compensation result. The updated drug list is the drug list processed by the insurance company A. The blockchain node 204 transfers the modification authority of the drug list to the insurance company B at this time according to the order of the enterprises. The insurance company B can compensate 90% of the cost of 0.9% Sodium Chloride Injection. At this time, a second compensation result is generated. The second compensation result is the drug list with compensation response information corresponding to 0.9% Sodium Chloride Injection added in the remarks column based on the first compensation result. Similarly, when it is determined that the desired time to complete compensation has not been reached, the blockchain node 204 updates the drug list according to the second compensation result. The updated drug list is the drug list processed by the insurance company B. The processing process of the insurance company C is similar to that of the insurance companies A and B, and is not described again. Taking the example of the time still not reaching the desired time to complete compensation after the insurance company C processes the compensation, the final drug list is the drug list processed by the insurance company C (i.e., the drug list with compensation response information corresponding to Penicillin added in the remarks column based on the second compensation result). In particular, the compensation response information in Table 1 is a compensation ratio. It can be understood that the compensation response information can also be a specific compensation amount.
[0061] When the time reaches the desired time to complete compensation, the blockchain node 204 transfers the modification authority of the current drug list to the user 202, i.e., returns the current drug list to the user. If the time reaches the desired time to complete compensation, and there are still insurance companies that have not processed the drug list for compensation, the blockchain node also returns the drug list that has not completed compensation to the user, avoiding the user's endless waiting. The user can re-initiate the compensation process for the drug list, improving the success rate and efficiency of the compensation of the drug list.
[0062] Referring to Figure 3 Fig. 1 is a flowchart of a ticket processing method provided by an embodiment of the present application; the ticket processing method is applied to a blockchain node, and the ticket processing method comprises the following steps:
[0063] 301. Receiving a compensation transaction sent by a terminal device in response to a ticket compensation operation instruction of a ticket holder, the compensation transaction carrying a to-be-compensated ticket, a timeout time and a designated compensation enterprise;
[0064] Specifically, the ticket holder initiates a compensation transaction through the terminal device, and the compensation transaction specifies a timeout time and a compensation enterprise, and the number of compensation enterprises is more than one.
[0065] 302. In response to the compensation transaction, calling compensation processing logic declared in a smart contract to transfer the modification authority of the to-be-compensated ticket to the designated compensation enterprise, and updating the to-be-compensated ticket according to the compensation result returned by the compensation enterprise until the timeout time is reached, and the modification authority of the to-be-compensated ticket is transferred to the ticket holder.
[0066] Specifically, the blockchain node responds to the compensation transaction, calls the compensation processing logic declared in the smart contract deployed thereon, and transfers the modification authority of the to-be-compensated ticket to the designated compensation enterprise, so that the ticket compensation system of the compensation enterprise can perform compensation processing on the to-be-compensated ticket, thereby obtaining a compensation result. The compensation enterprise performs on-chain operation to submit the compensation result to the smart contract, and the smart contract updates the to-be-compensated ticket according to the compensation result returned by the compensation enterprise according to the compensation processing logic, until the timeout time is reached, and the modification authority of the to-be-compensated ticket is transferred to the ticket holder.
[0067] In this embodiment, after the ticket holder initiates the compensation transaction, the smart contract transfers the modification authority of the to-be-compensated ticket to the designated compensation enterprise, and updates the to-be-compensated ticket according to the compensation result returned by the compensation enterprise until the timeout time is reached, and the modification authority of the current to-be-compensated ticket is transferred to the ticket holder; this can effectively avoid the situation that the compensation enterprise does not process the to-be-compensated ticket all the time, resulting in stagnation of the ticket compensation process. After the timeout time is reached, the current to-be-compensated ticket is returned to the ticket holder, and the ticket holder can re-initiate the compensation process for the to-be-compensated ticket, thereby effectively improving the success rate and efficiency of ticket compensation.
[0068] In a possible embodiment, the specified compensation enterprise can be a unique enterprise identifier (enterprise number or enterprise name, etc.) of the specified compensation enterprise or an address of the specified compensation enterprise on the blockchain, and a correspondence between the unique enterprise identifier of the compensation enterprise and the public key of the compensation enterprise (or a correspondence between the unique enterprise identifier of the compensation enterprise, the blockchain address of the enterprise, and the public key of the compensation enterprise) needs to be established in advance, and the correspondence is chained to make each blockchain node of the blockchain share the correspondence. The blockchain address of the compensation enterprise can be obtained according to the public key of the compensation enterprise.
[0069] Further, the modification permission of the to-be-compensated bill is transferred to the specified compensation enterprise, including:
[0070] S1, determining the blockchain address and the public key of the specified compensation enterprise according to the correspondence between the specified compensation enterprise, the unique enterprise identifier of the compensation enterprise, and the public key of the compensation enterprise, or the correspondence between the blockchain address of the compensation enterprise and the public key of the compensation enterprise; when the unique enterprise identifier of the specified compensation enterprise is input by the bill holder when initiating the compensation transaction, the public key corresponding to the enterprise can be determined according to the unique enterprise identifier, and the blockchain address of the enterprise can be obtained according to the public key; when the blockchain address of the specified compensation enterprise is input by the bill holder when initiating the compensation transaction, the public key corresponding to the enterprise can be found according to the address;
[0071] S2, transferring the modification permission of the to-be-compensated bill to the specified compensation enterprise according to the blockchain address of the specified compensation enterprise, so that the specified compensation enterprise processes the to-be-compensated bill to obtain a compensation result, and the compensation result is chained;
[0072] S3, verifying the compensation result chained according to the public key of the specified compensation enterprise, to determine that the compensation result is sent by the specified compensation enterprise, and to ensure the accuracy of the compensation result.
[0073] It can be seen that for each chained compensation result, the verification operation ensures that the compensation result is sent by the compensation enterprise, and the to-be-compensated bill is updated according to the correct compensation result, which can ensure the accuracy of the bill compensation and avoid compensation errors.
[0074] In a possible embodiment, when the number of specified compensation enterprises is more than two, step 302 includes:
[0075] 3021, transferring the modification permission of the to-be-compensated bill to the specified preceding compensation enterprise according to the enterprise order, and receiving the compensation result returned by the preceding compensation enterprise;
[0076] Specifically, the enterprise order can be set as needed, for example, the order in the compensation transaction can be taken as the enterprise order, or the enterprise order can be set in advance, for example, the order of multiple compensation enterprises is set in advance, for example, the order of insurance companies is set in advance as A, B, C, D, E, and F, assuming that the insurance companies specified in the compensation transaction are C, B, and E, then compared with the company, it can be determined that the final enterprise order at this time is B, C, and E.
[0077] Next, according to the enterprise order, the modification permission of the to-be-compensated bill is transferred to the designated preceding compensation enterprise, and the compensation result returned by the preceding compensation enterprise is received. Taking C, B, and E as an example, the modification permission of the to-be-compensated bill is first transferred to the insurance company B, and the compensation result is obtained after the bill compensation system of the insurance company B is processed. The insurance company B submits the compensation result to the smart contract by chaining.
[0078] 3022, when the current time is less than the timeout time, the to-be-compensated bill is updated according to the compensation result of the preceding compensation enterprise, and then the modification permission of the updated to-be-compensated bill is transferred to the designated subsequent compensation enterprise according to the enterprise order, and the compensation result returned by the subsequent compensation enterprise is received;
[0079] Specifically, after receiving the compensation result, it is judged whether the current time is less than the timeout time. When the current time is less than the timeout time, the to-be-compensated bill is updated according to the compensation result of the preceding compensation enterprise, and then the modification permission of the updated to-be-compensated bill is transferred to the designated subsequent compensation enterprise according to the enterprise order, and the compensation result returned by the subsequent compensation enterprise is received. When there is no subsequent compensation enterprise, the modification permission of the current to-be-compensated bill is transferred to the bill holder after the waiting time reaches the timeout time.
[0080] 3023, when the current time is equal to the timeout time, the to-be-compensated bill is updated according to the compensation result of the preceding compensation enterprise, and the modification permission of the to-be-compensated bill is transferred to the bill holder.
[0081] Specifically, when the timeout time is reached, the current to-be-compensated bill is updated according to the compensation result of the preceding compensation enterprise, and the modification permission of the updated to-be-compensated bill is transferred to the bill holder.
[0082] The processing procedure of the compensation result of the post-compensation enterprise is the same as the processing procedure of the compensation result of the pre-compensation enterprise, and will not be described herein. Taking the insurance company B as an example, when the current time is less than the timeout time, the to-be-compensated ticket is updated according to the compensation result of the insurance company B, the updated to-be-compensated ticket carries the compensation result of the insurance company B, and then the modification permission of the updated to-be-compensated ticket is transferred to the insurance company C. Similarly, for the insurance company C, the corresponding compensation result can be obtained, and it is continuously judged whether the current time is less than the timeout time. If it is judged that the current time is less than the timeout time, the current to-be-compensated ticket (the to-be-compensated ticket carrying the compensation result of the insurance company B at this time) is updated according to the compensation result of the insurance company C, so that the to-be-compensated ticket carries the compensation result of the insurance company C. Then the modification permission of the updated to-be-compensated ticket is transferred to the insurance company E. When it is judged that the current time is equal to the timeout time, the current to-be-compensated ticket is updated according to the compensation result of the insurance company B or the insurance company C, and then the modification permission of the to-be-compensated ticket is transferred to the ticket holder.
[0083] In one possible embodiment, the compensation result can be compensation response information, for example, referring to Table 1, the compensation response information can be “insurance company A compensates 50% of the cost of cefaclor”, in addition to the compensation ratio, it can also be a specific compensation amount, for example, “insurance company A compensates 60 yuan of the cost of cefaclor”. In order to reduce the processing time of updating the to-be-compensated ticket according to the compensation result, the compensation result can also be a to-be-compensated ticket carrying compensation response information, as shown in Table 1, the compensation response information is directly added to the to-be-compensated ticket as the compensation result; when updating the to-be-compensated ticket, the compensation result can be directly used to replace the original to-be-compensated ticket.
[0084] In one possible embodiment, when the compensation result is a to-be-compensated ticket carrying compensation response information, taking the compensation result of one compensation enterprise (the pre-compensation enterprise or the post-compensation enterprise) as an example, referring to Table 1, the to-be-compensated ticket carrying the compensation result of the pre-compensation enterprise is directly used to replace the to-be-compensated ticket carrying the compensation result of the post-compensation enterprise, and the to-be-compensated ticket carrying the compensation result of the post-compensation enterprise is directly discarded. Figure 4 , Figure 4 FIG. 1 is a flowchart of a ticket processing method provided by an embodiment of the present application, and step 302 further includes:
[0085] 401, determining the ticket processing permission of the compensation enterprise;
[0086] Specifically, after receiving the compensation result returned by the compensation enterprise, the ticket processing authority of the compensation enterprise is determined according to the pre-set corresponding relationship between the compensation enterprise and the ticket processing authority. The corresponding relationship can be established according to the unique enterprise identification mark of the compensation enterprise and the set ticket processing authority, or according to the blockchain address of the compensation enterprise and the set ticket processing authority. The ticket processing authority includes adding information (such as compensation response information) to the to-be-compensated ticket and transferring the modification authority of the to-be-compensated ticket. The modification authority has a higher authority than the ticket processing authority in the above corresponding relationship. The ticket processing authority of the compensation enterprise can be determined by querying the corresponding relationship according to the unique enterprise identification mark or the blockchain address of the compensation enterprise.
[0087] 402. Determine whether the compensation enterprise exceeds the ticket processing authority according to the ticket processing authority, the compensation result returned by the compensation enterprise, and the to-be-compensated ticket;
[0088] Specifically, the blockchain node transfers the modification authority of the to-be-compensated ticket to the compensation enterprise, and the compensation enterprise modifies the to-be-compensated ticket to form a compensation result after obtaining the modification authority of the to-be-compensated ticket. After receiving the compensation result returned by the compensation enterprise, the blockchain node compares the original to-be-compensated ticket with the compensation result, and combines the ticket processing authority determined in step 401 to determine whether the compensation enterprise exceeds the ticket processing authority.
[0089] 403. When it is determined that the compensation enterprise does not exceed the ticket processing authority, perform updating the to-be-compensated ticket according to the compensation result returned by the compensation enterprise;
[0090] Specifically, when the compensation enterprise does not exceed the ticket processing authority, the compensation result returned by the compensation enterprise is continued to be processed. Whether the to-be-compensated ticket is updated according to the compensation result can be determined according to the timeout time, that is, steps 3022 and 3023 are executed.
[0091] 404. When it is determined that the compensation enterprise exceeds the ticket processing authority, skip performing updating the to-be-compensated ticket according to the compensation result returned by the compensation enterprise.
[0092] Specifically, when the compensation enterprise exceeds the ticket processing authority, the compensation result returned by the compensation enterprise is not processed, and when steps 3022 and 3023 are executed, the step of updating the to-be-compensated ticket according to the compensation result returned by the compensation enterprise is skipped. The behavior of exceeding the ticket processing authority includes modifying the data (such as modifying the name of the medicine and the retail price) in the to-be-compensated ticket when the ticket user initiates a transaction, and adding a compensation ticket (such as adding a medicine in Table 1). These behaviors are not allowed to occur.
[0093] Utilizing Figure 4The method comprises the following steps: when a compensation result is received, it is verified whether the compensation result exceeds the bill processing authority; if the compensation result exceeds the bill processing authority, the compensation result is not processed, and the subsequent process is directly entered, so as to reduce the data processing amount and accelerate the bill compensation speed.
[0094] In one possible embodiment, when the ticket user does not provide the timeout time, a method for automatically determining the timeout time according to the compensation enterprise is provided, and the bill processing method further comprises the following steps:
[0095] The credit level of the specified compensation enterprise is obtained.
[0096] Specifically, the credit level of the compensation enterprise is evaluated according to unified standards, and the evaluation standards include one or more than two of historical compensation amount, average compensation speed and average user score. The credit level of the compensation enterprise is calculated by regularly obtaining multiple data of the compensation enterprise, and the credit level of each compensation enterprise is regularly chained to realize credit level information sharing. For example, the evaluation standards include historical compensation amount, average compensation speed and average user score, the credit level is calculated according to the preset weights of the three, for example, the weight of historical compensation amount is 0.2, the weight of average compensation speed is 0.4, and the weight of average user score is 0.4, then a numerical value can be obtained by weighted calculation according to the specific values of the three parameters, and the numerical value is taken as the credit level of the compensation enterprise.
[0097] According to the corresponding relationship between the credit level and the timeout time, the timeout time corresponding to the specified compensation enterprise is determined.
[0098] Specifically, the corresponding relationship between the range of the credit level and the timeout time is established in advance, for example, the credit level is 0-2W, the timeout time is 0.5 days, the credit level is 2W-100W, the timeout time is 1 day, and the credit level is 100W or more, the timeout time is 2 days. According to the credit level of the compensation enterprise, the corresponding relationship is searched, and the timeout time corresponding to the compensation enterprise is determined; when the specified compensation enterprise is more than two, the sum of the timeout times of the multiple compensation enterprises is the timeout time of the compensation transaction.
[0099] A method for automatically determining the timeout time is provided, when the ticket user forgets to provide the timeout time, the timeout time is automatically determined, so that the compensation process can proceed normally, and the success rate of providing the bill compensation is provided.
[0100] Referring to Figure 5 , Figure 5 is a flowchart of a bill processing method provided by an embodiment of the application. The embodiment further provides a bill processing method applied to a terminal device, and the bill processing method comprises the following steps:
[0101] 501. In response to the bill compensation operation instruction from the bill holder, a compensation transaction is sent to the blockchain node. The compensation transaction carries the bill to be compensated, a preset waiting time, and a designated compensation company. The compensation transaction is used to instruct the blockchain node to call the compensation processing logic declared in the smart contract, transfer the modification rights of the bill to be compensated to the designated compensation company, and update the bill to be compensated according to the compensation result returned by the compensation company until the timeout period is reached, at which point the modification rights of the bill to be compensated are transferred to the bill holder.
[0102] Specifically, the ticket holder performs a ticket compensation operation on their terminal device to send a compensation transaction to the blockchain node. The compensation transaction instructs the blockchain node to invoke the compensation processing logic in the smart contract deployed on it, so as to transfer the right to modify the ticket to be compensated to the designated compensation enterprise, and update the ticket to be compensated according to the compensation result returned by the compensation enterprise, until the timeout period is reached, at which point the right to modify the ticket to be compensated is transferred to the ticket holder.
[0103] 502. Receive the compensation ticket sent by the blockchain node.
[0104] use Figure 5 This method can effectively prevent the compensation process from stalling due to the compensation company not processing the bills to be compensated. After the timeout period expires, the bills to be compensated are returned to the bill holder, who can then re-initiate the compensation process for the bill, effectively improving the success rate and efficiency of bill compensation.
[0105] For the processing steps in the blockchain node, please refer to the above-mentioned ticket processing method applied to the blockchain node, which will not be repeated here.
[0106] Based on the description of the above-described bill processing method embodiments, this invention also discloses a bill processing device applied in a blockchain node, referencing... Figure 6 , Figure 6 This is a schematic diagram of a bill processing device provided in an embodiment of the present invention. The bill processing device includes:
[0107] The first receiving module 601 is used to receive a compensation transaction sent by the terminal device in response to the ticket compensation operation instruction of the ticket holder. The compensation transaction carries the ticket to be compensated, the timeout time, and the designated compensation company.
[0108] The processing module 602 is used to respond to the compensation transaction, call the compensation processing logic declared in the smart contract, transfer the modification rights of the bill to be compensated to the designated compensation enterprise, and update the bill to be compensated according to the compensation result returned by the compensation enterprise until the timeout period is reached, and then transfer the modification rights of the bill to be compensated to the bill holder.
[0109] In a possible implementation, when the number of the designated compensation enterprises is more than two, the processing module comprises:
[0110] a first submodule, configured to transfer the modification right of the to-be-compensated ticket to the designated preceding compensation enterprise according to the enterprise order, and receive the compensation result returned by the preceding compensation enterprise;
[0111] a second submodule, configured to, when the current time is less than the timeout time, transfer the modification right of the updated to-be-compensated ticket to the designated subsequent compensation enterprise according to the enterprise order after the to-be-compensated ticket is updated according to the compensation result of the preceding compensation enterprise, and receive the compensation result returned by the subsequent compensation enterprise;
[0112] a third submodule, configured to, when the current time is equal to the timeout time, update the to-be-compensated ticket according to the compensation result of the preceding compensation enterprise, and transfer the modification right of the to-be-compensated ticket to the ticket holder.
[0113] In a possible implementation, the compensation result is a compensation ticket carrying compensation response information, and the processing module further comprises:
[0114] a determining submodule, configured to determine the ticket processing right of the compensation enterprise;
[0115] a judging submodule, configured to determine whether the compensation enterprise exceeds the ticket processing right according to the ticket processing right, the compensation result returned by the compensation enterprise, and the to-be-compensated ticket;
[0116] a first executing submodule, configured to, when it is determined that the compensation enterprise does not exceed the ticket processing right, execute the updating of the to-be-compensated ticket according to the compensation result returned by the compensation enterprise;
[0117] a second executing submodule, configured to, when it is determined that the compensation enterprise exceeds the ticket processing right, skip the updating of the to-be-compensated ticket according to the compensation result returned by the compensation enterprise.
[0118] In a possible implementation, the apparatus further comprises:
[0119] an obtaining module, configured to obtain the credit level of the designated compensation enterprise;
[0120] a determining module, configured to determine the timeout time corresponding to the designated compensation enterprise according to the correspondence between the credit level and the timeout time.
[0121] It is worth pointing out that the specific function implementation of the bill processing device can refer to the description of the bill processing method described above, and will not be repeated here. The units or modules in the bill processing device can be combined into one or several other units or modules, or some of the units or modules can be further divided into a plurality of units or modules with smaller functions to constitute, which can achieve the same operation without affecting the implementation of the technical effects of the embodiments of the present application. The above units or modules are divided based on logical functions. In actual application, the function of one unit (or module) can also be implemented by multiple units (or modules), or the functions of multiple units (or modules) are implemented by one unit (or module).
[0122] Based on the description of the above bill processing method embodiment, the present embodiment also discloses a bill processing device applied to a terminal device, which refers to Figure 7 , Figure 7 is a structural schematic diagram of a bill processing device provided by the present embodiment. The bill processing device comprises:
[0123] The sending module 701 is configured to send a compensation transaction to the blockchain node in response to the bill compensation operation instruction of the bill holder, wherein the compensation transaction carries a to-be-compensated bill, a preset waiting time and a designated compensation enterprise. The compensation transaction is used to instruct the blockchain node to call the compensation processing logic declared in the smart contract, transfer the modification authority of the to-be-compensated bill to the designated compensation enterprise, and update the to-be-compensated bill according to the compensation result returned by the compensation enterprise until the timeout time is reached, and then transfer the modification authority of the to-be-compensated bill to the bill holder.
[0124] The second receiving module 702 is configured to receive the to-be-compensated bill sent by the blockchain node.
[0125] It is worth pointing out that the specific function implementation of the bill processing device can refer to the description of the bill processing method described above, and will not be repeated here. The units or modules in the bill processing device can be combined into one or several other units or modules, or some of the units or modules can be further divided into a plurality of units or modules with smaller functions to constitute, which can achieve the same operation without affecting the implementation of the technical effects of the embodiments of the present application. The above units or modules are divided based on logical functions. In actual application, the function of one unit (or module) can also be implemented by multiple units (or modules), or the functions of multiple units (or modules) are implemented by one unit (or module).
[0126] Based on the description of the above method embodiment and device embodiment, the present embodiment also provides a bill processing device. Please refer to Figure 8This is a schematic diagram of the structure of a ticket processing device provided in an embodiment of the present invention. Figure 8 As shown, the aforementioned document processing device can be applied to the document processing equipment 800, which may include a processor 801, a network interface 804, and a memory 805. Furthermore, the document processing equipment 800 may also include a user interface 803 and at least one communication bus 802. The communication bus 802 is used to enable communication between these components. The user interface 803 may include a display screen and a keyboard; optionally, the user interface 803 may also include a standard wired interface or a wireless interface. The network interface 804 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface). The memory 805 may be high-speed RAM or non-volatile memory, such as at least one disk storage device. Optionally, the memory 805 may also be at least one storage device located remotely from the aforementioned processor 801. Figure 8 As shown, the memory 805, which serves as a computer storage medium, may include an operating system, a network communication module, a user interface module, and a device control application program.
[0127] exist Figure 8 In the ticket processing device 800 shown, the network interface 804 provides network communication functionality; the user interface 803 is mainly used to provide an input interface for the user; and the processor 801 can be used to call the device control application stored in the memory 805 to implement the steps of the above-mentioned ticket processing method:
[0128] It should be understood that the bill processing device 800 described in the embodiments of the present invention can execute the bill processing method described above, or it can execute the bill processing apparatus described above, and will not be repeated here. In addition, the beneficial effects of using the same method will not be repeated here either.
[0129] Furthermore, it should be noted that this embodiment of the invention also provides a computer storage medium, which stores a computer program executed by the aforementioned document processing device. The computer program includes program instructions, and when the processor executes the program instructions, it can perform the document processing method described above. Therefore, it will not be repeated here. Additionally, the beneficial effects of using the same method will also not be repeated. For technical details not disclosed in the computer storage medium embodiments of this invention, please refer to the description of the method embodiments of this invention.
[0130] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by a computer program instructing relevant hardware. The program can be stored in a computer readable storage medium, and when the program is executed, the processes of the above-mentioned embodiment methods can be included. The storage medium can be a magnetic disc, an optical disc, a read-only memory (ROM), a random access memory (RAM), or the like.
[0131] The above disclosure is only the preferred embodiments of the present application, and of course cannot limit the scope of the present application. Therefore, equivalent changes made according to the claims of the present application are still within the scope of the present application.
Claims
1. A method for processing invoices, characterized in that, When applied to blockchain nodes, the method includes: Obtain the historical compensation amount, average compensation speed, and average user rating for the specified compensation company; The credit rating of the designated compensation company is obtained by weighted summing of the historical compensation amount, the average compensation speed, and the average user rating. Based on the correspondence between the credit rating and the timeout period, the timeout period corresponding to the designated compensation enterprise is determined, and the timeout period is sent to the terminal device. The terminal device receives a compensation transaction in response to a bill compensation operation instruction from a bill holder. The compensation transaction carries the bill to be compensated, the timeout time, and the designated compensation company. In response to the compensation transaction, the compensation processing logic declared in the smart contract is invoked to transfer the modification permission of the bill to be compensated to the designated compensation enterprise. The bill to be compensated is then updated based on the compensation result returned by the compensation enterprise until the timeout period is reached, at which point the modification permission is transferred to the bill holder. The designated compensation enterprise is determined based on enterprise order. The bill to be compensated is updated based on the compensation result when the time to receive the compensation result from the designated compensation enterprise is less than the timeout period, and when it is detected that the compensation enterprise providing the compensation result conforms to the enterprise order. The updated bill to be compensated is then used to update the bill according to the enterprise order. The process continues to transfer the compensation to subsequent compensation companies. If no compensation result is received from the designated compensation company by the timeout period, the bill to be compensated is updated using the compensation result returned by the prior compensation company to obtain an updated bill to be compensated. The modification rights of the updated bill to be compensated are transferred to the bill holder. The prior compensation company refers to the compensation company that precedes the designated compensation company in the company order. The company order is determined by the compensation processing capabilities among multiple compensation companies. The updated bill to be compensated is used to enable the bill holder to re-initiate a compensation transaction with an unprocessed compensation company, which includes both the designated compensation company and the subsequent compensation company.
2. The method according to claim 1, characterized in that, The modification rights of the invoice to be compensated are transferred to the designated compensation company, and the invoice to be compensated is updated according to the compensation result returned by the compensation company until the timeout period is reached. Then, the modification rights of the invoice to be compensated are transferred back to the invoice holder. This includes: According to the order of enterprises, the right to modify the invoice to be compensated is transferred to the designated enterprise that compensates first, and the compensation result returned by the enterprise that compensates first is received; When the current time is less than the timeout period, the bill to be compensated is updated according to the compensation result of the prior compensation enterprise. Then, the modification authority of the updated bill to be compensated is transferred to the designated subsequent compensation enterprise according to the order of the enterprises, and the compensation result returned by the subsequent compensation enterprise is received. When the current time equals the timeout period, the bill to be compensated is updated according to the compensation result of the prior compensation enterprise, and the right to modify the bill to be compensated is transferred to the bill holder.
3. The method according to claim 1, characterized in that, The compensation result is a compensation invoice carrying compensation response information. The invoice to be compensated is updated based on the compensation result returned by the compensating company until the timeout period is reached. Then, the modification rights of the invoice to be compensated are transferred to the invoice holder, including: Determine the invoice processing authority of the compensation enterprise; Based on the bill processing authority, the compensation result returned by the compensation enterprise, and the bill to be compensated, it is determined whether the compensation enterprise has exceeded the bill processing authority. If it is determined that the compensation enterprise has not exceeded the bill processing period, the bill to be compensated shall be updated according to the compensation result returned by the compensation enterprise; If it is determined that the compensation enterprise has exceeded the bill processing authority, the process of updating the bill to be compensated based on the compensation result returned by the compensation enterprise is skipped.
4. A method for processing invoices, characterized in that, When applied in a terminal device, the method includes: Obtain the historical compensation amount, average compensation speed, and average user rating for the specified compensation company; The credit rating of the designated compensation company is obtained by weighted summing of the historical compensation amount, the average compensation speed, and the average user rating. Based on the correspondence between the credit rating and the timeout period, the timeout period corresponding to the designated compensation enterprise is determined; In response to the bill holder's instruction for bill compensation, a compensation transaction is sent to the blockchain node. This compensation transaction carries the bill to be compensated, the timeout period, and the designated compensation company. The transaction instructs the blockchain node to invoke the compensation processing logic declared in the smart contract, transfer the modification rights of the bill to be compensated to the designated compensation company, and update the bill according to the compensation result returned by the compensation company. This process continues until the timeout period is reached, at which point the modification rights of the bill to be compensated are transferred back to the bill holder. The designated compensation company is determined based on company order. The bill to be compensated is used when the time to receive the compensation result returned by the designated compensation company is less than the timeout period, and the verification... When a compensation company providing the compensation result is found to be in the specified company order, the compensation result is updated to obtain an updated compensation ticket. This updated compensation ticket is then transferred to subsequent compensation companies according to the company order. If no compensation result is received from the designated compensation company by the timeout period, the compensation ticket is updated using the compensation result returned by the earlier compensation company to obtain a previously updated compensation ticket. The modification rights of this previously updated compensation ticket are transferred to the ticket holder. The previously updated compensation company refers to the compensation company preceding the designated compensation company in the company order. The company order is determined by the compensation processing capabilities among multiple compensation companies. The system receives the previously updated compensation ticket sent by the blockchain node; the previously updated compensation ticket is used to enable the ticket holder to re-initiate a compensation transaction with the unprocessed compensation enterprise, the unprocessed compensation enterprise including the designated compensation enterprise and the subsequent compensation enterprise.
5. A ticket processing device, characterized in that, Applied to blockchain nodes, including: The acquisition module is used to obtain the historical compensation amount, average compensation speed, and average user rating for a specified compensation company. The determination module is used to perform a weighted summation of the historical compensation amount, the average compensation speed, and the average user rating to obtain the credit rating of the designated compensation enterprise. The determining module is further configured to determine the timeout time corresponding to the designated compensation enterprise based on the correspondence between the credit rating and the timeout time, and send the timeout time to the terminal device; The first receiving module is used to receive a compensation transaction sent by the terminal device in response to the bill compensation operation instruction of the bill holder, wherein the compensation transaction carries the bill to be compensated, the timeout time, and the designated compensation company. The processing module, in response to the compensation transaction, invokes the compensation processing logic declared in the smart contract, transfers the modification permission of the bill to be compensated to the designated compensation enterprise, and updates the bill to be compensated according to the compensation result returned by the compensation enterprise, until the timeout period is reached, at which point the modification permission of the bill to be compensated is transferred to the bill holder. The designated compensation enterprise is determined based on enterprise order. The bill to be compensated is updated according to the compensation result when the time to receive the compensation result returned by the designated compensation enterprise is less than the timeout period, and when it is detected that the compensation enterprise providing the compensation result conforms to the enterprise order, thus obtaining an updated bill to be compensated. The updated bill to be compensated is used according to the enterprise order. The order of business continues to be transferred to the subsequent compensation enterprise; if the compensation result is not received from the designated compensation enterprise after the timeout period, the bill to be compensated is used to update it by the compensation result returned by the prior compensation enterprise, resulting in an updated bill to be compensated. The modification rights of the updated bill to be compensated are transferred to the bill holder. The prior compensation enterprise refers to the compensation enterprise that is located before the designated compensation enterprise in the enterprise order; the enterprise order is determined by the enterprise compensation processing capabilities among multiple compensation enterprises; the updated bill to be compensated is used to enable the bill holder to re-initiate a compensation transaction with the unprocessed compensation enterprise, which includes the designated compensation enterprise and the subsequent compensation enterprise.
6. A ticket processing device, characterized in that, Applied in terminal devices, including: The acquisition module is used to obtain the historical compensation amount, average compensation speed, and average user rating for a specified compensation company. The determination module is used to perform a weighted summation of the historical compensation amount, the average compensation speed, and the average user rating to obtain the credit rating of the designated compensation enterprise. The determining module is further configured to determine the timeout period corresponding to the designated compensation enterprise based on the correspondence between the credit rating and the timeout period; The sending module is used to send a compensation transaction to the blockchain node in response to the bill compensation operation instruction from the bill holder. The compensation transaction carries the bill to be compensated, the timeout time, and the designated compensation company. The compensation transaction instructs the blockchain node to invoke the compensation processing logic declared in the smart contract, transfer the modification rights of the bill to be compensated to the designated compensation company, and update the bill according to the compensation result returned by the compensation company until the timeout time is reached, at which point the modification rights of the bill to be compensated are transferred back to the bill holder. The designated compensation company is determined based on company order, and the bill to be compensated is used if the time to receive the compensation result returned by the designated compensation company is less than the timeout time. When it is detected that the compensation enterprise providing the compensation result conforms to the enterprise order, the compensation result is updated to obtain an updated compensation ticket; the updated compensation ticket is used to continue to transfer to subsequent compensation enterprises according to the enterprise order; if the compensation result returned by the designated compensation enterprise is not received by the timeout period, the compensation ticket is used to update the compensation result returned by the earlier compensation enterprise to obtain an earlier updated compensation ticket, and the modification right of the earlier updated compensation ticket is transferred to the ticket holder; the earlier compensation enterprise refers to the compensation enterprise that is located before the designated compensation enterprise in the enterprise order; the enterprise order is determined by the enterprise compensation processing capabilities among multiple compensation enterprises; The second receiving module is used to receive the previously updated compensation ticket sent by the blockchain node; the previously updated compensation ticket is used to enable the ticket holder to re-initiate a compensation transaction with the unprocessed compensation enterprise, the unprocessed compensation enterprise including the designated compensation enterprise and the subsequent compensation enterprise.
7. A ticket processing device, characterized in that, include: Processor and memory; The processor is connected to a memory, wherein the memory is used to store program code, and the processor is used to call the program code to execute the ticket processing method as described in any one of claims 1-4.
8. A computer storage medium, characterized in that, The computer storage medium stores a computer program, which includes program instructions. When executed by a processor, the program instructions perform the ticket processing method as described in any one of claims 1-4.
Citation Information
Patent Citations
Monitoring resume auditing method and device, computer equipment and storage medium
CN109658049A
Bill reimbursement method, device and equipment, and computer storage medium
CN110599276A