CN111695326B

CN111695326B - XBRL report checking method and device

Info

Publication number: CN111695326B
Application number: CN202010498940.3A
Authority: CN
Inventors: 舒小娟; 王斌; 周颖婕; 诸文东
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2020-06-04
Filing date: 2020-06-04
Publication date: 2023-07-21
Anticipated expiration: 2040-06-04
Also published as: CN111695326A

Abstract

The embodiment of the application provides a method and a device for checking an XBRL report, wherein the method comprises the following steps: judging whether configuration information of each target label of the source XBRL report is contained in a preset label library, if yes, generating source XBRL report check data consisting of attribute values of each target label of the source XBRL report, wherein the label library is used for storing the configuration information of each label which is newly added and/or multiplexed according to a user instruction; generating target report check data corresponding to the target report, wherein the type of the target report is the same as the configuration information of the corresponding target label; distributed data reconciliation is performed on the source XBRL report and the target report to determine whether to disclose information for the source XBRL report based on the corresponding reconciliation results. The method and the device can effectively improve the flexibility, efficiency and accuracy of XBRL report checking, and further can effectively improve the efficiency, the authenticity and the reliability of information disclosure or disclosure of the XBRL report.

Description

XBRL report checking method and device

Technical Field

The application relates to the technical field of data processing, in particular to a method and a device for checking an XBRL report.

Background

The extensible business reporting language XBRL (EXtensible Business Reporting Language) is an XML-based markup language for the definition and exchange of business and financial information, a method of standardized definition and representation of business data. In the financial industry, XBRL reports are widely used as an important information display mode. Wherein, in order to ensure the accuracy of business and financial information, data verification is required for the generated XBRL report.

Currently, the main way to check the data of the XBRL report is to use the inherent tag to check the data of the XBRL report in a serial cycle traversing way, which cannot guarantee the efficiency and quality of the check of the XBRL report, and even if part of the tags are generated in advance, it is difficult to exhaust all the tags related to various types of XBRL reports. For example, before information disclosure is performed to a license manager, a fund company performs data verification of an XBRL report with a hosting bank, in the existing verification method, it is difficult to ensure that each tag of the XBRL report can be covered by an inherent tag, so that verification work of the XBRL report cannot be completed.

Disclosure of Invention

Aiming at the problems in the prior art, the application provides the XBRL report checking method and the XBRL report checking device, which can effectively improve the flexibility, the efficiency and the accuracy of XBRL report checking, and further can effectively improve the efficiency, the authenticity and the reliability of information disclosure or disclosure of an XBRL report.

In order to solve the technical problems, the application provides the following technical scheme:

in a first aspect, the present application provides an XBRL report checking method, including:

judging whether configuration information of each target label of an active XBRL report is contained in a preset label library, if yes, generating source XBRL report check data composed of attribute values of each target label of the active XBRL report, wherein the label library is used for storing the configuration information of each label which is newly added and/or multiplexed according to a user instruction;

generating a target report with the same type as the source XBRL report and the configuration information of the corresponding target label, and acquiring target report check data corresponding to the target report;

and carrying out distributed data verification on the source XBRL report and the target report according to the configuration information of each target label so as to determine whether to carry out information disclosure on the source XBRL report or not based on the corresponding verification result.

Further, if the source XBRL report is an XBRL report of a fund company, the target report is a hosted line report of a hosted bank corresponding to the fund company;

correspondingly, before judging whether the configuration information of each target tag of the active XBRL report is contained in the preset tag library, the method further comprises:

Receiving an XBRL report checking request sent by a terminal of a fund company, and reading an XBRL report of the fund company from the XBRL report checking request;

correspondingly, the XBRL report checking method further comprises the following steps:

and judging whether the XBRL report of the fund company accords with a preset disclosure requirement according to the checking result, and if so, sending the XBRL report of the fund company to a license to perform information disclosure.

Further, the method further comprises the following steps:

if the configuration information of at least one target tag reported by the source XBRL is judged to be not contained in the tag library, sending a configuration request aiming at the target tag which is not contained in the tag library to a user terminal corresponding to the tag library;

receiving a user instruction which is sent by the user terminal based on the configuration request and aims at the tag library, wherein the user instruction contains attribute information of target tags which are not contained in the tag library;

and adding the attribute information of the target tag in the tag newly-added instruction into the tag library to form configuration information of the target tag in the tag library.

Further, each of the tags in the tag library corresponds to at least four attributes: tag type attributes, context attributes, precision attributes, and unit attributes;

Correspondingly, the generating the source XBRL report checking data composed of the attribute values of the target labels of the source XBRL report comprises the following steps:

acquiring the values of the tag type attribute, the context attribute, the precision attribute and the unit attribute corresponding to each target tag from the source XBRL report;

and generating corresponding source XBRL report check data based on the values of the tag type attribute, the context attribute, the precision attribute and the unit attribute corresponding to each target tag.

Further, the generating the target report with the same type of the source XBRL report and the configuration information of the corresponding target label includes:

acquiring the report type and the fund type of the XBRL report of the fund company;

based on the report type and the fund type of the XBRL report of the fund company, correspondingly searching to obtain prestored managed line system matching information;

and generating a managed line report with the same report type and the same fund type as those of the XBRL report of the fund company according to the managed line system matching information, wherein the managed line report is identical to the configuration information of each target label of the XBRL report of the fund company.

Further, the obtaining the target report check data corresponding to the target report includes:

Judging whether the attributes of all the target labels in the target report correspond to prestored set values, if so, determining the values of the corresponding attributes of all the target labels according to the set values of the attributes of all the target labels to the application;

and generating target report check data corresponding to the target report based on the value of the attribute corresponding to each target label.

Further, the obtaining the target report check data corresponding to the target report further includes:

and if the attribute of the target label which does not correspond to the set value exists in the target report through judgment, generating a value of the attribute of the target label which does not correspond to the set value based on a preset dynamic structured query statement for label configuration.

Further, the performing distributed data checking on the source XBRL report and the target report according to the configuration information of each target tag includes:

and distributing each target label to a plurality of independently operated service clusters so that each service cluster performs distributed data check on the source XBRL report and the target report, wherein each service cluster comprises a plurality of servers, and each server is respectively used for processing a check task corresponding to one target label through a unique corresponding thread.

Further, the method further comprises the following steps:

receiving a user instruction aiming at the tag library, which is sent by the user terminal based on the configuration request, in real time, wherein the user instruction comprises: a new instruction of attribute information of the tag which is not contained in the tag library and/or a multiplexing instruction of attribute information of an original tag which is already contained in the tag library;

and updating the tag library according to the user instruction.

In a second aspect, the present application further provides an XBRL report checking apparatus, including:

the first data generation module is used for judging whether configuration information of each target label of the source XBRL report is contained in a preset label library, if yes, generating source XBRL report check data composed of attribute values of each target label of the source XBRL report, wherein the label library is used for storing the configuration information of each label which is newly added and/or multiplexed according to a user instruction;

the second data generation module is used for generating a target report with the same type as the source XBRL report and the configuration information of the corresponding target label, and acquiring target report check data corresponding to the target report;

and the data checking module is used for carrying out distributed data checking on the source XBRL report and the target report according to the configuration information of each target label so as to determine whether to carry out information disclosure on the source XBRL report or not based on the corresponding checking result.

correspondingly, the XBRL report checking device further includes:

the XBRL report receiving module is used for receiving an XBRL report checking request sent by a terminal of a fund company and reading an XBRL report of the fund company from the XBRL report checking request;

and the XBRL report sending module is used for judging whether the XBRL report of the fund company accords with the preset disclosure requirement according to the checking result, and if so, sending the XBRL report of the fund company to a license party for information disclosure.

Further, the method further comprises the following steps: a supplemental configuration tag module for performing the following:

correspondingly, the first data generating module is used for executing the following contents:

Further, the second data generation module includes: a managed line report generation unit for performing:

Further, the second data generation module includes: a target report collation data generation unit for executing the following:

Further, the target report collation data generation unit is further configured to execute:

Further, the data collation module includes:

and the distributed cluster execution unit is used for distributing each target label to a plurality of independently operated service clusters so that each service cluster performs distributed data check on the source XBRL report and the target report, wherein each service cluster comprises a plurality of servers, and each server is respectively used for processing a check task corresponding to one target label through a unique corresponding thread.

Further, the method further comprises the following steps: the tag library custom module is used for executing the following contents:

and updating the tag library according to the user instruction.

In a third aspect, the present application provides an electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the XBRL report reconciliation method when executing the program.

In a fourth aspect, the present application provides a computer readable storage medium having stored thereon a computer program which when executed by a processor implements the XBRL report reconciliation method described.

According to the technical scheme, the XBRL report checking method and device provided by the application comprise the following steps: judging whether configuration information of each target label of an active XBRL report is contained in a preset label library, if yes, generating source XBRL report check data composed of attribute values of each target label of the active XBRL report, wherein the label library is used for storing the configuration information of each label which is newly added and/or multiplexed according to a user instruction; generating a target report with the same type as the source XBRL report and the configuration information of the corresponding target label, and acquiring target report check data corresponding to the target report; according to the configuration information of each target label, distributed data verification is carried out on the source XBRL report and the target report so as to determine whether to carry out information disclosure on the source XBRL report or not based on a corresponding verification result, flexible configuration of labels of the XBRL report can be effectively realized through a custom label library, the accuracy, reliability and timeliness of label setting can be effectively improved, the verification efficiency and verification accuracy of the XBRL report can be effectively improved, meanwhile, the verification flexibility, efficiency and accuracy of the XBRL report can be further improved through the setting and distributed verification mode of the target report, accurate judgment basis can be further provided for the XBRL report needing to carry out information disclosure or disclosure, so that the efficiency, the authenticity and the reliability of the information disclosure or disclosure of the XBRL report can be effectively improved, and the source user of the XBRL report with information disclosure or disclosure and the user experience of the user needing to know the information in the XBRL report can be effectively improved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a flow chart of an XBRL report reconciliation method in an embodiment of the present application.

Fig. 2 is a flow chart of an XBRL report reconciliation method comprising steps 010 and 500 in an embodiment of the application.

Fig. 3 is a flow chart of an XBRL report reconciliation method comprising steps 120 through 140 in an embodiment of the present application.

Fig. 4 is a schematic diagram of a specific flow of step 200 in the XBRL report checking method in the embodiment of the present application.

Fig. 5 is a schematic flowchart of steps 310 to 330 in the XBRL report checking method in the embodiment of the present application.

Fig. 6 is a schematic flow chart of step 300 of the XBRL report checking method in the embodiment of the present application, including steps 340 to 360.

Fig. 7 is a schematic flow chart of step 300 of the XBRL report checking method including step 370 in the embodiment of the present application.

Fig. 8 is a schematic flow chart of steps 020 and 030 in the XBRL report checking method in the embodiment of the present application.

Fig. 9 is a schematic diagram of a first configuration of an XBRL report collation apparatus in the embodiment of the present application.

Fig. 10 is a schematic diagram of a second configuration of an XBRL report checking apparatus in an embodiment of the present application.

Fig. 11 is a schematic diagram of a third configuration of an XBRL report collation apparatus in the embodiment of the present application.

Fig. 12 is a schematic diagram of the structure of an XBRL report collation apparatus including the managed-line report generating unit 21 in the embodiment of the present application.

Fig. 13 is a schematic diagram of the structure of an XBRL report collation apparatus including the target report collation data generation unit 22 in the embodiment of the present application.

Fig. 14 is a schematic structural diagram of an XBRL report checking apparatus including a distributed cluster execution unit 31 in the embodiment of the present application.

Fig. 15 is a schematic structural diagram of an XBRL report checking device that includes a tag library custom module 70 in an embodiment of the present application.

Fig. 16 is a flowchart of an XBRL report reconciliation method in the present application example.

Fig. 17 is a detailed flowchart of the custom tag library in the present application example.

Figure 18 is a detailed flow chart of generating foundation corporation XBRL report data in this application example.

FIG. 19 is a detailed flow chart of generating managed line system report data in the present application example.

Fig. 20 is a distributed architecture diagram in the present application example.

Fig. 21 is a detailed flowchart of the XBRL collation and output result in the present application example.

Fig. 22 is a schematic structural diagram of an electronic device in an embodiment of the present application.

Detailed Description

For the purposes of making the objects, technical solutions and advantages of the embodiments of the present application more clear, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.

Aiming at the problems of poor expansibility and low verification efficiency and accuracy of the XBRL report caused by serial verification modes of the existing XBRL report, the embodiments of the application respectively provide an XBRL report verification method, an XBRL report verification device and an electronic equipment computer readable storage medium, and judge whether configuration information of each target label of an active XBRL report is contained in a preset label library or not, if yes, source XBRL report verification data consisting of attribute values of each target label of the active XBRL report is generated, wherein the label library is used for storing the configuration information of each label which is newly added and/or multiplexed according to a user instruction; generating a target report with the same type as the source XBRL report and the configuration information of the corresponding target label, and acquiring target report check data corresponding to the target report; according to the configuration information of each target label, distributed data checking is performed on the source XBRL report and the target report, so that whether to perform information disclosure processing on the source XBRL report or not is determined based on a corresponding checking result, flexible and efficient self-defined label library configuration and efficient and reliable distributed checking process are realized, flexible configuration of labels of the XBRL report can be effectively realized through the self-defined label library, accuracy, reliability and timeliness of label setting can be effectively improved, checking efficiency and checking accuracy of the XBRL report can be effectively improved, checking flexibility, efficiency and accuracy of the XBRL report can be further improved through the setting and distributed checking mode of the target report, accurate judgment basis can be provided for the XBRL report needing to perform information disclosure or disclosure, true efficiency, authenticity and reliability of the information disclosure or disclosure of the XBRL report can be effectively improved, and user experience of the information disclosure or disclosure of the information disclosure source of the XBRL report and user needing to acquire information in the information disclosure request of the XBRL report can be effectively improved.

The following examples are given by way of illustration.

In order to solve the problems of poor expansibility and low verification efficiency and accuracy of the existing XBRL report due to serial verification mode, the present application provides an embodiment of an XBRL report verification method, referring to fig. 1, where the XBRL report verification method specifically includes the following contents:

step 100: and judging whether configuration information of each target tag reported by the source XBRL is contained in a preset tag library, and if yes, executing step 200.

It can be understood that the source XBRL report may be a currently received XBRL report, or may be a previously received and timing processed XBRL report, which may be specifically set according to practical applications.

Step 200: generating source XBRL report check data composed of attribute values of all target tags of the source XBRL report, wherein the tag library is used for storing configuration information of all newly added and/or multiplexed tags according to user instructions.

In step 200, if the preset tag library includes configuration information of each target tag of the source XBRL report, the value of each attribute corresponding to each target tag, that is, the attribute value, is searched in the source XBRL report, and the corresponding relationship between each attribute corresponding to each target tag and each attribute value is stored, so as to form the source XBRL report verification data. In one example, the source XBRL report reconciles an example form of data, see table 1, where the representations of tags a and B are merely schematic and not actual tag numbers, while attribute values 1 through 4 are also merely schematic, with actual representations made up of numerical values.

TABLE 1

Step 300: and generating a target report with the same type as the source XBRL report and the configuration information of the corresponding target label, and acquiring target report check data corresponding to the target report.

In step 300, a preset matching rule may be applied to generate a target report that is the same as the type of the source XBRL report and the configuration information of the corresponding target tag. The matching rule may be pre-stored in a database locally or accessible to a server or a client device for executing the XBRL report reconciliation method, for example, the XBRL report reconciliation device for executing the XBRL report reconciliation method may be provided in a reconciliation platform of a hosted bank, and if the fund company sends an XBRL report to the reconciliation platform of the hosted bank, the XBRL report reconciliation device reads the XBRL report and looks up a pre-stored matching rule corresponding to the type and source of the source XBRL report in the reconciliation platform of the hosted bank, where the matching rule may be embodied in the form of hosted system matching information, in particular for identifying a logic rule for generating a target report corresponding to the XBRL report.

Step 400: and carrying out distributed data verification on the source XBRL report and the target report according to the configuration information of each target label so as to determine whether to carry out information disclosure on the source XBRL report or not based on the corresponding verification result.

As can be seen from the foregoing description, the XBRL report checking method provided by the embodiment of the present application can effectively implement flexible configuration of the tag of the XBRL report through the custom tag library, and can effectively improve accuracy, reliability and timeliness of tag setting, so as to effectively improve checking efficiency and checking accuracy of the XBRL report, and meanwhile, through setting and distributed checking modes of the target report, can further improve checking flexibility, efficiency and accuracy of the XBRL report, further can provide an accurate judgment basis for the XBRL report that needs to perform information disclosure or disclosure, so as to effectively improve true efficiency, authenticity and reliability of the information disclosure or disclosure of the XBRL report, and can effectively improve user experience of a source user of the XBRL report with information disclosure or disclosure requirements and a user who needs to learn information in the XBRL report.

In order to provide an XBRL report checking method suitable for a fund company, in one embodiment of the XBRL report checking method provided in the present application, if the source XBRL report is an XBRL report of the fund company, the target report is a hosted line report of a hosted bank corresponding to the fund company, and referring to fig. 2, step 100 of the XBRL report checking method specifically includes the following steps:

Step 010: and receiving an XBRL report checking request sent by the terminal of the fund company, and reading the XBRL report of the fund company from the XBRL report checking request.

Correspondingly, the following content is specifically included after step 400 of the XBRL report checking method:

step 500: and judging whether the XBRL report of the fund company accords with a preset disclosure requirement according to the checking result, and if so, sending the XBRL report of the fund company to a license to perform information disclosure.

As can be seen from the above description, the XBRL report checking method provided by the embodiment of the present application can effectively implement flexible configuration of the tag of the XBRL report of the foundation company, and further can effectively improve the checking flexibility, efficiency and accuracy of the XBRL report of the foundation company, so as to provide an accurate judgment basis for the XBRL report of the foundation company that needs to perform information disclosure to the license, and effectively improve the authenticity, accuracy and reliability of the information disclosure or disclosure of the XBRL report of the foundation company to the license.

In order to add a custom tag to a tag library when an unconfigured tag exists in a received XBRL report, in one embodiment of the XBRL report checking method provided in the present application, referring to fig. 3, step 100 of the XBRL report checking method may further specifically include the following:

Step 120: and if the configuration information of at least one target tag reported by the source XBRL is judged to be not contained in the tag library, sending a configuration request aiming at the target tag which is not contained in the tag library to a user terminal corresponding to the tag library.

Step 130: and receiving a user instruction which is sent by the user terminal based on the configuration request and is aimed at the tag library, wherein the user instruction contains attribute information of target tags which are not contained in the tag library.

Step 140: and adding the attribute information of the target tag in the tag newly-added instruction into the tag library to form configuration information of the target tag in the tag library.

From the above description, it can be known that the XBRL report checking method provided by the embodiment of the present application can further improve the applicability and flexibility of the custom tag library, and further can further improve the checking flexibility, efficiency and accuracy of the XBRL report.

In order to provide a specific way of providing the generation source XBRL report reconciliation data, in one embodiment of the XBRL report reconciliation method provided herein, each of the tags in the tag library corresponds to at least four attributes: the tag type attribute, the context attribute, the precision attribute and the unit attribute, referring to fig. 4, the step 200 of the XBRL report checking method specifically includes the following:

Step 210: and acquiring the values of the tag type attribute, the context attribute, the precision attribute and the unit attribute corresponding to each target tag from the source XBRL report.

Step 220: and generating corresponding source XBRL report check data based on the values of the tag type attribute, the context attribute, the precision attribute and the unit attribute corresponding to each target tag.

From the above description, the XBRL report checking method provided by the embodiment of the present application can effectively improve the reliability and effectiveness of the application of the source XBRL report checking data, and further can further improve the accuracy of XBRL report checking.

In order to provide a specific way to generate the target report, in one embodiment of the XBRL report checking method provided in the present application, referring to fig. 5, step 300 of the XBRL report checking method specifically includes the following:

step 310: and acquiring the report type and the fund type of the XBRL report of the fund company.

Step 320: and correspondingly searching to obtain prestored managed line system matching information based on the report type and the fund type of the XBRL report of the fund company.

Step 330: and generating a managed line report with the same report type and the same fund type as those of the XBRL report of the fund company according to the managed line system matching information, wherein the managed line report is identical to the configuration information of each target label of the XBRL report of the fund company.

From the above description, it can be seen that the XBRL report checking method provided by the embodiment of the present application can effectively improve the efficiency and accuracy of managed line report generation, and further can further improve the checking efficiency and accuracy of the XBRL report.

In order to provide a specific way to generate the target report collation data in the presence of the preset value, in one embodiment of the XBRL report collation method provided in the present application, referring to fig. 6, step 300 of the XBRL report collation method further specifically comprises the following:

step 340: and judging whether the attributes of all the target labels in the target report correspond to prestored set values, and if so, executing step 350.

Step 350: determining the value of each corresponding attribute of each target label according to the set value of each attribute of each target label to the application;

step 360: and generating target report check data corresponding to the target report based on the value of the attribute corresponding to each target label.

From the above description, it can be seen that the XBRL report checking method provided by the embodiment of the present application can effectively improve the reliability and accuracy of target report checking data generation, and further can further improve the checking reliability and accuracy of the XBRL report.

In order to provide a specific way to generate the target report collation data when there is no preset value, in one embodiment of the XBRL report collation method provided in the present application, referring to fig. 7, step 340 of the XBRL report collation method further specifically comprises the following:

step 370: and if the attribute of the target label which does not correspond to the set value exists in the target report through judgment, generating a value of the attribute of the target label which does not correspond to the set value based on a preset dynamic structured query statement for label configuration.

As can be seen from the above description, the XBRL report checking method provided by the embodiment of the present application can further improve the reliability and accuracy of target report checking data generation, and further can further improve the checking reliability and accuracy of the XBRL report.

In order to provide a specific way of distributing and checking data, in one embodiment of the XBRL report checking method provided in the present application, step 400 of the XBRL report checking method specifically includes the following:

step 410: and distributing each target label to a plurality of independently operated service clusters so that each service cluster performs distributed data check on the source XBRL report and the target report, wherein each service cluster comprises a plurality of servers, and each server is respectively used for processing a check task corresponding to one target label through a unique corresponding thread.

From the above description, the XBRL report checking method provided by the embodiment of the present application can effectively improve the efficiency and reliability of distributed data checking of the XBRL report.

In order to provide a specific way to customize the tag library at any time, in one embodiment of the XBRL report checking method provided in the present application, referring to fig. 8, the XBRL report checking method further specifically includes the following:

step 020: receiving a user instruction aiming at the tag library, which is sent by the user terminal based on the configuration request, in real time, wherein the user instruction comprises: a new instruction of the attribute information of the tag which is not contained in the tag library, and/or a multiplexing instruction of the attribute information of the original tag which is already contained in the tag library.

Step 030: and updating the tag library according to the user instruction.

It will be appreciated that the steps 020 and 030 may be performed before the step 010 to perform the preset of the tag library, or may be performed at any stage of the steps 100 to 500 to update the tag library at any time.

As can be seen from the above description, the XBRL report checking method provided by the embodiment of the present application can further improve the flexibility and reliability of the application of the tag library, and further can effectively improve the accuracy and reliability of the distributed data checking of the XBRL report.

In order to solve the problem of poor expandability and low XBRL report verification efficiency and accuracy caused by serial verification modes of the existing XBRL report verification from a software aspect, the present application provides an embodiment of an XBRL report verification device for implementing all or part of the content in an XBRL report verification method, and referring to fig. 9, the XBRL report verification device specifically includes the following contents:

the first data generating module 10 is configured to determine whether configuration information of each target tag of the source XBRL report is included in a preset tag library, if yes, generate source XBRL report check data composed of attribute values of each target tag of the source XBRL report, where the tag library is configured to store configuration information of each tag that is newly added and/or multiplexed according to a user instruction;

the second data generating module 20 is configured to generate a target report with the same type as the source XBRL report and configuration information of a corresponding target tag, and obtain target report verification data corresponding to the target report;

and a data checking module 30, configured to perform distributed data checking on the source XBRL report and the target report according to the configuration information of each target tag, so as to determine whether to perform information disclosure on the source XBRL report based on the corresponding checking result.

As can be seen from the foregoing description, the XBRL report checking device provided by the embodiment of the present application can effectively implement flexible configuration of the tag of the XBRL report through the custom tag library, and can effectively improve accuracy, reliability and timeliness of tag setting, so as to effectively improve checking efficiency and checking accuracy of the XBRL report, and meanwhile, through setting and distributed checking modes of the target report, can further improve checking flexibility, efficiency and accuracy of the XBRL report, further can provide an accurate judgment basis for the XBRL report that needs to perform information disclosure or disclosure, so as to effectively improve true efficiency, authenticity and reliability of the information disclosure or disclosure of the XBRL report, and can effectively improve user experience of a source user of the XBRL report with information disclosure or disclosure requirement and a user who needs to learn information in the XBRL report.

In order to provide an XBRL report checking method suitable for a fund company, in one embodiment of the XBRL report checking device provided in the present application, if the source XBRL report is an XBRL report of the fund company, the target report is a hosted line report of a hosted bank corresponding to the fund company, and referring to fig. 10, the XBRL report checking device further specifically includes the following:

An XBRL report receiving module 40, configured to receive an XBRL report check request sent by a terminal of a foundation company, and read an XBRL report of the foundation company from the XBRL report check request.

And the XBRL report sending module 50 is configured to determine, according to the check result, whether an XBRL report of the fund company meets a preset disclosure requirement, and if yes, send the XBRL report of the fund company to a license party for information disclosure.

As can be seen from the above description, the XBRL report checking device provided by the embodiment of the present application can effectively implement flexible configuration of the tag of the XBRL report of the foundation company, and further can effectively improve the checking flexibility, efficiency and accuracy of the XBRL report of the foundation company, so as to provide an accurate judgment basis for the XBRL report of the foundation company that needs to perform information disclosure to the license, and effectively improve the authenticity, accuracy and reliability of the information disclosure or disclosure of the XBRL report of the foundation company to the license.

In order to enable a new custom tag to be added to the tag library when an unconfigured tag exists in a received XBRL report, in one embodiment of an XBRL report checking device provided in the present application, referring to fig. 11, the XBRL report checking device may further specifically include a supplementary configuration tag module 60, where the supplementary configuration tag module 60 is configured to perform the following:

And if the configuration information of at least one target tag reported by the source XBRL is judged to be not contained in the tag library, sending a configuration request aiming at the target tag which is not contained in the tag library to a user terminal corresponding to the tag library.

And receiving a user instruction which is sent by the user terminal based on the configuration request and is aimed at the tag library, wherein the user instruction contains attribute information of target tags which are not contained in the tag library.

As can be seen from the above description, the XBRL report checking device provided in the embodiment of the present application can further improve the applicability and flexibility of the custom tag library, and further can further improve the checking flexibility, efficiency and accuracy of the XBRL report.

In order to provide a specific way of providing the generation source XBRL report reconciliation data, in one embodiment of the XBRL report reconciliation apparatus provided herein, each of the tags in the tag library corresponds to at least four attributes: tag type attribute, context attribute, accuracy attribute and unit attribute, the first data generation module 10 in the XBRL report reconciliation apparatus is configured to perform:

And acquiring the values of the tag type attribute, the context attribute, the precision attribute and the unit attribute corresponding to each target tag from the source XBRL report.

As can be seen from the above description, the XBRL report checking device provided in the embodiment of the present application can effectively improve the reliability and effectiveness of application of source XBRL report checking data, and further can further improve the accuracy of XBRL report checking.

In order to provide a specific way of generating the target report, in one embodiment of the XBRL report checking device provided in the present application, referring to fig. 12, the second data generating module 20 of the XBRL report checking device specifically includes the following:

a managed line report generating unit 21, the managed line report generating unit 21 being configured to perform:

and acquiring the report type and the fund type of the XBRL report of the fund company.

And correspondingly searching to obtain prestored managed line system matching information based on the report type and the fund type of the XBRL report of the fund company.

From the above description, it can be seen that the XBRL report checking device provided in the embodiment of the present application can effectively improve the efficiency and accuracy of managed line report generation, and further can further improve the checking efficiency and accuracy of the XBRL report.

In order to provide a specific way to generate the target report collation data when the preset value exists, in one embodiment of the XBRL report collation apparatus provided in the present application, referring to fig. 13, the second data generation module 20 of the XBRL report collation apparatus further specifically comprises the following:

a target report collation data generation unit 22, the target report collation data generation unit 22 being for performing the following:

judging whether the attributes of all the target labels in the target report correspond to prestored set values, if so, determining the values of the corresponding attributes of all the target labels according to the set values of the attributes of all the target labels to the application.

As can be seen from the above description, the XBRL report checking device provided in the embodiment of the present application can effectively improve the reliability and accuracy of target report checking data generation, and further can further improve the checking reliability and accuracy of the XBRL report.

In order to provide a specific way of generating target report reconciliation data in the absence of a preset value, in one embodiment of the XBRL report reconciliation device provided in the present application, the target report reconciliation data generation unit 22 in the XBRL report reconciliation device is further adapted to perform:

As can be seen from the above description, the XBRL report checking device provided in the embodiments of the present application can further improve the reliability and accuracy of target report checking data generation, and further can further improve the checking reliability and accuracy of the XBRL report.

In order to provide a specific way of distributively checking data, in one embodiment of the XBRL report checking device provided in the present application, referring to fig. 14, the data checking module 30 of the XBRL report checking device specifically includes the following:

the distributed cluster execution unit 31 is configured to allocate each target tag to a plurality of independently operating service clusters, so that each service cluster performs distributed data checking on the source XBRL report and the target report, where each service cluster includes a plurality of servers, and each server is respectively configured to process a checking task corresponding to one target tag through a unique corresponding thread.

As can be seen from the above description, the XBRL report checking device provided in the embodiments of the present application can effectively improve the efficiency and reliability of distributed data checking of XBRL reports.

In order to provide a specific way to customize the tag library at any time, in one embodiment of the XBRL report checking device provided in the present application, referring to fig. 15, the XBRL report checking device further specifically includes a tag library customization module 70, where the tag library customization module 70 is configured to perform the following:

Receiving a user instruction aiming at the tag library, which is sent by the user terminal based on the configuration request, in real time, wherein the user instruction comprises: a new instruction of the attribute information of the tag which is not contained in the tag library, and/or a multiplexing instruction of the attribute information of the original tag which is already contained in the tag library.

And updating the tag library according to the user instruction.

As can be seen from the above description, the XBRL report checking device provided in the embodiment of the present application can further improve the flexibility and reliability of the application of the tag library, and further can effectively improve the accuracy and reliability of the distributed data checking of the XBRL report.

In order to further explain the scheme, the application example of the XBRL report checking device is used for realizing the concrete application example of the XBRL report checking method, the application example of the application method overcomes the problems that the traditional checking mode is single, XBRL label elements cannot be flexibly configured, the report checking efficiency is low, the accuracy is poor and the like, integrates the prior art, flexibly and dynamically configures and intelligently matches XBRL labels, efficiently queries dynamic SQL configured by the labels, and adopts a distributed architecture checking label, thereby improving the flexibility, the accuracy and the high efficiency of XBRL report checking.

Through the application example, the inherent tag and the custom tag can be multiplexed, and query SQL codes are assembled, so that XBRL report checking is efficiently realized by adopting a distributed architecture. Referring to fig. 16, an application example of the present application specifically includes the following:

step 1: and customizing the tag library. The tag library currently contains some inherent tag configuration, and also provides for customization of tags by business personnel. And selecting a report type, completing the configuration of the Tag label attribute, the Context attribute, the Decimal precision attribute and the UnitRef unit attribute, dynamically generating SQL according to the configuration by the system, and forming the configuration of a new custom Tag.

Step 2: and generating the XBRL report data of the fund company. The method comprises the steps of initializing a source XBRL report sent by a foundation company, analyzing all tags and storing the tags. Secondly, whether each label is configured or not is confirmed, if not, label elements are initialized, the step 1 is skipped, and label configuration is automatically recorded.

Step 3: managed line system report data is generated. And obtaining the report type and generating a report of the corresponding type of the managed line. And analyzing the dynamic SQL of the label configuration, inquiring the report data of the system, generating corresponding comparable system report data and storing the system report data.

Step 4: the XBRL report checks and outputs the result. And the distributed parallel computing is adopted, the label check of the report is processed by using a distributed cluster, and the cluster resource manager dynamically distributes tasks according to the load of each server, so that the computing and checking efficiency is improved.

Referring to fig. 17, the process of customizing a tag library includes the steps of selecting a report type, adding a tag element, generating a tag configuration, and the like.

Step 101: the type is selected. Report types include equity reports, partial temporary announcements, quarter reports, half-year and year reports, etc.

Step 102: and selecting a label configuration mode. Including both step 103 and step 110. Step 103, newly adding label element setting, mainly aiming at brand new personalized label customization, provides a mode of autonomously configuring each attribute of the label. Step 110 multiplexes the original tag, and the configuration can be completed by one-key duplication without repeated configuration for the case of the same configuration as the original tag.

Step 103: and (5) setting a new label. This includes the configuration of 4 attributes, the Tag attribute, the Context attribute, the Decimal precision attribute, and the UnitRef element attribute, steps 104-107.

Step 104: tag label attribute. Step 108 and step 109 are distinguished according to the classification of the tag. Tag attributes include Tag name, configuration of Tag type.

Step 105: context attribute. I.e. context-directed properties, describe the reporting period and reporting scenario of the described reporting information, helping to understand the business facts of XBRL data items. For example, the attribute of time is C_inst_yyyymmdd, and the attribute of the representative time interval is C_duration_yyyyymmdd-yyyymmdd.

Step 106: decimal property. That is, the precision attribute may be configured as an arbitrary integer for the numerical type, and the nondata type is fixed as INF.

Step 107: unitRef properties. I.e., the unit pointing property, specifies the unit of measure of the reporting item. For example, RMB, UDS, EUR, etc.

Step 108: element tags. I.e. a common element tag. Providing a user with the required conditions for tag generation based on data sources such as valuation tables, asset liability tables, profit tables, owner equity tables, asset distribution tables, general ledger details, equity tables, and the like for selection.

Step 109: a multiple tag. I.e. a tuple tag, is a set of related concepts comprising a plurality of values, one tuple member being unable to provide the required information, the completed information being provided by the group member. For example, the tuple "positive investment top five stock details" may contain the following constituent members: "stock code", "stock name", "stock number", "end of term fair value", "rank number", etc. The corresponding data source selection is consistent with the Element tag.

Step 110: the original label is multiplexed. For the newly configured tag, the tag configuration is consistent with the tag configuration in the existing tag library, and the configuration consistent with the selected tag can be generated by selecting the tag in the existing tag library and copying the tag by one key.

Step 111: a tag configuration is generated. Summarizing the configuration of the tag, converting the processing logic into SQL language to form attribute configuration of the tag.

Referring to fig. 18, the refinement process of generating managed line system report data is as follows:

step 201: an XBRL report is initialized. And receiving an XBRL report of the fund company, reading and analyzing the file through an API interface, and storing and initializing the report type and the fund type. Report types include equity reports, partial temporary announcements, quarter reports, half-year and year reports, etc. The types of funds are classified as monetary funds, non-monetary funds.

Step 202: a determination is made as to whether the tag in the XBRL report is configured, if so, step 203 is skipped, and if not, step 204 is skipped.

Step 203: XBRL report collation data is generated. The VALUEs of the corresponding TAGs in the XBRL report are obtained to form data of TAG_KEY and TAG_VALUE. Where TAG_KEY is a TAG element containing 4 attributes of the TAG and TAG_VALUE is the content VALUE of the corresponding TAG.

Step 204: and (5) complement tag element configuration. Intelligent matching and automatic generation of label basic configuration, mail sending service prompt supplementary recording or confirmation.

Referring to fig. 19, the refinement process for generating managed line system report data in the present application example specifically includes the following:

step 301: managed row report data is generated. And the system generates corresponding managed line report data according to the report type and the fund type of the XBRL and system logic, and provides a data source for the fetch of the subsequent dynamic SQL.

Step 302: and judging whether the corresponding label has a preset value, if so, jumping to step 304, and if not, jumping to step 305.

Step 303: query dynamic SQL. And acquiring dynamic SQL according to the label configuration, and executing to acquire corresponding values.

Step 304: and acquiring the numerical value of the label according to the preset value of the label set by the business foreground parameter.

Step 305: managed row collation data is generated. The results of steps 303 and 304 are combined with the TAG into TAG_KEY and TAG_VALUE data.

Referring to the distributed architecture diagram shown in fig. 20, the distributed collation process provided by the application example includes:

step 401: overall task. Initializing a checking task of the XBRL report, acquiring the fund company report data and the managed line report data required by the task, subdividing the report task according to the report type, and forming each subtask Z1 to subtask Z3 of the step 402.

Step 402: subtask Z1 through subtask Z3. The subtasks are assigned to different server processes of the cluster, the subtasks comprising a plurality of labels, each label assigned a thread processing check, forming step 403.

Step 403: a thread. Each subtask corresponds to thread 1 through thread 3, respectively. Each server of the cluster, i.e. each thread runs independently, checking a single tag.

Referring to fig. 21, the refinement flow of the XBRL collation and output result in the present application example corresponds to the specific task of step 402, and specifically includes the following contents:

step 501: and obtaining check data results of the XBRL report of the foundation company and the managed line system report data.

Step 502: and judging whether the checked label is a key element for checking. If not, step 503 is skipped. If so, step 504 or step 505 is skipped.

Step 503: the tag element is not checked. If the checked tag is not the check key element, the tag element is not checked, and the default is the check coincidence.

Step 504: element tag collation. The collated tag is a collation key element, and collation data is required. For the Element Tag, matching and finding corresponding values according to the Tag attribute name, the Contex context attribute, the Decimal precision attribute and the UnitRef unit attribute, judging whether the data results of the two parties are consistent, and if so, checking the Tag Element to be consistent. If the collation results are inconsistent, the tag element collates inconsistent.

Step 505: the Tuple tag checks. For the Tuple tag, the data of each constituent member in the Tuple is checked by sequence number according to the number of loop layers of the Tuple tag.

Step 506: summarizing all labels of the XBRL report, checking the XBRL report to be consistent if all labels are checked to be consistent, and checking the XBRL report to be inconsistent if all labels are checked to be consistent.

As can be seen from the above description, the XBRL report checking method provided by the application example of the application flexibly and dynamically configures and intelligently matches XBRL labels, the query SQL codes are assembled, the distributed architecture is adopted, the checking of the report labels is distributed on a plurality of servers to balance the calculation load, and simultaneously, the multithreading processing is started, so that the XBRL report checking is realized efficiently.

In order to solve the problem of poor expandability and low XBRL report verification efficiency and accuracy caused by serial verification modes of the existing XBRL report verification from the hardware level, the present application provides an embodiment of an electronic device for implementing all or part of the content in the XBRL report verification method, where the electronic device specifically includes the following contents:

fig. 22 is a schematic block diagram of a system configuration of the electronic device 9600 of the embodiment of the present application. As shown in fig. 22, the electronic device 9600 may include a central processor 9100 and a memory 9140; the memory 9140 is coupled to the central processor 9100. Notably, this fig. 22 is exemplary; other types of structures may also be used in addition to or in place of the structures to implement telecommunications functions or other functions.

In one embodiment, the XBRL report reconciliation functionality can be integrated into the central processor. Wherein the central processor may be configured to control:

In step 200, if the preset tag library includes configuration information of each target tag of the source XBRL report, the value of each attribute corresponding to each target tag, that is, the attribute value, is searched in the source XBRL report, and the corresponding relationship between each attribute corresponding to each target tag and each attribute value is stored, so as to form the source XBRL report verification data.

As can be seen from the foregoing description, the electronic device provided in the embodiment of the present application can effectively implement flexible configuration of the tag of the XBRL report through the custom tag library, and can effectively improve accuracy, reliability and timeliness of tag setting, so as to effectively improve verification efficiency and verification accuracy of the XBRL report, and meanwhile, through setting and distributed verification modes of the target report, can further improve verification flexibility, efficiency and accuracy of the XBRL report, so as to provide an accurate judgment basis for the XBRL report that needs to perform information disclosure or disclosure, so as to effectively improve true efficiency, authenticity and reliability of the information disclosure or disclosure of the XBRL report, and can effectively improve user experience of a source user of the XBRL report with information disclosure or disclosure requirements and a user who needs to learn information in the XBRL report.

In another embodiment, the XBRL report reconciliation device can be configured separately from central processor 9100, e.g., the XBRL report reconciliation device can be configured as a chip connected to central processor 9100, with the XBRL report reconciliation function being implemented by control of the central processor.

As shown in fig. 22, the electronic device 9600 may further include: a communication module 9110, an input unit 9122, an audio processor 9130, a display 9160, and a power supply 9170. It is noted that the electronic device 9600 need not include all of the components shown in fig. 22; in addition, the electronic device 9600 may further include components not shown in fig. 22, and reference may be made to the related art.

As shown in fig. 22, the central processor 9100, sometimes also referred to as a controller or operational control, may include a microprocessor or other processor device and/or logic device, which central processor 9100 receives inputs and controls the operation of the various components of the electronic device 9600.

The memory 9140 may be, for example, one or more of a buffer, a flash memory, a hard drive, a removable media, a volatile memory, a non-volatile memory, or other suitable device. The information about failure may be stored, and a program for executing the information may be stored. And the central processor 9100 can execute the program stored in the memory 9140 to realize information storage or processing, and the like.

The input unit 9122 provides input to the central processor 9100. The input unit 9122 is, for example, a key or a touch input device. The power supply 9170 is used to provide power to the electronic device 9600. The display 9160 is used for displaying display objects such as images and characters. The display may be, for example, but not limited to, an LCD display.

The memory 9140 may be a solid state memory such as Read Only Memory (ROM), random Access Memory (RAM), SIM card, etc. But also a memory which holds information even when powered down, can be selectively erased and provided with further data, an example of which is sometimes referred to as EPROM or the like. The memory 9140 may also be some other type of device. The memory 9140 includes a buffer memory 9141 (sometimes referred to as a buffer). The memory 9140 may include an application/function storage portion 9142, the application/function storage portion 9142 storing application programs and function programs or a flow for executing operations of the electronic device 9600 by the central processor 9100.

The memory 9140 may also include a data store 9143, the data store 9143 for storing data, such as contacts, digital data, pictures, sounds, and/or any other data used by an electronic device. The driver storage portion 9144 of the memory 9140 may include various drivers of the electronic device for communication functions and/or for performing other functions of the electronic device (e.g., messaging applications, address book applications, etc.).

The communication module 9110 is a transmitter/receiver 9110 that transmits and receives signals via an antenna 9111. A communication module (transmitter/receiver) 9110 is coupled to the central processor 9100 to provide input signals and receive output signals, as in the case of conventional mobile communication terminals.

Based on different communication technologies, a plurality of communication modules 9110, such as a cellular network module, a bluetooth module, and/or a wireless local area network module, etc., may be provided in the same electronic device. The communication module (transmitter/receiver) 9110 is also coupled to a speaker 9131 and a microphone 9132 via an audio processor 9130 to provide audio output via the speaker 9131 and to receive audio input from the microphone 9132 to implement usual telecommunications functions. The audio processor 9130 can include any suitable buffers, decoders, amplifiers and so forth. In addition, the audio processor 9130 is also coupled to the central processor 9100 so that sound can be recorded locally through the microphone 9132 and sound stored locally can be played through the speaker 9131.

The embodiments of the present application also provide a computer-readable storage medium capable of implementing all the steps in the XBRL report collation method in the above embodiments, the computer-readable storage medium storing thereon a computer program which, when executed by a processor, implements all the steps of the XBRL report collation method in which the execution subject in the above embodiments is a server or a client, for example, the processor implements the following steps when executing the computer program:

As can be seen from the foregoing description, the computer readable storage medium provided in the embodiments of the present application can effectively implement flexible configuration of the labels of the XBRL report through the custom label library, and can effectively improve accuracy, reliability and timeliness of label setting, so as to effectively improve verification efficiency and verification accuracy of the XBRL report, and meanwhile, through setting and distributed verification modes of the target report, can further improve verification flexibility, efficiency and accuracy of the XBRL report, further can provide an accurate judgment basis for the XBRL report that needs to perform information disclosure or disclosure, so as to effectively improve true efficiency, authenticity and reliability of information disclosure or disclosure of the XBRL report, and can effectively improve user experience of a source user of the XBRL report with information disclosure or disclosure requirements and a user who needs to learn information in the XBRL report.

It will be apparent to those skilled in the art that embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (devices), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The principles and embodiments of the present invention have been described in detail with reference to specific examples, which are provided to facilitate understanding of the method and core ideas of the present invention; meanwhile, as those skilled in the art will have variations in the specific embodiments and application scope in accordance with the ideas of the present invention, the present description should not be construed as limiting the present invention in view of the above.

Claims

1. An XBRL report reconciling method comprising:

2. The XBRL report reconciliation method of claim 1, where if the source XBRL report is an XBRL report for a fund company, the target report is a hosted line report for a hosted bank corresponding to the fund company;

3. The XBRL report checking method of claim 1, further comprising:

and adding the attribute information of the target tag in the user instruction into the tag library to form configuration information of the target tag in the tag library.

4. The XBRL report reconciling method of claim 1, where each of the labels in the pool of labels corresponds to at least four attributes: tag type attributes, context attributes, precision attributes, and unit attributes;

5. The XBRL report reconciling method of claim 2, where generating the target report that is the same as both the type of source XBRL report and the configuration information of the corresponding target label comprises:

6. The XBRL report reconciling method of claim 1, wherein the obtaining the target report reconciling data corresponding to the target report comprises:

7. The XBRL report reconciling method of claim 6, wherein the obtaining the target report reconciling data for the target report further comprises:

8. The XBRL report reconciling method of claim 1, where the distributed data reconciling of the source XBRL report and the target report based on the configuration information for each of the target tags comprises:

9. A method of XBRL report reconciling in accordance with claim 3, further comprising:

and updating the tag library according to the user instruction.

10. An XBRL report reconciling apparatus comprising:

11. The XBRL report reconciling apparatus of claim 10, where if the source XBRL report is an XBRL report for a fund company, the target report is a hosted line report for a hosted bank corresponding to the fund company;

correspondingly, the XBRL report checking device further includes:

12. The XBRL report checking apparatus of claim 10, further comprising: a supplemental configuration tag module for performing the following:

13. The XBRL report checking apparatus of claim 10, where each of the labels in the library of labels corresponds to at least four attributes: tag type attributes, context attributes, precision attributes, and unit attributes;

14. The XBRL report reconciling apparatus of claim 11, where the second data generation module comprises: a managed line report generation unit for performing:

15. The XBRL report reconciling apparatus of claim 10, where the second data generation module comprises: a target report collation data generation unit for executing the following:

16. The XBRL report reconciling apparatus of claim 15, wherein the targeted report reconciling data generation unit is further configured to:

17. The XBRL report checking apparatus of claim 10, where the data checking module comprises:

18. The XBRL report checking apparatus of claim 12, further comprising: the tag library custom module is used for executing the following contents:

and updating the tag library according to the user instruction.

19. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the XBRL report reconciling method of any one of claims 1 to 9 when the program is executed by the processor.

20. A computer readable storage medium having stored thereon a computer program, which when executed by a processor implements the XBRL report reconciliation method of any one of claims 1 to 9.