PEPPOL-EN16931-P0109 — E-Invoice Validation Rule & Fix

Fixture ID: peppolVatexOnE2 · XPath: /ubl:Invoice/cac:TaxTotal/cac:TaxSubtotal/cac:TaxCategory/cbc:TaxExemptionReasonCode

1. Why This Rule Triggers (Diagnostic Message)

You set vatExemptionReasonCodes.AE to "VATEX-EU-F", which attaches the VAT exemption reason code (BT-121) "VATEX-EU-F" to the VAT breakdown for category AE. Peppol requires that code to appear only on category E, because the code *is* a statement of the category: "VATEX-EU-F" means "Intra-community acquisition of second-hand goods", and a breakdown that says AE in BT-118 and Intra-community acquisition of second-hand goods in BT-121 says two different things about one group of money. A human reader would skim past the contradiction; an automated records would post it twice, once per claim. This is a Peppol BIS Billing 3.0 profile rule: it applies because profile is "peppol-bis-3". It does not apply to the en16931, xrechnung-ubl or xrechnung-cii profiles, whose validators will accept the same document.

2. How to Fix PEPPOL-EN16931-P0109

Either move the code — set vatExemptionReasonCodes.E instead of vatExemptionReasonCodes.AE — or pick a code that matches category AE. The VATEX list also carries article-level codes (VATEX-EU-132-1A and its siblings) which name a provision rather than a treatment and are not constrained to any category.

3. Valid Code / Payload Example

"vatExemptionReasonCodes": { "E": "VATEX-EU-F" }