1 / 5

XBRL in Luxembourg

XBRL in Luxembourg. October 2006. J.-L. Franck IT Manager CSSF, Luxembourg October 4, 2006. Activities on a national level. Luxembourg jurisdiction in constitution (XBRL Luxembourg a.s.b.l.)

jela
Download Presentation

XBRL in Luxembourg

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. XBRL in Luxembourg October 2006 J.-L. Franck IT Manager CSSF, Luxembourg October 4, 2006

  2. Activities on a national level • Luxembourg jurisdiction in constitution (XBRL Luxembourg a.s.b.l.) • Partners: institutions and organisations (Bankers’ association, regulators, Luxembourg Stock Exchange, …) • 2 concrete projects

  3. COREP / FINREP reporting • Prepared by CSSF (Luxembourg banking and financial sector regulator) • Introduction in 2007 (voluntary) resp. 2008 (mandatory) • Detailed in CSSF Circular 06/251 • Copy of data goes to BCL (central bank)

  4. Circular 06/251 • XBRL format mandatory • Publication of taxonomies early 2007 • Just core information, no (significant) extension • Further details on « www.cssf.lu » (Laws/Circulars resp. Legal/Periodic reporting)

  5. Open questions • Filenaming convention: • Name, reporting month, template? • Should the following data be included in the filename or shall we extend the taxonomy? • Name or id of the bank or institution • Information if the bank is exempted from calculating capital requirements for their trading portfolio • Return path for information about validation? • Further restrictions (only one time period per instance, …) • No calculation rules left in « core information »

More Related