Whole-of-Government ERP Payment Authorisation File
Detects bulk payment authorisation files extracted from government ERP systems (SAP, Oracle, TechnologyOne) containing payee bank accounts, payment amounts, and authorisation codes for batch processing.
- Type
- regex
- Engine
- universal
- Confidence
- high
- Confidence justification
- High confidence: ABA/BECS file format patterns combined with ERP system context and payment authorisation markers are highly specific to government payment files. The structured fixed-width format is distinctive.
- 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
\b0\s{6,}.{0,20}\d{3}-\d{3}Corroborative evidence keywords
payment file, ABA file, BECS, direct entry, batch payment, EFT file, authorised, approved, certified, released for payment, SAP, Oracle, TechnologyOne, ERP, payment run, remittance, financial, fiscal, monetary, accounting (+26 more)
Proximity: 300 characters
Should match
PROTECTED — ERP Payment Authorisation File. Source: SAP Payment Run PR-2026-0451. Batch payment file (ABA format) authorised for processing. Contains 1,247 payment records totalling $34,567,890.45. BSB/Account details for all payees included. Dual authorisation: Approved by J. Smith and B. Williams. Released for BECS direct entry.— SAP payment authorisation file with batch details0 064-000Department of Health 0123456Payment File 280226 1064-000 12345678 530000003450000Employee Payment J Smith 064-000 98765432 1084-004 87654321 530000004520000Employee Payment M Jones 084-004 11223344— Raw ABA file format with header and payment recordsPROTECTED — Oracle ERP batch payment authorisation. Payment run reference PR-2026-1180 certified and released for payment. ABA file generated for BECS direct entry covering 842 payee records. Dual authorisation: approved by the Director of Finance.— Oracle ERP bulk authorisation file with payment run reference
Should not match
Payment request form. Please approve a single payment to Supplier ABC Pty Ltd against the attached invoice. This is an individual payment request, not a bulk authorisation or batch file.— Individual payment request prose — not a bulk authorisation file, no ABA records or BSBABA file format specification. The Type 0 record contains the header with BSB, account name, and file description. Used for training purposes.— ABA file format documentation — training materialERP payment template. Enter the payee BSB and account number in the highlighted fields before submitting. Training example only — no live banking values populated.— Placeholder ERP template prose with no populated BSB or account values
Known false positives
- Individual payment requests and purchase order approvals Mitigation: Require bulk indicators (batch, multiple records, payment run) rather than single payment context
- ABA/BECS file format specifications and training documentation Mitigation: Exclude documents containing 'specification', 'format guide', 'training', 'example file' without real payment data
- Placeholder BSB/account values in ERP templates or testing artefacts. Mitigation: Exclude all-same-digit and trivial sequential payment identifiers.