Skip to content

Australian ABA file viewer and validator

Inspect Australian AusPayNet Cemtex .aba Direct Entry files locally: verify 120-character widths, BSBs, and Type 7 totals.

Drop an Australian 120-character .aba file here

Validates 120-char Cemtex fixed widths, NNN-NNN BSBs, 6-digit APCA ID, DDMMYY dates, and Type 7 999-999 control totals.

Loads a synthetic Cemtex payment & self-balancing run.

How to use ABA file viewer

  1. Load an ABA batch file. Drag a .aba or .txt file into the drop sheet, click Choose ABA file, or click Load sample ABA file to inspect the Harbor Direct Entry sample.
  2. Check header and line diagnostics. Read the PASS badge alongside the FI mnemonic, 6-digit APCA ID, and DDMMYY date, then review any line-numbered ERROR or WARNING rows.
  3. Review parsed entries and totals. Inspect the 300-row table for red BSB alerts or Self-bal Code 13 tags alongside AUD totals in the sidebar.
  4. Export your ABA report. Keep Excel workbook (.xlsx) or switch to Transactions CSV (.csv), adjust the account masking checkbox if required, and click Export ABA report.

Everything you type stays in this browser on your device. Nothing is uploaded, and your saved details are never sent anywhere.

Understanding Australian 120-character Cemtex ABA file layouts

Direct Entry batch submissions in Australia exchange payroll, supplier, and collection instructions inside fixed-width plain-text rows. When you validate an Australian ABA bank file offline, the Web Worker decodes UTF-8 or Windows-1252 files up to 25 MB and verifies that every non-empty row spans exactly 120 bytes.

Maintained across the AusPayNet Direct Entry resource center, the Cemtex layout divides every file into three record tiers: a Type 0 descriptive header, Type 1 or Type 2 detail entries, and a Type 7 file trailer. Files missing Type 0, Type 1/2, or Type 7 records raise immediate structural errors.

Type 0, Type 1, Type 2, and Type 7 byte positions

Checking fixed 1-based byte positions guarantees ERP exports did not truncate trailing spaces or corrupt field alignment inside a 120 character ABA file. Any non-empty row deviating from 120 bytes emits a line-numbered RECORD_LENGTH error before your bank gateway rejects the upload.

Record / Bytes Field name Length Local validation rule applied
Type 0 (21-23) FI mnemonic 3 Checks uppercase letters (FI_MNEMONIC warning if absent)
Type 0 (57-62) APCA User ID 6 Must contain 6 numeric digits (APCA_ID error)
Type 0 (75-80) Processing date 6 Valid calendar DDMMYY resolved to ISO 8601
Type 1/2 (2-8) Target BSB 7 Hyphenated NNN-NNN format (BSB_FORMAT error)
Type 1/2 (19-20) Tx code 2 Accepts 13 and 50 through 57 Cemtex codes
Type 1/2 (21-30) Amount in cents 10 Zero-padded integer cents formatted in AUD
Type 7 (2-8) Control marker 7 Requires exact 999-999 sentinel plus totals

Header validation also verifies that only one Type 0 descriptive line exists (MISSING_HEADER or DUPLICATE_HEADER) and confirms a non-blank 26-character User Supplying File name at positions 31-56. Detail lines also require non-empty alphanumeric accounts up to nine characters rather than blank or all-zero placeholders.

Checking supplier ABNs before releasing Direct Entry runs

Validating fixed-width syntax prevents file upload rejections, yet invoice compliance starts before assembling vendor bank instructions. Before generating supplier payment batches from new creditor onboarding forms, validate 11-digit supplier ABNs before Direct Entry runs to confirm ATO Modulo-89 checksums locally.

How do BSB checks, self-balancing rows, and Type 7 trailers work?

Offline validation inspects six-digit hyphenated routing codes, Type 13 offset entries, and file-end control totals inside a local browser worker. Passing every check displays ABA Cemtex checks PASS alongside the header FI mnemonic, APCA ID, and DDMMYY date, while errors highlight exact line numbers.

NNN-NNN BSB rules, APCA IDs, and DDMMYY calendar checks

To check NNN-NNN BSB and 6 digit APCA ID rules properly, the validator verifies hyphen placement across bytes 2-8 for primary BSBs and bytes 81-87 for trace BSBs. Invalid BSB entries display in red bold inside the table, while calendar validation rejects impossible DDMMYY dates such as 310226.

While structural checking catches dropped hyphens or malformed digits offline, confirming an active branch number requires an authoritative online lookup. Use the AusPayNet Public BSB Lookup directory when onboarding new suppliers or troubleshooting closed BSB numbers returned by your bank.

Self-balancing Code 13 offsets and UK clearing comparisons

Many accounting suites emit a self balancing code 13 ABA entry to debit your own clearing account for the sum of outgoing credit rows. This parser detects Self-bal entries automatically whenever transaction code 13 pairs matching destination and trace BSB/account coordinates.

To fix a Type 7 999-999 trailer mismatch in ABA exports, inspect sidebar metrics for Detail records, Credit total (AUD), Debit total (AUD), and Net total (AUD). Type 7 errors flag discrepancies in declared net cents (|credit - debit|), credits (31-40), debits (41-50), or six-digit row counts (75-80).

Treasury teams handling multi-country payroll batches across Commonwealth clearing networks often compare Australian fixed-width batches with UK submissions. Open the BACS file checker to audit 100-character Pay.UK Standard 18 payroll files using similar debit-credit offset logic.

Exporting Excel audit workbooks or RFC 4180 CSV summaries

Finance reviewers can archive parsed Direct Entry runs either as multi-tab spreadsheets or flat comma-delimited tables. By default, Excel workbook (.xlsx) is selected under Export format alongside enabled **Mask account numbers (**1234) masking so sign-off packs protect employee account numbers.

Reading transaction codes, withholding flags, and 300-row previews

Built-in rules translate all nine ABA transaction codes 13, 50, 51, 52, 53, 54, 55, 56, and 57, separating supplier payments (50), payroll salaries (53), dividends (56), and debits (13). Withholding indicators at byte 18 (blank, N, W, X, Y) and Type 2 tax cents (113-120) parse cleanly.

As documented in the Reserve Bank of Australia Payments System overview, Direct Entry handles high-volume domestic batch settlement across Australian depository institutions. Inside the browser table, on-screen rows cap at 300 entries to preserve responsive scrolling while exports include all parsed records.

Three-sheet XLSX outputs versus 14-column CSV downloads

Teams looking to export an ABA file to Excel or CSV with masked accounts can choose between two structured downloads via Export ABA report. Excel workbooks separate Transactions, Header & Control Totals, and Validation Issues across three worksheets for clean internal audit review.

Choosing Transactions CSV (.csv) builds a 14-column RFC 4180 comma-delimited spreadsheet prefixed with a UTF-8 Byte Order Mark and CWE-1236 formula escaping (=+@-|). Bookkeepers migrating older accounting histories alongside batch summaries can also use the Quicken QIF ledger spreadsheet converter locally.

Browser-only privacy, compliance scope, and treasury limits

Australian supplier bank account records, salary runs, and APCA identifiers remain confidential throughout validation. Because the Web Worker loads only after file selection and computes every check inside your browser tab, 100% of file bytes stay strictly offline with zero server logging.

Before processing sensitive payroll runs, click Load sample ABA file to inspect harbor-direct-entry.aba featuring a CBA header, APCA 301500, codes 50 and 53, a Self-bal code 13 row, and 999-999 control trailers. Review Australian Government payments and invoicing guidance for broader commercial record-keeping rules.

Tip: Confirm your Type 0 DDMMYY processing date against your bank’s daily Direct Entry cutoff before uploading .aba files, and keep **Mask account numbers (**1234) checked whenever emailing Export ABA report workbooks for approval.

Multinational accounting desks reconciling US corporate bank statements alongside Australian Direct Entry payroll can run private US BAI2 statement parsing without server uploads inside the same zero-network browser toolkit.

This ABA file viewer validates 120-character Cemtex syntax, BSB patterns, and Type 7 arithmetic for informational purposes only and does not constitute accounting, tax, payroll, or financial advice. Verify live BSB branch status, APCA User ID activation, and statutory obligations with your bank and a qualified accountant.

Questions

Why must every line in an ABA file measure 120 characters?

Australian Cemtex Direct Entry uses fixed-width positioning without field delimiters, so banks split BSBs, amounts, account titles, and lodgement references by exact column index. Any non-empty row shorter or longer than 120 characters shifts subsequent fields and triggers a RECORD_LENGTH error.

What is a self-balancing Type 13 record in an ABA batch?

A self-balancing record is an externally initiated debit using code 13 whose BSB and account number match the Trace BSB and Trace Account fields. Banks pair that offset debit against credit payments so the net total on the Type 7 trailer balances cleanly.

Does this viewer confirm that a BSB number is active at an Australian bank?

No. Offline validation checks that both primary and trace BSB strings match the hyphenated NNN-NNN six-digit format and flags invalid patterns in red bold text. You must query AusPayNet or your business bank portal to confirm live branch status.

What does the 999-999 code on a Type 7 ABA record check?

Type 7 trailers always carry 999-999 in bytes 2 through 8 to signal the end-of-file control summary. This validator reconciles the declared net total, total credits, total debits, and 6-digit detail row count against computed Type 1 and Type 2 entries.

What sheets and columns appear in the exported Excel or CSV ABA report?

Excel workbook (.xlsx) exports three tabs named Transactions, Header & Control Totals, and Validation Issues. Switching to Transactions CSV (.csv) creates a 14-column UTF-8 BOM spreadsheet detailing Record Type, Tx Code, Direction, BSB, masked Account Number, Account Title, AUD Amount, Lodgement Reference, Trace details, Remitter, and Self-Balancing status.

Does this ABA file viewer upload supplier or payroll details anywhere?

No. Decoding, line-width checks, Type 7 arithmetic, and spreadsheet downloads run locally inside a Web Worker tab on your machine. Zero bytes of account numbers, BSBs, or salary amounts ever leave your browser.

Updated