Report data collection method and device, storage medium and server

Abstract

The embodiment of the invention discloses a report data collection method and device, a storage medium and terminal equipment, and relates to the field of data collection. According to the method and the device, the full-process automation of report data reporting is realized, and the working efficiency and the data accuracy are remarkably improved in each link from template matching, task allocation, filling notification, progress monitoring to data auditing. Therefore, resource waste caused by repeated labor and human errors is reduced, and more timely and accurate data support is provided for enterprise decision making.

Description

Technical Field

[0001] The present application relates to the field of data collection, and in particular to a method, device, storage medium and server for collecting report data. Background Art

[0002] Users collect and report report data according to business application scenarios. For example, according to regulatory needs, the State-owned Assets Supervision and Administration Commission collects monthly financial reports from central enterprises every month, and annual financial final accounts every year. The tax department collects tax returns from enterprises quarterly. The State-owned Assets Supervision and Administration Commission collects financial business-related reports from financial subsidiaries of central enterprises for financial supervision needs. Report collection mainly involves superior units, regulatory departments, etc. collecting a set of report data from relevant enterprises as needed. However, in the current market, the method of collecting report data is that the financial personnel of each department compile and submit and report manually to the superior unit. This method is inefficient and prone to errors. Summary of the invention

[0003] The embodiments of the present application provide a method, device, storage medium and server for collecting report data, which can solve the problems of low efficiency and easy errors in reporting report data in the prior art. The technical solution is as follows:

[0004] In a first aspect, an embodiment of the present application provides a method for collecting report data, the method comprising:

[0005] According to the basic information of the report receiving task obtained, the corresponding report receiving template is searched in the template library;

[0006] Matching a corresponding reporting subject type according to the report type of the report receiving template, and setting a task receiving user for the reporting subject type;

[0007] Sending a task receiving message to a terminal device of a task receiving user, wherein the task receiving message includes a download link address of the report receiving template, and instructing the task receiving user to use the terminal device to fill in the report receiving template and generate a target report;

[0008] Monitoring the report preparation progress of the task receiving user, and displaying a progress breakdown table according to the report preparation progress;

[0009] The target report returned by the task receiving user through the terminal device is received, and the target report is audited according to the preset data audit rules, and the target report and the audit result are displayed.

[0010] In a second aspect, an embodiment of the present application provides a device for collecting report data, the device comprising:

[0011] A query unit, used to query the corresponding report receiving template in the template library according to the acquired basic information of the report receiving task;

[0012] A matching unit, used for matching a corresponding reporting subject type according to the report type of the report receiving template, and setting a task receiving user for the reporting subject type;

[0013] A sending unit, used to send a task receiving message to a terminal device of a task receiving user, wherein the task receiving message includes a download link address of the report receiving template, and instructs the task receiving user to use the terminal device to fill in the report receiving template and generate a target report;

[0014] A monitoring unit, used to monitor the report preparation progress of the task receiving user, and display a progress list according to the report preparation progress;

[0015] The receiving unit is used to receive the target report returned by the task receiving user through the terminal device, and to review the target report according to the preset data audit rules, and to display the target report and the audit result.

[0016] In a third aspect, an embodiment of the present application provides a computer storage medium, wherein the computer storage medium stores a plurality of instructions, wherein the instructions are suitable for being loaded by a processor and executing the above-mentioned method steps.

[0017] In a fourth aspect, an embodiment of the present application provides a server, which may include: a processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the above-mentioned method steps.

[0018] The beneficial effects brought about by the technical solutions provided by some embodiments of the present application include at least:

[0019] According to the basic information of the report receiving task, the corresponding report receiving template can be automatically searched and matched in the template library, and then the reporting subject type and task receiving user can be automatically set according to the report type. This process greatly reduces manual intervention, improves the efficiency and accuracy of task allocation, and avoids task allocation errors caused by human errors. By sending a report receiving task message containing a download link of the report receiving template to the terminal device of the task receiving user, the user can download the template anytime and anywhere for reporting, which greatly improves the flexibility and convenience of reporting. This instant notification mechanism ensures the rapid transmission of task information and reduces delays caused by information lag. Real-time monitoring of the report preparation progress of the task receiving user and displaying the progress breakdown table provide an intuitive monitoring tool for management. This transparency not only helps to identify problems and take measures in a timely manner, but also enhances the efficiency and sense of responsibility of teamwork, and further promotes the timeliness of report reporting. After receiving the target report submitted by the user, it can automatically review it according to the preset data audit rules, quickly identify and point out possible problems. This automated review process not only reduces the burden of manual review, but also greatly improves the accuracy and efficiency of the review, and effectively reduces the risk of errors caused by human negligence. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0021] Figure 1 It is a schematic diagram of the network architecture provided by the embodiment of the present application;

[0022] Figure 2 It is a flowchart of a method for collecting report data provided in an embodiment of the present application;

[0023] Figure 3 It is a schematic diagram of a progress breakdown table provided in an embodiment of the present application;

[0024] Figure 4 is a schematic diagram of a scoring table provided in an embodiment of the present application;

[0025] Figure 5 It is a structural schematic diagram of a report data collection device provided by the present application;

[0026] Figure 6 It is a structural diagram of a server provided by this application. DETAILED DESCRIPTION

[0027] In order to make the objectives, technical solutions and advantages of the present application more clear, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

[0028] It should be noted that the report data collection method provided in the present application is generally executed by a server, and accordingly, the report data collection device is generally set in the server.

[0029] Figure 1 An exemplary system architecture of a report data collection method or a report data collection device that can be applied to the present application is shown.

[0030] like Figure 1 As shown, the system architecture may include: a terminal device 101 and a server 102. The terminal device 101 and the server 102 may communicate via a network, and the network is used as a medium for providing communication links between the above-mentioned units. The network may include various types of wired communication links or wireless communication links, for example: a wired communication link includes an optical fiber, a twisted pair or a coaxial cable, etc., and a wireless communication link includes a Bluetooth communication link, a wireless fidelity (WIreless-FIdelity, Wi-Fi) communication link or a microwave communication link, etc.

[0031] It should be noted that the terminal device 101 and the server 102 can be hardware or software. When the terminal device 101 and the server 102 are hardware, they can be implemented as a distributed server cluster consisting of multiple servers, or as a single server. When the terminal device 101 and the server 102 are software, they can be implemented as multiple software or software modules (for example, to provide distributed services), or as a single software or software module, which is not specifically limited here.

[0032] Various communication client applications can be installed on the terminal device of the present application, such as: video recording applications, video playback applications, voice interaction applications, search applications, instant messaging tools, email clients, social platform software, etc.

[0033] The terminal device can be hardware or software. When the terminal device is hardware, it can be various terminal devices with a display screen, including but not limited to smart phones, tablet computers, laptops, and desktop computers. When the terminal device is software, it can be installed in the terminal devices listed above. It can be implemented as multiple software or software modules (for example: used to provide distributed services), or it can be implemented as a single software or software module, which is not specifically limited here.

[0034] When the terminal device is hardware, a display device and a camera may be installed thereon. The display device may be any device capable of realizing a display function, and the camera is used to collect video streams; for example, the display device may be a cathode ray tube display (CR), a light-emitting diode display (LED), an electronic ink screen, a liquid crystal display (LCD), a plasma display panel (PDP), etc. The user may use the display device on the terminal device to view displayed text, pictures, videos and other information.

[0035] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be used as required.

[0036] The following will be combined with the attached Figure 2 , the report data collection method provided in the embodiment of the present application is described in detail. Among them, the report data collection device in the embodiment of the present application can be Figure 1 The server shown.

[0037] See also Figure 2 , which is a flow chart of a method for collecting report data according to an embodiment of the present application. Figure 2 As shown, the method of the embodiment of the present application may include the following steps:

[0038] S201. Searching for a corresponding report receiving template in a template library according to the acquired basic information of the report receiving task.

[0039] Among them, parsing the basic information of the report receiving task: the server first receives and parses the basic information of the report receiving task from the client or database, including fields such as the report filling task code, the report filling task name, the report filling period, the data start and end date, and the report filling task description. Based on the parsed basic information of the task, the server constructs SQL query conditions or API call parameters for querying the template library. These conditions may include keyword matching of the task code and the task name, as well as possible specific periods or date ranges. Using the constructed query conditions, the server accesses an internal or external report template library (which may be a database, file system, or cloud storage service). The template library contains multiple types of report templates, each of which is associated with a specific task code, task name, or other attributes. The server searches for a report receiving template that matches the query conditions in the template library. Once a matching template is found, its content (such as an Excel template file, a PDF template, or a JSON template structure) is loaded into the memory for further processing. The found report receiving template is returned to the requester in an appropriate format (such as a file download link, direct file content, or template structure data) for use in subsequent steps.

[0040] In some embodiments of the present application, the server performs intelligent word segmentation on the input message receiving task description text, and generates basic message receiving task information according to the word segmentation result.

[0041] The received message receiving task description text is then initially cleaned, such as removing irrelevant characters (such as punctuation marks, special symbols, etc.), unifying the text format (such as converting to lowercase or unified encoding format), etc.

[0042] The preprocessed text is segmented using the NLP word segmentation algorithm. The word segmentation algorithm can be rule-based (such as using a dictionary for matching), statistical-based (such as using machine learning algorithms such as hidden Markov model HMM, conditional random field CRF), or a combination of the two. For texts in the financial field, it is necessary to introduce a proprietary dictionary in the financial field to improve the accuracy and professionalism of word segmentation. On the basis of word segmentation, the word segmentation results are tagged with parts of speech, that is, to determine whether each word is a noun, verb, adjective, etc. Named entity recognition is performed, with special attention paid to entities related to the reporting task, such as "reporting task code", "reporting task name", "data start and end dates", etc. These entities usually correspond to key fields of the basic information of the reporting task. According to the results of part-of-speech tagging and named entity recognition, key information related to the basic information of the reporting task is extracted from the text. The extracted information is stored in a structured manner to form a data structure of the basic information of the reporting task, such as a JSON object or a database record, including fields such as reporting task code, reporting task name, reporting cycle, data start and end dates, and reporting task description. Post-process the generated basic information of the receiving task, such as removing duplicate information, filling in missing default values, etc. Verify to ensure that the generated basic information of the receiving task meets the business logic and format requirements. Store the generated basic information of the receiving task in the database for use in subsequent steps (such as querying the report receiving template). The server can return the generated basic information of the receiving task to the front end or the caller for display, and the front end can manually modify the word segmentation results according to needs.

[0043] In some embodiments of the present application, the server determines the attachment type related to the report according to the report type of the report receiving template, so as to instruct the task receiving user to submit an attachment indicated by the attachment type.

[0044] Among them, the server needs to be able to identify the report type specified in the user or system request. The report type may be defined based on a variety of factors, such as business scenarios, data requirements, format requirements, etc. Each report type has its own specific purpose and use. Once the report type is identified, the server will determine the attachment type associated with the report type based on the preset rules or mapping relationships. These attachment types may include but are not limited to data files, pictures, document templates, configuration files, etc., depending on the information or resources required during the report generation or processing process. The server will then issue instructions to the task receiving user (who may be the creator, reviewer, or other relevant personnel of the report) to submit attachments that match the determined attachment type. This instruction can be made through various channels, such as email, system messages, user interface prompts, etc. The user prepares and uploads the corresponding attachments according to the server's instructions. These attachments are essential for subsequent processes such as report generation, analysis, review, or distribution. After receiving the attachments submitted by the user, the server will perform necessary verification and processing to ensure the integrity and correctness of the attachments. Subsequently, these attachments may be used in tasks such as automatic report generation, data filling, format adjustment, etc.

[0045] S202: Match the corresponding reporting subject type according to the report type of the report receiving template, and set the task receiving user for the reporting subject type.

[0046] Among them, the server extracts or parses the report type information (such as "trust report", "bank report", etc.) from the report template. According to the report type, the corresponding reporting entity type (such as securities companies, insurance companies, etc.) is found in the preset mapping relationship table or logic. This mapping relationship can be hard-coded in the server logic or stored in a table in the database. According to the reporting entity type, combined with the user roles, permission settings or specific business rules within the system, determine which users or user groups should be designated as task receiving users, which involves querying the user database and screening according to user roles, department affiliations and other information. Associate the determined task receiving user information (such as user ID, user name, email address, etc.) with the current receiving task, and prepare to send the receiving task message.

[0047] S203, sending a task receiving message to the terminal device of the task receiving user, the task receiving message including a download link address of the report receiving template, instructing the task receiving user to use the terminal device to fill in the report receiving template to generate a target report.

[0048] The server constructs a message body containing task details based on the basic information of the task and the download link address of the report template. The message body may contain key information such as task name, deadline, download link, etc. Use email, SMS, instant messaging tools (such as DingTalk, WeChat for Enterprise) or the system's internal notification mechanism to send task messages to the terminal device of the task recipient. The choice of sending method depends on user configuration and the system's integration capabilities. Record the log of message sending, including sending time, receiving user information, message content, etc., for subsequent tracking and auditing.

[0049] S204, the monitoring task receives the report preparation progress of the user, and displays a progress list according to the report preparation progress.

[0050] The server periodically checks or receives progress update requests from the user terminal to track whether the user has started filling in the form, the progress of the filling in, etc. The user's filling in progress information (such as start time, latest update time, proportion of completed parts, etc.) is recorded in the database. Based on the recorded progress information, the server can dynamically generate a progress breakdown table and display it to the task manager or relevant users for viewing.

[0051] In some embodiments of the present application, see Figure 3 The schematic diagram of the progress breakdown table shown in the figure can be counted according to the report or according to the unit. It includes the report name, number of units, number in preparation, number under review, number passed review, and completion status.

[0052] Among them, report name: an identifier used to distinguish different progress reports, corresponding to different projects, departments or time periods. Through the report name, users can quickly locate the progress information they need to view. Number of units: usually refers to the number of units involved in the report or project work, including different departments, teams or sub-projects, and is an important indicator for evaluating the scale and complexity of the project. Number in preparation: partially shows the number of reports or tasks currently in the preparation stage, which is used to reflect the amount of tasks that have not yet completed the preliminary preparation work, helping managers understand the current workload and potential bottlenecks. Number in review: refers to the number of reports or tasks that have been prepared and submitted for review, but have not yet passed the review. This data point is crucial for evaluating the efficiency of the review process and possible review delays. Number of approved reviews: refers to the number of reports or tasks that have passed the review and can be considered officially completed or entered the next stage. This data is important for measuring work results and progress. Completion status: can be expressed by percentage, color coding or other methods. All the above quantitative information is combined to give an intuitive overview of the completion progress of the entire report or project. The completion status not only reflects the physical completion of the work, but may also involve other aspects of evaluation such as quality and satisfaction.

[0053] S205, receiving the target report returned by the user through the terminal device, and auditing the target report according to the preset data audit rules, and displaying the target report and the audit results.

[0054] Among them, the server receives the target report file (such as Excel, CSV, etc.) from the user terminal and saves it to a specified location (such as a file server, database or cloud storage). The received target report is parsed, the data content is extracted, and preparation is made for subsequent data processing and analysis. The parsed data is audited according to the preset data audit rules (such as data integrity check, logical consistency check, range check, etc.). These rules may be stored in the database or may be part of the server logic. Problems and errors found during the audit process are recorded and an audit result report is generated. The audit results may include an error list, modification suggestions, etc. The audit result report is returned to the user, or the user is informed of the audit results through the system notification mechanism. Users can modify and improve the report based on the feedback.

[0055] In some embodiments of the present application, it also includes:

[0056] If the time interval between the current date and the preset reporting deadline is less than the day threshold, a corresponding push method is determined according to the job role of the task receiving user, and a reminder message is sent to the task receiving user using the determined push method.

[0057] Among them, the push mode includes: one or more of system message, email message, short message, and APP message. The server periodically (such as daily) calculates the time interval between the current date and the preset reporting deadline. If the time interval is less than the preset number of days threshold, the reminder process is triggered; otherwise, regular monitoring continues. The server queries the user information database according to the identity of the task receiving user to determine the user's job role (such as power distribution dispatching post, PC user, etc.). For power distribution dispatching post users, since they mainly work outdoors and prefer mobile applications, the server intelligently recommends SMS or APP push as the preferred reminder mode. For PC user roles, the server uses system message and email reminder mode by default. For particularly important or urgent information, the server will also add additional APP and SMS reminders to ensure timely communication of information. According to the user role and preference, the server constructs personalized reminder message content and selects the appropriate push method to send it to the user. The message content should clearly indicate the task name, deadline, current progress, and consequences of failure to complete the task, so as to attract the user's attention. The server supports setting timed tasks and automatically sends reminder messages to users who have not completed the task at a specific time (such as a fixed time every day, N days before the reporting deadline, etc.). This helps to remind users in advance and avoid task expiration.

[0058] Administrators or system operators can manually trigger the reminder process when needed and send reminder messages to specified users or user groups. This is suitable for handling special situations or urgent tasks. In addition to the time interval being less than the day threshold, the server can also automatically initiate reminder messages based on other conditions, such as the user has not completed the report before the deadline, the report deadline is approaching but the progress is slow, etc. For these situations, the server will intelligently judge and take corresponding reminder measures to ensure that the task can be completed on time. The server records key information such as the sending time of each reminder message, the receiving user, the push method used, the message content, etc., for subsequent tracking and auditing. At the same time, the server should also track the user's response, such as whether the message has been viewed, whether the report has been started, etc., so as to adjust the reminder strategy in time.

[0059] Based on user feedback and system monitoring data, the server can continuously optimize the sending strategy of reminder messages to improve reminder effects and user satisfaction. For example, if it is found that the response rate of a certain push method is low, the server can try to change to another method or increase the push frequency; if it is found that users are not interested in certain types of messages, the server can adjust the message content or format, etc.

[0060] Through the implementation of the above process, the server can intelligently select the push method according to the work characteristics and preferences of different user roles, and combine the functions of scheduled reminders and manual reminders to initiate effective reminder messages to users who have not completed the report, so as to ensure the timely completion of the report collection task.

[0061] In some embodiments of the present application, the target report after approval is analyzed according to multiple dimensions to generate statistical charts.

[0062] Among them, the server first collects all the target report data that have been reviewed and approved. The collected data is cleaned, verified and sorted to ensure the accuracy and completeness of the data. According to business needs and analysis purposes, the server defines multiple analysis dimensions. These dimensions may include time (such as year, month, day), region (such as province, city), department (such as sales department, marketing department), product type, sales channel, etc. Each dimension can be used as an independent analysis angle, or it can be used in combination for more in-depth cross-analysis. The server aggregates and calculates the data according to the defined analysis dimensions. For example, monthly sales are counted by the time dimension, and sales performance of each province is counted by the regional dimension. More complex calculations can also be performed, such as calculating averages, growth rates, proportions, etc., to reveal the trends and laws behind the data. Based on the aggregated and calculated data, the server selects the appropriate chart type (such as bar charts, line charts, pie charts, scatter charts, etc.) to display the analysis results. The chart should present the data intuitively and clearly, so that readers can quickly understand the meaning and trend of the data. The chart can also contain auxiliary information such as titles, legends, and data labels to enhance readability.

[0063] After generating preliminary statistical charts, the server will further optimize and adjust them. For example, the size, color, font, etc. of the chart will be adjusted to improve the aesthetics and readability of the chart. If the data in the chart is found to be abnormal or not in line with expectations, the server will recheck the data source and analysis logic to ensure the accuracy of the chart. The optimized and adjusted statistical charts can be saved in a variety of formats (such as PNG, PDF, SVG, etc.) and can be shared with relevant personnel through email, internal systems or data dashboards. Relevant personnel can discuss, make decisions or formulate the next action plan based on the data and analysis results in the statistical charts. The server will regularly update the data of the target report, and re-analyze and generate charts based on the new data. At the same time, the server will also monitor the changing trends and abnormalities of the data to detect and solve problems in a timely manner.

[0064] Through the implementation of the above process, the server can conduct in-depth analysis of the approved target reports based on multiple dimensions and generate intuitive and clear statistical charts. These charts not only help to understand the meaning and trend of the data, but also provide strong support for the company's decision-making.

[0065] In some embodiments of the present application, each reporting entity is scored and a scoring table is generated. Figure 4The schematic diagram of the scoring sheet shown includes the reporting entity, reporting completion status, completion time, number of rollbacks, reporting timeliness score, completeness score, reporting quality score, evaluator, and indicator achievement score.

[0066] Among them, the server first collects various data related to the reporting subject, including but not limited to the completion status, completion time, number of rollbacks, and reporting content. These data come from multiple channels such as the reporting system, audit records, and timestamps to ensure the comprehensiveness and accuracy of the data. According to business needs and management requirements, the server defines a set of scoring criteria. This set of criteria usually includes multiple dimensions, such as timeliness, completeness, quality, and achievement of indicators. Specific scoring indicators and weights are set under each dimension to quantitatively evaluate the reporting subject. The server scores each reporting subject based on the collected data and the defined scoring criteria. The timeliness score is calculated based on the difference between the completion time and the deadline. The earlier the completion, the higher the score. The completeness score is based on whether the report content is complete and whether it complies with the specifications. The reporting quality score takes into account factors such as the accuracy, clarity, and logic of the report. The indicator achievement score is given based on the performance of the reporting subject on key business indicators. If there is a rollback, the server will also adjust the score accordingly based on the number of rollbacks and reasons.

[0067] After completing the scoring of all reporting entities, the server organizes the scoring information into a scoring table. The scoring table includes basic information such as the name of the reporting entity, the completion of the reporting, the completion time, the number of rollbacks, and specific scoring items such as the timeliness score of the reporting, the completeness score, the quality score of the reporting, and the score of the indicator achievement. At the same time, the scoring table will also indicate the scorer (such as automatic scoring by the system or designated reviewer) and the scoring time for subsequent traceability and review. If the scoring process involves manual review or confirmation, the server will submit the scoring table to the relevant personnel for review. The reviewer can adjust the score according to the actual situation or submit the final scoring result after confirmation. The reviewed and confirmed scoring table can be shared with relevant personnel or departments through internal systems, emails, etc. The scoring table can be used as an objective basis for the work performance of the reporting entity, and can be used in performance appraisal, reward and punishment decisions, training needs identification and other aspects.

[0068] The server will regularly update the data in the scoring table to reflect the latest performance of the reporting entity. At the same time, the scoring standards and processes will be evaluated and optimized to ensure the fairness, accuracy and effectiveness of the scoring results.

[0069] The embodiments of the present application have the following beneficial effects when performing report compilation tasks:

[0070] Based on the customized reporting task system for reporting application scenarios, a comprehensive and systematic reporting framework is built by accurately constructing the reporting task framework. Under this framework, each reporting entity is efficiently given clear task instructions, prompting them to execute the detailed filling of reports, rigorous submission and review, and timely data submission process, thereby ensuring the accuracy and effective confirmation of the report data.

[0071] Throughout the entire process, management entities at all levels can gain real-time insight into the progress of the task of receiving reports, implement early warning mechanisms for potential delay risks, and flexibly use reminders and message reminders to effectively avoid the possibility of task delays. Once the task of receiving reports is successfully completed, the system will quickly move to the data analysis and application stage to conduct in-depth mining and extensive use of the valuable data received.

[0072] This application not only achieves the precise connection and efficient delivery of report collection tasks and reports, but also supports a full-chain, integrated report collection management system covering task initiation, release, execution (including report filling and review), progress monitoring, urging management, data review and even analytical application. This move has greatly improved the standardization and automation level of report collection work, and laid a solid foundation for the precise management and efficient use of data.

[0073] The following are device embodiments of the present application, which can be used to execute the method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.

[0074] See also Figure 5 , which shows a schematic diagram of the structure of a report data collection device provided by an exemplary embodiment of the present application, hereinafter referred to as device 5. The device 5 can be implemented as all or part of the server through software, hardware or a combination of both. The device 5 includes: a query unit 501, a matching unit 502, a sending unit 503, a monitoring unit 504, and a receiving unit 505.

[0075] The query unit 501 is used to query the corresponding report receiving template in the template library according to the acquired basic information of the report receiving task;

[0076] A matching unit 502, configured to match a corresponding reporting subject type according to the report type of the report receiving template, and to set a task receiving user for the reporting subject type;

[0077] The sending unit 503 is used to send a task receiving message to the terminal device of the task receiving user, wherein the task receiving message includes a download link address of the report receiving template, and instructs the task receiving user to use the terminal device to fill in the report receiving template to generate a target report;

[0078] A monitoring unit 504, used to monitor the report preparation progress of the task receiving user, and display a progress list according to the report preparation progress;

[0079] The receiving unit 505 is used to receive the target report returned by the task receiving user through the terminal device, and to review the target report according to the preset data audit rules, and to display the target report and the audit result.

[0080] In one or more possible embodiments, searching for a corresponding report receiving template in a template library according to the acquired basic information of the report receiving task includes:

[0081] According to the intelligent word segmentation of the inputted report receiving task description text, basic information of the report receiving task is generated according to the word segmentation result; the basic information of the report receiving task includes: report filling task code, report filling task name, report filling cycle, data start and end date, and report filling task description;

[0082] According to the basic information of the report receiving task, the corresponding report receiving template is searched in the template library.

[0083] In one or more possible embodiments, it further includes:

[0084] The indicating unit is used to determine the attachment type related to the report receiving according to the report type of the report receiving template, so as to indicate the task receiving user to submit the attachment indicated by the attachment type.

[0085] In one or more possible embodiments, the progress breakdown is counted based on reports or units, and the progress breakdown includes: report name, number of units, number in preparation, number under review, number passed review, and completion status.

[0086] In one or more possible embodiments, it further includes:

[0087] The prompting unit is used to determine the corresponding push method according to the job role of the task receiving user when the time interval between the current date and the preset reporting deadline is less than the day threshold, and send a reminder message to the task receiving user using the determined push method.

[0088] In one or more possible embodiments, it further includes:

[0089] The scoring unit is used to score each reporting entity type and generate a scoring table, which includes the reporting entity, reporting completion status, completion time, number of rollbacks, reporting timeliness score, completeness score, reporting quality score, evaluator, and indicator achievement score.

[0090] In one or more possible embodiments, the data audit rules include: data integrity check rules, logical consistency check rules, and range check rules.

[0091] It should be noted that, when the device 5 provided in the above embodiment executes the method for collecting report data, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the above functions. In addition, the report data collection device provided in the above embodiment and the report data collection method embodiment belong to the same concept, and the implementation process thereof is detailed in the method embodiment, which will not be repeated here.

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

[0093] The present application also provides a computer storage medium, which can store multiple instructions, and the instructions are suitable for being loaded and executed by a processor as described above. Figure 2 The method steps of the embodiment shown in the figure can be found in the specific implementation process. Figure 2 The specific description of the illustrated embodiment will not be repeated here.

[0094] The present application also provides a computer program product, which stores at least one instruction, and the at least one instruction is loaded and executed by the processor to implement the report data collection method described in the above embodiments.

[0095] See also Figure 6 , which is a schematic diagram of the structure of a server provided in the embodiment of the present application. Figure 6 As shown, the server 600 may include: at least one processor 601 , at least one network interface 604 , a user interface 603 , a memory 605 , and at least one communication bus 602 .

[0096] The communication bus 602 is used to realize the connection and communication between these components.

[0097] The user interface 603 may include a display screen (Display) and a camera (Camera), and the optional user interface 603 may also include a standard wired interface and a wireless interface.

[0098] The network interface 604 may optionally include a standard wired interface or a wireless interface (such as a WI-FI interface).

[0099] Among them, the processor 601 may include one or more processing cores. The processor 601 uses various interfaces and lines to connect various parts within the entire server 600, and executes various functions and processes data of the server 600 by running or executing instructions, programs, code sets or instruction sets stored in the memory 605, and calling data stored in the memory 605. Optionally, the processor 601 can be implemented in at least one hardware form of digital signal processing (Digital Signal Processing, DSP), field programmable gate array (Field-Programmable Gate Array, FPGA), and programmable logic array (Programmable Logic Array, PLA). The processor 601 can integrate one or a combination of a central processing unit (Central Processing Unit, CPU), a graphics processing unit (Graphics Processing Unit, GPU) and a modem. Among them, the CPU mainly processes the operating system, user interface and application programs; the GPU is responsible for rendering and drawing the content to be displayed on the display screen; the modem is used to process wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 601, and it can be implemented separately through a chip.

[0100] Among them, the memory 605 may include a random access memory (Random Access Memory, RAM) and may also include a read-only memory (Read-Only Memory). Optionally, the memory 605 includes a non-transitory computer-readable storage medium. The memory 605 can be used to store instructions, programs, codes, code sets or instruction sets. The memory 605 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned method embodiments, etc.; the data storage area may store data involved in the above-mentioned method embodiments, etc. The memory 605 may optionally be at least one storage device located away from the aforementioned processor 601. As Figure 6 As shown, the memory 605 as a computer storage medium may include an operating system, a network communication module, a user interface module, and an application program.

[0101] exist Figure 6In the server 600 shown in FIG. 1 , the user interface 603 is mainly used to provide an input interface for the user and obtain the data input by the user; and the processor 601 can be used to call the application stored in the memory 605 and specifically execute the following steps: Figure 2 The specific process can be referred to Figure 2 As shown, no further description is given here.

[0102] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing related hardware through a computer program, and the program can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. The storage medium can be a disk, an optical disk, a read-only storage memory, or a random access memory, etc.

[0103] The above disclosure is only the preferred embodiment of the present application, which certainly cannot be used to limit the scope of rights of the present application. Therefore, equivalent changes made according to the claims of the present application are still within the scope covered by the present application.

Claims

1. A method for collecting report data, characterized in that: include: According to the basic information of the report receiving task obtained, the corresponding report receiving template is searched in the template library; Matching a corresponding reporting subject type according to the report type of the report receiving template, and setting a task receiving user for the reporting subject type; Sending a task receiving message to a terminal device of a task receiving user, wherein the task receiving message includes a download link address of the report receiving template, and instructing the task receiving user to use the terminal device to fill in the report receiving template and generate a target report; Monitoring the report preparation progress of the task receiving user, and displaying a progress breakdown table according to the report preparation progress; The target report returned by the task receiving user through the terminal device is received, and the target report is audited according to the preset data audit rules, and the target report and the audit result are displayed.

2. The method according to claim 1, characterized in that The step of searching the template library for the corresponding report receiving template according to the acquired basic information of the report receiving task includes: According to the intelligent word segmentation of the inputted report receiving task description text, basic information of the report receiving task is generated according to the word segmentation result; the basic information of the report receiving task includes: report filling task code, report filling task name, report filling cycle, data start and end date, and report filling task description; According to the basic information of the report receiving task, the corresponding report receiving template is searched in the template library.

3. The method according to claim 1 or 2, characterized in that: Also includes: The attachment type related to the report receipt is determined according to the report type of the report receipt template, so as to indicate the task receiving user to submit the attachment indicated by the attachment type.

4. The method according to claim 3, characterized in that The progress breakdown is counted based on the report or based on the unit, and the progress breakdown includes: report name, number of units, number in preparation, number under review, number passed review, and completion status.

5. The method according to claim 1, 2 or 4, characterized in that: Also includes: When the time interval between the current date and the preset reporting deadline is less than the day threshold, a corresponding push method is determined according to the job role of the task receiving user, and a reminder message is sent to the task receiving user using the determined push method.

6. The method according to claim 5, characterized in that Also includes: Each reporting entity type is scored and a score sheet is generated, which includes the reporting entity, reporting completion status, completion time, number of rollbacks, reporting timeliness score, completeness score, reporting quality score, rater, and indicator achievement score.

7. The method according to claim 1 or 2 or 4 or 5, characterized in that: The data audit rules include: data integrity check rules, logical consistency check rules, and range check rules.

8. A device for collecting report data, characterized in that: include: A query unit, used to query the corresponding report receiving template in the template library according to the acquired basic information of the report receiving task; A matching unit, used for matching a corresponding reporting subject type according to the report type of the report receiving template, and setting a task receiving user for the reporting subject type; A sending unit, used to send a task receiving message to a terminal device of a task receiving user, wherein the task receiving message includes a download link address of the report receiving template, and instructs the task receiving user to use the terminal device to fill in the report receiving template and generate a target report; A monitoring unit, used to monitor the report preparation progress of the task receiving user, and display a progress list according to the report preparation progress; The receiving unit is used to receive the target report returned by the task receiving user through the terminal device, and to review the target report according to the preset data audit rules, and to display the target report and the audit result.

9. A computer storage medium, characterized in that The computer storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor and executing the method steps according to any one of claims 1 to 7.

10. A server, characterized in that: include: A processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the method steps as claimed in any one of claims 1 to 7.

Images