BIC Directory: What It Is and How to Integrate It
The BIC Directory is the reference data behind reliable institution identification in payments. Here is what it is, how it is used, where integrations get messy, and how to wire it into your routing, screening, and onboarding cleanly.
What is the BIC Directory?
The BIC Directory is SWIFT's reference list of Business Identifier Codes (BICs) and the institutions behind them. It is the data SWIFT publishes from the ISO 9362 BIC registry, and it was previously distributed as BIC Plus.
A BIC identifies a financial or business institution: which bank, in which country, and optionally which branch. The directory turns a raw code into trusted context, which is exactly what payment, compliance, and onboarding systems need.
How the BIC Directory is used in payments
The directory sits at several control points in a payment lifecycle. Getting institution identification right early removes downstream repairs and exceptions.
- Routing: confirm the counterparty institution and select the correct path before a payment is sent.
- Pre-validation: check that a BIC is valid and active before instructing, rather than after a rejection.
- Sanctions screening: resolve a code to a known institution so screening hits the right entity.
- Onboarding: validate institution data captured during client and counterparty onboarding.
BIC structure and common data issues
A BIC is 8 or 11 characters: a 4-character institution code, a 2-character ISO country code, a 2-character location code, and an optional 3-character branch code. An 8-character BIC refers to the head office.
The codes are simple, but the data captured around them rarely is. Internal systems accumulate truncated names, retired BICs, head-office codes used where a branch was meant, and free-text fields that no longer match the registry. These mismatches are the real cost of a BIC Directory integration.
Integrating the BIC Directory cleanly
Loading the feed is the easy part. The work that determines success is reconciling the directory against the institution records you already hold, then keeping them aligned as both change.
The approach is to validate your messy internal records against the BIC Directory using deterministic, explainable checks, so integration is seamless and any migration runs smooth. Every proposed correction is a suggestion your team approves, never a silent overwrite. BankValidate is the reference build that demonstrates this remediation core on synthetic data; the same approach applies against live directory data in a real engagement.
Frequently Asked Questions
- Is the BIC Directory the same as BIC Plus?
- It is the same lineage. SWIFT's BIC reference data product was distributed as BIC Plus and is now provided as the BIC Directory within the SWIFTRef portfolio.
- What is the difference between a BIC and a SWIFT code?
- They are the same thing. SWIFT code is the informal name for a BIC (Business Identifier Code), the ISO 9362 code that identifies a financial institution.
- Why does an 8-character BIC differ from an 11-character BIC?
- An 8-character BIC identifies the institution's head office. The optional final 3 characters are a branch code that points to a specific branch or department.
- How do I keep our internal data aligned with the BIC Directory?
- Reconcile internal institution records against the directory with deterministic checks, surface the mismatches for review, and apply approved corrections. Repeating that on each refresh keeps the two sources aligned over time.