Australian bookkeepers running ERPNext hit the same wall every quarter: the system tracks tax on transactions, but it does not speak the ATO's language. There is no native BAS worksheet that maps your GST to labels 1A, 1B, G1, W1 and W2, no PAYG withholding scaffolding, and — the daily pain — no way to pay a batch of suppliers or staff without keying each line into internet banking. ERPNext core gives you tax templates and a general ledger, but the reconciliation from your ledger to a lodgement-ready BAS, and from a payment run to a bank-accepted file, is manual, spreadsheet-driven and error-prone.

ECOSIRE builds a proper Frappe app — its own module, DocTypes, permissions and hooks.py doc events — that closes that gap on top of your existing ERPNext. We ship ATO-aligned GST tax templates and tax categories (GST, GST-Free, Input Taxed, Export) wired to the correct tax codes, plus a BAS Report DocType and Query Report that aggregate the period's sales and purchase tax into the exact BAS labels, so a bookkeeper can reconcile against the GL before lodging. PAYG withholding accounts and tax codes are configured so wages and withheld amounts flow into W1/W2. ABN capture and checksum validation are added to Customer and Supplier via a Client Script plus a whitelisted server method, so an invalid ABN is caught at data entry rather than at audit.

The ABA (Australian Bankers' Association direct entry) file generator is the centrepiece. From a Payment Entry batch or a selection of outgoing payments, a controlled server-side method builds a compliant ABA file — descriptive record (type 0), detail records (type 1) with BSB, account number, transaction code, amount, lodgement reference and trace BSB/account, and the file total record (type 7) with hash totals and record counts. The file is validated (BSB format, 6-digit amounts in cents, record-length rules), attached to the source document, and made available for download to upload straight into your bank. All of it runs on Frappe/ERPNext v15/v16, honours role-based permissions and multi-company setups, and exposes whitelisted methods so the same logic can be triggered from the REST API or a scheduler event for recurring pay runs.

Because this is build-to-order, nothing ships as a blind download. We start with a short scoping call to confirm your bank's ABA dialect (banks differ on the balancing record and self-balancing flag), your chart of accounts, your GST and PAYG setup and your ERPNext version. We build against a staging copy of your data, run UAT with you generating a real BAS reconciliation and a test ABA file your bank accepts, then install on production with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope. You receive the full source as an installable Frappe app in a git repository you own, so there is no lock-in.