> ## Documentation Index
> Fetch the complete documentation index at: https://docs.creditbenchmark.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Bank Data Onboarding

> Credit Benchmark reviews sample PD files, validates contributor models, and onboards new contributing banks through a structured process before go-live.

Before onboarding a new contributor bank, Credit Benchmark runs a **structured analysis** to ensure data is fit for inclusion in the consensus. These discussions can run in parallel with other client onboarding workstreams. We review contributor models and data, examine **sample PD files**, and work collaboratively with client teams and data owners to investigate potential outliers or differences versus history and peers. Confirmed issues are resolved before **go‑live**.

## Pre-Onboarding Review

As part of this analysis, we:

* **Verify PD scope and definitions** — 1‑year TTC; senior unsecured; wholesale/commercial book; default definition alignment
* **Evaluate PD scale** — confirm whether the bank's PD scale aligns with other contributors or whether practices are inconsistent with existing contributors
* **Screen sample submissions for anomalies** — dispersion/RSD, large movements; confirm outliers with the bank
* **Validate identifiers and mapping approach** — support accurate entity resolution (LEI/ticker where available)

<Note>
  In select cases, Credit Benchmark has opted to **not include** contributed data in the consensus. CB will still receive these data points for reporting and concordance purposes, but will not use them when publishing CCRs.
</Note>

## Onboarding Questionnaire

Contributors complete a structured methodology **questionnaire** confirming **eligibility and comparability** of contributed PDs, documenting governance and data practices, and establishing operational readiness for ongoing submissions.

### What we confirm in each area

<AccordionGroup>
  <Accordion title="PD definition and scope">
    * 1‑year TTC obligor PDs
    * Senior unsecured
    * Wholesale/commercial book
    * Out‑of‑scope items (facility‑level, retail, asset‑backed)

    *Example: Do your 1‑year PDs represent obligor‑level TTC views for senior unsecured exposure in the wholesale/commercial book?*
  </Accordion>

  <Accordion title="Default definition">
    * Alignment with the Basel definition of default (or jurisdictional equivalent)

    *Example: Which default definition do you apply in production?*
  </Accordion>

  <Accordion title="Rating system governance">
    * Model validation
    * Approvals and overrides
    * Watchlist and early warning
    * Re‑rating triggers
    * Review cadence

    *Example: How are rating overrides raised, approved, and tracked?*
  </Accordion>

  <Accordion title="Submission frequency and timeliness">
    * Minimum monthly snapshot
    * Cut‑off dates
    * Backfill and roll‑forward rules

    *Example: What is your monthly submission timeline and how do you handle backfills/corrections?*
  </Accordion>

  <Accordion title="Data elements provided">
    * Identifiers (LEI, ticker, national IDs)
    * Internal rating
    * PD and as‑of date
    * Model or scorecard
    * Firmographics
    * Explicit non‑collection: no facility data, exposure, MNPI, or financial inputs

    *Example: Which identifiers will you provide per obligor and what coverage do you expect?*
  </Accordion>

  <Accordion title="Special cases and treatments">
    * Guarantees and credit enhancements
    * Consolidated vs. legal entity
    * Branches and subsidiaries
    * Funds and SPVs
    * Sovereigns and public sector

    *Example: How do you treat guarantees and group structures?*
  </Accordion>

  <Accordion title="Change management">
    * Notification of model changes and recalibrations
    * Methodology drift
    * Known data limitations

    *Example: How will you notify CB of model changes or recalibrations?*
  </Accordion>

  <Accordion title="Security and transfer">
    * Secure transport method
    * Operational and escalation contacts

    *Example: What secure transfer method will you use and who are the contacts?*
  </Accordion>
</AccordionGroup>