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

Fixture ID: vatScenarioConflict · XPath: /ubl:Invoice/cac:InvoiceLine[1]/cac:Item/cac:ClassifiedTaxCategory/cbc:ID

1. Why This Rule Triggers (Diagnostic Message)

Line 1 states vatScenario "export", which stands for VAT category G (Export outside the EU), and also vatCategory "S". The scenario says what happened and the category is its code, so one of the two is wrong. An explicit category wins over a scenario, so the document would say "S" and nothing from the scenario would be written.

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

Remove one of the two from lines[0]: drop vatCategory to let the scenario decide the code, or drop vatScenario if "S" is what you meant.

3. Valid Code / Payload Example

"vatScenario": "export"