SWIFT or BIC codes

Detects references to SWIFT or BIC codes in financial and compliance documents. Commonly found in Australian regulatory filings, transaction records, and audit documentation. Phrase-level payment-rail concept detection anchored on explicit SWIFT/BIC vocabulary; it does not parse 8- or 11-character BIC values.

Type: regex
Engine: boost_regex
Confidence: medium
Confidence justification: category-aware structural regex with anchor and context constraints replaces phrase-only detection.
Detection quality: Topic false positive
Jurisdictions: global
Regulations: Anti-Money Laundering and Counter-Terrorism Financing Act 2006 (Cth), Information Privacy Act 2009 (Qld), NDB Scheme (Cth), Privacy Act 1988 (Cth), GDPR
Frameworks: ISO 27001, ISO 27701, PCI-DSS, SOC 2
Data categories: financial
Scope: wide
Risk rating: 4
Platform compatibility: Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?is)\b(?:SWIFT\s+code|BIC\s+code|bank\s+identifier\s+code|SWIFT\s+network)\b

Corroborative evidence keywords

swift or bic codes, swift, bic, codes, financial, accounts, payments, bank account, account number, account no, [object Object], routing number, sort code, IBAN, SWIFT, [object Object]

Proximity: 300 characters

Should match

SWIFT code — Primary topic phrase match
bic code — Case-insensitive topic phrase match
bank identifier code — Alternative topic phrase match
SWIFT network — Additional topic phrase match
SWIFT code: Recorded Payee: Avery Teston Account number: 12345678 — Populated attribute field with a linked record field (85 tier)

Should not match

unrelated generic text without domain phrases — No relevant topic phrases present
placeholder value 12345 — Random text should not match topic-specific regex
bank transfer — Generic word pair from old broad template should not match
Domestic routing code changed. — Generic routing-code wording demoted out of the primary - no SWIFT/BIC linkage
correspondent bank arrangements — Correspondent-bank wording demoted out of the primary - corroborative evidence only
wire transfer approval — Generic payment wording demoted out of the primary
SWIFT code: Payee: Account name: Account number: — Empty form: the heading and field labels without values must not corroborate themselves (discovery only)
Policy guidance: this procedure explains how records about swift code are handled, who may access them and how long they are kept. It contains no records about any person or system. — Policy guidance naming the topic without any record (discovery only)
SWIFT code: Payee: Avery Teston — Record with the attribute label but no value: the label must not corroborate itself (discovery only)

Known false positives

Financial terminology appearing in published reports, accounting textbooks, regulatory guidance, or template documents without actual transaction data. Mitigation: Require corroborative evidence keywords within the proximity window. Cross-reference with structured financial identifiers to confirm actual sensitive data.
In Australian English, standard business terminology overlapping with financial detection keywords in routine correspondence and documentation. Mitigation: Increase confidence threshold when scanning business correspondence. Layer with transaction-specific patterns for higher precision.