ABA File Converter

ABA File Validator

Validate your ABA file against the full Australian Bankers' Association direct-entry specification before uploading it to your bank. Every error and warning is listed with the exact row and field — so you fix the right thing, not guess. Free, no signup, files never leave your browser.

Source ABA file

How to use

  1. 1

    Drop the ABA file

    Drag an .aba file into the dropzone. The validator parses it and surfaces every issue immediately.

  2. 2

    Review the report

    Errors and warnings are grouped by severity. Click an item to jump to the offending row and field.

  3. 3

    Fix and re-check

    To repair the file, use the ABA Editor. To regenerate from your source spreadsheet, use the CSV or Excel converter.

Why use ABA File Converter's ABA Validator

  • Catches every spec violation before you upload to your bank.
  • Covers structure, field rules, FI codes, BSB format, and totals reconciliation.
  • Each issue links straight to the offending row and field.
  • Free, no signup, no file-size limit.

What the validator checks

The validator checks every rule in the ABA direct-entry specification:

  • Structure: exactly one Type 0 header · one or more Type 1 detail records · exactly one Type 7 total record · each record exactly 120 characters wide.
  • Field rules: BSB in NNN-NNN format · account number up to 9 digits · account name up to 32 characters · lodgement reference up to 18 characters · valid transaction code (13, 50, 53, 54, 55, 56, or 57) · amount in cents, non-negative.
  • Totals reconciliation: credit total equals the sum of all credit-type detail rows · debit total equals the sum of all debit rows · record count matches the number of Type 1 rows.
  • Warnings (non-blocking): lodgement reference starts with a space · account name contains unusual characters · processing date in the past.

Common ABA file errors

These are the most common reasons a bank rejects an ABA file:

  • Invalid BSB:The BSB is not in NNN-NNN format, or the branch does not exist in the financial institution code library. Check the BSB against your payee's bank statement.
  • Totals out of balance: The Type 7 total record does not match the sum of the detail rows. This usually happens when a row is added or removed after the file was generated. Re-generate the file from your source data.
  • Record too long or too short: A line is not exactly 120 characters. Often caused by a text editor that stripped trailing spaces or added a byte-order mark. Use the ABA File Editor to fix individual rows.
  • Account name too long: The ABA spec limits account names to 32 characters. Truncate names longer than this before generating the file.

About the ABA file format

The ABA file (sometimes called Direct Entry or Cemtex) is the fixed-width 120-character text format Australian banks accept for batch payments. Every record is exactly 120 characters; a file has one Type 0 descriptive header, one or more Type 1 detail records, and one Type 7 totals record. Read the full ABA file format spec.

Frequently asked questions

What does the validator check?

Every rule in the Australian Bankers' Association direct-entry spec: 120-character line width, allowed characters, BSB format (NNN-NNN), account number rules, valid transaction-code set, amount bounds, and Type 7 totals reconciliation.

Is the file uploaded to a server?

No. Parsing and validation run entirely in your browser; the file never leaves your device.

What's the difference between an error and a warning?

Errors are spec violations that banks will reject — the file will not download if errors are present in the editor. Warnings are advisories (such as a lodgement reference starting with a space) that may or may not cause issues depending on the bank.

Why did my bank reject the ABA file?

Common causes are an invalid or unrecognised BSB, an account name that is too long (max 32 characters), totals that do not reconcile with the detail rows, or a missing balancing record (required by some banks such as BOQ). Run the file through this validator to find the exact issue.

Can I validate a file from Xero or MYOB?

Yes. Export the ABA file from your payroll software and drop it here. Even files generated by professional software sometimes contain bank-specific quirks — validating before upload is always a good idea.

Does the validator fix errors?

No — the validator reports issues only. To fix errors, use the ABA File Editor or regenerate the file from your source spreadsheet using the CSV to ABA Converter.

Is there a file size limit for validation?

No. The validator uses virtual scrolling to display files with thousands of rows without performance issues.