SWIFTRef and reference data directories
Trusted directories of codes, identifiers, and settlement instructions keep payments routed correctly and out of manual repair.
L0 Explain simply
A payment only reaches the right place when the data used to route it is correct. Every message names parties and paths using codes: a Business Identifier Code (BIC) for an institution, an International Bank Account Number (IBAN) for an account, national clearing codes, and settlement instructions that say where funds should land. If any of these is wrong or out of date, the payment stops for manual repair or reaches the wrong party. Reference data is the shared, trusted list that keeps these codes accurate. SWIFTRef is the utility that collects and publishes that data so institutions do not each maintain their own copy from scratch.
L1 Core concepts
SWIFTRef is Swift's reference-data utility. It gathers data from national authorities, banks, and Swift's own records, then publishes a set of directories that payment systems consult before and during processing. The core directories are the BIC Directory of Business Identifier Codes, Bank Directory Plus for banks and branches with their national codes and Legal Entity Identifiers (LEIs), IBAN Plus for International Bank Account Number structures and their matching BICs, the Standing Settlement Instructions (SSI) Directory for where counterparties want funds settled, and the SEPA Routing Directory for reachability across Single Euro Payments Area schemes. Institutions take this data through downloadable files, a web application called Bankers World Online, and application programming interfaces (APIs), choosing whatever fits their systems.
L2 Practitioner view
The point of shared reference data is to prevent errors that are expensive to fix later. When a sender has the wrong BIC for a beneficiary bank, or an IBAN that does not match the institution named, the payment cannot be applied automatically. It falls into a repair queue where staff investigate, contact counterparties, and re-key details, which costs time and money and delays the beneficiary. Good reference data lets systems validate a BIC, derive the correct BIC from an IBAN, and confirm reachability before the message leaves. IBAN Plus is what lets a system move from an account number to the right institution. The SSI Directory removes the need to exchange settlement details for every trade. Kept current, these directories raise the share of payments that pass straight through.
L3 Technical details
Reference data connects to how an institution controls its correspondents. The Relationship Management Application (RMA) governs which counterparties may exchange messages at all, and RMA Plus makes that control more granular by permitting or blocking specific message types with each partner. Reference data and RMA work together: the directories confirm who a counterparty is and how to reach them, while RMA authorisations decide whether traffic with that counterparty is allowed and of what kind. Delivery choice also matters operationally. Large institutions often load the full files nightly into their processing engines; others query the APIs in real time as a message is built; and staff investigating a specific case can look a party up interactively in Bankers World Online. Each channel serves a different point in the payment lifecycle.
L4 Standards & sources
In practice, reference data quality is a continuous obligation rather than a one-time load. Directories change as banks merge, branches open or close, national code schemes update, and settlement instructions are revised. An institution that loads a directory once and lets it age will see its repair rate climb as stale entries route payments to identifiers that no longer exist. The discipline is to refresh on the publisher's cycle, reconcile against internal records, and treat a validation failure as a signal to update data rather than to override it. Because SWIFTRef consolidates data from many authoritative sources into one utility, it reduces the number of separate feeds an institution must maintain, but it does not remove the responsibility to keep the local copy current and to apply it consistently across every payment channel.
Sources & standards1
- Official requirement
SwiftRef reference data services ↗ — Swift
Used for public summaries of the SwiftRef directories and their delivery through files, a web application, and application programming interfaces.
Sources for this topic2
- Official requirement
SwiftRef reference data services ↗ — Swift
Used for public summaries of the SwiftRef directories and their delivery through files, a web application, and application programming interfaces.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
What this simplifies: The directories and delivery options are summarised at a conceptual level; exact fields, update cadence, and product packaging vary and full detail sits behind swift.com. All example institutions are fictional.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.
Deepest material on this page: L4 — Standards & sources. Where a topic stops short of implementation depth, that is a deliberate coverage decision, not an oversight — see coverage.