A method, device, electronic device and storage medium for collecting input invoice files

Abstract

The present invention provides a method, device, electronic device and storage medium for collecting input invoice files. The method comprises: after synchronizing the invoice data to be processed, comparing and verifying the synchronized invoice data, and determining the invoice file after successful verification as the input invoice file, so that not only the input invoice file can be automatically collected to save labor costs, but also the input invoice file can be obtained by performing multi-level verification on the invoice data to be processed, so that the obtained input invoice file is more accurate, thereby improving the accuracy of obtaining the input invoice file.

Description

Technical Field

[0001] This application relates to the field of financial and tax management, specifically to a method, apparatus, electronic device, and storage medium for collecting input invoice documents. Background Technology

[0002] Input invoices are invoices issued by taxpayers when purchasing goods, and they need to be collected through the value-added tax system.

[0003] Currently, input invoices are typically collected manually by corporate finance staff. However, manual entry is not only prone to errors but also extremely inefficient, especially for large enterprises with a large number of invoices. Manual entry is time-consuming and reduces work efficiency. While some methods compare input invoice data with relevant databases, this method alone is prone to inaccuracies, leading to the acquisition of incorrect input invoice data. Summary of the Invention

[0004] In view of the shortcomings of the above-mentioned related technologies, this application provides a method, apparatus, electronic device and storage medium for collecting input invoice documents to solve the above-mentioned technical problems.

[0005] This application provides a method for collecting input invoice data. The method includes: receiving a callback notification for input invoice data, synchronizing the input invoice data to be processed, generating an input invoice file to be compared, and sending the input invoice file to be compared to the invoice file processing core service; parsing the input invoice file to be compared through the invoice file processing core service to obtain an input invoice file to be verified; verifying the input invoice file to be verified, and determining the successfully verified input invoice file to be verified as the input invoice file, thereby completing the collection of input invoice files.

[0006] In one embodiment of this application, synchronizing the input invoice data to be processed includes: identifying the type of the input invoice data to be processed; obtaining four elements of the input invoice data to be processed based on the type of the input invoice data to be processed; generating a hash value based on the four elements; performing hash value matching in the input invoice data database according to the hash value; if the same hash value exists in the input invoice data database, the synchronization is completed, and the input invoice data database has a correspondence between hash values ​​and the four elements; if the same hash value does not exist in the input invoice data database, a prompt message is sent, the prompt message including alarm information.

[0007] In one embodiment of this application, the process of parsing the input invoice file to be compared and obtaining the input invoice file to be verified through the core service of invoice file processing includes: comparing the invoice files in the whitelist with the input invoice file to be compared based on the Hypertext Transfer Protocol; if the comparison is successful, authenticating the input invoice file to be compared using an access code and a token, and determining the verified input invoice file to be compared as the input invoice file to be verified; if the comparison fails, sending a prompt message, the prompt message including alarm information.

[0008] In one embodiment of this application, the type of input invoice data to be processed is identified, and four elements of the input invoice data to be processed are obtained based on the type of input invoice data to be processed, including: if the input invoice data to be processed is a VAT special invoice, then the four elements of the input invoice data to be processed include invoice number, invoice code, invoice date, and amount excluding tax. If the input invoice data to be processed is a VAT ordinary invoice, then the four elements of the input invoice data to be processed include invoice number, invoice code, invoice date, and verification code.

[0009] In one embodiment of this application, verifying the input invoice document to be verified and determining the successfully verified input invoice document as an input invoice document includes: identifying the invoice number and invoice code of the input invoice document to be verified; using the invoice number and invoice code as an index to compare the input invoice document to be verified, obtaining a comparison result, and recording the comparison result in a comparison log; and determining the input invoice document to be verified corresponding to the latest comparison result in the comparison log as the input invoice document.

[0010] In one embodiment of this application, after the collection of input invoice documents is completed, the process includes: recording an input invoice document collection log, the collection log including the collection time of the input invoice documents, the number of input invoice documents collected, and collection failures of the input invoice documents; and performing fault repair based on the collection log.

[0011] In one embodiment of this application, before processing the input invoice data to be processed, the method further includes: synchronizing the input invoice data to be processed; if the synchronization is successful, then asynchronously processing the synchronized input invoice data to be processed; if the synchronization fails, then sending a prompt message, the prompt message including an alarm message.

[0012] This application provides an apparatus for collecting input invoice data. The apparatus includes: a generation module, which, in response to an input invoice data synchronization request, synchronizes the input invoice data to be processed, generates an input invoice file to be compared, and sends a processing completion request; a sending module, which receives the processing completion request and sends the input invoice file to be compared to an invoice file processing core service; a parsing module, which parses the input invoice file to be compared through the invoice file processing core service to obtain an input invoice file to be verified and stores the input invoice file to be verified in an input invoice database; and a verification module, which verifies the input invoice file to be verified and determines the successfully verified input invoice file as an input invoice file, thereby completing the collection of input invoice files.

[0013] Beneficial effects: After synchronizing the invoice data to be processed, the synchronized invoice data is compared and verified, and the invoice files that are successfully verified are identified as input invoice files. This not only automatically collects input invoice files, saving labor costs, but also makes the obtained input invoice files more accurate by performing multi-level verification on the invoice data to be processed, thus improving the accuracy rate of obtaining input invoice files.

[0014] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0015] Figure 1 This is a flowchart illustrating an exemplary embodiment of the present application of a method for collecting input invoice documents;

[0016] Figure 2 This is a timing diagram illustrating an exemplary embodiment of the present application of a method for collecting input invoice documents;

[0017] Figure 3 This is a block diagram illustrating an input invoice document collection device, as shown in an exemplary embodiment of this application;

[0018] Figure 4 This is a schematic diagram illustrating the structure of an electronic device as shown in an exemplary embodiment of this application. Detailed Implementation

[0019] The following specific examples illustrate the implementation of this application. Those skilled in the art can easily understand other advantages and effects of this application from the content disclosed in this specification. This application can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of this application. It should be noted that, unless otherwise specified, the following embodiments and features in the embodiments can be combined with each other.

[0020] It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of this application. Therefore, the drawings only show the components related to this application and are not drawn according to the actual number, shape and size of the components in the actual implementation. In the actual implementation, the form, quantity and proportion of each component can be arbitrarily changed, and the layout of the components may also be more complex.

[0021] It should be noted that in this application, terms such as "first" and "second" are merely for distinguishing similar objects, and do not limit the order or sequence of similar objects. The variations of "including" and "having" indicate that the scope covered by the subject of the word is not exclusive, except for the examples shown by the word.

[0022] It is understood that the various numerical designations, step numbers, and other identifiers recorded in this application are for descriptive convenience and are not intended to limit the scope of this application. The size of the identifiers in this application does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

[0023] In the following description, numerous details are explored to provide a more thorough explanation of embodiments of the present application. However, it will be apparent to those skilled in the art that embodiments of the present application may be practiced without these specific details. In other embodiments, well-known structures and devices are shown in block diagram form rather than in detail to avoid obscuring embodiments of the present application.

[0024] The embodiments of this application respectively propose a method for collecting input invoice documents, an apparatus for collecting input invoice documents, an electronic device, a computer-readable storage medium, and a computer program product. These embodiments will be described in detail below.

[0025] First, it's important to note that the VAT invoice management platform has a dedicated client application for each enterprise user. Enterprise users log in to the platform through this client. The platform generates a database based on the enterprise user's client information, facilitating the retrieval of invoice information. The service interface sends the input invoice information found in the database to the electronic ledger module of the enterprise's tax-related accounting planning management system. This module receives and verifies the input invoice information and saves it. The VAT invoice management platform's query interface then retrieves the verified invoice information saved in the electronic ledger module through the service interface of the enterprise's tax-related accounting planning management system.

[0026] Please see Figure 1 , Figure 1 This is a flowchart illustrating an exemplary embodiment of this application, showing a method for collecting input invoice data. For example... Figure 1 As shown, in an exemplary embodiment, the input invoice data collection method includes at least steps S110 to S140, which are described in detail below:

[0027] Step S110: Receive input invoice data callback notification, synchronize the input invoice data to be processed, and generate input invoice files to be compared.

[0028] In one embodiment of this application, the input invoice data for the day is synchronized periodically via an input invoice data collection protocol.

[0029] In one embodiment of this application, the input invoice data of the day is synchronized periodically through an input invoice data collection protocol. Specifically, this involves encapsulating a service interface that calls a timer in the backend of the enterprise tax-related accounting planning management system. The timer triggers the service interface to search for and obtain relevant invoice information, completing the synchronization and verification of input invoices. The VAT invoice management platform obtains the synchronized and verified invoice information through the front-end query interface and the service interface encapsulated in the backend of the enterprise tax-related accounting planning management system. This achieves automatic acquisition of invoice information, eliminating the need for manual entry and verification, and improving work efficiency.

[0030] Step S120: Send the input invoice files to be compared to the core invoice file processing service.

[0031] Step S130: The input invoice file to be compared is parsed through the core service of invoice file processing to obtain the input invoice file to be verified.

[0032] Step S140: Verify the input invoice file to be verified, and determine the successfully verified input invoice file as the input invoice file to complete the collection of input invoice files.

[0033] exist Figure 1 In this process, after synchronizing the invoice data to be processed, the synchronized invoice data is compared and verified, and the invoice file that is successfully verified is identified as the input invoice file. This not only automatically collects input invoice files, saving labor costs, but also makes the obtained input invoice files more accurate by performing multi-level verification on the invoice data to be processed, thus improving the accuracy rate of obtaining input invoice files.

[0034] In one embodiment of this application, processing the input invoice data to be processed includes: synchronizing the input invoice data to be processed; if synchronization is successful, then asynchronously processing the synchronized input invoice data to be processed; if synchronization fails, then sending a prompt message, including an alarm message. Because the VAT invoice management platform has a large data volume, a callback service is provided to process the invoice data. A separate sub-thread requests the invoice data, while the main thread continues to respond to user interactions. This ensures that even if the system crashes while waiting for a response, it can continue to wait for a response upon restarting, guaranteeing the acquisition of input invoice data.

[0035] In one embodiment of this application, a synchronous request refers to the client sending a request to the server, waiting for the server's response, and returning the response after processing. The client browser does not perform any other data request interactions. Therefore, when synchronously requesting data, any operation performed on the user interface is invalid and unresponsive until the data request is successful. User interaction only responds after the data request is complete, which often freezes the main thread. If the service crashes while blocked during operation, it cannot reconnect to the ongoing call upon restart, resulting in lost response. An asynchronous request, on the other hand, is triggered by an event. The server processes the request and returns the response, but the client browser can perform other data request interactions. In this case, a separate sub-thread requests data while the main thread continues to handle user interaction, ensuring smooth operation and improved user experience. Furthermore, with asynchronous requests, even if the system crashes while waiting for a response, it can continue waiting upon system restart.

[0036] In one embodiment of this application, synchronizing the input invoice data to be processed includes: identifying the type of the input invoice data to be processed; obtaining the four elements of the input invoice data to be processed based on the type of the input invoice data; generating a hash value based on the four elements; matching the hash value in the input invoice data database; if the same hash value exists in the input invoice data database, the synchronization is completed, and a correspondence between the hash value and the four elements exists in the input invoice data database; if the same hash value does not exist in the input invoice data database, a prompt message is sent, including an alarm message. By comparing the hash values ​​of the invoice data to be processed to obtain the input invoice file, the obtained input invoice file is more accurate, improving the accuracy rate of obtaining the input invoice file.

[0037] In one embodiment of this application, the invoice file processing core service parses the input invoice file to be compared to obtain the input invoice file to be verified. This includes: comparing invoice files in a whitelist with the input invoice file to be compared based on the Hypertext Transfer Protocol; if the comparison is successful, authenticating the input invoice file to be compared using an access code and token, and confirming the verified input invoice file as the input invoice file to be verified; if the comparison fails, sending a prompt message, including an alarm message. Obtaining the input invoice file to be verified from the input invoice file to be compared makes the obtained input invoice file more accurate, improving the accuracy rate of obtaining input invoice files. Furthermore, it can promptly issue prompt messages indicating comparison failures, facilitating technicians to locate faults and avoid greater losses.

[0038] In one embodiment of this application, the type of input invoice data to be processed is identified, and the four elements of the input invoice data to be processed are obtained based on the type of input invoice data to be processed, including: if the input invoice data to be processed is a VAT special invoice, then the four elements of the input invoice data to be processed include invoice number, invoice code, invoice date, and amount excluding tax. If the input invoice data to be processed is a VAT ordinary invoice, then the four elements of the input invoice data to be processed include invoice number, invoice code, invoice date, and verification code.

[0039] In one embodiment of this application, the verification of the input invoice document to be verified, and the determination of the successfully verified input invoice document as the input invoice document, includes: identifying the invoice number and invoice code of the input invoice document to be verified; using the invoice number and invoice code as indexes to compare the input invoice document to be verified, obtaining the comparison result, and recording the comparison result in a comparison log; and determining the input invoice document to be verified corresponding to the latest comparison result in the comparison log as the input invoice document. By performing multiple comparisons to obtain the input invoice document, the obtained input invoice document becomes more accurate, thus improving the accuracy rate of obtaining input invoice documents.

[0040] In one embodiment of this application, after the collection of input invoice documents is completed, the process includes: recording an input invoice document collection log, which includes the collection time, the number of input invoice documents collected, and any collection failures. Fault repair is then performed based on the collection log. This facilitates technicians in locating and promptly repairing faults, preventing greater losses.

[0041] In one embodiment of this application, all interfaces interacting with data are monitored. All provided interfaces undergo parameter validation of the incoming data to ensure the integrity of the requested data. In this embodiment, the status of each service is monitored, specifically including the server's CPU (Central Processing Unit), memory, disk, and network. By providing operation and maintenance monitoring services, email alerts and alert logs are obtained, and alert notifications can be sent via email, SMS, WeChat Work, and other methods. In this embodiment, the collection logs of input invoice documents are analyzed, and fault repair is performed based on these logs.

[0042] In one embodiment of this application, the collection logs for input invoice files are ELK (ElasticSearch, Logstash, and Kibana) logs, displayed through a real-time data dashboard, including status codes, access domain rankings, IP rankings, and map distribution. ELK logs are a complete log collection, analysis, and display solution provided by the ElasticSearch open-source ecosystem. ElasticSearch is a near real-time distributed search and analysis engine used for full-text search, structured search, and analysis. It is a search engine built on the full-text search engine Apache Lucene and written in Java. Logstash is a data collection, filtering, and analysis engine with near real-time transmission capabilities, used for data collection, parsing, and filtering. Kibana is a visualization platform that provides analysis and display for ElasticSearch. Kibana can search and interact with data in ElasticSearch's index and generate various dimensional tables, graphs, and dashboards. The collection status of input invoice files is collected based on ELK logs, and fault repair is performed when faults are detected. This facilitates technicians in locating and promptly fixing faults, preventing greater losses.

[0043] In one embodiment of this application, Figure 2 This application illustrates a timing diagram of an exemplary input invoice data collection method, as shown below. Figure 2 As shown, the enterprise side triggers a task daily at set times via a task scheduler, sending a synchronization request to retrieve input invoice data. The VAT invoice management platform receives this request, returns a success message, asynchronously processes the pending invoice data, and sends an input invoice data callback notification to the enterprise side. Upon receiving the callback notification, the enterprise side obtains the pending input invoice data through a file acquisition interface, parses the input invoice file to be compared using the core invoice file processing service, obtains the input invoice file to be verified, synchronizes the verified file, stores it in the input invoice file database, and performs verification to obtain the final input invoice file. This process, after synchronizing the pending invoice data, compares and verifies the synchronized data, identifying the successfully verified invoice file as the input invoice file, not only automatically collects input invoice files, saving labor costs, but also improves the accuracy of input invoice file retrieval through multi-level verification of the pending invoice data.

[0044] Please see Figure 3 , Figure 3This is a block diagram illustrating an exemplary embodiment of the input invoice document collection device of this application. The exemplary input invoice document collection device includes: a generation module 301, a sending module 302, a parsing module 303, and a verification module 304. Specifically, the generation module 301 receives input invoice data callback notifications, synchronizes the input invoice data to be processed, and generates an input invoice file to be compared; the sending module 302 sends the input invoice file to be compared to the core service of invoice document processing; the parsing module 303 parses the input invoice file to be compared through the core service of invoice document processing to obtain the input invoice file to be verified, and stores the input invoice file to be verified in the input invoice database; the verification module 304 verifies the input invoice file to be verified, and determines the successfully verified input invoice file as the input invoice file, thereby completing the collection of input invoice files. After synchronizing the invoice data to be processed, the synchronized invoice data is compared and verified, and the invoice files that are successfully verified are identified as input invoice files. This not only automatically collects input invoice files, saving labor costs, but also makes the obtained input invoice files more accurate by performing multi-level verification on the invoice data to be processed, thus improving the accuracy rate of obtaining input invoice files.

[0045] In an exemplary embodiment of the present invention, the generation module 301 is used to identify the type of input invoice data to be processed, obtain the four elements of the input invoice data to be processed based on the type of input invoice data, generate a hash value based on the four elements, perform hash value matching in the input invoice data database according to the hash value, if the same hash value exists in the input invoice data database, the process is completed synchronously, and the input invoice data database has a correspondence between hash value and four elements; if the same hash value does not exist in the input invoice data database, a prompt message is sent, the prompt message including alarm information.

[0046] In an exemplary embodiment of the present invention, the parsing module 303 is used to compare the invoice files in the whitelist with the input invoice files to be compared based on the Hypertext Transfer Protocol; if the comparison is successful, the input invoice files to be compared are authenticated by the access code and token, and the verified input invoice files to be compared are determined as input invoice files to be verified; if the comparison fails, a prompt message is sent, including alarm information.

[0047] In an exemplary embodiment of the present invention, the parsing module 303 is further configured to identify the type of the input invoice data to be processed, and obtain the four elements of the input invoice data to be processed based on the type of the input invoice data to be processed, including: if the input invoice data to be processed is a VAT special invoice, then the four elements of the input invoice data to be processed include invoice number, invoice code, invoice date, and amount excluding tax. If the input invoice data to be processed is a VAT ordinary invoice, then the four elements of the input invoice data to be processed include invoice number, invoice code, invoice date, and verification code.

[0048] In an exemplary embodiment of the present invention, the verification module 304 is used to identify the invoice number and invoice code of the input invoice file to be verified, use the invoice number and invoice code as indexes to compare the input invoice file to be verified, obtain the comparison result, and record the comparison result in the comparison log; the input invoice file to be verified corresponding to the latest comparison result in the comparison log is determined as the input invoice file.

[0049] In an exemplary embodiment of the present invention, the input invoice document acquisition device further includes a synchronization module 305, which is used to synchronize the input invoice data to be processed before synchronizing the input invoice data to be processed. If the synchronization is successful, the synchronized input invoice data to be processed is processed asynchronously; if the synchronization fails, a prompt message is sent, which includes an alarm message.

[0050] In an exemplary embodiment of the present invention, the input invoice document acquisition device further includes a fault repair module 306, which is used to record the acquisition log of the input invoice document, including the acquisition time of the input invoice document, the acquisition quantity of the input invoice document, and acquisition failures of the input invoice document; and to perform fault repair based on the acquisition log.

[0051] Please see Figure 4 , Figure 4 This is a schematic diagram illustrating the structure of an electronic device according to an exemplary embodiment of this application. It should be noted that... Figure 4 The electronic device 400 shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0052] like Figure 4 As shown, the electronic device 400 includes a processor 401, a memory 402, and a communication bus 403; the communication bus 403 is used to connect the processor 401 and the memory 402; the processor 401 is used to execute the computer program stored in the memory 402 to implement one or more of the input invoice document acquisition methods as described in the above embodiments.

[0053] This embodiment also provides a computer-readable storage medium storing a computer program thereon. When executed by a computer's processor, the computer program causes the computer to perform the input invoice document collection method as described above. This computer-readable storage medium may be included in the electronic device described in the above embodiments, or it may exist independently without being assembled into the electronic device. This embodiment also provides a computer program product or computer program including computer instructions stored in the computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the input invoice document collection method provided in the various embodiments above.

[0054] The electronic device provided in this embodiment includes a processor, a memory, a transceiver, and a communication interface. The memory and the communication interface are connected to the processor and the transceiver and complete communication between them. The memory is used to store computer programs, the communication interface is used to perform communication, and the processor and the transceiver are used to run the computer programs, so that the electronic device performs the various steps of the above method.

[0055] In this embodiment, the memory may include random access memory (RAM) and may also include non-volatile memory, such as at least one disk storage device.

[0056] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0057] As will be understood by those skilled in the art, the computer-readable storage medium described in this embodiment allows for the implementation of all or part of the steps in the above method embodiments by computer program-related hardware. The aforementioned computer program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM (Read-Only Memory), RAM (Random Access Memory), magnetic disks, or optical disks.

[0058] The above embodiments are merely illustrative of the principles and effects of this application and are not intended to limit this application. Any person skilled in the art can modify or alter the above embodiments without departing from the spirit and scope of this application. Therefore, all equivalent modifications or alterations made by those skilled in the art without departing from the spirit and technical concept disclosed in this application should still be covered by the claims of this application.

Claims

1. A method for collecting input invoice documents, characterized in that: The input invoice document collection method includes: Receive the input invoice data callback notification, synchronize the input invoice data to be processed, and generate the input invoice file to be compared; wherein, the process of synchronizing the input invoice data to be processed includes: identifying the type of the input invoice data to be processed, and obtaining the four elements of the input invoice data to be processed based on the type of the input invoice data to be processed; generating a hash value based on the four elements, and performing hash value matching in the input invoice data database according to the hash value; if the same hash value exists in the input invoice data database, the synchronization is completed, and the input invoice data database has a corresponding relationship between the hash value and the four elements; if the same hash value does not exist in the input invoice data database, a prompt message is sent, and the prompt message includes an alarm message; and after the synchronization of the input invoice data to be processed is successful, asynchronously process the synchronized input invoice data to be processed; after the synchronization of the input invoice data to be processed fails, send the prompt message; Sending the input invoice file to be compared to the invoice file processing core service; The invoice file processing core service is used to parse the input invoice file to be compared, and obtain the input invoice file to be verified; including: based on the hypertext transfer protocol, comparing the invoice file in the white list with the input invoice file to be compared; if the comparison is successful, the input invoice file to be compared is authenticated by the access code and the token, and the input invoice file to be compared that passes the verification is determined as the input invoice file to be verified; if the comparison fails, the prompt information is sent; The input invoice file to be verified is verified, and the input invoice file to be verified that succeeds in the verification is determined as the input invoice file, so as to complete the collection of the input invoice file; wherein, the input invoice file to be verified is verified, and the input invoice file to be verified that succeeds in the verification is determined as the input invoice file, including: identifying the invoice number and the invoice code of the input invoice file to be verified, using the invoice number and the invoice code as indexes, comparing the input invoice file to be verified, obtaining a comparison result, and recording the comparison result in a comparison log; and determining the input invoice file to be verified corresponding to the latest comparison result in the comparison log as the input invoice file.

2. The method for collecting input invoice files according to claim 1 is characterized in that: Identify the type of the input invoice data to be processed, and obtain four elements of the input invoice data to be processed based on the type of the input invoice data to be processed, including: If the input invoice data to be processed is a special VAT invoice, the four elements of the input invoice data to be processed include invoice number, invoice code, invoice date, and amount excluding tax; If the input invoice data to be processed is a general VAT invoice, the four elements of the input invoice data to be processed include the invoice number, invoice code, invoice date, and verification code.

3. The method for collecting input invoice files according to claim 1 or 2, characterized in that: After completing the collection of input invoice documents, including: Recording a collection log of the input invoice file, the collection log includes the collection time of the input invoice file, the collection quantity of the input invoice file and the collection failure of the input invoice file; Fault repair is performed based on the collection log.

4. A device for collecting input invoice files for implementing the method for collecting input invoice files as claimed in any one of claims 1 to 3, characterized in that: The input invoice file collection device comprises: The generation module is used to receive the input invoice data callback notification, synchronize the input invoice data to be processed, and generate the input invoice file to be compared; A sending module, used for sending the input invoice file to be compared to the invoice file processing core service; A parsing module, used for parsing the input invoice file to be compared through the invoice file processing core service to obtain the input invoice file to be verified, and storing the input invoice file to be verified in the input invoice data database; The verification module is used to verify the input invoice file to be verified, and determine the input invoice file to be verified that has been successfully verified as the input invoice file to complete the collection of the input invoice file.

5. An electronic device, characterized in that: The electronic device comprises: one or more processors; A storage device for storing one or more programs, which, when executed by the one or more processors, enables the electronic device to implement the input invoice file collection method as described in any one of claims 1 to 3.

6. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and when the computer program is executed by a processor of a computer, the computer is caused to execute the input invoice file collection method as described in any one of claims 1 to 3.

Images