Supervision report generation method and device, electronic equipment and storage medium

Abstract

The invention discloses a supervision report generation method and device, electronic equipment and a storage medium, and relates to the technical field of big data or other related fields, and the method comprises the steps: obtaining supervision submission demands of N supervision organizations in a preset supervision period, and N is a positive integer; analyzing the N supervision submission demands to obtain a total collection demand; acquiring element information based on the total acquisition demand, and acquiring monitoring element data from a target database based on the acquiring element information to obtain a monitoring element data set, the target database being an internal database of each supervised financial institution; and for each supervision mechanism, generating a target supervision report based on the supervision submission demand and the monitoring element data set. Through the method and the device, the technical problem of slow response caused by large resource consumption due to repeated acquisition and repeated submission of financial institutions for data acquisition requirements of different supervision institutions in related technologies is solved.

Description

Technical Field

[0001] The present invention relates to the field of big data technology or other related fields, and in particular to a method for generating a regulatory report, a device thereof, an electronic device, and a storage medium. Background Art

[0002] In recent years, collaborative oversight among regulatory agencies has become a major trend in regulatory work. For regulatory work involving multiple regulatory agencies, regulatory agencies are required to regularly monitor regulated entities and report the results. To achieve this goal, each regulatory agency typically establishes a corresponding regulatory information system and provides specific regulatory content and reporting formats in the form of regulatory reporting requirements, either regularly or irregularly. For example, regulated entities may be required to upload data such as production status and equipment operating status, as well as provide documentation such as production logs and equipment maintenance records.

[0003] However, different regulatory agencies have different regulatory requirements for the same regulatory object. Therefore, the same regulatory object needs to provide different regulatory agencies with regulatory data and regulatory documents with different regulatory reporting requirements. In order to meet the differences in regulatory reporting requirements, existing technologies need to collect regulatory data and regulatory documents separately through multiple regulatory systems, and manually parse regulatory reporting requirements, and determine the regulatory content and regulatory document format based on the parsing results. In addition, during the regulatory cycle, regulatory agencies need to repeat the above operations many times. Therefore, the above operations are time-consuming, labor-intensive and inefficient, and it is difficult to meet the requirements of the rapid development of regulatory work.

[0004] To address the above-mentioned problems, no effective solutions have been proposed so far. Summary of the Invention

[0005] The main purpose of this application is to provide a method for generating regulatory reports and its device, electronic device, and storage medium, so as to at least solve the technical problem in related technologies that financial institutions face data collection requirements from different regulatory agencies and will repeatedly collect and submit data, which consumes a lot of resources and leads to slow response.

[0006] In order to achieve the above-mentioned purpose, according to one aspect of the present application, a method for generating regulatory reports is provided, which includes: obtaining the regulatory reporting requirements of N regulatory agencies within a preset regulatory cycle, wherein N is a positive integer; parsing the N regulatory reporting requirements to obtain a full collection requirement, wherein the full collection requirement is used to indicate the overall monitoring data requirements of all the regulatory agencies within the preset regulatory cycle; determining the collection element information based on the full collection requirement, and collecting monitoring element data from a target database based on the collection element information to obtain a monitoring element data set, wherein the target database refers to the internal database of each regulated financial institution; for each of the regulatory agencies, generating a target regulatory report based on the regulatory reporting requirement and the monitoring element data set.

[0007] Furthermore, the step of parsing N of the regulatory reporting requirements to obtain the full collection requirements includes: parsing each of the regulatory reporting requirements to obtain R monitoring element items required by each of the regulatory agencies, where R is a positive integer; after obtaining all of the monitoring element items required by the N regulatory agencies, merging similar items of all the monitoring element items based on a preset merging strategy to obtain the full collection requirements.

[0008] Furthermore, the preset merging strategy includes at least: a transaction link merging sub-strategy, which merges similar items of all the monitoring element items based on the preset merging strategy to obtain the step of the full collection requirement, including: obtaining the transaction link segment information of all the monitoring element items; based on the transaction link merging sub-strategy, comparing the transaction link segment information of all the monitoring element items, and merging the transaction link segments of the same link to obtain the simplest transaction segment collection requirement, wherein the simplest transaction segment collection requirement covers the transaction link segments required by all the monitoring element items and does not contain duplicate link segments.

[0009] Furthermore, the preset merging strategy also includes: a collection time period merging sub-strategy, which merges similar items of all the monitoring element items based on the preset merging strategy to obtain the full collection requirement, and also includes: obtaining the collection name and collection time period information of all the monitoring element items; based on the collection time period merging sub-strategy, comparing the collection time period information of all the monitoring element items, and merging the collection time periods of the same collection name to obtain the minimum time range collection requirement, wherein the minimum time range collection requirement covers the collection time period required by each collection name, and does not contain repeated time periods.

[0010] Furthermore, the preset merging strategy also includes: a collection range merging sub-strategy, which merges similar items of all the monitoring element items based on the preset merging strategy to obtain the full collection requirement, including: obtaining the collection name and collection range information of all the monitoring element items; based on the collection range merging sub-strategy, comparing the collection range information of all the monitoring element items, and merging the collection ranges of the same collection name to obtain the minimum collection range requirement, wherein the minimum collection range requirement covers the collection range required by all the monitoring element items and does not contain repeated collection ranges.

[0011] Furthermore, the step of determining the collection element information based on the full collection requirement includes: for each of the monitoring element items in the full collection requirement, determining the transaction business where the monitoring element item is located, and determining the transaction link information of the transaction business; mapping the monitoring element item to the service node in the transaction link based on the transaction link information, and determining the node identity of each of the service nodes; based on the node identity, using the node parameters on the service node as the collection element to obtain the collection element information.

[0012] Furthermore, based on the node identity, the node parameters on the service node are used as collection elements to obtain the collection element information, including: for each of the service nodes, when the node identity indicates that the service node is a master node, determining the node parameters on the master node as master variable parameters; determining the master variable parameters as collection elements, and integrating the monitoring element items associated with the master variable parameters to obtain the collection element information.

[0013] Furthermore, the step of taking the node parameters on the service node as acquisition elements based on the node identity to obtain the acquisition element information also includes: when the node identity indicates that the service node is not the main node and there is a data dependency relationship between the service node and the main node, determining the node parameters on the service node as dependent variable parameters; determining the dependent variable parameters as derivable elements, wherein the monitoring element items associated with the derivable elements are derived based on the main variable parameters and the data dependency relationship after obtaining the main variable parameters associated with the dependent variable parameters; when the node identity indicates that the service node is not the main node and there is no data dependency relationship between the service node and the main node, determining the node parameters on the service node as independent parameters; determining the independent parameters as acquisition elements, and integrating the monitoring element items associated with the independent parameters to obtain the acquisition element information.

[0014] Furthermore, for each of the regulatory agencies, the step of generating a target regulatory report based on the regulatory reporting requirements and the monitoring element data set includes: for each of the regulatory agencies, extracting the element conversion information and element conversion identifier in the regulatory reporting requirements, wherein the element conversion information includes data conversion instructions, and the element conversion identifier is used to record the data reporting format required by the regulatory agency; performing data screening on the monitoring element data set based on the element conversion information to obtain the target regulatory data required by the regulatory agency; performing format conversion on the target regulatory data based on the element conversion identifier to obtain target reporting data, and generating the target regulatory report based on the target reporting data.

[0015] In order to achieve the above-mentioned purpose, according to another aspect of the present application, a device for generating a regulatory report is also provided, which includes: an acquisition unit, used to obtain the regulatory reporting requirements of N regulatory agencies within a preset regulatory cycle, wherein N is a positive integer; a parsing unit, used to parse the N regulatory reporting requirements to obtain a full collection requirement, wherein the full collection requirement is used to indicate the overall monitoring data requirements of all the regulatory agencies within the preset regulatory cycle; a determination unit, used to determine the collection element information based on the full collection requirement, and collect monitoring element data from the target database based on the collection element information to obtain a monitoring element data set, wherein the target database refers to the internal database of each regulated financial institution; a generation unit, used to generate a target regulatory report for each of the regulatory agencies based on the regulatory reporting requirements and the monitoring element data set.

[0016] Furthermore, the parsing unit includes: a parsing module for parsing each of the regulatory reporting requirements to obtain R monitoring element items required by each regulatory agency, where R is a positive integer; a processing module for merging similar items of all the monitoring element items based on a preset merging strategy after obtaining all of the monitoring element items required by N regulatory agencies to obtain the full collection requirement.

[0017] Furthermore, the preset merging strategy includes at least: a transaction link merging sub-strategy.

[0018] Furthermore, the processing module includes: a first acquisition submodule, used to obtain the transaction link segment information of all the monitored element items; a first merging submodule, used to compare the transaction link segment information of all the monitored element items based on the transaction link merging sub-strategy, and merge the transaction link segments of the same link to obtain the simplest transaction segment collection requirements, wherein the simplest transaction segment collection requirements cover the transaction link segments required by all the monitored element items and do not contain duplicate link segments.

[0019] Furthermore, the preset merging strategy also includes: a collection time period merging sub-strategy.

[0020] Furthermore, the processing module also includes: a second acquisition submodule, used to obtain the collection items and collection time period information of all the monitoring element items; a second merging submodule, used to compare the collection time period information of all the monitoring element items based on the collection time period merging sub-strategy, and merge the collection time periods of the same collection items to obtain the minimum time range collection requirement, wherein the minimum time range collection requirement covers the collection time period required by each of the collection items and does not contain repeated time periods.

[0021] Furthermore, the preset merging strategy also includes: a collection range merging sub-strategy.

[0022] Furthermore, the processing module includes: a third acquisition submodule, used to obtain the collection name and collection range information of all the monitoring element items; a third merging submodule, used to compare the collection range information of all the monitoring element items based on the collection range merging sub-strategy, and merge the collection ranges of the same collection name to obtain the minimum collection range requirement, wherein the minimum collection range requirement covers the collection range required by all the monitoring element items and does not contain repeated collection ranges.

[0023] Furthermore, the determination unit includes: a first determination module, used to determine the transaction business to which the monitored element item is located, and determine the transaction link information of the transaction business for each monitored element item in the full collection requirement; a second determination module, used to map the monitored element item to the service node in the transaction link based on the transaction link information, and determine the node identity of each service node; a third determination module, used to use the node parameters on the service node as the collection element based on the node identity to obtain the collection element information.

[0024] Furthermore, the third determination module includes: a first determination submodule, used to determine, for each of the service nodes, that the node parameters on the main node are main variable parameters when the node identity indicates that the service node is a main node; a second determination submodule, used to determine the main variable parameters as acquisition elements, and integrate the monitoring element items associated with the main variable parameters to obtain the acquisition element information.

[0025] Furthermore, the third determination module also includes: a third determination sub-module, used to determine that the node parameter on the service node is a dependent variable parameter when the node identity indicates that the service node is not the main node and there is a data dependency relationship between the service node and the main node; a fourth determination sub-module, used to determine the dependent variable parameter as a derivable element, wherein the monitoring element item associated with the derivable element is derived based on the main variable parameter and the data dependency relationship after obtaining the main variable parameter associated with the dependent variable parameter; a fifth determination sub-module, used to determine that the node parameter on the service node is an independent parameter when the node identity indicates that the service node is not the main node and there is no data dependency relationship between the service node and the main node; a sixth determination sub-module, used to determine the independent parameter as an acquisition element, and integrate the monitoring element item associated with the independent parameter to obtain the acquisition element information.

[0026] Furthermore, the generation unit includes: an extraction module, used to extract the element conversion information and element conversion identifier in the regulatory reporting requirements for each regulatory agency, wherein the element conversion information includes data conversion instructions, and the element conversion identifier is used to record the data reporting format required by the regulatory agency; a screening module, used to perform data screening on the monitoring element data set based on the element conversion information to obtain the target regulatory data required by the regulatory agency; a generation module, used to perform format conversion on the target regulatory data based on the element conversion identifier to obtain target reporting data, and generate the target regulatory report based on the target reporting data.

[0027] In order to achieve the above-mentioned purpose, according to another aspect of the present application, a computer-readable storage medium is also provided, wherein the computer-readable storage medium includes a stored computer program, wherein when the computer program is running, the device where the computer-readable storage medium is located is controlled to execute any one of the above-mentioned methods for generating regulatory reports.

[0028] In order to achieve the above-mentioned purpose, according to another aspect of the present application, an electronic device is also provided, including one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method for generating regulatory reports described in any one of the above-mentioned items.

[0029] In the present invention, a method for generating regulatory reports is proposed. First, the regulatory reporting requirements of N regulatory agencies within a preset regulatory cycle are obtained, where N is a positive integer. The N regulatory reporting requirements are then parsed to obtain a full collection requirement, where the full collection requirement is used to indicate the overall monitoring data requirements of all regulatory agencies within the preset regulatory cycle. Then, based on the full collection requirement, collection element information is determined, and based on the collection element information, monitoring element data is collected from a target database to obtain a monitoring element data set, where the target database refers to the internal database of each regulated financial institution. Finally, for each regulatory agency, a target regulatory report is generated based on the regulatory reporting requirement and the monitoring element data set.

[0030] In the present invention, the method of integrating full regulatory requirements is adopted, and the purpose of optimizing resource utilization is achieved through precise analysis and efficient collection, thereby realizing the technical effect of rapid response and reduction of repetitive work. Specifically, by collecting and analyzing the reporting requirements of multiple regulatory agencies within a preset period, a unified full-scale collection requirement is determined, avoiding the repetitive work of collecting data for each regulatory agency separately, and efficiently collecting monitoring element data from the internal database (target database) of the financial institution according to the determined collection element information to form a monitoring element data set. According to the specific needs of each regulatory agency, relevant data is called from the monitoring element data set and converted according to its specific reporting format to generate corresponding regulatory reports. This not only reduces the repetitiveness of data collection and reduces the consumption of financial institution resources, but also speeds up the report generation, improves the flexibility and efficiency of financial institutions in responding to regulatory needs, and thus solves the technical problem in related technologies that financial institutions will repeatedly collect and report data in response to data collection requirements of different regulatory agencies, which consumes a lot of resources and leads to slow response. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] The accompanying drawings, which constitute part of this application, are intended to provide a further understanding of this application. The exemplary embodiments and descriptions of this application are intended to explain this application and do not constitute an improper limitation on this application. In the accompanying drawings:

[0032] Figure 1 A hardware structure block diagram of a computer terminal for implementing a method for generating a supervisory report is shown;

[0033] Figure 2 is a flow chart of an optional method for generating a supervision report according to an embodiment of the present invention;

[0034] Figure 3 is a flowchart of an optional transaction link merging method according to an embodiment of the present invention;

[0035] Figure 4is a flow chart of an optional method for merging acquisition time periods according to an embodiment of the present invention;

[0036] Figure 5 is a flow chart of an optional acquisition range merging method according to an embodiment of the present invention;

[0037] Figure 6 is a schematic diagram of an optional supervisory report generation device according to an embodiment of the present invention;

[0038] Figure 7 The present invention is a structural block diagram of an electronic device for executing a method for generating a supervision report according to an embodiment of the present invention. DETAILED DESCRIPTION

[0039] In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the embodiments described are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of the present invention.

[0040] It should be noted that the terms "first", "second", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate, so that the embodiments of the present invention 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 inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0041] It should be noted that the method for generating regulatory reports and the device thereof in this application can be used in the field of big data technology to efficiently manage and intelligently analyze the operating data of financial institutions, and can also be used in any field other than the field of big data technology to efficiently manage and intelligently analyze the operating data of financial institutions. This application does not limit the application field of the method for generating regulatory reports and the device thereof.

[0042] It should be noted that the relevant information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, storage, processing, transmission, provision, disclosure, use and processing of the relevant data comply with the laws, regulations and standards of the relevant regions, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or refuse. For example, an interface is set up between this system and the relevant users or institutions. Before obtaining relevant information, it is necessary to send an acquisition request to the aforementioned user or institution through the interface, and obtain relevant information after receiving the consent information fed back by the aforementioned user or institution.

[0043] The information collection (for example, user voice, video, and text collection) and analysis operations involved in this application have provided users with corresponding operation entrances when they are executed, allowing users to choose to agree or reject the automated decision-making results; if the user chooses to reject, the expert decision-making process will be entered.

[0044] The following embodiments of the present invention can be applied to various systems, applications, and devices that require data integration and report generation, enabling optimization and automation of financial institutions' data reporting processes. The present invention uses intelligent parsing algorithms to analyze regulatory reporting requirements and then, based on the determined full data collection requirements, guides efficient data collection from the financial institution's internal database, enabling better resource optimization and avoiding duplicate data collection and processing.

[0045] The present invention can also speed up the generation of regulatory reports, ensure that financial institutions can respond to regulatory agencies' reporting requirements in a timely and accurate manner, improve the efficiency and quality of data reporting, and support financial institutions in operating stably in an increasingly complex regulatory environment.

[0046] The present invention will be described in detail below with reference to various embodiments.

[0047] Example 1

[0048] According to an embodiment of the present invention, an embodiment of a method for generating a regulatory report is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0049] The method embodiment provided in the first embodiment of the present invention may be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 1The hardware structure block diagram of a computer terminal (or mobile device) for implementing a method for generating a regulatory report is shown. Figure 1 As shown, the computer terminal 10 (or mobile device) may include one or more (illustrated as 102a, 102b, ..., 102n in the figure) processors 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission device 106 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera. It will be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 1 More or fewer components than shown, or with Figure 1 Different configurations shown.

[0050] It should be noted that the one or more processors 102 and / or other data processing circuits described above may generally be referred to herein as "data processing circuitry". The data processing circuitry may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuitry may be a single independent processing module, or may be incorporated in whole or in part into any of the other components of the computer terminal 10 (or mobile device). As described in the embodiments of the present application, the data processing circuitry serves as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0051] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the method for generating regulatory reports in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, realizing the above-mentioned method for generating regulatory reports. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include a memory remotely located relative to the processor 102, and these remote memories may be connected to the computer terminal 10 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0052] The transmission device 106 is configured to receive or transmit data via a network. A specific example of the aforementioned network may include a wireless network provided by the communications provider of the computer terminal 10. In one embodiment, the transmission device 106 includes a network interface controller (NIC), which can be connected to other network devices via a base station to enable communication with the Internet. In another embodiment, the transmission device 106 may be a radio frequency (RF) module, which is configured to communicate with the Internet wirelessly.

[0053] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 10 (or mobile device).

[0054] Under the above operating environment, the present invention provides Figure 2 The method for generating regulatory reports shown in the figure is implemented by a regulatory report generation system, which is combined with big data analysis technology and is used in financial regulatory scenarios. In particular, it solves the problems of repeated collection, high resource consumption and low response efficiency when financial institutions face the diverse data reporting requirements of different regulatory agencies.

[0055] The embodiments of the present invention use intelligent demand integration and data reuse, specifically including the steps of obtaining full collection requirements, determining collection element information, intelligently collecting monitoring element data, and generating target regulatory reports based on regulatory requirements, to achieve the purpose of improving data collection efficiency, reducing resource consumption, and speeding up report generation, thereby ensuring that financial institutions can respond to regulatory requirements efficiently and accurately and support their compliance operations in a complex regulatory environment.

[0056] The embodiment of the present invention is described in detail below with reference to various specific steps.

[0057] Figure 2 is a flow chart of an optional method for generating a supervisory report according to an embodiment of the present invention, such as Figure 2 As shown, the method includes the following steps:

[0058] Step S201: Obtain regulatory reporting requirements of N regulatory agencies within a preset regulatory period, where N is a positive integer.

[0059] Specifically, the preset regulatory cycle refers to the time period for data reporting and regulatory activities agreed upon between financial institutions and regulatory authorities. It can be fixed, such as daily, weekly, monthly or quarterly, or it can be dynamic and adjusted according to the specific requirements of the regulatory authorities and changes in the market environment.

[0060] Regulatory agencies are organizations responsible for overseeing, managing, and guiding the operations of financial institutions. Regulatory reporting requirements include specific requirements for various data reports and statistical information that regulatory agencies require financial institutions to submit within a pre-set regulatory cycle. These typically include, but are not limited to, data types (e.g., balance sheets, income statements, cash flow statements, risk indicators, and compliance status), data formats (e.g., Excel, CSV, XML), timeframes, reporting frequency, and specific fields.

[0061] In step S201, detailed requirements for data reporting within a specific time frame from multiple regulatory agencies are collected and organized. Through comprehensive understanding and integration, a more efficient data processing process that is more compliant with regulatory standards can be designed, avoiding compliance risks caused by inaccurate understanding or missed requirements. At the same time, it also optimizes resource allocation for data collection and processing, reduces unnecessary duplication of work, and improves overall regulatory response efficiency.

[0062] Step S202 : Parse N regulatory reporting requirements to obtain a full data collection requirement, wherein the full data collection requirement is used to indicate the overall monitoring data requirements of all regulatory agencies within a preset regulatory cycle.

[0063] Specifically, full data collection requirements refer to a comprehensive and complete list of data collection requirements obtained after analyzing and merging the regulatory reporting requirements of all N regulatory agencies within a preset regulatory cycle, covering all data types, fields, indicators and time ranges that may be required by regulatory agencies, ensuring that financial institutions can meet the data reporting requirements of all regulatory agencies at one time when collecting data, avoiding duplication of work and waste of resources caused by responding to the needs of each regulatory agency individually.

[0064] The acquisition of full collection requirements in step S202 is based on in-depth analysis and cross-comparison of requirements submitted by multiple regulatory agencies. The algorithm identifies the commonalities and differences in the requirements of different regulatory agencies, thereby refining a minimum data set that includes the requirements of all regulatory agencies and avoids unnecessary data redundancy for efficient collection requirements.

[0065] For example, if one regulator requires the collection of total loan data for the first quarter of 2023, and another regulator requires the collection of total deposit data for the same time period, then the full collection requirement will include these two data items, ensuring that the data needs of both regulators can be covered simultaneously in one data collection process.

[0066] In order to obtain the most concise and comprehensive full-quantity collection requirements, it is necessary to merge similar items for all monitoring element items. Optionally, step S202 includes: parsing each regulatory reporting requirement to obtain R monitoring element items required by each regulatory agency, where R is a positive integer; after obtaining all monitoring element items required by N regulatory agencies, merging similar items for all monitoring element items based on a preset merging strategy to obtain the full-quantity collection requirements.

[0067] Specifically, the preset merging strategy includes: a transaction link merging sub-strategy, a collection time period merging sub-strategy, and a collection range merging sub-strategy.

[0068] Figure 3 is a flow chart of an optional transaction link merging method according to an embodiment of the present invention. Figure 3 As shown, the method includes the following steps:

[0069] Step S301, obtaining transaction link segment information of all monitored element items;

[0070] In step S302, based on the transaction link merging sub-strategy, the transaction link segment information of all monitored element items is compared, and the transaction link segments of the same link are merged to obtain the simplest transaction segment collection requirements, where the simplest transaction segment collection requirements cover the transaction link segments required by all monitored element items and do not contain duplicate link segments.

[0071] It's important to note that a transaction chain refers to the series of steps or operational processes from the initiation of a transaction to its final outcome within a financial institution. Different regulators require different lengths of transaction chains to be collected. For example, some institutions may focus on the entire process from transaction initiation to funds arrival, while others may only focus on key steps. The transaction chain consolidation sub-strategy aims to identify and consolidate identical or duplicate chain information by comparing and analyzing transaction chain segments across all monitored elements, thereby achieving the minimum required transaction chain segment collection.

[0072] In step S301, the transaction link description related to each monitoring element item is extracted from the reporting requirements of N regulatory agencies, including the starting point of the transaction, the links passed, the systems or departments involved, etc. In step S302, these transaction link information are compared and analyzed to identify the same or repeated transaction link segments, and the widest or longest link covering all requirements is used as the final collection requirement, thereby avoiding redundant operations due to the collection of the same link required by different regulatory agencies.

[0073] Figure 4 FIG. 1 is a flow chart of an optional method for merging acquisition time periods according to an embodiment of the present invention. Figure 4 As shown, the method includes the following steps:

[0074] Step S401: Obtain the collection items and collection time period information of all monitoring elements;

[0075] In step S402, based on the collection time period merging sub-strategy, the collection time period information of all monitoring element items is compared, and the collection time periods of the same collection name are merged to obtain the minimum time range collection requirement, wherein the minimum time range collection requirement covers the collection time period required by each collection name and does not contain repeated time periods.

[0076] It should be noted that regulatory agencies' requirements for data collection time periods vary depending on regulatory objectives and schedules. The collection time period merging sub-strategy focuses on integrating the collection time period information for all monitoring elements to determine a minimum time range that meets all regulatory requirements while avoiding duplicate collection.

[0077] In step S401, the name of each monitoring element item and the corresponding collection time period requirement are extracted from the regulatory reporting requirements. For example, agency A may require daily collection, while agency B requires collection every Thursday, agency C requires collection at the beginning of each month, etc. In step S402, the collection time periods of monitoring element items with the same collection name are compared to determine the maximum time range required by all regulatory agencies for a specific data item. For example, in the above example, for data required daily, the final collection time period will cover the entire preset regulatory cycle, while for data of some specific frequencies, the time range will be determined based on the earliest start time and the latest end time.

[0078] Figure 5 FIG. 1 is a flow chart of an optional acquisition range merging method according to an embodiment of the present invention. Figure 5 As shown, the method includes the following steps:

[0079] Step S501: Acquire the collection name and collection scope information of all monitoring elements;

[0080] In step S502, based on the collection scope merging sub-strategy, the collection scope information of all monitoring elements is compared, and the collection scopes of the same collection name are merged to obtain the minimum collection scope requirement, wherein the minimum collection scope requirement covers the collection scope required by all monitoring elements and does not contain duplicate collection scopes.

[0081] It's important to note that collection scope refers to the extent of data coverage, such as specific customer types, product areas, or geographic regions. Different regulators may have different collection scope requirements for the same type of data. The collection scope consolidation sub-strategy aims to identify and consolidate identical or overlapping collection scopes by comparing and analyzing the collection scope information of all monitoring elements. Ultimately, it determines the minimum collection scope requirement, ensuring full compliance with regulatory requirements while avoiding unnecessary data collection.

[0082] In step S501, the name of each monitoring element and its corresponding collection scope requirement are extracted from the regulatory reporting requirements. For example, if one regulatory agency requires the collection of all individual customer data, while another requires the collection of all corporate customer data, step S502 compares the collection scopes of the monitoring elements with the same collection name to determine the minimum collection scope that covers all regulatory agency requirements. For example, in the above example, if regulatory agency A requires the collection of all individual customer data and regulatory agency B requires the collection of all corporate customer data, the combined collection scope requirements will cover all individual and corporate customer data, thereby ensuring comprehensive data collection.

[0083] Step S203 : determining the collected element information based on the full collection requirement, and collecting the monitoring element data from the target database based on the collected element information to obtain a monitoring element data set, wherein the target database refers to the internal database of each regulated financial institution.

[0084] Specifically, the collection element information is used to guide the accurate acquisition of specific information of the required monitoring data from the target database, which usually includes but is not limited to: data type information (such as financial data, transaction data, customer information data, etc.), field information (such as account number, transaction amount, date and time stamp, etc.), data indicator information (such as non-performing loan ratio, capital adequacy ratio, liquidity ratio, etc.), data collection frequency (such as daily, weekly, monthly, etc.) and data collection scope (such as the type of customers involved, product types, business departments, etc.).

[0085] Monitoring element data is extracted from the target database based on the collected element information and is directly linked to regulatory reporting requirements. It is used to reflect the financial status, operating results, risk management capabilities, and compliance of financial institutions within the preset regulatory cycle. The monitoring element dataset integrates and organizes all monitoring element data according to the requirements of the collected element information to form a structured data set. It contains all the data and information that all regulatory agencies need to monitor within the preset regulatory cycle, providing the necessary data foundation for subsequent report generation and data reporting.

[0086] A target database refers to a financial institution's internal database system that stores operational data, customer information, transaction records, financial statements, and other information. It is the core of a financial institution's data management and contains all the critical data required for its operations. It can be a single database or a collection of multiple databases, categorized and stored according to data type and purpose. In the context of this invention, the target database specifically refers to the internal database of each regulated financial institution, i.e., the system used by the financial institution to store and manage its business data.

[0087] Optionally, the step of determining the collection element information based on the full collection requirement includes: for each monitoring element item in the full collection requirement, determining the transaction business where the monitoring element item is located, and determining the transaction link information of the transaction business; mapping the monitoring element item to the service node in the transaction link based on the transaction link information, and determining the node identity of each service node; based on the node identity, using the node parameters on the service node as the collection element to obtain the collection element information.

[0088] It should be noted that the transactional businesses in which monitoring elements are located include, but are not limited to, loan issuance, deposit operations, and transaction settlement. This allows for further identification of the transaction chain information for each business, including the various systems and service nodes through which data flows, as well as the logical relationships between them. For example, in the loan issuance business, data may need to be processed through multiple service nodes, including customer information verification, loan approval, and loan issuance.

[0089] After determining the transaction link information, the monitoring element items are mapped to specific service nodes in the transaction link. By comparing and analyzing the monitoring element items with the functions and data processing logic of each service node in the transaction link, it is identified which service node or nodes the monitoring element items are directly associated with, and then the node identity is determined.

[0090] Node identity refers to the role a service node plays in the transaction chain and its contribution to data processing. Based on node identity, service nodes can be categorized as "master nodes," "slave nodes," or "independent nodes." Master nodes are key nodes in the transaction chain, responsible for generating and processing critical data. Slave nodes rely on the master node's data for further processing or analysis. Independent nodes are independent of other nodes and do not rely on other data for processing. Determining the node identity of each service node facilitates the subsequent adoption of different data collection strategies based on the node's different roles, thereby optimizing data collection efficiency and resource allocation.

[0091] For the master node, node parameters are usually core data, directly related to the execution and results of the business, and will be directly determined as collection elements; for the slave node, if the node parameters depend on the master node parameters, they are regarded as derivable elements and do not need to be directly collected. Instead, they are obtained through data deduction and calculation after obtaining the master node parameters; for independent nodes, node parameters will also be determined as collection elements.

[0092] Optionally, the step of taking the node parameters on the service node as acquisition elements based on the node identity to obtain acquisition element information includes: for each service node, when the node identity indicates that the service node is a master node, determining the node parameters on the master node as master variable parameters; determining the master variable parameters as acquisition elements, and integrating the monitoring element items associated with the master variable parameters to obtain acquisition element information.

[0093] Optionally, the step of taking the node parameters on the service node as collection elements based on the node identity to obtain collection element information also includes: when the node identity indicates that the service node is not the main node and there is a data dependency relationship between the service node and the main node, determining the node parameters on the service node as dependent variable parameters; determining the dependent variable parameters as derivable elements, wherein the monitoring element items associated with the derivable elements are derived based on the main variable parameters and the data dependency relationship after obtaining the main variable parameters associated with the dependent variable parameters; when the node identity indicates that the service node is not the main node and there is no data dependency relationship between the service node and the main node, determining the node parameters on the service node as independent parameters; determining the independent parameters as collection elements, and integrating the monitoring element items associated with the independent parameters to obtain collection element information.

[0094] Based on the full-volume collection requirements, the embodiment of the present invention deeply analyzes the status and role of monitoring elements in transaction business, identifies transaction link information, maps it to specific service nodes, analyzes node identities, and finally determines the collection element information based on the node identity of each service node, ensuring the precise positioning of data collection and avoiding unnecessary access and processing of data, thereby greatly improving the efficiency of data collection and reducing resource consumption, providing financial institutions with an efficient data collection and management solution while meeting regulatory requirements.

[0095] At the same time, by distinguishing between master nodes, slave nodes and independent nodes, the embodiments of the present invention can also adopt differentiated collection strategies for different types of data, further improving the flexibility and intelligence level of data collection, and supporting financial institutions to achieve compliance operations and optimization of risk management in a complex and changing regulatory environment.

[0096] Step S204: For each regulatory agency, a target regulatory report is generated based on the regulatory reporting requirements and the monitoring element data set.

[0097] In order to generate regulatory reports that meet their respective requirements and satisfy the specific format and content requirements of regulatory reporting, optionally, step S204 includes: for each regulatory agency, extracting element conversion information and element conversion identifiers in the regulatory reporting requirements, wherein the element conversion information includes data conversion instructions, and the element conversion identifier is used to record the data reporting format required by the regulatory agency; based on the element conversion information, the monitoring element data set is screened to obtain the target regulatory data required by the regulatory agency; based on the element conversion identifier, the target regulatory data is format-converted to obtain target reporting data, and a target regulatory report is generated based on the target reporting data.

[0098] It's important to note that element conversion information represents the regulator's specific requirements for the required data, including but not limited to data filtering criteria, calculation logic, and aggregation methods. These information constitutes data conversion instructions, providing guidance on how to accurately obtain the target regulatory data from the monitored element dataset. For example, a regulator may require statistics on only the total deposits of a specific type of account within a specific time period. This requires the data conversion instructions to specify the two filtering criteria, time period and account type.

[0099] The element conversion identifier is used to record the data reporting format required by the regulatory agency, such as Excel, PDF, XML, etc., to ensure that the generated regulatory report can be submitted in a form acceptable to the regulatory agency.

[0100] Data screening is the process of accurately locating and extracting data subsets that meet regulatory reporting requirements from the monitoring element data set based on the data conversion instructions in the extracted element conversion information. It involves data filtering, classification, sorting, calculation and other operations to ensure that the extracted target regulatory data not only covers all indicators required by the regulatory agency, but also meets multi-dimensional screening requirements such as time range, data type, and specific conditions.

[0101] Format conversion involves reorganizing, encoding, and presenting data to ensure that the generated target reporting data matches the regulatory body's report template or data interface. For example, if the regulatory body requires data to be submitted in XML format, format conversion involves converting the target regulatory data from the internal database format to XML. This involves mapping data fields, converting data types, and restructuring data structures.

[0102] Generating target regulatory reports is to integrate the above-mentioned target reporting data after screening and format conversion into formal report documents in accordance with the specific needs and format requirements of the regulatory agency. It involves data aggregation, chart generation, text compilation, etc., to ensure that the generated regulatory reports contain complete information of all target regulatory data and meet the format consistency and standardization requirements.

[0103] Through the above steps S201 to S204, the regulatory reporting requirements of N regulatory agencies within the preset regulatory cycle can be first obtained, where N is a positive integer, and then the N regulatory reporting requirements are parsed to obtain the full collection requirements, where the full collection requirements are used to indicate the overall monitoring data requirements of all regulatory agencies within the preset regulatory cycle, and then the collection element information is determined based on the full collection requirements, and the monitoring element data is collected from the target database based on the collection element information to obtain a monitoring element data set, where the target database refers to the internal database of each regulated financial institution, and finally, for each regulatory agency, a target regulatory report is generated based on the regulatory reporting requirements and the monitoring element data set.

[0104] In an embodiment of the present invention, a method of integrating full regulatory requirements is adopted, and the purpose of optimizing resource utilization is achieved through precise analysis and efficient collection, thereby realizing the technical effect of rapid response and reduction of repetitive work. Specifically, by collecting and analyzing the reporting requirements of multiple regulatory agencies within a preset period, a unified full collection requirement is determined, thereby avoiding the repetitive work of collecting data separately for each regulatory agency. According to the determined collection element information, monitoring element data is efficiently collected from the internal database (target database) of the financial institution to form a monitoring element data set. According to the specific needs of each regulatory agency, relevant data is called from the monitoring element data set and converted according to its specific reporting format to generate corresponding regulatory reports. This not only reduces the repetitiveness of data collection and reduces the consumption of financial institution resources, but also speeds up the speed of report generation, improves the flexibility and efficiency of financial institutions in responding to regulatory needs, and thus solves the technical problem in related technologies that financial institutions will repeatedly collect and report data in response to data collection requirements of different regulatory agencies, which consumes a lot of resources and leads to slow response.

[0105] Example 2

[0106] An embodiment of the present invention also provides a device for generating a regulatory report. It should be noted that the device for generating a regulatory report in an embodiment of the present invention includes multiple implementation units, which can be used to execute the method for generating a regulatory report provided in the above-mentioned embodiment one, and each implementation unit corresponds to each implementation step in the above-mentioned embodiment one.

[0107] Figure 6 is a schematic diagram of an optional supervisory report generation device according to an embodiment of the present invention, such as Figure 6 As shown, the device may include: an acquisition unit 61, a parsing unit 62, a determination unit 63, and a generation unit 64.

[0108] The acquisition unit 61 is configured to acquire regulatory reporting requirements of N regulatory agencies within a preset regulatory period, where N is a positive integer.

[0109] The parsing unit 62 is used to parse N regulatory reporting requirements to obtain a full data collection requirement, wherein the full data collection requirement is used to indicate the overall monitoring data requirements of all regulatory agencies within a preset regulatory cycle.

[0110] The determination unit 63 is configured to determine the collected element information based on the full collection requirement, and collect the monitoring element data from the target database based on the collected element information to obtain a monitoring element data set, wherein the target database refers to the internal database of each regulated financial institution.

[0111] The generating unit 64 is configured to generate a target regulatory report for each regulatory agency based on regulatory reporting requirements and a monitoring element data set.

[0112] The above-mentioned regulatory report generation device can first obtain the regulatory reporting requirements of N regulatory agencies within a preset regulatory cycle through the acquisition unit 61, where N is a positive integer, and then parse the N regulatory reporting requirements through the parsing unit 62 to obtain a full collection requirement, wherein the full collection requirement is used to indicate the overall monitoring data requirements of all regulatory agencies within the preset regulatory cycle, and then determine the collection element information based on the full collection requirement through the determination unit 63, and collect monitoring element data from the target database based on the collection element information to obtain a monitoring element data set, wherein the target database refers to the internal database of each regulated financial institution, and finally generate a target regulatory report for each regulatory agency based on the regulatory reporting requirement and the monitoring element data set through the generation unit 64.

[0113] In an embodiment of the present invention, the method of integrating full regulatory requirements is adopted, and the purpose of optimizing resource utilization is achieved through precise analysis and efficient collection, thereby realizing the technical effect of rapid response and reduction of repetitive work. Specifically, by collecting and analyzing the reporting requirements of multiple regulatory agencies within a preset period, a unified full collection requirement is determined, thereby avoiding the repetitive work of collecting data for each regulatory agency separately. According to the determined collection element information, monitoring element data is efficiently collected from the internal database (target database) of the financial institution to form a monitoring element data set. According to the specific needs of each regulatory agency, relevant data is called from the monitoring element data set and converted according to its specific reporting format to generate corresponding regulatory reports. This not only reduces the repetitiveness of data collection and reduces the consumption of financial institution resources, but also speeds up the speed of report generation, improves the flexibility and efficiency of financial institutions in responding to regulatory needs, and thus solves the technical problem in related technologies that financial institutions will repeatedly collect and report data in response to data collection requirements of different regulatory agencies, which consumes a lot of resources and leads to slow response.

[0114] Optionally, the parsing unit includes: a parsing module for parsing each regulatory reporting requirement to obtain R monitoring element items required by each regulatory agency, where R is a positive integer; a processing module for merging similar items of all monitoring element items based on a preset merging strategy after obtaining all monitoring element items required by N regulatory agencies to obtain full collection requirements.

[0115] Optionally, the preset merging strategy includes at least: a transaction link merging sub-strategy.

[0116] Optionally, the processing module includes: a first acquisition sub-module, used to obtain the transaction link segment information of all monitored element items; a first merging sub-module, used to compare the transaction link segment information of all monitored element items based on the transaction link merging sub-strategy, and merge the transaction link segments of the same link to obtain the simplest transaction segment collection requirements, wherein the simplest transaction segment collection requirements cover the transaction link segments required by all monitored element items and do not contain duplicate link segments.

[0117] Optionally, the preset merging strategy further includes: a collection time period merging sub-strategy.

[0118] Optionally, the processing module also includes: a second acquisition submodule, used to obtain the collection items and collection time period information of all monitoring element items; a second merging submodule, used to compare the collection time period information of all monitoring element items based on the collection time period merging sub-strategy, and merge the collection time periods of the same collection items to obtain the minimum time range collection requirement, wherein the minimum time range collection requirement covers the collection time period required by each collection item and does not contain repeated time periods.

[0119] Optionally, the preset merging strategy further includes: a collection range merging sub-strategy.

[0120] Optionally, the processing module includes: a third acquisition sub-module, used to obtain the collection name and collection range information of all monitoring element items; a third merging sub-module, used to compare the collection range information of all monitoring element items based on the collection range merging sub-strategy, and merge the collection ranges of the same collection name to obtain the minimum collection range requirement, wherein the minimum collection range requirement covers the collection range required by all monitoring element items and does not contain repeated collection ranges.

[0121] Optionally, the determination unit includes: a first determination module, used to determine the transaction business to which the monitoring element item is located for each monitoring element item in the full collection requirement, and determine the transaction link information of the transaction business; a second determination module, used to map the monitoring element item to the service node in the transaction link based on the transaction link information, and determine the node identity of each service node; a third determination module, used to use the node parameters on the service node as the collection element based on the node identity to obtain the collection element information.

[0122] Optionally, the third determination module includes: a first determination submodule, used to determine, for each service node, that the node parameters on the main node are main variable parameters when the node identity indicates that the service node is a main node; a second determination submodule, used to determine the main variable parameters as acquisition elements, and integrate the monitoring element items associated with the main variable parameters to obtain acquisition element information.

[0123] Optionally, the third determination module also includes: a third determination sub-module, used to determine that the node parameters on the service node are dependent variable parameters when the node identity indicates that the service node is not the main node and there is a data dependency relationship between the service node and the main node; a fourth determination sub-module, used to determine the dependent variable parameters as derivable elements, wherein the monitoring element items associated with the derivable elements are derived based on the main variable parameters and the data dependency relationship after obtaining the main variable parameters associated with the dependent variable parameters; a fifth determination sub-module, used to determine that the node parameters on the service node are independent parameters when the node identity indicates that the service node is not the main node and there is no data dependency relationship between the service node and the main node; a sixth determination sub-module, used to determine the independent parameters as acquisition elements, and integrate the monitoring element items associated with the independent parameters to obtain acquisition element information.

[0124] Optionally, the generation unit includes: an extraction module for extracting element conversion information and element conversion identifiers in the regulatory reporting requirements for each regulatory agency, wherein the element conversion information includes data conversion instructions, and the element conversion identifier is used to record the data reporting format required by the regulatory agency; a screening module for performing data screening on the monitoring element data set based on the element conversion information to obtain the target regulatory data required by the regulatory agency; a generation module for performing format conversion on the target regulatory data based on the element conversion identifier to obtain the target reporting data, and generating a target regulatory report based on the target reporting data.

[0125] It should be noted that the acquisition unit 61, parsing unit 62, determination unit 63, and generation unit 64 correspond to steps S201 to S204 in the first embodiment. The examples and application scenarios implemented by the above units and the corresponding steps are the same, but are not limited to the contents disclosed in the first embodiment. It should be noted that the above modules or units can be hardware components or software components stored in a memory (e.g., memory 104) and processed by one or more processors (e.g., processors 102a, 102b, ..., 102n). The above modules or units can also be part of a device and can be run in the computer terminal 10 provided in the first embodiment.

[0126] The present invention is described below in conjunction with another optional embodiment.

[0127] Example 3

[0128] An embodiment of the present invention may further provide an electronic device, Figure 7 is a structural block diagram of an electronic device for executing a method for generating a supervisory report according to an embodiment of the present invention. Figure 7 As shown, the electronic device may include: one or more ( Figure 7 Only one is shown) processor 702, memory 704, storage controller, and peripheral interface, wherein the peripheral interface is connected to the radio frequency module, audio module and display.

[0129] Among them, the memory can be used to store software programs and modules, such as program instructions / modules corresponding to the methods and devices in the embodiments of the present application. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory, that is, implementing the above-mentioned method. The memory may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include a memory remotely arranged relative to the processor, and these remote memories may be connected to the terminal via a network. Examples of the above-mentioned network include but are not limited to the Internet, an intranet, a local area network, a mobile communication network and a combination thereof.

[0130] The processor can call the information and application stored in the memory through the transmission device to perform the following steps: obtain the regulatory reporting requirements of N regulatory agencies within a preset regulatory cycle, where N is a positive integer; parse the N regulatory reporting requirements to obtain a full collection requirement, where the full collection requirement is used to indicate the overall monitoring data requirements of all regulatory agencies within the preset regulatory cycle; determine the collection element information based on the full collection requirement, and collect monitoring element data from the target database based on the collection element information to obtain a monitoring element data set, where the target database refers to the internal database of each regulated financial institution; for each regulatory agency, generate a target regulatory report based on the regulatory reporting requirement and the monitoring element data set.

[0131] The processor can also call the information and applications stored in the memory through the transmission device to perform the following steps: parse each regulatory reporting requirement to obtain R monitoring element items required by each regulatory agency, where R is a positive integer; after obtaining all monitoring element items required by N regulatory agencies, merge similar items of all monitoring element items based on the preset merging strategy to obtain the full collection requirement.

[0132] The processor can also call the information and application stored in the memory through the transmission device to perform the following steps: obtain the transaction link segment information of all monitored element items; based on the transaction link merging sub-strategy, compare the transaction link segment information of all monitored element items, and merge the transaction link segments of the same link to obtain the simplest transaction segment collection requirements, wherein the simplest transaction segment collection requirements cover the transaction link segments required by all monitored element items and do not contain duplicate link segments.

[0133] The processor can also call the information and application stored in the memory through the transmission device to perform the following steps: obtain the collection items and collection time period information of all monitoring element items; based on the collection time period merging sub-strategy, compare the collection time period information of all monitoring element items, and merge the collection time periods of the same collection items to obtain the minimum time range collection requirements, wherein the minimum time range collection requirements cover the collection time period required by each collection item and do not include repeated time periods.

[0134] The processor can also call the information and application programs stored in the memory through the transmission device to perform the following steps: obtain the collection name and collection scope information of all monitoring element items; based on the collection scope merging sub-strategy, compare the collection scope information of all monitoring element items, and merge the collection scopes of the same collection name to obtain the minimum collection scope requirement, wherein the minimum collection scope requirement covers the collection scope required by all monitoring element items and does not contain repeated collection scopes.

[0135] The processor can also call the information and application stored in the memory through the transmission device to perform the following steps: for each monitoring element item in the full collection requirement, determine the transaction business where the monitoring element item is located, and determine the transaction link information of the transaction business; based on the transaction link information, map the monitoring element item to the service node in the transaction link, and determine the node identity of each service node; based on the node identity, use the node parameters on the service node as the collection element to obtain the collection element information.

[0136] The processor can also call the information and application stored in the memory through the transmission device to perform the following steps: for each service node, when the node identity indicates that the service node is a master node, determine the node parameters on the master node as master variable parameters; determine the master variable parameters as acquisition elements, and integrate the monitoring element items associated with the master variable parameters to obtain acquisition element information.

[0137] The processor can also call the information and application stored in the memory through the transmission device to perform the following steps: when the node identity indicates that the service node is not the main node and there is a data dependency relationship between the service node and the main node, determine the node parameter on the service node as the dependent variable parameter; determine the dependent variable parameter as a derivable element, wherein the monitoring element item associated with the derivable element is derived based on the main variable parameter and the data dependency relationship after obtaining the main variable parameter associated with the dependent variable parameter; when the node identity indicates that the service node is not the main node and there is no data dependency relationship between the service node and the main node, determine the node parameter on the service node as an independent parameter; determine the independent parameter as the acquisition element, and integrate the monitoring element items associated with the independent parameter to obtain acquisition element information.

[0138] The processor can also call the information and application programs stored in the memory through the transmission device to perform the following steps: for each regulatory agency, extract the element conversion information and element conversion identifier in the regulatory reporting requirements, wherein the element conversion information includes data conversion instructions, and the element conversion identifier is used to record the data reporting format required by the regulatory agency; based on the element conversion information, the monitoring element data set is screened to obtain the target regulatory data required by the regulatory agency; based on the element conversion identifier, the target regulatory data is format converted to obtain the target reporting data, and a target regulatory report is generated based on the target reporting data.

[0139] By adopting the embodiment of the present invention, a solution for generating regulatory reports is provided. By integrating the full amount of regulatory requirements and achieving the purpose of optimizing resource utilization through precise analysis and efficient collection, the technical effect of rapid response and reduction of repetitive work is achieved. Specifically, by collecting and analyzing the reporting requirements of multiple regulatory agencies within a preset period, a unified full amount of collection requirements is determined, thereby avoiding the repetitive work of collecting data separately for each regulatory agency. According to the determined collection element information, monitoring element data is efficiently collected from the internal database (target database) of the financial institution to form a monitoring element data set. According to the specific needs of each regulatory agency, relevant data is called from the monitoring element data set and converted according to its specific reporting format to generate corresponding regulatory reports. This not only reduces the repetitiveness of data collection and reduces the consumption of financial institution resources, but also speeds up the report generation, improves the flexibility and efficiency of financial institutions in responding to regulatory needs, and thus solves the technical problem in the related art that financial institutions will repeatedly collect and report data in response to the data collection requirements of different regulatory agencies, which consumes a lot of resources and leads to slow response.

[0140] It can be understood by those skilled in the art that Figure 7The structure shown is for illustration only, and the electronic device may also be a terminal device such as a smart phone, a tablet computer, a PDA, a mobile Internet device (MID), or a PAD. Figure 7 It does not limit the structure of the above electronic device. For example, the electronic device may also include Figure 7 More or fewer components (such as network interfaces, display devices, etc.) shown in, or with Figure 7 Different configurations shown.

[0141] A person skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing the hardware related to the terminal device through a program, and the program can be stored in a computer-readable storage medium, which may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0142] The present invention is described below in conjunction with another optional embodiment.

[0143] Example 4

[0144] The embodiment of the present invention further provides a computer-readable storage medium. Optionally, in the embodiment of the present invention, the computer-readable storage medium can be used to store the program code executed by the method for generating a regulatory report provided in the first embodiment.

[0145] Optionally, in an embodiment of the present invention, the above-mentioned storage medium may be located in any computer terminal in a computer terminal group in a computer network, or in any mobile terminal in a mobile terminal group.

[0146] An embodiment of the present invention also provides a computer program product, which, when executed on a data processing device, is suitable for executing the steps of a method for generating a regulatory report: obtaining the regulatory reporting requirements of N regulatory agencies within a preset regulatory cycle, where N is a positive integer; parsing the N regulatory reporting requirements to obtain a full collection requirement, where the full collection requirement is used to indicate the overall monitoring data requirements of all regulatory agencies within the preset regulatory cycle; determining collection element information based on the full collection requirement, and collecting monitoring element data from a target database based on the collection element information to obtain a monitoring element data set, where the target database refers to the internal database of each regulated financial institution; for each regulatory agency, generating a target regulatory report based on the regulatory reporting requirement and the monitoring element data set.

[0147] The serial numbers of the above embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0148] In the above embodiments of the present application, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0149] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0150] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0151] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0152] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0153] The above is only a preferred embodiment of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for generating a supervision report, characterized in that: include: Obtain the regulatory reporting requirements of N regulatory agencies within a preset regulatory period, where N is a positive integer; Parsing N of the regulatory reporting requirements to obtain a full collection requirement, wherein the full collection requirement is used to indicate the overall monitoring data requirements of all the regulatory agencies within the preset regulatory period; Determine the collection element information based on the full collection requirement, and collect the monitoring element data from the target database based on the collection element information to obtain the monitoring element data set, wherein the target database refers to the internal database of each regulated financial institution; For each of the regulatory agencies, a target regulatory report is generated based on regulatory reporting requirements and the monitoring element data set.

2. The generation method according to claim 1, characterized in that: The steps of parsing N regulatory reporting requirements to obtain full collection requirements include: Parsing each of the regulatory reporting requirements to obtain R monitoring element items required by each regulatory agency, where R is a positive integer; After obtaining all the monitoring element items required by the N regulatory agencies, similar items are merged for all the monitoring element items based on a preset merging strategy to obtain the full amount collection requirements.

3. The generation method according to claim 2, characterized in that: The preset merging strategy at least includes: a transaction link merging sub-strategy, and the steps of merging similar items of all the monitoring element items based on the preset merging strategy to obtain the full amount collection requirement include: Obtaining transaction link segment information of all monitoring element items; Based on the transaction link merging sub-strategy, the transaction link segment information of all the monitored element items is compared, and the transaction link segments of the same link are merged to obtain the simplest transaction segment collection requirements, wherein the simplest transaction segment collection requirements cover the transaction link segments required by all the monitored element items and do not contain duplicate link segments.

4. The generation method according to claim 2, characterized in that: The preset merging strategy also includes: a collection time period merging sub-strategy, a step of merging similar items of all the monitoring element items based on the preset merging strategy to obtain the full collection requirement, and also includes: Obtaining the collection items and collection time period information of all the monitoring element items; Based on the collection time period merging sub-strategy, the collection time period information of all the monitoring element items is compared, and the collection time periods of the same collection item are merged to obtain the minimum time range collection requirement, wherein the minimum time range collection requirement covers the collection time period required by each collection item and does not contain repeated time periods.

5. The generation method according to claim 2, characterized in that: The preset merging strategy also includes: a collection range merging sub-strategy, and the step of merging similar items of all the monitoring element items based on the preset merging strategy to obtain the full collection requirement includes: Obtaining the collection name and collection scope information of all the monitoring element items; Based on the collection scope merging sub-strategy, the collection scope information of all the monitored element items is compared, and the collection scopes of the same collection name are merged to obtain the minimum collection scope requirement, wherein the minimum collection scope requirement covers the collection scope required by all the monitored element items and does not contain repeated collection scopes.

6. The generation method according to claim 2, characterized in that: The step of determining the collection element information based on the full collection requirement includes: For each of the monitoring element items in the full collection requirement, determining the transaction business to which the monitoring element item belongs, and determining the transaction link information of the transaction business; Mapping the monitoring element items to service nodes in the transaction link based on the transaction link information, and determining the node identity of each of the service nodes; Based on the node identity, the node parameters on the service node are used as collection elements to obtain the collection element information.

7. The generation method according to claim 6, characterized in that: The step of taking the node parameters on the service node as collection elements based on the node identity to obtain the collection element information includes: For each of the service nodes, when the node identity indicates that the service node is a master node, determining a node parameter on the master node as a main variable parameter; The main variable parameter is determined as a collection element, and the monitoring element items associated with the main variable parameter are integrated to obtain the collection element information.

8. The generation method according to claim 7, characterized in that: The step of using the node parameters on the service node as collection elements based on the node identity to obtain the collection element information further includes: When the node identity indicates that the service node is not a master node and there is a data dependency relationship between the service node and the master node, determining a node parameter on the service node as a dependent variable parameter; Determine the dependent variable parameter as a derivable element, wherein the monitoring element item associated with the derivable element is derived based on the main variable parameter and the data dependency after obtaining the main variable parameter associated with the dependent variable parameter; When the node identity indicates that the service node is not a master node and there is no data dependency relationship between the service node and the master node, determining that the node parameter on the service node is an independent parameter; The independent parameter is determined as a collection element, and the monitoring element items associated with the independent parameter are integrated to obtain the collection element information.

9. The generation method according to claim 1, characterized in that: For each of the regulatory agencies, the step of generating a target regulatory report based on the regulatory reporting requirements and the monitoring element data set includes: For each of the regulatory agencies, extracting element conversion information and element conversion identifiers in the regulatory reporting requirements, wherein the element conversion information includes data conversion instructions, and the element conversion identifier is used to record the data reporting format required by the regulatory agency; Performing data screening on the monitoring element data set based on the element conversion information to obtain target regulatory data required by the regulatory agency; The target supervision data is format-converted based on the element conversion identifier to obtain target reporting data, and the target supervision report is generated based on the target reporting data.

10. A device for generating a supervision report, characterized in that: include: An acquisition unit, used to acquire regulatory reporting requirements of N regulatory agencies within a preset regulatory period, where N is a positive integer; A parsing unit, used for parsing the N regulatory reporting requirements to obtain a full collection requirement, wherein the full collection requirement is used to indicate the overall monitoring data requirements of all the regulatory agencies within the preset regulatory period; a determination unit, configured to determine the collection element information based on the full collection requirement, and collect the monitoring element data from the target database based on the collection element information to obtain a monitoring element data set, wherein the target database refers to an internal database of each regulated financial institution; A generating unit is used to generate a target regulatory report for each regulatory agency based on regulatory reporting requirements and the monitoring element data set.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored computer program, wherein when the computer program is executed, the device where the computer-readable storage medium is located is controlled to execute the method for generating a regulatory report according to any one of claims 1 to 9.

12. An electronic device, characterized in that: It includes one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method for generating a regulatory report as described in any one of claims 1 to 9.

13. A computer program product, characterized in that The method comprises computer instructions, wherein when the computer instructions are executed by a processor, the steps of the method for generating a regulatory report as described in any one of claims 1 to 9 are implemented.

Images