Bank Account with Payment Authorisation Token

Detects government bank account details (BSB + account number) combined with payment authorisation credentials, approval tokens, or signing authorities that together enable the initiation of payments.

Type: regex
Engine: universal
Confidence: medium
Confidence justification: Medium confidence: BSB + account number + payment authorisation credentials is a highly specific combination. The requirement for authorisation context (not just banking details) distinguishes this from routine SENS_Fin BSB detection.
Detection quality: Error
Jurisdictions: au
Regulations: Financial Accountability Act 2009 (Qld)
Frameworks: QGISCF
Data categories: financial, government
Scope: wide
Risk rating: 8
Platform compatibility: Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Compatible, Netskope: Compatible

Pattern

\b\d{3}-?\d{3}\b

Corroborative evidence keywords

authorisation, authorised, approval, approved, signing authority, payment token, EFT, batch payment, BECS, direct entry, ABA file, payment instruction, bank account, BSB, financial, fiscal, monetary, accounting, treasury, audit (+24 more)

Proximity: 300 characters

Should match

PROTECTED — Payment Authorisation File. BSB: 064-000, Account: 12345678. Payment token: AUTH-2026-00451. Authorised signatory: J. Smith (Delegate Level 3). Batch payment approved for $2,450,000 via BECS direct entry. Released for processing. — Payment authorisation with BSB, account, and approval token
EFT Payment Instruction — PROTECTED. Account BSB 084-004 Account No 98765432. Signing authority: Dual authorisation required. First approver: A. Jones (approved). Second approver: B. Williams (approved). Payment amount: $890,000. ABA file generated. — Dual-authorised payment with BSB and signing authority
PROTECTED — Batch payment authorisation. BSB: 032-001, Account: 45678901. Authorised signatory: K. Brown (Delegate Level 4). Payment token: AUTH-2026-00872. Released for processing via BECS direct entry. — Batch payment with BSB, account, and approval token
BSB 032-001 Account 45678901; dual authorisation by K Brown and S Tran; ABA file released for processing. — Account number plus dual authorisation and release evidence satisfy the non-token enforcing branch

Should not match

Please update your bank details for salary payments. BSB: ___ Account: ___. Submit to HR with a void cheque or bank statement. — Blank bank details form — no authorisation context
Supplier registration: Company ABC Pty Ltd. Please provide your bank details on the attached form for accounts payable setup. No banking numbers recorded yet. — Routine supplier onboarding prose with no BSB, account, or token values
Pay your fee to BSB 064-000 account 12345678. — Inbound payment instruction — pay-your exclusion applies and there is no authorisation evidence
Example: BSB 111-222 account 12345678 AUTH-2026-0001. — Example-prefixed training text — noise exclusion overrides credential-shaped content
BSB 064-000 payment BSB payment. — BSB with repeated generic payment words — no account number or authorisation path, so no enforcement
Accounts receivable reconciled yesterday's customer deposits. — Routine financial operations with no BSB, account number, or authorisation content

Known false positives

Routine bank detail collection forms for HR or accounts payable Mitigation: Require authorisation/approval context (not just BSB + account) to distinguish from SENS_Fin patterns
Published banking details for government payment receipt (e.g., fine payments) Mitigation: Exclude documents containing 'pay your', 'payment to government', 'revenue account' indicating inbound payments