Third party priority claims against the protection (THRD_PRTY_PRRTY_CLMS)

Edition: first edition Veröffentlicht: 10.03.2017 Zum Quelldokument →

Definition: Third party priority claims against the protection. The maximum amount of any existing higher ranked liens with respect to third parties other than the observed agent against the protection. The third party priority claim against the protection is the maximum amount of any existing higher ranked liens with respect to third parties other than the observed agent against the protection.

Reporting qualification: This data attribute is to be reported for every combination of a protection item and an instrument that it secures.

Values: This data attribute is a monetary amount in euro. The reported value is a non- negative real number. General reporting instructions, specific cases and examples The third party priority claim against the protection is the total amount of all third party claims on the protection item with higher ranked liens compared to the reported instrument. Instruments granted by third party credit institutions (observed agents) which give rise to the third party priority claims on the protection securing a reported instrument are not subject to AnaCredit reporting from the perspective of the reporting agent of the observed agent that extended the reported instrument (unless the third party is another observed agent within the scope of the same reporting agent). This is because only instruments held or serviced by an observed agent are reportable. The third party claims against the protection available to an observed agent are typically based on the information as recorded at the inception of an instrument rather than at a reporting reference date. Therefore, this data attribute in AnaCredit is quite static, as it is not expected to change regularly. It would tend to be updated when the claim of the third party on the protection item as such no longer exists with the third party. Nevertheless, the third party priority claim may be updated on an ongoing basis if observed agents have up-to-date information in this respect. The amount of the third party priority claims against the protection is typically a feature of the protection item itself rather than of the instrument-protection combination vis-à-vis an observed agent. Therefore, in cases where multiple instruments are reported that are secured by the same protection item, it is common practice to report the same amount for the data attribute “third party priority claim” for 28 February 2017 AnaCredit Reporting Manual – Part II – Datasets and data attributes each instrument-protection combination. However, this is not necessarily the case in general, as the observed agent may have different liens of the same protection item in relation to different instruments. The third party priority claim is the maximum amount of any existing higher ranked liens with respect to third parties where higher ranked liens are to be determined on the basis of the lowest priority claim the creditor has against the protection (if the creditor has multiple claims with mixed liens ranks on the same property). For an illustration of how the instrument-protection received dataset may be reported in the presence of multiple claims (with mixed ranks) on the same protection item, including the reporting of the third party priority claim, please consider the following example. 28 February 2017 AnaCredit Reporting Manual – Part II – Datasets and data attributes Example 52: Multiple mortgage claims on a single property with third party claims This example concerns the perspective of observed agent (OA#1). 1. On 5 August 2016 OA#1 makes a contract Con#6 to extend a first-lien loan in the amount of €100,000 (Inst#1) to a legal entity (Cpy#A). The loan is secured by a mortgage claim of €400,000 on commercial real estate (CRE#1). The market value of the property is established to be €950,000. 2. On 23 June 2017, a credit institution (OtherBank) extends a second-lien loan of €150,000 (Inst#2) to Cpy#A on the basis of a mortgage inscription amount of €300,000 on the same commercial real estate (CRE#1); at the origination of the loan, the market value of the property is established to be €950,000. 3. On 7 September 2018 OA#1, on the basis of contract Con#8 extends a loan of €500,000 (Inst#3) to Cpy#A. The loan is secured by a third-lien mortgage on the commercial real estate CRE#1 (with a mortgage claim of €500,000). The market value established at the origination of Inst#3 is €1 million. 4. As of 30 September 2018, the outstanding nominal amounts of the loans extended by OA#1are €100,000 and €500,000 for Inst#1 and Inst#3, respectively. The real estate collateral is exclusively owned by Cpy#A. OA#1 has no insight into the outstanding nominal amount of Inst#2 extended by OtherBank. The real estate collateral is reported to AnaCredit as of 30 September 2018 in connection with Inst#1 and Inst#2. This reporting is depicted in Table 97 (selected data attributes only). Table 97 Commercial real estate CRE#1 in the protection received dataset Reporting reference date Protection provider identifier Protection identifier Protection value Type of protection 30/09/2018 CPY#A CRE#1 1,000,000.00 Commercial real estate collateral Please note that it is the immovable property itself, not the mortgage claim on the property, which is considered a protection item in relation to both instruments. As regards the allocation of the protection value to the two instruments, OA#1 calculates as follows in the event that Cpy#A defaults: • the commercial real estate collateral will be realised in the market and the liquidation will give €1 million of proceeds; • having a first-lien of €400,000 on the protection, OA#1 allocates €100,000 of it to Inst#1 and the remaining €300,000 to Inst#3; • from the remaining proceeds of €600,000, OA#1 subtracts the claim of OtherBank of €300,000, which has a prior lien over its other claim, and allocates an additional €200,000 of the protection value to Inst#3 (up to the lien amount). This allocation is reported in the instrument-protection received dataset, which is depicted in Table 98. Table 98 Protection allocated value in the instrument-protection received dataset Reporting reference date Contract identifier Instrument identifier Protection identifier Protection allocated value Third party priority claim 30/09/2018 CON#6 INST#1 CRE#1 100,000.00 0.00 30/09/2018 CON#8 INST#3 CRE#1 500,000.00 300,000.00 28 February 2017 AnaCredit Reporting Manual – Part II – Datasets and data attributes Please note that the third party priority claim is the maximum amount of any existing higher ranked liens with respect to third parties (i.e. other than the observed agent), where higher ranked liens are to be determined on the basis of the lowest priority claim OA#1 has against the protection (as in this case there are multiple claims with mixed liens ranks on the same property). Please also note that in this case OA#1 own prior liens are not accounted for in the third party priority claim reported for Inst#3. Last but not least, the instrument (Inst#2) extended by the third party credit institution is not reported vis-à-vis OA#1, as only instruments held or serviced by the observed agent are subject to AnaCredit reporting. In this connection, the actual amount that could be eventually claimed by the third party credit institution (as the loan is substantially lower than the mortgage inscription) is not taken into account by OA#1. Please note that, when determining the protection allocated value in relation to Inst#3, both the third party priority claims and the amount of the protection value allocated to Inst#1 have been taken into consideration. This is necessary, as otherwise an amount larger than actually allocable would be dispensed to the instrument. This goes against the definition of the protection allocated value as the maximum amount of the protection value that can be considered as credit protection for the instrument. The amount of the existing third parties or observed agent priority claims against the protection is excluded in the protection allocated value. 28 February 2017 AnaCredit Reporting Manual – Part II – Datasets and data attributes Protection received dataset General aspects 9.1 The protection received dataset describe the characteristics of any protection (both funded and unfunded) that serves to secure the repayment of instruments reported in the instrument dataset. For the purposes of AnaCredit data collection, protection received data comprise data on any kind of protection that is linked to any reported instrument via the instrument-protection received table. Protection items that are not linked to any instrument reported under AnaCredit requirements do not have to be reported. A protection item is recorded in the protection received dataset if it is considered by the reporting agent to be an assurance or coverage against a negative credit event that may arise in relation to an instrument. In other words, protection serves as a creditor’s protection against a debtor’s default where the value of the protection can be used to offset the loan if the debtor fails to satisfactorily pay any amount that it is obliged to pay under the terms of the contract. Consequently, AnaCredit considers that any item accepted by the reporting agent as security and providing assurance or coverage against the credit risk arising under a contract or an instrument is reported. In particular, all protection items considered as such by reporting agents are reported irrespective of whether or not they are eligible for credit risk mitigation in the calculation of the minimum capital requirements under the CRR or reported as collateral under Annex V to the ITS. Similarly, protection is reported independently of the loan/collateral ratio. If a protection item is contractually assigned not at the level of a particular instrument but at the level of a debtor or a contract, this implicitly means that the protection item is linked to all instruments of the debtor or all instruments existing under the contract. Consequently, such protection is reported as a single record in the protection received dataset, whereas the instrument-protection received dataset includes a record for every combination of this protection item with any instrument of the debtor (or of the contract, respectively) that is reported to AnaCredit. Each protection has one protection identifier. This identifier will not change over time and cannot be used as the protection identifier for any other protection. Each protection item has a value and the total protection value without considering any (regulatory) haircuts is reported. Each protection item is assigned one type of protection as referred to in Article 1(25) of the AnaCredit Regulation. 28 February 2017 AnaCredit Reporting Manual – Part II – Datasets and data attributes 9.1.1 Relationship with the counterparty risk/default datasets As regards the relationship between the protection received entity table and the counterparty risk/default entity table, the counterparty risk/default entity table is applicable for those protection providers which are at the same time the protection issuers of the protection (i.e. when the provider of the protection and the issuer of the protection coincide). This situation happens in the case of unfunded credit protection as defined in Article 4(1)(59) of the CRR. In particular, regarding protection providers of a “financial guarantee” as defined in paragraph 58 of Annex V to the ITS, the counterparty which is the protection provider of such a protection item and is recorded in the protection received entity table is also recorded in the counterparty risk/default entity table. Note that “financial guarantee” as defined in paragraph 58 of Annex V to the ITS corresponds to the following types of protection as defined in Annex IV of the AnaCredit Regulation: “financial guarantees other than credit derivatives” and “credit derivative”, to the extent the credit derivative meets the definition of a “financial guarantee”. Level of granularity 9.2 The level of granularity is the individual protection item, which may be linked to multiple instruments. The protection identifier represents a protection item (e.g. real estate property or debt securities) that is used to secure payments arising under one or more instruments. A protection item refers to a specific property rather than a debtor’s (or third party’s) pledge of specific property. In particular, the level of protection will not be lower than the level of property (as opposed to a claim on the property). Please note, however, that a protection item may entail several properties (e.g. a pool of securities or a pool of trade receivables) but in no case will the protection level be lower than the property level. For more guidance on the level at which protection is considered please refer to the following example. 28 February 2017 AnaCredit Reporting Manual – Part II – Datasets and data attributes Example 53: Level of protection – multiple mortgage claims on single property 1. On 17 September 2018 observed agent (OA#1) extends a loan of the amount of €300,000 (Inst#1) to a legal entity (Cpy#A). The loan is secured by a mortgage claim of €500,000 on commercial real estate (CRE#1). 2. During the loan acceptance process, the market value of the real estate was established to be €1,000,000 following a third party appraisal. The property is exclusively owned by Cpy#A. 3. In addition, the information available in the cadastre shows a third party credit institution’s claim of €150,000 on the real estate which was made in 2016. The real estate collateral is reported to AnaCredit as of 30 September 2018 in connection with Inst#1. This reporting is depicted in Table 99 (selected data attributes only). Table 99 Reporting property as protection Reporting reference date Protection provider identifier Protection identifier Protection value Type of protection 30/09/2018 CPY#A CRE#1 1,000,000.00 Commercial real estate collateral Please note that it is the immovable property itself, not the mortgage claim on the property, which is considered a protection item in relation to Inst#1. Therefore it is the property that is reported in the protection received dataset. Furthermore, as regards the protection value, it is the total amount that is reported in the dataset rather than the mortgage claim of €500,000. Similarly, the protection value is reported without taking account of the third party priority claim that exists in relation to the protection item (i.e. the immovable property). Please note, however, that both claims (i.e. the actual claim of OA#1 and the third party priority claim) are expected to be taken into consideration when determining the protection allocated value as reported in the instrument-protection received dataset, which is defined to be “the maximum amount of the protection value that can be considered as credit protection for the instrument. The amount of the existing third parties or observed agent priority claims against the protection are excluded in the protection allocated value”. For more guidance regarding the protection allocated value please refer to Chapter 8 of this Manual dealing specifically with the instrument-protection received dataset. Please note that AnaCredit does not stipulate at which level so-called bundled protection items are reported. In this respect, it is clarified that in the case of protection items which entail several individual items, each of which could be considered a separate protection item (e.g. a pool of securities or a pool of trade receivables), the level of granularity depends on the approach that the reporting agent takes to value such protection items. More specifically, for bundled protection items which are valued and considered by the reporting agent as one multi-name protection item, the reporting granularity of the protection item is the same, and the reporting agent does not report the individual items separately. An example of such protection items includes a pool of securities received which are valued and considered by the creditor as a single 28 February 2017 AnaCredit Reporting Manual – Part II – Datasets and data attributes protection item; in such a case, the pool of securities is reported as one (bundled) protection item in a single record in the protection received dataset with a value reflecting the total value of the securities included therein, as opposed to reporting each individual security within this pool (each with a separate protection identifier). However, if for the valuation and consequent utilisation the creditor uses a look- through approach for such bundled protection items, then such protection is reported to AnaCredit at the level of an individual item included in the basket. 9.2.1 Uniqueness of protection identifier at the level of a reporting agent An individual protection item is uniquely identified by a protection identifier at the level of a reporting agent, cf. Section 2.2.6. This means that the same protection identifier of a protection item is used by whichever observed agent whose data include instruments secured by the protection item. A single protection item which is used as protection by different observed agents within the scope of the same reporting agent is therefore identified with the same (and common) protection identifier across the different observed agents. 28 February 2017 AnaCredit Reporting Manual – Part II – Datasets and data attributes For an illustration of how a protection item common across multiple observed agents of the same reporting agent is reported, consider the following example. Example 54: Unique identification of protection at the level of reporting agent 1. A credit institution (RepAgt#1) consists of the domestic part (OA#1/DOM) and a foreign branch (OA#2/FB). 2. On 17 September 2018 OA#1/DOM grants a short-term lending cross-limit to a legal entity (IntCpy#1) which is internationally active. In accordance with the contract, the credit cross-limit can be used by any subsidiary of IntCpy#1. 3. The cross-limit is secured by a financial guarantee (GUA#1) provided by IntCpy#1. The guaranteed amount is €5,000,000. 4. On 2 October, OA#1/DOM extends under the short-term lending cross-limit a loan (Loan#1/A) to a legal entity (Cpy#A) which is a subsidiary of IntCpy#1. 5. On 19 October OA#2/FB extends under the short-term lending cross-limit a loan (Loan#2/B) to a legal entity (Cpy#B) which is a subsidiary of IntCpy#1. In this situation, both Loan#1/A and Loan#2/B which relate to two different observed agents of the same reporting agent are secured with the same protection item (GUA#1). In connection with Loan#1/A, OA#1/DOM reports the guarantee in the protection received dataset. The reporting as of 31 October 2018 is depicted in Table 100. Table 100 Protection received dataset reported in relation to OA#1/DOM Reporting reference date Observed agent identifier Protection provider identifier Protection identifier Protection value Type of protection Type of protection value 31/10/2018 OA#1/DOM INTCPY#1 GUA#1 5,000,000.00 Financial guarantee other than credit derivatives Notional amount Meanwhile, OA#2/FB reports the same protection item in connection with Loan#2/B. This is presented in Table 101. Table 101 Protection received dataset reported in relation to OA#2/FB Reporting reference date Observed agent identifier Protection provider identifier Protection identifier Protection value Type of protection Type of protection value 31/10/2018 OA#2/FB INTCPY#1 GUA#1 5,000,000.00 Financial guarantee other than credit derivatives Notional amount Please note that, in this situation, when there is one protection item linked with multiple instruments relating to different observed agents of the same reporting agent, the common protection is reported in the protection received datasets of all the observed agents concerned, with the observed agents replicating the information regarding the common protection item (i.e. they report identical information for the whole record with the exception of the observed agent identifier). Irrespective of the fact that the same protection item may be reported multiple times in the protection received dataset (including in relation to different reporting agents, e.g. many unrelated credit institutions may have mortgage claims on the same real estate 28 February 2017 AnaCredit Reporting Manual – Part II – Datasets and data attributes property), the protection allocated values and the third party priority claims as reported in the instrument-protection received dataset in relation to different instruments are required to accurately reflect the actual situation, i.e. the reported value takes into account the fact that it is one and the same protection item, and, in particular, if a part of the protection value is allocated to one instrument, the maximum amount of the protection allocable to other instruments is reduced accordingly. In other words, the risk of double-counting the protection allocated value is mitigated thanks to the definitions of the protection allocated value and the third party priority claims. Reporting frequency 9.3 The information contained in the protection received dataset describes the protection regularly reported in the instrument-protection received dataset as of a reporting reference date. However, rather than being regularly reported, the information in the protection received dataset is submitted to AnaCredit once and updated whenever changed. This applies both to new records (i.e. when new/additional protection was received as security for the repayment of any instrument reported in AnaCredit) and to changed records (i.e. when a change takes place regarding a protection item for which the protection-received dataset was reported previously). In both cases, the records are reported no later than the monthly transmission of the instrument-protection received relevant for the reporting reference date on or before which the change came into effect. The protection received dataset – data attributes 9.4 The protection received dataset is applicable for protection items which are reported in the instrument-protection received dataset. For each protection item, the following data attributes are reported. Table 102 Overview of data attributes in the protection received dataset Data attribute Internal identifier Data type Section in Part II Reporting agent identifier √ String 2.2.1 Observed agent identifier √ String 2.2.2 Protection identifier √ String 2.2.6 Protection provider identifier √ String 2.2.7 Type of protection Code list 9.4.3 Protection value Amount in euro 9.4.4 Type of protection value Code list 9.4.5 Protection valuation approach Code list 9.4.6 Real estate collateral location Code list 9.4.7 Date of protection value Date 9.4.8 Maturity date of the protection Date 9.4.2 Original protection value Amount in euro 9.4.9 Date of original protection value Date 9.4.10 28 February 2017 AnaCredit Reporting Manual – Part II – Datasets and data attributes

Veröffentlicht: 06.02.2026 aktuell Zum Quelldokument →

Die vorrangigen Ansprüche Dritter an der Sicherheit entsprechen dem Maximalbetrag an Ansprüchen, die Dritte (bei denen es sich nicht um die beobachtete Einheit handelt) aufgrund vorhandener höherrrangiger Pfandrechte an der Sicherheit geltend machen können. In das Datenfeld ist ein Betrag in Euro einzutragen. Von fremden Kreditinstituten gewährte Instrumente, durch die die vorrangigen Ansprüche Dritter an der das gemeldete Instrument besichernden Sicherheit begründet werden, werden nicht in den AnaCredit-Meldungen der beobachteten Einheit, die das gemeldete Instrument gewährt hat, erfasst. Die Ansprüche Dritter an der einer beobachteten Einheit bereitgestellten Sicherheit beruhen in der Regel auf den Informationen, wie sie bei Vertragsabschluss erfasst wurden, statt auf der Datenmeldung zu einem bestimmten Meldestichtag. Somit ist dieses Datenfeld in AnaCredit eher statisch, denn es sind diesbezüglich keine regelmäßigen Änderungen zu erwarten. Eine Aktualisierung wäre tendenziell dann erforderlich, wenn der Anspruch des Dritten am eigentlichen Sicherungsgegenstand erlischt. Dennoch ist die laufende Aktualisierung dieses Datenfelds möglich, wenn der beobachteten Einheit neue Informationen in Bezug auf die vorrangigen Ansprüche Dritter vorliegen. Deutsche Bundesbank Statistik Richtlinien Juli 2026 6.141 Kreditdaten- statistik Der Betrag der vorrangigen Ansprüche Dritter auf die Sicherheit ist in der Regel ein Merkmal des Sicherungsgegenstands selbst und nicht der auf eine beobachtete Einheit bezogenen Kombination aus Instrument und empfangener Sicherheit. Bei Meldung von mehreren Instrumenten, die durch ein und denselben Sicherungsgegenstand besichert werden, wird daher üblicherweise für jede Kombination aus Instrument und Sicherheit derselbe Betrag im Datenfeld Vorrangige Ansprüche Dritter auf die Sicherheit gemeldet. Allerdings ist dies nicht unbedingt der Fall, denn eine beobachtete Einheit kann über unterschiedliche Pfandrechte an ein und denselben Sicherungsgegenstand für unterschiedliche Instrumente verfügen. Sofern der Gläubiger mehrere Ansprüche mit im Rang unterschiedlichen Pfandrechten hat, wird die Rangigkeit an dem auf der untersten Stufe stehenden vorrangigen Anspruch des Gläubigers an der Sicherheit gemessen. 5.8 Tabelle Daten des Vertragspartnerrisikos Die Tabelle Daten des Vertragspartnerrisikos bildet die Bewertung des Kreditrisikos des Vertragspartners gemäß CRR ab. Die Angaben in dieser Tabelle werden auf Ebene des Vertragspartners zusammengestellt. Die Meldung der Tabelle Daten des Vertragspartnerrisikos richtet sich danach, ob das Kreditinstitut über Vertragspartner verfügt, für die das Datenfeld Ausfallwahrscheinlichkeit zu melden ist. Siehe „Ausfallwahrscheinlichkeit“ Für Vertragspartner, bei denen es sich weder um Schuldner noch um Sicherungsgeber handelt, ist das Datenfeld Ausfallwahrscheinlichkeit nicht zu melden. Für diese Vertragspartner sind dementsprechend keine Datensätze in der Tabelle Daten des Vertragspartnerrisikos zu melden. Eine Meldung des Datenfelds Ausfallwahrscheinlichkeit ist erforderlich, wenn das Kreditinstitut die Erlaubnis erhalten hat, Schätzungen der Ausfallwahrscheinlichkeiten betroffener Schuldner und Sicherungsgeber gemäß dem auf internen Ratings basierenden Ansatz (IRBA) der CRR vorzunehmen. Hat das Kreditinstitut diese Erlaubnis nicht erhalten, dann ist die gesamte Tabelle Daten des Vertragspartnerrisikos nicht zu melden. Verfügt ein Kreditinstitut über keinerlei Vertragspartner, für die das Datenfeld Ausfallwahrscheinlichkeit zu melden ist, so entfällt die Meldung der gesamten Tabelle Daten des Vertragspartnerrisikos. Dies gilt insbesondere für Kreditinstitute, die ihre aufsichtlichen Mindesteigenkapitalanforderungen zur Unterlegung von Adressrisiken ausschließlich nach dem Kreditrisiko-Standardansatz (KSA) berechnen. Für Kreditinstitute, die zwar eine Erlaubnis zur Verwendung des IRBA haben, für bestimmte Risikopositionen jedoch dennoch den KSA in Übereinstimmung mit den Artikeln 148 und 150 CRR anwenden, gilt Folgendes: Wendet ein Kreditinstitut für sämtliche Risikopositionen eines bestimmten Vertragspartners den KSA an, so entfällt die Meldung des gesamten Datensatzes in der Tabelle Daten des Vertragspartnerrisikos für diesen Vertragspartner.