Field mapping management for e-invoice file templates in Avalara for New Zealand
Use the default New Zealand Avalara e-invoice templates as a baseline, and verify that seller, buyer, billing document, line-item, and custom field mappings align with the PEPPOL/UBL requirements before promoting changes to production.
For a new pre-integrated Avalara country, the required deliverables include default e-invoice templates for Invoice, Credit Memo, and Debit Memo, default response field mappings and status reason mappings, and documented Zuora data model details such as business regions, account profiles, custom fields, and sample configurations.
For New Zealand, the implementation table identifies PEPPOL as the supported mandate, UBL as the outbound format, and marks response mapping as N/A.
What to map in the New Zealand templates
When you review or extend the default New Zealand templates, verify that the following data groups are mapped correctly:
seller information from the Zuora business region
buyer information from the customer account, e-invoicing profile, and sold-to contact
billing document header information for invoices, credit memos, and debit memos
line-item data, totals, tax values, and document references
Peppol endpoint and routing values required for document delivery
any custom fields that your implementation uses for country-specific or business-specific data
Recommended mapping review approach
Review mappings for the following document types separately:
Invoice
Credit Memo
Debit Memo
For each document type:
confirm that the generated payload aligns with the New Zealand Peppol/UBL flow used by Avalara
verify that seller and buyer identification values are populated from the intended Zuora fields
validate that references between related documents, such as invoice-to-credit-memo relationships, are preserved for downstream processing
use representative sample data before promoting template changes to production
Best practices
Start with the default pre-integrated New Zealand templates when available, and customize only where your business process requires it.
Keep business region, customer profile, and sold-to contact data consistent so that Avalara validations can succeed.
Test template updates with posted billing documents before enabling them for production traffic.