CN113656517B - Account checking file processing method and device, electronic equipment and storage medium - Google Patents

Abstract

The present application provides a reconciliation file processing method, device, electronic equipment and storage medium. The method comprises: obtaining a reconciliation file through a zkettle tool; analyzing and processing the reconciliation file through a preset script of the zkettle tool to obtain a reconciliation result; generating write-off files in different provinces according to the reconciliation result, and send the write-off file to the corresponding provincial server, to instruct each provincial server to generate a receipt file according to the write-off file; obtain the receipt file of each provincial server, and update it according to the receipt file of each provincial server The write-off status of the reconciliation file. This application can realize automatic account reconciliation in recharge and payment, avoid cumbersome manual account reconciliation by financial personnel, improve account reconciliation efficiency, and ensure account reconciliation accuracy.

Description

Reconciliation file processing method, device, electronic equipment and storage medium

technical field

The present application relates to computer technology, and in particular to a method, device, electronic equipment and storage medium for processing reconciliation files.

Background technique

As online services become more and more perfect, users can complete recharge and payment online through mobile phones or computers, because the process of online recharge and payment will involve multiple institutions, such as third-party payment agencies, different banks, etc. Therefore, it is more necessary to ensure the accuracy of reconciliation of online self-service recharge and payment.

However, the current online self-service recharge and payment reconciliation method is manual reconciliation by financial personnel. This method of reconciliation is not only cumbersome and inefficient, but also the accuracy of reconciliation cannot be guaranteed.

Contents of the invention

This application provides a method, device, electronic device and storage medium for processing account reconciliation files, which are used to realize automatic account reconciliation in recharge and payment, avoid cumbersome manual account reconciliation by financial personnel, improve account reconciliation efficiency, and ensure account reconciliation accuracy .

In the first aspect, the embodiment of the present application provides a method for processing reconciliation documents, including:

Obtain the reconciliation file through the zkettle tool;

Analyzing and processing the reconciliation file through the preset script of the zkettle tool to obtain a reconciliation result;

Generate write-off files in different provinces according to the reconciliation results, and send the write-off files to corresponding provincial servers to instruct each province server to generate a return receipt file according to the write-off files;

Obtain the receipt file of each provincial server, and update the write-off status of the reconciliation file according to the receipt file of each provincial server.

In an optional implementation manner, the reconciliation file is analyzed and processed through the preset script of the zkettle tool to obtain a reconciliation result, including:

Importing the reconciliation file into a distributed relational database;

The reconciliation file in the distributed relational database is invoked by the zkettle tool, and the reconciliation file is analyzed and processed by the preset script of the zkettle tool to obtain a reconciliation result.

In an optional implementation, the distributed relational database includes the payment data in the government-enterprise online platform, the reconciliation file includes the payment data of the payment platform, and the preset through the zkettle tool Set up a script to analyze and process the reconciliation file, and obtain the reconciliation results, including:

Matching and comparing the payment data and the payment data through the preset script of the zkettle tool;

If the payment data does not match the payment data, determine that the reconciliation result is abnormal;

If the payment data matches the payment data, it is determined that the reconciliation result is normal.

In an optional embodiment, the method includes:

If the reconciliation result is abnormal, obtaining the abnormal data in the comparison file;

Marking the abnormal data, or/and outputting first reminder information corresponding to the abnormal data.

In an optional implementation manner, the reconciliation file is analyzed and processed through the preset script of the zkettle tool to obtain a reconciliation result, including:

Analyzing and processing the reconciliation file according to a plurality of process nodes corresponding to the preset script to obtain an initial reconciliation result;

If the execution result of each process node in the plurality of process nodes is normal, the initial reconciliation result is determined as the reconciliation result.

In an optional embodiment, the method also includes:

If there is a process node whose execution result is abnormal among the plurality of process nodes, the process node whose execution result is abnormal is determined as the target process node;

Outputting second prompt information corresponding to the target process node.

In an optional embodiment, the method also includes:

A summary file is generated according to the receipt file of the server in each province, wherein the summary file includes total receivable information and total payment information;

Send the summary file to the fund platform file server.

In a second aspect, an embodiment of the present application provides a device for processing reconciliation documents, the device comprising:

The reconciliation file acquisition module is used to obtain the reconciliation file through the zkettle tool;

The reconciliation result acquisition module is used to analyze and process the reconciliation file through the preset script of the zkettle tool to obtain the reconciliation result;

A write-off file sending module, configured to generate write-off files in different provinces according to the reconciliation results, and send the write-off files to corresponding provincial servers to instruct each province server to generate a receipt according to the write-off files document;

An update module, configured to obtain the receipt file of each province server, and update the write-off status of the account reconciliation file according to the receipt file of each province server.

In an optional implementation manner, the reconciliation result acquisition module is specifically used for:

Importing the reconciliation file into a distributed relational database;

The reconciliation file in the distributed relational database is invoked by the zkettle tool, and the reconciliation file is analyzed and processed by the preset script of the zkettle tool to obtain a reconciliation result.

In an optional embodiment, the distributed relational database includes the payment data in the government-enterprise online platform, the reconciliation file includes the payment data of the payment platform, and the reconciliation result acquisition module includes:

A comparison unit, configured to match and compare the payment data and the payment data through the preset script of the zkettle tool;

An abnormality determining unit, configured to determine that the reconciliation result is abnormal if the payment data does not match the payment data;

A normal determination unit, configured to determine that the reconciliation result is normal if the payment data matches the payment data.

In an optional implementation manner, the reconciliation file processing device further includes:

An abnormal data acquisition module, configured to obtain the abnormal data in the comparison file if the reconciliation result is abnormal;

The exception processing module is configured to mark the abnormal data, or/and output first reminder information corresponding to the abnormal data.

In an optional implementation manner, the reconciliation result acquisition module also includes:

The initial reconciliation result acquisition unit is configured to analyze and process the reconciliation file according to a plurality of process nodes corresponding to the preset script to obtain an initial reconciliation result;

The execution result detection unit is configured to determine the initial reconciliation result as the reconciliation result if the execution result of each process node in the plurality of process nodes is normal.

In an optional implementation manner, the reconciliation file processing device further includes:

A target process node determining module, configured to determine the process node whose execution result is abnormal as the target process node if there is a process node whose execution result is abnormal among the plurality of process nodes;

A second prompt information output module, configured to output second prompt information corresponding to the target process node.

In an optional implementation manner, the reconciliation file processing device further includes:

A summary file generating module, configured to generate a summary file according to the receipt file of each province server, wherein the summary file includes total receivable information and total payment information;

The summary file sending module is used to send the summary file to the fund platform file server.

In a third aspect, an embodiment of the present application provides an electronic device, including: a memory and a processor;

a memory for storing said processor-executable instructions;

Wherein, the processor is configured to execute the method provided in the foregoing embodiments.

In a fourth aspect, embodiments of the present application provide a computer-readable storage medium, where computer-executable instructions are stored in the computer-readable storage medium, and the computer-executable instructions are used to implement the methods provided in the above-mentioned embodiments when executed by a processor .

In a fifth aspect, the embodiments of the present application provide a computer program product, where the computer program product includes a computer program, and when the computer program is executed by a processor, the method provided in the foregoing embodiments is implemented.

The reconciliation file processing method, device, electronic equipment and storage medium provided by the present application obtain the reconciliation file through the zkettle tool, and analyze and process the reconciliation file through the preset script of the zkettle tool to obtain the reconciliation result , since the zkettle tool can visualize and deploy job timing tasks, it can automatically analyze and process the obtained reconciliation files according to its preset scripts. Generate write-off files in different provinces according to the reconciliation results, and send the write-off files to corresponding provincial servers to instruct each province server to generate a receipt file according to the write-off files, and finally obtain each province Receipt file of the server, update the write-off status of the reconciliation file according to the receipt file of each province server, so that each provincial server can check the data in the reconciliation file according to the reconciliation result and the actual situation of various provinces Perform write-off processing, and update the write-off status in real time according to the feedback from the provincial server, improving the efficiency and accuracy of account reconciliation.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description serve to explain the principles of the application.

Fig. 1 is a schematic diagram of the application environment of the reconciliation file processing method provided by the embodiment of the present application;

FIG. 2 is a schematic flow diagram of a method for processing reconciliation files provided in an embodiment of the present application;

FIG. 3 is a schematic flow diagram of another method for processing reconciliation files provided in the embodiment of the present application;

FIG. 4 is an interface schematic diagram of a GUI design interface provided by an embodiment of the present application;

FIG. 5 is an interface schematic diagram of another GUI design interface provided by the embodiment of the present application;

FIG. 6 is an interface schematic diagram of another GUI design interface provided by the embodiment of the present application;

FIG. 7 is a schematic flowchart of step 203 provided according to the embodiment of FIG. 3;

FIG. 8 is an interface schematic diagram of another GUI design interface provided by the embodiment of the present application;

FIG. 9 is a schematic structural diagram of a reconciliation file processing device provided in an embodiment of the present application;

FIG. 10 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.

By means of the above drawings, specific embodiments of the present application have been shown, which will be described in more detail hereinafter. These drawings and text descriptions are not intended to limit the scope of the concept of the application in any way, but to illustrate the concept of the application for those skilled in the art by referring to specific embodiments.

Detailed ways

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numerals in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with aspects of the present application as recited in the appended claims.

As online services become more and more perfect, users can complete recharge and payment online through mobile phones or computers. Since online recharge and payment will involve multiple institutions, such as third-party payment agencies, different banks, etc., therefore , It is even more necessary to ensure the accuracy of reconciliation of online self-service recharge and payment.

However, at present, the reconciliation of online self-service recharge and payment is usually done by financial personnel through manual reconciliation. This method of reconciliation is not only cumbersome and inefficient, but also the accuracy of reconciliation cannot be guaranteed.

Since manual reconciliation can no longer meet the rapid development of the times, the application of the reconciliation system has been developed. The current application of the reconciliation system is mainly divided into several modules, such as file acquisition, file analysis, reconciliation processing, etc. The acquisition of files is mainly Actively obtained or pushed by the other party, most banks or third-party payment institutions require the access party to provide SSH File Transfer Protocol (Secret File Transfer Protocol, SFTP)/File Transfer Protocol (File Transfer Protocol, FTP) services, and regularly transfer the reconciliation files Push it to the server, and technically download the reconciliation file in the server to the local directory with analysis through the computer programming language (java) program, and then complete the analysis of the file and put it into the warehouse, and compare it with the local order data. The reconciliation logic is based on the order of the bank or third-party payment institution, and finally the difference in reconciliation is processed. With the continuous increase of business volume, according to the existing reconciliation model design, it will lead to bottlenecks in the response speed of the database and the performance of the database server, affecting normal business.

Specifically, the current reconciliation solution mainly uses java timing tasks to obtain reconciliation files from upstream channels, and the program is parsed line by line into the database, and the java program is used to connect to the database for processing. Record. Relevant data are processed during the reconciliation process.

However, if the reconciliation data is huge, it will put pressure on the reading and writing of the database, which will have a great impact on performance, and the expansion of reconciliation logic is extremely troublesome, and as the reconciliation data accumulates over time, the database will encounter great challenges. In the case of a large business volume, the reconciliation server and the database server have a high load, which affects the entire reconciliation process.

The embodiment of the present application provides a reconciliation file processing method, device, electronic device and storage medium, aiming to solve the above technical problems in the prior art. The reconciliation file processing method, device, electronic device and storage medium provided in the embodiment of the present application The medium can implement the account reconciliation solution by using the Zkettle tool. Using the characteristics of zkettle to operate the database asynchronously, it can reduce the pressure of application testing, reduce database connections, flexible deployment methods, convenient and easy-to-use process design and flexible data conversion process It is also conducive to the expansion of reconciliation logic and further improves the efficiency of reconciliation.

The technical terms involved in the application examples are explained below:

Zkettle: It is a data warehouse technology (Extract Transform Load, ETL) tool that allows you to manage data from different databases and describe what you want to do by providing a graphical development environment. Compared with the open source kettle, the government The company's self-developed zkettle supports distributed deployment, supports visual scripts to be deployed according to plan, and script SMS alerts, and adds support for Tiangong components.

Distributed Relational Database Service (DRDS) is a distributed relational database service middleware independently developed by Alibaba and highly compatible with MySQL protocol and syntax. Focusing on solving the scalability problem of stand-alone relational databases, it has the characteristics of light weight (stateless), flexibility, stability, and high efficiency. Compared with traditional databases, it is more prominent in distributed technology and sub-database keys, and has light weight and flexibility. , stability, high efficiency and other characteristics, it is used for the storage of reconciliation data in this solution.

kvStore: It is compatible with the open source Redis protocol standard and provides persistent memory database services. Based on a highly reliable dual-machine hot standby architecture and a seamlessly scalable cluster architecture, it meets the business needs of high-reading and writing performance scenarios and elastic capacity changes. .

The following describes the application environment of the reconciliation file processing method of the embodiment of the present application. As shown in FIG. 1 , the application environment may include payment companies, government-enterprise online platforms, DRDS databases, provincial systems, and capital platforms.

Among them, the government-enterprise online platform can respectively establish communication links with payment companies, DRDS databases, provincial systems, and capital platforms to realize data transmission. Among them, payment companies, government-enterprise online platforms, DRDS databases, provincial systems, and capital platforms can all be servers. Among them, the payment company can push the reconciliation file to the government-enterprise online platform. The government-enterprise online platform can push documents to the fund platform. Files are exchanged between the government-enterprise online platform and the provincial system. The government-enterprise online platform can also write data into the DRDS database, or extract data from the DRDS database.

The technical solution of the present application and how the technical solution of the present application solves the above technical problems will be described in detail below with specific embodiments. The following specific embodiments may be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present application will be described below in conjunction with the accompanying drawings.

Fig. 2 is a schematic flow chart of a method for processing reconciliation files provided in the embodiment of the present application. As shown in Fig. 2, the method provided in the present embodiment includes:

101. Obtain the reconciliation file through the zkettle tool.

Exemplarily, the subject of execution of this embodiment may be an electronic device, or a terminal device, or a server, or other apparatuses or devices capable of executing this embodiment, without limitation. In this embodiment, the execution subject is described as a server, which may specifically be the server of the government-enterprise online platform in FIG. 1 .

In some embodiments, the government-enterprise online platform can use the zkettle tool to obtain the reconciliation file pushed by the payment company to the file server of the government-enterprise online platform. Wherein, the reconciliation file may include the payment data recorded by the payment company or the payment platform, such as the payment data that the user pays to the merchant through WeChat, Alipay, UnionPay and other platforms. Specifically, the payment data may include payment amount, payment time, payment platform, user information, and the like.

102. Analyze and process the reconciliation file through the preset script of the zkettle tool to obtain the reconciliation result.

In some implementations, the government-enterprise online platform can compare and analyze the payment data of the payment company and the payment data recorded in the government-enterprise online platform through the preset script of the zkettle tool. Specifically, the preset script can be used to convert the payment The company's payment data is compared with the payment data recorded in the government-enterprise online platform. If the payment data of the payment company is consistent with the payment data recorded in the government-enterprise online platform, it can be determined that the reconciliation result is normal. If the payment data of the payment company is inconsistent with the payment data recorded in the government-enterprise online platform, it can be determined that the reconciliation result is abnormal.

In some embodiments, if the government-enterprise online platform determines that the reconciliation result is abnormal, it can further analyze the abnormal data and record the abnormal data in the reconciliation result. Optionally, the abnormal data may include the difference between the payment data of the payment company and the payment data recorded in the government-enterprise online platform, the abnormal payment company, the region and province corresponding to the abnormal data, and the like.

103. Generate write-off files in different provinces according to the reconciliation results, and send the write-off files to corresponding provincial servers, so as to instruct each provincial server to generate a receipt file according to the write-off files.

In some embodiments, the government-enterprise online platform can generate the BSS (Business Support System) write-off files of the provinces according to the reconciliation results, and send the write-off files corresponding to each province to the provincial servers of the corresponding provinces to instruct each The provincial server generates a receipt file according to the write-off file it receives. Wherein, the write-off file corresponding to the province may include data such as the receivable amount of the province. Wherein, the receipt file corresponding to the province may include data that can reflect the situation of the receivable amount and the actual amount received in the province, such as the difference between the receivable amount and the actual amount received in the province, or the reason for the difference.

As an example, for example, the server whose province is Sichuan can record the actual amount received in the province in the last month in real time, and then perform write-off processing according to the amount received and the amount receivable in the latest month in the write-off file, and according to A return receipt file is generated as a result of the write-off processing. For example, the return receipt file may include data such as the deviation between the amount received in the last month and the amount receivable, and the degree of deviation.

104. Obtain the receipt file of the server in each province, and update the write-off status of the reconciliation file according to the receipt file of the server in each province.

In some real-time methods, the government-enterprise online platform can send a request for obtaining the receipt file to each provincial server to instruct the provincial server to feed back the receipt file, thereby obtaining the receipt file of each provincial server, and then according to the The receipt file updates the write-off status of the reconciliation file. Specifically, the data used to reflect the write-off status of the reconciliation file can be updated and saved to the file server of the government-enterprise online platform, or the data used to reflect the write-off status of the reconciliation file can be displayed on the government-enterprise online platform on the display and update in real time.

In this embodiment, the reconciliation file is obtained through the zkettle tool, and the reconciliation file is analyzed and processed through the preset script of the zkettle tool to obtain the reconciliation result. Since the zkettle tool can deploy job timing tasks visually, It can automatically analyze and process the obtained reconciliation files according to its pre-set scripts. Generate write-off files in different provinces according to the reconciliation results, and send the write-off files to corresponding provincial servers to instruct each province server to generate a receipt file according to the write-off files, and finally obtain each province Receipt file of the server, update the write-off status of the reconciliation file according to the receipt file of each province server, so that each provincial server can check the data in the reconciliation file according to the reconciliation result and the actual situation of various provinces Perform write-off processing, and update the write-off status in real time according to the feedback from the provincial server, improving the efficiency and accuracy of account reconciliation. In addition, by using the zkettle tool, you can deploy job timing tasks visually, import reconciliation files into the database regularly, and use zkettle to operate the database asynchronously, which can reduce the pressure of application testing, reduce database connections, flexible deployment methods, and easy-to-use The process-based design and flexible data conversion process are also conducive to the expansion of reconciliation logic, which solves the bottleneck of stand-alone database capacity and the difficulty of database expansion.

Fig. 3 is a schematic flowchart of another method for processing reconciliation files provided in the embodiment of the present application. As shown in Fig. 3, the method provided in the present embodiment includes:

201. Obtain the reconciliation file through the zkettle tool.

202. Import the reconciliation file into the distributed relational database.

In some embodiments, the government-enterprise online platform can use zkettle to obtain the reconciliation file pushed by the payment company to the file server, and import it into a distributed relational database (hereinafter referred to as DRDS database), and link the payment company's data with the government-enterprise online The payment data in the platform is compared and analyzed and the abnormal data is processed, and the reconciliation results obtained are converted into reconciliation data and stored in the DRDS database. The reconciliation data can be the table corresponding to the reconciliation results.

203. Call the reconciliation file in the distributed relational database through the zkettle tool, and analyze and process the reconciliation file through the preset script of the zkettle tool to obtain a reconciliation result.

In some implementations, the distributed relational database includes the payment data in the government-enterprise online platform, and the reconciliation file includes the payment data of the payment platform. The specific implementation of step 203 includes: using the preset script of the zkettle tool to transfer the If the payment data and payment data do not match, the reconciliation result is determined to be abnormal; if the payment data and payment data match, the reconciliation result is determined to be normal.

Optionally, if the payment data is inconsistent with the payment data, it can be determined that the payment data and the payment data do not match; if the payment data and the payment data are consistent, it can be determined that the payment data and the payment data match.

Optionally, if the difference between the payment data and the payment data is within a specified range, it may be determined that the payment data and the payment data match. Otherwise, it is determined that the payment data does not match the payment data.

In this embodiment, the accuracy of the reconciliation can be ensured by comparing the data of different platforms for reconciliation.

In some implementations, if the reconciliation result is abnormal, obtain the abnormal data in the comparison file; mark the abnormal data, or/and output the first reminder information corresponding to the abnormal data.

As an example, abnormal data may be highlighted and displayed, or displayed in a specific color or in a specific display manner.

As another example, outputting the first reminder information corresponding to the abnormal data may specifically send a short message to the user's mobile terminal, so as to remind the user that the account reconciliation data is abnormal.

204. Generate write-off files in different provinces according to the reconciliation results, and send the write-off files to corresponding provincial servers, so as to instruct each provincial server to generate a receipt file according to the write-off files.

As an example, as shown in Figure 4, the user can pre-set a script about the write-off file generation process in the graphical user interface (Graphical User Interface, GUI) design interface of the zkettle tool, wherein, about the write-off file The script of the generation process can correspond to multiple process nodes, such as process nodes such as verifying payment tasks, generating reconciliation data, generating BSS files, and uploading files. When any one of the multiple process nodes fails, a short message can be sent to the user to remind the user of the location of the failure point. Specifically, the specific process of generating the write-off file can be as follows: Start→Set variable_automatic→Judging payment task→Check payment task→Generate reconciliation data→Generate BSS file→File upload→BSS file uploaded successfully→ Insert log → update task → success. Among them, if there is a failure in checking payment tasks, generating reconciliation data, generating BSS files, or uploading files, such as payment task failure, reconciliation data generation failure, BSS file generation failure, and BSS file upload failure, a text message can be sent to remind the user. And abort the job on the failed process node. Wherein, setting the variable_automatically may be a variable for setting the process node on or off, or the like.

Among them, the government-enterprise online platform can use kvstore as a provincial switch, and can customize different reconciliation schemes according to different provinces.

205. Obtain the receipt file of the server in each province, and update the write-off status of the reconciliation file according to the receipt file of the server in each province.

As an example, as shown in Figure 5, the user can preset a script about the process of updating the write-off status according to the receipt file in the graphical GUI design interface of the zkettle tool, wherein, about the process of updating the write-off status according to the receipt file Scripts can correspond to multiple process nodes, such as checking CBSS (Centralized Business Support System) upload tasks, checking BSS upload tasks, downloading receipt files, calling HTTP interfaces, calling abnormal order interfaces and other process nodes. When any one of the above multiple process nodes fails, a short message can be sent to the user to remind the user of the location of the failure point. Specifically, the specific process of updating the write-off status according to the receipt file can be followed in sequence: Start→Set variable_automatic→Judge CBSS and BSS upload tasks→Check CBSS upload tasks→Check BSS upload tasks→Receipt file download→Receipt File storage→check the receipt file→call the HTTP interface→call the abnormal order interface→get the receipt task successfully→insert the log→update the task→success, among them, if you check the CBSS upload task, check the BSS upload task, download the receipt file, and call the HTTP interface 1. If there is a failure in calling the abnormal order interface, a short message can be sent to remind the user, and the job will be terminated at the failed process node. Wherein, the setting variable_auto can be a variable for setting each process node to be turned on or off. Wherein, checking the CBSS upload task may be checking whether the upload of the CBSS file is successful. Checking the BSS upload task may be checking whether the BSS file upload is successful.

206. Generate a summary file according to the receipt file of the server in each province, where the summary file includes information on the total amount receivable and the total amount received.

207. Send the summary file to the file server of the fund platform.

Among them, the fund platform file server can collect and record the national payment data.

As an example, as shown in Figure 6, the user can pre-set the script on the process of generating the summary file in the graphical GUI design interface of the zkettle tool, where the summary file can also be called the fund platform file or the required file of the fund platform , the script about the process of generating the summary file can correspond to multiple process nodes, such as process nodes such as checking account write-off tasks, generating fund platform data, generating fund platform files, and file uploads. When any one of the multiple process nodes fails, a short message can be sent to the user to remind the user of the location of the failure point. Specifically, the specific process of generating summary files can be followed in sequence: Start→Set upload variables→Judge write-off tasks→Generate fund platform data→Generate fund platform files→File upload→Upload log parameters→Insert logs→Update tasks →Success, among them, if there is a failure in the account verification task, you can verify the write-off log, if there is a failure in generating the fund platform data, you can generate a data log, if there is a failure in generating the fund platform file, you can generate a file log, and if a file upload fails, you can generate File upload log, and then send the faulty process node to the user via SMS, and terminate the job on the faulty process node. Wherein, judging the write-off task may be used to detect whether the write-off task is a normal write-off or an abnormal write-off.

In some implementations, as shown in Figure 7, the specific implementation of the above step 203 includes the following sub-steps:

2031. Analyze and process the reconciliation file according to multiple process nodes corresponding to the preset script, and obtain an initial reconciliation result.

2032. If the execution result of each process node in the plurality of process nodes is normal, determine the initial reconciliation result as the reconciliation result.

2033. If there is a process node whose execution result is abnormal among the plurality of process nodes, determine the process node whose execution result is abnormal as the target process node.

2034. Output second prompt information corresponding to the target process node. As an example, as shown in Figure 8, the user can set a preset script in the graphical GUI design interface of the zkettle tool, for example, when setting a preset script for analyzing and processing the reconciliation file, you can set Multiple process nodes. When the preset script is executed, it can be executed sequentially according to its corresponding multiple progress nodes. Wherein, when a process node breaks down, a second prompt message (such as a short message) can be sent to the user's mobile terminal to remind the user that if a process is grounded, it can automatically enter the next process node if there is no failure. Among them, the process node can include file download and analysis, copy data to snapshot table, government and enterprise order statistics and change title (title) table, reconciliation process, call Hyper Text Transfer Protocol (Hyper Text Transfer Protocol, HTTP) interface, etc., request HttpClient. Among them, HttpClient is a client programming toolkit. Specifically, the whole process of analyzing and processing the reconciliation file can be followed in turn: Start → generate subsequent unified parameters → storage task table → file download and analysis → copy data to snapshot table → government and enterprise order statistics and changes title table→reconciliation process→request HttpClient→call HTTP interface→set variable 5→change title table record 2→success. Among them, file download analysis, copy data to snapshot table, government and enterprise order statistics and change title table, account reconciliation process, request HttpClient, change title table record 2 failure, and call HTTP interface failure can send SMS to remind, and failure The short message can be recorded in the record log 2, and then set variables according to the record log 2 to copy the attributes of the title table, thereby changing the record of the title table record, and sending the changed title table record to the user through a text message, and then aborting the job.

Optionally, the first prompt information and the second prompt information include but are not limited to short message information, voice information, image information, and the like.

In this embodiment, by using zkettle to obtain the reconciliation file pushed by the payment company to the file server, and import it into the DRDS database, compare and analyze the payment company's data with the payment data in the government-enterprise online platform and analyze the abnormal processing of data. Then use zkettle to call the compared reconciliation data in the DRDS database, and generate a provincial BSS write-off file, which is pushed to the file server of each province for the province to do write-off to obtain the write-off receipt file pushed by each province, and use zkettle to call the write-off Interface to update the payment write-off status. Finally, the documents required by the fund platform (such as the total amount receivable and the total amount received) are generated by province and pushed to the fund platform file server. In this way, the payment data of each province can be reconciled in a stable and orderly manner by using the zkettle tool and the DRDS database, which improves the reconciliation efficiency. Among them, the job is deployed visually through the zkettle tool, and the reconciliation files are regularly imported into DRDS. Using zkettle to operate the database asynchronously can reduce the pressure of application testing, reduce database connections, flexible deployment methods, and convenient and easy-to-use process design and flexible The data conversion process is also conducive to the expansion of reconciliation logic. At the same time, DRDS supports features such as sub-database and sub-table, smooth expansion, service upgrade and upgrade, transparent read-write separation, and distributed transactions, which reduces the pressure on the database server and solves the bottleneck of stand-alone database capacity and the difficulty of database expansion.

Fig. 9 is a schematic structural diagram of a reconciliation file processing device provided in the embodiment of the present application. As shown in Fig. 9, the device includes:

The reconciliation file obtaining module 31 is used to obtain the reconciliation file through the zkettle tool.

The reconciliation result acquisition module 32 is used to analyze and process the reconciliation file through the preset script of the zkettle tool to obtain the reconciliation result.

The write-off file sending module 33 is configured to generate write-off files in different provinces according to the reconciliation results, and send the write-off files to corresponding provincial servers to instruct each provincial server to generate a receipt file according to the write-off files.

The update module 34 is configured to obtain the receipt file of each provincial server, and update the write-off status of the reconciliation file according to the receipt file of each provincial server.

In some embodiments, the reconciliation result acquisition module 32 is specifically used for:

Import the reconciliation file into the distributed relational database.

The reconciliation file in the distributed relational database is invoked through the zkettle tool, and the reconciliation file is analyzed and processed through the preset script of the zkettle tool to obtain the reconciliation result.

In some embodiments, the distributed relational database includes the payment data in the government-enterprise online platform, the reconciliation file includes the payment data of the payment platform, and the reconciliation result acquisition module 32 includes:

The comparison unit is used to match and compare the payment data and payment data through the preset script of the zkettle tool.

The abnormality determination unit is configured to determine that the reconciliation result is abnormal if the payment data does not match the payment data.

The normal determination unit is configured to determine that the reconciliation result is normal if the payment data matches the payment data.

In some embodiments, the reconciliation file processing device further includes:

The abnormal data obtaining module is used to obtain the abnormal data in the comparison file if the reconciliation result is abnormal.

The exception processing module is configured to mark the abnormal data, or/and output the first reminder information corresponding to the abnormal data.

In some embodiments, the reconciliation result acquisition module 32 also includes:

The initial reconciliation result acquisition unit is configured to analyze and process the reconciliation file according to a plurality of process nodes corresponding to the preset script to obtain the initial reconciliation result.

The execution result detection unit is configured to determine the initial reconciliation result as the reconciliation result if the execution result of each process node in the plurality of process nodes is normal.

In some embodiments, the reconciliation file processing device further includes:

The target process node determining module is used to determine the process node whose execution result is abnormal as the target process node if there is a process node whose execution result is abnormal among the plurality of process nodes.

The second prompt information output module is configured to output second prompt information corresponding to the target process node.

In some embodiments, the reconciliation file processing device further includes:

The summary file generation module is used to generate a summary file according to the receipt file of each provincial server, wherein the summary file includes information on the total amount receivable and the total amount received.

The summary file sending module is used to send the summary file to the fund platform file server.

Exemplarily, this embodiment may refer to the foregoing method embodiment, and its principles and technical effects are similar, so details are not repeated here.

FIG. 10 is a schematic structural diagram of an electronic device provided by an embodiment of the present application. As shown in FIG. 10 , the electronic device includes a memory 43 and a processor 42 .

The memory 43 is used for storing instructions executable by the processor 42 .

The processor 42 is configured to execute the methods provided in the foregoing embodiments.

The electronic device also includes a receiver 40 and a transmitter 41 . The receiver 40 is used to receive instructions and data sent by the external device, and the transmitter 41 is used to send instructions and data to the external device.

Wherein, the electronic device may be a mobile phone, a computer, a tablet computer or the like.

Specifically, the electronic device may further include one or more of the following components: a processing component, a power supply component, a multimedia component, and an input/output (I/O) interface. The processing component may be equivalent to the processor 42 of the above-mentioned embodiment,

The processing components typically control the overall operations of the electronic device, such as those associated with display and recording operations. The processing component may include one or more processors to execute instructions to complete all or part of the steps of the above method. Additionally, a processing component may include one or more modules to facilitate interaction between the processing component and other components. For example, the processing component may include a multimedia module to facilitate interaction between the multimedia component and the processing component.

The memory is configured to store various types of data to support operations at the electronic device. Examples of such data include, among other things, instructions for any application or method operating on the electronic device. The memory can be realized by any type of volatile or non-volatile storage devices or their combination, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read Only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, etc.

Power components provide power to various components of electronic equipment. Power components may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to electronic devices.

The multimedia component includes a screen providing an output interface between said electronic device and a user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may not only sense a boundary of a touch or swipe action, but also detect duration and pressure associated with the touch or swipe action.

The I/O interface provides an interface between the processing component and the peripheral interface module, and the above peripheral interface module can be a keyboard, a click wheel, a button, and the like. These buttons may include, but are not limited to: a home button, volume buttons, start button, and lock button.

In an exemplary embodiment, there is also provided a non-transitory computer-readable storage medium including instructions, such as a memory including instructions, which can be executed by a processor of an electronic device to implement the above method. For example, the non-transitory computer readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.

An embodiment of the present application provides a computer-readable storage medium, where computer-executable instructions are stored in the computer-readable storage medium, and the computer-executable instructions are used to implement the methods provided in the foregoing embodiments when executed by a processor.

An embodiment of the present application provides a computer program product, the computer program product includes: a computer program, the computer program is stored in a readable storage medium, at least one processor of an electronic device can read the computer program from the readable storage medium, at least one The processor executes the computer program so that the electronic device executes the solutions provided by any of the foregoing embodiments.

Other embodiments of the present application will be readily apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any modification, use or adaptation of the application, these modifications, uses or adaptations follow the general principles of the application and include common knowledge or conventional technical means in the technical field not disclosed in the application . The specification and examples are to be considered exemplary only, with a true scope and spirit of the application indicated by the following claims.

It should be understood that the present application is not limited to the precise constructions which have been described above and shown in the accompanying drawings, and various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims (8)

1. A method for processing reconciliation documents, characterized in that, comprising: Obtain the reconciliation file through the zkettle tool; Analyzing and processing the reconciliation file through the preset script of the zkettle tool to obtain a reconciliation result; Generate write-off files in different provinces according to the reconciliation results, and send the write-off files to corresponding provincial servers to instruct each province server to generate a return receipt file according to the write-off files; Obtain the receipt file of each provincial server, and update the write-off status of the reconciliation file according to the receipt file of each provincial server; The described reconciliation file is analyzed and processed through the preset script of the zkettle tool to obtain a reconciliation result, including: Analyzing and processing the reconciliation file according to a plurality of process nodes corresponding to the preset script to obtain an initial reconciliation result; If the execution result of each process node in the plurality of process nodes is normal, the initial reconciliation result is determined as the reconciliation result; If there is a process node whose execution result is abnormal among the plurality of process nodes, the process node whose execution result is abnormal is determined as the target process node; Outputting second prompt information corresponding to the target process node. 2. The method according to claim 1, characterized in that, the said reconciliation file is analyzed and processed by said preset script of said zkettle tool to obtain a reconciliation result, comprising: Importing the reconciliation file into a distributed relational database; The reconciliation file in the distributed relational database is invoked by the zkettle tool, and the reconciliation file is analyzed and processed by the preset script of the zkettle tool to obtain a reconciliation result. 3. The method according to claim 2, wherein the distributed relational database includes payment data in the government-enterprise online platform, the reconciliation file includes the payment data of the payment platform, and the said payment data through the said The preset script of the zkettle tool analyzes and processes the reconciliation file to obtain the reconciliation results, including: Matching and comparing the payment data and the payment data through the preset script of the zkettle tool; If the payment data does not match the payment data, determine that the reconciliation result is abnormal; If the payment data matches the payment data, it is determined that the reconciliation result is normal. 4. The method according to claim 3, characterized in that the method comprises: If the reconciliation result is abnormal, obtain the abnormal data in the comparison file; Marking the abnormal data, or/and outputting first reminder information corresponding to the abnormal data. 5. The method according to any one of claims 1-4, characterized in that the method further comprises: A summary file is generated according to the receipt file of the server in each province, wherein the summary file includes total receivable information and total payment information; Send the summary file to the fund platform file server. 6. A reconciliation file processing device, characterized in that the device comprises: The reconciliation file acquisition module is used to obtain the reconciliation file through the zkettle tool; The reconciliation result acquisition module is used to analyze and process the reconciliation file through the preset script of the zkettle tool to obtain the reconciliation result; A write-off file sending module, configured to generate write-off files in different provinces according to the reconciliation results, and send the write-off files to corresponding provincial servers to instruct each province server to generate a receipt according to the write-off files document; An update module, configured to obtain the receipt file of each provincial server, and update the write-off status of the reconciliation file according to the receipt file of each provincial server; The reconciliation result acquisition module includes: The initial reconciliation result acquisition unit is configured to analyze and process the reconciliation file according to a plurality of process nodes corresponding to the preset script to obtain an initial reconciliation result; An execution result detection unit, configured to determine the initial reconciliation result as the reconciliation result if the execution result of each process node in the plurality of process nodes is normal; The target process node determination module, if there is a process node whose execution result is abnormal among the plurality of process nodes, determine the process node whose execution result is abnormal as the target process node; A second prompt information output module, configured to output second prompt information corresponding to the target process node. 7. An electronic device, comprising: a memory and a processor; a memory for storing said processor-executable instructions; Wherein, the processor is configured to execute the method according to any one of claims 1-4. 8. A computer-readable storage medium, characterized in that, computer-executable instructions are stored in the computer-readable storage medium, and the computer-executable instructions are used to implement any one of claims 1-4 when executed by a processor the method described.

Images