This post is the second post in a series about how to build effective integrations between a DW/BI solution and an XBRL based reporting solution such as CRD IV or Solvency II. The previous post can be found here. In this post we describe how you can make your integration with your DW/BI solution more effective.
Knowing that there are great similarities between the XBRL structure and the classical dimensional model used in most Data Warehouse / Business Intelligence (DW/BI) solutions the possibility of reusing the DW design for your CRD IV/Solvency II reporting should be something to consider. Assuming that you have a DW/BI solution in place you would want to make sure that you have
- the same numbers in your internal BI reports as you have in your external reporting
- an effective and cost effective integration with your external reporting solution.
In order to make sure that you have the same numbers in your external and internal reporting you need to make sure that your dimensional model supports both types of reporting. In this instance you can consider the external reporting solution (or your XBRL vendor) as just an other reporting solution. many organizations use for example Excel for analytics, Reporting services for static reports and Qlik or Tableau for graphical ineractive reports. In this scenario your XBRL vendor would be one more reporting solution. In this way we base all the reports on the same values using the same data model and we should confident that we also get the same numbers.
How then do we get an efficient integration from the DW to the XBRL provider? One way of doing this is to basically export “fact tables” using the XBRL tags from your Dimension tables as keys/references. This should allow your XBRL solution map incoming numbers to it’s own internal data model and after that the templates should be populated automatically. What’s the down side? Well, you need to define what goes where. That is, how liquid are your assets, where are your exposures and so on. What’s the upside? That you should do this anyway and after the initial cost of defining and developing the integrations you will have a reporting solution that is faster, more reliable and in synch with your inernal reporting. Another advantage is that this strategy puts the power and the bargaining chips in your hand by decoupling your data and your design from your XBRL vendor.
What if you don’t have a BI solution yet? Can your CRD IV/Solvency II reporting be used to help you define your DW/BI solution? Can you have one solution for both? Ofcourse!
Dirept can help you define and design your DW architecture and we can even host your DW/BI solution and make sure that it is integrated properly with our XBRL generation.
Contact us at firstname.lastname@example.org.