Integrations

ERP eInvoicing in Australia: what Business Central, NetSuite, and Odoo buyers should test before Peppol gets urgent

A practical Australian buyer guide to Peppol eInvoicing across Business Central, NetSuite, and Odoo, with the platform checks that matter before finance teams lock in software or rollout scope.

The ATO is also keeping the topic commercially relevant. Its current guidance says businesses need to register on the Peppol network to start using eInvoicing, and its government guidance says the Australian Government is establishing eInvoicing as the default method of invoicing in government procurement for most Australian Government entities. That does not create one simple private-sector mandate tomorrow, but it does make Peppol readiness a stronger shortlist question now.

The useful question is not “does this ERP mention eInvoicing?” It is how differently Business Central, NetSuite, and Odoo document Australian Peppol readiness, external-provider dependency, and the work still left with the buyer or implementation partner.

What the Australian baseline looks like

• The ATO says businesses can get started with eInvoicing through existing eInvoicing-ready software, an eInvoicing service provider, or a free or low-cost online solution.
• The same ATO guidance says both your business and your trading partners need to connect to the Peppol network, so software capability alone is not enough.
• The government adoption page says eInvoicing is being established as the default invoicing method in government procurement for most Australian Government entities. For buyers serving government or expecting broader ecosystem uptake, that raises the importance of clean sender, receiver, and onboarding design.

Business Central: the Australian path is the clearest documented one

• Microsoft's Australian localisation page says the E-Document framework for Australia supports only the Peppol PINT A-NZ format.
• The same Microsoft page says buyers can choose any service provider available for the Australian market with whom they have an agreement. That means the product path is documented, but the commercial and onboarding path still depends on the provider relationship.
• Microsoft's e-invoicing FAQ says Australia and New Zealand were enabled for PEPPOL PINT A-NZ with 2025 release wave 1.
• The FAQ also says Business Central supports different connectors, names built-in support providers including Avalara, B2BRouter, Continia, Logiq, Pagero, and SignUp, and says use of the service can incur extra costs.
• For Australian buyers, the practical reading is that Business Central currently gives the strongest official Australia-specific documentation of the three products reviewed here, but it still does not remove the need to choose and contract with an external network provider.

NetSuite: real PEPPOL capability is documented, but the Australian implementation path needs harder validation

• Oracle's NetSuite Electronic Business overview says the NSEB SuiteApp lets users participate in global business networks including PEPPOL and provides global electronic invoicing solutions by partnering with Avalara.
• Oracle also says participating NetSuite users can be linked to the PEPPOL network through that Avalara relationship without needing to sign up for access points in each country.
• NetSuite's Electronic Invoicing documentation says the Electronic Invoicing SuiteApp can generate and send e-documents and receive inbound e-documents that are converted into transaction records.
• Oracle's PEPPOL template documentation explicitly includes an ANZ PEPPOL template for Australia and New Zealand. That is the strongest Australia-specific signal in the public NetSuite help.
• The caution point is that Oracle's public help is more framework-oriented than Microsoft's Australian localisation guidance. It shows that NetSuite has PEPPOL and ANZ template capability, but buyers should still ask their partner to prove the exact Australian onboarding, trading-partner setup, and subsidiary design path for the target account.

Odoo: strong native Peppol story, but Australia is not listed in the current built-in registration footprint

• Odoo 19 documentation says Odoo acts as both an access point and an SMP for Peppol transactions.
• Odoo also says Peppol registration is free and available in Odoo Community.
• The same documentation lists the countries eligible for Peppol registration in Odoo, and Australia is not on that current list.
• That does not automatically mean an Australian Odoo customer cannot reach Peppol through other implementation patterns. It does mean the native documented registration path is not currently presented as Australia-ready in Odoo's own docs.
• For Australian shortlist buyers, that should trigger a stricter question set around third-party access points, local compliance interpretation, support ownership, and whether the partner is proposing standard product behaviour or a more bespoke workaround.

What buyers should compare before they shortlist on eInvoicing alone

• Connector and provider dependency: Business Central explicitly expects a service-provider agreement. NetSuite documents Avalara-linked PEPPOL participation. Odoo documents native Peppol registration, but not for Australia in the current eligibility list.
• Australia-specific documentation quality: Microsoft is the clearest. Oracle shows real capability but is less explicit about the Australian rollout path in public docs. Odoo is explicit, but currently explicit in a way that raises an Australian gap rather than removing one.
• Inbound and outbound scope: NetSuite publicly documents both sending and inbound conversion. Business Central's E-Documents framework supports purchasing and sales workflows. Odoo documents both sending invoices and receiving vendor bills through Peppol.
• Commercial surprise risk: every path can involve extra service or implementation effort. Microsoft says services can incur extra cost, Oracle positions the solution through SuiteApps and partners, and Odoo may require an Australia-specific non-standard path.

Five questions to force into every demo or partner workshop

• 1. Show one Australian outbound invoice and one inbound supplier invoice end to end, including master-data setup, validation, exception handling, and audit trail.
• 2. Name the external party that actually gets us onto the Peppol network and explain who owns onboarding, support, certification, and issue escalation.
• 3. Explain whether the proposed path is standard documented product behaviour for Australia or a partner-assembled workaround.
• 4. Show how customer and supplier identifiers, subsidiary or entity design, and approval workflow interact once Peppol is live.
• 5. Separate software capability from rollout readiness. The most common mistake is hearing “supported” and assuming the operational model is already solved.

Where ERP projects usually go wrong on this topic

• Teams treat Peppol as an accounts-payable add-on instead of a trading-partner, master-data, and support-model design problem.
• Buyers accept a vague “yes, the ERP does eInvoicing” answer without confirming whether the Australian path is native, partner-led, or third-party dependent.
• Finance and IT agree the sending format, but no one owns onboarding sequence, exception queues, or the process for counterparties that are not yet ready on the network.
• The business asks licensing questions before it asks operating questions. In practice, provider choice, implementation effort, and support boundaries often move the real budget more than base subscription cost.

What Australian buyers should conclude now

• Business Central currently has the clearest Australia-specific public documentation for Peppol readiness, but it still depends on an external service-provider relationship.
• NetSuite has documented PEPPOL capability and an ANZ template path, but buyers should demand more account-specific proof before treating Australian rollout as straightforward.
• Odoo has a strong native Peppol story in Europe, but its current built-in registration documentation does not list Australia, so local buyers should assume more validation work is required.
• If eInvoicing matters materially to your operating model, do not leave it as a late-stage integration footnote. Put it into the shortlist script early and make each vendor prove the real Australian path.

FAQ

• Which ERP looks most straightforward for Australian Peppol adoption from public documentation alone? Business Central. Microsoft's Australia-specific localisation and FAQ material is the clearest of the three.
• Does NetSuite support Peppol for Australia and New Zealand? Oracle's public help includes an ANZ PEPPOL template and PEPPOL participation through NetSuite Electronic Business, but buyers should still verify the exact Australian rollout path for their account.
• Can Odoo be activated natively for Australian Peppol registration today? Odoo's current public documentation does not list Australia among the countries eligible for its built-in Peppol registration path.
• What is the safest next step if eInvoicing matters in our shortlist? Run one scenario-led workshop focused only on Peppol onboarding, inbound and outbound document flow, identifiers, provider dependency, and support ownership.

Sources used

• Australian Taxation Office guidance on eInvoicing for businesses and eInvoicing for government.
• Microsoft Learn pages for Electronic invoicing in Australia and the Electronic Invoicing FAQ for Business Central.
• Oracle NetSuite help pages for NetSuite Electronic Business Overview and Electronic Invoicing, including the ANZ PEPPOL template reference.
• Odoo 19.0 documentation for Electronic invoicing (EDI), including the Peppol registration eligibility list.