Bank routing numbers

Detects references to bank routing numbers in financial and compliance documents. Commonly found in Australian regulatory filings, transaction records, and audit documentation.

Type: regex
Engine: boost_regex
Confidence: medium
Confidence justification: identifier/document-structure anchored regex with constrained context replaces phrase-only detection. Added context gating and exclusion rules improve precision and reduce incidental matches.
Detection quality: Topic false positive
Jurisdictions: global
Regulations: AML/CTF Act (Cth), IPA 2009 (Qld), NDB Scheme (Cth), Privacy Act 1988 (Cth), SOCI Act 2018 (Cth), GDPR, PCI-DSS
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: Compatible, Netskope: Unsupported

Pattern

\b\d{3}-\d{3}\b|\b(?:routing\s+number|ABA|RTN)\b[\s:#-]{0,20}\d{9}\b

Corroborative evidence keywords

bank routing numbers, bank, routing, numbers, financial, accounts, payments, bank account, account number, account no, [object Object], routing number, sort code, IBAN, SWIFT, [object Object], file number, reference number, case number, record number (+19 more)

Proximity: 300 characters

Should match

062-000 — Australian BSB (3-3)
Routing number: 021000021 — Labelled US ABA routing number
BSB 083-004 — BSB with label

Should not match

12345 — Too short
1234567 — Not a routing format
template example placeholder — Template/sample text

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.