Simple. Secure. Seamless.
Part of the Singapore LEI knowledge hub — back to the Singapore pillar.
LEI in SWIFT Messaging in Singapore connects with the SWIFT BIC through the BIC-to-LEI mapping, linking an institution's messaging identifier with its legal-entity identifier for correspondent banking and financial workflows.
A BIC identifies an institution or business party for financial messaging and transaction routing, while an LEI identifies the legal entity. The GLEIF and SWIFT BIC-to-LEI mapping allows the two identifiers to be linked and cross-referenced.
Linking a BIC with an LEI helps banks and financial institutions connect messaging information with standardised legal-entity data. This supports counterparty identification, KYC, reconciliation and due-diligence workflows.
ISO 20022 supports structured legal-entity identifiers, including the LEI, in relevant organisation-identification fields. In cross-border payments, an LEI can complement other party information when supported by the applicable message and implementation requirements.
Apply for your LEI
Transfer (free)
Renew
Get your LEI
Fast-Track LEI issuance in 2 to 4 UK working hours is available subject to data completeness, applicant authority, and successful compliance validation. Transfers from another GLEIF-accredited LOU are free.
No — the BIC is a messaging code; the LEI identifies the legal entity. They are mapped together.
To connect messaging identity to verified legal identity for screening and trust.
Yes — in structured party data.
Yes. A financial institution can have both identifiers because they perform different functions. The BIC supports financial messaging and routing, while the LEI identifies the underlying legal entity.