Intelligent combined statement and financial statement linkage method and system and medium

Abstract

The invention discloses an intelligent combined report and financial report linkage method and system and a medium, mainly relates to the technical field of report linkage, and is used for solving the problems of complicated operation, inaccurate combined report data and the like caused by articulation of financial reports and combined report data in the prior art. Comprising the following steps: storing financial statements into a first database and storing a merged statement data source into a second database by adopting double-instance deployment; a data monitor is built in the first database so as to transmit an extraction instruction to an ETL tool when the data monitor monitors that newly-added reported financial data appears, and the newly-added reported financial data is extracted to a second database through the ETL tool; when the second database receives newly-added reported financial data, triggering a financial data verification program; and when a financial data verification program built-in rule is satisfied, adding newly-added reported financial data as a merged report data source to a second database.

Description

Technical Field

[0001] This application relates to the technical field of report processing, and particularly to a linkage method, system and medium for intelligent consolidated statements and financial statements. Background Art

[0002] Consolidated statements are the basic way for a group company to disclose data externally and comprehensively reflect the true operating conditions and financial status of the group enterprise. For listed companies, the securities regulatory authorities also require that complete, accurate and detailed consolidated statements must be provided regularly and disclosed externally. However, because the preparation of consolidated statements involves a large number of internal transaction operations and complex equity relationships, it is one of the three major problems recognized in the international accounting community.

[0003] In recent years, with the development of financial informatization and internationalization, the preparation of consolidated statements with the help of a financial information system has been realized. However, due to the business complexity of consolidated statements and the limitations of the information system, difficulties such as complex calculations caused by the data reconciliation between financial statements and consolidated statements and inaccurate data of the issued consolidated statements may still occur during the preparation of consolidated statements.

[0004] Nowadays, it is particularly important to correctly collect individual statement data from each subsidiary and be able to verify and automatically synchronize data during the preparation of consolidated statements. At this time, a linkage method, system and medium for intelligent consolidated statements and financial statements are needed to solve the above technical problems. Summary of the Invention

[0005] In view of the above deficiencies of the prior art, this application provides a linkage method, system and medium for intelligent consolidated statements and financial statements to solve the problems in the prior art, such as complex calculations caused by the data reconciliation between financial statements and consolidated statements and inaccurate data of the issued consolidated statements.

[0006] In a first aspect, this application provides a linkage method for intelligent consolidated statements and financial statements. The method includes: Adopt dual-instance deployment, store financial statements in a first database, and store consolidated statement data sources in a second database; build a data listener in the first database to transmit an extraction instruction to an ETL tool when the data listener detects newly reported financial data, and extract the newly reported financial data to the second database through the ETL tool; when the second database receives the newly reported financial data, trigger a financial data verification program; when the built-in rules of the financial data verification program are not met, return the newly reported financial data and send a reminder message to a preset maintenance terminal; when the built-in rules of the financial data verification program are met, add the newly reported financial data as a consolidated statement data source to the second database.

[0007] In an implementation manner of the present application, after adopting dual-instance deployment and storing the financial statements in the first database and the data source of the consolidated statements in the second database, the method further includes: Perform an operation of adding financial statements to the first database through a preset interface; When an upload button preset in the preset interface is triggered, send a new addition instruction to the data listener; Furthermore, activate the data listener so that the data listener records the newly added financial statements currently.

[0008] In an implementation manner of the present application, performing an operation of adding financial statements to the first database through a preset interface specifically includes: Select a report filling task through a preset financial statement upload interface; Determine the applicable consolidation scope of the financial statements to be filled in this time and the type of the statements through selecting the report filling task; the types of the statements at least include: daily report, weekly report, ten-day report, monthly report, quarterly report, semi-annual report, annual report; Determine the time point to be filled in, the statement data of the specific unit to be filled in this time, and the specific statements to be filled in this time; among them, the specific statements at least include: balance sheet, income statement, cash flow statement.

[0009] In an implementation manner of the present application, when the second database receives newly reported financial data, trigger a financial data verification program, specifically including: When the second database receives newly reported financial data, trigger a financial data verification program to verify whether the financial data contains preset necessary fields, whether each field in the financial data conforms to the preset logical relationship, and compare with the existing data to verify whether there is a change greater than the preset difference value.

[0010] In an implementation manner of the present application, after adding the newly reported financial data as the data source of the consolidated statements to the second database, the method further includes: At intervals of a preset detection time point, compare in real time whether there is a difference between the newly reported financial data and the newly added data source of the consolidated statements between the previous preset detection time point and the current preset detection time point; When there is a difference, replace the newly added data source of the consolidated statements with the newly reported financial data.

[0011] In a second aspect, the present application provides an intelligent linkage system for consolidated statements and financial statements, and the system includes: A storage module, which is used for dual-instance deployment to store financial statements in a first database and store the data source of consolidated statements in a second database; An extraction module, which is used to build a data listener in the first database to transmit an extraction instruction to an ETL tool when the data listener detects newly reported financial data, and extract the newly reported financial data to the second database through the ETL tool; An addition module, which is used to trigger a financial data verification program when the second database receives the newly reported financial data; when the built-in rules of the financial data verification program are not met, the newly reported financial data is returned, and a reminder message is sent to a preset maintenance terminal; when the built-in rules of the financial data verification program are met, the newly reported financial data is added to the second database as the data source of consolidated statements.

[0012] In an implementation manner of the present application, the extraction module includes a recording unit, which is used to perform an operation of adding financial statements to the first database through a preset interface; When an upload button preset in the preset interface is triggered, a new instruction is sent to the data listener; Furthermore, the data listener is activated so that the data listener records the currently added financial statements.

[0013] In an implementation manner of the present application, the system includes an upload module, which is used to select a report filling task through a preset financial statement upload interface; The applicable consolidation scope of the financial statements to be filled in this time is determined by selecting the report filling task, and the type of the report is determined; the types of the reports at least include: daily report, weekly report, ten-day report, monthly report, quarterly report, semi-annual report, annual report; The time point to be filled, the report data of the specific unit to be filled this time, and the specific report to be filled this time are determined; among them, the specific reports at least include: balance sheet, income statement, cash flow statement.

[0014] In an implementation manner of the present application, the system further includes a verification module, which is used to trigger a financial data verification program when the second database receives the newly reported financial data, verify whether the financial data contains preset necessary fields, whether each field in the financial data conforms to the preset logical relationship, compare with the existing data, and verify whether there is a change greater than the preset difference value.

[0015] In a third aspect, the present application provides a non-volatile computer storage medium, on which computer instructions are stored, and when the computer instructions are executed, they implement an intelligent consolidation statement and financial statement linkage method as described in any one of the above.

[0016] Those skilled in the art can understand that the present application has at least the following beneficial effects: Through an automated data verification program, ensure the accuracy and compliance of the data entering the consolidated financial statements. The dual-instance deployment and the use of ETL tools enable automatic extraction and synchronization of data, reduce manual operations, and improve work efficiency. When the data does not meet the verification rules, the system can automatically reject it and send a reminder, facilitating timely handling by maintenance personnel. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] To more clearly illustrate the technical solutions of the present invention, the drawings required for description will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other drawings can be obtained based on these drawings.

[0018] Figure 1 is a flowchart of a linkage method between an intelligent consolidated financial statement and a financial statement provided by an embodiment of the present application.

[0019] Figure 2 is a schematic internal structure diagram of a linkage system between an intelligent consolidated financial statement and a financial statement provided by an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0020] Those skilled in the art should understand that the embodiments described below are only preferred embodiments of the present disclosure, and do not mean that the present disclosure can only be implemented through these preferred embodiments. The preferred embodiments are only used to explain the technical principles of the present disclosure, and are not used to limit the protection scope of the present disclosure. Based on the preferred embodiments provided by the present disclosure, all other embodiments obtained by those of ordinary skill in the art without creative efforts should still fall within the protection scope of the present disclosure.

[0021] It should also be noted that the term "including", "comprising" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed, or further includes elements inherent to such process, method, commodity or device. Without further limitations, the element defined by the statement "including one..." does not exclude the existence of another identical element in the process, method, commodity or device including the element.

[0022] The technical solutions proposed by the embodiments of the present application will be described in detail below with reference to the drawings.

[0023] The embodiment provides a linkage method between an intelligent consolidated financial statement and a financial statement. As Figure 1 shown, the method provided by the embodiment of the present application mainly includes the following steps: Step 110: Adopt dual-instance deployment to store the financial statements in the first database and the data sources for consolidated statements in the second database.

[0024] It should be noted that in order to store the data sources of financial statements and consolidated statements in different databases respectively, so as to achieve data isolation and management convenience.

[0025] ‌Operation‌: ‌The first database‌: Used to store the individual financial statement data of each subsidiary. These data may be regular (such as monthly, quarterly, annual) financial statements, which contain information such as the company's financial position, operating results, and cash flows. ‌The second database‌: As the data source library for consolidated statements, it stores the individual statement data after verification and collation, as well as other data required for preparing consolidated statements (such as equity relationships, internal transaction offsets, etc.).

[0026] In some embodiments, after adopting dual-instance deployment to store the financial statements in the first database and the data sources for consolidated statements in the second database, the method further includes: Perform an operation to add financial statements to the first database through a preset interface; when the upload button preset in the preset interface is triggered, send a new instruction to the data listener; and then activate the data listener so that the data listener records the currently added financial statements.

[0027] It should be added that the preset interface is a user-friendly interface that allows users (such as financial personnel) to conveniently add, view, and manage financial statements. The interface may include elements such as tables, buttons, and drop-down menus for users to perform various operations. Users can fill in or select relevant information about the new financial statements (such as statement type, statement period, subsidiary name, etc.) on the preset interface. Users click the "Upload" button or a button with a similar function on the interface to trigger the upload button. When the upload button is triggered, the interface sends a new instruction to the background system, indicating that there is a new financial statement to be added. After receiving the new instruction, the background system activates the data listener in the first database. The data listener starts to monitor the new data operations in the first database and is ready to record the newly added financial statement data. The data listener records the new financial statement data added by the user to the first database through the preset interface. These data may include the detailed content of the statement, timestamp, adder information, etc.

[0028] Example: Suppose a company has three subsidiaries (A, B, C), and each subsidiary needs to submit monthly financial statements to the parent company regularly. The parent company adopts the above dual-instance deployment strategy to manage these statement data.

[0029] First database (DB1): Stores the monthly financial statement data of three subsidiaries A, B, and C. Second database (DB2): Serves as the data source library for consolidated statements and is initially empty.

[0030] The financial staff logs in to the preset financial management interface. Select the "Add Financial Statement" function, fill in the information of a certain monthly financial statement of Subsidiary A, and click the "Upload" button. The interface sends a new addition instruction to the background system and activates the data listener in DB1. The data listener records the newly added monthly financial statement data of Subsidiary A into DB1.

[0031] Similarly, the financial staff can continue to add the monthly financial statement data of Subsidiaries B and C to DB1 through the preset interface. When it is necessary to prepare consolidated statements, the system can extract the verified data from DB1 to DB2 and perform consolidation processing. In this way, the company can efficiently manage the financial statement data of each subsidiary and ensure the accuracy and reliability of the consolidated statement preparation process.

[0032] In addition, users can perform the operation of adding financial statements to the first database through the preset interface. The specific operations are as follows: Through the preset financial statement upload interface, select the report filling task; determine the applicable consolidation scope of the financial statement to be filled in this time by selecting the report filling task, and determine the type of the report; the types of the report include at least: daily report, weekly report, ten-day report, monthly report, quarterly report, semi-annual report, annual report; determine the time point to be filled in, the report data of the specific unit to be filled in this time, and determine the specific report to be filled in this time; among them, the specific reports include at least: balance sheet, income statement, cash flow statement.

[0033] Step 120: Install a data listener in the first database to transmit an extraction instruction to the ETL tool when the data listener detects newly reported financial data, and extract the newly reported financial data to the second database through the ETL tool.

[0034] It should be noted that the process of setting up the data listener can be as follows: A data listener (Listener) is built into DB1. This listener can be a software component or a service that continuously monitors changes in specific tables or data sets in DB1. The listener is configured to listen for INSERT operations on the "financial data" table (or related data sets). Whenever a new record is inserted into this table, the listener is triggered. When the listener detects the reporting of new data (i.e., a new record is inserted into the "financial data" table), it automatically generates an extraction instruction. This extraction instruction contains the identification information of the new data (such as record ID, reporting time, etc.), as well as other parameters required to extract this data. The listener sends this extraction instruction to the ETL (Extract, Transform, Load) tool through an internal communication mechanism (such as message queue, REST API call, etc.). After receiving the extraction instruction, the ETL tool locates the new data in DB1 according to the information in the instruction. The ETL tool performs the data extraction operation and reads the new data out of DB1. During the extraction process, the ETL tool may perform some basic data transformation or cleaning to ensure that the format and quality of the data meet the requirements of DB2. After the extraction is completed, the ETL tool loads the new data into DB2 for subsequent data processing and analysis.

[0035] For further example, Suppose that subsidiary A reported its financial data for January 2025 to DB1 at 10:00 am on February 18, 2025. The following is the specific application of step 120 in this scenario: Data listener: The listener detects that a new record has been inserted into the "financial data" table in DB1, and this record contains the financial data of subsidiary A for January 2025. Instruction transmission: The listener generates an extraction instruction that contains information such as the ID and reporting time of the new record, and sends this instruction to the ETL tool through the message queue. Data extraction: After receiving the instruction, the ETL tool locates the new record in DB1 and extracts it. During the extraction process, the ETL tool performs format conversion and cleaning on the data to ensure its consistency with other data in DB2. Finally, the ETL tool loads the new data into DB2 for subsequent preparation of consolidated financial statements. Through this automated process, the enterprise can ensure that the consolidated financial statement data in DB2 is always up-to-date and reduces the possibility of manual intervention and errors.

[0036] Step 130: When the second database receives newly reported financial data, trigger the financial data verification program; when the built-in rules of the financial data verification program are not met, return the newly reported financial data and send a reminder message to the preset maintenance terminal; when the built-in rules of the financial data verification program are met, add the newly reported financial data as the data source for the consolidated statements to the second database.

[0037] In some embodiments, when the second database receives newly reported financial data, triggering the financial data verification program specifically includes: When the second database receives newly reported financial data, trigger the financial data verification program, verify whether the financial data contains preset necessary fields, whether each field in the financial data conforms to the preset logical relationship, compare with the existing data, and verify whether there is a change greater than the preset difference value.

[0038] Illustrate with an example: Suppose a company reported its financial data for January 2025 to the second database on February 18, 2025. According to Step 130, when these data are received, the financial data verification program will be triggered.

[0039] Data integrity verification: The verification program checks whether the reported financial data contains all necessary fields, such as date, subject, amount, etc. If any necessary field is found missing, the program will automatically return the data and send a reminder message to the preset maintenance terminal, indicating the missing field.

[0040] Data logical relationship verification: The verification program further checks whether the logical relationships in the financial data hold. For example, it may check whether the difference between income and expenditure matches the net profit. If the logical relationship is found not to hold, the program will also return the data with an error explanation.

[0041] Data abnormal change detection: Finally, the verification program compares the reported financial data with the existing historical data to detect whether there are abnormal changes. If a change in a certain data is detected to exceed the preset difference value range, the program will trigger a warning and return the data for further verification. In this way, the company can promptly discover and correct errors or abnormalities in the data, ensuring the accuracy and reliability of the consolidated statements.

[0042] After adding the newly reported financial data as the data source for the consolidated statements to the second database, the method further includes: At intervals of a preset detection time point, compare in real time whether there is a difference between the newly reported financial data and the newly added data source for the consolidated statements between the previous preset detection time point and the current preset detection time point; When there are differences, replace the newly added consolidated statement data source with the newly reported financial data.

[0043] In addition, this application Figure 2 is a linkage system between an intelligent consolidated statement and a financial statement provided by an embodiment of this application. As Figure 2 shown, the system provided by the embodiment of this application mainly includes: A storage module 210, which is used for dual-instance deployment to store financial statements in a first database and store consolidated statement data sources in a second database.

[0044] An extraction module 220 is used to build a data listener in the first database. When the data listener detects newly reported financial data, it transmits an extraction instruction to an ETL tool, and the ETL tool extracts the newly reported financial data to the second database.

[0045] The extraction module 220 includes a recording unit, which is used to operate on the first database to add financial statements through a preset interface; when the upload button preset in the preset interface is triggered, it sends a new instruction to the data listener; and then activates the data listener so that the data listener records the currently newly added financial statements.

[0046] The system includes an upload module, which is used to select a report filling task through a preset financial statement upload interface; determine the applicable consolidation scope of the financial statement to be filled this time and determine the type of the report; the types of the report at least include: daily report, weekly report, ten-day report, monthly report, quarterly report, semi-annual report, annual report; determine the time point to be filled, the report data of the specific unit to be filled this time, and determine the specific report to be filled this time; among them, the specific reports at least include: balance sheet, income statement, cash flow statement.

[0047] An addition module 230 is used to trigger a financial data verification program when the second database receives newly reported financial data; when the built-in rules of the financial data verification program are not met, return the newly reported financial data and send a reminder message to a preset maintenance terminal; when the built-in rules of the financial data verification program are met, add the newly reported financial data as a consolidated statement data source to the second database.

[0048] The system further includes a verification module, which is used to trigger a financial data verification program when the second database receives newly reported financial data, verify whether the financial data contains preset necessary fields, whether each field in the financial data conforms to the preset logical relationship, compare with the existing data, and verify whether there is a change greater than the preset difference value.

[0049] In addition, an embodiment of the present application further provides a non-volatile computer storage medium, on which executable instructions are stored. When the executable instructions are executed, the linkage method of an intelligent consolidated statement and a financial statement as described above is implemented.

[0050] So far, the technical solutions of the present disclosure have been described in combination with multiple embodiments above. However, those skilled in the art can easily understand that the protection scope of the present disclosure is not limited to these specific embodiments. Without departing from the technical principle of the present disclosure, those skilled in the art can split and combine the technical solutions in the above embodiments, and can also make equivalent changes or replacements to the relevant technical features. Any changes, equivalent replacements, improvements, etc. made within the technical concept and / or technical principle of the present disclosure will fall within the protection scope of the present disclosure.

Claims

1. A method for linking intelligent consolidated statements with financial statements, characterized in that: The method comprises: Use dual-instance deployment to store financial statements in the first database and consolidate report data sources in the second database; A data listener is built into the first database, so that when the data listener detects the presence of newly reported financial data, an extraction instruction is transmitted to the ETL tool, and the newly reported financial data is extracted to the second database through the ETL tool; When the second database receives newly reported financial data, the financial data verification program is triggered; when the built-in rules of the financial data verification program are not met, the newly reported financial data will be returned and a reminder message will be sent to the preset maintenance terminal; when the built-in rules of the financial data verification program are met, the newly reported financial data will be added to the second database as a consolidated report data source.

2. The method for linking intelligent consolidated statements with financial statements according to claim 1, characterized in that: After adopting dual-instance deployment, storing the financial statements in the first database, and storing the consolidated statement data source in the second database, the method further includes: Adding financial statements to the first database through a preset interface; When the preset upload button in the preset interface is triggered, a new instruction is sent to the data listener; The data listener is then activated so that the data listener records the newly added financial statements.

3. The method for linking intelligent consolidated statements with financial statements according to claim 2, characterized in that: The operation of adding a financial statement to the first database through the preset interface specifically includes: Select the report filling task through the preset financial report upload interface; Determine the applicable consolidation scope of the financial statements to be submitted this time and the type of report by selecting the report submission task; the types of reports include at least: daily report, weekly report, ten-day report, monthly report, quarterly report, semi-annual report, and annual report; Determine the time point when reporting is required, the report data of the specific unit to be reported, and determine the specific reports to be reported; among which, the specific reports include at least: balance sheet, income statement, and cash flow statement.

4. The method for linking intelligent consolidated statements with financial statements according to claim 1, characterized in that: When the second database receives the newly reported financial data, the financial data verification procedure is triggered, which specifically includes: When the second database receives newly reported financial data, the financial data verification program is triggered to verify whether the financial data contains the preset necessary fields, whether the various fields in the financial data conform to the preset logical relationship, and compare it with the existing data to verify whether there is a change greater than the preset difference value.

5. The method for linking intelligent consolidated statements with financial statements according to claim 1, characterized in that: After adding the newly reported financial data as a consolidated report data source to the second database, the method further includes: Using the preset detection time points as intervals, compare in real time whether there are any differences between the newly reported financial data and the newly added consolidated report data source between the last preset detection time point and the current preset detection time point; When there are differences, replace the newly added consolidated report data source with the newly reported financial data.

6. A linkage system for intelligent consolidated statements and financial statements, characterized in that: The system comprises: A storage module, used to adopt dual-instance deployment, store financial statements in the first database, and store the consolidated statement data source in the second database; An extraction module is used to embed a data listener in the first database, so that when the data listener detects the presence of newly reported financial data, an extraction instruction is transmitted to the ETL tool, and the newly reported financial data is extracted to the second database through the ETL tool; Add a module to trigger the financial data verification program when the second database receives newly reported financial data; when the built-in rules of the financial data verification program are not met, the newly reported financial data will be returned and a reminder message will be sent to the preset maintenance terminal; when the built-in rules of the financial data verification program are met, the newly reported financial data will be added to the second database as a consolidated report data source.

7. The linkage system of intelligent consolidated statements and financial statements according to claim 6, characterized in that: The extraction module includes a recording unit, Used to add financial statements to the first database through a preset interface; When the preset upload button in the preset interface is triggered, a new instruction is sent to the data listener; The data listener is then activated so that the data listener records the newly added financial statements.

8. The linkage system of intelligent consolidated statements and financial statements according to claim 6, characterized in that: The system comprises an upload module, Used to select report filling tasks through the preset financial report upload interface; Determine the applicable consolidation scope of the financial statements to be submitted this time and the type of report by selecting the report submission task; the types of reports include at least: daily report, weekly report, ten-day report, monthly report, quarterly report, semi-annual report, and annual report; Determine the time point when reporting is required, the report data of the specific unit to be reported, and determine the specific reports to be reported; among which, the specific reports include at least: balance sheet, income statement, and cash flow statement.

9. The linkage system of intelligent consolidated statements and financial statements according to claim 6, characterized in that: The system also includes a verification module, When the second database receives newly reported financial data, it triggers the financial data verification program to verify whether the financial data contains preset necessary fields, whether the various fields in the financial data conform to the preset logical relationship, and compares it with the existing data to verify whether there is a change greater than the preset difference value.

10. A non-volatile computer storage medium, characterized in that: Computer instructions are stored thereon, and when the computer instructions are executed, a method for linking an intelligent consolidated statement with a financial statement is implemented as described in any one of claims 1 to 5.

Images