Testing recommendations in Avalara for Norway
Guidelines for testing Norway-specific Avalara integration in Zuora, including end-to-end UAT flows, document formats, and validation checks.
For a pre-integrated country, Zuora expects successful end-to-end UAT runs for representative flows and edge cases, along with an operational runbook for resync, regenerate, download, and country-specific limitations.
Recommended testing approach
Start with a standard B2B invoice scenario to confirm that a posted billing document in Zuora is accepted by Avalara for Norway.
Validate invoice, credit memo, and debit memo flows separately because the Norway package includes default templates for all three billing document types.
Confirm that all required seller and buyer identifiers are populated correctly before testing transaction submission.
Test document download in all supported Norway formats: XML, PDF, and UBL_XML.
Include negative tests for missing or invalid organization number, VAT number, destination code, or schema ID values. These are required inputs in the Norway setup.
Validate your operational procedures for resubmission and troubleshooting after correcting source data in Zuora.
What to verify in Avalara
During testing, verify the following from the Avalara side:
The transaction is created under the expected Norway company and mandate configuration.
The generated document follows the expected UBL-based PEPPOL structure for the Norway flow.
Validation messages clearly identify configuration or data issues when required identifiers are missing or invalid.
Status transitions, document downloads, and resubmission behavior align with your operational expectations.