29.06.2013 Views

SEC Form 20-F - Deutsche Bank Annual Report 2012

SEC Form 20-F - Deutsche Bank Annual Report 2012

SEC Form 20-F - Deutsche Bank Annual Report 2012

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Deutsche</strong> <strong>Bank</strong><br />

<strong>Annual</strong> <strong>Report</strong> <strong>20</strong>10 on <strong>Form</strong> <strong>20</strong>-F<br />

Item 11: Quantitative and Qualitative Disclosures about Credit, Market and Other Risk 178<br />

We buy insurance in order to protect ourselves against unexpected and substantial unforeseeable losses. The<br />

identification, definition of magnitude and estimation procedures used are based on the recognized insurance<br />

terms of “common sense”, “state-of-the-art” and/or “benchmarking”. The maximum limit per insured risk takes<br />

into account the reliability of the insurer and a cost/benefit ratio, especially in cases in which the insurance<br />

market tries to reduce coverage by restricted/limited policy wordings and specific exclusions.<br />

We maintain a number of captive insurance companies, both primary and re-insurance companies. However,<br />

insurance contracts provided are only considered in the modeling/calculation of insurance-related reductions of<br />

operational risk capital requirements where the risk is re-insured in the external insurance market.<br />

The regulatory capital figure includes a deduction for insurance coverage amounting to € 467 million. Currently,<br />

no other risk transfer techniques beyond insurance are recognized in the AMA model.<br />

CI/D selects insurance partners in strict compliance with the regulatory requirements specified in the Solvency<br />

Regulations and the Operational Risks Experts Group recommendation on the recognition of insurance in<br />

advanced measurement approaches. The insurance portfolio, as well as CI/D activities are audited by Group<br />

Audit on a periodic basis.<br />

Operational Risk at Postbank<br />

Postbank’s approach to Operational Risk Management is largely comparable to <strong>Deutsche</strong> <strong>Bank</strong>’s approach.<br />

The Management Board of the Postbank is solely responsible for the management, control, and monitoring of<br />

operational risk. The Operational Risk Committee (ORK) commissioned by the Postbank Management Board<br />

defines the strategy and framework for controlling operational risk. Day-to-day management of operational risk<br />

is the responsibility of the individual units within the Postbank. Strategic parameters for managing operational<br />

risk, both qualitative as well as quantitative, are part of the overall strategy.<br />

At Postbank the economic capital requirements for operational risk both for the Postbank as a whole and for<br />

the four business divisions individually have been determined using a standalone internal capital model to<br />

calculate capital requirements for operational risk. Postbank received the approval by the BaFin for their AMA<br />

in December <strong>20</strong>10.<br />

Within the consolidation of Postbank the results of the economic capital requirements for operational risk have<br />

been recalculated using <strong>Deutsche</strong> <strong>Bank</strong>’s economic capital methodology for operational risk based upon<br />

pooled data from <strong>Deutsche</strong> <strong>Bank</strong> Group and Postbank and are reported in aggregate in section “Overall Risk<br />

Position” of this report.<br />

Liquidity Risk at <strong>Deutsche</strong> <strong>Bank</strong> Group (excluding Postbank)<br />

Liquidity risk management safeguards our ability to meet all payment obligations when they come due. Our<br />

liquidity risk management framework has been an important factor in maintaining adequate liquidity and in<br />

managing our funding profile during <strong>20</strong>10.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!