Scenario 1: Standard B2B invoice flow

Objective: Confirm that a posted B2B invoice in Zuora results in a valid Belgium PEPPOL invoice in Avalara and can be exchanged through the PEPPOL network.

High-level steps:

1. Create and post an invoice in Zuora for a Belgium B2B customer configured with the correct business region and e-invoicing profile.

2. Trigger e-invoicing so that Zuora generates the Belgium PEPPOL UBL payload and submits it to Avalara.

3. In Avalara, verify that the transaction is processed under the Belgium PEPPOL configuration and that the document is valid for PEPPOL exchange.

4. Download the document in XML, PDF, and UBL_XML, and confirm the output is usable by downstream consumers.

Expected results:

• Avalara accepts the document without blocking validation errors.

• The invoice is processed as a Belgium PEPPOL invoice using the expected UBL structure.

Scenario 2: B2G invoice routing

Objective: Verify that a Belgium B2G invoice follows the expected PEPPOL-based routing pattern and is handled correctly for public-sector processing.

High-level steps:

1. Create and post a test invoice for a Belgium public-sector customer scenario.

2. Submit the invoice through Zuora to Avalara using the Belgium business region.

3. In Avalara, verify that the document is handled according to the Belgium B2G route and that Avalara can route it to Mercurius where applicable.

Expected results:

• The B2G invoice follows the Belgium public-sector routing pattern supported by Avalara.

Scenario 3: Credit memo referencing an original invoice

Objective: Verify that a Belgium credit memo is generated as a valid correction document and correctly references the original invoice.

High-level steps:

1. Create and post a credit memo in Zuora that references a previously posted invoice.

2. Trigger e-invoicing and verify that Avalara receives the correction document.

3. Confirm that the credit memo is treated as the proper mechanism to correct or nullify the original invoice in Belgium.

Expected results:

• The credit memo is processed as a valid Belgium correction document.

• The original invoice remains part of the audit trail and is corrected by reference, not deleted.

Scenario 4: Debit memo correction flow

Objective: Validate debit-memo handling for Belgium, where debit notes are less common but supported as correction documents.

High-level steps:

1. Create and post a debit memo in Zuora for a Belgium account.

2. Submit it to Avalara through the Belgium PEPPOL flow.

3. Confirm that the generated document is accepted and treated as a valid correction document where applicable.

Expected results:

• Belgium debit-memo scenarios work with the default pre-integrated template set and PEPPOL flow.

Scenario 5: Validation failure and identifier mismatch checks

Objective: Confirm that Belgium-specific validation failures are surfaced clearly when seller, buyer, or routing data is incomplete or inconsistent.

Suggested negative tests:

• Submit a document with mismatched PEPPOL-related identifiers between Avalara and Zuora.

• Submit a document with incomplete country-specific data required by the Belgium business region or account profile.

• Submit a billing document before it is correctly posted or before the Belgium configuration path is complete.

Expected results:

• Avalara exposes actionable validation errors.

• The implementation team can determine whether the issue must be fixed in template mapping, master data, or operational setup.

Scenario 6: Regeneration and resync after data correction

Objective: Confirm that Belgium documents can be corrected operationally after a failure by fixing the data and using Zuora's regenerate or resync actions.

High-level steps:

1. Intentionally submit a Belgium document that fails validation.

2. Correct the underlying data in Zuora.

3. Regenerate the e-invoice or resync the status as appropriate.

4. Verify that Avalara reflects the updated state and that the corrected document can be downloaded in the supported formats.

Expected results:

• Regeneration produces a corrected Belgium payload.

• Resync correctly updates document status after Avalara-side processing changes.