A method, device and medium for processing business data

Abstract

The present invention discloses a method, device and medium for processing business data, including storing statistical non-tax revenue business data into a first main table and a second main table, generating a pre-application document for refund based on the first sub-table and the second sub-table and sending it to the fiscal cross-link system; the fiscal cross-link system generates and returns corresponding remote verification files, prompt files, etc. to the non-tax revenue management system; the fiscal cross-link system controls the correction of non-tax revenue business data through the remote verification files and generates corresponding modification record files; the fiscal cross-link system verifies whether the modification information in the modification record file complies with the prompt file, and if so, the verification passes, and TIPS performs compliance testing before refunding. The present invention can reduce the error rate and verification workload of business data, and can effectively shorten the refund cycle of non-tax revenue.

Description

Technical Field

[0001] The present application relates to the field of computer network technology, and in particular to a method, device, and medium for processing business data. Background Art

[0002] Non-tax payments refer to the payment of fiscal funds other than taxes, which are obtained by governments at all levels, state organs, public institutions, social groups that perform government functions, and other organizations through the legal use of government power, government credibility, national resources, state-owned assets, or the provision of specific public services or quasi-public services. For example, various types of fines. Non-tax refunds refer to the process in which non-tax revenues that have been paid into the national treasury are refunded to the original payer or payee upon approval for special reasons. In the existing technology, non-tax refunds are mainly made by local units applying for refunds, which then go through various approval processes such as digital signatures and verification, and the number and types of bills involved are numerous. Therefore, the refund period for non-tax revenues is long, and it is easy for some details to cause the period to be extended or the refund to fail. Summary of the Invention

[0003] In view of the above problems, the present application provides a method for processing business data to solve the technical problems of the long non-tax refund cycle and the large amount of data involved and the proneness to errors.

[0004] To achieve the above-mentioned objectives, the inventors provide a business data processing method for processing non-tax business data in a non-tax revenue management system, wherein the non-tax revenue management system is connected to a fiscal cross-link system via a network, and the fiscal cross-link system is connected to TIPS via a network. The business data processing method comprises: the non-tax revenue management system collects information on bills of non-tax revenue involved in a current non-tax refund and collects statistics on items and amounts of non-tax revenue; synchronously writes the bill information to a first main table and a first sub-table, and synchronously writes the items and amounts to a second main table and a second sub-table, and establishes a comparison table between the first main table and the second main table;

[0005] The non-tax revenue management system generates a refund pre-application document based on the first sub-table and the second sub-table and sends it to the financial horizontal connection system;

[0006] The fiscal cross-link system generates and returns to the non-tax revenue management system a corresponding remote verification file, encapsulation rule file, key, and prompt file based on the pre-refund application file; the verification logic of the remote verification file is controlled by the fiscal cross-link system;

[0007] The non-tax revenue management system calls the remote verification file to open and verify the first master table and the second master table, and identifies corresponding information in the first master table and the second master table through the prompt file and the comparison table; the non-tax revenue management system receives modifications to the first master table and / or the second master table, generates a modification record file based on the modifications, and encapsulates the modified first master table and / or the second master table and the modification record file using the encapsulation rule file to obtain an encapsulated file, and then encrypts the encapsulated file using the key to obtain an encrypted application file and upload it to the fiscal cross-link system;

[0008] The financial cross-link system decrypts the received encrypted application document and verifies whether the modification information in the modification record file conforms to the prompt file. If so, the encrypted application document is digitally signed and uploaded to the TIPS.

[0009] The TIPS performs a compliance check on the signed encrypted application document received, and approves the return if it passes.

[0010] In some technical solutions, the modification record file is encrypted using the key to obtain an encrypted ciphertext;

[0011] The verifying whether the modification information in the modification record file complies with the prompt file includes:

[0012] Decrypting the encrypted ciphertext, extracting modification information from the modification record file obtained by decryption, and adding the modification information to the first verification queue;

[0013] The modified information in the first verification queue is extracted one by one and compared with the prompt file to determine whether there is a difference between the first verification queue and the prompt file. If not, the verification is passed.

[0014] Furthermore, the non-tax revenue management system receives a modification to the first master table and / or the second master table, and generates a modification record file according to the modification, including:

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

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

[0017] Checking and correcting the business data associated with the specific location according to the prompt content in the prompt information;

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

[0019] Furthermore, the scanned image corresponding to the bill information is embedded into the first main table as an attachment; the comparison table includes the comparison relationship between the bill information and the scanned image as well as the items and amounts.

[0020] Furthermore, the second main table also includes the treasury payment certificate number and the collection unit.

[0021] Furthermore, the interface names involved in the remote verification file have 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.

[0022] To solve the above technical problems, this application also provides another technical solution:

[0023] A business data processing device is used for processing non-tax business data; the business data processing device comprises:

[0024] The non-tax revenue management system is configured to collect information on bills, items, and amounts of non-tax revenue involved in the non-tax refund; synchronously write the bill information to a first main table and a first sub-table, and synchronously write the items and amounts to a second main table and a second sub-table, and establish a comparison table between the first main table and the second main table; and generate a refund pre-application document based on the first sub-table and the second sub-table and send it to the fiscal cross-link system.

[0025] The financial cross-link system is used to generate and return to the non-tax revenue management system a corresponding remote verification file, encapsulation rule file, key, and prompt file based on the pre-refund application document; the verification logic of the remote verification file is controlled by the financial cross-link system;

[0026] The non-tax revenue management system is further configured to call the remote verification file to open and verify the first master table and the second master table, and identify corresponding information in the first master table and the second master table using the prompt file and the comparison table; the non-tax revenue management system receives modifications to the first master table and / or the second master table, generates a modification record file based on the modifications, and encapsulates the modified first master table and / or the second master table and the modification record file using the encapsulation rule file to obtain an encapsulated file, and then encrypts the encapsulated file using the key to obtain an encrypted application file and upload it to the fiscal cross-link system;

[0027] The financial cross-link system is further configured to decrypt the received encrypted application document and verify whether the modification information in the modification record file conforms to the prompt file. If so, the encrypted application document is digitally signed and uploaded to the TIPS after passing the verification.

[0028] The TIPS is used to perform a compliance check on the signed encrypted application document received, and if it passes, the document is approved for return to the warehouse.

[0029] Furthermore, the scanned image corresponding to the bill information is embedded in the first main table as an attachment; the comparison table includes the comparison relationship between the bill information and the scanned image as well as the items and amounts; the second main table also includes the treasury payment book number and the collecting unit.

[0030] Furthermore, the interface names involved in the remote verification file have 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.

[0031] To solve the above technical problems, this application also provides another technical solution:

[0032] A computer-readable storage medium stores a computer program, which, when executed by a processor, implements the method for processing business data described in any of the above technical solutions.

[0033] Different from the existing technology, the non-tax revenue management system in the above technical solution divides the non-tax business data into a first main table and a second main table for storage, and establishes a comparison table between the two, thereby facilitating subsequent modification and correction of business data; and the financial cross-link system generates and returns a remote verification file, an encapsulation rule file, a key and a prompt file based on the pre-refund application file submitted by the non-tax revenue management system. The non-tax revenue management system can modify, correct, verify and encapsulate the business data based on the problems pointed out in the prompt file according to the above files, and the above operations on the business data are all realized through the remote verification file returned by the financial cross-link system. Therefore, the financial cross-link system does not need to conduct a comprehensive verification of the modified business data, but only needs to judge whether the problems raised in the prompt file have been fully processed based on the modification record file, thereby greatly reducing the error rate and verification workload of the business data, and can effectively shorten the refund cycle of non-tax revenue.

[0034] The above-mentioned records related to the content of the invention are only an overview of the technical solution of this application. In order to enable ordinary technicians in this field to understand the technical solution of this application more clearly, and then implement it according to the text of the specification and the contents recorded in the drawings, and to make the above-mentioned purposes and other purposes, features and advantages of this application easier to understand, the following is an explanation in combination with the specific implementation methods and drawings of this application. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] The drawings are only used to illustrate the principles, implementation methods, applications, features and effects of the specific embodiments of the present invention and other related contents, and are not to be considered as limiting the present application.

[0036] In the drawings of the specification:

[0037] Figure 1 This is a business flow chart for the electronic refund of non-tax revenue described in the specific implementation method;

[0038] Figure 2 A flowchart of a method for processing business data according to a specific embodiment;

[0039] Figure 3 It is a flowchart of verifying the modification record file according to the specific implementation method;

[0040] Figure 4 A schematic diagram of a device for processing business data according to a specific embodiment;

[0041] Figure 5 A schematic diagram of a computer-readable storage medium according to a specific embodiment;

[0042] The reference numerals in the above drawings are described as follows:

[0043] 10. Non-tax revenue management system;

[0044] 20. Financial horizontal linkage system;

[0045] 30. TIPS;

[0046] 400. Business data processing device;

[0047] 500. Computer-readable storage medium; DETAILED DESCRIPTION

[0048] In order to explain in detail the possible application scenarios, technical principles, specific solutions that can be implemented, and the purpose and effects of this application, the following is a detailed description of the specific embodiments listed in conjunction with the accompanying drawings. The embodiments described herein are only used to more clearly illustrate the technical solutions of this application and are therefore only examples and are not intended to limit the scope of protection of this application.

[0049] References to "embodiments" herein mean that the specific features, structures, or characteristics described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the word "embodiment" in various places in the specification does not necessarily refer to the same embodiment, nor does it particularly limit its independence or relevance to other embodiments. In principle, in this application, as long as there are no technical contradictions or conflicts, the various technical features mentioned in the embodiments can be combined in any manner to form a corresponding implementable technical solution.

[0050] Unless otherwise defined, the technical terms used herein have the same meanings as those generally understood by those skilled in the art to which this application belongs; the use of relevant terms herein is only for describing specific embodiments and is not intended to limit this application.

[0051] In the description of this application, the term "and / or" is used to describe a logical relationship between objects, indicating that three relationships can exist. For example, A and / or B means: A exists, B exists, and both A and B exist. In addition, the character " / " in this document generally indicates that the objects before and after are in a logical "or" relationship.

[0052] In this application, terms such as "first" and "second" are merely used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual quantity, priority or sequence relationship between these entities or operations.

[0053] Without further limitations, in this application, the words "include", "comprise", "have" or other similar open-ended expressions used in sentences are intended to cover non-exclusive inclusion. These expressions do not exclude the presence of additional elements in the process, method or product that includes the elements, so that the process, method or product that includes a series of elements may include not only those defined elements, but also other elements that are not explicitly listed, or also include elements inherent to such process, method or product.

[0054] Consistent with the understanding in the Examination Guidelines, in this application, expressions such as "greater than," "less than," and "exceed" are understood to exclude the number itself; expressions such as "above," "below," and "within" are understood to include the number itself. Furthermore, in the description of the embodiments of this application, "multiple" means more than two (including two), and similar expressions related to "multiple" are also understood in this manner, such as "multiple groups," "multiple times," etc., unless otherwise specifically defined.

[0055] In the description of the embodiments of the present application, the space-related expressions used, such as "center", "longitudinal", "lateral", "length", "width", "thickness", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "vertical", "top", "bottom", "inside", "outside", "clockwise", "counterclockwise", "axial", "radial", "circumferential", etc., indicate the orientation or position relationship based on the orientation or position relationship shown in the specific embodiments or drawings, and are only for the convenience of describing the specific embodiments of the present application or facilitating the reader's understanding, and do not indicate or imply that the device or component referred to must have a specific position, a specific orientation, or be constructed or operated in a specific orientation. Therefore, it should not be understood as a limitation on the embodiments of the present application.

[0056] Unless otherwise expressly specified or limited, in the description of the embodiments of the present application, the terms "installed", "connected", "connected", "fixed", "set", etc. used should be understood in a broad sense. For example, the "connection" can be a fixed connection, a detachable connection, or an integrated setting; it can be a mechanical connection, an electrical connection, or a communication connection; it can be a direct connection or an indirect connection through an intermediate medium; it can be the internal connection of two elements or the interaction relationship between two elements. For those skilled in the art of the present application, the specific meanings of the above terms in the embodiments of the present application can be understood according to the specific circumstances.

[0057] See also Figures 1 to 2 This embodiment provides a method for processing business data. This method can be used for processing non-tax business data in a non-tax revenue management system and for non-tax revenue refund applications. This embodiment facilitates the management of non-tax revenue business data, reduces business data errors during refund applications, and shortens the non-tax refund cycle.

[0058] like Figure 1 The figure below shows a business process diagram for the electronic refund of non-tax revenue in one embodiment, involving the non-tax revenue management system, the fiscal horizontal connection system, and TIPS. The non-tax revenue management system is connected to the fiscal horizontal connection system via a network, and the fiscal horizontal connection system is connected to TIPS via a network. The fiscal horizontal connection system, also known as the fiscal-tax-treasury-bank horizontal networking system, is an electronic tax payment system jointly built by the People's Bank of China, the Ministry of Finance, the State Administration of Taxation, the People's Bank of China Treasury, various commercial banks, Hainan UnionPay, and other banking and financial institutions. The TIPS (National Treasury Information Processing System) is the treasury information processing system.

[0059] like Figure 2 As shown, the method for processing the business data includes:

[0060] Business data statistics: The non-tax revenue management system counts the bill information, items and amounts of the non-tax revenue involved in this non-tax refund; the bill information is synchronously written into the first main table and the first sub-table, and the items and amounts are synchronously written into the second main table and the second sub-table, and a comparison table is established between the first main table and the second main table. The comparison table associates the bill information in the first main table with the items in the second main table. The bill information and item names corresponding to the same business data can be found through the comparison table. Among them, the scanned image corresponding to the bill information is embedded in the first main table as an attachment; the comparison table includes the comparison relationship between the bill information and the scanned image as well as the items and amounts. The second main table also includes the treasury payment book number and the collection unit.

[0061] Pre-tax Refund Application: The non-tax revenue management system generates a pre-tax refund application document based on the first and second sub-tables and sends it to the fiscal cross-link system. The first sub-table can contain the same content as the first main table, and the second sub-table can contain the same content as the second main table. Alternatively, the first sub-table can be a simplified version of the first main table, obtained by deleting and compressing some information from the first main table.

[0062] Refund Pre-approval: The fiscal cross-link system generates and returns the corresponding remote verification file, encapsulation rule file, key, and prompt file to the non-tax revenue management system based on the refund pre-application document. The verification logic of the remote verification file is controlled by the fiscal cross-link system. The remote verification file can be a binary file in the *.dll or *.so format. The remote verification file is generated by the fiscal cross-link system based on the refund pre-application. The fiscal cross-link system may pre-store multiple remote verification file templates. The fiscal cross-link system can select the corresponding remote verification file type based on the interface type involved in the refund pre-application and the content in the prompt file.

[0063] Remote Verification: The non-tax revenue management system calls the remote verification file to open and verify the first and second master tables, and identifies the corresponding information in the first and second master tables using the prompt file and the comparison table. The non-tax revenue management system receives modifications to the first and / or second master tables, generates a modification record file based on the modifications, and encapsulates the modified first and / or second master tables and the modification record file using the encapsulation rule file to generate an encapsulated file. The encapsulated file is then encrypted using the key to generate an encrypted application file and upload it to the fiscal cross-link system. The remote verification file is used to perform offline verification (to ensure that the business data has not been tampered with), read and write, and record (i.e., record the entire reading and writing process) of the business data involved in non-tax refunds, including the first and second master tables. The remote verification file can call different interfaces and threads within the non-tax revenue management system, and the verification logic of the remote verification file is stored in the fiscal cross-link system and can be selected or modified by the fiscal cross-link system. Furthermore, the execution function of the interface can be adjusted or modified at any time as needed by the fiscal cross-link system, enabling flexible control. The encapsulation rule file is used to specify the encapsulation method of the business data involved in non-tax refunds, such as the first main table and the second main table, such as file naming rules, file compression methods, etc.

[0064] Verification: The financial cross-link system decrypts the received encrypted application document and verifies whether the modification information in the modification record file is consistent with the prompt file. If so, the verification is passed and the encrypted application document is digitally signed and uploaded to the TIPS.

[0065] Withdrawal: The TIPS performs a compliance check on the signed encrypted application documents received, and approves withdrawal if they pass.

[0066] In this embodiment, the non-tax revenue management system can modify, correct, verify, and encapsulate the business data based on the issues pointed out in the prompt file based on the above-mentioned file. Furthermore, all of the above-mentioned operations on the business data are implemented through the remote verification file returned by the fiscal cross-link system. The calling, reading, writing, and correction of business data are all implemented under the monitoring of the remote verification file provided by the fiscal cross-link system, while the non-tax revenue management system implements them independently. In other words, the non-tax revenue management system's operations on business data are controlled, and the fiscal cross-link system can adjust the verification implementation logic of the remote verification file at any time as needed, while the non-tax revenue management system does not need to make any changes. Therefore, the fiscal cross-link system does not need to fully verify the modified business data. It only needs to determine whether all the issues raised in the prompt file have been addressed based on the modification record file, thereby greatly reducing the error rate and verification workload of the business data and effectively shortening the return cycle of non-tax revenue.

[0067] like Figure 3 As shown, in one embodiment, the modification record file is encrypted by the key to obtain an encrypted ciphertext; and verifying whether the modification information in the modification record file conforms to the prompt file includes:

[0068] Decrypt the encrypted ciphertext and extract the modification information in the modification record file obtained by decryption; and add the modification information to the first verification queue.

[0069] The modified information in the first verification queue is extracted one by one and compared with the prompt file to determine whether there is a difference between the first verification queue and the prompt file. If not, the verification is passed.

[0070] In this embodiment, the questions raised in the prompt file can be verified one by one through the first verification queue, thereby ensuring the comprehensiveness of the verification of the modification record file.

[0071] In one embodiment, the non-tax revenue management system receives a modification to the first master table and / or the second master table, and generates a modification record file based on the modification, including:

[0072] The remote verification file starts an information recording thread; the information recording thread can record the reading and writing (ie, correction) records of the specified object and generate a corresponding record file.

[0073] The non-tax revenue management system retrieves each prompt message from the prompt file, locates the specific location of the first master table and / or the second master table based on the location information in the prompt message, and retrieves the business data associated with the specific location. Each row in the first and second master tables contains one piece of data, so the corresponding specific data can be located based on the row number in the table. Once the business data in the first master table is located, the associated business data in the second master table can be located based on the comparison table.

[0074] The business data associated with the specific location is checked and corrected according to the prompt content in the prompt information; the correction process is recorded in real time through the information recording thread, and the correction process is summarized to obtain the modification record file.

[0075] like Figure 4 As shown, in one embodiment, a business data processing device 400 is provided, which is used for processing non-tax business data; the business data processing device includes:

[0076] The non-tax revenue management system 10 is configured to compile statistics on the bill information, items, and amounts of non-tax revenue involved in this non-tax refund; synchronously write the bill information to a first master table and a first sub-table, and synchronously write the items and amounts to a second master table and a second sub-table; establish a comparison table between the first master table and the second master table; and generate a pre-refund application document based on the first and second sub-tables and transmit it to the fiscal cross-link system. The comparison table associates the bill information in the first master table with the items in the second master table, allowing the bill information and item names corresponding to the same business data to be found through the comparison table. A scanned image corresponding to the bill information is embedded as an attachment in the first master table; the comparison table includes a comparison between the bill information, the scanned image, and the items and amounts; the second master table also includes the treasury payment certificate number and the collection unit.

[0077] The fiscal cross-link system 20 is used to generate and return the corresponding remote verification file, encapsulation rule file, key and prompt file to the non-tax revenue management system based on the refund pre-application file; the verification logic of the remote verification file is controlled by the fiscal cross-link system.

[0078] The non-tax revenue management system 10 is further configured to call the remote verification file to open and verify the first and second master tables, and to identify corresponding information in the first and second master tables using the prompt file and the comparison table. The non-tax revenue management system receives modifications to the first and / or second master tables, generates a modification record file based on the modifications, and encapsulates the modified first and / or second master tables and the modification record file using the encapsulation rule file to obtain an encapsulated file, which is then encrypted using the key to obtain an encrypted application file and upload it to the fiscal cross-link system. The remote verification file can be a binary file in the form of *.dll or *.so. The remote verification file is generated by the fiscal cross-link system based on the pre-application for the destocking. The fiscal cross-link system may pre-store multiple remote verification file templates. The fiscal cross-link system may select the corresponding type of remote verification file based on the type of interface involved in the pre-application for the destocking and the content in the prompt file.

[0079] The remote verification file is used to perform offline verification (verification is to ensure that the business data has not been tampered with), reading, writing, and recording (i.e., recording the entire reading and writing process) of the business data involved in non-tax refunds, 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 financial cross-link system and selected or changed by the financial cross-link system. In addition, the execution function of the interface can be adjusted or changed at any time as needed on the financial cross-link system side to achieve flexible control. The encapsulation rule file is used to specify the encapsulation method of the business data involved in non-tax refunds, such as the first master table and the second master table, such as file naming rules, file compression methods, etc.

[0080] The financial cross-link system is further configured to decrypt the received encrypted application document and verify whether the modification information in the modification record file conforms to the prompt file. If so, the encrypted application document is digitally signed and uploaded to the TIPS after passing the verification.

[0081] The TIPS30 is used to perform a compliance check on the signed encrypted application document received, and if it passes, the document is approved for return to the warehouse.

[0082] The interface names involved in the remote verification file have been pre-agreed and stored in the non-tax revenue management system. 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.

[0083] In this embodiment, the non-tax revenue management system can modify, correct, verify, and encapsulate the business data based on the issues pointed out in the prompt file based on the above-mentioned file. Furthermore, all of the above-mentioned operations on the business data are implemented through the remote verification file returned by the fiscal cross-link system. The calling, reading, writing, and correction of business data are all implemented under the monitoring of the remote verification file provided by the fiscal cross-link system, while the non-tax revenue management system implements them independently. In other words, the non-tax revenue management system's operations on business data are controlled, and the fiscal cross-link system can adjust the verification implementation logic of the remote verification file at any time as needed, while the non-tax revenue management system does not need to make any changes. Therefore, the fiscal cross-link system does not need to fully verify the modified business data. It only needs to determine whether all the issues raised in the prompt file have been addressed based on the modification record file, thereby greatly reducing the error rate and verification workload of the business data and effectively shortening the return cycle of non-tax revenue.

[0084] like Figure 5 As shown, in one embodiment, a computer-readable storage medium 500 is provided, on which a computer program is stored. When the program is executed by a processor, the method for processing business data as described in the above embodiments is implemented.

[0085] Finally, it should be noted that although the above embodiments have been described in the specification and drawings of this application, this does not limit the scope of patent protection of this application. All technical solutions generated by replacing or modifying equivalent structures or equivalent processes based on the essential concepts of this application using the contents recorded in the specification and drawings of this application, as well as directly or indirectly implementing the technical solutions of the above embodiments in other related technical fields, are included in the scope of patent protection of this application.

Claims

1. A method for processing business data, characterized in that: The method is applied to the processing of non-tax business data in a non-tax revenue management system, wherein the non-tax revenue management system is connected to a fiscal cross-link system via a network, and the fiscal cross-link system is connected to TIPS via a network. The method for processing the business data includes: The non-tax revenue management system collects the bill information, items, and amounts of the non-tax revenue involved in the non-tax refund; synchronously writes the bill information to the first main table and the first sub-table, and synchronously writes the items and amounts to the second main table and the second sub-table, and establishes a comparison table between the first main table and the second main table; The non-tax revenue management system generates a refund pre-application document based on the first sub-table and the second sub-table and sends it to the financial horizontal connection system; The fiscal cross-link system generates and returns to the non-tax revenue management system a corresponding remote verification file, encapsulation rule file, key, and prompt file based on the pre-refund application file; the verification logic of the remote verification file is controlled by the fiscal cross-link 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, and identifies corresponding information in the first master table and the second master table through the prompt file and the comparison table; the non-tax revenue management system receives modifications to the first master table and / or the second master table, generates a modification record file based on the modifications, and encapsulates the modified first master table and / or the second master table and the modification record file using the encapsulation rule file to obtain an encapsulated file, and then encrypts the encapsulated file using the key to obtain an encrypted application file and upload it to the fiscal cross-link system; The financial cross-link system decrypts the received encrypted application document and verifies whether the modification information in the modification record file conforms to the prompt file. If so, the encrypted application document is digitally signed and uploaded to the TIPS. The TIPS performs a compliance check on the signed encrypted application document received and approves the return if it passes. The interface names involved in the remote verification file have been pre-agreed and stored in the non-tax revenue management system. 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. All operations on business data are realized through the remote verification files returned by the financial cross-link system. The calling, reading, writing and correction of business data are all realized under the monitoring of the remote verification files provided by the financial cross-link system. The non-tax revenue management system receives the modification to the first master table and / or the second master table, and generates a modification record file according to the modification, including: The remote verification file starts an information recording thread; The non-tax revenue management system obtains prompt information in the prompt file one by one, locates the specific location of the first master table and / or the second master table according to the location information in the prompt information, and retrieves the business data associated with the specific location; Checking and correcting the business data associated with the specific location according to the prompt content in the prompt information; The correction process is recorded in real time through the information recording thread, and the correction process is summarized to obtain the modification record file.

2. The method for processing business data according to claim 1, characterized in that: The encrypted ciphertext obtained by encrypting the modification record file with the key; The verifying whether the modification information in the modification record file complies with the prompt file includes: Decrypting the encrypted ciphertext, extracting modification information from the modification record file obtained by decryption, and adding the modification information to the first verification queue; The modified information in the first verification queue is extracted one by one and compared with the prompt file to determine whether there is a difference between the first verification queue and the prompt file. If not, the verification is passed.

3. The method for processing business data according to claim 1, characterized in that: The scanned image corresponding to the bill information is embedded into the first main table as an attachment; the comparison table includes the comparison relationship between the bill information and the scanned image as well as the items and amounts.

4. The method for processing business data according to claim 1, wherein: The second main table also includes the treasury payment certificate number and the collection unit.

5. A business data processing device, characterized in that: Used for non-tax business data processing; The service data processing device includes: The non-tax revenue management system is used to collect information on bills, items, and amounts of non-tax revenue involved in the non-tax refund; synchronously write the bill information to the first main table and the first sub-table, and synchronously write the items and amounts to the second main table and the second sub-table, and establish a comparison table between the first main table and the second main table; and generate a refund pre-application document based on the first sub-table and the second sub-table and send it to the financial horizontal connection system; The financial cross-link system is used to generate and return to the non-tax revenue management system a corresponding remote verification file, encapsulation rule file, key, and prompt file based on the pre-refund application document; the verification logic of the remote verification file is controlled by the financial cross-link system; The non-tax revenue management system is further configured to call the remote verification file to open and verify the first master table and the second master table, and identify corresponding information in the first master table and the second master table using the prompt file and the comparison table; the non-tax revenue management system receives modifications to the first master table and / or the second master table, generates a modification record file based on the modifications, and encapsulates the modified first master table and / or the second master table and the modification record file using the encapsulation rule file to obtain an encapsulated file, and then encrypts the encapsulated file using the key to obtain an encrypted application file and upload it to the fiscal cross-link system; The financial cross-link system is also used to decrypt the received encrypted application document and verify whether the modification information in the modification record file is consistent with the prompt file. If so, the encrypted application document is digitally signed and uploaded to TIPS after passing the verification. The TIPS is used to perform a compliance check on the signed encrypted application document received, and if it passes, the document is approved for return to the warehouse; The interface names involved in the remote verification file have been pre-agreed and stored in the non-tax revenue management system. 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. All operations on business data are realized through the remote verification files returned by the financial cross-link system. The calling, reading, writing and correction of business data are all realized under the monitoring of the remote verification files provided by the financial cross-link system. The non-tax revenue management system receives the modification to the first master table and / or the second master table, and generates a modification record file according to the modification, including: The remote verification file starts an information recording thread; The non-tax revenue management system obtains prompt information in the prompt file one by one, locates the specific location of the first master table and / or the second master table according to the location information in the prompt information, and retrieves the business data associated with the specific location; Checking and correcting the business data associated with the specific location according to the prompt content in the prompt information; The correction process is recorded in real time through the information recording thread, and the correction process is summarized to obtain the modification record file.

6. The service data processing device according to claim 5, characterized in that: The scanned image corresponding to the bill information is embedded in the first main table as an attachment; the comparison table includes the comparison relationship between the bill information and the scanned image as well as the items and amounts; the second main table also includes the treasury payment certificate number and the collection unit.

7. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method for processing business data according to any one of claims 1 to 4 is implemented.

Images