A self-checking and early warning engine tool for abnormal anti-money laundering data in financial institutions
Through the self-check and early warning engine tool for anti-money laundering abnormal data of financial institutions, the rule management and data verification modules are used to batch check and control anti-money laundering data, which solves the lack of systematic search for problem data in financial institutions' anti-money laundering compliance. The problem has achieved internal governance of data quality and improved efficiency.
Patent Information
- Application Number
- CN202311808856.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-12-26
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2043-12-26
AI Technical Summary
Financial institutions lack the tools to systematically and proactively find problem data in the anti-money laundering compliance process, which makes it difficult to ensure data quality and rely on manual patching and correction, which is inefficient.
Provide a self-check and early warning engine tool for anti-money laundering abnormal data of financial institutions, including rule management module, data verification module and data governance module. By running batches, the target data files are batch checked, the verification results are generated, and the exceptions are transferred. Data is assigned and rectified for governance tasks, and supports the initialization of built-in verification rules and institutional custom rules to realize internal governance of data quality.
It has realized systematic and proactive search and rectification of anti-money laundering data of financial institutions, discovered inaccurate or incomplete data early, improved data quality, reduced the penalty risk of regulatory inspections, released manual labor, and improved data governance efficiency.
Smart Images

Figure CN118134636B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of financial technology, and in particular to a self-checking and early warning engine tool for abnormal anti-money laundering data of financial institutions. Background Art
[0002] The focus of data governance is on customers and transactions, which means that every organization has to face a huge amount of data, which makes it difficult to start. From the perspective of the data itself, on the one hand, the data involves customer information and transaction information, the data volume is huge, the distribution is scattered, and the business scenarios are complex; on the other hand, there are data quality problems caused by chaotic historical data storage, changes in information collection standards, system switching, inadequate data processing, etc., which are difficult to unravel and trace the root causes. From the institutional level, on the one hand, some institutions do not have a full understanding of data governance, have not invested resources or have invested limited resources, resulting in weak professional strength and non-cooperation from relevant departments. On the other hand, data governance is a long-term task, and the effect is difficult to see immediately, and a unique "data culture" has not yet been established.
[0003] In a traditional anti-money laundering compliance process, problems with data are often discovered only when it is needed, such as in regulatory reporting and model batching. Compliance personnel will provide scattered feedback of these issues to technical personnel, who will then make corrections in a patch-like manner. Financial institutions lack the tools to systematically and proactively find the root causes of problematic data. Summary of the invention
[0004] This application provides a self-checking and early warning engine tool for abnormal anti-money laundering data of financial institutions, aiming to help financial institutions systematically and proactively find problematic data.
[0005] First, a self-checking and early warning engine tool for abnormal anti-money laundering data of financial institutions, including:
[0006] The rule management module is used to manage multiple verification rules for data quality governance of different financial institutions;
[0007] The data verification module is used to receive the target data file of the financial institution to be inspected, create a verification task and a protocol file corresponding to the verification task according to the target data file, and store the target data file and the protocol file in a receiving directory; read the target data file from the receiving directory, perform batch verification on the target data file by running a batch according to the verification rule, extract abnormal data in the target data file that does not meet the verification rule, and generate a verification result;
[0008] The data governance module is used to assign governance tasks to the abnormal data according to data ownership, and send the governance tasks to the corresponding financial institutions; receive the governance results and completion operations fed back by the corresponding financial institutions of the governance tasks.
[0009] In the above scheme, optionally, the verification rules include initialized built-in verification rules and verification rules flexibly configured by the financial institution according to its actual needs; the initialized built-in verification rules are summarized based on the regulatory agency's requirements for anti-money laundering on-site inspection data of financial institutions.
[0010] In the above scheme, optionally, the verification rules include format verification rules, content compliance verification rules and logical rationality verification rules.
[0011] In the above scheme, optionally, the format of the target data file is a csv text file, the content format of the target data file is UTF-8 encoding, and the amount of data in each target data file is less than or equal to 300 million; in the target data file, the field content is enclosed in half-width double quotes, and the fields are separated by half-width single vertical lines or commas; the content in the protocol file uses json format data, and the name of the protocol file uses Chinese, English, numbers, underscores, hyphens, and the name length is less than or equal to 20 characters.
[0012] In the above scheme, optionally, in the data verification module, when multiple target data files are received and multiple verification tasks and protocol files are created, all target data files are stored in a folder named with the current date in the receiving directory, each protocol file is named according to the corresponding verification task, and each protocol file is stored in a pre-agreed scanning directory in the receiving directory.
[0013] In the above solution, optionally, the data governance module is also used to:
[0014] Sending the abnormal overview and details of the abnormal data to the corresponding financial institution;
[0015] Send task processing deadline reminders to the corresponding financial institutions.
[0016] In the above solution, optionally, the self-checking early warning engine tool further includes:
[0017] The verification result statistics module is used to visualize the verification results and display the specific distribution of the abnormal data during the visualization; receive the selected display dimension, and perform statistics and visualization on the verification results according to the display dimension.
[0018] In the above solution, further optionally, the verification result statistics module is also used to:
[0019] When displaying visually, the specific reasons why the verification failed are displayed for the target data files and fields that failed the verification;
[0020] The input export condition is accepted, and the abnormal data in the verification result that meets the export condition is exported in batches.
[0021] In the above solution, optionally, the self-checking early warning engine tool further includes:
[0022] The task comparison module is used to compare the abnormal data and the governance results, and to visualize the comparison results; receive two selected verification tasks, the two verification tasks correspond to the same target data file in different time periods, compare the corresponding verification results of the two verification tasks, and visualize the abnormal data of the same target data file in different verification tasks respectively.
[0023] In the above scheme, optionally, the self-check and early warning engine tool adopts a B / S architecture, the self-check and early warning engine tool supports multiple legal persons and a head-branch-branch architecture, the front-end interactive interface of the self-check and early warning engine tool is developed using VUE technology components, and the data storage of the self-check and early warning engine tool adopts a MySQL database.
[0024] Compared with the prior art, this application has at least the following beneficial effects:
[0025] Based on the regulatory authorities' requirements for anti-money laundering on-site inspection data of financial institutions such as banks, payments, insurance, securities, and futures, verification rules for data quality governance of different financial institutions are summarized to form a self-inspection and early warning engine tool for abnormal anti-money laundering data of financial institutions; using this self-inspection and early warning engine tool, after scanning and reading the target inspection data, the anti-money laundering data of financial institutions is systematically batch-verified through systematic batch running, and abnormal data that does not conform to the rules can be extracted, and the abnormal data can be actively located and tracked, and the data quality can be understood in advance, and the institution is urged to make prior rectification to achieve internal governance of data quality; while financial institutions actively respond to regulatory inspections, they can also conduct self-inspection and self-examination of anti-money laundering data within the financial institutions, and discover problems such as inaccurate and incomplete data within the institutions as early as possible, so as to improve the data in a targeted manner, improve the data quality, and reduce the penalties of regulatory inspections; at the same time, the self-inspection and early warning engine tool can release manual labor, greatly reduce manual workload, and enable the main focus of manual labor to be on later rectification or other more important things, greatly improving the efficiency of institutional data governance. BRIEF DESCRIPTION OF THE DRAWINGS
[0026] Figure 1 A schematic diagram of the technical architecture of a self-checking and early warning engine tool for abnormal anti-money laundering data of a financial institution provided by an embodiment of the present application;
[0027] Figure 2 A module architecture block diagram of a self-checking and early warning engine tool for anti-money laundering abnormal data of a financial institution provided in one embodiment of the present application;
[0028] Figure 3 This is a schematic diagram of the contents of a target data file in one embodiment of the present application;
[0029] Figure 4 This is a schematic diagram of file storage for multiple scanning tasks in one embodiment of the present application;
[0030] Figure 5 A schematic diagram of the data architecture of a self-checking and early warning engine tool for abnormal anti-money laundering data of a financial institution provided by one embodiment of the present application;
[0031] Figure 6 A schematic diagram of a processing flow of a self-checking and early warning engine tool for anti-money laundering abnormal data of a financial institution provided by an embodiment of the present application;
[0032] Figure 7 A schematic diagram of the deployment architecture of a self-checking and early warning engine tool for anti-money laundering abnormal data of a financial institution provided in accordance with an embodiment of the present application. DETAILED DESCRIPTION
[0033] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.
[0034] In the description of the present application: unless otherwise specified, expressions such as “include”, “comprising”, “having”, etc. also mean “not limited to” (certain units, components, materials, steps, etc.).
[0035] In one embodiment, Figure 1 As shown, a self-checking and early warning engine tool for abnormal anti-money laundering data of financial institutions is provided. The self-checking and early warning engine tool adopts B / S architecture, uses mainstream development frameworks and development languages, supports multiple legal persons, supports headquarter-branch-branch architecture, and adapts to the strategic development requirements of different financial institutions. It has the advantages of Java cross-platform deployment, easy deployment and maintenance, and stable operation. The front-end interactive interface is developed using VUE technology components, the page is easy to maintain and compatible with a variety of mainstream browsers. The data storage uses MySQL database, which is open source and free, has a fast running speed, and has a high password encryption security factor. It can be deployed on a variety of mainstream servers such as Linux and Windows.
[0036] The target inspection data of the self-inspection warning engine tool is based on the on-site inspection data extraction interface specification requirements issued by current regulators for banks, payment institutions, securities, futures, insurance and other industries as the basic data file. Each data file has a corresponding protocol file to explain it.
[0037] Specifically, if Figure 2 As shown, the self-checking early warning engine tool includes the following program modules:
[0038] A rule management module 201 is used to manage multiple verification rules for data quality management of different financial institutions;
[0039] The data verification module 202 is used to receive the target data file of the financial institution to be inspected, create a verification task and a protocol file corresponding to the verification task according to the target data file, and store the target data file and the protocol file in a receiving directory; read the target data file from the receiving directory, perform batch verification on the target data file according to the verification rules by running a batch, extract the abnormal data in the target data file that does not meet the verification rules, and generate a verification result;
[0040] The data governance module 203 is used to assign governance tasks to abnormal data according to data ownership, and send the governance tasks to the corresponding financial institutions; receive the governance results and completion operations fed back by the corresponding financial institutions of the governance tasks.
[0041] Furthermore, the verification rules include the initialized built-in verification rules and the verification rules that the financial institution can flexibly configure according to its actual needs; the initialized built-in verification rules are summarized based on the regulatory agency's requirements for the anti-money laundering on-site inspection data of financial institutions. The verification rules include format verification rules, content compliance verification rules and logical rationality verification rules.
[0042] In other words, the above-mentioned self-check and early warning engine tool is based on the distillation, summary and classification of the requirements of the regulatory authorities for different anti-money laundering business scenarios. The refined verification rules are divided into format verification, content compliance verification and logical rationality verification. The total number of initialized rules exceeds one thousand, covering many aspects of anti-money laundering scenarios.
[0043] The rules involving parameters will set the parameter values in the system in advance. The parameter settings are generally within the scope of the regulatory system requirements, and are appropriately adjusted according to the size of financial institutions. For example, the regulatory requirements for the next re-rating of high-risk customers are 6 months. Some institutions set it to 6 months, while others set it to 3 months. Institutions can flexibly configure the rule parameters according to their actual business needs. As long as it does not exceed 6 months, it is within the compliance range.
[0044] Furthermore, the format of the target data file is a csv text file, the content format in the target data file is UTF-8 encoding, and the amount of data in each target data file is less than or equal to 300 million; in the target data file, the field content is enclosed in half-width double quotes, and the fields are separated by half-width single vertical lines or commas; the content in the protocol file uses json format data, and the name of the protocol file uses Chinese, English, numbers, underscores, and hyphens, and the name length is less than or equal to 20 characters.
[0045] In other words, the data file format uses a csv text file. The content of the file is in UTF-8 encoding. The file name is consistent with the table name of the source table (not case sensitive). For example, {table_name}.csv or {table_name}_{num}.csv. {table_name} is the name of the original table of the document, and {num} is a positive integer. For example:
[0046] tb_company.csv
[0047] tb_company_1.csv
[0048] tb_company_2.csv
[0049] The self-checking warning engine tool can verify that the data file is a csv text file in UTF-8 encoding format. The field content in the file is enclosed in double quotes and separated by "|" or "," (the separator is in English half-width). For example: the organization comparison table data file is named: TB_BANK.csv, and the content is as follows: Figure 3 shown.
[0050] The data volume of a single file does not exceed 300 million. If the data volume of a single file exceeds 300 million, the file needs to be split into 300 million csv files. For example, if the "credit card account financial transaction data table tb_cred_txn" generates 800 million data in a year, it can be split into 3 files. That is:
[0051] tb_cred_txn_1.csv (30 million data)
[0052] tb_cred_txn_2.csv (30 million data)
[0053] tb_cred_txn_3.csv (20 million data)
[0054] The name of the protocol file is displayed as the task name in the task list. Protocol file naming: Only Chinese and English, numbers, underscores, and hyphens can be used, and the length must be less than or equal to 20 characters.
[0055] The content of the protocol file uses json format data. The protocol file name cannot be repeated in the same directory. When multiple verification tasks need to be created on the same day, a protocol file needs to be created for each verification task (that is, multiple verification tasks correspond to multiple protocol files).
[0056] File parameter description:
[0057]
[0058]
[0059] Furthermore, in the data verification module, when multiple target data files are received and multiple verification tasks and protocol files are created, all target data files are stored in a folder named with the current date in the receiving directory, each protocol file is named according to the corresponding verification task, and each protocol file is stored in a pre-agreed scanning directory in the receiving directory.
[0060] In other words, when there are multiple scanning tasks, the storage of protocol files and data files can refer to Figure 4 The protocol files are stored in the agreed scanning directory, and all data files are stored in folders named after the current date. In the protocol file, indicate the data files required for the task.
[0061] For example, on September 7, 2020, you want to use the data from January to March 2020 to generate a batch of data as a task; use the data from April to June 2020 to generate a batch of data as a task. At this time, you can generate two protocol files named "202001-03.ok" and "202004-06.ok" respectively. The data files generated from January to March 2020 are tb_bank_1.csv, tb_bank_2.csv, tb_bank_3.csv, and tb_acc_1.csv. The data files generated from April to June 2020 are tb_bank_4.csv and tb_acc_2.csv. After putting all the csv files in the 20200927 folder, put "202001-03.ok" and "202004-06.ok" in the agreed scanning directory.
[0062] The deployer configures the scan file path, the parameter is dqc.scan.path. The default path is / home / kaifa / receive. Confirm the path during deployment so that the path has read permissions. Receive the csv data file and the corresponding YYYYMMDD.ok protocol file in the YYYYMMDD directory transferred from other systems through the file transfer system BTP in the application server receiving directory / home / appuser / amldqc / fsdisk / receive. For example, today is September 8, 2020.
[0063] Other systems transfer folders 20200908 and 20200908.ok through the BTP file transfer system (the folders marked in red font need to be created by the manufacturer providing the file data), and be sure to transfer the folder where the csv data file is located first and then transfer the 20200908.ok file; store the data file in the directory in the previous step and wait for the scan task to be executed; the scan task will be taken within 10 minutes [or within the configured time interval]; the manual configuration of the scan task is as follows:
[0064] ① Log in to the application server (the primary server 10.190.42.202 and the standby server 10.190.42.203), enter the / home / appuser / amldqc / dqc-server-1.0.0-SNAPSHOT / config directory, and use the vi command to modify the dqc.scan.cron configuration in the application-release.yml file under the primary server [application-release-bak.yml under the standby server];
[0065] ②When the protocol file is scanned and can be parsed correctly, the data files related to the protocol will be removed; if the relevant data files exist for a long time, it means that the task execution has failed;
[0066] ③ It is not recommended to upload data files and protocol files to the directory of the day after 23:00 every day to avoid missing scans when crossing days;
[0067] ④ The protocol file must be transferred to the receiving directory after all data files are transferred to the receiving directory. Otherwise, the task will fail to execute because the data file cannot be found.
[0068] Furthermore, the data governance module 203 is also used for:
[0069] Send the abnormal overview and details of abnormal data to the corresponding financial institution;
[0070] Send task processing deadline reminders to the corresponding financial institutions.
[0071] Furthermore, the self-checking early warning engine tool also includes:
[0072] The verification result statistics module is used to visualize the verification results and display the specific distribution of abnormal data during the visualization; it receives the selected display dimension and performs statistics and visualization on the verification results according to the display dimension.
[0073] The verification result statistics module is also used for:
[0074] When displaying visually, the specific reasons why the verification failed are displayed for the target data files and fields that failed the verification;
[0075] Accept the input export conditions and batch export the abnormal data in the verification results that meet the export conditions.
[0076] Furthermore, the self-checking early warning engine tool also includes:
[0077] The task comparison module is used to compare abnormal data with governance results and visualize the comparison results; receive two selected verification tasks, the two verification tasks correspond to the same target data file in different time periods, compare the corresponding verification results of the two verification tasks, and visualize the abnormal data of the same target data file in different verification tasks.
[0078] The self-check warning engine tool reads the files to be verified that are scanned to a fixed location, and runs batches to generate verification results based on the built-in verification rules. For tables and fields that fail the verification, you can view the specific reasons for the failure of the verification.
[0079] The inspection results can be located by rule or field search and can be exported in batches. The format content exported from the perspective of rules can be used to view the customers that trigger the same rule; the format content exported from the perspective of customers can be used to view the rules triggered by each field related to the customer.
[0080] The verification results can be compared through numbers and charts, and the triggering rules and error data of the data table in different tasks can be displayed, the difference in numerical quality before and after can be intuitively seen, and the effectiveness of anti-money laundering data quality management can be obtained.
[0081] In summary, if Figure 1 and Figure 5 As shown, the self-check warning engine tool mainly includes modules such as data verification, rule management, data governance, task comparison, data table management, code table management, and verification result statistics.
[0082] Different verification rules are built into the "Rule Management" module, and the problem data of on-site inspections are displayed in the "Data Verification" module through system batch verification. "Data Governance" will automatically assign and rectify the problem data according to the data ownership. When handling governance tasks, the institution to which the erroneous data belongs can view the error overview and details related to the institution, which is convenient for locating problems and subsequent governance; after completing upstream data governance, the governance tasks can be completed, and the governance results can be fed back to achieve closed-loop processing of overall data governance.
[0083] In the "Task Comparison" module, you can select two different verification tasks to compare the data of the verification results. The comparison content is applicable to the comparison of the same business data in different time periods, and also to the comparison before and after the governance of the same batch of data. When creating a task comparison, you can only select the data source table included in both tasks to avoid invalid comparison. After the comparison, the trigger rules and error data of each data table in the report in different tasks are displayed in numbers and charts, and the difference in numerical quality before and after is intuitive, and the report data can be exported to Excel. Through the "Verification Result Statistics", you can view the specific distribution of abnormal data, and support statistics and display of verification results by different dimensions such as tasks, data files, and data tables. The "Task Comparison" and "Verification Result Statistics" modules are both in-depth analyses of data after governance, which are convenient for intuitively viewing the distribution of problems and the effect of governance. Other modules such as "Data Table Management" and "Code Table Management" are basic support modules, mainly used for the configuration of basic information.
[0084] The self-checking and early warning engine tool mentioned above has two reading modes: manual and automatic. Manual means manually selecting the target data to be checked and then performing system verification; automatic means placing the target data in a specified location, and the self-checking and early warning engine tool mentioned above will automatically read the data at the specified location, and can set a scheduled task, such as reading in units of "days" according to the actual needs of financial institutions, or automatically reading once a quarter, etc. This method can meet the reading and verification needs of different time periods.
[0085] The deployment architecture diagram of the self-check warning engine tool can be found in Figure 6 , the processing flow diagram can be found in Figure 7 .
[0086] In order to overcome the problems of wide range, scattered distribution, poor quality, large amount of historical data, and complex business scenarios of anti-money laundering data, the embodiment of the present application sorts out the corresponding data requirements in accordance with the regulatory requirements, and classifies these requirements into different data verification rules and models, which are built into the system to form a self-inspection and early warning engine tool for screening anti-money laundering abnormal data based on a multi-dimensional rule model. Then, the anti-money laundering data of financial institutions is systematically batch-verified through systematic batch running, and abnormal data that does not comply with the rules is extracted, and the institution is urged to make rectifications in advance to achieve internal governance of data quality and reduce penalties for regulatory inspections. At the same time, it also greatly reduces manual workload and greatly improves the efficiency of institutional data governance.
[0087] The technical solution adopted this time is: based on the regulatory authorities' requirements for anti-money laundering on-site inspection data of financial institutions such as banks, payments, insurance, securities, and futures, the verification rules for data quality governance of different financial institutions are summarized, and financial institutions are supported to flexibly configure the verification rules according to their actual needs. Through the built-in rules initialized by the system and the rules customized by the institutions, a self-inspection and early warning engine tool for screening anti-money laundering abnormal data based on a multi-dimensional rule model is formed. By scanning and reading the target inspection data, the abnormal data can be located and tracked, the data quality can be understood in advance, and while actively responding to regulatory inspections, the financial institutions can conduct self-inspection of anti-money laundering data within the institutions, and discover problems such as inaccurate and incomplete data within the institutions as early as possible, so as to improve the data and improve the data quality in a targeted manner.
[0088] The self-checking and early warning engine tool provided by this application strengthens the integration and application of technology in anti-money laundering compliance and other aspects, finds the balance between manpower and technology, promotes efficiency with intelligence, and improves the efficiency and accuracy of anti-money laundering data governance. Anti-money laundering covers the entire amount of customer and transaction data, connects various business systems with the customer management system, and has certain particularities. When doing anti-money laundering data governance, simply discovering through manual labor or performing scattered data checks through individual functions in different systems can only be a drop in the bucket for anti-money laundering data governance work. This self-checking and early warning engine tool can release manual labor and focus the main energy of manual labor on later rectification or other more important things.
[0089] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
Claims
1. A self-checking and early warning engine tool for abnormal anti-money laundering data of financial institutions, characterized in that: include: A rule management module, which is used to manage multiple verification rules for data quality management of different financial institutions; A data verification module, used for receiving a target data file of a financial institution to be inspected, creating a verification task and a protocol file corresponding to the verification task according to the target data file, and storing the target data file and the protocol file in a receiving directory; Read the target data file from the receiving directory, perform batch verification on the target data file by running a batch according to the verification rule, extract abnormal data in the target data file that does not meet the verification rule, and generate a verification result; A data governance module, used to assign governance tasks to the abnormal data according to data ownership, and send the governance tasks to the corresponding financial institutions; Receive feedback on governance results and completion operations from the financial institutions that are responsible for the governance tasks; The task comparison module is used to compare the abnormal data with the governance results and visualize the comparison results; receive two selected verification tasks, the two verification tasks correspond to the same target data file in different time periods, compare the corresponding verification results of the two verification tasks, and visualize the abnormal data of the same target data file in different verification tasks respectively; The self-check and early warning engine tool adopts a B / S architecture, the self-check and early warning engine tool supports multiple legal persons and a head-branch-branch architecture, the front-end interactive interface of the self-check and early warning engine tool is developed using VUE technology components, and the data storage of the self-check and early warning engine tool adopts a MySQL database.
2. The self-checking and early warning engine tool for anti-money laundering abnormal data of financial institutions according to claim 1 is characterized in that: The verification rules include initialized built-in verification rules and verification rules flexibly configured by financial institutions according to their actual needs; the initialized built-in verification rules are summarized based on the regulatory agency's requirements for anti-money laundering on-site inspection data of financial institutions.
3. The self-checking and early warning engine tool for anti-money laundering abnormal data of financial institutions according to claim 1 is characterized in that: The verification rules include format verification rules, content compliance verification rules and logical rationality verification rules.
4. The self-checking and early warning engine tool for anti-money laundering abnormal data of financial institutions according to claim 1 is characterized in that: The format of the target data file is a csv text file, and the content format of the target data file is UTF-8 encoding. The amount of data in each target data file is less than or equal to 300 million; in the target data file, the field content is enclosed in half-width double quotes, and the fields are separated by half-width single vertical lines or commas; the content in the protocol file uses json format data, and the name of the protocol file uses Chinese, English, numbers, underscores, and hyphens, and the name length is less than or equal to 20 characters.
5. The self-checking and early warning engine tool for anti-money laundering abnormal data of financial institutions according to claim 1 is characterized in that: In the data verification module, when multiple target data files are received and multiple verification tasks and protocol files are created, all target data files are stored in a folder named with the current date in the receiving directory, each protocol file is named according to the corresponding verification task, and each protocol file is stored in a pre-agreed scanning directory in the receiving directory.
6. The self-checking and early warning engine tool for anti-money laundering abnormal data of financial institutions according to claim 1 is characterized in that: The data governance module is also used to: Sending the abnormal overview and details of the abnormal data to the corresponding financial institution; Send task processing deadline reminders to the corresponding financial institutions.
7. The self-checking and early warning engine tool for anti-money laundering abnormal data of financial institutions according to claim 1 is characterized in that: The self-checking early warning engine tool also includes: The verification result statistics module is used to visualize the verification results and display the specific distribution of the abnormal data during the visualization; receive the selected display dimension, and perform statistics and visualization on the verification results according to the display dimension.
8. The self-checking and early warning engine tool for abnormal anti-money laundering data of financial institutions according to claim 7 is characterized in that: The verification result statistics module is also used for: When displaying visually, the specific reasons why the verification failed are displayed for the target data files and fields that failed the verification; The input export condition is accepted, and the abnormal data in the verification result that meets the export condition is exported in batches.
