Requirements for severity indicator on assertions 1.0

Requirements Document 30 September 2015

Copyright © 2014, 2015 XBRL International Inc., All Rights Reserved.

This version:
<http://www.xbrl.org/REQ/severity-indicator-assertions/REQ-2015-09-30/severity-indicator-assertions-2015-09-30.html>
Editors:
Roland Hommes, SBR-NL <roland@rhocon.nl>
Paul Warren, XBRL International Inc. <pdw@xbrl.org>

Status

Circulation of this Requirements Document is unrestricted. Other documents may supersede this document.

Abstract

Formula assertions can have only one of two outcomes: true or false. From the business perspective there is however the need to place a nuance on the outcome. The result of an assertion can be either 'as expected', 'in error' or 'a warning'. This requirement describes the required nuance.

Table of Contents

1 Introduction
2 Use Cases
2.1 SBR-NL
2.2 EBA Taxonomy
3 Requirements
3.1 Severities
4 Out of scope requirements

Appendices

A References
B Intellectual property status (non-normative)
C Acknowledgements (non-normative)
D Document history
E Errata corrections in this document


1 Introduction

All formula assertions specifications (value-assertions [VALUE ASSERTIONS], existence-assertions [EXISTENCE ASSERTIONS] and consistency-assertions [CONSISTENCY ASSERTIONS]) define a standard XML-based syntax for validations on XBRL business reports. The technical nature of an assertion is that the result is either true or false. These specifications have deliberately not prescribed whether true or false is a situation that should be recognized as an error. From a business perspective more results from an assertion can be expected. Besides the result being 'OK' or 'error', the severity of the 'error' situation needs to be expressed. The requirement for placing this severity indicator does NOT prescribe the reason or the number of nuances that can be placed on the 'erroneous' situation, all that is required is that a nuance can be made.

A complementary requirement to the severity placed on the outcome of the assertions is that each severity can be equipped with an appropriate message text. These messages are similar to the existing messages specification [GENERIC MESSAGES] and can use aspects of the assertion in their content.

No requirement is made on the consequences of the severity reported. It is left to the software or user evaluating the results if any sorting or filtering is in order. It IS required however, that the severity is part of the reported message to prevent assertion creators to structure the message content with a structural severity level aspect.

2 Use Cases

2.1 SBR-NL

Tax filings have a level of rules that prevents users to file their report. This has legal consequences since not filing in time causes fines and other problems for the reporter. In general errors of this nature tend to be syntax oriented or completeness oriented. For other rules the severity is less. Filing is allowed but tax internal reviewing is needed to assess if the situation is in error or still a possibility. These rules include rounding problems, incorrect summations or situations that on first glance contradict. These situations should not prohibit the user from filing, but it would be better if these situations are detected and brought to the attention of the reporter in a way that is best described as 'are you sure you want to file this situation?'.

2.2 EBA Taxonomy

The Dutch central bank (DNB) is using the European Banking Authority (EBA) taxonomy to collect reports from commercial banks. EBA has defined approximately 1800 business rules as assertions. The results of these assertions is always an 'error' that primes the supervisor to inspect the filing. DNB is however planning on creating complementary assertions on this taxonomy. These complementary rules MUST NOT prevent the reporter to file with DNB since the instance can be 'EBA legitimate'. Applying a result that places a 'warning' on the outcome of the DNB specific assertions allows both reporter and DNB to take appropriate action without disturbing the filing process to EBA.

3 Requirements

3.1 Severities

  • A severity may be associated with an assertion in order to indicate the severity of a failure to satisfy that assertion.
  • Severities should be classified into three types: "error" indicating a genuine error in the filing, "warning" indicating an issue that may indicate a problem with a filing, and "ok", indicating an issue that is purely for informational purposes. It is expected that "error" would typically lead to rejection of a filing, whereas other severities would not.
  • In order to allow processors to deal with all assertion failures in a consistent manner, a default severity should be prescribe for those assertions that are not explicitly given a severity.

4 Out of scope requirements

The following requirements were considered, but deemed to be out of scope.

Appendix A References

CONSISTENCY ASSERTIONS
XBRL International Inc.. "XBRL Value Assertions 1.0"
Victor Morilla
, and Geoff Shuetrim.
(See http://www.xbrl.org/Specification/consistencyAssertions/PR-2009-03-31/consistencyAssertions-PR-2009-03-31.html)
EXISTENCE ASSERTIONS
XBRL International Inc.. "Existence Assertions 1.0"
Victor Morilla
, and Geoff Shuetrim.
(See http://www.xbrl.org/specification/existenceassertions/rec-2009-06-22/existenceassertions-rec-2009-06-22.html)
GENERIC MESSAGES
XBRL International Inc.. "Generic Messages 1.0"
Masatomo Goto
, Victor Morilla, Takahide Muramoto, Hitoshi Okumura, Herm Fischer, and Andy Harris.
(See http://www.xbrl.org/specification/genericmessages/rec-2011-10-24/genericmessages-rec-2011-10-24.html)
VALUE ASSERTIONS
XBRL International Inc.. "Value Assertions 1.0"
Victor Morilla
, and Geoff Shuetrim.
(See http://www.xbrl.org/Specification/valueAssertions/PR-2009-03-31/valueAssertions-PR-2009-03-31.html)

Appendix B Intellectual property status (non-normative)

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to XBRL International or XBRL organizations, except as required to translate it into languages other than English. Members of XBRL International agree to grant certain licenses under the XBRL International Intellectual Property Policy (www.xbrl.org/legal).

This document and the information contained herein is provided on an "AS IS" basis and XBRL INTERNATIONAL DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

The attention of users of this document is directed to the possibility that compliance with or adoption of XBRL International specifications may require use of an invention covered by patent rights. XBRL International shall not be responsible for identifying patents for which a license may be required by any XBRL International specification, or for conducting legal inquiries into the legal validity or scope of those patents that are brought to its attention. XBRL International specifications are prospective and advisory only. Prospective users are responsible for protecting themselves against liability for infringement of patents. XBRL International takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Members of XBRL International agree to grant certain licenses under the XBRL International Intellectual Property Policy (www.xbrl.org/legal).

Appendix C Acknowledgements (non-normative)

This document could not have been written without the contributions of many people.

Appendix D Document history

DateAuthorDetails
20 February 2014Roland Hommes

First draft created

23 September 2015Paul Warren

Updated to reflect agreed reduction in scope.

Appendix E Errata corrections in this document

This appendix contains a list of the errata that have been incorporated into this document. This represents all those errata corrections that have been approved by the XBRL International Formula Working Group up to and including 30 September 2015. Hyperlinks to relevant e-mail threads may only be followed by those who have access to the relevant mailing lists. Access to internal XBRL mailing lists is restricted to members of XBRL International Inc.

No errata have been incorporated into this document.