Australian Bulk Payment File (ABA Direct Entry, BPAY Batch or EFT Upload)

Bulk payment files prepared for upload to a bank: ABA / Cemtex Direct Entry files in the BECS fixed-width format, BPAY batch files and delimited EFT payment uploads. The ABA format has a descriptive record (type 0), one detail record per payment (type 1: BSB, account number, transaction code, amount in cents, account title and lodgement reference) and a file total record (type 7: 999-999 with net, credit and debit totals and a record count). An EFT upload is a delimited file of BSB, account and amount columns; a BPAY batch lists biller codes, customer reference numbers (CRNs) and amounts. A payment file holds many payees' bank accounts and amounts in the exact form the bank will process, so altering one line diverts a payment. This SIT anchors on the payment lines (type 1 detail records, delimited BSB/account/amount rows and labelled biller code / CRN lines), not on the type 0 header. whole-of-government-erp-payment-authorisation-file anchors on the type 0 header with ERP and authorisation context; a complete government ABA file can match both. A single set of bank details on an invoice or form does not match.

Type
regex
Engine
boost_regex
Confidence
medium
Confidence justification
Medium. The ABA type 1 detail record is a rigid 120-character layout (BSB, account field, transaction code, 10-digit amount) that rarely occurs outside payment files, and delimited rows need a hyphenated BSB beside an account number and a decimal amount. Format specifications and bank help pages reproduce worked records, so enforce tiers need a control record, header or payment-file context, and guidance framing is excluded. A delimited row can still occur in a reconciliation or supplier master extract that is not a payment file. 85/75 are heuristic evidence tiers, not measured accuracy. Test values are synthetic.
Jurisdictions
au
Regulations
Privacy Act 1988 (Cth), Information Privacy Act 2009 (Qld), Financial Accountability Act 2009 (Qld)
Frameworks
QGISCF, BECS Procedures (Australian Payments Network)
Data categories
financial, pii
Scope
narrow
Risk rating
8
Platform compatibility
Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?i)(?:\b1\d{3}-\d{3}[ 0-9-]{9}[ NWXY](?:13|5[0-7])\d{10}[A-Z0-9&]|\b\d{3}-\d{3}[ \t]{0,2}[,|\t][ \t]{0,2}"?\d{5,10}"?[ \t]{0,2}[,|\t](?:[^\n,|\t]{1,40}[,|\t]){0,3}[ \t]{0,2}"?\$?\d{1,9}\.\d{2}\b|\bbiller\s+code[ \t]{0,3}[:#]?[ \t]{0,3}\d{3,10}[ \t]{0,3}[,|;\t]?[ \t]{0,3}(?:CRN|customer\s+ref(?:erence)?(?:\s+(?:no\.?|number))?|ref(?:erence)?(?:\s+(?:no\.?|number))?)[ \t]{0,3}[:#]?[ \t]{0,3}\d{2,20}\b)

Corroborative evidence keywords

direct entry, Cemtex, BECS, ABA file, bulk payment, batch payment, payment file, EFT file, payment run, BPAY batch, lodgement reference

Proximity: 300 characters

Should match

Should not match

Known false positives

References