Recommended end-to-end test scenarios in Avalara for Spain
Use these draft scenarios to validate the Spain package in Avalara for vendor validation and future customer onboarding and production-readiness testing.
Scenario 1: Standard invoice validation
Objective: Verify that a standard posted invoice from Zuora is accepted by Avalara for the Spain package and produces the expected UBL output.
High-level steps:
In Zuora, create and post a standard invoice for a Spain business region.
Trigger e-invoicing so that the invoice is submitted to Avalara.
In Avalara, confirm that the transaction is processed under the Spain configuration and FACE mandate.
Verify that the generated document is available in the supported download types.
Expected results: Avalara accepts the invoice for vendor validation, generates the expected UBL output, and makes the supported files available for review.
Scenario 2: Credit memo validation
Objective: Verify that a posted credit memo can be submitted and validated through the Spain package.
High-level steps:
Create and post a credit memo in Zuora for the same Spain configuration.
Trigger e-invoicing for the credit memo.
Review the generated output and validation behavior in Avalara.
Expected results: The credit memo is accepted for the vendor-validation scenario and the resulting output is available for document review.
Scenario 3: Debit memo validation
Objective: Verify that a posted debit memo can be submitted and validated through the Spain package.
High-level steps:
Create and post a debit memo in Zuora for the Spain business region.
Trigger e-invoicing for the debit memo.
Review the resulting document and validation status in Avalara.
Expected results: The debit memo is processed successfully for vendor validation and can be reviewed in the supported formats.
Scenario 4: Validation failure and data-quality checks
Objective: Confirm that missing or inconsistent source data is surfaced clearly during validation.
Suggested negative test variations:
Missing seller tax or legal information
Missing buyer identification or destination details
Invalid or incomplete billing-document data
Expected results: Avalara flags the failed transaction clearly enough for the implementation team to correct the data or mappings before future onboarding.
Scenario 5: Resubmission after correction
Objective: Verify that corrected transactions can be revalidated after source-data fixes are made.
High-level steps:
Submit a transaction with intentionally incomplete data.
Correct the source data in Zuora.
Re-trigger e-invoicing and review the updated result in Avalara.
Expected results: The corrected transaction is accepted and the updated output reflects the corrected source data.
Scenario 6: Future end-to-end production validation
Objective: Reserve a scenario set for full Spain end-to-end validation once real tax IDs and production-like onboarding data are available.
Expected results: This scenario set remains deferred in the current draft. Complete it when customer onboarding or compliant test identifiers are available for Spain.