Every ERP sold in Australia will tell you it’s “ATO-compliant”. The truthful version has tiers — and the tier decides your project cost.
Native = built into the core product. Add-on = certified third-party product required. Partner = handled via connected products or localisation packs. Everything in this table should be re-verified with the vendor for your version and modules before you sign; certifications and product scopes change.
| System | STP Phase 2 payroll | GST / BAS | SuperStream · PEPPOL |
|---|---|---|---|
| MYOB Acumatica | Native | Native | Native · Via localisation |
| Wiise | Native | Native | Native · |
| TechnologyOne | Native | Native | Native · Supported |
| Pronto Xi | Native | Native | Native · Supported |
| Business Central | Add-on | Native (AU localisation) | Via add-on · Native (PINT A-NZ) |
| NetSuite | Add-on/connected payroll | Native tax engine | Via add-on · Via partner |
| SAP Business One | Add-on | Native (localisation pack) | Via add-on · Via partner |
| Sage Intacct | Partner payroll | Supported | Via partner · Via partner |
| Odoo | AU payroll | Native localisation | · |
| Epicor Kinetic | Partner | Localisation | Via partner · Via partner |
| SYSPRO | Partner | Localisation | Via partner · Via partner |
| SAP S/4HANA | Via SAP/partner payroll | Native | Supported · Native |
Top 20 ERP Software Report — independent vendor comparison with pricing and best-fit segments.
Single Touch Payroll Phase 2 is the hard one; it’s the reason this article splits vendors into native and add-on. Phase 2 requires payroll data disaggregated to the ATO’s taxonomy (income types, cessation reasons, itemised allowances, salary sacrifice) reported every pay event. A system either has an ATO-whitelisted payroll engine or it doesn’t; “we integrate with payroll providers” means the compliance burden lives in the integration. That’s fine, as long as you’ve scoped and priced it as real work.
Table stakes, but quality varies wildly. The test isn’t whether the system “supports GST” (everything does); it’s whether it produces a BAS your agent can lodge without a spreadsheet intermediary: correct label mapping (G1–G20, 1A/1B), mixed-supply handling, and RCTI support if you use them. Ask to watch a BAS prepared end-to-end in the demo. The vendors who can’t, won’t.
Super contributions must flow through the SuperStream standard, in practice via a clearing house or an integrated payroll engine’s gateway. Native-payroll systems bundle this; add-on arrangements inherit whatever the payroll add-on provides. Confirm who pays the clearing house fees and how choice-of-fund data is captured.
If you’re in building and construction, cleaning, couriers, IT or security services, the Taxable Payments Annual Report needs contractor payment data tagged all year; retrofitting it in June is painful. Check the system flags reportable contractors at supplier level, rather than leaving you to dig back through a year of transactions.
Australia’s e-invoicing standard, driven by government procurement and spreading into the private sector. Today it’s an advantage; the direction of travel suggests it becomes an expectation. The question for every vendor: “Who is your PEPPOL access point, and is it included or priced separately?” Plenty of the sales teams we’ve spoken with can’t answer it yet.
For how compliance fit ranks against the other selection criteria (partner strength, cost, industry fit), see the full Australian ERP comparison.
Capability classifications come from each vendor’s published documentation and the ATO’s published STP Phase 2, SuperStream and PEPPOL material, checked 7–8 August 2026. Where capability changed recently we re-verified against current docs (Business Central’s PEPPOL PINT A-NZ support is now native via Microsoft’s E-Documents framework; Odoo’s STP Phase 2 compliance applies from version 19). Add-on classifications mean the platform vendor does not ship the capability itself; the certified partner product carries the compliance. No vendor sponsored or reviewed this page.
MYOB Acumatica, Wiise, TechnologyOne and Pronto Xi include ATO-compliant STP Phase 2 payroll in the core product. Business Central, NetSuite, SAP Business One and Sage Intacct rely on certified payroll add-ons or connected AU payroll products. For Odoo and other global platforms, confirm certification for the specific version you would deploy.
For GST and BAS, yes: the native tax engine handles Australian requirements. Payroll (STP Phase 2, SuperStream) runs through localised third-party payroll products, so compliance depends on the add-on you pair with it.
Not natively. The AU localisation covers GST and BAS; STP Phase 2 payroll comes from certified add-ons or connected payroll products, which is a real scope and cost line in any Business Central project.
Not for businesses generally, but Commonwealth agencies are required to receive e-invoices, adoption is expanding through government supply chains, and vendors’ PEPPOL readiness is now a fair selection criterion.
SuperStream is the mandatory data-and-payment standard for super contributions. Your ERP needs it only if it runs payroll; native-payroll systems bundle a gateway, add-on arrangements inherit the add-on’s.