ATW-VAT-SCENARIO-APPLIED — E-Invoice Validation Rule & Fix

Fixture ID: vatScenarioApplied · XPath: N/A (Computed / Semantic Rule)

1. Why This Rule Triggers (Diagnostic Message)

vatScenario "intra-eu-services" (a service to a business in another EU member state, which accounts for the VAT itself) was turned into codes. Filled in: vatCategory "AE" (reverse charge) and vatRate 0 on line 1, vatExemptionReasonCodes.AE "VATEX-EU-AE" (BT-121) and vatExemptionReasons.AE "Steuerschuldnerschaft des Leistungsempfängers" (BT-120). The text is in German because the seller's country (BT-40) is DE. These are the codes validateInput judged and the generators write, and applyVatScenarios returns them as an explicit invoice.

2. How to Fix ATW-VAT-SCENARIO-APPLIED

Nothing needs fixing. To write something else, state it yourself: an explicit vatCategory, vatRate, vatExemptionReasons.AE or vatExemptionReasonCodes.AE always wins over a scenario.

3. Valid Code / Payload Example

"vatCategory": "AE", "vatRate": 0, "vatExemptionReasonCodes": { "AE": "VATEX-EU-AE" }, "vatExemptionReasons": { "AE": "Steuerschuldnerschaft des Leistungsempfängers" }