A method and device for batch processing of ticket data, and a medium

Abstract

The application discloses a kind of batch processing method, device and medium of bill data, comprising: obtaining bill data in preset time, preset classification template, bill data is divided into standard bill data and non-standard bill data by classification template, and standard data is batch written into first main table;More than two sub-classification templates and supplementary templates are preset, and non-standard bill data is divided into multiple sub-bill data by sub-classification template and is temporarily stored in sub-table;Bill supplementary information and bill data deletion operation are obtained for the to-be-supplemented information table, the sub-bill data in the temporary sub-table is updated, the sub-bill data in each temporary sub-table after updating is batch written into the first main table and is marked, and the data in the operation table is associated with the corresponding bill data in the first main table.The application can improve the operation efficiency of bill data, and can avoid data misoperation.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of bill management, in particular to a batch processing method and device for bill data and a medium. BACKGROUND

[0002] Non-tax payment refers to the financial funds obtained by various government, state organs, institutions, social groups acting as government functions and other organizations by law using government power, government credibility, national resources, state assets or providing specific public services and quasi-public services. For example, various fines. Non-tax refund refers to the process of refunding the non-tax income paid into the treasury to the original payment unit or payer due to special reasons. In the financial bill management system, non-tax electronic bills involve various types, and bill data may be insufficient or in the wrong format during management. Moreover, the databases involved in the non-tax electronic bill system mainly include Oracle, Mysql, HBase and other data in different formats, so it is difficult to provide a unified management solution. Therefore, the management operation of bill data involves a large amount of data, complicated operation steps and is prone to data errors or loss. SUMMARY

[0003] In view of the above problems, the present application provides a batch processing method for bill data to solve the technical problems of non-uniform management, low efficiency and easy errors of bill data.

[0004] To achieve the above purpose, the inventors provide a batch processing method for bill data, which is applied to bill data processing in a non-tax income management system connected with a financial cross-system through a network; the batch processing method for bill data comprises:

[0005] Obtaining bill data within a preset time from an internal data source and a financial cross-system, wherein the bill data obtained from the financial cross-system includes bank end data, financial collection administrative charge data and financial collection non-tax income refund data;

[0006] A preset classification template is used to divide the bill data into standard bill data and non-standard bill data, and the standard data is batch written into a first master table;

[0007] Two or more sub-classification templates and a supplementary template corresponding to each sub-classification template are preset, the non-standard bill data is divided into a plurality of sub-bill data by the sub-classification templates, and the sub-bill data is respectively stored in the corresponding temporary sub-tables;

[0008] According to each supplementary template, a to-be-supplemented information table of each corresponding temporary sub-table is generated, and the to-be-supplemented information table is sent to a corresponding bill data upload end;

[0009] acquire the bill supplement information and the bill data deletion operation for the to-be-supplemented information table, and verify whether the supplement information and the bill data deletion operation are compliant and complete; if yes, update the sub-bill data in the temporary sub-table using the bill supplement information and the bill data deletion operation, and write the bill supplement information and the bill data deletion operation into an operation table;

[0010] write the sub-bill data in each updated temporary sub-table into the first main table in batches and mark, and associate the data in the operation table with the corresponding bill data in the first main table.

[0011] To solve the above technical problems, the present application further provides another technical solution:

[0012] The acquisition module is configured to acquire bill data within a preset time from an internal data source and a financial cross-system, and the bill data acquired from the financial cross-system includes bank end data, financial collection administrative charge data and financial collection non-tax income withdrawal data.

[0013] The classification module is configured to preset a classification template, classify the bill data into standard bill data and non-standard bill data through the classification template, and write the standard data into the first main table in batches; preset two or more sub-classification templates and a supplement template corresponding to each sub-classification template, classify the non-standard bill data into a plurality of sub-bill data through the sub-classification templates, and store the sub-bill data into corresponding temporary sub-tables respectively.

[0014] The supplement module is configured to generate a to-be-supplemented information table for each corresponding temporary sub-table according to each supplement template, send the to-be-supplemented information table to a corresponding bill data uploading end, acquire bill supplement information and bill data deletion operation for the to-be-supplemented information table, and verify whether the supplement information and the bill data deletion operation are compliant and complete; if yes, update the sub-bill data in the temporary sub-table using the bill supplement information and the bill data deletion operation, and write the bill supplement information and the bill data deletion operation into an operation table.

[0015] The update module is configured to write the sub-bill data in each updated temporary sub-table into the first main table in batches and mark, and associate the data in the operation table with the corresponding bill data in the first main table.

[0016] To solve the above technical problems, the present application further provides another technical solution:

[0017] A computer readable storage medium, having stored thereon a computer program, which, when executed by a processor, implements the batch processing method of bill data according to any one of the preceding technical solutions.

[0018] Different from the prior art, the technical solution classifies the non-standard bill data through the classification template, writes the obtained standard data into the first master table in batches, then classifies the non-standard bill data into multiple sub-bill data through the sub-classification template, updates each sub-bill data according to the supplementary information table supplemented by the supplementary module, finally writes the sub-bill data in each temporary sub-table after update into the first master table in batches and marks, and associates the data in the operation table with the corresponding bill data in the first master table. Therefore, through the technical solution, the bill data of different formats can be applied, the bill data can be uniformly processed in batches, the operation efficiency of the bill data is improved, and the tedious operation on the first master table can be avoided, and the data misoperation can be avoided.

[0019] The above invention content is only a summary of the technical solutions of the present application. In order to enable those skilled in the art to more clearly understand the technical solutions of the present application, and then can be implemented according to the content of the description and the drawings, and in order to make the above and other purposes, characteristics and advantages of the present application more easily understood, the following will be described in combination with the specific embodiments of the present application and the drawings. BRIEF DESCRIPTION OF DRAWINGS

[0020] The accompanying drawings are only used to show the principles, implementation manners, applications, characteristics and effects of the specific embodiments of the present application and other related contents, and cannot be considered as limitations of the present application.

[0021] In the drawings of the specification:

[0022] Figure 1 Flowchart of the batch processing method of bill data described in the specific embodiments;

[0023] Figure 2 Flowchart of the bill data operation step described in the specific embodiments;

[0024] Figure 3 Flowchart of the non-tax revenue deposit application described in the specific embodiments;

[0025] Figure 4 Module block diagram of the batch processing device of bill data described in the specific embodiments;

[0026] Figure 5 Schematic diagram of the computer readable storage medium described in the specific embodiments.

[0027] The reference signs mentioned in the above-mentioned figures are explained as follows:

[0028] 10, acquisition module; 20, classification module; 30, supplement module; 40, update module; 50, operation module; 400, batch processing device of bill data; 500, computer readable storage medium; DETAILED DESCRIPTION

[0029] To explain the possible application scenarios, technical principles, specific schemes that can be implemented, and the purposes and effects that can be achieved of the present application in detail, the following will be described in detail in combination with the specific embodiments listed and with the accompanying drawings. The embodiments described in this paper are only used to more clearly illustrate the technical solutions of the present application, and therefore only serve as examples, and cannot limit the protection scope of the present application.

[0030] In this paper, the term "embodiment" means that the specific features, structures or characteristics described in combination with the embodiment can be included in at least one embodiment of the present application. The term "embodiment" appearing at various places in the specification does not necessarily refer to the same embodiment, and does not particularly limit the independence or association between other embodiments. In principle, in this application, as long as there is no technical contradiction or conflict, the technical features mentioned in each embodiment can be combined in any way to form a corresponding implementable technical solution.

[0031] Unless otherwise defined, the meaning of the technical terms used in this paper is the same as that generally understood by those skilled in the art to which the present application belongs; the use of related terms in this paper is only for the purpose of describing specific embodiments, and is not intended to limit the present application.

[0032] In the description of the present application, the phrase "and / or" is a description of the logical relationship between the objects, which means that there can be three relationships, for example, A and / or B, which means that there are three cases: A exists, B exists, and A and B exist at the same time. In addition, the character " / " in this paper generally represents that the associated objects before and after are a kind of "or" logical relationship.

[0033] In this application, such as "first" and "second", the phrases are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual quantity, primary and secondary or order relationship between the entities or operations.

[0034] In the present application, the terms "comprise", "contain", "include", or other similar expressions used in the description of the application are intended to encompass non-exclusive inclusion, and do not exclude the presence of additional elements, so that the process, method or product comprising a series of elements can not only include those defined elements, but also include other elements not explicitly listed, or also include elements inherent to such process, method or product.

[0035] In the present application, the terms "greater than", "less than", "exceed" and the like are understood as not including the number itself; the terms "above", "below", "within" and the like are understood as including the number itself. In addition, in the description of the embodiments of the present application, the meaning of "multiple" is more than two (including two), and similar expressions related to "multiple" are also understood in this way, for example, "multiple groups", "multiple times" and the like, unless otherwise explicitly specified.

[0036] In the description of the embodiments of the present application, the spatial-related expressions used, such as "center", "longitudinal", "transverse", "length", "width", "thickness", "upper", "lower", "front", "rear", "left", "right", "vertical", "horizontal", "perpendicular", "top", "bottom", "inner", "outer", "clockwise", "counterclockwise", "axial", "radial", "circumferential", and the like, indicate the orientation or positional relationship based on the orientation or positional relationship shown in the specific embodiments or the drawings, and are only for the convenience of describing the specific embodiments of the present application or for the reader to understand, and do not indicate or imply that the indicated device or component must have a specific position, a specific orientation, or be constructed or operated in a specific orientation, and therefore cannot be understood as a limitation on the embodiments of the present application.

[0037] Unless otherwise explicitly specified or limited, in the description of the embodiments of the present application, the terms "mount", "connect", "connect", "fix", "set", and the like should be understood broadly. For example, the "connection" can be a fixed connection, or a detachable connection, or an integral setting; it can be a mechanical connection, or an electrical connection, or a communication connection; it can be directly connected, or indirectly connected through an intermediate medium; it can be the internal communication of two elements or the interaction relationship between two elements. For those skilled in the art to which the present application belongs, the specific meaning of the above terms in the embodiments of the present application can be understood according to the specific circumstances.

[0038] Please refer to Figures 1 to 5The embodiment provides a batch processing method, device and medium for bill data, and the batch processing method for bill data can be applied to bill data processing in a non-tax revenue management system. Since the non-tax revenue involves a large number of aspects and types, the channels and bill types involved are very complicated, and bill data supplement, deletion, change and other transactions can easily occur, and problems such as bill loss and statistical errors can easily occur, thereby affecting the non-tax revenue management efficiency. Through the embodiment, the bill data of different formats can be applied, the bill data can be uniformly processed in batches, the operation efficiency of the bill data is improved, and direct operation on the first master table can be avoided, and data misoperation can be avoided.

[0039] As shown in the drawings, Figure 1 In an embodiment, a batch processing method for bill data is disclosed, which is applied to bill data processing in a non-tax revenue management system, and the non-tax revenue management system is connected with a financial cross-system through a network. The financial cross-system connection, also known as a financial tax bank cross-networking system, is an electronic tax payment system jointly constructed by the People's Bank of China, the Ministry of Finance, the State Administration of Taxation, the People's Bank of China, various commercial banks, Hainan UnionPay and other bank financial institutions. The batch processing method for bill data comprises the following steps:

[0040] S101, obtaining bill data in a preset time from an internal data source and a financial cross-system, and the bill data obtained from the financial cross-system comprises bank end data, financial collection administrative charge data and financial collection non-tax revenue withdrawal data;

[0041] S102, classifying bill data: a preset classification template is used to divide the bill data into standard bill data and non-standard bill data, and the standard data is written into a first master table in batches;

[0042] S103, secondary classification of non-standard bill data: two or more sub-classification templates and a supplement template corresponding to each sub-classification template are preset, the non-standard bill data is divided into a plurality of sub-bill data through the sub-classification templates, and the sub-bill data is respectively stored in a corresponding temporary sub-table;

[0043] S104, generating a to-be-supplemented information table of each corresponding temporary sub-table according to each supplement template, and sending the to-be-supplemented information table to a corresponding bill data uploading end; obtaining bill supplement information and bill data deletion operation for the to-be-supplemented information table, and verifying whether the supplement information and the bill data deletion operation are compliant and complete; if yes, updating the sub-bill data in the temporary sub-table by using the bill supplement information and the bill data deletion operation, and writing the bill supplement information and the bill data deletion operation into an operation table;

[0044] S105. Write the updated sub-ticket data from each temporary sub-table into the first main table in batches according to a preset period and mark it, and associate the data in the operation table with the corresponding ticket data in the first main table.

[0045] The non-tax revenue management system connects to the fiscal cross-linking system via the intranet to obtain invoice data from the fiscal cross-linking system. In steps S102 and S103, the internal structures of each category template and sub-category template are different. The category template sets all the required content for compliant invoice data, such as the collecting department, invoice number, and stamp information. The category template can be used to check whether the invoice data contains all the required content for compliant invoice data. If it does, the corresponding invoice data is batch-written into the first main table. Each sub-category template corresponds to invoices lacking one or more types of content. For example, sub-category template one is used to filter invoice data lacking invoice numbers, and sub-category template two is used to filter invoice data lacking collecting departments.

[0046] In step S104, the supplementary template is set for each sub-category template. The supplementary template can generate a corresponding supplementary information table based on the characteristics of the invoice data in the sub-category template. The supplementary information table lists in detail the invoice content that needs to be supplemented for each invoice data, and classifies and summarizes the invoice content that needs to be supplemented in the supplementary information table according to the data source, and then sends it to the corresponding invoice data upload terminal.

[0047] In step S104, the supplementary information and the deletion operation of the bill data are used to update the sub-bill data in the temporary sub-table, and the supplementary information and the deletion operation of the bill data are written into the operation table. Therefore, by updating the first main table in batches through the temporary sub-table and the operation table, it is not only applicable to bill data of different formats, but also allows for unified batch processing of bill data, improving the efficiency of bill data operation. At the same time, it can avoid cumbersome operations on the first main table directly, thus avoiding data misoperation.

[0048] like Figure 2 As shown, in one embodiment, the batch processing method for invoice data further includes the following steps:

[0049] S201. Receive an operation request for the invoice data in the first master table, the operation request including query, add and modify;

[0050] S202. Determine whether the operation request is the modification and points to the ticket data updated in the first main table in the temporary sub-table;

[0051] S203, if yes, modifying the corresponding data in the operation table through the operation request, and updating the corresponding bill data in the first master table in batches using the modified operation table at a preset period.

[0052] In the embodiment, when the bill information in the first master table needs to be modified, instead of directly modifying in the first master table (which may cause frequent operation of the first master table and easily lead to misoperation or modification of other bill data), the corresponding bill data in the temporary sub-table is found through the operation table, and then the data in the temporary sub-table is modified. After the modification, the operation table is updated, and the modified temporary sub-tables are summarized to modify the corresponding data in the first master table, so that the bill data in the first master table can be modified in batches, and the frequent operation of the first master table and misoperation can be avoided.

[0053] As shown in Figure 3 in an embodiment, the bill data is non-tax revenue bill data;

[0054] The batch processing method of bill data further includes the following steps:

[0055] S301, data writing: writing the corresponding items and amounts of the bill data in the first master table into the second master table, and establishing a comparison table between the first master table and the second master table; the second master table further includes treasury deposit slip number and collection unit;

[0056] S302, pre-application for returning to the bank: the non-tax revenue management system generates a pre-application for returning to the bank according to the first master table and the second master table and sends it to the financial cross-linking system;

[0057] S303, pre-examination for returning to the bank: the financial cross-linking system generates a corresponding remote verification file and a prompt file according to the pre-application for returning to the bank and returns them to the non-tax revenue management system; the verification logic of the remote verification file is controlled by the financial cross-linking system;

[0058] S304, remote verification: the non-tax revenue management system calls the remote verification file to open and verify the first master table and the second master table, modifies the corresponding data according to the prompt file, generates a corresponding modification record file, then encapsulates and encrypts the modification record file and the modified first master table and second master table to obtain an encrypted application file and sends it to the financial cross-linking system;

[0059] S305, verification: the financial cross-linking system decrypts the received encrypted application file, verifies whether the modification information in the modification record file conforms to the prompt file, if yes, the verification is passed, and the encrypted application file is digitally signed and uploaded to the TIPS after the verification is passed;

[0060] S306, treasury: the TIPS conducts compliance inspection on the received signed encrypted application file, and agrees to return the treasury if it passes.

[0061] The remote verification file can be a binary file in *.dll or *.so format, and is generated by the fiscal cross-link system according to the current treasury return pre-application. The fiscal cross-link system can pre-store multiple remote verification file templates, and can select a remote verification file of a corresponding type according to the interface type involved in the current treasury return pre-application and the content in the prompt file. The remote verification file is used to perform offline verification (verification is to ensure that the business data has not been tampered with), read / write and record (i.e. record the entire read / write process) on the business data involved in the non-tax treasury return, including the first master table and the second master table. The remote verification file can call different interfaces and threads in the non-tax revenue management system, and the verification logic of the remote verification file is stored in the fiscal cross-link system and selected or changed by the fiscal cross-link system. In addition, the execution function of the interface can be adjusted or changed at any time according to the needs of the fiscal cross-link system, realizing flexible control. The packaging rule file is used to specify the packaging method of the business data involved in the non-tax treasury return, such as the file naming rule, the file compression method, etc.

[0062] Further, the step of modifying the corresponding data according to the prompt file to generate a corresponding modification record file comprises the steps of:

[0063] The remote verification file starts an information recording thread;

[0064] The non-tax revenue management system obtains the prompt information in the prompt file one by one, and locates the specific position of the first master table and / or the second master table according to the position information in the prompt information, and calls the business data associated with the specific position;

[0065] According to the prompt content in the prompt information, the business data associated with the specific position is checked and corrected;

[0066] The information recording thread records the correction process in real time, and the correction process is summarized to obtain the modification record file.

[0067] The interface name involved in the remote verification file has been pre-agreed and stored in the non-tax revenue management system, and the verification logic of the remote verification file is stored in the fiscal cross-link system and selected or changed by the fiscal cross-link system.

[0068] In the embodiment, the non-tax revenue management system can modify, correct, verify and package the business data according to the problems indicated in the prompt file according to the above-mentioned file, and the above-mentioned operations on the business data are implemented through the remote verification file returned by the financial cross-link system. The calling, reading, writing, correction and other behaviors of the business data are implemented under the monitoring of the remote verification file provided by the financial cross-link system, rather than being implemented independently on the non-tax revenue management system side. That is, the operation of the non-tax revenue management system on the business data is controlled. The financial cross-link system can adjust the verification implementation logic of the remote verification file at any time as needed, and the non-tax revenue management system side can not need to make any changes. Therefore, the financial cross-link system does not need to verify the modified business data in whole, but only needs to judge whether the problems in the prompt file have been completely processed according to the modification record file, thereby greatly reducing the error rate of the business data and the verification workload, and effectively shortening the non-tax revenue withdrawal period.

[0069] As shown in Figure 4 In an embodiment, a batch processing device 400 of bill data is provided, which is applied to bill data processing in a non-tax revenue management system. The batch processing device 400 of bill data comprises:

[0070] An acquisition module 10 is configured to acquire bill data within a preset time from an internal data source and a financial cross-link system, wherein the bill data acquired from the financial cross-link system comprises bank end data, financial collection administrative charge data and financial collection non-tax revenue withdrawal data;

[0071] A classification module 20 is configured to preset a classification template, divide the bill data into standard bill data and non-standard bill data through the classification template, and batch write the standard data into a first master table; preset two or more sub-classification templates and a supplementary template corresponding to each sub-classification template, divide the non-standard bill data into a plurality of sub-bill data through the sub-classification templates, and store the sub-bill data in corresponding temporary sub-tables respectively;

[0072] A supplementary module 30 is configured to generate a to-be-supplemented information table of each corresponding temporary sub-table according to each supplementary template, send the to-be-supplemented information table to a corresponding bill data uploading end, acquire bill supplement information and bill data deletion operation for the to-be-supplemented information table, and verify whether the supplement information and the bill data deletion operation are compliant and complete; if yes, update the sub-bill data in the temporary sub-table by using the bill supplement information and the bill data deletion operation, and write the bill supplement information and the bill data deletion operation into an operation table;

[0073] The update module 40 is used to write the updated sub-ticket data from each temporary sub-table into the first main table in batches according to a preset period and mark it, and to associate the data in the operation table with the corresponding ticket data in the first main table.

[0074] In one embodiment, the batch processing device 400 for invoice data further includes an operation module 50, configured to receive operation requests for invoice data in the first master table, the operation requests including querying, adding, and modifying; determine whether the operation request is the modification and points to the invoice data updated in the first master table from the temporary sub-table; if so, modify the corresponding data in the operation table through the operation request, and batch update the corresponding invoice data in the first master table using the modified operation table at a preset period.

[0075] In one embodiment, a non-tax refund module is also included, which is used to apply for non-tax revenue refund based on the first master table and the second master table.

[0076] like Figure 5 As shown, in one embodiment, a computer-readable storage medium 500 is provided, on which a computer program is stored, which, when executed by a processor, implements the batch processing method for invoice data as described in any of the above embodiments.

[0077] Finally, it should be noted that although the above embodiments have been described in the text and drawings of this application, this should not limit the scope of patent protection of this application. Any technical solutions that are based on the essential concept of this application and utilize the content described in the text and drawings of this application, resulting in equivalent structural or procedural substitutions or modifications, as well as the direct or indirect application of the technical solutions of the above embodiments to other related technical fields, are all included within the scope of patent protection of this application.

Claims

1. A method of batch processing of ticket data, characterized by, The application is applied to bill data processing in a non-tax revenue management system connected with a financial cross-linking system through a network. The batch processing method of bill data comprises the following steps: Obtaining bill data within a preset time from an internal data source and the financial cross-linking system, wherein the bill data obtained from the financial cross-linking system comprises bank end data, financial collection administrative charge data and financial collection non-tax revenue withdrawal data; Predefining a classification template, dividing the bill data into standard bill data and non-standard bill data through the classification template, and batch writing the standard bill data into a first master table; Predefining two or more sub-classification templates and a supplementary template corresponding to each sub-classification template, dividing the non-standard bill data into a plurality of sub-bill data through the sub-classification templates, and storing the sub-bill data in corresponding temporary sub-tables respectively; Generating a to-be-supplemented information table of each corresponding temporary sub-table according to each supplementary template, and sending the to-be-supplemented information table to a corresponding bill data uploading end; Obtaining bill supplement information and bill data deletion operation for the to-be-supplemented information table, and verifying whether the supplement information and bill data deletion operation are compliant and complete; if yes, updating the sub-bill data in the temporary sub-tables by using the bill supplement information and the bill data deletion operation, and writing the bill supplement information and the bill data deletion operation into an operation table; Batch writing the sub-bill data in the updated temporary sub-tables into the first master table and marking, and associating the data in the operation table with corresponding bill data in the first master table.

2. The method of claim 1, wherein, Further comprising the following steps: Receiving an operation request for bill data in the first master table, wherein the operation request comprises query, addition and modification; Judging whether the operation request is the modification and points to bill data in the temporary sub-tables updated into the first master table; If yes, modifying corresponding data in the operation table through the operation request, and batch updating corresponding bill data in the first master table by using the modified operation table at a preset period.

3. The method of claim 2, wherein, The bill data is non-tax revenue bill data; Further comprising the following steps: writing corresponding items and amounts of the bill data in the first master table into a second master table, and establishing a comparison table between the first master table and the second master table; The non-tax revenue management system generates a withdrawal pre-application file according to the first master table and the second master table and sends it to the financial cross-linking system; The financial cross-linking system generates a corresponding remote verification file and a prompt file according to the withdrawal pre-application file and returns them to the non-tax revenue management system; the verification logic of the remote verification file is controlled by the financial cross-linking system; The non-tax revenue management system calls the remote verification file to open and verify the first master table and the second master table, modifies corresponding data according to the prompt file, generates a corresponding modification record file, then encapsulates and encrypts the modification record file and the modified first master table and the second master table to obtain an encrypted application file and sends it to the financial cross-linking system; The application further comprises the following steps: Receiving the encrypted application file from the non-tax revenue management system, and verifying the encrypted application file by using the remote verification file; If the verification is successful, returning a corresponding modification record file to the non-tax revenue management system, wherein the modification record file comprises a corresponding modification record of the first master table and the second master table; The non-tax revenue management system modifies corresponding data in the first master table and the second master table according to the modification record file, and generates a corresponding modification record file, then encapsulates and encrypts the modification record file and the modified first master table and the second master table to obtain an encrypted application file and sends it to the financial cross-linking system. The financial cross-linking system decrypts the received encrypted application file, verifies whether the modification information in the modification record file conforms to the prompt file, and if so, the modification record file is verified and passed, and the encrypted application file is digitally signed and uploaded to the TIPS; The TIPS performs compliance inspection on the received signed encrypted application file, and if passed, agrees to return the deposit.

4. The method of claim 3, wherein, The modification record file is generated by modifying the corresponding data according to the prompt file, including the following steps: The remote verification file starts an information recording thread; The non-tax revenue management system obtains the prompt information in the prompt file one by one, and locates the specific position of the first main table and / or the second main table according to the position information in the prompt information, and calls the business data associated with the specific position; According to the prompt content in the prompt information, the business data associated with the specific position is checked and corrected; The information recording thread records the correction process in real time, and the correction process is summarized to obtain the modification record file.

5. The method of claim 3, wherein, The interface name involved in the remote verification file is pre-agreed and stored in the non-tax revenue management system, and the verification logic of the remote verification file is stored in the financial cross-linking system and selected or changed by the financial cross-linking system.

6. The method for processing a batch of document data according to claim 3, wherein, The second main table further includes treasury deposit receipt number and collection unit.

7. A batch processing apparatus of ticket data, characterized by comprising: The bill data processing applied to the non-tax revenue management system includes: The acquisition module is used to acquire bill data within a preset time from an internal data source and a financial cross-linking system, and the bill data acquired from the financial cross-linking system includes bank end data, financial collection administrative charge data and financial collection non-tax revenue deposit return data; The classification module is used to preset a classification template, classify the bill data into standard bill data and non-standard bill data through the classification template, and batch write the standard bill data into a first main table; two or more sub-classification templates and a supplementary template corresponding to each sub-classification template are preset, the non-standard bill data is divided into a plurality of sub-bill data through the sub-classification template, and the sub-bill data is respectively stored in a corresponding temporary sub-table; The supplementary module is used to generate a to-be-supplemented information table of each corresponding temporary sub-table according to each supplementary template, and send the to-be-supplemented information table to a corresponding bill data upload end; acquire bill supplement information and bill data deletion operation for the to-be-supplemented information table, and verify whether the supplement information and bill data deletion operation are compliant and complete; if so, update the sub-bill data in the temporary sub-table with the bill supplement information and the bill data deletion operation, and write the bill supplement information and the bill data deletion operation into an operation table; The update module is used to batch write the sub-bill data in each updated temporary sub-table into the first main table and mark, and associate the data in the operation table with the corresponding bill data in the first main table.

8. A bulk processing apparatus for sheet data according to claim 7, wherein Further comprising an operation module for receiving an operation request for the bill data in the first main table, the operation request including query, addition and modification; determining whether the operation request is the modification and points to the bill data in the first master table updated from the staging sub-table; if yes, modifying the corresponding data in the operation table through the operation request, and updating the corresponding bill data in the first master table in batches using the modified operation table at a preset period.

9. A bulk processing apparatus for sheet data according to claim 8, wherein, The application also comprises a non-tax refund module for applying for non-tax income refund according to the first master table and the second master table.

10. A computer-readable storage medium having stored thereon a computer program, characterized in that, The program is executed by the processor to realize the batch processing method of bill data as claimed in any one of claims 1 to 6.

Images