Direct Debit Request (DDR/BECS)
Detects direct debit requests, BECS authorizations, and recurring payment arrangements under Australian banking standards.
- Type
- keyword_list
- Confidence
- medium
- Confidence justification
- Medium confidence: keyword-based detection requires corroborative evidence for accurate identification.
- Jurisdictions
- global
- Regulations
- AML/CTF Act (Cth), IPA 2009 (Qld), NDB Scheme (Cth), Privacy Act 1988 (Cth), SOCI Act 2018 (Cth)
- Frameworks
- ISO 27001, ISO 27701, PCI-DSS, SOC 2
- Data categories
- financial, banking
- Scope
- narrow
- Risk rating
- 8
Should match
Direct debit request received— Exact 65 discovery probe with a mandate phrase and no account or schedule detailsDirect debit request: BSB 062000— Exact 75 probe with one banking-detail evidence familyDirect debit request: BSB 062000, first debit date 01/03/2026— Exact 85 probe with banking authority and payment schedule evidenceDirect Debit Request: I authorise debit my account— Direct debit authority wordingDDR/BECS form with BSB and account number details— Test match 2Recurring debit arrangement with first debit date 01/03/2026— Test match 3
Should not match
Credit card payment processed successfully— Non-match 1Please debit the inventory count— Non-match 2User ID: 123456 architecture workshop— BECS-shaped user identifier in technical prose without mandate or payment details
Known false positives
- Use of debit in general accounting contexts. Mitigation: Require DDR, BECS, or bank authority language alongside debit terms.