Multi-terminal linkage early warning method and system based on audit rectification progress monitoring

Abstract

The invention provides a multi-terminal linkage early warning method and system based on auditing rectification progress monitoring, and relates to the technical field of auditing, and the method comprises the steps: carrying out the real-time comparison of rectification progress data, predicted rectification completion time and rectification time limit based on an auditing rectification problem; judging whether the rectification progress data exceeds the predicted rectification completion time or rectification time limit or not, and generating a judgment result; when the judgment result is that the rectification progress data exceeds the predicted rectification completion time but does not exceed the rectification time limit, generating a first early warning mark; when the judgment result is that the rectification progress data exceeds the rectification time limit, generating a second early warning mark; and activating the message push module to synchronize to the intelligent terminal application, and adjusting the rectification progress data according to the early warning state information. According to the method and the device, the technical problem that the rectification delay early warning efficiency is further influenced due to the fact that the rectification progress is difficult to monitor and the delay degree cannot be effectively identified in the prior art is solved.

Description

Technical Field

[0001] This application relates to the field of auditing technology, specifically to a multi-terminal linkage early warning method and system based on audit rectification progress monitoring. Background Technology

[0002] In the current field of audit rectification monitoring, there is a general reliance on process-oriented business management, lacking the ability to automatically monitor and quantitatively analyze rectification progress data. This results in the inability to identify the degree of task delays and potential risks in a real-time and effective manner. Because a real-time comparison mechanism based on progress, estimated completion time, and rectification deadlines has not been established, it is difficult to accurately judge deviations from the plan, thus hindering proactive, tiered early warning systems. Furthermore, existing methods typically keep audit information internal, requiring relevant personnel to actively log into the management platform to view task status. This leads to delays in the transmission of early warning information, preventing timely synchronization of rectification delay risks with responsible parties and severely impacting the efficiency of early warning response and the closed-loop control of rectification management.

[0003] In summary, existing technologies suffer from the technical problem that makes it difficult to monitor the progress of rectification, thus failing to effectively identify the degree of delay and further affecting the efficiency of rectification delay early warning. Summary of the Invention

[0004] The purpose of this application is to provide a multi-terminal linkage early warning method and system based on audit rectification progress monitoring, in order to solve the technical problem in the prior art that the difficulty in monitoring the rectification progress leads to the inability to effectively identify the degree of delay, which further affects the efficiency of rectification delay early warning.

[0005] To achieve the above objectives, this application provides a multi-terminal linkage early warning method and system based on audit rectification progress monitoring.

[0006] Firstly, this application provides a multi-terminal linkage early warning method based on audit rectification progress monitoring. This method is implemented through a multi-terminal linkage early warning system based on audit rectification progress monitoring. The method includes: acquiring rectification progress data, expected completion time, and rectification time limit for audit rectification issues; performing real-time comparisons of the rectification progress data, the expected completion time, and the rectification time limit to determine whether the rectification progress data exceeds the expected completion time or the rectification time limit, and generating a judgment result; generating a first early warning flag when the judgment result indicates that the rectification progress data exceeds the expected completion time but does not exceed the rectification time limit; generating a second early warning flag when the judgment result indicates that the rectification progress data exceeds the rectification time limit; and activating a message push module to synchronize with smart terminal applications when the first or second early warning flag is generated, adjusting the rectification progress data according to the early warning status information.

[0007] Optionally, the system retrieves audit rectification issues from multiple data sources to respond to and update rectification events; performs logical verification on the rectification events, and generates a verification-passed dataset when the rectification events pass the logical verification; stores the verification-passed dataset in the audit rectification issue database for identification, generating multiple valid monitoring targets; and tracks the rectification progress data in real time according to the multiple valid monitoring targets.

[0008] Optionally, the rectification events are iterated through to assess rectification completion and an estimated rectification completion time is set; extreme value analysis is performed on the rectification events according to the estimated rectification completion time to determine the initial rectification time limit; the estimated initial rectification completion time and the initial rectification time limit are verified as follows: S1: Verify whether the estimated rectification completion time is not later than the initial rectification time limit, and generate a first verification result; S2: Introduce the audit problem discovery date to verify whether the estimated rectification completion time and the initial rectification time limit are not earlier than the audit problem discovery date, and generate a second verification result; based on the first verification result and the second verification result, the estimated initial rectification completion time and the initial rectification time limit are updated to determine the estimated rectification completion time and the rectification time limit.

[0009] Optionally, the rectification progress data is continuously polled and monitored to generate a rectification progress status, which is either completed or incomplete. Based on the rectification progress status, event trigger analysis is performed according to a preset time period to obtain the current time parameter. The current time parameter is compared with the expected rectification completion time to generate a first comparison result. The current time parameter is compared with the rectification deadline to generate a second comparison result. The first comparison result and the second comparison result are integrated according to the rectification progress status to construct the judgment result.

[0010] Optionally, if the rectification progress status is incomplete, and the first comparison result indicates that the rectification progress data exceeds the expected rectification completion time, and the second comparison result indicates that the rectification progress data does not exceed the rectification time limit, a first-level early warning judgment result is generated; the first-level early warning judgment result is used as an index to search the audit rectification problem database to determine a first identifier; the first identifier is associated with the first-level early warning judgment result and stored in the cache area to generate the first early warning tag.

[0011] Optionally, if the rectification progress status is incomplete, and the first comparison result indicates that the rectification progress data exceeds the expected rectification completion time, and the second comparison result indicates that the rectification progress data exceeds the rectification time limit, a second-level early warning judgment result is generated; the second-level early warning judgment result is used as an index to search the audit rectification problem database to determine a second identifier; the second identifier is associated with the second-level early warning judgment result and stored in the cache area to generate a second early warning tag.

[0012] Optionally, in response to the first warning flag, a warning configuration is performed to determine a first warning level, and a first push strategy is generated based on the first warning level; in response to the second warning flag, a warning configuration is performed to determine a second warning level, and a second push strategy is generated based on the second warning level; the first push strategy and the second push strategy are linked across multiple terminals to construct a warning push task; the warning push task is filled into a message queue, and the message push module is activated; the warning push task is transmitted to a smart terminal application through the message push module to generate the warning status information.

[0013] Secondly, this application also provides a multi-terminal linkage early warning system based on audit rectification progress monitoring, used to execute the multi-terminal linkage early warning method based on audit rectification progress monitoring as described in the first aspect. The multi-terminal linkage early warning system based on audit rectification progress monitoring includes: a data acquisition module, used to acquire rectification progress data, expected rectification completion time, and rectification time limit for audit rectification issues; a real-time comparison module, used to perform real-time comparison based on the rectification progress data, the expected rectification completion time, and the rectification time limit, to determine whether the rectification progress data exceeds the expected rectification completion time or the rectification time limit, and to generate a judgment result; a first early warning module, used to generate a first early warning flag when the judgment result indicates that the rectification progress data exceeds the expected rectification completion time but does not exceed the rectification time limit; a second early warning module, used to generate a second early warning flag when the judgment result indicates that the rectification progress data exceeds the rectification time limit; and an information push module, used to activate a message push module to synchronize to a smart terminal application when the first or second early warning flag is generated, and to adjust the rectification progress data according to the early warning status information.

[0014] One or more technical solutions provided in this application have at least the following technical effects or advantages: By acquiring rectification progress data, estimated completion time, and rectification deadline for audit rectification issues; and by comparing the rectification progress data, estimated completion time, and rectification deadline in real time to determine whether the rectification progress data exceeds the estimated completion time or rectification deadline, a judgment result is generated. When the judgment result indicates that the rectification progress data exceeds the estimated completion time but does not exceed the rectification deadline, a first warning flag is generated; when the judgment result indicates that the rectification progress data exceeds the rectification deadline, a second warning flag is generated. When either the first or second warning flag is generated, a message push module is activated to synchronize with the smart terminal application, and the rectification progress data is adjusted according to the warning status information. In other words, by acquiring rectification progress data in real time and comparing it with the estimated completion time and rectification deadline, effective monitoring of rectification progress is achieved. When the rectification progress exceeds the estimated completion time or rectification deadline, a first warning flag is generated; when the rectification progress exceeds the rectification deadline, a second warning flag is generated, and a message push module is activated to synchronize with the smart terminal application. This comprehensively identifies and assesses audit rectification risks, improving the efficiency of rectification delay warnings.

[0015] The above description is merely an overview of the technical solution of this application. To better understand the technical means of this application and to facilitate its implementation according to the description, and to make the above and other objects, features, and advantages of this application more apparent, specific embodiments of this application are described below. It should be understood that the content described in this section is not intended to identify key or important features of the embodiments of this application, nor is it intended to limit the scope of this application. Other features of this application will become readily apparent through the following description. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are merely exemplary. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0017] Figure 1 This is a flowchart illustrating the multi-terminal linkage early warning method based on audit rectification progress monitoring in this application.

[0018] Figure 2 This is a schematic diagram of the multi-terminal linkage early warning system based on audit rectification progress monitoring in this application.

[0019] Explanation of reference numerals in the attached diagram: Data acquisition module 11, real-time comparison module 12, first early warning module 13, second early warning module 14, information push module 15. Detailed Implementation

[0020] This application provides a multi-terminal linkage early warning method and system based on audit rectification progress monitoring, solving the technical problem in existing technologies where the inability to effectively identify the degree of delay due to the difficulty in monitoring rectification progress further affects the efficiency of rectification delay early warning. By acquiring rectification progress data in real time and comparing it with the expected completion time or rectification deadline, effective monitoring of rectification progress is achieved. When the rectification progress exceeds the expected completion time or rectification deadline, a first early warning flag is generated; when the rectification progress exceeds the rectification deadline, a second early warning flag is generated, activating the message push module to synchronize to smart terminal applications. This comprehensively identifies and assesses audit rectification risks, improving the efficiency of rectification delay early warning.

[0021] The technical solutions of this application will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. It should be understood that this application is not limited to the exemplary embodiments described herein. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application. It should also be noted that, for ease of description, only the parts related to this application are shown in the accompanying drawings, not all of them.

[0022] Example 1, please refer to the appendix. Figure 1 This application provides a multi-terminal linkage early warning method based on audit rectification progress monitoring. The method is applied to a multi-terminal linkage early warning system based on audit rectification progress monitoring, and specifically includes the following steps: S100: Obtain data on the progress of audit rectification issues, the estimated completion time of rectification, and the rectification deadline.

[0023] Furthermore, S100 of this application includes: responding to audit rectification issues based on multiple data sources and updating rectification events; performing logical verification on the rectification events, and generating a verification-passed dataset when the rectification events pass the logical verification; storing the verification-passed dataset in the audit rectification issue database for identification, and generating multiple valid monitoring targets; and performing real-time tracking according to the multiple valid monitoring targets to determine the rectification progress data.

[0024] Specifically, through pre-defined data interfaces, such as APIs and database connectors, the latest list of audit rectification issues is retrieved from various data sources at preset time intervals, such as every 15 minutes. Each retrieved issue is encapsulated into a structured rectification event object. The multiple data sources are various independent business systems that generate audit rectification issues, such as internal audit management systems, supply chain management systems, and human resources systems. A rectification event is a complete data package of a specific audit issue retrieved from a data source; it is a structured object that typically includes key fields such as a unique issue identifier, issue title, detailed issue description, responsible department, primary responsible person, audit discovery date, and required rectification deadline.

[0025] Initiate an automated verification process to perform multiple logical verifications on rectification events. Verification rules are pre-configured in the rule engine. For example, rule one checks if the planned completion date is no earlier than the audit discovery date; rule two verifies if the responsible department code exists in the company's standard organizational structure dictionary; and rule three ensures that the problem description field is not empty and meets the length requirements. Logical verification executes a series of predefined rule checks on the event to ensure its validity and logical rationality.

[0026] Any event must pass all validation rules to be included in the validation-passed dataset. The validation-passed dataset is then batch-written into the audit rectification issue database, assigning each record a globally unique system ID and initializing its status as a valid monitoring target. Once the target takes effect, the real-time tracking module starts, continuously acquiring and updating the rectification progress data for each target—typically the percentage of completion—by polling via APIs, receiving proactive reports from responsible parties, and parsing status feedback from business systems, such as the completion status of tasks in a project management system. Audit rectification issue data is integrated and cleaned from multiple data sources, and logical validation ensures the accuracy and completeness of the data.

[0027] Furthermore, this application also includes the following steps: traversing the rectification events to assess rectification completion and setting an estimated rectification completion time; performing extreme value analysis on the rectification events according to the estimated rectification completion time to determine the initial rectification deadline; verifying the estimated initial rectification completion time and the initial rectification deadline: S1: verifying whether the estimated rectification completion time is not later than the initial rectification deadline, generating a first verification result; S2: introducing the audit issue discovery date to verify whether the estimated rectification completion time and the initial rectification deadline are not earlier than the audit issue discovery date, generating a second verification result; updating the estimated initial rectification completion time and the initial rectification deadline based on the first verification result and the second verification result to determine the estimated rectification completion time and the rectification deadline.

[0028] Specifically, each rectification event is assessed for completion, typically based on factors such as the actual completion status of rectification measures, remaining workload, and required resources, to determine the estimated completion time. The estimated completion time is set based on the rectification completion assessment results and is usually a specific date or time. Extreme value analysis is then performed on the rectification events according to the estimated completion time to determine the latest completion time, i.e., the initial rectification deadline. A fixed buffer period is usually added to the estimated completion time to obtain the initial rectification deadline.

[0029] Verify the initial expected completion time and initial rectification deadline for rectification. Verify that the expected completion time is no later than the initial rectification deadline to prevent the absurd situation where the planned completion time is later than the final deadline. Introduce the audit issue discovery date to verify that the expected completion time and initial rectification deadline are no earlier than the audit issue discovery date. The audit issue discovery date is the date the auditor formally records and reports the issue; it is the baseline for all time calculations. Ensure that rectification occurs after the issue is discovered, conforming to a linear timeline.

[0030] Based on the first and second verification results, the estimated initial time for rectification completion and the initial rectification deadline are updated to obtain the final estimated rectification completion time and rectification deadline. If either the first or second verification result fails, it is marked as an abnormal time setting, and the responsible person is automatically notified to make corrections. Only after both the first and second verification results pass will the current estimated initial time for rectification completion and the initial rectification deadline be used as the estimated rectification completion time and rectification deadline.

[0031] The verification process ensures that the set expected completion time and deadline for rectification conform to the actual situation and regulations, avoids problems and risks caused by unreasonable expected completion times, helps improve the accuracy of monitoring and early warning of rectification progress, and ensures that rectification work can be completed on time.

[0032] S200: Based on the rectification progress data, the expected rectification completion time, and the rectification time limit, a real-time comparison is performed to determine whether the rectification progress data exceeds the expected rectification completion time or the rectification time limit, and a judgment result is generated.

[0033] Furthermore, S200 of this application includes: continuously polling and monitoring the rectification progress data to generate a rectification progress status, wherein the rectification progress status is a completed status or an incomplete status; performing event trigger analysis based on the rectification progress status according to a preset time period to obtain a current time parameter; comparing the current time parameter with the expected rectification completion time to generate a first comparison result; comparing the current time parameter with the rectification deadline to generate a second comparison result; and integrating the first comparison result and the second comparison result according to the rectification progress status to construct the judgment result.

[0034] Specifically, the progress data of all rectification events in the audit rectification issues is continuously polled and monitored at fixed short intervals. Each time the current rectification progress data is obtained, the current rectification progress status is determined according to preset rules, such as completed or incomplete. Event-triggered analysis is performed according to preset time cycles. When the predetermined time is reached, the analysis process is initiated: first, the standard current time parameter is obtained; then, for each target in the incomplete state, two key time comparisons are performed. First, the current time is compared with the expected rectification completion time to determine if it has exceeded the limit; second, the current time is compared with the rectification deadline to determine if it has exceeded the deadline. Event-triggered analysis automatically initiates a complete analysis process after the preset time cycle is reached; this process is initiated as if triggered by a time event. The current time parameter is the current standard time obtained when performing event-triggered analysis.

[0035] The current time parameter is compared with the estimated rectification completion time to obtain the first comparison result. If the current time exceeds the estimated rectification completion time, but the rectification progress status is incomplete, an early warning (yellow warning) is triggered, indicating that the work progress may deviate from the plan and requires attention. The current time parameter is then compared with the rectification deadline to generate the second comparison result. If the current time exceeds the rectification deadline, but the rectification progress status is incomplete, a serious warning (red warning) is triggered, indicating that there is a serious violation and immediate action is required.

[0036] The first and second comparison results are integrated according to the rectification progress status to construct a judgment result. This judgment result will be used to determine whether an early warning needs to be triggered, and if so, what type. Through event-triggered analysis, changes in the rectification progress are tracked in real time, and it is determined whether an early warning needs to be triggered. By comparing the current time parameter with the expected rectification completion time and rectification deadline, first and second comparison results are generated, and a judgment result is constructed. This helps to promptly identify deviations from the planned rectification progress and take corresponding measures to prevent the escalation of problems and the accumulation of risks.

[0037] S300: When the judgment result is that the rectification progress data exceeds the expected rectification completion time but does not exceed the rectification time limit, a first warning mark is generated.

[0038] Furthermore, S300 of this application includes: if the rectification progress status is the incomplete status, the first comparison result is that the rectification progress data exceeds the expected rectification completion time, and the second comparison result is that the rectification progress data does not exceed the rectification time limit, generating a first-level early warning judgment result; using the first-level early warning judgment result as an index to search the audit rectification problem database to determine a first identifier; associating the first identifier with the first-level early warning judgment result and storing it in a cache area to generate the first early warning tag.

[0039] Specifically, if the rectification progress status is "incomplete," and the first comparison result indicates that the rectification completion time has exceeded the expected time, while the second comparison result indicates that the rectification deadline has not been exceeded, a Level 1 warning judgment result is generated, indicating that the work progress may deviate from the plan and requires attention. The Level 1 warning judgment result is used as an index to search the audit rectification issue database to determine the first identifier associated with the Level 1 warning judgment result. The first identifier is a complete set of data used to uniquely identify and describe this warning event, including not only the issue ID but also the responsible department, responsible person, responsible person's contact information, issue title, and other contextual information necessary for issuing the warning.

[0040] The first identifier is associated with the first-level warning judgment result and stored in the cache area. The cache area is a temporary data storage area for fast data access and processing. By associating the first identifier with the first-level warning judgment result, rectification events associated with that warning judgment result can be quickly retrieved and identified. After storage, a first warning tag is generated to identify and notify relevant responsible persons, indicating that the first-level warning has been triggered. Relevant responsible persons can receive warning information through push notifications and take corresponding measures to ensure that rectification work can be completed on time.

[0041] S400: When the judgment result indicates that the rectification progress data exceeds the rectification time limit, a second warning mark is generated.

[0042] Furthermore, S400 of this application includes: if the rectification progress status is the incomplete status, and the first comparison result is that the rectification progress data exceeds the expected rectification completion time, and the second comparison result is that the rectification progress data exceeds the rectification time limit, generating a second-level early warning judgment result; using the second-level early warning judgment result as an index to search the audit rectification problem database to determine a second identifier; associating the second identifier with the second-level early warning judgment result and storing it in a cache area to generate a second early warning tag.

[0043] Specifically, if the rectification progress status is incomplete, and the first comparison result indicates that the rectification completion time has exceeded the expected time, and the second comparison result indicates that the rectification deadline has been exceeded, a Level 2 warning judgment result is generated, indicating that a serious violation has occurred and must be dealt with immediately. The Level 2 warning judgment result is a data object that indicates a serious violation and contains core information such as the warning level (Level 2), the problem ID, and the judgment time.

[0044] The second-level early warning judgment result is used as an index to search the audit rectification issue database to identify a second identifier associated with the second-level early warning judgment result. The second identifier is similar to the first identifier, but because it is of a higher level, it may contain more information, such as a list of supervisors to be copied, a higher-level approval flow ID, etc. The second identifier is then associated with the second-level early warning judgment result and stored in a cache. This associated storage allows for quick retrieval and identification of rectification events associated with that early warning judgment result.

[0045] After storage, a second warning tag is generated to identify and notify relevant responsible persons, indicating that a second-level warning has been triggered. Relevant responsible persons can receive the warning information via push notifications and take corresponding measures to ensure that rectification work is completed on time. By creating an independent second-level warning tag, high-level risks can be internally distinguished from ordinary risks, ensuring that critical risks are given priority.

[0046] S500: When the first warning marker or the second warning marker is generated, the message push module is activated to synchronize with the smart terminal application, and the rectification progress data is adjusted according to the warning status information.

[0047] Furthermore, S500 of this application includes: responding to the first warning flag to configure a warning, determining a first warning level, and generating a first push strategy based on the first warning level; responding to the second warning flag to configure a warning, determining a second warning level, and generating a second push strategy based on the second warning level; linking the first push strategy and the second push strategy across multiple terminals to construct a warning push task; filling the warning push task into a message queue and activating a message push module; and transmitting the warning push task to a smart terminal application through the message push module to generate the warning status information.

[0048] Specifically, the system continuously monitors the cache and responds immediately upon detecting a new alert flag. Based on either the first or second alert flag, it queries the alert configuration rule base to determine the corresponding alert level, i.e., the first alert level and the second alert level. In response to the first alert flag, it configures the alert, determines the first alert level, and generates a first push strategy based on that level. For example, if the first alert level is high, it sets a shorter push interval and selects an urgent push method, such as SMS or phone notification. Similarly, in response to the second alert flag, it configures the alert, determines the second alert level, and generates a second push strategy based on that level. For example, if the second alert level is high, it sets an even shorter push interval and selects a more urgent push method, such as SMS or phone notification.

[0049] The first and second push strategies are linked across multiple devices to construct an early warning push task. This multi-device linkage process involves integrating the first and second push strategies to deliver early warning information to multiple terminal devices. For example, sending early warning information simultaneously to mobile phones, tablets, and computers. An early warning push task is an executable task object that encapsulates complete push instructions, including the specific content of the early warning, a list of target users, and a list of selected push channels.

[0050] The alert push task is filled into the message queue, which is a queue used to store and transmit messages, ensuring the orderly delivery and processing of messages. By filling the alert push task into the message queue, the orderly delivery and processing of alert information is ensured. The message push module is immediately activated to retrieve push tasks from the message queue and call the interfaces of each channel to complete the final message sending.

[0051] The alert push module transmits the alert push task to the smart terminal application, namely the mobile office application that users use daily, such as an APP. The alert information is sent to the smart terminal application via the push module, generating alert status information. The alert status information is the specific notification content ultimately presented on the user's smart terminal application; it is generated by the system and transmitted via the push module, resulting in visual or interactive alarm information on the user's end.

[0052] For scenarios involving exceeding the expected completion time and deadline for rectification, notifications are typically sent via the app. A notification is sent 15 calendar days in advance, and again on the first calendar day after the deadline. Alternatively, a notification can be sent daily starting 15 calendar days in advance. When rectification progress warning conditions are met, the progress reports submitted by the responsible rectification unit need to be controlled. Because the progress is already behind schedule, when submitting rectification progress reports, the option to "rectify according to schedule" cannot be selected; only "behind schedule" or "rectified" can be chosen. When the responsible rectification unit applies for rectification adjustments, the system needs to determine whether the issue is overdue based on the new date. When a red "overdue" date is reached, the responsible rectification unit is not allowed to select "rectify according to schedule" when submitting rectification progress reports. When an issue exceeds the rectification deadline and is marked with a red icon, the responsible rectification unit cannot select the "rectify according to schedule" option when submitting the next rectification status report; only "behind schedule" or "rectified" can be chosen. When the responsible unit submits the rectification report, if an error message appears indicating that the batch of issues has exceeded the rectification deadline, and the rectification progress for that issue is set to "rectify according to progress," then the message will prompt that the current issue summary has exceeded the rectification deadline, and the rectification progress does not support "rectify according to progress." Please adjust and try again. Also, refresh the submission page. Different prompts will be given for issues exceeding different deadlines.

[0053] If a rectification adjustment is requested, the new date will be used to determine if the deadline has passed. After the rectification adjustment application is approved, the responsible unit personnel need to determine whether the issue has exceeded the expected rectification completion time (highlighted in yellow) or the actual rectification time (highlighted in red) based on the adjusted estimated rectification completion time and the automatically calculated rectification time after the rectification type was adjusted. If the rectification time has not been exceeded after the adjustment, the responsible unit personnel can freely choose the rectification progress when submitting the rectification status next time, without being controlled by the system. The rectification time needs to be recalculated based on the newly selected rectification type and rectification configuration. The estimated rectification completion time for the rectification adjustment needs to be subject to restrictions, and the submission cannot be later than the adjusted rectification time.

[0054] Through strategic configuration, different levels of risk can automatically trigger push notifications of varying severity and scope, ensuring efficient allocation of management resources and appropriate early warning intensity.

[0055] In summary, the multi-terminal linkage early warning method based on audit rectification progress monitoring provided in this application has the following technical effects: By acquiring rectification progress data, estimated completion time, and rectification deadline for audit rectification issues; and by comparing the rectification progress data, estimated completion time, and rectification deadline in real time to determine whether the rectification progress data exceeds the estimated completion time or rectification deadline, a judgment result is generated. When the judgment result indicates that the rectification progress data exceeds the estimated completion time but does not exceed the rectification deadline, a first warning flag is generated; when the judgment result indicates that the rectification progress data exceeds the rectification deadline, a second warning flag is generated. When either the first or second warning flag is generated, a message push module is activated to synchronize with the smart terminal application, and the rectification progress data is adjusted according to the warning status information. In other words, by acquiring rectification progress data in real time and comparing it with the estimated completion time and rectification deadline, effective monitoring of rectification progress is achieved. When the rectification progress exceeds the estimated completion time or rectification deadline, a first warning flag is generated; when the rectification progress exceeds the rectification deadline, a second warning flag is generated, and a message push module is activated to synchronize with the smart terminal application. This comprehensively identifies and assesses audit rectification risks, improving the efficiency of rectification delay warnings.

[0056] Example 2: Based on the same inventive concept as the multi-terminal linkage early warning method for monitoring audit rectification progress in Example 1, this application also provides a multi-terminal linkage early warning system for monitoring audit rectification progress. Please refer to the appendix. Figure 2 The multi-terminal linkage early warning system based on audit rectification progress monitoring includes: The data acquisition module 11 is used to acquire the rectification progress data, expected rectification completion time, and rectification time limit of the audit rectification issues; the real-time comparison module 12 is used to perform real-time comparison based on the rectification progress data, the expected rectification completion time, and the rectification time limit, to determine whether the rectification progress data exceeds the expected rectification completion time or the rectification time limit, and to generate a judgment result; the first early warning module 13 is used to generate a first early warning mark when the judgment result is that the rectification progress data exceeds the expected rectification completion time but does not exceed the rectification time limit; the second early warning module 14 is used to generate a second early warning mark when the judgment result is that the rectification progress data exceeds the rectification time limit; the information push module 15 is used to activate the message push module to synchronize to the smart terminal application when the first early warning mark or the second early warning mark is generated, and to adjust the rectification progress data according to the early warning status information.

[0057] Furthermore, the data acquisition module 11 in the multi-terminal linkage early warning system based on audit rectification progress monitoring is also used for: retrieving audit rectification issues from multiple data sources to respond and update rectification events; performing logical verification on the rectification events, and generating a verification-passed dataset when the rectification events pass the logical verification; storing the verification-passed dataset in the audit rectification issue database for identification, and generating multiple valid monitoring targets; and performing real-time tracking according to the multiple valid monitoring targets to determine the rectification progress data.

[0058] Furthermore, the data acquisition module 11 in the multi-terminal linkage early warning system based on audit rectification progress monitoring is also used for: traversing the rectification events to evaluate rectification completion and setting the expected rectification completion time; performing extreme value analysis on the rectification events according to the expected rectification completion time to determine the initial rectification time limit; verifying the expected initial rectification completion time and the initial rectification time limit: S1: verifying whether the expected rectification completion time is not later than the initial rectification time limit, generating a first verification result; S2: introducing the audit problem discovery date to verify whether the expected rectification completion time and the initial rectification time limit are not earlier than the audit problem discovery date, generating a second verification result; updating the expected initial rectification completion time and the initial rectification time limit based on the first verification result and the second verification result to determine the expected rectification completion time and the rectification time limit.

[0059] Furthermore, the real-time comparison module 12 in the multi-terminal linkage early warning system based on audit rectification progress monitoring is also used for: continuously polling and monitoring the rectification progress data to generate a rectification progress status, wherein the rectification progress status is either completed or incomplete; performing event trigger analysis based on the rectification progress status according to a preset time period to obtain a current time parameter; comparing the current time parameter with the expected rectification completion time to generate a first comparison result; comparing the current time parameter with the rectification deadline to generate a second comparison result; and integrating the first comparison result and the second comparison result according to the rectification progress status to construct the judgment result.

[0060] Furthermore, the first early warning module 13 in the multi-terminal linkage early warning system based on audit rectification progress monitoring is also used to: generate a first-level early warning judgment result if the rectification progress status is incomplete, the first comparison result is that the rectification progress data exceeds the expected rectification completion time, and the second comparison result is that the rectification progress data does not exceed the rectification time limit; use the first-level early warning judgment result as an index to search the audit rectification problem database to determine a first identifier; associate the first identifier with the first-level early warning judgment result and store it in the cache area to generate the first early warning tag.

[0061] Furthermore, the second early warning module 14 in the multi-terminal linkage early warning system based on audit rectification progress monitoring is also used to: generate a second-level early warning judgment result when the rectification progress status is incomplete, the first comparison result is that the rectification progress data exceeds the expected rectification completion time, and the second comparison result is that the rectification progress data exceeds the rectification time limit; use the second-level early warning judgment result as an index to search the audit rectification problem database to determine a second identifier; and associate the second identifier with the second-level early warning judgment result and store it in the cache area to generate a second early warning tag.

[0062] Furthermore, the information push module 15 in the multi-terminal linkage early warning system based on audit rectification progress monitoring is also used for: responding to the first early warning flag to configure an early warning, determining a first early warning level, and generating a first push strategy based on the first early warning level; responding to the second early warning flag to configure an early warning, determining a second early warning level, and generating a second push strategy based on the second early warning level; linking the first push strategy and the second push strategy across multiple terminals to construct an early warning push task; filling the early warning push task into a message queue and activating the message push module; and transmitting the early warning push task to a smart terminal application through the message push module to generate the early warning status information.

[0063] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. The multi-terminal linkage early warning method and specific examples based on audit rectification progress monitoring in the aforementioned embodiment 1 are also applicable to the multi-terminal linkage early warning system based on audit rectification progress monitoring in this embodiment. Through the foregoing detailed description of the multi-terminal linkage early warning method based on audit rectification progress monitoring, those skilled in the art can clearly understand the multi-terminal linkage early warning system based on audit rectification progress monitoring in this embodiment. Therefore, for the sake of brevity, it will not be described in detail here.

[0064] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0065] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of this application and its equivalents, this application also intends to include such modifications and variations.

Claims

1. A multi-end linkage early warning method based on audit rectification progress monitoring, characterized in that, include: Obtain data on the progress of audit rectification issues, the estimated completion time of rectification, and the rectification deadline; Based on the real-time comparison of the rectification progress data, the expected rectification completion time, and the rectification time limit, it is determined whether the rectification progress data exceeds the expected rectification completion time or the rectification time limit, and a judgment result is generated. When the judgment result indicates that the rectification progress data exceeds the expected rectification completion time but does not exceed the rectification time limit, a first warning flag is generated; When the judgment result indicates that the rectification progress data exceeds the rectification time limit, a second early warning marker is generated; When the first warning marker or the second warning marker is generated, the message push module is activated to synchronize with the smart terminal application, and the rectification progress data is adjusted according to the warning status information.

2. The multi-end linkage early warning method based on audit rectification progress monitoring according to claim 1, wherein, Methods for obtaining progress data on audit rectification issues include: Retrieve audit rectification issues from multiple data sources and update rectification events accordingly; The rectification event is logically validated, and when the rectification event passes the logical validation, a validation pass dataset is generated. The verification data is stored in the audit rectification issue database for identification, generating multiple valid monitoring targets; Real-time tracking is performed on the multiple effective monitoring targets to determine the rectification progress data.

3. The multi-end linkage early warning method based on audit rectification progress monitoring according to claim 2, characterized in that, Methods for obtaining the estimated completion time and time limit for audit rectification issues include: Iterate through the rectification events to assess the completion of rectification and set the estimated completion time for rectification. An extreme value analysis was performed on the rectification event based on the estimated rectification completion time to determine the initial rectification time limit; Verify the estimated initial time for completion of rectification and the initial time limit for rectification: S1: Verify whether the estimated rectification completion time is not later than the initial rectification time limit, and generate the first verification result; S2: Introduce the audit issue discovery date to verify whether the estimated rectification completion time and the initial rectification deadline are not earlier than the audit issue discovery date, and generate a second verification result; Based on the first verification result and the second verification result, the estimated initial time for completion of rectification and the initial time limit for rectification are updated to determine the estimated time for completion of rectification and the time limit for rectification.

4. The multi-end linkage early warning method based on audit rectification progress monitoring according to claim 2, characterized in that, Based on a real-time comparison of the rectification progress data, the estimated rectification completion time, and the rectification time limit, a determination is made as to whether the rectification progress data exceeds the estimated rectification completion time or the rectification time limit, and a determination result is generated. The method includes: The rectification progress data is continuously polled and monitored to generate a rectification progress status, which is either completed or incomplete. Based on the rectification progress status, event trigger analysis is performed according to a preset time period to obtain the current time parameter; The current time parameter is compared with the estimated rectification completion time to generate a first comparison result; The current time parameter is compared with the rectification deadline to generate a second comparison result; The first comparison result and the second comparison result are integrated according to the rectification progress status to construct the judgment result.

5. The multi-end linkage early warning method based on audit rectification progress monitoring according to claim 4, characterized in that, When the judgment result indicates that the rectification progress data exceeds the expected rectification completion time but does not exceed the rectification time limit, a first warning flag is generated, the method including: If the rectification progress status is incomplete, and the first comparison result is that the rectification progress data exceeds the expected rectification completion time, and the second comparison result is that the rectification progress data does not exceed the rectification time limit, a first-level early warning judgment result is generated. The first-level early warning judgment result is used as an index to search the audit rectification issue database to determine the first identifier; The first identifier is associated with the first-level warning judgment result and stored in the cache area to generate the first warning tag.

6. The multi-end linkage early warning method based on audit rectification progress monitoring according to claim 5, characterized in that, When the judgment result indicates that the rectification progress data exceeds the rectification time limit, a second early warning marker is generated, the method including: If the rectification progress status is incomplete, and the first comparison result is that the rectification progress data exceeds the expected rectification completion time, and the second comparison result is that the rectification progress data exceeds the rectification time limit, a second-level early warning judgment result is generated. The second-level early warning judgment result is used as an index to search the audit rectification issue database to determine the second identifier; The second identifier is associated with the second-level warning judgment result and stored in the cache area to generate the second warning tag.

7. The multi-end linkage pre-warning method based on audit rectification progress monitoring according to claim 1, wherein, When the first warning marker or the second warning marker is generated, the message push module is activated to synchronize with the smart terminal application, and the rectification progress data is adjusted according to the warning status information. The method includes: In response to the first warning flag, a warning configuration is performed, a first warning level is determined, and a first push strategy is generated based on the first warning level. In response to the second warning flag, a warning configuration is performed, a second warning level is determined, and a second push strategy is generated based on the second warning level; The first push strategy and the second push strategy are linked across multiple terminals to construct an early warning push task; Fill the warning push task into the message queue and activate the message push module; The warning push task is transmitted to the smart terminal application through the message push module, and the warning status information is generated.

8. A multi-terminal linkage early warning system based on audit rectification progress monitoring, characterized in that: The step of implementing the multi-terminal linkage early warning method based on audit rectification progress monitoring as described in any one of claims 1 to 7, wherein the multi-terminal linkage early warning system based on audit rectification progress monitoring includes: The data acquisition module is used to acquire data on the progress of audit rectification issues, the estimated completion time of rectification, and the rectification deadline. The real-time comparison module is used to perform a real-time comparison based on the rectification progress data, the expected rectification completion time, and the rectification time limit, to determine whether the rectification progress data exceeds the expected rectification completion time or the rectification time limit, and to generate a judgment result. The first early warning module is used to generate a first early warning flag when the judgment result is that the rectification progress data exceeds the expected rectification completion time but does not exceed the rectification time limit; The second early warning module is used to generate a second early warning flag when the judgment result indicates that the rectification progress data exceeds the rectification time limit; The information push module is used to activate the message push module to synchronize with the smart terminal application when the first warning mark or the second warning mark is generated, and to adjust the rectification progress data according to the warning status information.

Images