Collection type data submission method and device, computer equipment and readable storage medium
By combining automated acquisition of reporting templates and data entry modules, the problem of data integration relying on manual operation has been solved, enabling efficient and accurate reporting of summary data and adapting to high-frequency, large-scale regulatory needs.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- CHINA CITIC BANK CO LTD
- Filing Date
- 2025-11-28
- Publication Date
- 2026-05-01
AI Technical Summary
In existing technologies, the data integration process relies on manual operation, resulting in long processing times, a large workload of repetitive checks, and data accuracy that is easily affected by human factors, making it difficult to meet the requirements of high-frequency, large-scale summary-type regulatory data reporting.
The configuration module automatically obtains the reporting template and sets the report parameters. Combined with the first filling module, it realizes the automatic data aggregation and filling. The verification module performs data verification, including intra-table, inter-table and soft verification rules, to ensure data accuracy. Finally, the reporting module reports the data to the regulatory channel.
It enables rapid adaptation to the requirements of different regulatory channels, reduces the time cost of manual adaptation, improves the accuracy of data reporting and the flexibility of the system, and forms a standardized and regulated regulatory reporting system.
Smart Images
Figure CN121960408A_ABST
Abstract
Description
Summary data reporting methods, devices, computer equipment, and readable storage media Technical Field
[0001] This application relates to the fields of financial technology and computer software technology, and in particular to a method, apparatus, computer equipment and readable storage medium for reporting aggregated data. Background Technology
[0002] Under the trend of digital supervision in the financial industry, regulatory agencies have placed increasingly stringent requirements on the timeliness, accuracy, and standardization of bank data reporting. The current regulatory reporting system has initially established an automated processing framework based on a rule engine, which automatically verifies reported data, generates reporting files, and periodically pushes data files to customer systems. For erroneous data returned by customer systems, business personnel manually modify and review it before re-executing the automated reporting. However, the data integration process of existing technologies relies on manual operation, resulting in technical problems such as time-consuming manual entry, a large workload of repetitive checks, and data accuracy being easily affected by human factors. This makes it difficult to meet the requirements of high-frequency, large-scale aggregated regulatory data reporting. Summary of the Invention
[0003] In view of this, this application provides a method, apparatus, computer equipment and readable storage medium for reporting aggregated data. The main purpose is to solve the technical problems of existing technologies, such as data integration processes relying on manual operation, time-consuming manual input, large workload of repetitive checks, and data accuracy being easily affected by human factors, which make it difficult to meet the requirements of high-frequency and large-scale aggregated regulatory data reporting.
[0004] According to a first aspect of this application, a method for reporting aggregated data is provided. The method includes: calling a configuration module to obtain a data reporting template corresponding to a reporting channel, and setting report parameters for the data reporting template according to the reporting rules corresponding to the reporting channel to obtain a report template. The report parameters include a filling process, report information, cell information, standard description, and verification rules. In response to a data reporting instruction, a first filling module is called to obtain data to be reported from a data warehouse, and the data to be reported is filled into the corresponding report template according to the cell information and the standard description to obtain a data report to be reported. A first verification module is called to perform data verification on the cell values corresponding to each cell in the data report to be reported according to the verification rules, generating a verification result for each cell. The verification rules include intra-table verification rules, inter-table verification rules, and soft verification rules. If the verification results for each cell indicate that the verification passed, the reporting module is called to report the data report to be reported to the reporting channel recorded in the report information.
[0005] Optionally, the step of responding to a data reporting instruction by calling a first filling module to retrieve the data to be reported from the data warehouse and filling the data to be reported into the data reporting template according to the cell information and the standard description to obtain a data report to be reported includes: setting a timer based on the reporting frequency indicated by the reporting rule; generating a data reporting instruction when the timer's duration reaches the reporting time interval corresponding to the reporting frequency; responding to the data reporting instruction by determining the report template corresponding to the data reporting instruction; calling the first filling module to retrieve the data to be reported from the data warehouse, wherein the report information includes, but is not limited to, report code, report name, report version, reporting frequency, and report validity period; calling the first filling module to fill the data to be reported into the cells of the report template, formatting the cell value corresponding to each cell according to the cell information, and standardizing the cell value corresponding to each cell according to the standard description to obtain the data report to be reported.
[0006] Optionally, after filling the data to be reported into the data reporting template according to the cell information and the standard description to obtain the data report to be reported, the method further includes: calling the second filling module to determine the business department associated with the data report to be reported, splitting the data report to be reported according to the business part to obtain the department data report corresponding to each business department, and sending the department data report to the department terminal corresponding to the corresponding business department for visualization display; within a preset modification time, in response to the modification request uploaded by the business department, calling the second filling module to modify the department data report in the system database, wherein the modification request is generated by the filler of the business department after modifying the corresponding department data report based on the department terminal, and the modification request carries modification parameters; after the modification time expires, merging all department data reports in the system database to obtain the modified data report to be reported; calling the first verification module to perform data verification on the cell value corresponding to each cell in the modified data report to be reported according to the verification rules, and generating a verification result corresponding to each cell.
[0007] Optionally, within a preset modification time, in response to a modification request uploaded by a business department, the second data entry module is invoked to modify the departmental data report in the system database. This includes: parsing the modification parameters carried in the modification request to obtain the report identifier to be modified, the cell identifier to be modified, the cell value to be modified, and the data entry person; determining the departmental data report corresponding to the report identifier to be modified in the system database, and determining the cell to be modified in the departmental data report based on the cell identifier to be modified; replacing the current cell value of the cell to be modified with the cell value to be modified, and associating the cell to be modified with the data entry person to obtain the modified departmental report data.
[0008] Optionally, the step of calling the first verification module to perform data verification on the cell values corresponding to each cell in the data report to be submitted, according to the verification rules, and generating a verification result for each cell, includes: for the data table to be submitted, calling the first verification module to perform threshold verification on each cell value based on the soft verification rules, and generating a soft verification result; calling the first verification module to perform calculation verification on the logical relationship between cell values belonging to the same sub-table based on the intra-table verification rules, and generating an intra-table verification result, wherein the data table to be submitted includes at least one sub-table; and calling the first verification module to perform threshold verification on different sub-table values based on the inter-table verification rules. Cross-table validation is performed on the data linkage relationship of related cell values within the sub-table to generate inter-table validation results. For any cell, if the soft validation result, intra-table validation result, and inter-table validation result all indicate that the data is correct, a validation result indicating that the validation has passed is generated. If any rule validation result among the soft validation result, intra-table validation result, and inter-table validation result indicates that the data is incorrect, a validation result indicating that the validation has failed is generated, along with the rule validation result indicating the data error and the validation rule corresponding to the rule validation result. The display style of the cell is adjusted according to the error display style associated with the validation rule.
[0009] Optionally, after performing data validation on the cell value corresponding to each cell in the data report to be submitted and generating a validation result for each cell, the method further includes: if any cell's validation result indicates that the validation failed, then calling the first validation module to determine the person filling out the cell according to the standard description; generating a re-filling prompt, and sending the re-filling prompt to the department terminal corresponding to the person filling out the cell, so that the person filling out the cell can re-fill out the cell value based on the department terminal according to the filling prompt, until the validation result corresponding to the cell indicates that the validation passed.
[0010] Optionally, before the reporting module submits the data report to be submitted to the reporting channel recorded in the report information, the method further includes: calling the second verification module to send the data report to be submitted to the review terminal and obtaining the review result uploaded by the review terminal; if the review result indicates that the review is passed, then submitting the data report to be submitted to the reporting channel recorded in the report information; if the review result indicates that the review is not passed, then reading the review comments associated with the review result, determining the cell identifier to be modified and the person filling it out, and generating a re-submission prompt, sending the re-submission prompt to the department terminal corresponding to the person filling it out, so that the person filling it out can re-submit the cell value corresponding to the cell identifier to be modified based on the department terminal according to the submission prompt, until the review result corresponding to the report to be submitted indicates that the review is passed.
[0011] According to a second aspect of this application, a data reporting device for aggregation is provided. The device includes: a configuration module, configured to acquire a data reporting template corresponding to a reporting channel, and set report parameters for the data reporting template according to the reporting rules corresponding to the reporting channel to obtain a report template, wherein the report parameters include a filling process, report information, cell information, standard description, and verification rules; a first filling module, configured to, in response to a data reporting instruction, acquire data to be reported from a data warehouse, and fill the data to be reported into the corresponding report template according to the cell information and the standard description to obtain a data report to be reported; a first verification module, configured to, according to the verification rules, perform data verification on the cell values corresponding to each cell in the data report to be reported, generating a verification result for each cell, wherein the verification rules include intra-table verification rules, inter-table verification rules, and soft verification rules; and a reporting module, configured to, if the verification result for each cell indicates that the verification has passed, report the data report to be reported to the reporting channel recorded in the report information.
[0012] According to a third aspect of this application, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the method described in any of the first aspects above.
[0013] According to a fourth aspect of this application, a computer-readable storage medium is provided, on which a computer program is stored, wherein the computer program, when executed by a processor, implements the steps of the method described in any one of the first aspects above.
[0014] By employing the above technical solutions, this application provides a method, apparatus, computer device, and readable storage medium for reporting aggregated data. In this embodiment, a configuration module automatically acquires reporting templates and sets report parameters, achieving a unified report format and standardized filling rules. This allows for rapid adaptation to different regulatory channel requirements, improving system flexibility and adaptability, and reducing the time cost and formatting errors associated with manual template adaptation. Furthermore, in the data processing stage, a first filling module automatically aggregates, fills, and maps the data to be reported based on a data warehouse. Combined with mandatory system verification, this ensures data matches regulatory requirements, improving reporting accuracy and forming a standardized and regulated regulatory reporting system. This provides financial institutions with an efficient and reliable method for reporting aggregated data to meet high-frequency regulatory reporting needs.
[0015] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, the following are specific embodiments of this application. Attached Figure Description
[0016] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of this application. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings: Figure 1 shows a flowchart of a summary data reporting method provided by an embodiment of this application; Figure 2 shows a schematic diagram of the architecture of a summary data reporting system provided by an embodiment of this application; Figure 3 shows a schematic diagram of the architecture of a summary data reporting system provided by an embodiment of this application; Figure 4 shows a schematic diagram of the architecture of a summary data reporting system provided by an embodiment of this application; Figure 5 shows a configuration flowchart of a summary data reporting method provided by an embodiment of this application; Figure 6 shows a configuration flowchart of another summary data reporting method provided by an embodiment of this application; Figure 7 shows a configuration flowchart of another summary data reporting method provided by an embodiment of this application; Figure 8... Figure 9 shows a schematic diagram of the configuration process of another summary data reporting method provided in the embodiments of this application; Figure 10 shows a schematic diagram of the splitting result of another summary data reporting method provided in the embodiments of this application; Figure 11 shows a schematic diagram of the modification process of another summary data reporting method provided in the embodiments of this application; Figure 12 shows a schematic diagram of the structure of a summary data reporting device provided in the embodiments of this application; Figure 13 shows a schematic diagram of the structure of another summary data reporting device provided in the embodiments of this application; Figure 14 shows a schematic diagram of the device structure of a computer equipment provided in the embodiments of this application. Detailed Implementation
[0017] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain this application, and should not be construed as limiting this application.
[0018] Those skilled in the art will understand that, unless specifically stated otherwise, the singular forms “a,” “an,” “the,” and “the” used herein may also include the plural forms. It should be further understood that the word “comprising” as used in the specification of this application means the presence of the stated features, integers, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.
[0019] Those skilled in the art will understand that, unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains. It should also be understood that terms such as those defined in general dictionaries should be understood to have the same meaning as in the context of the prior art, and should not be interpreted in an idealized or overly formal sense unless specifically defined as herein.
[0020] Those skilled in the art will understand that the term "terminal" as used herein includes both devices that are wireless signal receivers, devices that are wireless signal receivers without transmitting capability, and devices with receiving and transmitting hardware, having receiving and transmitting hardware capable of performing bidirectional communication on a bidirectional communication link. Such devices may include: cellular or other communication devices having a single-line display, a multi-line display, or a cellular or other communication device without a multi-line display; PCS (Personal Communications Service) that can combine voice, data processing, fax, and / or data communication capabilities; PDA (Personal Digital Assistant) that may include a radio frequency receiver, pager, Internet / intranet access, web browser, notepad, calendar, and / or GPS (Global Positioning System) receiver; and conventional laptop and / or handheld computers or other devices that have and / or include a radio frequency receiver. As used herein, "terminal" can be portable, transportable, installed in a means of transportation (air, sea, and / or land), or suitable and / or configured to operate locally, and / or in a distributed manner, operating in any other location on Earth and / or in space. "Terminal" as used herein can also be a communication terminal, an internet access terminal, or a music / video playback terminal, such as a PDA, a MID (Mobile Internet Device), and / or a mobile phone with music / video playback capabilities, or a smart TV, set-top box, etc.
[0021] This application provides a summary data reporting method, as shown in Figure 1. The method includes: S10, calling the configuration module to obtain the data reporting template corresponding to the reporting channel, and setting report parameters for the data reporting template according to the reporting rules corresponding to the reporting channel to obtain the report template. The report parameters include the filling process, report information, cell information, standard description and verification rules.
[0022] The summary data reporting method provided in this application is applicable to data reporting systems, as shown in Figures 2 and 3. These systems include a front-end page and a back-end server. The front-end page adopts the latest Vue 3 specification, uses Nginx for caching the front-end page and as a reverse proxy for the access page service, and the presentation layer uses the HTTP protocol to interact with the back-end service. All data returned by the access interface is in JSON format. The back-end server uses the latest Spring Boot framework, integrates MyBatis as an ORM framework to connect to the database, and uses Spring MVC to expose RESTful APIs, implementing independent microservice nodes for each subsystem.
[0023] As is understandable, all microservice nodes are registered with the registry center (citiccard-eureka), and all service acquisitions are made from the registry center. The main configuration information of the microservice nodes is stored in the configuration center (citiccard-config) for unified management of configurations for microservice nodes with similar functions. Each microservice node is configured with call chain performance monitoring (citiccard-trace) to monitor the performance of microservice request calls. The main operation logs of the microservice nodes are stored in a log cloud platform for convenient unified logging and viewing. Interface access between microservices is conducted using Spring Cloud Feign, with the registry center used for load balancing and circuit breaking of unavailable service nodes. The backend database uses MySQL MGR for data storage, ensuring high availability and consistency.
[0024] The overall system architecture is shown in Figure 4. The system uses Nginx as a reverse proxy server, and the front-end uses the Vue3 framework to load pages. The front-end and back-end use RESTful APIs for communication, and JSON for data transmission. System management, one-stop reporting, process and log management, and data entry analysis utilize Spring Boot to quickly build microservices, simplifying dependency management and configuration to ensure scalability. Eureka is used as the service registry, enabling automatic registration and discovery of various microservices such as system management and one-stop reporting, facilitating communication between them. Spring Cloud Config is used to uniformly manage the configuration information of all microservices. The Quartz scheduled task framework is used to implement the monthly data entry process plan. Report process control management is implemented based on the Activti plugin, and the data entry page uses the Apache POI plugin to load the reporting template and display the data. The back-end database, MySQL MGR, stores system business data, such as aggregated data from data processing and modification. The underlying detailed data is in the Hive data warehouse. Monthly aggregated data is processed and stored in the Hive database using a batch scheduling tool, and the Hive tables are synchronized to the MySQL tables using Sqoop.
[0025] In this step, the regulatory agency will periodically update the submitted Excel template and corresponding reporting rules. Operators upload the updated submission template and corresponding reporting rules from the regulatory agency through the report publishing function on the system's front-end page. As shown in Figures 5 to 8, the system calls the configuration module, receives the configuration request sent by the front-end via the HTTP interface, imports the Excel template, and uses the Apache POI plugin to configure the report parameters for the submission template. This includes configuring the filling process (as shown in Figures 5 and 6), report information, cell information (as shown in Figure 7), and validation rules (as shown in Figure 8), ultimately obtaining the report template for the business data to be filled.
[0026] Understandably, the Apache POI plugin supports dynamic adaptation to various versions of reporting templates from regulatory agencies. The system establishes a template version management center to compare and record field changes and rule differences between different template versions. When a reporting task is triggered, the corresponding version of the Excel template and validation rules are automatically loaded based on the template version number in the task parameters, ensuring consistency of data format and rules within the same reporting batch. This process supports multi-format file validation and breakpoint resume, ensuring stable uploading of large amounts of template data.
[0027] In actual operation, report parameters include, but are not limited to, report information, cell information, standard descriptions, and validation rules. Report information may include, but is not limited to, report code, report name, report version, reporting frequency, and report validity period. In practice, report information may also include the module to which the report belongs, report code, report name, report version, report activation / deactivation time, start and end coordinates of report data, reporting batch, and reporting frequency. Cell information is used to constrain the format of each cell, such as num_10000_2_CNY representing "ten-thousands digit, two decimal places, RMB currency". Format validation is implemented through the plugin's underlying algorithm to ensure that the reported data conforms to the data type, precision, and unit requirements of regulatory agencies. Standard descriptions are used to constrain the content of the indicators entered into each cell. Validation rules are used to indicate the corresponding soft validation rules, intra-table validation rules, and inter-table validation rules for the report.
[0028] S20. In response to the data reporting instruction, the first filling module is called to retrieve the data to be reported from the data warehouse, and the data to be reported is filled into the corresponding report template according to the cell information and standard instructions to obtain the data to be reported report.
[0029] In this embodiment, the system stores the reporting frequency in the system database, such as in the `report_rule` table of the `MySQLMGR` database. Related fields include `report_code` (report code), `frequency` (reporting frequency), and `interval_days` (interval time). Further, as shown in Figure 5, the system executes steps S21 to S23, dynamically creating a timer instance for each report instance based on the Quartz scheduled task framework. When the timer's duration reaches the reporting interval corresponding to the reporting frequency, a data reporting instruction is generated. In response to the data reporting instruction, the system calls the first data entry module to retrieve the data to be reported from the data warehouse and fills the data into the corresponding report template according to the cell information and standard specifications, thus obtaining the report of the data to be reported.
[0030] S21. Set a timer based on the reporting frequency indicated by the reporting rules. When the timer's duration reaches the reporting time interval corresponding to the reporting frequency, generate a data reporting instruction.
[0031] In this step, when the timer reaches the time interval corresponding to the reporting frequency (such as the 90-day interval for quarterly reporting), the system sends an event notification to the data-delivery-service microservice through the Eureka registry center, generates a data reporting instruction containing report_id (unique identifier of the report), trigger_time (trigger time), and version (report version number), and stores it in the message queue Kafka for consumption.
[0032] S22. In response to the data reporting instruction, determine the report template corresponding to the data reporting instruction, and call the first filling module to retrieve the data to be reported from the data warehouse.
[0033] The microservice `data-delivery-service` consumes data delivery commands from the Kafka queue. In response, the system calls the first data entry module, which queries the report version management database (stored in MySQL MGR) using the `report_id` to retrieve the corresponding report template metadata. Further, based on the metric mapping and time indicated by the report metadata, it filters the data to be submitted from the data warehouse. Understandably, for multi-department submission scenarios, data can be filtered using the `department_code` field to generate department-level data subsets, facilitating subsequent filling of these subsets into the report template by department and improving filling efficiency.
[0034] S23. Call the first data entry module to fill the data to be submitted into the cells of the report template, format the cell value corresponding to each cell according to the cell information, and standardize the cell value corresponding to each cell according to the standard instructions to obtain the data report to be submitted.
[0035] In this step, a report template, such as an XSSFWorkbook object, is loaded using the Apache POI plugin. The mapping between cell coordinates and data fields in the `report_mapping` table is iterated, and the `setCellValue()` method is called to populate data row by row. For example, the cell "G17_E_33" corresponds to the data field `overdraft_balance`, which is filled by reading the value "6000" from the department number 022000000 in the MySQL table `temp_report_data`.
[0036] It is understandable that data input errors will inevitably occur during the automatic generation of data reports to be submitted. Therefore, it is necessary for the relevant departments' data entry personnel to review the reports and correct any erroneous cell values. Specifically, as shown in Figure 9, the system can call the second data entry module to identify the various business departments associated with the data reports to be submitted, and split the data reports to be submitted according to the business departments to obtain the departmental data reports corresponding to each business department. After the splitting is completed, the system will push the departmental data reports to the terminal devices of the corresponding business departments according to the report download requests sent by each department, and display them through the front-end visual interface. In actual operation, in order to ensure the timeliness of data modification, the system sets a node operation time threshold for this process, namely the modification time. Data entry personnel in the business departments can modify the departmental data reports, and modifications exceeding this time limit will be considered invalid. That is to say, within the specified modification time, the system will monitor modification requests in real time. Once it receives a request from a business department's data entry personnel after completing data modification on the departmental terminal, it will immediately call the second data entry module and update the corresponding departmental data reports in the system database according to the modification parameters carried in the request. Specifically, the system calls the second data entry module to parse the modification parameters carried in the modification request, obtaining key information such as the report identifier to be modified, the cell identifier to be modified, the cell value to be modified, and the data entry person. Further, the system accurately locates the corresponding department data report in the database based on the report identifier to be modified, and then locks the cell to be modified within the department data report based on the cell identifier to be modified. Finally, the system replaces the current value of the cell with the value to be modified and establishes a link record between the cell to be modified and the data entry person, thereby completing the modification of the department report data and obtaining the modified department report data. When the modification time expires, the system automatically summarizes all department data reports and integrates them to generate the modified data report to be submitted. Finally, the system calls the first verification module to perform data verification on each cell value in the modified report according to preset verification rules, generating a verification result for each cell.
[0037] S30. Call the first verification module to perform data verification on the cell value corresponding to each cell in the data report to be submitted according to the verification rules, and generate the verification result corresponding to each cell. The verification rules include intra-table verification rules, inter-table verification rules and soft verification rules.
[0038] In this embodiment of the application, after automatic filling and manual modification of the work nodes, as shown in Figure 10, the system calls the first verification module and executes the following steps S31 to S33 to verify the cell value corresponding to each cell in the data report to be submitted, and generates the verification result corresponding to each cell, so as to ensure the accuracy and compliance of subsequent data submission.
[0039] S31. For the data table to be reported, call the first verification module, perform threshold verification on each cell value based on the soft verification rules, and generate soft verification results.
[0040] The data table to be reported includes at least one sub-table. For each sub-table within the data table to be reported, the system calls the first verification module to perform threshold verification on each cell value based on soft verification rules, generating a soft verification result. Soft verification rules are typically non-mandatory verification conditions, such as reasonable data ranges and threshold limits. By performing threshold verification on cell values, it is possible to preliminarily determine whether the data is within a reasonable range and whether there are obvious outliers. Specifically, for each cell value in the data table to be reported, the system calls the first verification module to read the soft verification rule associated with that cell for verification. Taking numeric cells as an example, if the soft verification expression is G17.G17_E_123>1, it means that the data in cell 123 of column E in report G17 must be greater than 1. The first verification module extracts the actual value of the corresponding cell for threshold comparison, generating a soft verification result that includes whether the data is correct or incorrect and the deviation amount. For non-numeric cells, such as date formats and character lengths, the module performs compliance verification based on preset format templates. Meanwhile, considering the logical relationships between cell values within each sub-table, such as the relationship between the total row and each detail row, and the reconciliation of data, the system can call the first verification module to calculate and verify the logical relationships between cell values belonging to the same sub-table based on the in-table verification rules, generating in-table verification results. Taking a financial business sub-table as an example, if the in-table verification expression is G17.G17_E_45=G17.G17_E_46+G17.G17_E_47, it means that cell E45 in report G17 equals cell E46 plus cell E47. The first verification module is called to extract the actual value of the corresponding cell for calculation, verify whether it conforms to the in-table verification rules, and generate the in-table verification result for the corresponding cell. If the verification does not conform to the in-table verification rules, all cells associated with the rule are identified, and the in-table verification results for all cells are set as data errors. Through in-table verification rules, the data logic within the same sub-table can be ensured to be consistent and meet business requirements. Meanwhile, considering the potential relationships between data in different sub-tables, such as the data correspondence between the main table and sub-tables, and data consistency between different sub-tables, the system can call the first verification module to perform cross-table verification on the data linkage relationships of related cell values within different sub-tables based on inter-table verification rules, generating inter-table verification results. Taking a financial regulatory reporting scenario as an example, if the inter-table verification expression is G17.G17_C_55+G17.G17_E_55=Q5301.Q5301_M_9, it means that cell C55 plus cell E55 in report G17 equals cell M9 in report Q5301. The first verification module is called to extract the actual value of the corresponding cell for calculation, verifying whether it conforms to the inter-table verification rules, generating the inter-table verification result for the corresponding cell. If the verification does not conform to the inter-table verification rules, all cells associated with the rules are identified, and the inter-table verification results for all cells are set as data errors.By using inter-table validation rules, we can ensure that the data linkage between different sub-tables is correct and avoid data inconsistencies.
[0041] S32. For any cell, if the soft validation result, intra-table validation result, and inter-table validation result all indicate that the data is correct, then a validation result is generated to indicate that the validation has passed.
[0042] For any cell to be validated, the first validation module integrates the soft validation result, intra-table validation result, and inter-table validation result corresponding to that cell for comprehensive judgment. The module generates a validation pass result containing information such as cell identifier, validation pass status, and validation timestamp, only if all three types of validation results indicate that the data is correct. This result follows a preset data structure specification and can be directly called by other modules in the system, serving as an important basis for data compliance.
[0043] S33. If any rule validation result in the soft validation result, intra-table validation result, or inter-table validation result corresponding to the cell indicates a data error, then a validation result indicating a validation failure is generated, along with the rule validation result indicating the data error and the validation rule corresponding to the rule validation result. The display style of the cell is adjusted according to the error display style associated with the validation rule.
[0044] When any rule-based validation result in a cell's soft validation, intra-table validation, or inter-table validation indicates a data error, the first validation module generates a checklist including the cell identifier, validation failure status, and error type (soft validation error, intra-table validation error, or inter-table validation error). Simultaneously, the module locates the specific rule-based validation result indicating the data error and its corresponding validation rule. Based on the pre-configured error display style associated with the validation rule, the module automatically adjusts the cell's display style. For example, for data errors triggering intra-table validation rules, the corresponding cell's background color is set to red; for data errors triggering inter-table validation rules, it's set to yellow; and for data errors triggering soft validation rules, it's set to orange. By establishing a mapping relationship between "validation rule - error level - display style," the module achieves visual identification of erroneous data, facilitating quick location and correction of data problems by business personnel.
[0045] S40. If the verification result for each cell indicates that the verification passed, the reporting module is called to report the data report to be reported to the reporting channel recorded in the report information.
[0046] In this embodiment, after all system verifications pass, to avoid potential omissions in the system verification, the system can also call the second verification module to send the data report to be submitted to the review terminal, where the reporting coordinator reviews it and uploads the review results. The system identifies the review results uploaded by the review terminal. If the review result indicates that the review has passed, the data report to be submitted is reported to the reporting channel recorded in the report information. If the review result indicates that the review has failed, the system reads the review comments associated with the review result, determines the cell identifier to be modified and the person filling it out, and generates a re-submission prompt containing modification instructions. The re-submission prompt is sent to the department terminal corresponding to the person filling out the report, so that the person filling out the report can re-submit the cell value corresponding to the cell identifier to be modified based on the department terminal according to the re-submission prompt, and re-execute the above steps S20 to S30 until the review result corresponding to the report to be submitted indicates that the review has passed.
[0047] Understandably, if any cell fails verification during the system validation phase, the system will use the first validation module to quickly locate the person who submitted the data according to the standard instructions, generate a resubmission instruction with an error message, and push it to the corresponding department's terminal. As shown in Figure 11, the person submitting the data needs to correct the data on the terminal according to the resubmission instruction until the cell passes validation.
[0048] The method provided in this application automatically acquires reporting templates and sets report parameters through a configuration module, achieving a unified report format and standardized filling rules. This allows for rapid adaptation to different regulatory channel requirements, improving system flexibility and adaptability, and reducing the time cost and formatting errors associated with manual template adaptation. Furthermore, in the data processing stage, the first filling module automatically aggregates, fills, and maps the data to be reported based on a data warehouse. Combined with mandatory system validation, this ensures data matches regulatory requirements, improving reporting accuracy and forming a standardized and regulated regulatory reporting system. This provides financial institutions with an efficient and reliable method for submitting aggregated data to meet high-frequency regulatory reporting needs.
[0049] Furthermore, as a specific implementation of the method described in Figure 1, this application embodiment provides a summary data reporting device, as shown in Figure 12. The system includes: a configuration module 1201, a first filling module 1202, a first verification module 1203, and a reporting module 1204.
[0050] The configuration module 1201 is used to obtain the data reporting template corresponding to the channel to be reported, and set report parameters for the data reporting template according to the reporting rules corresponding to the reporting channel to obtain the report template. The report parameters include the filling process, report information, cell information, standard description, and verification rules. The first filling module 1202 is used to respond to the data reporting instruction, obtain the data to be reported from the data warehouse, and fill the data to be reported into the corresponding report template according to the cell information and the standard description to obtain the data report to be reported. The first verification module 1203 is used to perform data verification on the cell value corresponding to each cell in the data report to be reported according to the verification rules, and generate a verification result corresponding to each cell. The verification rules include intra-table verification rules, inter-table verification rules, and soft verification rules. The reporting module 1204 is used to report the data report to be reported to the channel to be reported recorded in the report information if the verification result corresponding to each cell indicates that the verification has passed.
[0051] In a specific application scenario, the first data entry module 1202 is used to set a timer based on the reporting frequency indicated by the reporting rules. When the timer's duration reaches the reporting time interval corresponding to the reporting frequency, a data reporting instruction is generated. In response to the data reporting instruction, the report template corresponding to the data reporting instruction is determined, and the first data entry module is invoked to retrieve the data to be reported from the data warehouse. The report information includes, but is not limited to, report code, report name, report version, reporting frequency, and report validity period. The first data entry module is invoked to fill the data to be reported into the cells of the report template, and the cell values corresponding to each cell are formatted according to the cell information and standardized according to the standard description to obtain the data report to be reported.
[0052] In a specific application scenario, as shown in Figure 13, the device also includes a second data entry module 1301.
[0053] The second data entry module 1301 is used to determine the business departments associated with the data report to be submitted according to the data entry process, split the data report to be submitted according to the business parts to obtain department data reports corresponding to each business department, and send the department data reports to the department terminals corresponding to the business departments for visualization display; within a preset modification time, in response to the modification requests uploaded by the business departments, modify the department data reports in the system database, wherein the modification requests are generated by the data entry personnel of the business departments after modifying the corresponding department data reports based on the department terminals, and the modification requests carry modification parameters; after the modification time expires, all department data reports in the system database are merged to obtain the modified data report to be submitted; the first verification module is called to perform data verification on the cell values corresponding to each cell in the modified data report to be submitted according to the verification rules, and generate a verification result for each cell.
[0054] In a specific application scenario, the second data entry module 1301 is used to parse the modification parameters carried in the modification request to obtain the report identifier to be modified, the cell identifier to be modified, the cell value to be modified, and the data entry person; determine the department data report corresponding to the report identifier to be modified in the system database, determine the cell to be modified in the department data report according to the cell identifier to be modified; replace the current cell value of the cell to be modified with the cell value to be modified, and associate the cell to be modified with the data entry person to obtain the modified department report data.
[0055] In a specific application scenario, the first verification module 1203 is used to, for the data table to be reported, call the first verification module to perform threshold verification on each cell value based on the soft verification rules, and generate a soft verification result; call the first verification module to calculate and verify the logical relationship between cell values belonging to the same sub-table based on the intra-table verification rules, and generate an intra-table verification result, wherein the data table to be reported includes at least one sub-table; call the first verification module to perform cross-table verification on the data linkage relationship of related cell values in different sub-tables based on the inter-table verification rules, and generate an inter-table verification result; for any cell, if the soft verification result, intra-table verification result, and inter-table verification result all indicate that the data is correct, a verification result indicating that the verification has passed is generated; if any rule verification result among the soft verification result, intra-table verification result, and inter-table verification result indicates that the data is incorrect, a verification result indicating that the verification has failed is generated, as well as the rule verification result indicating the data error and the verification rule corresponding to the rule verification result, and the display style corresponding to the cell is adjusted according to the error display style associated with the verification rule.
[0056] In a specific application scenario, the first verification module 1203 is used to, if any cell's corresponding verification result indicates that the verification has failed, call the first verification module to determine the person filling out the cell according to the standard description; generate a re-filling prompt, and send the re-filling prompt to the department terminal corresponding to the person filling out the cell, so that the person filling out the cell can re-fill out the cell value based on the department terminal according to the filling prompt, until the verification result corresponding to the cell indicates that the verification has passed.
[0057] In a specific application scenario, as shown in Figure 13, the device also includes a second verification module 1302.
[0058] The second verification module 1302 is used to call the second verification module to send the data report to be submitted to the audit terminal and obtain the audit result uploaded by the audit terminal; if the audit result indicates that the audit is passed, the data report to be submitted is reported to the submission channel recorded in the report information; if the audit result indicates that the audit is not passed, the audit opinion associated with the audit result is read, the cell identifier to be modified and the person filling it out are determined, and a re-submission prompt is generated. The re-submission prompt is sent to the department terminal corresponding to the person filling it out, so that the person filling it out can re-submit the cell value corresponding to the cell identifier to be modified based on the department terminal according to the submission prompt, until the audit result corresponding to the report to be submitted indicates that the audit is passed.
[0059] The apparatus provided in this application automatically acquires reporting templates and sets report parameters through a configuration module, achieving a unified report format and standardized filling rules. This allows for rapid adaptation to different regulatory channel requirements, improving system flexibility and adaptability, and reducing the time cost and formatting errors associated with manual template adaptation. Furthermore, in the data processing stage, the first filling module automatically aggregates, fills, and maps the data to be reported based on a data warehouse. Combined with mandatory system verification, this ensures data matches regulatory requirements, improving reporting accuracy and forming a standardized and regulated regulatory reporting system. This provides financial institutions with an efficient and reliable method for submitting aggregated data to meet high-frequency regulatory reporting needs.
[0060] It should be noted that other corresponding descriptions of the functional units involved in the power distribution network restoration device provided in this application embodiment can be found in the corresponding descriptions in Figures 1 to 11, and will not be repeated here.
[0061] To address the aforementioned technical problems, embodiments of the present invention also provide a computer device. Please refer to Figure 14 for details; Figure 14 is a basic structural block diagram of the computer device of this embodiment.
[0062] Figure 14 shows a schematic diagram of the internal structure of a computer device. The computer device includes a processor, a non-volatile storage medium, a memory, and a network interface connected via a system bus. The non-volatile storage medium stores an operating system, a database, and computer-readable instructions. The database may store control information sequences. When the computer-readable instructions are executed by the processor, they enable the processor to implement a data relationship reconstruction method. The processor provides computing and control capabilities to support the operation of the entire computer device. The memory stores computer-readable instructions, which, when executed by the processor, enable the processor to perform a data relationship reconstruction method. The network interface of the computer device is used for communication with a terminal. Those skilled in the art will understand that the structure shown in Figure 14 is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.
[0063] In this embodiment, the processor executes the specific functions of the configuration module 1201, the first filling module 1202, the first verification module 1203, and the reporting module 1204 shown in Figure 12. The memory stores the program code and various types of data required to execute the above modules. The network interface is used for data transmission between the user terminal and the server. In this embodiment, the memory stores the program code and data required to execute all sub-modules in the data relationship reconstruction device, and the server can call the server's program code and data to execute the functions of all sub-modules.
[0064] The present invention also provides a storage medium storing computer-readable instructions, which, when executed by one or more processors, cause the one or more processors to perform the steps of the data relationship reconstruction method of any of the above embodiments.
[0065] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This computer program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the methods described above. The aforementioned storage medium can be a non-volatile storage medium such as a magnetic disk, optical disk, or read-only memory (ROM), or random access memory (RAM).
[0066] Those skilled in the art will understand that the steps, measures, and solutions in the various operations, methods, and processes discussed in this application can be alternated, modified, combined, or deleted. Furthermore, other steps, measures, and solutions in the various operations, methods, and processes discussed in this application can also be alternated, modified, rearranged, decomposed, combined, or deleted. Furthermore, steps, measures, and solutions in the prior art that are similar to those disclosed in this application can also be alternated, modified, rearranged, decomposed, combined, or deleted.
[0067] The above description is only a partial embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.
Claims
1. A method for reporting aggregated data, characterized in that, include: The system calls the configuration module to obtain the data reporting template corresponding to the channel to be reported, and sets report parameters for the data reporting template according to the reporting rules corresponding to the reporting channel to obtain the report template. The report parameters include the filling process, report information, cell information, standard description and validation rules. In response to the data reporting instruction, the system calls the first filling module to obtain the data to be reported from the data warehouse, and fills the data to be reported into the corresponding report template according to the cell information and the standard description to obtain the data report to be reported. The first verification module is invoked to perform data verification on the cell value corresponding to each cell in the data report to be submitted, according to the verification rules, and generate a verification result for each cell. The verification rules include intra-table verification rules, inter-table verification rules, and soft verification rules. If the verification result for each cell indicates that the verification passed, the reporting module is invoked to report the data report to be reported to the reporting channel recorded in the report information.
2. The method according to claim 1, characterized in that, The process of responding to a data reporting instruction by invoking a first data entry module to retrieve data to be reported from a data warehouse and filling the data to be reported into a data reporting template according to the cell information and the standard description to obtain a data report to be reported includes: setting a timer based on the reporting frequency indicated by the reporting rules; generating a data reporting instruction when the timer's duration reaches the reporting time interval corresponding to the reporting frequency; responding to the data reporting instruction by determining the report template corresponding to the data reporting instruction; invoking the first data entry module to retrieve the data to be reported from the data warehouse, wherein the report information includes, but is not limited to, report code, report name, report version, reporting frequency, and report validity period; invoking the first data entry module to fill the data to be reported into the cells of the report template, formatting the cell values corresponding to each cell according to the cell information, and standardizing the cell values corresponding to each cell according to the standard description to obtain the data report to be reported.
3. The method according to claim 1, characterized in that, After filling the data to be reported into the data reporting template according to the cell information and the standard description to obtain the data report to be reported, the method further includes: calling the second filling module, determining the business department associated with the data report to be reported according to the filling process, splitting the data report to be reported according to the business part to obtain the department data report corresponding to each business department, and sending the department data report to the department terminal corresponding to the business department for visualization display; within a preset modification time, responding to the modification request uploaded by the business department, calling the second filling module to modify the department data report in the system database, wherein the modification request is generated by the filler of the business department after modifying the corresponding department data report based on the department terminal, and the modification request carries modification parameters; after the modification time expires, merging all department data reports in the system database to obtain the modified data report to be reported; calling the first verification module to perform data verification on the cell value corresponding to each cell in the modified data report to be reported according to the verification rules, and generating a verification result for each cell.
4. The method according to claim 3, characterized in that, Within a preset modification time, in response to a modification request uploaded by a business department, the second data entry module is invoked to modify the departmental data report in the system database. This includes: parsing the modification parameters carried in the modification request to obtain the report identifier to be modified, the cell identifier to be modified, the cell value to be modified, and the data entry person; determining the departmental data report corresponding to the report identifier to be modified in the system database, and determining the cell to be modified in the departmental data report based on the cell identifier to be modified; replacing the current cell value of the cell to be modified with the cell value to be modified, and associating the cell to be modified with the data entry person to obtain the modified departmental report data.
5. The method according to claim 1, characterized in that, The step of calling the first verification module to perform data verification on the cell values corresponding to each cell in the data report to be submitted, according to the verification rules, and generating a verification result for each cell, includes: for the data table to be submitted, calling the first verification module to perform threshold verification on each cell value based on the soft verification rules, and generating a soft verification result; calling the first verification module to calculate and verify the logical relationship between cell values belonging to the same sub-table based on the intra-table verification rules, and generating an intra-table verification result, wherein the data table to be submitted includes at least one sub-table; and calling the first verification module to perform inter-table verification on different sub-tables based on the inter-table verification rules. Cross-table validation is performed on the data linkage relationship of related cell values to generate inter-table validation results. For any cell, if the soft validation result, intra-table validation result, and inter-table validation result all indicate that the data is correct, a validation result indicating that the validation passed is generated. If any rule validation result among the soft validation result, intra-table validation result, and inter-table validation result indicates that the data is incorrect, a validation result indicating that the validation failed is generated, along with the rule validation result indicating the data error and the validation rule corresponding to the rule validation result. The display style of the cell is adjusted according to the error display style associated with the validation rule.
6. The method according to claim 1, characterized in that, After performing data validation on the cell value corresponding to each cell in the data report to be submitted and generating a validation result for each cell, the method further includes: if any cell's validation result indicates that the validation failed, the first validation module is invoked to determine the person filling out the cell according to the standard description; a re-filling prompt is generated and sent to the department terminal corresponding to the person filling out the cell, so that the person filling out the cell can re-fill out the cell value based on the department terminal according to the filling prompt until the validation result corresponding to the cell indicates that the validation passed.
7. The method according to claim 1, characterized in that, Before the reporting module submits the data report to be submitted to the reporting channel recorded in the report information, the method further includes: calling the second verification module to send the data report to be submitted to the review terminal and obtaining the review result uploaded by the review terminal; if the review result indicates that the review is passed, then submitting the data report to be submitted to the reporting channel recorded in the report information; if the review result indicates that the review is not passed, then reading the review comments associated with the review result, determining the cell identifier to be modified and the person filling it out, and generating a re-submission prompt, sending the re-submission prompt to the department terminal corresponding to the person filling it out, so that the person filling it out can re-submit the cell value corresponding to the cell identifier to be modified based on the department terminal according to the submission prompt, until the review result corresponding to the report to be submitted indicates that the review is passed.
8. A data reporting device for data aggregation, characterized in that, include: A configuration module is used to obtain the data reporting template corresponding to the channel to be reported, and set report parameters for the data reporting template according to the reporting rules corresponding to the reporting channel to obtain the report template. The report parameters include the filling process, report information, cell information, standard description and validation rules. A first filling module is used to respond to the data reporting instruction, obtain the data to be reported from the data warehouse, and fill the data to be reported into the corresponding report template according to the cell information and the standard description to obtain the data to be reported report. The first verification module is used to perform data verification on the cell value corresponding to each cell in the data report to be submitted according to the verification rules, and generate a verification result for each cell. The verification rules include intra-table verification rules, inter-table verification rules, and soft verification rules. The reporting module is used to report the data report to be reported to the reporting channel recorded in the report information if the verification result corresponding to each cell indicates that the verification is passed.
9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 7.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.