attestwireAttestwire › Rule reference › PEPPOL-EN16931-P0111
PEPPOL-EN16931-P0111 The VATEX-EU-J exemption code is only for exempt supplies
noun · Peppol BIS · fatal · BT-121 / BT-118
For a sample invoice, the library reports: You set vatExemptionReasonCodes.AE to "VATEX-EU-J", which attaches the VAT exemption reason code (BT-121) "VATEX-EU-J" to the VAT breakdown for category AE.
- Business term
BT-121 / BT-118- Severity
fatal
The fix
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.
A passing value
"vatExemptionReasonCodes": { "E": "VATEX-EU-J" }What the library returns
The full error returned by @attestwire/en16931. It includes the rule ID,
affected field and suggested correction. Developers can use this object in their application:
{
"rule": "PEPPOL-EN16931-P0111",
"field": [
"BT-121",
"BT-118"
],
"severity": "fatal",
"message": "You set vatExemptionReasonCodes.AE to \"VATEX-EU-J\", which attaches the VAT exemption reason code (BT-121) \"VATEX-EU-J\" 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-J\" means \"Intra-community acquisition of works of art\", and a breakdown that says AE in BT-118 and Intra-community acquisition of works of art in BT-121 says two different things about one group of money. A human reader would skim past the contradiction; an automated ledger 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.",
"fix": "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.",
"example": "\"vatExemptionReasonCodes\": { \"E\": \"VATEX-EU-J\" }",
"xpath": "/ubl:Invoice/cac:TaxTotal/cac:TaxSubtotal/cac:TaxCategory/cbc:TaxExemptionReasonCode",
"docsUrl": "https://attestwire.com/rules/PEPPOL-EN16931-P0111"
}
xpath is always a UBL path. On a CII invoice, look for the
matching CII field instead.