New Features
Arelle validation of ESEF report package with less notifications
Feature ID: FPS-8260
More validations have been added to ESEF Reporting Tool, which now reveals problems in the report earlier for the user. The report generation has been updated also to better conform with the non-mandatory rules listed in ESEF Reporting Manual. In interpretation of the non-mandatory recommendations Arelle application (referred to by XBRL Finland) has also been used as reference.
According to ESMA, there must not be any elements in the extension taxonomy which are not used to mark up the facts on the XHTML report. It is easy to end up in this situation for example by hiding columns or rows on entry sheets or commenting rows on Mapping sheet. For this reason, there now is a warning message in log to reveal this issue. The identifier of the error is "UsableConceptsNotAppliedByTaggedFacts".
The generation of technical linkrole "[999999] Line items not dimensionally qualified" has been changed so that XBRL application Arelle no longer lists messages on it in the log. The changed logic prioritizes the examples in ESEF Conformance Suite over ESEF Reporting Manual.
Furthermore, ESMA recommends the use of different label roles for the elements in the extension taxonomy. A column named "PreferredLabel" should be inserted after the Lang=xx columns on the Extension sheet of existing ESEF workbooks. The preferred label should be used to separate elements describing opening and closing balance lines on the report (period start and period end labels), elements describing total lines (total label) etc. Other possible label roles currently available are net, negated, negated terse, negated total, and documentation labels. By default, all defined labels in Lang=xx columns are saved as terse labels and they are now defined as such also in the presentation hierarchy, which means that XBRL consumption software will show the presentation trees of the report with the labels reporters use themselves.
Another recommendation of ESMA is that all the primary financial statements should be separated into their own linkroles (extended link roles). This has now been made possible and it requires that a new row with ItemType "Linkrole" will be added before the start of each financial statement on the Extension sheet and before the list of mandatory elements. Earlier it was only possible to separate statements consisting of an XBRL table into their own linkrole in ESEF reports and all the other statements were represented in the same linkrole. The only statement having an XBRL table in ESEF reports for financial years 2020 and 2021 is the statement of changes in equity. As a result, each linkrole will have its separate presentation and calculation hierarchy.
Third ESEF Reporting Manual recommendation has been also implemented and it concerns the names of the report package and the files inside it. The format for the names is prefix of the extension taxonomy, underscore and the date (eg. "dg_2020-12-31").
Additionally, defining rows to XBRL tables has been simplified. Earlier a row of an XBRL table was required to be defined on two rows in the Extension sheet: first to define it (ItemType, Balance, Anchoring, etc.) and the second time to actually link it to the Table element using the ItemType "LineItem". Now, this should be done on one row only and ItemType "LineItem" has been deprecated. As a result, the presentation hierarchy will also be simplified as earlier the XBRL table rows were presented in the presentation tree two times as well.
Power BI sample reports
Feature ID: FPS-8259
A set of example reports exists for Power BI reports. These reports can be used for faster implementation of analytical report set.
This is a feature that requires a separate license. Type of license depends on whether the customer has a valid Power BI license or not.
If you want to explore the demo reports, please contact Clausion sales or product management.
Input template locked if another user opens template with the same selections (year, unit, data type)
Feature ID: FPS-7938
It is restricted for two users to open the same input template at the same time. When the second user tries to open the same template with the same dimension combination (year, unit, data type and possible document series/document series numbre), the screen will be locked, and a validation message opens. A warning opens to the second user when a different input template is opened but the dimension combination is the same.
Presentation property data type usage and default templates to use it with conditional formatting
Feature ID: FPS-7885
In addition to the account ID and name, the datatypeusage of the account can now be selected as visible in the definition column. This enables showing, whether the account is of sum level or input level from the selected data type's point of view.
This possibility is now utilized in formatting on all FPM as well as content package default templates, in which the account rows are formed by generating according to the account hierarchy. With conditional formatting definition, the font of the sum accounts is shown bolded, and thus they are differentiated from the input levels. In content package templates the conditional formatting was previously based on last digits of the account code.
Data retrieval from single document series number with the DRDATA function
Feature ID: FPS-5889
Data retrieval with the Clausion Dynamic Reporting for FPM Data function is now possible from single document series number. It is also possible to restrict the search with several document series numbers and combinations of document series and single document series numbers.
FPM Web Client: Home page (Dashboard)
Feature ID: FPS-5766
A home page has been added to the FPM Web Client. When the user enters the Web Client, the home page opens. By clicking the Clausion logo on the top left corner of the screen the user returns on the home page from any other page. The home page provides a general overview and introduction to the Web Client, FPM version and environment information, links to user guidance, Clausion Customer Support, end user licence agreement, and other useful information.
FPM Web Client: Importing data from Excel
Feature ID: FPS-2985
Importing of data from Microsoft Excel has been implemented to the FPM Web Client. The functionality works in the same way as with the FPM Desktop Client.
Other Improvements
Multiple Application Servers: need to restart the servers
Feature ID: FPS-7203
Before the changes made by administrative user take effect to all users, restarting the server/service has been required in environments were multiple application servers are used. This scenario is typical in Clausion Cloud environment (admin client and web client use separated servers)
In the following cases restart is no longer required:
* Saving data in web client to newly added unit
* Saving data in case of expired and reactivated user account
* Retrieving the following in DR after update or adding by admin (related DR function):
* Account name (DRAccountName)
* DC code of account (DRAccountDCCode)
* Currency rate (DRCurrencyRate)
* Data type name (DRDatatypeName)
* Unit name (DRUnitName)
* Unit currency (DRUnitCurrency) (Note: changing unit currency not even possible in desktop client)
Note also cases that are not confirmed/likely still require restart:
* Unlocking periods (FPS-6789)
* Adding year
* Adding period
* Adding data type
* Adding new dimension, dimension data type connection or dimension count/code
Corrected Known Issues
{name_en}
Issue ID: FPS-7586
Earlier, even if the xml had column width=0, the columns were visible if the columns were grouped in the xlsx file. The issue occurred only in FPM Web client. Now the issue has been fixes, and the column is no more visible.
{name_en}
Issue ID: FPS-7149
Earlier in the web client when data was inputted to the internal account on account level, when it should be inputted only by drill down, rows were saved even when there is no counter unit. The problem has been fixed now.
{name_en}
Issue ID: FPS-6520
The performance issue with DR formulas starting with DRACC has been corrected, so the problem has been solved.
{name_en}
Issue ID: FPS-6472
Internal data transfer previously checked unit rights from hierarchy 1, even if another hierarchy was selected in transfer selections. The error occurred, if counter unit restrictions were in use (CODIM00RIGHTS=TRUE). Now the unit rights are checked from the selected DIM00 hierarchy.
{name_en}
Issue ID: FPS-5556
Previously, the values were pasted to Excel (etc.) as text if number formatting contained a thousand separator (space character in Finnish region). Hence the values could not automatically be summed up. The user had to remove the space used as a thousand separator before the value was handled as number. The problem has now been fixed in the web client.
Known Issues
Issue ID | Summary | Description |
|---|---|---|
FPS-9070 | FPM Web Client does not give error message on entering data to internal account without using drilldown | FPM web client does not give any error or warning message, when entering the data to account level for internal account, that can be inputted only using drill-down functionality (with counter unit information). Also saving functions gives no message, and the data does not get saved. |
FPS-8265 | FPM Web Client: Save to file option not working after drilldown by rows | Incorrect behavior of "Save to file" option after row drill down from report sheet. |
FPS-7577 | FPM Desktop Client: Import from Excel fails if template includes several types of data sheets | Data import from Excel file to a predefined input sheet fails if the template includes also sheet of "retrieve from data" type (as other entries sheet). Problem appears only in desktop client, not web client. |
FPS-5046 | FPM Web Client: Taxonomy import fails when network (UNC) path is given in the application server (XBRLTAXONOMY_PATH) | Importing the taxonomy works for all browsers, if the taxonomy storage folder (XBRLTAXONOMY_PATH) has been defined to the application server. With Firefox, the taxonomy import fails if trying to import to some other path (network UNC path). Clausion Cloud: taxonomy import succeeds, if uploaded to virtual machine (VM address given in the Parameters input sheet). Should be Storage instead. |
FPS-4110 | Clausion DR for FPM: DR tab is not added in certain cases | The configuration files have impact on addition of the DR tab. Special characters are not allowed in the file names. |
FPS-3803 | Unicode support for Cyrillic characters missing from Clausion FPM | Non-latin characters are not allowed in comment and input fields. They show incorrectly in FPM. |
FPS-3200 | FPM Web Client in Cloud: Several user sessions created and not removed when closing browser | Several user sessions in the web client in Cloud are removed when closing the browser. Previously, the sessions were not removed. |