service balance des paiements adaptations projetees a partir de ...

PortfolioTo give a quick summary, a cssr document is divided into two parts :• Admin part : containing definitions to control the processing of the transfer. This part is independend of the reportingit contains• Content part : an application specific part containing the actual data to reportIt is the content part that is further described in this document.The first section will describe the XML Schema at which the element of the XML document must satisfy.Small examples will be given with their associated definition of the part it highlights. The second section givesthe complete XML Schema, followed by a last section with an example of a valid cssr document containing a fictionaldelivery of this reporting.2. Comparision with Schema A reporting protocolAnno 2004, the financial institutions report already portfolio tables (039x) as part of the Schema A reporting. Thisprotocol is based on it and will correspond exactly with it, taking the following differences into account.• Because the amounts are expressed in the currency unit of the security, as reported in the data, or in EUR if notapplicable, the attribute cbrk is omitted on the tag.• The portfolio is a reporting where rubric is just a sequential numbering to identify a reported item. Because ofthis uniformity in the portfolio, the attribute dyn is also deleted.• Different content type, instead of SfiAcquisitionDataset it will be PrtAcquisitionDataset3. XML Schema.NoteThis schema needs definitions defined elsewhere in CSSR3.1. Some general definitionsThe following types are defined.3.1.1. Schema A Rubric3.1.1.1. DescriptionSchema A rubric Code3.1.1.2. Schema Definition1this documentation can be obtained by contacting the team resposible for the technical implementation of CSSR at the NBB, see CSSRGuidelines on NBB website [http://www.nbb.be/dq/n/dq8/Readme_cssr.htm]2