Australia is part of the Peppol network and uses the Peppol mandate with UBL as the supported outbound format. The Australia pre-integrated package includes default Peppol-compliant e-invoice templates, data mappings, and validation logic in Avalara, aligned with local regulatory requirements.

Prerequisites in Avalara

From Avalara's perspective, your primary goal is to ensure that inbound e-invoice data from Zuora can be accepted, validated, and routed according to Australian Peppol rules. Confirm the following in your Avalara E‑Invoicing and Live Reporting tenant:

• Product activation and mandate selection

  • Avalara E‑Invoicing and Live Reporting is activated for Australia.
  • During onboarding or when adding a new company, you completed the activation flow for Australia and selected the Peppol mandate and relevant platform/network.
  • A Peppol ID is configured for your legal entity in Avalara, either by entering an existing identifier or by applying for a new Peppol ID as part of activation.

• ABN and Peppol ID details

  • When applying for a new Peppol ID, you entered a valid Australian Business Number (ABN) as the Country of Establishment Tax Number.
  • The ABN used in Avalara matches the seller legal business number configured in Zuora's business regions and e‑invoicing profiles, to avoid validation failures.

• Supported formats and downloads

  • For Australia, Avalara is configured to handle the Peppol mandate in UBL format.

  • You understand which download types (for example, XML, PDF, UBL_XML) are available from Avalara's UI and APIs, and how they will be consumed in your downstream processes.

Prerequisites in Zuora (source system)

From Avalara's standpoint, Zuora must send complete and consistent source data. Verify in Zuora that:

• An e‑invoicing business region is configured for Australia with the required seller details:

  • Country = Australia

  • Legal Business Name and Legal Business Number (ABN)

  • Business Number Schema Id = 0151 for ABN-based identification

  • E‑Invoice Destination Code and E‑Invoice Destination Code Schema Id, corresponding to your Peppol ID structure (for example, iso6523-actorid-upis::0151:ABN).

  • Service Provider set to Avalara, which drives the Peppol network process in Zuora.

• Customer e‑invoicing profiles and sold-to contacts are fully populated for buyers in Australia, including:

  • Generate E‑Invoice for Customer enabled

  • Buyer Business Category (B2B, B2C, B2G), legal name, legal business number (ABN where applicable), and e‑invoice destination code details

  • Australian sold-to address fields (Country, postal code, city, and state) correctly set, as these are used in Avalara's payload.

• Billing documents (Invoices, Credit Memos, and Debit Memos) used for testing are in Posted status and linked to the correct Australian business region.

Supported coverage for Australia in Avalara

Avalara's Australia configuration should support at least the following capabilities for data submitted from Zuora:

When you design tests, you are validating that:

• Zuora-generated billing documents arrive in Avalara as Peppol UBL e‑invoices.

• Avalara's validation and routing logic accept or reject documents based on Australian rules.

• Avalara can expose resulting documents and responses in all expected download formats (XML, PDF, UBL_XML) for your consumers.