ERP (Enterprise Resource Planning) system financial and business data reconciliation method and system based on checking method

Abstract

The invention provides an ERP (Enterprise Resource Planning) system financial and business data reconciliation method and system based on a checking method, and relates to the technical field of computers, and the method comprises a data acquisition module which obtains reconciliation data from a third-party data source in a unified configuration form; the reconciliation rule maintenance module is used for defining a basic framework of reconciliation and performing reconciliation by using a dynamic SQL technology; and the data display module is used for carrying out personalized display on different reconciliation data and reconciliation results by using a dynamic page loading technology. The problems of different reconciliation data sources, reconciliation logic differentiation and personalized result display are solved.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and specifically, to a method and system for reconciling financial and business data of an ERP system based on a verification method. Background Art

[0002] Data reconciliation is a process for monitoring whether the data of upstream and downstream business systems is consistent, and is used to ensure the accuracy of the data of upstream and downstream business systems. Data reconciliation is applied in many industrial fields. For example, in the financial industry. Since various business systems in the financial industry have relatively strict requirements for data consistency, data reconciliation is an essential business link in the business system process of the financial industry, a powerful tool for detecting inconsistent data between upstream and downstream business systems, and also the last means to ensure the accuracy of data.

[0003] The invention patent with the publication number CN109743133B discloses a data reconciliation method and device, including: a data receiver receives data blocks; parses the data blocks to obtain a first code, a second code, and data to be reconciled; verifies the data to be reconciled obtained by parsing according to the second code obtained by parsing; if the verification is successful, reconciles the data to be reconciled obtained by parsing according to the first code obtained by parsing.

[0004] In summary, the common current reconciliation methods between systems include manual reconciliation, report reconciliation, program reconciliation, etc. These methods have problems such as difficult data extraction, limited reconciliation scope, high labor costs, and non-standard reconciliation processes. Summary of the Invention

[0005] In view of the defects in the prior art, the present invention provides a method and system for reconciling financial and business data of an ERP system based on a verification method.

[0006] According to the method and system for reconciling financial and business data of an ERP system based on a verification method provided by the present invention, the solutions are as follows:

[0007] In a first aspect, a system for reconciling financial and business data of an ERP system based on a verification method is provided. The system includes:

[0008] A data collection module: obtains reconciliation data from a third-party data source in a uniformly configured form;

[0009] A reconciliation rule maintenance module: defines the basic framework for reconciliation and uses dynamic SQL technology for reconciliation;

[0010] A data display module: uses dynamic page loading technology to perform personalized display on different reconciliation data and reconciliation results.

[0011] Preferably, the data collection module includes:

[0012] Data Management Module: Set the function of managing the metadata of data tables, including the name of the table, primary key, index, and column information; it can directly import the table structure information from the database into the reconciliation platform, or after modifying the table structure data on the reconciliation platform, synchronize it back to the database in reverse.

[0013] Data Fetching Module: Set different data fetching methods for each table, and actively or passively obtain the basic reconciliation data from the third-party system in various forms. The data fetching conditions can be configured or manually input on the page.

[0014] Query Module: Set a dynamic page to query the collected reconciliation data. The query conditions of this page can be configured by itself, and the data result columns change automatically according to the table structure.

[0015] Preferably, the reconciliation rule maintenance module includes:

[0016] Reconciliation System Maintenance Module: Differentiate the systems that need to be reconciled by system type.

[0017] Reconciliation Plan Maintenance Module: Set multiple groups of reconciliation plans. The operation permissions for reconciliation are authorized according to the reconciliation plan + accounting set. The reconciliation period is divided into daily reconciliation and monthly reconciliation, and each reconciliation plan uses a different reconciliation period to meet specific reconciliation requirements.

[0018] Reconciliation Template Maintenance Module: Divide the verification methods of the reconciliation template into system reconciliation and only confirm the result; for system reconciliation, maintain the reconciliation SQL in the reconciliation template, compare the data on the reconciliation platform and generate the reconciliation result; for only confirm the result, the external system sends the reconciliation result to the reconciliation platform, and then maintain the SQL for obtaining the successful number or failed number on the reconciliation template.

[0019] Reconciliation Field Maintenance Module: Maintain the conditional fields and comparison fields required for each reconciliation template, as well as the allowable error for each field.

[0020] Preferably, the reconciliation template maintenance module includes: Provide multiple comparison methods, which can be configured according to needs. Each reconciliation template can specify a custom result table or use the default result table.

[0021] Preferably, the data display module includes:

[0022] Reconciliation Result Overview Module: From the perspective of system type, display how many templates in each accounting set have completed reconciliation and confirmed the reconciliation information within the reconciliation period, and query the overall completion situation of the reconciliation.

[0023] Reconciliation result summary query module: From the perspective of the reconciliation plan, display the number of successful and failed reconciliations for each reconciliation template in each accounting set during the reconciliation period; users can link to the detailed reconciliation results of a certain reconciliation template from this page to make remarks and confirm the reconciliation results.

[0024] Reconciliation result default table query module: Use fixed fields to display the detailed reconciliation results and query the reconciliation details.

[0025] Reconciliation result custom table query module: Personalize the configuration according to the query requirements through the display fields to display the reconciliation results.

[0026] In the second aspect, a method for reconciling financial and business data of an ERP system based on the verification method is provided. The method includes:

[0027] Data collection step: Obtain reconciliation data from a third-party data source in a unified configuration form.

[0028] Reconciliation rule maintenance step: Define the basic framework of the reconciliation and use dynamic SQL technology for reconciliation.

[0029] Data display step: Use dynamic page loading technology to perform personalized display of different reconciliation data and reconciliation results.

[0030] Preferably, the data collection step includes:

[0031] Data management step: Set the data table metadata management function, including the name, primary key, index, and column information of the table; be able to directly import the table structure information from the database into the reconciliation platform, or after modifying the table structure data on the reconciliation platform, synchronize it back to the database in reverse.

[0032] Data extraction step: Set different data extraction methods for each table, and actively or passively obtain the basic reconciliation data from a third-party system in various forms. The data extraction conditions can be configured or manually entered on the page.

[0033] Query step: Set a dynamic page to query the collected reconciliation data. The query conditions of this page can be configured by itself, and the data result columns change automatically according to the table structure.

[0034] Preferably, the reconciliation rule maintenance step includes:

[0035] Reconciliation system classification maintenance step: Classify the systems that need to be reconciled by system.

[0036] Reconciliation plan maintenance step: Set multiple groups of reconciliation plans. The operation permissions for reconciliation are authorized according to the reconciliation plan + accounting set. The reconciliation period is divided into daily reconciliation and monthly reconciliation, and each reconciliation plan uses a different reconciliation period to meet specific reconciliation requirements.

[0037] Steps for reconciling statement template maintenance: The reconciliation methods of the reconciliation statement template are divided into system reconciliation and only result confirmation; for the system reconciliation, reconciliation SQL is maintained for the reconciliation statement template, data is compared on the reconciliation platform, and a reconciliation result is generated; for only result confirmation, the external system sends the reconciliation result to the reconciliation platform, and then SQL for obtaining the successful count or failed count is maintained on the reconciliation statement template.

[0038] Steps for reconciling field maintenance: Maintain the conditional fields and comparison fields required for each reconciliation statement template, as well as the allowable error for each field.

[0039] Preferably, the steps for reconciling statement template maintenance include: providing multiple comparison methods, which can be configured according to needs, and each reconciliation statement template can specify a custom result table or use the default result table.

[0040] Preferably, the steps for data display include:

[0041] Steps for overview of reconciliation results: From the perspective of other systems, display how many templates in each accounting set have completed reconciliation and confirmed reconciliation information during the reconciliation period, and query the overall completion status of the reconciliation.

[0042] Steps for summary query of reconciliation results: From the perspective of the reconciliation plan, display the number of successful and failed reconciliations for each reconciliation statement template in each accounting set during the reconciliation period; users can link to the detailed reconciliation results of a certain reconciliation statement template from this page to make remarks and confirm the reconciliation results.

[0043] Steps for querying the default table of reconciliation results: Use fixed fields to display the detailed reconciliation results and query the reconciliation details.

[0044] Steps for querying the custom table of reconciliation results: Configure the display fields according to the query requirements for personalized configuration and display the reconciliation results.

[0045] Compared with the prior art, the present invention has the following beneficial effects:

[0046] 1. Based on unified configuration, the present invention allows users to obtain reconciliation data from third-party data sources through methods such as multi-data sources, microservices, telegrams, and REST, solving the problem of difficult data extraction for reconciliation.

[0047] 2. The present invention provides multiple data comparison methods, solving the problem of different reconciliation logics.

[0048] 3. The present invention provides two reconciliation result storage methods, uses dynamic page loading technology, and performs personalized display on different reconciliation data and reconciliation results, solving the problem of personalized result display.

[0049] Other beneficial effects of the present invention will be described in the specific implementation manners through the introduction of specific technical features and technical solutions. Those skilled in the art should be able to understand the beneficial technical effects brought by the technical features and technical solutions through the introduction of these technical features and technical solutions. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] By reading the following detailed description of non-limiting embodiments with reference to the accompanying drawings, other features, objects, and advantages of the present invention will become more apparent:

[0051] Figure 1 is the overall system block diagram of the present invention;

[0052] Figure 2 is the reconciliation template maintenance diagram;

[0053] Figure 3 is the data collection diagram of the data table;

[0054] Figure 4 is the overview diagram of the reconciliation result. SPECIFIC IMPLEMENTATION MANNERS

[0055] The present invention will be described in detail below with reference to specific embodiments. The following embodiments will help those skilled in the art to further understand the present invention, but do not limit the present invention in any form. It should be noted that those of ordinary skill in the art can make several changes and improvements without departing from the concept of the present invention. These all belong to the protection scope of the present invention.

[0056] An embodiment of the present invention provides an ERP system financial and business data reconciliation system based on the verification method. Referring to Figure 1 as shown, the system includes: a data collection module, a reconciliation rule maintenance module, and a data display module.

[0057] 1. Data collection module: This module adopts a unified configuration form, allowing users to obtain reconciliation data from third-party data sources through methods such as multi-data sources, microservices, telegrams, and REST. The user defines one or more data extraction methods for each data table in the data extraction configuration interface of the data table. Referring to Figure 2 as shown, set the data extraction parameters of each data extraction method (including database connection string, microservice / telegram number, REST request address, etc.), and can grab data from the defined data sources with one key on the unified data capture interface, solving the problems of different sources of reconciliation data and difficulty in obtaining reconciliation data.

[0058] The reconciliation platform maintains a set of data table metadata management functions, including table names, primary keys, indexes, column information, etc. The table structure information can be directly imported from the database into the reconciliation platform, or after modifying the table structure data on the reconciliation platform, it can be synchronously reversed to the database, thus avoiding the problem of frequently operating the database in the background.

[0059] The reconciliation platform can maintain different data extraction methods for each table, actively or passively obtain the basic reconciliation data from third-party systems in various forms, and the data extraction conditions can also be configured or manually input on the page.

[0060] The reconciliation platform provides a dynamic page to query the collected reconciliation data. The query conditions of this page can be configured by itself, and the data result columns will automatically change according to the table structure.

[0061] 2. Reconciliation rule maintenance module: This module defines the basic framework of reconciliation and uses dynamic SQL technology to achieve different reconciliations.

[0062] System-level maintenance of the reconciliation system: Differentiate the systems that need to be reconciled by system level.

[0063] Reconciliation plan maintenance: The reconciliation plan is the largest management scope of reconciliation management. There can be multiple groups of reconciliations under one reconciliation plan. The operation permissions of reconciliation are authorized according to "reconciliation plan + accounting set". The reconciliation period is divided into daily reconciliation and monthly reconciliation. Each reconciliation plan can use different reconciliation periods to meet specific reconciliation requirements.

[0064] Reconciliation template maintenance: The reconciliation template is the smallest basic unit of reconciliation, as shown in Figure 3 Some reconciliations are carried out in other systems. In order to uniformly manage them in the reconciliation system, the verification methods of the reconciliation template are divided into system reconciliation and only confirm the result. For system reconciliation, the reconciliation SQL is maintained in the reconciliation template, and the data is compared on the reconciliation platform to generate the reconciliation result. For the template that only confirms the result, the external system sends the reconciliation result to the reconciliation platform, and then the SQL for obtaining the successful number or failed number is maintained on the reconciliation template. The reconciliation platform provides 4 comparison methods, which can be configured according to needs. Each reconciliation template can specify a custom result table or use the default result table.

[0065] The following is the implementation principle of each comparison method:

[0066] a. Pass the result of A as a parameter into B (dynamic condition method);

[0067] The system will first execute SQL-A, and then each result retrieved by A will be passed as a parameter value into SQL-B. Finally, the two query results will be compared according to the configured comparison fields.

[0068] b. Use the reconciliation condition details table (exhaustive condition method);

[0069] The system will first query the reconciliation condition details table, which stores all possible comparison conditions for the two comparison tables. Then, each group of conditions in the reconciliation condition result table will be passed into SQL-A and SQL-B respectively. Finally, the two query results will be compared according to the configured comparison fields.

[0070] c. Process the condition fields by oneself;

[0071] The system will only execute SQL-A. The user processes the reconciliation logic of the two tables in SQL-A, and then places the condition fields and numerical fields in the result column.

[0072] The following are the principles, advantages and disadvantages of the two result storage methods:

[0073] a. Use the default result table;

[0074] The system provides a default storage table with fixed storage fields. After comparison, all condition fields will be concatenated with the @ symbol and written. The advantage is that it is more convenient to use and there is no need to create an additional table. The disadvantage is that it is difficult to identify the concatenated condition fields and their meanings are unknown.

[0075] b. Use a custom result table;

[0076] The user needs to create a table by oneself (provide a table creation page), and this table must have some fixed necessary fields. Other fields can be set by oneself. After comparison, the comparison result fields will be written into the corresponding fields of this table according to the configuration. The advantage is that additional fields (such as Chinese descriptions) can be stored, and the meaning of each field is clear.

[0077] Reconciliation field maintenance: This page maintains the condition fields, comparison fields required for each reconciliation template, and information such as the allowable error for each field.

[0078] 3. Data display module: This module uses a configured form and dynamic page loading technology to perform personalized display of different reconciliation data and reconciliation results.

[0079] To meet different management and query requirements, there are four display forms for the reconciliation results:

[0080] a. Reconciliation result overview: This page shows, from another perspective of the system, how many templates in each account set have completed reconciliation, confirmed reconciliation, etc. during the reconciliation period, and it is convenient to query the overall completion status of the reconciliation. Refer to Figure 4 as shown.

[0081] b. Summary Query of Reconciliation Results: From the perspective of the reconciliation plan, this page shows the number of successful and failed reconciliations for each reconciliation template in each accounting set during the reconciliation period. Users can link to the detailed reconciliation results of a certain reconciliation template from this page to make remarks and confirm the reconciliation results.

[0082] c. Detailed Query of Reconciliation Results (Default Table): This page displays the detailed reconciliation results using fixed fields, and it is convenient to query the reconciliation details without additional configuration.

[0083] d. Detailed Query of Reconciliation Results (Custom Table): The display fields of this page can be personalized configured according to the query requirements, and the reconciliation results can be displayed in the most concise and intuitive way.

[0084] The present invention also provides a method for reconciling financial and business data of an ERP system based on the checking method, which specifically includes:

[0085] Data collection step: This step uses a unified configuration form and methods such as multi-data sources, microservices, and REST to obtain reconciliation data from third-party data sources.

[0086] The reconciliation platform maintains a set of data table metadata management functions, including the name of the table, primary key, index, column information, etc. The table structure information can be directly imported from the database into the reconciliation platform, or after modifying the table structure data on the reconciliation platform, it can be synchronously reversed to the database, thus avoiding the problem of frequently operating the database in the background.

[0087] The reconciliation platform can maintain different data extraction methods for each table, and actively or passively obtain the basic reconciliation data from the third-party system in various forms. The data extraction conditions can also be configured or manually input on the page.

[0088] The reconciliation platform provides a dynamic page to query the collected reconciliation data. The query conditions of this page can be configured by itself, and the data result columns will automatically change according to the table structure.

[0089] Reconciliation rule maintenance step: This step defines the basic framework of the reconciliation and uses dynamic SQL technology to achieve different reconciliations.

[0090] Reconciliation system classification maintenance: Classify the systems that need to be reconciled.

[0091] Reconciliation plan maintenance: The reconciliation plan is the largest management scope of the reconciliation management. There can be multiple groups of reconciliations under one reconciliation plan. The operation authority of the reconciliation is authorized according to "reconciliation plan + accounting set". The reconciliation period is divided into daily reconciliation and monthly reconciliation, and each reconciliation plan can use different reconciliation periods to meet specific reconciliation requirements.

[0092] Reconciliation Template Maintenance: The reconciliation template is the smallest basic unit for reconciliation. Some reconciliations are carried out in other systems. To manage them uniformly in the reconciliation system, the verification methods of the reconciliation template are divided into system reconciliation and only result confirmation. For system reconciliation, the reconciliation SQL is maintained in the reconciliation template, and the data is compared on the reconciliation platform to generate the reconciliation result. For the template of only result confirmation, the external system sends the reconciliation result to the reconciliation platform, and then the SQL for obtaining the successful count or failure count is maintained on the reconciliation template. The reconciliation platform provides 4 comparison methods, which can be configured according to needs. Each reconciliation template can specify a custom result table or use the default result table.

[0093] Reconciliation Field Maintenance: This page maintains the conditional fields and comparison fields required for each reconciliation template, as well as information such as the allowable error for each field.

[0094] Data Display Step: This step uses a configured form and dynamic page loading technology to perform personalized display of different reconciliation data and reconciliation results.

[0095] To meet different management and query requirements, there are four display forms for the reconciliation result:

[0096] a. Reconciliation Result Overview: This page shows, from the perspective of other systems, information such as how many templates in each accounting set have completed reconciliation and confirmed reconciliation during the reconciliation period, and it is convenient to query the overall completion status of the reconciliation.

[0097] b. Reconciliation Result Summary Query: This page shows, from the perspective of the reconciliation plan, the number of successful and failed reconciliations for each reconciliation template in each accounting set during the reconciliation period. Users can link to the detailed reconciliation result of a certain reconciliation template from this page to make remarks and confirm the reconciliation result.

[0098] c. Reconciliation Result Detail Query (Default Table): This page uses fixed fields to display the detailed reconciliation result, and it is convenient to query the reconciliation details without additional configuration.

[0099] d. Reconciliation Result Detail Query (Custom Table): The display fields of this page can be personalized configured according to the query requirements, and the reconciliation result can be displayed in the simplest and most intuitive way.

[0100] The embodiment of the present invention provides a method and system for reconciling financial and business data of an ERP system based on the verification method. Based on unified configuration, reconciliation data is obtained from a third-party data source through methods such as multi-data sources, microservices, messages, and REST, solving the problem of different sources of reconciliation data. Multiple data comparison methods are provided, including the exhaustive method, using the result of A as a condition to be passed into B, custom processing, etc., solving the problem of different reconciliation logics. Multiple storage methods for reconciliation results are provided, and dynamic page loading technology is used to perform personalized display of different reconciliation data and reconciliation results, solving the problem of personalized result display.

[0101] Those skilled in the art know that in addition to implementing the system and its various devices, modules, and units provided by the present invention in the form of pure computer-readable program code, the method steps can be logically programmed to enable the system and its various devices, modules, and units provided by the present invention to be implemented in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers, etc., to achieve the same functions. Therefore, the system and its various devices, modules, and units provided by the present invention can be considered as a kind of hardware component, and the devices, modules, and units included therein for implementing various functions can also be regarded as the structures within the hardware component; the devices, modules, and units for implementing various functions can also be regarded as either software modules for implementing the method or structures within the hardware component.

[0102] The specific embodiments of the present invention have been described above. It should be understood that the present invention is not limited to the above specific embodiments, and those skilled in the art can make various changes or modifications within the scope of the claims, which does not affect the essence of the present invention. Without conflict, the embodiments of the present application and the features in the embodiments can be combined with each other arbitrarily.

Claims

1. An ERP system financial and business data reconciliation system based on the verification method, characterized in that: include: Data collection module: uses a unified configuration to obtain reconciliation data from third-party data sources; Reconciliation rule maintenance module: defines the basic structure of reconciliation and uses dynamic SQL technology to perform reconciliation; Data display module: Use dynamic page loading technology to personalize the display of different reconciliation data and reconciliation results.

2. The ERP system financial and business data reconciliation system based on the verification method according to claim 1 is characterized in that: The data acquisition module comprises: Data management module: set up data table metadata management functions, including table name, primary key, index, and column information; can directly import table structure information from the database to the reconciliation platform, or modify the table structure data on the reconciliation platform and synchronize it back to the database; Data acquisition module: Set different data acquisition methods for each table, and use various forms to actively or passively obtain basic reconciliation data from third-party systems. The data acquisition conditions can be configured or manually entered on the page; Query module: Set up a dynamic page to query the collected reconciliation data. The query conditions of this page can be configured by yourself, and the data result column changes automatically according to the table structure.

3. The ERP system financial and business data reconciliation system based on the verification method according to claim 1 is characterized in that: The reconciliation rule maintenance module includes: Reconciliation system maintenance module: distinguish the systems that need to be reconciled by system; Reconciliation plan maintenance module: Set up multiple reconciliation plans. The reconciliation operation permissions are authorized according to the reconciliation plan + account set. The reconciliation cycle is divided into daily reconciliation and monthly reconciliation. Each reconciliation plan uses a different reconciliation cycle to meet specific reconciliation requirements; Reconciliation template maintenance module: the reconciliation template verification mode is divided into system reconciliation and result confirmation only; the system reconciliation is to maintain the reconciliation SQL in the reconciliation template, compare the data on the reconciliation platform and generate the reconciliation result; the result confirmation only is that the external system sends the reconciliation result to the reconciliation platform, and then maintains the SQL for obtaining the number of successes or failures on the reconciliation template; Reconciliation field maintenance module: maintains the conditional fields and comparison fields required for each reconciliation template, as well as the allowable error for each field.

4. The ERP system financial and business data reconciliation system based on the verification method according to claim 3 is characterized in that: The reconciliation template maintenance module includes: providing multiple comparison methods, which can be configured according to needs, and each reconciliation template can specify a custom result table or use a default result table.

5. The ERP system financial and business data reconciliation system based on the verification method according to claim 1 is characterized in that: The data display module includes: Reconciliation result overview module: From the perspective of the system, it shows how many templates have completed reconciliation and confirmed reconciliation information for each account set within the reconciliation cycle, and queries the overall completion status of the reconciliation; Reconciliation result summary query module: from the perspective of the reconciliation plan, it displays the number of successful and failed reconciliations for each reconciliation template in each account set during the reconciliation cycle; users can link to the reconciliation result details of a certain reconciliation template from this page to make notes and confirm the reconciliation results; Reconciliation result default table query module: use fixed fields to display the reconciliation result details and query the reconciliation details; Reconciliation result custom table query module: display the reconciliation results by personalizing the display fields according to the query requirements.

6. A method for reconciling financial and business data in an ERP system based on a verification method, characterized in that: include: Data collection steps: Use unified configuration to obtain reconciliation data from third-party data sources; Reconciliation rule maintenance steps: define the basic structure of reconciliation and use dynamic SQL technology to perform reconciliation; Data display steps: Use dynamic page loading technology to display different reconciliation data and reconciliation results in a personalized manner.

7. The ERP system financial and business data reconciliation method based on the verification method according to claim 6 is characterized in that: The data collection step comprises: Data management steps: Set up data table metadata management functions, including table name, primary key, index, and column information; be able to directly import table structure information from the database to the reconciliation platform, or modify table structure data on the reconciliation platform and then synchronize it back to the database; Data acquisition step: Set different data acquisition methods for each table, and use various forms to actively or passively obtain basic reconciliation data from third-party systems. The data acquisition conditions can be configured or manually entered on the page; Query step: Set up a dynamic page to query the collected reconciliation data. The query conditions of this page can be configured by yourself, and the data result column changes automatically according to the table structure.

8. The ERP system financial and business data reconciliation method based on the verification method according to claim 6 is characterized in that: The reconciliation rule maintenance steps include: Reconciliation system maintenance steps: distinguish the systems that need to be reconciled by system; Reconciliation plan maintenance steps: Set up multiple reconciliation plans. The reconciliation operation permissions are authorized according to the reconciliation plan + account set. The reconciliation cycle is divided into daily reconciliation and monthly reconciliation. Each reconciliation plan uses a different reconciliation cycle to meet specific reconciliation requirements; Reconciliation template maintenance step: the reconciliation template verification method is divided into system reconciliation and result confirmation only; the system reconciliation is to maintain the reconciliation SQL in the reconciliation template, compare the data on the reconciliation platform and generate the reconciliation result; the result confirmation only is that the external system sends the reconciliation result to the reconciliation platform, and then maintains the SQL for obtaining the number of successes or failures on the reconciliation template; Reconciliation field maintenance steps: Maintain the conditional fields and comparison fields required for each reconciliation template, as well as the allowable error for each field.

9. The ERP system financial and business data reconciliation method based on the verification method according to claim 8 is characterized in that: The reconciliation template maintenance step includes: providing multiple comparison methods, configuring them according to needs, and each reconciliation template can specify a custom result table or use a default result table.

10. The ERP system financial and business data reconciliation method based on the verification method according to claim 6, characterized in that: The data display step comprises: Reconciliation result overview step: From the perspective of the system, it shows how many templates have completed reconciliation and confirmed reconciliation information for each account set within the reconciliation cycle, and queries the overall completion status of the reconciliation; Reconciliation result summary query steps: From the perspective of the reconciliation plan, the number of successful and failed reconciliations for each reconciliation template in each account set during the reconciliation cycle is displayed; users can link to the reconciliation result details of a reconciliation template from this page to make notes and confirm the reconciliation results; Steps for querying the default table of reconciliation results: Use fixed fields to display the reconciliation result details and query the reconciliation details; Steps for customizing the query table for reconciliation results: Customize the display fields according to query requirements to display the reconciliation results.

Images