European companies expanding into Australia or New Zealand arrive with a reassuring assumption: the Anglo-Saxon business culture, the English language, and the region’s technological maturity should make ERP deployment straightforward. In practice, the opposite is true. Single Touch Payroll Phase 2 imposes a payroll reporting granularity that has no equivalent anywhere in the OECD. SuperStream converts pension contributions into complex electronic data flows. E-invoicing via Peppol is jointly governed by both countries under a shared authority. And the leading local vendors — TechnologyOne, MYOB Acumatica, and Epicor Pronto — are virtually unknown to IT departments in Europe.
This guide covers the non-negotiable compliance requirements, the vendors you need to know, and the three ERP strategies that mid-market European companies adopt to align their ANZ subsidiary with their group information systems.
Australia and New Zealand: Two Mature but Distinct ERP Markets
Australia is the second-largest economy in Asia-Pacific, with 26 million people and a GDP of around AUD 2.2 trillion. New Zealand, with 5 million people, is a smaller but equally digitised market. The two countries share close economic ties (the Closer Economic Relations agreement since 1983), advanced digital infrastructure, and a tax culture built around real-time self-reporting.
Tax Specifics That Shape the ERP Market
GST (Goods and Services Tax) applies at 10% in Australia and 15% in New Zealand. These different rates mean any multi-entity ANZ ERP must manage two separate tax configurations, with distinct GST codes, rates, and recovery rules for each jurisdiction.
In Australia, the periodic filing is the BAS (Business Activity Statement), which consolidates GST, PAYG withholding, and — since 2018 — payroll data via STP. In New Zealand, the equivalent is the GST return submitted to the IRD (Inland Revenue Department), with mandatory payday filing for payroll data since April 2019.
Why European ERPs Require Deep Localisation
A European ERP that is not localised for ANZ will be missing, at minimum: BAS/GST return processing with Australia-specific codes (Input Taxed, GST-free, Taxable Supply), the STP connection to the ATO’s (Australian Tax Office) API, SuperStream clearing for pension contributions, and a Peppol connector for e-invoicing. These are not optional modules: their absence exposes the company to penalties and blocks the relationship with the tax authority.
SAP, Oracle, and Microsoft Dynamics 365 all offer official ANZ localisations, but depth varies by module. Local vendors have built these requirements in natively from the outset, which explains their resilience against international competition.
Single Touch Payroll Phase 2: The OECD’s Most Granular Payroll Mandate
Single Touch Payroll (STP) is arguably the most demanding payroll reporting system in the world for businesses of any size. It requires every Australian employer to transmit payroll data to the ATO in real time, at every pay cycle.
STP Phase 1: The Foundation (2018–2019)
Phase 1, mandatory for large employers from July 2018 and for all employers from July 2019, covered the essentials: gross total salary, withholding tax, and superannuation contributions per employee. The ATO received payroll data without waiting for the annual return.
STP Phase 2: Full Disaggregation
Phase 2, which began rolling out in January 2022, goes considerably further. The ATO now requires payroll income to be disaggregated into 36 distinct categories: ordinary hours, overtime, bonuses, annual leave payments, sick leave, long service leave, car allowances, reimbursements, union deductions, voluntary super contributions, and more.
What your ERP must do. At each approved payrun, the ERP must automatically build a compliant STP2 XML file, sign it with the employer’s digital certificate, and transmit it to the ATO’s STP API via an accredited service provider (DSP, Digital Service Provider). Transmission must occur on the same day as, or no later than the day of, salary payment.
The ATO publishes the official list of STP2-certified software. Among the certified ERPs and payroll solutions: MYOB (AccountRight and Acumatica Payroll), TechnologyOne HCM, Xero Payroll, ADP Australia, Elmo, and Employment Hero. SAP and Microsoft Dynamics 365 require integration via a certified third-party DSP.
The Implications for European Mid-Market Companies
Underestimating STP2 is the first trap for IT leaders deploying a group ERP in Australia. A European ERP certified for Making Tax Digital (UK), FEC (France), or GoBD (Germany) is not automatically STP2-certified. Certification is granted by the ATO, and it is specific to the software and its version. Verifying STP2 certification for your target system before any Australian ERP project is a non-negotiable prerequisite.
SuperStream and Superannuation: Mandatory Pensions Inside Your ERP
The Super Guarantee: An Indexed Employer Contribution
The Super Guarantee (SG) is the mandatory pension contribution every Australian employer must make for each employee. The rate has increased progressively: 11% for the 2023–2024 financial year, 11.5% from 1 July 2024, and 12% from 1 July 2025 — now a fixed rate (ATO, Super Guarantee rates). This contribution applies to each employee’s ordinary time earnings, up to a quarterly cap.
The ERP must calculate the SG at the correct rate, correctly provision it in the accounts, and remit it to the fund chosen by the employee within the statutory deadlines (28 days after the end of each quarter, or 7 days for employers on a monthly frequency).
SuperStream: The Electronic Transmission Protocol
SuperStream is the government standard that mandates the electronic transmission of pension contributions. Every employer must send contribution data (unique fund identifier, member number, amount) in a standardised electronic format.
Two options exist depending on company size. SMEs use the Small Business Superannuation Clearing House (SBSCH) managed by the ATO, which consolidates payments to different funds into a single payment for the employer. Larger businesses go through a commercial super clearing house or connect directly to super funds via SuperStream protocols.
The ERP impact. The payroll module must natively generate SuperStream files (ECI, Electronic Commerce Interface format) or connect to a clearing house via API. Local vendors (MYOB Acumatica, TechnologyOne HCM) handle this natively. For international ERPs, this is a point to verify module by module.
Peppol ANBP: E-Invoicing Under Joint ANZ Governance
A Peppol Authority Shared Between Two Countries
One of the distinguishing features of the ANZ region is that Peppol governance is handled jointly by Australia and New Zealand under the ANBP (Australian and New Zealand Peppol Authority). This is one of the rare configurations globally where two separate countries share a single Peppol authority, simplifying cross-border trans-Tasman transactions.
The ATO is Australia’s Peppol authority, while New Zealand Government Procurement represents New Zealand. The shared standard is PINT A-NZ (Peppol International), which replaced the previous ANZ Peppol BIS 3.0 specification from September 2024.
A Phased B2G Then B2B Rollout
Peppol e-invoicing became mandatory for suppliers to Australian federal agencies from July 2022 (B2G). On the B2B side, Australia’s strategy is a progressive mandate by company size: large companies (revenue above AUD 100 million) had to be capable of receiving e-invoices from July 2023; medium companies (revenue between AUD 10–100 million) from July 2024; small companies from July 2025.
For companies identified by their ABN (Australian Business Number), connecting to the Peppol network requires an Access Point certified by the ATO. ERPs with a certified Peppol ANBP connector include Xero, MYOB AccountRight, SAP Document and Reporting Compliance, and Oracle Fusion.
What an ERP Must Cover
An ERP deployed for an Australian subsidiary must be able to generate invoices in PINT A-NZ format, transmit them via a certified Access Point, and — on receipt — automatically extract structured data for accounting purposes. Suppliers to the public sector who cannot issue via Peppol risk losing contracts. For a subsidiary that aims to work with local councils or Australian universities, Peppol certification is effectively mandatory.
ERP Vendor Landscape in the ANZ Market
TechnologyOne: The Australian Public Sector Champion
TechnologyOne is the most significant 100% Australian ERP vendor. Founded in Brisbane in 1987, it generated revenue of AUD 515 million in its FY2024 financial year (TechnologyOne FY2024 Annual Results), with 17% growth and ARR of AUD 470 million.
Its competitive strength. TechnologyOne dominates the Australian public sector with remarkable penetration: more than 250 local councils, 40 universities, and the major government agencies across all Australian states use TechnologyOne. This near-monopoly in the ANZ public segment is explained by deep localisations (native STP2, BAS, SuperStream, Peppol ANBP), a SaaS cloud architecture designed for public entities, and long-term client relationships. For a European mid-market company that aims to sell services to Australian councils or manages assets for the public sector, TechnologyOne is often the reference ERP imposed by the client.
Its limitations. There are few certified integrators outside Australia and New Zealand. Deploying a TechnologyOne instance from Europe is a project that requires local resources or a partnership with an ANZ integrator.
MYOB Acumatica (formerly MYOB Advanced): The ANZ Private Sector ERP
MYOB is the best-known ERP brand in Australia and New Zealand, with more than 1.2 million business customers across all products. The group’s mid-market ERP solution, previously called MYOB Advanced (and Greentree before its cloud migration), was rebranded as MYOB Acumatica in early 2024, reflecting the depth of the partnership with US vendor Acumatica.
Positioning. MYOB Acumatica targets businesses with 20 to 500 employees, with particular strength in construction, distribution, professional services, and healthcare. The solution is available as SaaS on Azure, with STP2, BAS, SuperStream, and Peppol ANBP localisations built in. Its modern interface and API-first architecture make it a natural choice for companies that want to integrate complementary SaaS tools.
Important distinction. MYOB Acumatica (formerly MYOB Advanced) is a full mid-market ERP. It should not be confused with MYOB AccountRight (SME accounting) or MYOB Business (micro-businesses): these are three distinct products within the MYOB catalogue.
Epicor Pronto: The ANZ Distribution and Manufacturing Specialist
Epicor Pronto is an ERP developed in Melbourne since the 1990s, now part of the Epicor Software portfolio. It dominates in wholesale distribution, B2B retail, and light manufacturing in Australia. Its interface is considered dated compared with cloud-native ERPs, but its installed base is solid and its mastery of ANZ specifics (Australian customs codes, BAS, distribution sector trade discounts) runs deep. For a subsidiary in distribution or manufacturing that does not require tight integration with a group ERP, Pronto is a pragmatic choice.
SAP Business One and S/4HANA: The Group Route
SAP offers an official ANZ localisation for Business One and S/4HANA. The localisation covers BAS, GST, PAYG Withholding, and STP2 support via certified DSP partners. In Australia, active SAP partners in the mid-market segment include Leverage Technologies, Mindware, and Clientele. For a European mid-market company already running SAP S/4HANA, deploying an Australian instance with the official SAP localisation is the most coherent approach — provided sufficient budget is allocated for STP2 and SuperStream customisation.
Oracle NetSuite: The Platform of Choice for International Subsidiaries
Oracle NetSuite has an official ANZ localisation covering GST, BAS, STP2 (via certified DSP partner), and Peppol compliance. Its strength is being the same platform used by many US and European mid-market companies for their international entities: a group that deploys NetSuite in France, the US, and Germany can extend to an ANZ instance without changing platforms. This is the central argument that makes NetSuite the preferred choice for Australian subsidiaries of international groups seeking multi-site consistency.
Microsoft Dynamics 365 Business Central: The Official AUS/NZ Localisation
Business Central has had an official localisation for Australia and New Zealand since the 2022 release. It covers GST, BAS, and core ANZ tax compliance. However, native STP2 support remains partial and frequently requires local ISV solutions such as Fenwick Software. For groups already on Microsoft 365 and Power Platform, Business Central ANZ is a natural extension of the ecosystem.
Business Activity Statement (BAS): Australian VAT Filing
The BAS is the periodic tax return that every GST-registered Australian business must submit to the ATO. Its frequency depends on annual revenue: monthly for businesses above AUD 20 million, quarterly for the vast majority of companies, and annually for the smallest.
What the ERP Must Produce
A properly configured BAS covers three areas. First, GST collected (sales) and reclaimable (purchases), with the mandatory distinction between three transaction categories: Taxable Supply (10% GST applies), GST-free (exempt, e.g. basic food items, medical care), and Input Taxed (no output GST and no input recovery, e.g. financial services, residential rentals). Second, PAYG Withholding — that is, withholding tax on salaries and on payments to contractors without an ABN. Third, since the STP integration, payroll data is automatically pre-filled in the BAS via the ATO Business Portal.
An ERP that is incorrectly configured for GST codes generates incorrect BAS returns, which can result in penalties and erroneous refunds. Verifying the GST configuration (especially for mixed taxable/GST-free activities) is a critical checkpoint during initial deployment.
New Zealand Specifics
In New Zealand, the equivalent of the BAS is the GST return submitted to the IRD. GST is 15% there, and the deduction rules differ slightly. An ERP deployed across ANZ must manage both regimes independently, with separate entities for the Australian subsidiary (ABN) and the New Zealand subsidiary (NZBN).
ERP Strategy for European Companies with an ANZ Subsidiary
Mid-market European companies operating or expanding in ANZ face three typical scenarios, depending on the size of their subsidiary, their sector, and their degree of integration with the group information systems.
Option A: Localised Group ERP
For subsidiaries with revenue above AUD 50 million. SAP S/4HANA and Microsoft Dynamics 365 Finance offer official ANZ localisations. This option ensures group reporting consistency, native consolidated accounting, and a unified financial chain. It requires significant integration investment (STP2 via DSP, SuperStream via commercial clearing house, Peppol via certified Access Point) and demands local consultants for the regulatory modules.
Option B: NetSuite ANZ as a Group Satellite Instance
For growing international groups. Oracle NetSuite makes it possible to unify global entities on a single platform while activating per-country localisations. The ANZ subsidiary benefits from the official localisation, and consolidation with European entities runs through the NetSuite OneWorld module. This is the solution adopted by many SaaS and professional services mid-market companies operating simultaneously in Europe, North America, and ANZ.
Option C: MYOB Acumatica or TechnologyOne as an Autonomous Local ERP
For highly autonomous subsidiaries or those in the public sector. When the ANZ subsidiary operates in a sector dominated by local vendors (councils, universities, construction, wholesale distribution), aligning with the sector’s ERP is often more pragmatic than imposing a group ERP. The subsidiary deploys MYOB Acumatica or TechnologyOne, with point-to-point integration to the group’s financial consolidator (SAP Analytics Cloud, IBM Cognos, or even a monthly CSV extract into the group’s reporting layer).
Comparison of the Three Options
| Criterion | Option A (Group ERP) | Option B (NetSuite ANZ) | Option C (MYOB / TechOne) |
|---|---|---|---|
| Deployment cost | High (AUD 300K–800K) | Medium (AUD 150K–350K) | Low to medium (AUD 80K–250K) |
| Timeline | 12–18 months | 6–12 months | 4–9 months |
| STP2 compliance | Via third-party DSP | Via certified DSP | Native |
| Group IS integration | Native | Good (API) | Limited (export/import) |
| ANZ public sector | Possible | Possible | Strong (TechnologyOne) |
| Local autonomy | Low | Medium | High |
The Time Zone Factor
One frequently overlooked point: ANZ subsidiaries operate between UTC+8 (Western Australia) and UTC+13 (New Zealand summer time). ERP synchronisation with European group systems must handle offsets of 8 to 13 hours. Month-end closings, intercompany reconciliations, and EDI transmissions all need to be scheduled with these offsets in mind to avoid month-end bottlenecks.
For further reading on managing international subsidiaries, see our complete guide to IT structure for international expansion and our analysis of the UK ERP market post-Brexit, which covers another English-speaking market with strong regulatory requirements. If your expansion also touches Latin America, our Brazil ERP guide: SPED, NF-e and fiscal compliance covers the compliance obligations of another market with comparable complexity.
