home

Zuora Billing

Zuora BillingZuora PaymentsZuora PlatformZuora CPQZephrZuora RevenueAccounts ReceivableRelease NotesBasicsEntitlementsSupport and policies
Zuora BillingZuora PaymentsZuora PlatformZuora CPQZephrZuora RevenueAccounts ReceivableRelease NotesBasicsEntitlementsSupport and policies

Welcome to Zuora Product Documentation

Explore our rich library of product information

Show Contents

thumbnailZuora Billing

Country-specific configurations in Avalara for New Zealand

Testing recommendations in Avalara for New Zealand

Testing guidance for New Zealand Avalara integrations, including Peppol mandate validation, UBL output verification, and end-to-end operational flows between Zuora and Avalara.

For New Zealand, testing should focus on the Peppol mandate, UBL output, document mappings, and the operational flows between Zuora and Avalara. The New Zealand implementation supports XML, PDF, and UBL_XML downloads.

For pre-integrated Avalara country packages, testing is expected to include successful end-to-end UAT runs for representative flows and edge cases, plus operational readiness for resync, regenerate, and download actions.

Prerequisites in Avalara

Verify the following in Avalara before you begin end-to-end validation:

  • The Avalara E-Invoicing and Live Reporting product is activated for the New Zealand company.

  • The Peppol mandate is selected for the implementation.

  • The company is configured with the Peppol identity required for routing.

  • Your team understands which supported file downloads are available for verification.

Prerequisites in Zuora

Verify the following in Zuora:

  • The New Zealand business region contains the seller details required by your implementation.

  • Customer e-invoicing profiles and sold-to contacts are fully populated for the buyers that you will test.

  • Invoices, credit memos, and debit memos used for testing are posted before submission.

What to validate

When you test, confirm that:

  • Zuora sends New Zealand billing documents to Avalara through the PEPPOL process.

  • Avalara accepts, validates, or rejects documents based on the configured data and mappings.

  • The expected UBL-based output is generated for the transaction flow.

  • The supported downloads are available for operational use after processing.

  • Standard positive-path processing for Invoice, Credit Memo, and Debit Memo.

  • Negative-path validation for missing or inconsistent seller, buyer, or routing data.

  • Resubmission behavior after data corrections.

  • Operational verification of download, resync, and regenerate flows.

Last updated: May 11, 2026