DICO’s Implementation of XBRL - PowerPoint PPT Presentation

dico s implementation of xbrl n.
Skip this Video
Loading SlideShow in 5 Seconds..
DICO’s Implementation of XBRL PowerPoint Presentation
Download Presentation
DICO’s Implementation of XBRL

play fullscreen
1 / 24
DICO’s Implementation of XBRL
Download Presentation
Download Presentation

DICO’s Implementation of XBRL

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. DICO’s Implementation of XBRL WEB Based Interactive Regulatory Filings XBRL Canada Conference Oct. 17, 2013 Bill Foster Vice President

  2. Presentation Overview • Who is DICO? • Profile of regulated Institutions • Monitoring & Statistics before XBRL • Decision to go to XBRL • Monitoring & Statistics with XBRL • System Components • Lessons learned

  3. Who is DICO? • Agent of Government of Ontario • Mandate: protect depositors of Ontario Credit Unions and CaissesPopulaires • Solvency Regulator • Deposit Insurer ($100,000) • Statistics gatherer • French Language Services Act (everything must be bilingual)

  4. Ontario Sector Profile by Size

  5. Profile of Regulated Institutions 5

  6. Monitoring & Statistics (before XBRL) • Paper based (1980’s to late 90’s) • Over 950 reporting entities in late 80’s • Information quarterly due to high volumes • Up to 300 fields of data – “key punched” by DICO • Data accuracy and data cleansing – a significant problem • Poor timeliness of report information • Limited reports - pre-programmed by IT Dept. • Limited ability to directly query data

  7. Monitoring & Statistics (before XBRL) • Electronic – late 1990’s - 2010 • distributed in-house developed visual basic application – filed from dedicated computer at reporting entity (Quarterly, Monthly and Annually) • Up to 300 fields of data • Ability to upload financial data from banking system • 100% data accuracy – extensive validation routine a pre-condition to filing) • Dynamic reporting with user defined peer groups

  8. WHY XBRL? Existing system lacked flexibility and scalability needed to address: • Diversity in size and complexity of institutions • Significant ongoing consolidation of institutions • Monitoring of new business products and activities

  9. THE XBRL PROMISE • Scalability / Flexibility • Thin client – work on all operating systems (including dial-up internet access) • Easily change filing frequency & specs at “entity” and “forms” level (one size does not fit all) • Accommodate DICO’s legacy systems • Do everything existing system does and more!

  10. MAJOR FUNCTIONS • Gather Information • Process and Store Information • Report Information • Support SQL / Lotus Notes legacy system

  11. DICO’s Current XBRL System • DICO custom taxonomy • Enterprise Application Server - Notes based user authentication tied with XBRL Reporting Window specifications • Web forms generator tags and verifies data at Forms level • XBRL Processing engine (data validation) • Reporting - DICO’s Legacy System

  12. INFORMATION GATHERING XBRL Reporting Window • Secure log-in / authentication utilizing DICO’s existing Lotus Notes based Authorized Contacts database • Institution specific “Reporting Window” • Reporting period • Input form(s) specifications • 1st level data fill-in and verification

  13. INFORMATION GATHERING (continued) XBRL Web Based Forms System • Tags over 700 fields of data – filed monthly (or quarterly) and annually from any computer - individual user authentication • Ability to upload financial data from banking system • Scalable through DICO entity specific specifications and “trigger” fields in forms (Capability in place but not currently utilized)

  14. INFORMATION GATHERING (continued) Data Accuracy 100% accurate – two stage electronic verification (form level and final validation) - a pre-condition to filing. • 573 fields have a rule re required content • 121 fields are auto totals or sub totals • 12 fields are auto fill from external “lookup” • Validation: 263 caution & 73 error rules

  15. INFORMATION PROCESSING XPE Processing Engine. XBRL Tagged information is passed from the Web Based Forms System to the XPE Processing Engine. • Data is validated before filing can be completed • Completed filing is “shredded” and passed to Oracle XDA (proprietary) database • Data posted to XDA is then also posted to legacy SQL database.

  16. MID PROJECT CHANGE IN DIRECTION The original project specifications called for the development of a reporting module by UBMmatrix, the project contractor. Meanwhile, SQL Power, (the project sub- contractor) developed “XBRL Analytics” a drag and drop report writer / query tool. DICO agreed to change the project specs to utilize the XBRL Analytics reporting capabilities.

  17. MID PROJECT CHANGE IN DIRECTION (Continued) Because XBRL Analytics is driven off a different database than the Oracle XDA, we are currently loading both the XDA and the XBRL Analytics databases from the XPE processing engine. We are running parallel data transfers to our legacy SQL database to verify the accuracy of the data load into the XBRL Analytics database.

  18. MID PROJECT CHANGE IN DIRECTION (Continued) User testing: compare XBRL Analytics reports against our legacy SQL / Lotus Notes reports Legacy individual and user designated peer group financial and performance reports continue to be available to DICO and its constituents on demand over DICO’s secure web site Once user testing of the parallel databases is complete, we will commence user testing of the various XBRL Analytics reports

  19. REPORTING INFORMATION NEXT STEPS • Legacy reports to be replaced by updated reports based on XBRL database • Longer term: DICO will migrate away from reliance on its SQL database and COGNOS by redirecting the Lotus Notes Corporate Information System data calls to the XBRL Analytics database.


  21. LESSONS LEARNED REALIZING UPON THE PROMISE OF XBRL IS FAR MORE DIFFICULT / COMPLICATED THAN WE WERE FIRST LED TO BELIEVE • Taxonomy: No suitable standard for our requirements – FinrepCorrep > DICO • Complex validation taxonomy requires very complicated hard coding • Implementation of XBRL for regulatory use is still largely uncharted territory • Il ne parle pas français

  22. LESSONS LEARNED • Work closely throughout the project with your integration partner who must: • thoroughly know his business • the products he is integrating • have a very good understanding of your business.

  23. Acknowledgments DICO’sXBRL system employs a combination of “off the shelf” and custom applications developed by Edgar Online (UBMatrix) and SQL Power with integration provided by SQL Power. These companies are working together to provide DICO with what we understand is a first of its kind XBRL, Dynamic, Regulatory Filing and Reporting Solution

  24. Questions