View
217
Download
0
Category
Tags:
Preview:
Citation preview
XBRL COFINREP ImplementationVII COFINREP Workshop
Bartosz Ochocki bartosz.ochocki@br-ag.eu
XBRL in Polish banking sector•National Bank of Poland▫extension of COREP and FINREP taxonomies▫COREP CA template required starting from March 2007▫COREP and FINREP obligatory since July/September 2007
legislative process development of the reporting platform designing of the data base enabling analysis
• Reporting banks▫preparation of their internal systems▫ solutions of Polish software vendors
2007-05-09VII COFINREP Workshop
2
Reporting chainModel approach
2007-05-09VII COFINREP Workshop
3
RegulatorRegulator
Reporting entityReporting entity
Content and format
Report
Data sources
Report generatingReport generating
Report receiving and validatingReport receiving and validating
Data mining
Software vendors and consultants
Legal regulations
Legal regulations
XBRL reporting implementation phases2007-05-09VII COFINREP Workshop
4
Requirements analysisRequirements analysis
Resources analysis and planningResources analysis and planning
Preparation of infrastructurePreparation of infrastructure
TestsTests
Production useProduction use
Rules and processes regarding maintenanceRules and processes regarding maintenance
I
II
III
IV
V
VI
Heavily depend on scope, conditions
and means of implementation
Heavily depend on scope, conditions
and means of implementation
Scope of implementation
2007-05-09VII COFINREP Workshop
5
RegulatorRegulator
Reporting entityReporting entity
Data sources
Report generatingReport generating
Report receivingReport receiving
Data mining
Report for statistics
Report for super-visors
Report for financial/
accounting
scope of reportingchain
range of data collected
Means of implementation2007-05-09VII COFINREP Workshop
6
development using own resources only
development using available tools as
components
purchase of the solution covering whole reporting chain
independencycustomization possibility
time and effort minimizingless knowledge required
XBRL reporting implementation phases2007-05-09VII COFINREP Workshop
7
Requirements analysisRequirements analysis
Resources analysis and planningResources analysis and planning
Preparation of infrastructurePreparation of infrastructure
TestsTests
Production useProduction use
Rules and processes regarding maintenanceRules and processes regarding maintenance
II
IIII
III
IVIV
VV
VIVI
2007-05-09VII COFINREP Workshop
8
Preparation of infrastructurePreparation of infrastructureIII
Preparation of data modelPreparation of data model
Taxonomy development and documentationTaxonomy development and documentation
Instance document requirements documentationInstance document requirements documentation
Development of reports generating solutions (optional)Development of reports generating solutions (optional)
Communication aspects (transferring and receiving files)Communication aspects (transferring and receiving files)
Taxonomies distributionTaxonomies distribution
Transfer of reports (receiving and validation)Transfer of reports (receiving and validation)
Data conversion and gatheringData conversion and gathering
Data analysisData analysis
11
22
33
44
55
5a5a
5b5b
66
77
2007-05-09VII COFINREP Workshop
9
Preparation of infrastructurePreparation of infrastructureIIIPreparation of data modelPreparation of data model 11
•Problems▫ level of details▫decision on use of dimensions▫ logical split in parts▫understanding of the nature and limitations of XBRL
technology
2007-05-09VII COFINREP Workshop
10
Preparation of infrastructurePreparation of infrastructureIIIPreparation of data modelPreparation of data model
Taxonomy development and documentationTaxonomy development and documentation11
22
RequirementsRequirements
DesignDesign
BuildingBuilding
TestingTesting
Publication & Recognition
Publication & Recognition
Maintenance and Usage
Maintenance and Usage
Taxonomy requirements
Taxonomy requirements
Information model
Information model
Taxonomy Working Drafts
Taxonomy Working Drafts
Taxonomy Exposure Draft
Taxonomy Exposure Draft
Taxonomy Final Version
Taxonomy Final Version
Predevelopment
Development
Post-development
• framework and modularization - building a taxonomy from logical pieces
• aim:▫ avoiding redundancy (elements and relationships)▫minimizing of efforts▫minimizing of size▫maximizing of functionality and flexibility
• technical approaches:▫modularization on linkbase (extended links) level [IFRS-GP]▫modularization with one sack for elements definitions [FINREP]▫modularization with common elements' sacks [COREP]▫mix
2007-05-09VII COFINREP Workshop
11
Preparation of infrastructurePreparation of infrastructureIIITaxonomy development and documentationTaxonomy development and documentation 22
2007-05-09VII COFINREP Workshop
12
S(w)
C
L
R
S(b)
S1(p)
P
L
R
D
S1(d)
L
R
C
S2(p)
P D C
S3(p)
P D
D
S2(d)
L
R
D
S3(d)
L
R
D
S1(t)
L
S2(t)
D L
S3(t)
D
S(ts)
S(tr)
modularization with one sack for elements definitions[FINREP]
2007-05-09VII COFINREP Workshop
13
C
S1(p)
P D
S1(d)
L
R
D
S2(d)
L
R
D
S3(d)
L
R
D
L
S1(t)
D L
S2(t)
D L
S3(t)
D
L R
C
S1(cp)
P D
L R
C
S2(cp)
P D
L R
C
S2(p)
P D
L R
C
S3(p)
P D
L R
S(ts)
modularization with common elements' sacks
[COREP]
NBP –Taxonomy framework2007-05-09VII COFINREP Workshop
14
monthly
quarterly
yearly
quarterly
quarterly
monthly
quarterly
yearly
monthly
quarterly
yearly
PAS
IFRS
IFRS
individual
consolidated
individual
consolidated
FINREP
COREP
COMMON
• requirements regarding indication of version and sort of taxonomy on which report is based:▫automatic: schemaRef attribute of the entry schema
(extending prohibited)▫additional:
file name context id reported element …
• requirements for data accuracy▫precision/decimals attributes▫depending on concept or data type
2007-05-09VII COFINREP Workshop
15
Preparation of infrastructurePreparation of infrastructureIIIInstance document requirements documentationInstance document requirements documentation 33 (1)
• specific file names and context ids, e.g.: N_a_b_c_d_RRRRMMDD.xbrl▫N: shortened bank name▫a: [c;f]▫b: [j;s]▫ c: [p;m]▫d: [m;k;r]▫RRRRMMDD: reporting date
• reporting entity identification:▫entity identifier: code of reporting bank▫ identifier scheme: http://sis.nbp.pl/ticker
2007-05-09VII COFINREP Workshop
16
Preparation of infrastructurePreparation of infrastructureIIIInstance document requirements documentationInstance document requirements documentation 33 (2)
2007-05-09VII COFINREP Workshop
17
Preparation of infrastructurePreparation of infrastructureIIIInstance document requirements documentationInstance document requirements documentation 33 (3)
<xbrli:context id="BANK_f_j_p_k_20070630P_FDPA003_FDPP023_FDWA002"> <xbrli:entity> <xbrli:identifier scheme="http://sis.nbp.pl/bank">111</xbrli:identifier> <xbrli:segment> <xbrldi:explicitMember dimension="d-FINREP-pl-pa:PortfelABWymiar">
d-FINREP-pl-pa:PortfelB </xbrldi:explicitMember> <xbrldi:explicitMember dimension="d-FINREP-pl-pp:PodzialPodmiotowyWymiar">
d-FINREP-pl-pp:DuzePrzedsiebiorstwa </xbrldi:explicitMember> <xbrldi:explicitMember dimension="d-FINREP-pl-wa:WalutyWymiar">
d-FINREP-pl-wa:Pln </xbrldi:explicitMember> </xbrli:segment> </xbrli:entity> <xbrli:period> <xbrli:startDate>2007-03-31</xbrli:startDate> <xbrli:endDate>2007-06-30</xbrli:endDate> </xbrli:period> </xbrli:context>
<xbrli:unit id="PLN"> <xbrli:measure>iso4217:PLN</xbrli:measure> </xbrli:unit>
<p-FINREP-pl:PrzychodyZTytuluOdsetekKredytyNaNieruchomosciMieszkaniowe decimals="0" unitRef="PLN" contextRef="BGK_f_j_p_k_20070630_FDPA003_FDPP023_FDWA002">1000 </p-FINREP-pl:PrzychodyZTytuluOdsetekKredytyNaNieruchomosciMieszkaniowe>
<xbrli:context id="BANK_f_j_p_k_20070630P_FDPA003_FDPP023_FDWA002"> <xbrli:entity> <xbrli:identifier scheme="http://sis.nbp.pl/bank">111</xbrli:identifier> <xbrli:segment> <xbrldi:explicitMember dimension="d-FINREP-pl-pa:PortfelABWymiar">
d-FINREP-pl-pa:PortfelB </xbrldi:explicitMember> <xbrldi:explicitMember dimension="d-FINREP-pl-pp:PodzialPodmiotowyWymiar">
d-FINREP-pl-pp:DuzePrzedsiebiorstwa </xbrldi:explicitMember> <xbrldi:explicitMember dimension="d-FINREP-pl-wa:WalutyWymiar">
d-FINREP-pl-wa:Pln </xbrldi:explicitMember> </xbrli:segment> </xbrli:entity> <xbrli:period> <xbrli:startDate>2007-03-31</xbrli:startDate> <xbrli:endDate>2007-06-30</xbrli:endDate> </xbrli:period> </xbrli:context>
<xbrli:unit id="PLN"> <xbrli:measure>iso4217:PLN</xbrli:measure> </xbrli:unit>
<p-FINREP-pl:PrzychodyZTytuluOdsetekKredytyNaNieruchomosciMieszkaniowe decimals="0" unitRef="PLN" contextRef="BGK_f_j_p_k_20070630_FDPA003_FDPP023_FDWA002">1000 </p-FINREP-pl:PrzychodyZTytuluOdsetekKredytyNaNieruchomosciMieszkaniowe>
•MS Excel macro for CA template
•Field left to the market
2007-05-09VII COFINREP Workshop
18
Preparation of infrastructurePreparation of infrastructureIIIDevelopment of reports generating solutions (optional)Development of reports generating solutions (optional) 44
• communication platform: Internet•basic features:▫ login▫taxonomy distribution▫transfer and receive of report
report classification period taxonomy package
information on submitting person information on person responsible for data
2007-05-09VII COFINREP Workshop
19
Preparation of infrastructurePreparation of infrastructureIIICommunication aspects (transferring and receiving files)Communication aspects (transferring and receiving files) 55
2007-05-09VII COFINREP Workshop
20
Preparation of infrastructurePreparation of infrastructureIIICommunication aspects (transferring and receiving files)Communication aspects (transferring and receiving files) 55
• XBRL and other validations
▫ XBRL - embedded in portal validator
▫ need for customization of error messages language human readability
▫ advanced business rules business rules need to be communicated to reporting entities (preferred
electronic format, e.g. CSV, XML, …) available software specific solutions
▫ other checks formal requirements regarding instance documents completeness
▫ historical checks on the database level
2007-05-09VII COFINREP Workshop
21
Preparation of infrastructurePreparation of infrastructureIIITransfer of reports (receiving and validation)Transfer of reports (receiving and validation) 5b5b
• Data conversion▫mapping of:
taxonomies in order to design database reports (instance documents) into databases
▫mechanism to flatten XBRL contextually dimensionally
▫may support problem of versioning indication of changes in taxonomies with regard to databases consequences of taxonomy changes for XBRL instance
documents content
2007-05-09VII COFINREP Workshop
22
Preparation of infrastructurePreparation of infrastructureIIIData conversion and gatheringData conversion and gathering 66
XBRL Reporting Chain Model
2007-05-09VII COFINREP Workshop
23
2007-05-09VII COFINREP Workshop
24
Rules and processes regarding maintenanceRules and processes regarding maintenanceVI
RegulatorRegulator
Reporting entityReporting entity
Report
Data sources
Generating reportsGenerating reports
Receiving and validating reportReceiving and validating report
Data gathering
New (changed/corrected)
taxonomy
Changes in legislationChanges in legislation
Former taxonomy
Changes in base taxonomy (in case of
extensions)
Changes in base taxonomy (in case of
extensions)
Format and content
Taxonomy bugs and
issues
Taxonomy bugs and
issues
Changes in taxonomy
• technical (ID) labels▫construction: link:label elements with specific xlink:role
attribute value▫unique identification of a concept▫benefits:
easier and faster communications (short codes instead of long labels)
easier indication of concepts (in taxonomy, instance document or validation reports)
direct link between data model and the taxonomy supports designing of, mappings to and maintenance of
databases supports versioning (codes don't change while names or
namespaces do)
2007-05-09VII COFINREP Workshop
25
Rules and processes regarding maintenanceRules and processes regarding maintenanceVI
Responsibilities of the reporting banks• gathering and calculation of reporting data• generation of the instance documents▫correct definition of context information▫ability to localise reporting concepts in the taxonomy
structure▫proper mapping from internal systems and databases
• validation of the instance document▫XBRL (XML and others)▫business rules▫ formal requirements
• sending of the instance document to the reporting system• understanding of error reports and correction of errors
2007-05-09VII COFINREP Workshop
26
Thank you
Bartosz Ochocki bartosz.ochocki@br-ag.eu
Recommended