Methods, equipment and computer-readable storage media for collecting invoices

Abstract

This invention discloses a method, device, and computer-readable storage medium for collecting invoices. The method includes: acquiring user information and invoice information; generating an invoice file based on the invoice information, the invoice file including an image of the invoice in a preset area, and storing the user information in association with the invoice file; if a user's reimbursement request is received, sending the user information corresponding to the reimbursement request and the invoice file to a reimbursement system. This invention achieves multi-channel collection of invoices by collecting invoice information and generating invoice files, facilitating subsequent invoice reimbursement and improving the convenience of invoice collection and reimbursement.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a method, device and computer-readable storage medium for collecting invoices. Background Technology

[0002] Receipts are commonly used vouchers, including invoices and tickets. When submitting receipts for reimbursement, they need to be verified. Before verification, the receipts need to be collected. However, current solutions rely solely on downloading and saving receipt files to the user's terminal, resulting in low efficiency. Summary of the Invention

[0003] The main objective of this invention is to provide a method, device, and computer-readable storage medium for collecting invoices, aiming to solve the problem of low efficiency in invoice entry.

[0004] To achieve the above objectives, the present invention provides a method for collecting invoices, the method comprising the following steps:

[0005] Obtain user information and ticket information;

[0006] A ticket file is generated based on the ticket information. The ticket file includes a ticket image of a preset area, and the user information is associated with and stored in the ticket file.

[0007] If a user's expense reimbursement request is received, the user information corresponding to the expense reimbursement request and the invoice file are sent to the expense reimbursement system.

[0008] Optionally, the step of generating a bill file based on the bill information includes:

[0009] When the original invoice is not included in the invoice information, an invoice template is determined based on the invoice information, and the invoice file is generated based on the invoice template.

[0010] When the bill information includes the original bill, a bill file is generated based on the original bill.

[0011] Optionally, the step of associating and storing the user information with the ticket document includes:

[0012] Obtain the bill type of the bill file;

[0013] The credibility level of the invoice document is determined based on the method by which the invoice information is collected.

[0014] The ticket file is stored in association with the ticket type, credibility level, user information, and ticket file.

[0015] Optionally, the step of determining the credibility level of the invoice document based on the method of collecting the invoice information includes:

[0016] Based on the historical invoice information corresponding to the collection method, determine the number of invoice reimbursement anomalies corresponding to the collection method;

[0017] The credibility level of the data collection method is determined based on the threshold number to which the number of reimbursement anomalies belongs.

[0018] Optionally, the method further includes:

[0019] Retrieve user query operations on invoice files;

[0020] Output at least one of the following: associated ticket, ticket type, credibility level, and ticket usage status of the ticket file corresponding to the query operation.

[0021] Optionally, when applied to a reimbursement system, the invoice collection method includes:

[0022] Obtain the ticket file, user information, and trust level sent by the user terminal;

[0023] If the invoice document, the user information, and the credibility level meet the reimbursement conditions, the invoice document is reimbursed, and a reimbursement success message is sent to the user terminal.

[0024] Optionally, before the step of reimbursing the invoice document if the invoice document and the user information meet the reimbursement conditions, the method further includes:

[0025] If the invoice document includes the original invoice and the credibility level is greater than the preset level, then the reimbursement condition is determined to be the first reimbursement condition.

[0026] When the invoice document does not include the original invoice, or the credibility level is less than or equal to the preset level, the reimbursement condition is determined to be the second reimbursement condition, and the second reimbursement condition has more items to be verified than the first reimbursement condition.

[0027] Optionally, after the step of obtaining the ticket file, user information, and trust level sent by the user terminal, the method further includes:

[0028] If any of the invoice document, the user information, or the credibility level fails to meet the reimbursement conditions, a reimbursement failure message is generated, which includes the reimbursement conditions that led to the failure.

[0029] The reimbursement failure message is sent to the user's terminal.

[0030] To achieve the above objectives, the present invention also provides a ticket acquisition device, which includes a memory, a processor, and a ticket acquisition program stored in the memory and executable on the processor. When the ticket acquisition program is executed by the processor, it implements the various steps of the ticket acquisition method described above.

[0031] To achieve the above objectives, the present invention also provides a computer-readable storage medium storing a ticket acquisition program, which, when executed by a processor, implements the various steps of the ticket acquisition method described above.

[0032] This invention provides a method, device, and computer-readable storage medium for collecting invoices. The method acquires user information and invoice information; generates invoice files based on the invoice information, the invoice files including invoice images of a preset area, and associates user information with the invoice files for storage; if a user's reimbursement request is received, the method sends the corresponding user information and invoice files to the reimbursement system. By collecting invoice information, multiple methods of invoice collection are achieved, and invoice files are generated, facilitating subsequent invoice reimbursement and improving the convenience of invoice collection and reimbursement. Attached Figure Description

[0033] Figure 1 This is a schematic diagram of the hardware structure of the ticket collection device according to an embodiment of the present invention;

[0034] Figure 2 This is a flowchart illustrating the first embodiment of the document collection method of the present invention;

[0035] Figure 3 This is a schematic diagram of the display interface of the invoice collection method of the present invention;

[0036] Figure 4 This is a schematic diagram of the display interface of the invoice collection method of the present invention;

[0037] Figure 5 This is a schematic diagram of the display interface of the invoice collection method of the present invention;

[0038] Figure 6 This is a flowchart illustrating another embodiment of the document collection method of the present invention;

[0039] Figure 7 This is a schematic diagram of the logical structure of the invoice collection method of the present invention;

[0040] Figure 8 This is a flowchart illustrating another embodiment of the document collection method of the present invention;

[0041] Figure 9 This is a schematic diagram of the display interface of the invoice collection method of the present invention;

[0042] Figure 10 This is a schematic diagram of the display interface of the invoice collection method of the present invention;

[0043] Figure 11 This is a flowchart illustrating another embodiment of the document collection method of the present invention.

[0044] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0045] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0046] The main solution of this invention is as follows: acquiring user information and invoice information; generating an invoice file based on the invoice information, the invoice file including an image of the invoice in a preset area, and storing the user information in association with the invoice file; if a user's reimbursement request is received, sending the corresponding user information and invoice file to the reimbursement system. By collecting invoice information, invoices can be collected through multiple channels, and invoice files can be generated, facilitating subsequent invoice reimbursement and improving the convenience of invoice collection and reimbursement.

[0047] As one implementation solution, ticket collection equipment can be like... Figure 1 As shown.

[0048] The present invention relates to a ticket acquisition device, which includes: a processor 101, such as a CPU, a memory 102, and a communication bus 103. The communication bus 103 is used to enable communication between these components.

[0049] Memory 102 can be high-speed RAM or stable memory (non-volatile memory), such as disk storage. Figure 1 As shown, the memory 102, which is a computer-readable storage medium, may include a ticket acquisition program; and the processor 101 may be used to call the ticket acquisition program stored in the memory 102 and perform the following operations:

[0050] Obtain user information and ticket information;

[0051] A ticket file is generated based on the ticket information. The ticket file includes a ticket image of a preset area, and the user information is associated with and stored in the ticket file.

[0052] If a user's expense reimbursement request is received, the user information corresponding to the expense reimbursement request and the invoice file are sent to the expense reimbursement system.

[0053] Optionally, the processor 101 can be used to call the ticket acquisition program stored in the memory 102 and perform the following operations:

[0054] When the original invoice is not included in the invoice information, an invoice template is determined based on the invoice information, and the invoice file is generated based on the invoice template.

[0055] When the bill information includes the original bill, a bill file is generated based on the original bill.

[0056] Optionally, the processor 101 can be used to call the ticket acquisition program stored in the memory 102 and perform the following operations:

[0057] Obtain the bill type of the bill file;

[0058] The credibility level of the invoice document is determined based on the method by which the invoice information is collected.

[0059] The ticket file is stored in association with the ticket type, credibility level, user information, and ticket file.

[0060] Optionally, the processor 101 can be used to call the ticket acquisition program stored in the memory 102 and perform the following operations:

[0061] Based on the historical invoice information corresponding to the collection method, determine the number of invoice reimbursement anomalies corresponding to the collection method;

[0062] The credibility level of the data collection method is determined based on the threshold number to which the number of reimbursement anomalies belongs.

[0063] Optionally, the processor 101 can be used to call the ticket acquisition program stored in the memory 102 and perform the following operations:

[0064] Retrieve user query operations on invoice files;

[0065] Output at least one of the following: associated ticket, ticket type, credibility level, and ticket usage status of the ticket file corresponding to the query operation.

[0066] Optionally, the processor 101 can be used to call the ticket acquisition program stored in the memory 102 and perform the following operations:

[0067] Obtain the ticket file, user information, and trust level sent by the user terminal;

[0068] If the invoice document, the user information, and the credibility level meet the reimbursement conditions, the invoice document is reimbursed, and a reimbursement success message is sent to the user terminal.

[0069] Optionally, the processor 101 can be used to call the ticket acquisition program stored in the memory 102 and perform the following operations:

[0070] If the invoice document includes the original invoice and the credibility level is greater than the preset level, then the reimbursement condition is determined to be the first reimbursement condition.

[0071] When the invoice document does not include the original invoice, or the credibility level is less than or equal to the preset level, the reimbursement condition is determined to be the second reimbursement condition, and the second reimbursement condition has more items to be verified than the first reimbursement condition.

[0072] Optionally, the processor 101 can be used to call the ticket acquisition program stored in the memory 102 and perform the following operations:

[0073] If any of the invoice document, the user information, or the credibility level fails to meet the reimbursement conditions, a reimbursement failure message is generated, which includes the reimbursement conditions that led to the failure.

[0074] The reimbursement failure message is sent to the user's terminal.

[0075] Based on the hardware architecture of the aforementioned invoice collection device, an embodiment of the invoice collection method of the present invention is proposed.

[0076] Reference Figure 2 , Figure 2 This is a first embodiment of the invoice collection method of the present invention, which includes the following steps:

[0077] Step S10: Obtain user information and ticket information.

[0078] Optionally, user information includes information such as enterprise tax number, enterprise name, employee number, and username.

[0079] Optionally, the invoice information includes at least one of the following: invoice image, invoice QR code, invoice serial number, and invoice type. Invoice types include paper invoices, blockchain invoices, fully electronic invoices, flight itineraries, train or high-speed rail tickets, etc.

[0080] Optionally, the collection of invoice information can be achieved through mobile terminal software apps or mini-programs. Alternatively, collection methods can include WeChat Wallet, WeChat sharing, email, photo recognition, QR code scanning, link sharing, and ride-hailing apps. Among these, photo recognition supports single and multiple images. For example, it can capture images of the front and back of the invoice. The photo recognition function can also capture partial images of the invoice, such as images of seals.

[0081] Optionally, such as Figure 3 As shown, the mobile terminal has a ticket collection and management mini-program. The mini-program offers a full range of ticket collection methods. Once bound, the mini-program can be opened directly for ticket collection in subsequent transactions. The mini-program has high scanning and recognition efficiency and can directly use the associated WeChat Wallet function to receive tickets.

[0082] Optionally, such as Figure 4 As shown, the mobile terminal has a ticket collection and management H5 page, in which the banner background and ticket collection icon can be customized, and the functions of scanning QR codes to collect tickets and collecting tickets via WeChat Wallet can be developed accordingly.

[0083] Optionally, the invoice information can be collected via a PC (Personal Computer). Alternatively, the PC can be used for invoice collection via barcode scanner, scanner, batch import of compressed files, or import of Excel spreadsheets.

[0084] Optionally, such as Figure 5 As shown, the PC terminal for ticket collection and management provides batch collection methods such as QR code ticket collection, barcode scanner, batch import, and scanner ticket collection. It can also manage and view all tickets and supports custom configuration of user identifiers.

[0085] Optionally, before step S10, the method further includes: when the user scans the code to log in to the user terminal's software or mini-program, retrieving all the added invoice files of the user information and displaying them on the user terminal, wherein each invoice file corresponds to the invoice's reimbursement status.

[0086] Step S20: Generate a ticket file based on the ticket information. The ticket file includes a ticket image of a preset area, and the user information is associated with and stored in the ticket file.

[0087] Optionally, when the ticket information includes the original ticket, a ticket file is directly generated based on the ticket information. The ticket file includes images of the ticket in preset areas. When the ticket file is an invoice, the ticket image includes images of the ticket header area, the area containing the seal, or the original electronic ticket. When the ticket file is a train ticket, the ticket image includes images of the areas containing the train number, time, and address, or the original train ticket. When the ticket file is an airline ticket, the ticket image includes images of the flight number, time, departure point, and destination, or the original airline ticket.

[0088] Optionally, user information can be associated with and stored locally on the user's terminal.

[0089] Optionally, user information can be associated with and stored in a cloud database. If a user terminal needs to obtain a ticket file, it can retrieve the ticket file corresponding to the user information from the cloud database.

[0090] Optionally, when the original invoice is not present in the invoice information, a preset invoice template corresponding to the invoice information is determined, and an invoice file is generated based on the preset invoice template and the invoice information. Optionally, when the original invoice is present in the invoice file, it is not necessary to generate an invoice file based on the invoice information.

[0091] Optionally, when the original document is not present in the document information, the credibility level of the document is determined to be the first credibility level; when the original document is present in the document information, the credibility level of the document is determined to be the second credibility level, where the first credibility level is lower than the second credibility level.

[0092] Optionally, the data collection method for invoice information is determined, including terminal device information. A credibility level corresponding to each data collection method is determined, and the credibility level is associated with and stored in relation to user information and invoice documents. Upon receiving a user's reimbursement request, the user information, invoice documents, and credibility level corresponding to that request are sent to the reimbursement system.

[0093] Optionally, different data collection methods correspond to different credibility levels. Specifically, historical invoice information from different collection methods is analyzed and statistically analyzed to obtain the number of invoice reimbursement anomalies corresponding to each method. The credibility level of each collection method is determined based on the threshold value to which the number of anomalies falls. Optionally, anomalies can include invoice forgery, unclear invoices, and other abnormal situations. Optionally, when the number of anomalies exceeds a preset first threshold, the credibility level is determined to be Level 1; when the number of anomalies is less than or equal to the preset first threshold but greater than a preset second threshold, the credibility level is determined to be Level 2; when the number of anomalies is less than or equal to the preset second threshold, the credibility level is determined to be Level 3. The preset first threshold is greater than the preset second threshold, Level 1 is lower than Level 2, and Level 2 is lower than Level 3.

[0094] Optionally, step S20 further includes: obtaining the bill type of the bill file; determining the credibility level of the bill file based on the collection method of the bill information; and storing the bill file in association with the bill type, credibility level, user information, and the bill file. The bill type includes paper invoices, blockchain invoices, fully electronic invoices, flight itineraries, train or high-speed rail tickets, etc.

[0095] Step S30: If a user's reimbursement request is received, the user information corresponding to the reimbursement request and the invoice file are sent to the reimbursement system.

[0096] Optionally, before a user submits an expense report, all invoices and receipts corresponding to the user's information are retrieved. The status of each invoice and receipt includes whether it is used or not. Unused invoices and receipts can be submitted for expense report, while used invoices and receipts can be submitted for expense report results, including whether the expense report was successful, the expense report time, or the expense report amount.

[0097] Optionally, upon receiving a user's reimbursement request, the system sends the corresponding user information and receipt documents to the reimbursement system, so that the system can process the reimbursement based on the user information and receipt documents.

[0098] Optionally, after step S30, the method further includes: obtaining the reimbursement result returned by the reimbursement system; if the reimbursement is successful based on the reimbursement result, updating the usage status of the invoice to reimbursed; if the reimbursement fails based on the reimbursement result, obtaining the reason information corresponding to the reimbursement failure.

[0099] Optionally, the system acquires the user's query operation on the invoice file; and outputs at least one of the following: the associated invoice, invoice type, credibility level, and invoice usage status of the invoice file corresponding to the query operation. Optionally, when the query operation is to query the invoice type of the invoice file, the system outputs the invoice type of the invoice file; when the query operation is to query the credibility level of the invoice file, the system outputs the credibility level of the invoice file; when the query operation is to query the invoice usage status of the invoice file, the system outputs the invoice usage status of the invoice file, wherein the usage status includes "reimbursed" or "reimbursement failed".

[0100] In one embodiment, such as Figure 6 As shown, the reimbursement system generates a QR code. Users open the scan function of the app or mini-program, scan the QR code, and the system launches a data collection page within the app or mini-program. Users add receipts in the app or mini-program, including collecting receipts from their local receipt folder before reimbursement, collecting receipts during reimbursement, and displaying the collected receipts. When a user submits a reimbursement request, the system associates the receipts with the user's information. The system queries the receipt files selected by the user, and the user's terminal receives the receipt data (the receipt file). The system notifies the user's terminal of the reimbursement result, and the user's terminal updates the receipt usage status. If the reimbursement is successful, the receipt is updated to "used"; if the reimbursement fails, the receipt is updated to "unused."

[0101] In one embodiment, such as Figure 7As shown, the interaction methods between the user terminal and the reimbursement system include: cloud direct connection / API (Application Programming Interface), invoice collection and management mini-program, H5 / PC embedding, etc.; the secure access methods between the user terminal and the reimbursement system include: gateway routing policies, authentication management, illegal character filtering, etc. The business services of the user terminal include: barcode scanning collection, manual data entry, OCR recognition, WeChat wallet, email invoice collection, and link invoice collection. The basic services of the user terminal include: email service, data statistical analysis, PDF / OFD parsing, file storage, etc. The underlying services of the user terminal include: barcode scanning engine, image recognition, database, object storage, message queue, etc.

[0102] In this embodiment, user information and invoice information are acquired; an invoice file is generated based on the invoice information, the invoice file including an image of the invoice in a preset area, and the user information is associated with and stored in the invoice file; if a user's reimbursement request is received, the user information corresponding to the reimbursement request and the invoice file are sent to the reimbursement system. By collecting invoice information, invoices are collected through multiple channels, and invoice files are generated, which facilitates subsequent invoice reimbursement and improves the convenience of invoice collection and reimbursement.

[0103] Reference Figure 8 , Figure 8 This is a second embodiment of the invoice collection method of the present invention, the method comprising the following steps:

[0104] Step S40: Obtain the ticket file and user information sent by the user terminal;

[0105] Step S50: If the invoice document and the user information meet the reimbursement conditions, reimburse the invoice document and send a reimbursement success message to the user terminal.

[0106] Optionally, when the reimbursement system is located on a PC, such as Figure 9 As shown, the PC version displays information such as expense details. When the expense reimbursement system is set up on a mobile device, as... Figure 10 As shown, the mobile terminal's display page includes information such as reimbursement details. Meeting the reimbursement criteria includes: the invoice document meeting the reimbursement criteria, specifically, the invoice header verification meeting the reimbursement criteria, the seal verification meeting the reimbursement criteria, and the original electronic invoice acquisition verification meeting the reimbursement criteria; the invoice document being a non-duplicate reimbursement; and the user information meeting the reimbursement criteria including the user information not being on a blacklist.

[0107] Optionally, if the invoice document includes the original invoice and the credibility level is greater than a preset level, indicating that the invoice document to be reimbursed has high credibility, then the reimbursement condition is determined as the first reimbursement condition. Optionally, if the invoice document does not include the original invoice, or the credibility level is less than or equal to the preset level, indicating that the invoice document to be reimbursed has low credibility, then the reimbursement condition is determined as the second reimbursement condition. The second reimbursement condition has more items to be verified than the first reimbursement condition. For example, the items to be verified in the first reimbursement condition include invoice header verification, seal verification, user blacklist verification, etc., while the items to be verified in the second reimbursement condition include verification of the original electronic invoice and user blacklist verification, etc.

[0108] Optionally, if any of the invoice document, the user information, or the credibility level does not meet the reimbursement conditions, a reimbursement failure message is generated, the reimbursement failure message including the reimbursement conditions for failure, and the reimbursement failure message is sent to the user terminal.

[0109] Optionally, the ticket number in the ticket document is verified to meet the corresponding preset ticket number conditions; after the ticket number verification is successful, the ticket number is matched with the ticket numbers of all tickets already entered in the database and the ticket numbers of all tickets in the locked list; after the required information is verified successfully, it is determined that the reimbursement conditions are met.

[0110] In one embodiment, such as Figure 11 As shown, the reimbursement system adds a new reimbursement form, calls the APP and mini-program interfaces to select invoices or query user and invoice information, and allows users to search for receipts in the APP or mini-program. It also supports various receipt collection methods, including batch import, manual import, WeChat Wallet import, email receipt, link receipt, QR code receipt, and photo receipt. The APP or mini-program sends a notification of successful collection to the reimbursement system. If receipt collection is successful, the system displays the receipt information and allows submission of a reimbursement claim. If receipt collection fails, a notification message is issued.

[0111] In this embodiment, the technical solution obtains the invoice file, user information, and credibility level sent by the user terminal. If the invoice file, user information, and credibility level meet the reimbursement conditions, the invoice file is reimbursed, and a reimbursement success message is sent to the user terminal. By verifying the invoice file, user information, and credibility level, the invoice file from the user terminal is reimbursed, thus improving the efficiency of invoice reimbursement.

[0112] The present invention also provides a ticket acquisition device, the ticket acquisition device including a memory, a processor, and a ticket acquisition program stored in the memory and executable on the processor, wherein when the ticket acquisition program is executed by the processor, it implements the various steps of the ticket acquisition method described in the above embodiments.

[0113] The present invention also provides a computer-readable storage medium storing a ticket collection program, which, when executed by a processor, implements the various steps of the ticket collection method described in the above embodiments.

[0114] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0115] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, system, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, system, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, system, article, or apparatus that includes that element.

[0116] Through the above description of the embodiments, those skilled in the art can clearly understand that the systems described in the embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a computer-readable storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device (which may be a mobile phone, computer, parking management device, air conditioner, or network device, etc.) to execute the systems described in the various embodiments of the present invention.

[0117] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.

Claims

1. A method for collecting invoices, characterized in that, The ticket collection method, applied to user terminals, includes: Obtain user information and ticket information; A bill file is generated based on the bill information, and the bill file includes a bill image of a preset area; Obtain the bill type of the bill file; Based on the historical invoice information corresponding to the collection method, determine the number of invoice reimbursement anomalies corresponding to the collection method, wherein the collection method includes the device information of the collection terminal; The credibility level of the data collection method is determined based on the threshold number to which the number of reimbursement anomalies belongs. The invoice file is stored in association with the invoice type, credibility level, user information, and invoice file. If a user's expense reimbursement request is received, the user information, the credibility level, and the invoice file corresponding to the expense reimbursement request will be sent to the expense reimbursement system.

2. The invoice collection method as described in claim 1, characterized in that, The step of generating a bill file based on the bill information includes: When the original invoice is not included in the invoice information, an invoice template is determined based on the invoice information, and the invoice file is generated based on the invoice template. When the bill information includes the original bill, a bill file is generated based on the original bill.

3. The invoice collection method as described in claim 1, characterized in that, The method further includes: Retrieve user query operations on invoice files; Output at least one of the following: associated ticket, ticket type, credibility level, and ticket usage status of the ticket file corresponding to the query operation.

4. A method for collecting invoices, characterized in that, The invoice collection method, applied to an expense reimbursement system, includes: The system acquires a receipt file, user information, and credibility level sent by a user terminal; wherein the user terminal acquires user information and receipt information; a receipt file is generated based on the receipt information, the receipt file including a receipt image of a preset area; the receipt type of the receipt file is acquired; the number of receipt reimbursement anomalies corresponding to the collection method is determined based on historical receipt information corresponding to the collection method, the collection method including device information of the collection terminal; the credibility level corresponding to the collection method is determined based on the number of anomalies to which the number of anomalies belongs; the receipt file is stored in association with the receipt type, credibility level, user information, and receipt file; if a user's reimbursement operation is received, the user information, credibility level, and receipt file corresponding to the reimbursement operation are sent to the reimbursement system; If the invoice document, the user information, and the credibility level meet the reimbursement conditions, the invoice document is reimbursed, and a reimbursement success message is sent to the user terminal.

5. The invoice collection method as described in claim 4, characterized in that, Before the step of reimbursing the invoice document if the invoice document and the user information meet the reimbursement conditions, the method further includes: If the invoice document includes the original invoice and the credibility level is greater than the preset level, then the reimbursement condition is determined to be the first reimbursement condition. When the invoice document does not include the original invoice, or the credibility level is less than or equal to the preset level, the reimbursement condition is determined to be the second reimbursement condition, and the second reimbursement condition has more items to be verified than the first reimbursement condition.

6. The invoice collection method as described in claim 4, characterized in that, After the steps of obtaining the ticket file, user information, and trust level sent by the user terminal, the method further includes: If any of the invoice document, the user information, or the credibility level fails to meet the reimbursement conditions, a reimbursement failure message is generated, which includes the reimbursement conditions that led to the failure. The reimbursement failure message is sent to the user's terminal.

7. A ticket collection device, characterized in that, The document acquisition device includes a memory, a processor, and a document acquisition program stored in the memory and executable on the processor. When the document acquisition program is executed by the processor, it implements the various steps of the document acquisition method as described in any one of claims 1-3 or 4-6.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a ticket acquisition program, which, when executed by a processor, implements the various steps of the ticket acquisition method as described in any one of claims 1-3 or 4-6.

Images