# SWIFT BIC to GLEIF LEI Mapping Standard & Cross-Referencing
> Cross-reference financial institution SWIFT BIC codes with GLEIF Legal Entity Identifiers for regulatory transaction reporting.

- **Canonical URL:** https://stanzaapi.com/tools/lei-validator/gleif/bic-to-lei-mapping
- **Governing Standard:** ISO 17442 Legal Entity Identifier (Global Legal Entity Identifier Foundation (GLEIF))
- **Latency:** <1ms Edge
- **Privacy:** In-memory execution only (zero data stored or logged)

## Technical Overview & Governing Rules
The SWIFT-to-LEI relationship mapping connects transaction message BICs directly to legal counterparty entities under MiFID II and Dodd-Frank mandates.

## Specification Matrix
| Institution Name | BIC / SWIFT | LEI Code | Country |
| --- | --- | --- | --- |
| Deutsche Bank AG | DBEUMM21XXX | 7LTWFZYICNSX8D621K86 | Germany |
| BNP Paribas SA | BNPAFRPPXXX | ROM0U67LCH70SCY05V10 | France |
| JPMorgan Chase Bank, N.A. | CHASUS33XXX | 7H6GLXDRUGQFU57RNE97 | United States |

## Standard JSON Response Model
```json
{
  "bic": "DBEUMM21XXX",
  "lei": "7LTWFZYICNSX8D621K86",
  "legalName": "Deutsche Bank AG"
}
```

## Frequently Asked Questions & Edge Cases
### Q: Why is BIC to LEI mapping required in banking?
**A:** MiFIR/EMIR regulatory reporting requires financial institutions to report transaction counterparties using LEIs rather than BICs.