Resource data checking method and device, equipment and storage medium

Abstract

The invention discloses a resource data checking method and device, equipment and a storage medium, and the method comprises the steps: creating a target checking item in response to a resource data checking request; in response to a configuration operation on the target check item, obtaining item configuration information; obtaining task configuration information of each target task in response to a configuration operation on the plurality of target tasks; determining a task script corresponding to each target task according to the item type and each task type; the task script comprises a resource data pulling script corresponding to a resource data pulling task, a resource data type identification script corresponding to a resource data type identification task and a resource data checking script corresponding to a resource data checking task; sequentially executing the resource data pulling script, the resource data type identification script and the resource data checking script according to the execution cycle to obtain a data checking result; according to the method, resource data checking can be flexibly and conveniently carried out, and the data checking efficiency is effectively improved.

Description

Technical Field

[0001] This application belongs to the field of computer technology, and particularly relates to a method, device, equipment and storage medium for resource data reconciliation. Background Art

[0002] With the continuous development of electronic payment, the transaction channels connected by the payment platform are increasing continuously. For example, multiple bank channels are connected, and the business scenarios are also different, such as cash withdrawal, remittance return, payment addition, exchange, etc. In order to ensure the correctness of transactions and funds, the reconciliation process needs to be carried out among the participating parties of resource data in various business scenarios. However, the data sources and data formats of the reconciliation participating parties in external channels are complex and changeable, resulting in the reconciliation logic becoming more complex.

[0003] The existing reconciliation method is a hard-coded method, that is, a new set of reconciliation codes needs to be written for the reconciliation requirements in each business scenario, and then tested and put into use. Therefore, the data reconciliation efficiency is low. And if the data format of the external channel changes, the reconciliation will fail and manual reconciliation is required, which affects the data reconciliation efficiency.

[0004] Therefore, how to perform resource data reconciliation flexibly and conveniently and improve the data reconciliation efficiency is a technical problem to be solved urgently. Summary of the Invention

[0005] This application provides a method, device, equipment and storage medium for resource data reconciliation, which can perform resource data reconciliation flexibly and conveniently and improve the data reconciliation efficiency.

[0006] On the one hand, an embodiment of this application provides a method for resource data reconciliation, and the method includes:

[0007] Respond to a resource data reconciliation request and create a target reconciliation item;

[0008] Respond to a configuration operation on the target reconciliation item and obtain item configuration information; the item configuration information includes the item type and execution period of the target reconciliation item; the target reconciliation item includes multiple target tasks;

[0009] Respond to a configuration operation on multiple target tasks and obtain the task configuration information of each target task; the task configuration information includes the task type of each target task;

[0010] Determine a task script corresponding to each target task according to the item type and each task type; the task script includes a resource data pulling script corresponding to a resource data pulling task, a resource data type identification script corresponding to a resource data type identification task, and a resource data reconciliation script corresponding to a resource data reconciliation task;

[0011] Execute the resource data pulling script, the resource data type identification script, and the resource data verification script in sequence according to the execution cycle to obtain a data verification result.

[0012] In an exemplary embodiment, the step of executing the resource data pulling script, the resource data type identification script, and the resource data verification script in sequence according to the execution cycle to obtain a data verification result includes:

[0013] In each execution cycle, obtain the execution time point of the resource data pulling task;

[0014] When the execution time point is reached, use the resource data pulling script to pull local resource data and peer resource data, and store the local resource data and the peer resource data into a verification data table;

[0015] Use the resource data type identification script to perform category label annotation processing on the resource data in the verification data table to obtain resource category labels;

[0016] Use the resource data verification script to perform data verification processing on the resource data with target resource category labels in the verification data table to obtain the data verification result.

[0017] In an exemplary embodiment, the step of using the resource data pulling script to pull local resource data and peer resource data, and storing the local resource data and the peer resource data into a verification data table includes:

[0018] Pull local resource data from the local business database;

[0019] Determine the peer data pulling method according to the peer data source address;

[0020] Download the peer resource data from the peer data source address according to the peer data pulling method;

[0021] Store the local resource data and the peer resource data into the verification data table.

[0022] In an exemplary embodiment, the step of using the resource data type identification script to perform category label annotation processing on the resource data in the verification data table to obtain resource category labels includes:

[0023] Obtain a category label comparison table; the category label comparison table includes multiple preset resource category labels and description information corresponding to the multiple preset resource category labels;

[0024] Obtain the field names of the resource data in the verification data table;

[0025] Determine the preset description information that matches the field name from the described information according to the preset tag matching strategy;

[0026] Determine the resource category tag of the resource data according to the corresponding relationship between the description information and the preset resource category tag in the category tag table.

[0027] In an exemplary embodiment, the data verification process of using the resource data verification script to verify the resource data with the target resource category tag in the verification data table to obtain the data verification result includes:

[0028] Obtain the target resource category tag; the target resource category tag includes at least one local target resource category tag and at least one peer target resource category tag;

[0029] Filter out the local target data set from the verification data table according to the at least one local target resource category tag, and filter out the peer target data set from the verification data table according to the at least one peer target resource category tag;

[0030] Compare the local target data set and the peer target data set to obtain the data verification result.

[0031] In an exemplary embodiment, when the resource data verification task is an exact verification task, the comparison of the local target data set and the peer target data set to obtain the data verification result includes:

[0032] Compare the attribute data of the target data with the same identification field in the local target data set and the peer target data set to obtain the data verification result;

[0033] When the resource data verification task is fuzzy verification, the comparison of the local target data set and the peer target data set to obtain the data verification result includes:

[0034] Determine the data verification result according to the total amount of resources and the resource transfer direction of the local target data set and the total amount of resources and the resource transfer direction of the peer target data set.

[0035] In an exemplary embodiment, the comparison of the local target data set and the peer target data set to obtain the data verification result includes:

[0036] Obtain a historical abnormal resource data set; the historical abnormal resource data set is a set formed by resource data indicating inconsistent data comparison in the data comparison results during a preset historical period; the historical abnormal resource data set includes a local historical abnormal resource data set and a peer historical abnormal resource data set;

[0037] Compare the local target data set and the peer target data set to obtain initial local multi-account data and initial peer multi-account data;

[0038] Compare the initial local multi-account data with the peer historical abnormal resource data set to obtain a first comparison result, and update the peer historical abnormal resource data set according to the first comparison result;

[0039] Compare the initial peer multi-account data with the local historical abnormal resource data set to obtain a second comparison result, and update the local historical abnormal resource data set according to the second comparison result;

[0040] Obtain the data comparison result according to the first comparison result and the second comparison result.

[0041] In an exemplary embodiment, the target task further includes a difference processing task. After obtaining the data comparison result, the method further includes:

[0042] Count the abnormal resource data indicating inconsistent data comparison in the data comparison result;

[0043] Determine a difference processing strategy according to the difference type of the abnormal resource data;

[0044] In response to the confirmation operation of the difference processing strategy, perform difference processing on the abnormal resource data according to the difference processing strategy, and form a difference processing record.

[0045] In an exemplary embodiment, the method further includes:

[0046] Create a first thread pool corresponding to the resource data pulling task, a second thread pool corresponding to the resource data type recognition task, and a third thread pool corresponding to the resource data comparison task;

[0047] For each of the target tasks, determine a target thread pool from the first thread pool, the second thread pool, and the third thread pool according to the task type of the target task;

[0048] Call the target thread pool to execute the task script corresponding to the target task.

[0049] On the other hand, the present application also provides a resource data comparison device, and the device includes:

[0050] A project creation module, configured to create a target verification project in response to a resource data verification request;

[0051] A project configuration module, configured to obtain project configuration information in response to a configuration operation on the target verification project; the project configuration information includes the project type and execution period of the target verification project; the target verification project includes a plurality of target tasks;

[0052] A task configuration module, configured to obtain task configuration information for each of the plurality of target tasks in response to a configuration operation on the plurality of target tasks; the task configuration information includes the task type of each target task;

[0053] A task script determination module, configured to determine a task script corresponding to each target task according to the project type and each task type; the task script includes a resource data pulling script corresponding to a resource data pulling task, a resource data type identification script corresponding to a resource data type identification task, and a resource data verification script corresponding to a resource data verification task;

[0054] A script execution module, configured to sequentially execute the resource data pulling script, the resource data type identification script, and the resource data verification script according to the execution period to obtain a data verification result.

[0055] On the other hand, the present application also provides an electronic device, which includes a processor and a memory. At least one instruction or at least one program segment is stored in the memory, and the at least one instruction or the at least one program segment is loaded and executed by the processor to implement the resource data verification method as described above.

[0056] On the other hand, the present application also provides a computer storage medium, which stores at least one instruction or at least one program segment, and the at least one instruction or at least one program segment is loaded and executed by a processor to implement the resource data verification method as described above.

[0057] On the other hand, the present application also provides a computer program product or a computer program. The computer program product or the computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes to implement the resource data verification method as described above.

[0058] The resource data verification method provided by the present application has the following technical effects:

[0059] In an embodiment of the present application, in response to a resource data verification request, a target verification item is created; then, in response to a configuration operation on the target verification item, project configuration information is obtained; the target verification item includes multiple target tasks. Subsequently, a financial staff member can configure the target tasks, and then, in response to a configuration operation on the multiple target tasks, task configuration information for each target task is obtained; according to the project type and each task type, a task script corresponding to each target task is determined; then, the task scripts corresponding to the target tasks are sequentially executed according to the execution period, including a resource data pulling script, a resource data type identification script, and a resource data verification script, thereby obtaining a data verification result. Through the dynamic configuration of the target verification item and the target tasks, the script writing time before resource data verification can be saved. When docking with a new channel, reconciliation can be quickly achieved through configuring the project; when the data format of the reconciliation file provided by the already docked channel changes, then reconciliation can be quickly achieved by modifying the task configuration of the relevant tasks in the corresponding project; compared with the hard-coding method in the traditional solution, the present application does not need to rewrite the reconciliation code every time a new channel is docked or the reconciliation file changes. Therefore, resource data verification can be carried out flexibly and conveniently, effectively improving the data verification efficiency. Brief Description of the Drawings

[0060] To more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings required for use in the embodiments or the description of the prior art. Obviously, the following-described drawings are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0061] Figure 1 is an application environment diagram of the resource data verification method provided by the embodiment of the present application;

[0062] Figure 2 is a flowchart of the resource data verification method provided by the embodiment of the present application;

[0063] Figure 3 is a schematic diagram of the project configuration page provided by the embodiment of the present application;

[0064] Figure 4 is a schematic diagram of the task configuration page provided by the embodiment of the present application;

[0065] Figure 5 is a flowchart of the script execution process provided by the embodiment of the present application;

[0066] Figure 6 is a flowchart of the data comparison of the target data set provided by the embodiment of the present application;

[0067] Figure 7It is a schematic diagram of the process nodes for resource data verification provided by an embodiment of the present application;

[0068] Figure 8 It is a schematic structural diagram of a resource data verification device provided by an embodiment of the present application;

[0069] Figure 9 It is a hardware structure block diagram of a server for a resource data verification method provided by an embodiment of the present application. Detailed implementation manners

[0070] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0071] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above accompanying drawings are used to distinguish similar objects, and do not necessarily need to be used to describe a specific order or sequence. It should be understood that such data can be interchanged under appropriate circumstances so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or server including a series of steps or units does not necessarily have to be limited to those clearly listed steps or units, but may include other steps or units not clearly listed or inherent to these processes, methods, products, or devices.

[0072] Figure 1 It is an application environment diagram of a resource data verification method provided by an embodiment of the present application.

[0073] As Figure 1 shown, the application environment may at least include a server 01 and a terminal device 02.

[0074] In an optional embodiment, the server 01 may be used to create a target verification item in response to a resource data verification request sent by the terminal device 02, determine a task script according to the item configuration information and the task configuration information, and execute the task script to complete the verification of the resource data. The server 01 may be an independent physical server, or a server cluster or a distributed system composed of multiple physical servers, or a cloud server providing cloud computing services.

[0075] In an optional embodiment, the terminal device 02 can be used to display a configuration page for financial personnel to perform project configuration operations and task configuration operations on the configuration page. The terminal device 02 can also receive and display the data verification result of the server 01. Specifically, the terminal device 02 can include, but is not limited to, electronic devices such as smartphones, desktop computers, tablet computers, laptop computers, smart speakers, digital assistants, augmented reality (AR) / virtual reality (VR) devices, smart wearable devices, vehicle-mounted terminals, smart TVs, etc.; it can also be software running on the above-mentioned electronic devices, such as application programs, applets, etc. The operating systems running on the electronic devices in the embodiments of the present application can include, but are not limited to, Android system, IOS system, linux, windows, etc.

[0076] Figure 2 It is a schematic flowchart of the resource data verification method provided by the embodiments of the present application. As Figure 2 shown, the method includes the following steps.

[0077] S201: In response to a resource data verification request, create a target verification item;

[0078] The resource data verification request can be initiated by Figure 1 the click operation of the financial personnel on the terminal device 02 as shown. One external channel corresponds to multiple account numbers and currencies, and each pair of account numbers and currencies can correspond to a verification item. For example, when a transaction in euros for account number 111 is newly added under channel AAA, the financial personnel click the creation control on the preset page, then a resource data verification request can be generated. In response to this request, a blank verification item can be created and displayed on the terminal device 02 for the financial personnel to configure the verification item according to requirements, realizing the efficient verification of resource data.

[0079] S203: In response to the configuration operation on the target verification item, obtain the project configuration information;

[0080] Among them, the project configuration information includes the project type and execution period of the target verification item;

[0081] In one implementation, after creating the target verification item, it can automatically jump to the project configuration page, and the project configuration page includes multiple project configuration controls. Figure 3 It is a schematic diagram of the project configuration page provided by the embodiments of the present application. As Figure 3As shown in the figure, the project configuration page includes a project type selection control and an execution cycle selection control; in response to a drop-down selection operation on the project type selection control on the project configuration page, the project type of the target reconciliation project is obtained; in response to a drop-down selection operation on the execution cycle selection control on the project configuration page, the execution cycle of the target reconciliation project is obtained. Among them, the project type is used to represent the reconciliation scenario, which can include: various types such as fund reconciliation, fund balance reconciliation, merchant balance reconciliation, and inter-system reconciliation; the execution cycle can be represented by natural days (D), working days (T), weeks (W), and months (M), for example, 1D, 1T, etc.

[0082] The project configuration page may further include: a project name input control, a reconciliation time zone selection control, and a holiday location selection control; the project name input control is used to obtain the project name configured by the financial staff. In one implementation, each target reconciliation project can be named in the way of channel code_account number_currency. For example, "AAA_111_EUR" means to reconcile the euro with the channel code of AAA and the account number of 111. The reconciliation time zone selection control and the holiday location selection control are used to restrict the execution conditions of the reconciliation project. For example, assuming that the execution cycle is every day, and the time zone where the target channel AAA is located is different from the time zone of the payment platform, then the daily reconciliation time needs to be determined according to the time zone where channel AAA is located. And on holidays, channel AAA may not provide a reconciliation file, so the target reconciliation project is not executed on holidays.

[0083] The project configuration page may further include a project parameter configuration control, which is used to receive the public parameters of the target reconciliation project, such as channel code, account number, currency, etc.

[0084] In response to a click operation on the target submission button on the project configuration page, the information provided by all project configuration controls on the project configuration page can be obtained to obtain the project configuration information.

[0085] Furthermore, the target reconciliation project includes multiple target tasks; for example, a resource data pulling task, a resource data type identification task, and a resource data reconciliation task.

[0086] The resource data pulling task, that is, pulling the resource data corresponding to both parties participating in the reconciliation, can be respectively recorded as the local resource data and the counterpart resource data. The local resource data is the data recorded inside the payment platform and can be stored in the business database of the internal system; the counterpart resource data is the reconciliation file data provided by the bank channels docked with the payment platform, etc.

[0087] The resource data category identification task, that is, labeling the resource data to classify the resource data. The labels can be, for example, merchant incoming funds, handling fees, interest, etc.

[0088] A resource data verification task, that is, reconciling resource data according to a preset verification logic.

[0089] S205: In response to a configuration operation on multiple target tasks, obtain the task configuration information of each target task;

[0090] Wherein, the task configuration information includes the task type of each target task;

[0091] In one implementation, after obtaining the project configuration information, it is possible to jump to the task configuration page. The task configuration page includes multiple task configuration controls. Figure 4 It is a schematic diagram of the task configuration page provided by an embodiment of the present application. As Figure 4 shown, the task configuration page includes a task type selection control. In response to a drop-down selection operation on the task type selection control on the task configuration page, obtain the task type of the target task; in one implementation, the task type may include local data pulling, peer data pulling, business type identification, precise reconciliation, fuzzy reconciliation, etc.

[0092] The task configuration page also includes an associated project name selection control, a task name input control, a task level input control, and a retry count input control.

[0093] The associated project name selection control can be used to select under which specific verification project this target task is, so as to achieve binding with the target verification project.

[0094] The task name input control is used to obtain the task name configured by the financial personnel. Taking the task type of local data pulling as an example, the task name can be cash out order acquisition, cash out remittance reversal order acquisition, top-up order acquisition, etc.; taking the task type of peer data pulling as an example, the task name can be fund details acquisition; taking the task type of resource data category identification as an example, the task name can be fund details identification; taking the task type of precise reconciliation as an example, the task name can be incoming funds reconciliation, incoming funds refund / recall refund, cash out reconciliation, etc.; taking the fuzzy reconciliation as an example, the task name can be remittance incoming account reconciliation, remittance outgoing account reconciliation, etc. It should be understood that the above task names are only examples, and the task name can be determined according to the actual input of the financial personnel.

[0095] The task level input control is used to determine the execution order of this target task under the target verification project, and any positive integer can be input. The smaller the value of the task level, the earlier the execution order; for example, the task level of the local data pulling task can be set to 1, and the task level of the resource data category identification task can be set to 2, so that the data pulling task is executed first.

[0096] The retry times input control is used to determine the number of retries supported when a task execution fails. For example, when data pulling fails due to network fluctuations, the data can be pulled again automatically through automatic retries; it should be understood that the specific value of the retry times in this application is not limited.

[0097] The task configuration page also includes an execution time input control, which is used to determine the execution time of the target task. The ISO-8601 time format can be adopted, and different target tasks can be executed at custom times. It should be noted that when the task type is a data pulling task, corresponding time data must be entered in the execution time input control, and for other task types, it is optional.

[0098] The task configuration page also includes a task parameter input control, which is used to input the unique configuration information of the target task. Taking the withdrawal slip acquisition as an example, in addition to configuring task type, execution time and other configuration items, the fund transfer direction, the default label for data annotation after data pulling, and the SQL statement for data pulling can also be entered in the task parameter input control.

[0099] In response to a click operation on the target submit button on the task configuration page, the information provided by all task configuration controls on the task configuration page is obtained to obtain the task configuration information.

[0100] S207: Determine the task script corresponding to each target task according to the project type and each task type;

[0101] Among them, the task script includes a resource data pulling script corresponding to a resource data pulling task, a resource data type identification script corresponding to a resource data type identification task, and a resource data verification script corresponding to a resource data verification task;

[0102] In one implementation, the task script can be written in the Groovy language. Groovy is an agile dynamic language for the Java virtual machine, which allows developers to be more flexible when writing code.

[0103] According to the project configuration information and task configuration information configured and submitted in the above steps, the task script corresponding to each target task can be obtained. Specifically, according to the project type and task type, an initial task script is determined, and then the remaining configuration item information in the project configuration information except the project type and in the task configuration information except the task type is passed as parameters into the initial task script to obtain the task script corresponding to the target task. For the same project type and task type, the execution logic is similar. Therefore, the parts with the same execution logic can be abstracted to obtain a general script, and the corresponding relationship between the project type and the task type is established to obtain a general script library, so that when applying subsequently, the initial task script can be determined from the general script library according to the project type and task type.

[0104] S209: Execute the resource data pulling script, the resource data type identification script, and the resource data verification script in sequence according to the execution period to obtain a data verification result.

[0105] In an embodiment of the present application, in response to a resource data verification request, a target verification project is created; then, in response to a configuration operation on the target verification project, project configuration information is obtained; the target verification project includes multiple target tasks. Subsequently, a financial staff member can configure the target tasks, and then, in response to a configuration operation on the multiple target tasks, task configuration information for each target task is obtained; task scripts corresponding to each target task are determined according to the project type and each task type; then, the task scripts corresponding to the target tasks are executed in sequence according to the execution period, including the resource data pulling script, the resource data type identification script, and the resource data verification script, so as to obtain a data verification result. Through the dynamic configuration of the target verification project and the target tasks, the script writing time before resource data verification can be saved. When docking with a new channel, reconciliation can be quickly realized through configuring the project; when the data format of the reconciliation file provided by the already docked channel changes, reconciliation can be quickly realized by modifying the task configuration of the relevant tasks in the corresponding project; compared with the hard-coded method in the traditional solution, in the present application, there is no need to rewrite the reconciliation code every time a new channel is docked or the reconciliation file changes. Therefore, resource data verification can be carried out flexibly and conveniently, effectively improving the data verification efficiency.

[0106] In one embodiment, the target task further includes a difference handling task. After obtaining the data verification result, the method further includes: counting the abnormal resource data indicating inconsistent data comparison in the data verification result; determining a difference handling strategy according to the difference type of the abnormal resource data; in response to a confirmation operation on the difference handling strategy, performing difference handling on the abnormal resource data according to the difference handling strategy, and forming a difference handling record. The abnormal resource data is the resource data that is not reconciled, which may include the resource data provided by the external channel side or the resource data recorded by the payment platform side, and is determined according to the actual reconciliation result. The difference types of the abnormal resource data may include daily cut-off, exchange daily cut-off, exchange anomaly, return remittance to be processed, recall to be processed, etc. Different difference handling strategies can be preset for different difference types, such as difference ignoring, manual reconciliation, refund backfilling, outgoing remittance return, generating incoming fund anomaly form, generating outgoing fund anomaly form, etc. In an example, assuming that the difference type of the abnormal resource data is less incoming funds during the day, the corresponding difference handling strategy may be to generate an incoming fund anomaly form. After the financial staff member confirms, execute the difference handling script corresponding to the difference handling strategy, and form a difference handling record and save it in the execution log.

[0107] In one implementation, after determining the difference handling strategy, a prompt message may be sent. The prompt message may include the difference handling strategy and the abnormal resource data. The prompt message may be sent in the form of an email, a text message, etc. The present application does not limit the specific form of the prompt message.

[0108] In one implementation, after the difference handling task is completed, a visualization result may also be generated according to the data verification result for financial personnel to perform data analysis and decision-making. Among them, the visualization result includes but is not limited to forms such as a reconciliation dashboard, for example, a daily cut-off dashboard for incoming payments, a daily cut-off dashboard for outgoing payments, and a daily cut-off dashboard for several accounts, which can be generated according to actual needs.

[0109] In the embodiments of the present application, by automatically processing the abnormal resource data to determine the difference handling strategy, the processing efficiency of the subsequent processing of data verification can be improved, and the difference handling strategy can be automatically executed after being confirmed by the financial personnel, which also ensures the accuracy and reliability of the difference handling.

[0110] Figure 5 is a schematic flowchart of the script execution process provided by the embodiments of the present application. As Figure 5 shown, the step of sequentially executing the resource data pulling script, the resource data type identification script, and the resource data verification script according to the execution cycle to obtain a data verification result may include:

[0111] S501: In each execution cycle, obtain the execution time point of the resource data pulling task;

[0112] It should be noted that the execution time point of the resource data pulling task can be parsed from the task configuration information corresponding to the resource data pulling task. Still taking the Figure 4 shown task configuration page as an example, the execution time point can be obtained by obtaining the data provided by the execution time input control on the page.

[0113] S503: When the execution time point is reached, use the resource data pulling script to pull the local resource data and the peer resource data, and store the local resource data and the peer resource data in the verification data table;

[0114] The local resource data may be the resource data recorded inside the payment platform; the peer resource data may be the resource data provided by an external channel. The task configuration information corresponding to the resource data pulling task may also include the peer data source address, which can be configured on the Figure 4 shown task configuration page according to the actual verification requirements. After pulling the local resource data and the peer resource data, all the pulled resource data can be stored to obtain a verification data table, so as to facilitate subsequent tasks such as data type identification and data verification.

[0115] In one embodiment, pulling local resource data and peer resource data by using the resource data pulling script, and storing the local resource data and the peer resource data into a verification data table includes: pulling local resource data from a local service database; determining a peer data pulling method according to a peer data source address; downloading the peer resource data from the peer data source address according to the peer data pulling method; and storing the local resource data and the peer resource data into the verification data table. In this application, the local service database is the database that records resource data inside the payment platform; the local resource data can be pulled from the local service database through a database query statement; the peer resource data can be downloaded by calling the peer data source address provided by an external channel, and the peer data source address can be understood as an interface for a reconciliation file download request. The resource data pulling script in this application supports multiple data pulling methods, including but not limited to Structured Query Language (SQL) query, Hypertext Transfer Protocol (HTTP) interface query, Secure File Transfer Protocol (SFTP) / File Transfer Protocol (FTP) pulling, Object Storage Service (OSS) pulling, etc.

[0116] The resource data pulling script in the embodiment of this application is universal, supports multiple data pulling methods, simplifies the configuration operation of the resource data pulling task, and improves the configuration efficiency.

[0117] S505: Performing category label annotation processing on the resource data in the verification data table by using the resource data type recognition script to obtain a resource category label;

[0118] The resource data type recognition script is written according to a preset labeling logic, and the resource data type recognition scripts for different target verification items are often different. The resource category label is used to identify the meaning of the resource data, so as to determine the actual resource data used for verification in subsequent data verification tasks.

[0119] In one embodiment, the process of using the resource data type recognition script to perform category label annotation processing on the resource data in the verification data table to obtain resource category labels may include: obtaining a category label comparison table; the category label comparison table includes a plurality of preset resource category labels and description information corresponding to the plurality of preset resource category labels; obtaining the field name of the resource data in the verification data table; determining, according to a preset label matching strategy, the preset description information that matches the field name from the description information; and determining the resource category label of the resource data according to the corresponding relationship between the description information and the preset resource category label in the category label table.

[0120] Table 1 is the category label comparison table provided by the application embodiment.

[0121] Table 1

[0122] Resource category label Description information 0 Unknown 1 User recharge, local merchant top-up, incoming funds 10 Remittance (destination currency), channel recharge 100 Remittance withdrawal fee … … 2 User recharge refund, incoming funds (non-international channel), local top-up recall … … 50 Counterparty data 51 Merchant top-up … …

[0123] As shown in Table 1, the resource category label is 1, and its corresponding description information is "user recharge, local merchant top-up, deposit"; the resource category label is 51, and its corresponding description information is "merchant top-up". Since the formats in the reconciliation files given by different external channels often vary, such as txt, csv, xlsx, json, xml, etc., and even for resource data with the same meaning in the reconciliation file, the corresponding field names will also be different. In order to unify the formats, before data verification in this application, all resource data in the verification data table are first labeled according to the field names. The preset matching strategy is pre-set by financial personnel according to actual verification requirements, and includes at least one of the conditions that the field name is equal to or contains a preset character, the field name starts with a preset character, ends with a preset character, etc. In another implementation manner, it is also possible to match according to the field name and the description information, and then determine the resource category label corresponding to the resource data according to the corresponding relationship between the resource category label and the description information in Table 1.

[0124] In the embodiment of this application, by setting up a category label comparison table and according to the preset label matching strategy, it is possible to quickly determine the resource category labels corresponding to all resource data in the verification data table, convert resource data with different data formats and different field names into unified resource data labels, so as to facilitate subsequent data verification using a general data verification script, effectively improving the data verification efficiency and convenience, and eliminating the need to develop and write corresponding data verification scripts specifically due to changes in the resource data format and field names at the opposite end, saving script development time.

[0125] It should be noted that before executing the resource data type recognition script, the execution status of the pre - resource data pulling task can also be checked. When the execution status is successful, the resource data type recognition script in this step is executed.

[0126] S507: Use the resource data verification script to perform data verification processing on the resource data with the target resource category label in the verification data table to obtain the data verification result.

[0127] The target resource category label can be parsed from the task configuration information corresponding to the resource data verification task. In an example, the task configuration information includes the data uploaded through the task parameter input control: "localTags":[1], "oppoTags":

[51] . In this example, the target resource category labels are 1 and 51. This configuration can be used to regard the resource data with the resource category label of 1 as the resource data for reconciliation on the local side, and the resource data with the resource category label of 51 as the resource data for reconciliation on the opposite side. It should be understood that since the verification data table stores the reconciliation files pulled from external channels, and for the target verification items, only some of the resource data in the verification data table is available. Therefore, in this application, the resource data corresponding to the target resource category label is screened out from the verification data table for reconciliation.

[0128] It should be noted that when the project types are the same, the reconciliation logic is often similar. The resource data verification script in the embodiments of this application can be regarded as a general script and can be adapted to multiple verification items.

[0129] In the embodiments of this application, by sequentially executing the resource data pulling script, the resource data type recognition script, and the resource data verification script, automatic data verification processing is realized, and through the generalized script, it is efficiently adapted to multiple verification items, improving the convenience and efficiency of resource data verification.

[0130] In one embodiment, step S507 can further include: obtaining the target resource category label; the target resource category label includes at least one local target resource category label and at least one opposite - side target resource category label; according to the at least one local target resource category label, screening out the local target data set from the verification data table, and according to the at least one opposite - side target resource category label, screening out the opposite - side target data set from the verification data table; comparing the local target data set and the opposite - side target data set to obtain the data verification result.

[0131] Still taking the example given in step S507, the local target resource category label is 1; the peer target resource category label is 51. It should be noted that the local target resource category label can be one or more; the peer target resource category label can also be one or more, and can be configured according to actual reconciliation requirements. Then, the resource data corresponding to all local target resource category labels forms a local target data set; the resource data corresponding to all peer target resource type labels forms a peer target data set. The local target data set and the peer target data set are the data actually used for reconciliation, and the data reconciliation result can be obtained by comparing the resource data in the two data sets of both parties.

[0132] In the embodiment of the present application, a local target data set is formed through the local target resource category label, and a peer target data set is formed through the peer target resource category label, so as to separate the data actually used for reconciliation from the reconciliation data table for subsequent data reconciliation.

[0133] In one embodiment, when the resource data reconciliation task is an exact reconciliation task, comparing the local target data set and the peer target data set to obtain the data reconciliation result includes:

[0134] Comparing the attribute data of the target data with the same identification field in the local target data set and the peer target data set to obtain the data reconciliation result;

[0135] When the reconciliation scenario requirements are incoming funds reconciliation, incoming funds refund / recall reconciliation, outgoing funds reconciliation, outgoing funds remittance reversal reconciliation, etc., the resource data reconciliation task can be determined as an exact reconciliation task. The exact reconciliation task requires the target data sets of both parties in the reconciliation to have a unique key, such as a bank transaction number, etc., so as to perform one-to-one reconciliation. For example, the amount corresponding to the transaction number xxx in the local target data set is 50, and the amount corresponding to the transaction number xxx in the peer target data set is also 50; then the data comparison result is consistent, and it is reconciled resource data. If there is no data record with the bank transaction number xxx in the peer target data set, the data comparison result is inconsistent, and it is recorded as abnormal resource data.

[0136] In another embodiment, when the resource data reconciliation task is a fuzzy reconciliation, comparing the local target data set and the peer target data set to obtain the data reconciliation result includes:

[0137] Determining the data reconciliation result according to the total amount of resources and the resource transfer direction of the local target data set and the total amount of resources and the resource transfer direction of the peer target data set.

[0138] When the requirements of the reconciliation scenario are foreign exchange incoming account reconciliation, foreign exchange outgoing account reconciliation, and other business reconciliations, etc., the resource data verification task can be determined as a fuzzy verification task. In the fuzzy verification task, there is no unique key for the target data sets of the two parties in the reconciliation. Multi-to-multi verification is performed based on the consistency of the type (currency) of the resource, the total amount of the resource (total amount), and the direction of resource transfer.

[0139] By classifying the resource verification task into an exact verification task and a fuzzy verification task in the embodiments of the present application, the diverse requirements of the reconciliation scenario are met, and the generality of resource data verification is enhanced.

[0140] Figure 6 It is a schematic flowchart of the data comparison of the target data set provided by the embodiments of the present application. It should be noted that Figure 6 The method shown is applicable to both the above-mentioned exact verification task and fuzzy verification task. The comparing the local target data set and the remote target data set to obtain the data verification result includes:

[0141] S601: Obtain a historical abnormal resource data set; the historical abnormal resource data set is a set formed by resource data indicating inconsistent data comparison in the data verification result during a preset historical period; the historical abnormal resource data set includes a local historical abnormal resource data set and a remote historical abnormal resource data set; the preset historical period can be the number of days for the reconciliation date cut, such as 10. The preset historical period can be obtained by parsing the data uploaded by the task parameter input control on the task configuration page corresponding to the resource verification task.

[0142] In the present application, when performing data comparison, a historical abnormal resource data set for a preset historical period is further obtained; then, the historical abnormal resource data set, the local target data set, and the remote target data set are compared to obtain the data verification result, realizing the date cut verification process. The specific comparison order is as follows:

[0143] S603: Compare the local target data set and the remote target data set to obtain initial local multi-account data and initial remote multi-account data;

[0144] Comparing the local target data set and the remote target data set will generate three types of differences. The first case is that the local data exists while the remote data does not exist, which is recorded as the initial local multi-account data; the second case is that the remote data exists while the local data does not exist, which is recorded as the initial remote multi-account data; the third case is that the amounts are inconsistent. Since the third case occurs very infrequently, it can be directly determined that the data comparison result of this data is inconsistent, and thus manual confirmation is performed.

[0145] S605: Compare the initial local multi-account data with the set of peer historical abnormal resource data to obtain a first comparison result, and update the set of peer historical abnormal resource data according to the first comparison result; if the first comparison result indicates consistency in verification, then this resource data is reconciled resource data and can be removed from the set of peer historical abnormal resource data.

[0146] S607: Compare the initial peer multi-account data with the set of local historical abnormal resource data to obtain a second comparison result, and update the set of local historical abnormal resource data according to the second comparison result; if the second comparison result indicates consistency in verification, then this resource data is reconciled resource data and can be removed from the set of local historical abnormal resource data.

[0147] S609: Obtain the data verification result according to the first comparison result and the second comparison result.

[0148] According to the first comparison result and the second comparison result, the target local multi-account data and the target peer multi-account data that have not been reconciled can be determined from the initial local multi-account data and the initial peer multi-account data, and the target local multi-account data is added to the set of local historical abnormal resource data, and the target peer multi-account data is added to the set of peer historical abnormal resource data, so as to facilitate data verification in the next execution cycle.

[0149] In the embodiment of the present application, by obtaining the set of historical abnormal resource data in a preset historical period for daily cut verification processing during data verification, the accurate verification requirement of resource data caused by cross-day transaction orders is met, and the data verification efficiency is improved.

[0150] In one embodiment, the method further includes: creating a first thread pool corresponding to the resource data pulling task, a second thread pool corresponding to the resource data type identification task, and a third thread pool corresponding to the resource data verification task; for each of the target tasks, determine a target thread pool from the first thread pool, the second thread pool, and the third thread pool according to the task type of the target task; call the target thread pool to execute the task script corresponding to the target task.

[0151] In the embodiment of the present application, each task type has an independent thread pool. When applied, the corresponding target thread pool can be selected according to the task type to execute the task script corresponding to the target task; for example, the local resource data pulling task, the peer data pulling task, the resource data type identification task, the resource data verification, and the difference processing task in different projects can be executed in parallel, thereby accelerating the verification process.

[0152] In this embodiment, by separately setting corresponding thread pools for tasks of different task types, the target tasks of different task types can execute the corresponding task scripts in parallel, shortening the overall execution time of the resource data verification process and improving the verification efficiency.

[0153] Figure 7 It is a schematic diagram of the process nodes for resource data verification provided by an embodiment of the present application.

[0154] S701: Configure the project.

[0155] The configurable items when configuring the project include but are not limited to the project name, classification, execution period (natural day, working day, weekly, monthly), holiday area, time zone, common parameters required for each task, etc. This step can be regarded as a specific example of step S203 and will not be elaborated here.

[0156] S703: Configure the task.

[0157] The configurable items when configuring the task include but are not limited to selecting the associated project, configuring the name, type, level, execution time, script type, script content, extension parameters, retry times, etc. This step can be regarded as a specific example of step S205 and will not be elaborated here.

[0158] S705: Execute task data pulling at the trigger time point.

[0159] This step can pull data through a general resource data pulling script according to the task configuration information corresponding to the resource data pulling task. The general script supports multiple data acquisition methods, such as sql query, dubbo interface query, http interface query, sftp pulling, etc. This step can be regarded as a specific example after combining step S501 and step S503 and will not be elaborated here.

[0160] S707: Automatically execute data marking after pulling is completed.

[0161] This step can be regarded as a specific example of step S505 and will not be elaborated here.

[0162] S709: Automatically execute precise verification and fuzzy verification after marking is completed.

[0163] This step can be regarded as a specific example of step S507 and will not be elaborated here.

[0164] S711: Automatically execute data processing after verification is completed.

[0165] This step is to perform data processing on the abnormal resource data representing inconsistent data comparison in the verification result. For the specific processing process, refer to the above embodiment and will not be elaborated here.

[0166] It should be noted that the tasks corresponding to each of the above steps can be regarded as nodes in the resource verification process, and the execution status of the above steps is the execution status of the nodes. At the same time, each node corresponds to an operation record, which can intuitively view the reason for the failure of the node execution, and can also manually retry a certain node and subsequent operations separately, saving processing time and reducing the pressure on computing resources.

[0167] It should be noted that there are different business departments within the payment platform, and some core data between departments also needs data verification. The resource data verification method provided in the embodiments of the present application can also be applied, and only the corresponding project type and task type need to be selected on the project configuration page and the task configuration page.

[0168] Through the above embodiments, for simple verification, product personnel can directly configure and go online within hours; for example, when the file format of the peer resource data changes, using the dynamic characteristics of the groovy scripting language, the script can be modified in the browser and submitted to the server, and it will take effect immediately. After taking effect, the new logic can be used to parse and process the new file format. For complex verification, it is necessary to customize the script and then configure it for production acceptance by the product, and it will take about one day to go online, and there is no need to restart the application. It can be seen that the method of the present application can conveniently and quickly implement resource data verification, effectively improving the data verification efficiency.

[0169] Figure 8 It is a structural schematic diagram of a resource data verification device provided by an embodiment of the present application.

[0170] As Figure 8 shown, the device 800 may include:

[0171] A project creation module 801, configured to create a target verification project in response to a resource data verification request;

[0172] A project configuration module 802, configured to obtain project configuration information in response to a configuration operation on the target verification project; the project configuration information includes the project type and execution period of the target verification project; the target verification project includes a plurality of target tasks;

[0173] A task configuration module 803, configured to obtain task configuration information of each of the target tasks in response to a configuration operation on the plurality of target tasks; the task configuration information includes the task type of each of the target tasks;

[0174] A task script determination module 804, configured to determine a task script corresponding to each target task according to the project type and each task type; the task script includes a resource data pulling script corresponding to a resource data pulling task, a resource data type identification script corresponding to a resource data type identification task, and a resource data verification script corresponding to a resource data verification task;

[0175] A script execution module 805, configured to sequentially execute the resource data pulling script, the resource data type identification script, and the resource data verification script according to the execution cycle, and obtain a data verification result.

[0176] In some embodiments, the script execution module may include:

[0177] An execution time point acquisition sub-module, configured to acquire the execution time point of the resource data pulling task in each execution cycle;

[0178] A data pulling sub-module, configured to, when the execution time point is reached, pull local resource data and peer resource data by using the resource data pulling script, and store the local resource data and the peer resource data into a verification data table;

[0179] A category label annotation sub-module, configured to perform category label annotation processing on the resource data in the verification data table by using the resource data type identification script, and obtain a resource category label;

[0180] A data verification sub-module, configured to perform data verification processing on the resource data with a target resource category label in the verification data table by using the resource data verification script, and obtain the data verification result.

[0181] In some embodiments, the data pulling sub-module may include:

[0182] A local resource data pulling unit, configured to pull local resource data from a local service database;

[0183] A peer data pulling mode determination unit, configured to determine a peer data pulling mode according to the peer data source address;

[0184] A peer resource data downloading unit, configured to download the peer resource data from the peer data source address according to the peer data pulling mode;

[0185] A resource data storage unit, configured to store the local resource data and the peer resource data into the verification data table;

[0186] In some embodiments, the category label annotation sub-module may include:

[0187] A category label comparison table acquisition unit for acquiring a category label comparison table; the category label comparison table includes a plurality of preset resource category labels and description information corresponding to the plurality of preset resource category labels;

[0188] A field name acquisition unit for acquiring the field names of the resource data in the verification data table;

[0189] A matching unit for determining, according to a preset label matching strategy, preset description information that matches the field name from the description information;

[0190] A resource category label determination unit for determining the resource category label of the resource data according to the correspondence between the description information and the preset resource category labels in the category label table.

[0191] In some embodiments, the data verification sub-module may include:

[0192] A target resource category label acquisition unit for acquiring a target resource category label; the target resource category label includes at least one local target resource category label and at least one peer target resource category label;

[0193] A data screening unit for screening out a local target data set from the verification data table according to the at least one local target resource category label, and screening out a peer target data set from the verification data table according to the at least one peer target resource category label;

[0194] A data comparison unit for comparing the local target data set and the peer target data set to obtain the data verification result.

[0195] In some embodiments, the data comparison unit may include:

[0196] An exact comparison sub-unit for performing attribute data comparison on the target data with the same identification field in the local target data set and the peer target data set to obtain the data verification result;

[0197] In some embodiments, the data comparison unit may further include:

[0198] A fuzzy comparison unit for determining the data verification result according to the total amount of resources and the resource transfer direction in the local target data set and the total amount of resources and the resource transfer direction in the peer target data set.

[0199] In some embodiments, the data verification sub-module may include:

[0200] A historical abnormal resource data set acquisition unit is configured to acquire a historical abnormal resource data set; the historical abnormal resource data set is a set formed by resource data indicating inconsistent data comparison in the data comparison results during a preset historical period; the historical abnormal resource data set includes a local historical abnormal resource data set and a peer historical abnormal resource data set;

[0201] A target data set comparison unit is configured to compare the local target data set with the peer target data set to obtain initial local multi-account data and initial peer multi-account data;

[0202] A first comparison unit is configured to compare the initial local multi-account data with the peer historical abnormal resource data set to obtain a first comparison result, and update the peer historical abnormal resource data set according to the first comparison result;

[0203] A second comparison unit is configured to compare the initial peer multi-account data with the local historical abnormal resource data set to obtain a second comparison result, and update the local historical abnormal resource data set according to the second comparison result;

[0204] A data comparison result determination unit is configured to obtain the data comparison result according to the first comparison result and the second comparison result.

[0205] In some embodiments, the target task further includes a difference processing task, and the apparatus 800 may further include:

[0206] An abnormal resource data statistics module is configured to count the abnormal resource data indicating inconsistent data comparison in the data comparison result;

[0207] A difference processing strategy determination module is configured to determine a difference processing strategy according to the difference type of the abnormal resource data;

[0208] A difference processing module is configured to, in response to the confirmation operation of the difference processing strategy, perform difference processing on the abnormal resource data according to the difference processing strategy, and form a difference processing record.

[0209] In some embodiments, the apparatus 800 may further include:

[0210] A thread pool creation module is configured to create a first thread pool corresponding to the resource data pulling task, a second thread pool corresponding to the resource data type identification task, and a third thread pool corresponding to the resource data comparison task;

[0211] A target thread pool determination module is configured to, for each of the target tasks, determine a target thread pool from the first thread pool, the second thread pool, and the third thread pool according to the task type of the target task;

[0212] A thread pool calling module, configured to call the target thread pool to execute a task script corresponding to the target task.

[0213] The device in the device embodiment and the method embodiment are based on the same inventive concept.

[0214] An embodiment of the present application provides an electronic device, which includes a processor and a memory. At least one instruction or at least one program segment is stored in the memory, and the at least one instruction or at least one program segment is loaded and executed by the processor to implement the method provided in the above method embodiment.

[0215] An embodiment of the present application further provides a computer storage medium, which can be set in a terminal to store at least one instruction or at least one program segment related to implementing a method provided in the method embodiment as described above. The at least one instruction or at least one program segment is loaded and executed by the processor to implement the method provided in the above method embodiment.

[0216] An embodiment of the present application further provides a computer program product or a computer program, which includes computer instructions stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes to implement the method provided in the above method embodiment.

[0217] Optionally, in an embodiment of the present application, the storage medium may be located in at least one of multiple network servers in a computer network. Optionally, in this embodiment, the above storage medium may include, but is not limited to: USB flash drives, read-only memories (ROMs), random access memories (RAMs), mobile hard disks, magnetic disks, or optical disks, etc., various media that can store program codes.

[0218] The memory in the embodiment of the present application can be used to store software programs and modules. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory. The memory mainly includes a program storage area and a data storage area. Among them, the program storage area can store an operating system, application programs required for functions, etc.; the data storage area can store data created according to the use of the device, etc. In addition, the memory may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices. Correspondingly, the memory may further include a memory controller to provide the processor with access to the memory.

[0219] The method provided by the embodiments of the present application can be executed on a mobile terminal, a computer terminal, a server, or a similar computing device. Taking running on a server as an example, Figure 9 is a hardware structure block diagram of a server for a resource data verification method provided by an embodiment of the present application. As Figure 9 shown, the server 900 may vary greatly due to different configurations or performances, and may include one or more central processing units (CPUs) 910 (the central processing unit 910 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 930 for storing data, and one or more storage media 920 (such as one or more mass storage devices) for storing application programs 923 or data 922. Among them, the memory 930 and the storage media 920 may be transient storage or persistent storage. The program stored in the storage media 920 may include one or more modules, and each module may include a series of instruction operations on the server. Further, the central processing unit 910 may be configured to communicate with the storage media 920 and execute a series of instruction operations in the storage media 920 on the server 900. The server 900 may also include one or more power supplies 960, one or more wired or wireless network interfaces 950, one or more input / output interfaces 940, and / or one or more operating systems 921, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, and so on.

[0220] The input / output interface 940 can be used to receive or send data via a network. Specific examples of the above network may include a wireless network provided by the communication provider of the server 900. In one example, the input / output interface 940 includes a network interface controller (NIC), which can be connected to other network devices through a base station and thus can communicate with the Internet. In one example, the input / output interface 940 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0221] Those of ordinary skill in the art can understand that Figure 9 the structure shown is only schematic and does not limit the structure of the above electronic device. For example, the server 900 may further include more or fewer components than those shown in Figure 9 , or have a different configuration from that shown in Figure 9 .

[0222] As can be seen from the embodiments of the resource data verification method, apparatus, device, and storage medium provided by the present application above, the embodiments of the present application create a target verification item in response to a resource data verification request; then obtain item configuration information in response to a configuration operation on the target verification item; the target verification item includes multiple target tasks. After that, the financial staff can configure the target tasks, and then obtain the task configuration information of each target task in response to the configuration operations on the multiple target tasks; determine the task script corresponding to each target task according to the project type and each task type; and then execute the task scripts corresponding to the target tasks in sequence according to the execution cycle, including the resource data pulling script, the resource data type identification script, and the resource data verification script, so as to obtain a data verification result. Through the dynamic configuration of the target verification item and the target tasks, the script writing time before resource data verification can be saved. When docking with a new channel, reconciliation can be quickly achieved through configuring the project; when the data format of the reconciliation file provided by the already docked channel changes, reconciliation can be quickly achieved by modifying the task configuration of the relevant tasks in the corresponding project; compared with the hard-coding method in the traditional solution, the present application does not need to rewrite the reconciliation code every time a new channel is docked or the reconciliation file changes. Therefore, resource data verification can be carried out flexibly and conveniently, effectively improving the data verification efficiency.

[0223] It should be noted that: the above sequence of the embodiments of the present application is only for description and does not represent the superiority or inferiority of the embodiments. And the above specific embodiments of this specification have been described. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be executed in a different order from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0224] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between each embodiment can be referred to each other. Each embodiment focuses on the differences from other embodiments. In particular, for the embodiments of the apparatus, device, and storage medium, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.

[0225] Those of ordinary skill in the art can understand that all or part of the steps to implement the above embodiments can be completed by hardware, or can be completed by a program instructing relevant hardware. The program can be stored in a computer storage medium. The above-mentioned storage medium can be a read-only memory, a disk, an optical disc, etc.

[0226] The above are only the preferred embodiments of the present application and are not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included within the protection scope of the present application.

Claims

1. A resource data verification method, characterized in that: The method comprises: In response to the resource data verification request, creating a target verification item; In response to the configuration operation of the target check item, acquiring project configuration information; the project configuration information includes the project type and execution period of the target check item; the target check item includes a plurality of target tasks; In response to the configuration operation on the plurality of target tasks, acquiring task configuration information of each target task; the task configuration information includes a task type of each target task; Determine a task script corresponding to each of the target tasks according to the project type and each of the task types; the task script includes a resource data pulling script corresponding to the resource data pulling task, a resource data type identification script corresponding to the resource data type identification task, and a resource data checking script corresponding to the resource data checking task; The resource data pulling script, the resource data type identification script and the resource data verification script are executed in sequence according to the execution cycle to obtain a data verification result.

2. The method according to claim 1, characterized in that: The step of sequentially executing the resource data pulling script, the resource data type identification script, and the resource data verification script according to the execution cycle to obtain a data verification result includes: In each of the execution cycles, obtaining the execution time point of the resource data pulling task; When the execution time point is reached, the resource data pulling script is used to pull the local resource data and the opposite resource data, and the local resource data and the opposite resource data are stored in the verification data table; Using the resource data type identification script to perform category labeling processing on the resource data in the verification data table to obtain a resource category label; The resource data verification script is used to perform data verification processing on the resource data with the target resource category tag in the verification data table to obtain the data verification result.

3. The method according to claim 2, characterized in that: The method of using the resource data pulling script to pull local resource data and peer resource data, and storing the local resource data and peer resource data in a verification data table, includes: Pull local resource data from the local business database; Determine the peer data pulling method based on the peer data source address; Downloading the peer resource data from the peer data source address according to the peer data pulling method; The local resource data and the opposite resource data are stored in the verification data table.

4. The method according to claim 2, characterized in that: The step of using the resource data type identification script to perform category labeling processing on the resource data in the verification data table to obtain a resource category label includes: Obtain a category label comparison table; the category label comparison table includes a plurality of preset resource category labels and description information corresponding to the plurality of preset resource category labels; Obtaining the field names of the resource data in the verification data table; Determining preset description information matching the field name from the description information according to a preset tag matching strategy; The resource category label of the resource data is determined according to the correspondence between the description information in the category label table and the preset resource category label.

5. The method according to claim 2, characterized in that: The method of using the resource data verification script to perform data verification processing on the resource data with the target resource category tag in the verification data table to obtain the data verification result includes: Acquire a target resource category tag; the target resource category tag includes at least one local target resource category tag and at least one opposite target resource category tag; Filtering a local target data set from the check data table according to the at least one local target resource category label, and filtering a peer target data set from the check data table according to the at least one peer target resource category label; The local target data set and the opposite target data set are compared to obtain the data verification result.

6. The method according to claim 5, characterized in that When the resource data verification task is a precise verification task, the comparing the local target data set with the peer target data set to obtain the data verification result includes: Performing attribute data comparison on the target data with the same identification field in the local target data set and the opposite target data set to obtain the data verification result; When the resource data verification task is fuzzy verification, the comparison of the local target data set with the peer target data set to obtain the data verification result includes: The data verification result is determined according to the total amount of resources and the resource transfer direction of the local target data set and the total amount of resources and the resource transfer direction of the opposite target data set.

7. The method according to claim 5, characterized in that The comparing the local target data set with the opposite target data set to obtain the data verification result includes: Acquire a historical abnormal resource data set; the historical abnormal resource data set is a set of resource data representing inconsistent data comparison in the data verification results in a preset historical period; the historical abnormal resource data set includes the historical abnormal resource data set of the local end and the historical abnormal resource data set of the opposite end; Comparing the local target data set with the opposite target data set to obtain initial local multi-account data and initial opposite multi-account data; Comparing the initial local multi-account data with the peer historical abnormal resource data set to obtain a first comparison result, and updating the peer historical abnormal resource data set according to the first comparison result; Comparing the initial peer-end multi-account data with the local-end historical abnormal resource data set to obtain a second comparison result, and updating the local-end historical abnormal resource data set according to the second comparison result; The data verification result is obtained according to the first comparison result and the second comparison result.

8. The method according to claim 7, characterized in that The target task also includes a difference processing task. After obtaining the data verification result, the method further includes: Collecting statistics of abnormal resource data representing inconsistent data comparison in the data verification results; Determining a difference processing strategy according to the difference type of the abnormal resource data; In response to a confirmation operation of the difference processing strategy, difference processing is performed on the abnormal resource data according to the difference processing strategy, and a difference processing record is formed.

9. The method according to claim 1, characterized in that: The method further comprises: Create a first thread pool corresponding to the resource data pulling task, a second thread pool corresponding to the resource data type identification task, and a third thread pool corresponding to the resource data checking task; For each of the target tasks, determining a target thread pool from the first thread pool, the second thread pool, and the third thread pool according to a task type of the target task; The target thread pool is called to execute a task script corresponding to the target task.

10. A resource data checking device, characterized in that: The device comprises: A project creation module, for creating a target verification project in response to a resource data verification request; A project configuration module, configured to obtain project configuration information in response to a configuration operation on the target check project; the project configuration information includes a project type and an execution period of the target check project; the target check project includes a plurality of target tasks; A task configuration module, configured to obtain task configuration information of each target task in response to configuration operations on the plurality of target tasks; the task configuration information includes a task type of each target task; A task script determination module is used to determine the task script corresponding to each of the target tasks according to the project type and each of the task types; the task script includes a resource data pulling script corresponding to the resource data pulling task, a resource data type identification script corresponding to the resource data type identification task, and a resource data verification script corresponding to the resource data verification task; The script execution module is used to execute the resource data pulling script, the resource data type identification script and the resource data verification script in sequence according to the execution cycle to obtain a data verification result.

11. An electronic device, characterized in that: The electronic device comprises: a processor and a memory, wherein the memory stores at least one instruction or at least one program, and the at least one instruction or at least one program is loaded and executed by the processor to implement the resource data verification method as described in any one of claims 1-9.

12. A computer storage medium, characterized in that: The computer storage medium stores at least one instruction or at least one program, and the at least one instruction or at least one program is loaded and executed by a processor to implement the resource data verification method as described in any one of claims 1-9.

Images