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 plus account number plus payment-authorisation context is a specific combination; authorisation references are system-specific, so the token is a documented label-anchored fallback.
- 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: PT88205531. 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 (reaches 85)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 (reaches 85)PROTECTED — Batch payment authorisation. BSB: 032-001, Account: 45678901. Authorised signatory: K. Brown (Delegate Level 4). Payment token: PT88207720. Released for processing via BECS direct entry.— Batch payment with BSB, account, and approval token (reaches 85)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 (reaches 85)Payment release record BSB 064-000 Account 12345678 Payment token: PT88205531— BSB + account + labelled payment token, no payment-method or marker evidence (reaches 75)
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 contextSupplier 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 valuesPay your fee to BSB 064-000 account 12345678.— Inbound payment instruction — pay-your exclusion applies and there is no authorisation evidenceExample: BSB 111-222 account 12345678 payment token PT00000001.— Example-prefixed training text — noise exclusion overrides credential-shaped contentBSB 064-000 payment BSB payment.— BSB with repeated generic payment words — no account number or authorisation path, so no enforcementAccounts receivable reconciled yesterday's customer deposits.— Routine financial operations with no BSB, account number, or authorisation contentPolicy: payments above $50,000 need dual authorisation by two financial delegates before the ABA file is released for processing via BECS direct entry.— Finance policy guidance naming the controls without any account details (must stay below 75)Payment release form BSB: ______ Account number: ________ Payment token: ________ Authorised signatory: ________— Blank payment release form (must stay below 75)
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