by Thomas Howells | Apr 21, 2022 | Digital Future Reporting, Extensibility, Inline XBRL, Interactive Data, Products, Quality, Solutions, Taxonomy, True North
CoreFiling have been helping standards setters write taxonomies for more than a decade. Taxonomies are increasingly important as part of digital standards and are increasingly seen as a core part of the standard itself. We recently completed a project with a standards...
by Tim Moore | Nov 18, 2021 | Artificial Intelligence, Digital Future Reporting, Fintech, Quality, Solutions, Taxonomy, XBRL
Environment, Social and Governance (ESG) issues are of increasing interest to regulators. With the COP26 climate change conference being held in Glasgow, the Financial Conduct Authority chose sustainability as the theme for their 2021 TechSprint. As a software...
by Ben Russell | Oct 7, 2021 | Digital Future Reporting, Products, Quality, Solutions, Taxonomy
It is becoming common for data collection programmes to release versions of taxonomies with an expectation that external stakeholders will provide feedback on issues based on their own testing. Subsequent work and new releases allow the data collector to reach the...
by Chris Mills | Sep 3, 2021 | Products, Quality, Solutions, XBRL
New taxonomies are published by regulators for a variety of reasons, to fix issues, introduce new report types or to apply year-on-year changes. CoreFiling customers are used to being given access to new versions of reports well before they are required, but how do we...
by Katherine Haigh | Jul 27, 2021 | Quality, Solutions, Taxonomy, XBRL
In this age of digital reporting, hundreds of XBRL taxonomies are published every year. Our analysis at CoreFiling shows that there are a few common mistakes that repeatedly crop up in such taxonomies. These issues can limit their usefulness, slow down implementation...
by Philip Allen | May 10, 2021 | Quality, Solutions
In my previous blogs, I have talked about how the iXBRL document validation process consists of a number of steps, like a ladder. If the validation process returns a failure at one step, it must stop processing immediately. It must NOT move on to the next step. Why?...
