CargodeskflowEnterprise ERP & Freight TMS
Integration

Procure-to-Pay in Australia and New Zealand: Peppol, Payment Times Rules and Costs

Peppol is established across Australian and New Zealand government, and large Australian companies report payment times twice a year. Here's what that means for P2P scope, access-point choice, cost and rollout time.

By the Cargodeskflow editorial team · November 2026 · 10 min read

Why ANZ Compliance Rules Change How You Scope a P2P Project

If you're choosing procure to pay software in Australia or New Zealand, you're making two decisions, not one. The first is the usual one: requisitions, approvals, purchase orders, invoice matching and payment runs. The second is compliance plumbing. Can the platform send and receive Peppol e-invoices through a certified access point? Can it produce the payment data that Australia's Payment Times Reporting Scheme expects from large businesses? Many buyers discover the second decision late, after signing with a vendor whose ANZ e-invoicing support is a partner integration they hadn't priced.

The region differs from Europe or Latin America. Neither country has a blanket B2B e-invoicing mandate with real-time tax clearance. What exists is a government-backed Peppol framework, faster payment commitments for e-invoices sent to government buyers, and, in Australia, a statutory reporting regime that makes slow payment to small suppliers public. Together these push buyers toward structured invoice intake and clean payment-date data. That, more than catalog features, is how procure to pay software in Australia should be judged.

Advertisement

This guide is for finance, procurement and IT leaders at manufacturers, distributors, retailers and 3PLs with ANZ entities, including multinationals in Asia, Europe or the Americas that run Australian or New Zealand subsidiaries on a group ERP. It explains how the rules generally work. Thresholds, entity coverage and reporting duties depend on your corporate structure, so confirm your position with a local tax adviser and a lawyer before building the project around them.

Peppol E-Invoicing in Australia and New Zealand: What Is Required and What Is Rewarded

Australia and New Zealand adopted Peppol jointly. The Australian Taxation Office acts as the Peppol Authority in Australia, and the Ministry of Business, Innovation and Employment (MBIE) does so in New Zealand. Both use a shared trans-Tasman invoice specification built on the Peppol International (PINT) model for A-NZ. Businesses are identified by ABN in Australia and NZBN in New Zealand. In practice, one access point connection can usually exchange invoices on both sides of the Tasman.

Australia

Peppol e-invoicing in Australia is required of many Commonwealth government entities, not of private companies. Agencies must be able to receive Peppol invoices, and federal payment policy sets faster payment targets for e-invoices than for paper or PDF. Suppliers who invoice through Peppol get paid sooner. Several state governments run their own e-invoicing programs and prompt-payment pledges. Federal Treasury has also consulted on B2B adoption, including whether larger businesses should have to receive e-invoices. Confirm current status before you plan, but build receive capability now. It's cheap, and retrofitting it under a deadline isn't.

New Zealand

New Zealand has a firmer public-sector direction. Government has directed larger agencies to send and receive e-invoices, with a start date in the 2026 timeframe, and has tied this to faster payment of domestic e-invoices. Some large private buyers and councils have followed. New Zealand also passed a payment-practices disclosure law for large entities in 2023, but later governments have moved to scale it back or repeal it. Check its status before designing any reporting around it.

The practical consequence is the same in both countries. If you sell to government, Peppol send capability shortens your cash cycle. If you buy from small suppliers, Peppol receive capability makes accurate payment-time data far easier to produce. Both point to an access point integrated with your P2P workflow, not bolted on beside it.

On GST: an e-invoice can be a valid tax invoice in both countries if it carries the required information, such as supplier identifier, GST amounts and dates. Peppol doesn't change your GST obligations. Have your tax adviser confirm that your configured templates meet tax-invoice requirements for each entity.

Designing P2P Data Around the Payment Times Reporting Scheme

The Payment Times Reporting Scheme applies to large businesses carrying on business in Australia. The main test is total annual income above A$100 million, and group structures can bring smaller entities into scope. Reporting entities lodge a report every six months on their payment terms and practices with small-business suppliers, and the regulator publishes the results. Recent amendments adjusted some reporting elements and the regulator's powers. The core dataset is unchanged: which suppliers are small businesses, what terms you agreed with them, and how long you actually took to pay.

That dataset lives in your P2P and AP systems, and it's usually messier than finance teams expect. These fields matter:

  • Small-business flag per supplier. The government provides an identification tool that classifies suppliers by ABN. Your vendor master needs a field for the result and a schedule to refresh it before each reporting period.
  • Contractual payment terms, stored as structured data such as "30 days end of month", not as free text in a PDF contract.
  • Invoice receipt date. This is the weakest data point in most AP processes. Emailed PDFs often get stamped with the date they were keyed, not the date they arrived. Peppol gives you a system-generated receipt timestamp.
  • Payment date at invoice level, including partial payments and credit notes.
  • Entity mapping, so reports can be produced per reporting entity in a group.

Hypothetical worked example: say a Melbourne industrial distributor has A$220 million in annual income and processes about 7,000 supplier invoices a month, roughly 45% from small businesses. Sixty percent of invoices arrive as emailed PDFs, and AP keys the receipt date from the inbox date when it gets to them, sometimes four or five days late. Its reported average time to pay looks better than reality on some invoices and worse on others. Moving small-business suppliers onto Peppol, even partly through supplier portals that generate e-invoices, gives it defensible receipt dates. It also lets AP prioritize small-business invoices in payment runs, which improves the published figures. The reporting export becomes a scheduled query instead of a six-week spreadsheet exercise.

When you evaluate vendors, ask for a payment-times extract by entity, built on your own field definitions. Treat "we have a report for that" as unverified until you've seen it run.

Access-Point Options and Vendor Availability in ANZ

Peppol works on a four-corner model. You connect to a certified access point, your supplier connects to theirs, and the network routes documents between them. You don't need the same provider as your trading partners. The ATO and MBIE each maintain lists of accredited providers, so check those rather than relying on vendor marketing.

There are three common ways to get connected:

ApproachTypical providers (examples)Best fitTrade-offs
Access point built into your P2P suiteBasware, SAP Business Network, Pagero, Coupa (confirm whether delivered natively or via a partner)Enterprises wanting one vendor for intake, matching and complianceHigher subscription; ANZ Peppol may run through a subcontracted access point, so ask who holds the certification
Standalone access point integrated with ERP or AP toolStorecove, Sovos, Comarch, Unifiedpost/Banqup, MessageXchange and other locally accredited providersMid-market firms on NetSuite, Dynamics 365, Acumatica or similar; multinationals wanting one provider across Peppol countriesYou own the integration and the support boundary between ERP and access point
Accounting-platform native e-invoicingXero, MYOB and other SME platforms, often paired with approval tools such as ApprovalMaxSmaller entities and subsidiaries with simple PO needsLimited three-way matching, approval depth and multi-entity reporting

Among full P2P suites, SAP Ariba, Coupa, Oracle Procurement Cloud, Workday and Basware have an established ANZ presence. In the mid-market, buyers commonly pair an ERP with AP automation and intake tools such as Zip, Procurify or regional AP specialists. Availability is generally good. Local support varies, so ask where implementation partners are based and whether support covers Australian and New Zealand business hours.

For multinationals, Peppol is a real argument for one access point provider across regions. The network carries invoices in much of Europe and in parts of Asia-Pacific, though each country has its own specification and some mandates add tax-reporting layers. A provider covering ANZ and your other Peppol markets cuts the number of integrations, but only if it supports each country's specification natively.

Indicative Costs and What Drives Them

Pricing is contract-specific and often quoted in local currency. The ranges below are typical 2026 market ranges in USD, indicative only. Local pricing, volume tiers and multi-year discounts will move them, so confirm with vendors.

Cost itemMid-market (roughly 2,000–15,000 invoices/month)Enterprise (multi-entity, 15,000+ invoices/month)
Peppol access point (standalone)$0.15–$0.80 per document, or $200–$1,500/month platform feeNegotiated volume pricing; often $15,000–$80,000/year
P2P / AP automation subscription$25,000–$120,000/year$150,000–$600,000+/year
Implementation and integration$20,000–$100,000$250,000–$1.5 million+
Supplier enablement campaign$5,000–$30,000 (often internal effort)$50,000–$200,000
Payment-times reporting build$5,000–$25,000$20,000–$80,000

The biggest cost drivers:

  • Number of ERPs and entities. Each ERP instance usually needs its own integration and testing cycle. A group running SAP in Sydney and a legacy system in Auckland pays for two projects.
  • Supplier mix. If most suppliers are small businesses on Xero or MYOB, many can already send Peppol invoices and enablement is cheap. Suppliers relying on manual invoicing need portals or OCR fallback, which adds per-document cost.
  • Matching complexity. Freight, landed costs, consignment stock and service-entry sheets need more configuration than simple goods receipts.
  • Who funds supplier onboarding. Some networks charge suppliers. Small suppliers are a sensitive constituency in this market, so read the supplier-fee terms carefully.

Our position: for most mid-market ANZ businesses, a standalone access point plus your ERP's native AP or a focused AP automation tool is better value than a full source-to-pay suite. Suites pay off when you also need sourcing, contract management and catalog buying at scale.

A Realistic P2P Implementation Timeline, Red Flags and Next Steps

Vendors quote best-case timelines. The ones below reflect typical projects, assuming a clean ERP, a decided scope and available internal staff.

PhaseMid-marketEnterprise
Requirements, data audit, vendor selection4–8 weeks8–16 weeks
Access point registration and Peppol testing2–4 weeks4–8 weeks
P2P configuration and ERP integration6–12 weeks4–9 months
Payment-times data model and report build2–4 weeks (in parallel)4–8 weeks (in parallel)
Supplier enablement waves2–4 months, ongoing6–12 months, ongoing
Total to stable operation3–6 months9–18 months

Plan go-live against your reporting calendar. Cutting over mid-period forces the report to combine data from two systems. Where you can, go live at the start of a six-month period, or keep a reconciled bridge extract.

Red flags during selection

  • The vendor can't name the certified access point that carries ANZ traffic, or can't show it on the ATO or MBIE lists.
  • Support covers only the older A-NZ specification, with no roadmap for PINT A-NZ.
  • Invoice receipt date is editable by AP users without an audit trail.
  • Payment-times reporting is offered as "custom reporting" with no example output.
  • Onboarding fees are charged to small suppliers without your approval.
  • No implementation partner or support coverage in ANZ time zones.

What to do this quarter

  1. Confirm with your tax adviser and lawyer which entities fall under Payment Times Reporting, and what your government-customer contracts require on e-invoicing and subcontractor payment terms.
  2. Audit your vendor master. Can you flag small-business suppliers by ABN or NZBN and store payment terms as structured data?
  3. Measure your current invoice channels: Peppol, PDF email, paper, portal.
  4. Shortlist two or three vendors and require a scripted demo: receive a Peppol invoice, match it to a PO and goods receipt, pay it, and produce a payment-times extract for one entity.

A simple decision rule: if more than a third of your supplier invoices come from small businesses, or you invoice government buyers, make Peppol send and receive capability pass/fail. Vendors that fail come off the shortlist, whatever their feature list says.

Common questions

Is Peppol e-invoicing mandatory for private businesses in Australia?

Not as a general rule. Peppol is required of many Commonwealth government agencies to receive. Federal Treasury has consulted on B2B adoption, including a possible requirement for larger businesses to receive e-invoices. Check current policy and confirm your position with a tax adviser.

Do we need separate Peppol access points for Australia and New Zealand?

Usually not. Both countries use a shared trans-Tasman Peppol specification, and one accredited access point can typically exchange invoices using ABN and NZBN identifiers. Check that your provider appears on both the ATO and MBIE accredited lists.

Which businesses must report under the Payment Times Reporting Scheme?

Broadly, businesses carrying on business in Australia with total annual income above A$100 million, plus some entities in larger corporate groups. Reports are lodged every six months on payment terms and practices with small-business suppliers. Coverage depends on group structure, so get legal advice for your specific entities.

How long does a P2P implementation with Peppol take in ANZ?

Mid-market projects typically reach stable operation in three to six months. Multi-entity enterprise programs often take nine to 18 months. Supplier enablement continues after go-live, and the number of ERP instances is usually the biggest factor in duration.

Can our existing ERP handle this without a full P2P suite?

Often, yes. Many mid-market firms pair an ERP such as NetSuite, Dynamics 365 or Acumatica with a standalone Peppol access point and an AP automation tool. A full suite is worth the extra cost mainly when you also need sourcing, contract management and catalog buying at scale.

Written by the Cargodeskflow editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.