Account reconciliation data processing method, device, electronic device and storage medium

Abstract

The present application provides a method, device, electronic device and storage medium for processing reconciliation data, and relates to the technical field of reconciliation data processing. The method includes: in response to received transaction flow data, obtaining transaction flow information of the transaction flow data, and determining the reconciliation category and reconciliation identification information of the transaction flow data according to the transaction flow information; calling the corresponding target reconciliation template based on the reconciliation category, generating the reconciliation information of the transaction flow data based on the transaction flow data and the target reconciliation template, and writing the reconciliation information of the transaction flow data into the reconciliation information table corresponding to the reconciliation category, the reconciliation information table including different reconciliation information with the same reconciliation category; in response to a reconciliation data sending instruction, obtaining reconciliation information with the same reconciliation identification information from all reconciliation information tables, and sending all the obtained reconciliation information to the target reconciliation platform corresponding to the current reconciliation identification information. The present application effectively improves the processing efficiency of reconciliation data.

Description

Technical Field

[0001] The present application relates to the technical field of reconciliation data processing, and in particular to a reconciliation data processing method, a reconciliation data processing device, an electronic device and a computer-readable storage medium. Background Art

[0002] Non-tax revenue refers to all revenues obtained other than taxes. At present, the reconciliation of non-tax revenue has the following problems: the non-tax components of the agent bank are connected to the non-tax systems of local finances. Due to the different requirements of different regions, different reconciliation messages usually have different statistical and sending requirements, which will lead to inconsistent reconciliation modes and multiple reconciliation modes, thereby increasing the management difficulty of the reconciliation mode and the processing efficiency of reconciliation data; at present, non-tax reconciliation usually needs to be completed on T+1 day. In order to ensure the normal operation of the daytime system business and the accuracy of the reconciliation data, the reconciliation needs to be completed from 00:00 to 06:00 on T+1 day. However, the calculation, statistics and sending of a large amount of reconciliation data within a limited time are a huge challenge to the performance of the system; at the same time, the current reconciliation method is difficult to avoid abnormal reconciliation data details caused by human factors, time differences and system fault tolerance, and it is impossible to monitor the reconciliation sending records and result data. Summary of the invention

[0003] The present application provides a reconciliation data processing method, a reconciliation data processing device, an electronic device and a computer-readable storage medium, which are used to solve the problem of low efficiency of reconciliation data processing in existing reconciliation methods.

[0004] In a first aspect of the present application, a method for processing reconciliation data is provided, comprising:

[0005] In response to the received transaction flow data, acquiring transaction flow information of the transaction flow data, and determining the reconciliation category and reconciliation identification information of the transaction flow data according to the transaction flow information;

[0006] Based on the reconciliation category, a corresponding target reconciliation template is called, reconciliation information of the transaction flow data is generated based on the transaction flow data and the target reconciliation template, and the reconciliation information of the transaction flow data is written into a reconciliation information table corresponding to the reconciliation category, wherein the reconciliation information table includes different reconciliation information with the same reconciliation category;

[0007] In response to the reconciliation data sending instruction, reconciliation information with the same reconciliation identification information is obtained from all reconciliation information tables, and all the obtained reconciliation information is sent to the target reconciliation platform corresponding to the current reconciliation identification information.

[0008] Optionally, the transaction flow information includes:

[0009] Transaction serial number, transaction amount, transaction account, transaction time, transaction category and region information;

[0010] Determining the reconciliation category of the transaction flow data according to the transaction flow information includes:

[0011] Based on a pre-constructed reconciliation category matching table, the reconciliation category of the transaction flow data is determined according to the transaction category, and the reconciliation category matching table includes reconciliation categories corresponding to different transaction categories.

[0012] Optionally, the region information includes information about the region where the transaction flow data is generated or information about the region where a transaction account associated with the transaction flow data is opened;

[0013] Determining the reconciliation identification information of the transaction flow data according to the transaction flow information includes:

[0014] Based on a pre-constructed reconciliation identification information matching table, the reconciliation identification information and the target reconciliation platform of the transaction flow data are determined according to the regional information. The reconciliation identification information matching table includes the reconciliation identification information corresponding to different regional information, and the target reconciliation platform corresponding to different reconciliation identification information.

[0015] Optionally, calling a corresponding target reconciliation template based on the reconciliation category includes:

[0016] Determining a reconciliation template set corresponding to the reconciliation category based on the reconciliation category, the reconciliation template set including different reconciliation templates belonging to the same reconciliation category, wherein each reconciliation category corresponds to one reconciliation template set;

[0017] Based on the regional information, a reconciliation template in the reconciliation template set that matches the regional information is determined as the target reconciliation template.

[0018] Optionally, different reconciliation templates belonging to the same reconciliation category include:

[0019] Universal reconciliation templates belonging to the same reconciliation category and at least one non-universal reconciliation template matching information in different regions;

[0020] Determining, based on the regional information, a reconciliation template in the reconciliation template set that matches the regional information as the target reconciliation template includes:

[0021] Based on the regional information, query whether the reconciliation template set includes a non-universal reconciliation template matching the regional information;

[0022] If a non-universal reconciliation template matching the regional information exists in the reconciliation template set, determining the non-universal reconciliation template as the target reconciliation template;

[0023] If there is no non-universal reconciliation template matching the regional information in the reconciliation template set, a universal reconciliation template in the reconciliation template set is determined as the target reconciliation template.

[0024] Optionally, the method further comprises:

[0025] Receiving a reconciliation result message from the target reconciliation platform, and writing the received reconciliation result message into a reconciliation result record table, wherein the reconciliation result message is generated by the target reconciliation platform after reconciling the reconciliation information sent to the target reconciliation platform, and the reconciliation result message includes verification information of reconciliation success or reconciliation failure;

[0026] The verification information of the reconciliation result message in the reconciliation result record table is determined to be the number of reconciliation results that failed to be reconciled, and if the number of reconciliation results is greater than a preset threshold, an alarm message is generated.

[0027] In a second aspect of the present application, a reconciliation data processing device is provided, comprising:

[0028] A data collection module is configured to obtain transaction flow information of the transaction flow data in response to the received transaction flow data, and determine the reconciliation category and reconciliation identification information of the transaction flow data according to the transaction flow information;

[0029] a reconciliation information generating module, configured to call a corresponding target reconciliation template based on the reconciliation category, generate reconciliation information of the transaction flow data based on the transaction flow data and the target reconciliation template, and write the reconciliation information of the transaction flow data into a reconciliation information table corresponding to the reconciliation category, wherein the reconciliation information table includes different reconciliation information of the same reconciliation category;

[0030] The reconciliation information sending module is configured to obtain reconciliation information with the same reconciliation identification information from all reconciliation information tables in response to the reconciliation data sending instruction, and send all the obtained reconciliation information to the target reconciliation platform corresponding to the current reconciliation identification information.

[0031] According to a third aspect of the present application, an electronic device is provided, comprising: a processor, and a memory communicatively connected to the processor;

[0032] The memory stores computer-executable instructions;

[0033] The processor executes the computer-executable instructions stored in the memory to implement the above method.

[0034] In a fourth aspect of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to implement the above-mentioned method when executed by a processor.

[0035] In a fifth aspect of the present application, a computer program product is provided, including a computer program, which implements the above method when executed by a processor.

[0036] This application constructs different reconciliation templates in advance according to different reconciliation categories, and calls the corresponding reconciliation templates to generate reconciliation information based on different reconciliation categories corresponding to different transaction flows during the day. At the end of the day, all the generated reconciliation information is sent to different reconciliation channels according to the reconciliation identifier. By decoupling the reconciliation data processing and the reconciliation data sending, the processing efficiency of the reconciliation data is effectively improved. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0038] Figure 1 A method flow chart of a method for processing reconciliation data provided in an embodiment of the present application;

[0039] Figure 2 A reconciliation data processing flow for a reconciliation category provided in an embodiment of the present application;

[0040] Figure 3 A schematic diagram of the process of sending reconciliation data provided in an embodiment of the present application;

[0041] Figure 4 A schematic diagram of the data processing flow of the reconciliation result provided in the embodiment of the present application;

[0042] Figure 5 A schematic diagram of a reconciliation data processing device provided in an embodiment of the present application;

[0043] Figure 6 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application.

[0044] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0045] In order to make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. It should be understood that the specific implementation methods described herein are only used to illustrate and explain the embodiments of the present application, and are not used to limit the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0046] It should be noted that if the embodiments of the present application involve directional indications (such as up, down, left, right, front, back...), the directional indications are only used to explain the relative position relationship, movement status, etc. between the components under a certain specific posture (as shown in the accompanying drawings). If the specific posture changes, the directional indication will also change accordingly.

[0047] In addition, if there are descriptions of "first", "second", etc. in the embodiments of the present application, the descriptions of "first", "second", etc. are only for descriptive purposes and cannot be understood as indicating or implying their relative importance or implicitly indicating the number of technical features indicated. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In addition, the technical solutions between the various embodiments can be combined with each other, but they must be based on the ability of ordinary technicians in the field to implement them. When the combination of technical solutions is contradictory or cannot be implemented, it should be considered that such a combination of technical solutions does not exist and is not within the scope of protection required by this application. It can be understood that in the technical solution of this application, the acquisition, collection, storage, use, processing, transmission, provision, disclosure and application of data are all in compliance with the provisions of relevant laws and regulations. It should be noted that in the embodiments of the present application, some existing solutions in the industry such as software, components, models, etc. may be mentioned, and they should be considered as exemplary. Their purpose is only to illustrate the feasibility of the implementation of the technical solution of this application, but it does not mean that the applicant has or must use the solution.

[0048] At present, the existing reconciliation processing mechanism does not uniformly manage various reconciliation modes, but adopts the reconciliation type configuration method to achieve it. That is, the existing technology couples the reconciliation sending and data processing together. When sending the reconciliation message, the corresponding reconciliation type is queried according to the division code, and the reconciliation template is generated in real time, the reconciliation details data are calculated, and then the reconciliation data is sent. In this way, during the system iteration process, if a new reconciliation mode is generated, a new code branch needs to be written, which makes the system scalability poor. At the same time, a large number of code branches will greatly increase the management and operation and maintenance costs of the system. At the same time, in the existing technology, the high coupling of reconciliation sending and reconciliation details data processing will also reduce the fault tolerance of the system. At the same time, data processing must be performed every time reconciliation data is sent, which reduces the processing efficiency of the system and greatly increases the system overhead.

[0049] In order to solve the above problems, Figure 1 As shown, in a first aspect of the present application, a method for processing reconciliation data is provided, comprising:

[0050] S100, in response to the received transaction flow data, obtaining transaction flow information of the transaction flow data, and determining the reconciliation category and reconciliation identification information of the transaction flow data according to the transaction flow information;

[0051] S200, calling a corresponding target reconciliation template based on the reconciliation category, generating reconciliation information of the transaction flow data based on the transaction flow data and the target reconciliation template, and writing the reconciliation information of the transaction flow data into a reconciliation information table corresponding to the reconciliation category, wherein the reconciliation information table includes different reconciliation information of the same reconciliation category;

[0052] S300 . In response to the reconciliation data sending instruction, obtain reconciliation information having the same reconciliation identification information from all reconciliation information tables, and send all the obtained reconciliation information to the target reconciliation platform corresponding to the current reconciliation identification information.

[0053] In this way, the present application constructs different reconciliation templates in advance according to different reconciliation categories, and calls the corresponding reconciliation templates to generate reconciliation information based on different reconciliation categories corresponding to different transaction flows during the day. At the end of the day, all the generated reconciliation information is sent to different reconciliation channels according to the reconciliation identifier. By decoupling the reconciliation data processing and the reconciliation data sending, the processing efficiency of the reconciliation data is effectively improved.

[0054] As you can understand, reconciliation types usually fall into the following categories:

[0055] 2555: Transaction reconciliation message, reflecting the daily confirmation information of all acquiring transactions of the acquiring institution;

[0056] 5555: Transaction flow reconciliation result message, reflecting the reconciliation result of all daily acquiring transaction confirmation information of the acquiring institution;

[0057] 2557: Receipt funds reconciliation message, reflecting the daily receipt information of all funds of the beneficiary bank;

[0058] 5557: Message of reconciliation result of funds received, reflecting the reconciliation result of all funds received by the beneficiary bank on a daily basis;

[0059] 2556: Account funds reconciliation message, reflecting the bank's daily financial account income and expenditure details;

[0060] 5556: Account funds reconciliation result message, reflecting the reconciliation results of the revenue and expenditure details of each financial account;

[0061] 2581: Unit supervision account income and expenditure balance message, reflecting the income and expenditure details of each collection unit account under financial supervision.

[0062] After the transaction flow data generated by various transactions during the day, such as payment, clearing, payment to the treasury, incoming account and virtual account payment, are stored in real time, this application is based on the Quartz framework, that is, the framework for starting the scheduled task, and generates the processing threads of the above five types of reconciliation data through the Quartz asynchronous task. At the same time, according to the signed contract account division information and the reconciliation template corresponding to the division, it generates reconciliation data information including division, pre-position, reconciliation date, account number and flow details, and establishes reconciliation data detail tables of four reconciliation categories 2555, 2556, 2557 and 2581 to record the reconciliation data; because some regions require the reconciliation data to be sent according to the division, and some regions require it to be sent according to the pre-position, therefore, at the end of the day, through the four types of reconciliation day-end scheduled tasks, according to the non-tax electronic contract query, the division or pre-position of the reconciliation data to be sent, the reconciliation data detail table is directly read according to the division or pre-position, and the reconciliation data is sent to the corresponding reconciliation agency. It can be understood that the division refers to the geographical or administrative area, and the prefix refers to the financial institution or financial system. For example, the division can be "XX City" and the prefix can be "XX Bank XX Branch" and so on.

[0063] Specifically, in step S100, after receiving a transaction flow data, the transaction flow information of the transaction flow data is first obtained, wherein the transaction flow information includes the transaction flow number, transaction amount, transaction account, transaction time, transaction category and regional information, etc., and then the reconciliation category of the current transaction flow data is determined according to the transaction category, and the reconciliation identification information of the current transaction flow data is determined according to the regional information. For example, the transaction flow information of a transaction flow data includes: the flow number, the arrival time, the arrival amount, the receiving account, the transaction status and other fields, then the transaction category can be judged as arrival according to the arrival amount, the arrival time and other fields, and the corresponding reconciliation category is 2557. It can be understood that the transaction category of the transaction flow is determined in the prior art, and this is not limited here.

[0064] In step S100, the reconciliation category of the transaction flow data is determined according to the transaction flow information, including: determining the reconciliation category of the transaction flow data according to the transaction category based on a pre-constructed reconciliation category matching table, wherein the reconciliation category matching table includes reconciliation categories corresponding to different transaction categories. A mapping relationship table between different transaction categories and corresponding reconciliation categories is pre-constructed, wherein the transaction category can also be represented by a corresponding field in the transaction flow information, for example, a combination of one or more of the fields such as receipt, payment, income, and expenditure is associated with the corresponding reconciliation category.

[0065] It is understandable that when reconciling transaction flow data, the reconciliation agency can be determined based on the area where the transaction flow is generated, or the reconciliation agency can be determined based on the account opening area where the transaction flow is generated. Therefore, in this application, the regional information includes the generation area information of the transaction flow data or the account opening area information of the transaction account associated with the transaction flow data, which is not limited here. In step S100, the reconciliation identification information of the transaction flow data is determined based on the transaction flow information, including: based on the pre-constructed reconciliation identification information matching table, the reconciliation identification information and the target reconciliation platform of the transaction flow data are determined based on the regional information, and the reconciliation identification information matching table includes the reconciliation identification information corresponding to different regional information, and the target reconciliation platform corresponding to different reconciliation identification information. It is understandable that different regions usually have different requirements for reconciliation. Usually, some regions require the reconciliation data to be sent according to the division, while some regions require the reconciliation data to be sent according to the pre-information. Therefore, the reconciliation identification information corresponding to different regional information can be pre-established according to the different requirements of different regions. For example, regions A, C, and D require reconciliation data to be sent according to the zoning, and regions B and E require reconciliation data to be sent according to the pre-information. Then, the first-level reconciliation identification information corresponding to the transaction flow of the region information A, C, and D is configured as reconciliation identification information 1, and the first-level reconciliation identification information corresponding to the transaction flow of the region information B and E is configured as reconciliation identification information 2. Furthermore, the reconciliation platforms corresponding to regions A, B, C, D, and E are reconciliation platform A, reconciliation platform B, reconciliation platform C, reconciliation platform D, and reconciliation platform E, respectively. Then, the region information is configured as The secondary reconciliation identification information corresponding to the transaction flows with domain information A, C, and D are reconciliation identification information 1A, reconciliation identification information 1C, and reconciliation identification information 1D, respectively. Mapping relationships are established between reconciliation identification information 1A, reconciliation identification information 1C, and reconciliation identification information 1D and reconciliation platforms A, C, and D, respectively. Similarly, the secondary reconciliation identification information corresponding to the transaction flows with configuration area information B and E are reconciliation identification information 2B and 2E, respectively. Mapping relationships are established between 2B and 2E and reconciliation platforms B and E, respectively.

[0066] In order to uniformly manage different reconciliation modes, this application pre-establishes reconciliation template sets corresponding to four reconciliation categories, namely 2555, 2556, 2557 and 2581, wherein each reconciliation template set includes at least one general reconciliation template belonging to the reconciliation category, and at least one non-general reconciliation template belonging to the reconciliation category. It can be understood that, usually, the reconciliation templates in most regions are universal, but some regions have special requirements for the sending of reconciliation data. Therefore, corresponding non-general reconciliation templates are pre-established for some regions with special requirements. That is, the reconciliation template set includes general reconciliation templates belonging to the same reconciliation category and at least one non-general reconciliation template that matches information of different regions, wherein each reconciliation category corresponds to a reconciliation template set. For example, taking the reconciliation category 2555 as an example, the reconciliation rules for region A, region B and Pos transactions are different from the general templates. The difference between the general template and the non-general template is shown in the following table:

[0067] Table 1

[0068]

[0069] The reconciliation template set with reconciliation category 2556 can include the following reconciliation templates:

[0070] Financial Software 1:

[0071] Clearing branch mode 1 (payment income flow, refund flow, clearing income flow, clearing outflow flow, payment to the treasury expenditure flow, unidentified income flow, unidentified expenditure flow);

[0072] Agent bank model 1 (payment income flow, refund flow, unknown income flow);

[0073] Correspondent bank model 2 (payment income flow, refund flow, sub-account income flow);

[0074] Agent bank model 3 (payment income flow, refund flow, clearing income flow, clearing outflow flow, payment to treasury expenditure flow, unidentified income flow, unidentified expenditure flow);

[0075] Detailed reconciliation mode (payment income flow, refund flow, third-party detailed flow, sub-account income flow);

[0076] Financial Software 2:

[0077] Clearing branch mode 2 (payment income flow, refund flow, clearing income flow, clearing outflow flow, payment to the treasury expenditure flow, unidentified income flow, unidentified expenditure flow, virtual account income flow, original return expenditure flow);

[0078] Agent bank model 4 (payment income flow, clearing income flow, clearing outflow flow, payment to the treasury expenditure flow, unknown income flow excluding collection, unknown expenditure flow, virtual account income flow, original return expenditure flow);

[0079] Agent bank model 5 (payment income flow, refund flow, clearing income flow, clearing outflow flow, payment to treasury expenditure flow, unidentified income flow, unidentified expenditure flow, virtual account income flow, original return expenditure flow, remarks and special rules for batch numbers).

[0080] Among them, the clearing branch mode is a general template, and different agent bank modes correspond to different reconciliation rules. For example, if region A requires agent bank mode 5 for reconciliation, when generating reconciliation information, if the current transaction data belongs to region A, the reconciliation template of agent bank mode 5 needs to be called to generate reconciliation information. Clearing branch mode 1 and clearing branch mode 2 can be general reconciliation templates of different existing financial software, and agent bank mode or region mode can be different regional numbers.

[0081] The reconciliation template set with reconciliation category 2557 can include the following reconciliation templates:

[0082] Financial Software 1:

[0083] Clearing Branch:

[0084] General mode 1 (payment income flow, third-party detailed flow);

[0085] Regional model 1 (payment income flow, third-party detailed flow (excluding #Z batch number data));

[0086] Agent bank model 1 (payment income flow, third-party detailed flow (including main account and sub-account)).

[0087] Financial Software 2:

[0088] Regional model 2 (payment income flow, clearing income flow, payment income flow, unknown income flow);

[0089] General mode 2 (payment income flow, clearing income flow, payment to the treasury income flow, unknown income flow, virtual account income flow);

[0090] Regional mode 3 (payment income flow, clearing income flow, payment income flow, unknown income flow, virtual account income flow), fetching flow data by natural day;

[0091] Regional model 4 (payment income flow (only includes successfully collected flow), clearing income flow, payment income flow, unknown income flow, virtual account income flow);

[0092] Regional model 5 (payment income flow, clearing income flow, payment to the treasury income flow, unknown income flow (excluding sub-account flow), virtual account income flow).

[0093] Different reconciliation template adapters are pre-built for different reconciliation categories. When asynchronously processing reconciliation flow data during the day, the corresponding reconciliation template adapter is used to select the corresponding reconciliation mode according to the district code to process the reconciliation flow of the district. Taking the reconciliation category 2557 as an example, the reconciliation processing flow is as follows Figure 2 shown.

[0094] Then, in step S200, calling the corresponding target reconciliation template based on the reconciliation category includes: determining the reconciliation template set corresponding to the reconciliation category based on the reconciliation category; determining the reconciliation template matching the regional information in the reconciliation template set as the target reconciliation template based on the regional information. Determining the reconciliation template matching the regional information in the reconciliation template set as the target reconciliation template based on the regional information includes: querying whether the reconciliation template set includes a non-universal reconciliation template matching the regional information based on the regional information; if there is a non-universal reconciliation template matching the regional information in the reconciliation template set, determining the non-universal reconciliation template as the target reconciliation template; if there is no non-universal reconciliation template matching the regional information in the reconciliation template set, determining the universal reconciliation template in the reconciliation template set as the target reconciliation template. For example, if the regional information of the current transaction flow data is determined to be region A and the reconciliation category is 2557 based on the current transaction flow information, then querying whether there is a reconciliation template numbered region A from the template set of 2557, if so, calling the template, if not, calling the universal template. After calling the corresponding reconciliation template, the reconciliation information of the current transaction flow data is generated according to the reconciliation template, and written into the reconciliation information table of the corresponding reconciliation category. It can be understood that each reconciliation category corresponds to a reconciliation information table, and a new reconciliation information table is generated every day to record the reconciliation information of the day.

[0095] like Figure 3As shown, in this application, all reconciliation details are generated during the day, and at the end of the day, it is only responsible for completing the sending of reconciliation data. Specifically, a Quartz task is established to asynchronously process the reconciliation sending task, select all non-tax electronic contracts for signed divisions, and select the detailed data that needs to be sent for reconciliation from the generated reconciliation information according to the division. If there is no detailed data to be sent, an empty package is generated; at the same time, the reconciliation data is monitored through the pre-built Quartz task to check whether there are divisions with transactions but no reconciliation data generated. For non-empty package data sending, the reconciliation data is checked by division, the reconciliation sending record is generated and the reconciliation sending task is executed; for empty package data, the empty package reconciliation task is uniformly executed to generate an empty package sending record. At the same time, after sending the reconciliation data, a receipt is received from the reconciliation platform, and the reconciliation sending result is updated according to the receipt. If the receipt fails, the updated receipt status and the reconciliation result status are both failed.

[0096] In step S300, the reconciliation data sending instruction may be a day-end reconciliation instruction, which is a timed instruction triggered at a fixed time every day. When sending reconciliation information, according to different reconciliation categories, reconciliation information with the same reconciliation identification information in different reconciliation categories is sent to the corresponding reconciliation agency. Figure 4 As shown, after sending the reconciliation information, the method of the present application also includes: receiving a reconciliation result message from the target reconciliation platform, and writing the received reconciliation result message into a reconciliation result record table, wherein the reconciliation result message is generated by the target reconciliation platform after reconciling the reconciliation information sent to the target reconciliation platform, and the reconciliation result message includes verification information of successful or failed reconciliation, and in the reconciliation result record table, the same reconciliation results of different package serial numbers are regarded as the same batch of reconciliation data of different sending records, or different reconciliation data of different sending records; at the end of the day, determining that the verification information of the reconciliation result message in the reconciliation result record table is the number of reconciliation results of failed reconciliation, and if the number of reconciliation results is greater than a preset threshold, generating an alarm message; the present application also uses a Quartz task to find the corresponding reconciliation data and sending records according to the received reconciliation results to update the reconciliation result record table.

[0097] This application also provides a reconciliation query function. Specifically, it can realize the query of reconciliation sending records and the query of reconciliation details. At the same time, it provides the functions of reconciliation data regeneration and reconciliation retransmission. Among them, the reconciliation data regeneration function is to deal with the situation where the reconciliation details data is abnormal and the reconciliation details data needs to be regenerated after adjusting the original transaction data; secondly, after the reconciliation details data is generated, select reconciliation to send the reconciliation message according to the latest generated details data.

[0098] like Figure 5 As shown, in a second aspect of the present application, a reconciliation data processing device is provided, comprising:

[0099] A data collection module is configured to obtain transaction flow information of the transaction flow data in response to the received transaction flow data, and determine the reconciliation category and reconciliation identification information of the transaction flow data according to the transaction flow information;

[0100] a reconciliation information generation module configured to call a corresponding target reconciliation template based on a reconciliation category, generate reconciliation information of the transaction flow data based on the transaction flow data and the target reconciliation template, and write the reconciliation information of the transaction flow data into a reconciliation information table corresponding to the reconciliation category, wherein the reconciliation information table includes different reconciliation information having the same reconciliation category;

[0101] The reconciliation information sending module is configured to obtain reconciliation information with the same reconciliation identification information from all reconciliation information tables in response to the reconciliation data sending instruction, and send all the obtained reconciliation information to the target reconciliation platform corresponding to the current reconciliation identification information.

[0102] It should be noted that it should be understood that the division of the various modules of the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. And these modules can all be implemented in the form of software called by processing elements; they can also be all implemented in the form of hardware; some modules can also be implemented in the form of software called by processing elements, and some modules can be implemented in the form of hardware. For example, the data acquisition module can be a separately established processing element, or it can be integrated in a chip of the above device. In addition, it can also be stored in the memory of the above device in the form of program code, and called and executed by a processing element of the above device. The function of the above data acquisition module. The implementation of other modules is similar. In addition, all or part of these modules can be integrated together, or they can be implemented independently. The processing element here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each module above can be completed by an integrated logic circuit of hardware in the processor element or instructions in the form of software.

[0103] According to a third aspect of the present application, an electronic device is provided, comprising: a processor, and a memory communicatively connected to the processor;

[0104] The memory stores computer-executable instructions;

[0105] The processor executes the computer-executable instructions stored in the memory to implement the above method.

[0106] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Figure 6 As shown, the electronic device may include: a transceiver 121 , a processor 122 , and a memory 123 .

[0107] The processor 122 executes the computer execution instructions stored in the memory, so that the processor 122 executes the scheme in the above embodiment. The processor 122 can be a general-purpose processor, including a central processing unit CPU, a network processor (network processor, NP), etc.; it can also be a digital signal processor DSP, an application-specific integrated circuit ASIC, a field programmable gate array FPGA or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.

[0108] The memory 123 is connected to the processor 122 via a system bus and completes communication between them. The memory 123 is used to store computer program instructions.

[0109] The transceiver 121 may be used to obtain tasks to be executed and configuration information of the tasks to be executed.

[0110] The system bus can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The system bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus. The transceiver is used to realize the communication between the database access device and other computers (such as clients, read-write libraries, and read-only libraries). The memory may include random access memory (RAM) and may also include non-volatile memory.

[0111] The electronic device provided in the embodiment of the present application may be the terminal device of the above embodiment.

[0112] In a fourth aspect of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to implement the above-mentioned method when executed by a processor.

[0113] In a fifth aspect of the present application, a computer program product is provided, including a computer program, which implements the above method when executed by a processor.

[0114] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

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

Claims

1. A method for processing reconciliation data, characterized in that: include: In response to the received transaction flow data, acquiring transaction flow information of the transaction flow data, and determining the reconciliation category and reconciliation identification information of the transaction flow data according to the transaction flow information; Based on the reconciliation category, a corresponding target reconciliation template is called, reconciliation information of the transaction flow data is generated based on the transaction flow data and the target reconciliation template, and the reconciliation information of the transaction flow data is written into a reconciliation information table corresponding to the reconciliation category, wherein the reconciliation information table includes different reconciliation information with the same reconciliation category; In response to the reconciliation data sending instruction, reconciliation information with the same reconciliation identification information is obtained from all reconciliation information tables, and all the obtained reconciliation information is sent to the target reconciliation platform corresponding to the current reconciliation identification information.

2. The method for processing reconciliation data according to claim 1, characterized in that: The transaction flow information includes: Transaction serial number, transaction amount, transaction account, transaction time, transaction category and region information; Determining the reconciliation category of the transaction flow data according to the transaction flow information includes: Based on a pre-constructed reconciliation category matching table, the reconciliation category of the transaction flow data is determined according to the transaction category, and the reconciliation category matching table includes reconciliation categories corresponding to different transaction categories.

3. The method for processing reconciliation data according to claim 2, characterized in that: The area information includes the generation area information of the transaction flow data or the account opening area information of the transaction account associated with the transaction flow data; Determining the reconciliation identification information of the transaction flow data according to the transaction flow information includes: Based on a pre-constructed reconciliation identification information matching table, the reconciliation identification information and the target reconciliation platform of the transaction flow data are determined according to the regional information. The reconciliation identification information matching table includes the reconciliation identification information corresponding to different regional information, and the target reconciliation platform corresponding to different reconciliation identification information.

4. The method for processing reconciliation data according to claim 2, characterized in that: Calling a corresponding target reconciliation template based on the reconciliation category includes: Determining a reconciliation template set corresponding to the reconciliation category based on the reconciliation category, the reconciliation template set including different reconciliation templates belonging to the same reconciliation category, wherein each reconciliation category corresponds to one reconciliation template set; Based on the regional information, a reconciliation template in the reconciliation template set that matches the regional information is determined as the target reconciliation template.

5. The method for processing reconciliation data according to claim 4, characterized in that: Different reconciliation templates belonging to the same reconciliation category, including: Universal reconciliation templates belonging to the same reconciliation category and at least one non-universal reconciliation template matching information in different regions; Determining, based on the regional information, a reconciliation template in the reconciliation template set that matches the regional information as the target reconciliation template includes: Based on the regional information, query whether the reconciliation template set includes a non-universal reconciliation template matching the regional information; If a non-universal reconciliation template matching the regional information exists in the reconciliation template set, determining the non-universal reconciliation template as the target reconciliation template; If there is no non-universal reconciliation template matching the regional information in the reconciliation template set, a universal reconciliation template in the reconciliation template set is determined as the target reconciliation template.

6. The method for processing reconciliation data according to claim 1, characterized in that: The method further comprises: Receiving a reconciliation result message from the target reconciliation platform, and writing the received reconciliation result message into a reconciliation result record table, wherein the reconciliation result message is generated by the target reconciliation platform after reconciling the reconciliation information sent to the target reconciliation platform, and the reconciliation result message includes verification information of reconciliation success or reconciliation failure; The verification information of the reconciliation result message in the reconciliation result record table is determined to be the number of reconciliation results that failed to be reconciled, and if the number of reconciliation results is greater than a preset threshold, an alarm message is generated.

7. A reconciliation data processing device, characterized in that: include: A data collection module is configured to obtain transaction flow information of the transaction flow data in response to the received transaction flow data, and determine the reconciliation category and reconciliation identification information of the transaction flow data according to the transaction flow information; a reconciliation information generating module, configured to call a corresponding target reconciliation template based on the reconciliation category, generate reconciliation information of the transaction flow data based on the transaction flow data and the target reconciliation template, and write the reconciliation information of the transaction flow data into a reconciliation information table corresponding to the reconciliation category, wherein the reconciliation information table includes different reconciliation information of the same reconciliation category; The reconciliation information sending module is configured to obtain reconciliation information with the same reconciliation identification information from all reconciliation information tables in response to the reconciliation data sending instruction, and send all the obtained reconciliation information to the target reconciliation platform corresponding to the current reconciliation identification information.

8. An electronic device, characterized in that: include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 6 when executed by a processor.

10. A computer program product, characterized in that The invention comprises a computer program, which implements the method according to any one of claims 1 to 6 when being executed by a processor.

Images