BR-G-06

The same invoice, failing and fixed

Neither block below is hand-written, and neither is an illustration: both are cut verbatim out of corpus/cen-en16931/test/Invoice-unit-UBL/BR-G-06.xml, the vendored unit test the CEN EN 16931 project ships for this rule. The people who wrote the Schematron wrote these two documents and labelled them <error>BR-G-06</error> and <success>BR-G-06</success>. They are published here only because this engine agreed with that labelling: it reported BR-G-06 for the first document and did not report it for the second, under --profile en16931.

UBL Invoice — fails

The upstream case description: “Trigger error when a document level allowance where the Invoice item VAT category code (BT-95) is "Export outside the EU" the Invoiced item VAT rate (BT-96) is not 0 (zero).”

<Invoice
	xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
	xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2"
	xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2">
	<cac:AllowanceCharge>
		<cbc:ChargeIndicator>false</cbc:ChargeIndicator>
		<cac:TaxCategory>
			<cbc:ID>G</cbc:ID>
			<cbc:Percent>10</cbc:Percent>
			<cac:TaxScheme>
				<cbc:ID>VAT</cbc:ID>
			</cac:TaxScheme>
		</cac:TaxCategory>
	</cac:AllowanceCharge>
	
</Invoice>

UBL Invoice — passes

The upstream case description: “Verify that in a document level allowance where the Invoice item VAT category code (BT-95) is "Export outside the EU" the Invoiced item VAT rate (BT-96) shall be 0 (zero).”

<Invoice
	xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
	xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2"
	xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2">
	<cac:AllowanceCharge>
		<cbc:ChargeIndicator>false</cbc:ChargeIndicator>
		<cac:TaxCategory>
			<cbc:ID>G</cbc:ID>
			<cbc:Percent>0</cbc:Percent>
			<cac:TaxScheme>
				<cbc:ID>VAT</cbc:ID>
			</cac:TaxScheme>
		</cac:TaxCategory>
	</cac:AllowanceCharge>
</Invoice>

What the engine reports for the failing document

{
  "element": "cac:AllowanceCharge/cac:TaxCategory/cbc:Percent",
  "field": "cac:AllowanceCharge/cac:TaxCategory/cbc:Percent",
  "fix_hint": "Adjust the VAT breakdown at `cac:AllowanceCharge[cbc:ChargeIndicator=false()]/cac:TaxCategory[normalize-space(cbc:ID)='G'][cac:TaxScheme/normalize-space(upper-case(cbc:ID))='VAT']` so that In a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is \"Export outside the EU\" the Document level allowance VAT rate (BT-96) shall be 0 (zero).",
  "location": "cac:AllowanceCharge[cbc:ChargeIndicator=false()]/cac:TaxCategory[normalize-space(cbc:ID)='G'][cac:TaxScheme/normalize-space(upper-case(cbc:ID))='VAT']",
  "message": "In a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is 'Export outside the EU' the Document level allowance VAT rate (BT-96) shall be 0 (zero).",
  "rule": "BR-G-06",
  "severity": "fatal",
  "terms": [
    "BG-20",
    "BT-95",
    "BT-96"
  ],
  "title": "In an Export outside the EU (G) Document level allowance the allowance VAT rate (BT-96) shall be 0."
}

Rule ids reported for the failing document: BR-01 BR-02 BR-03 BR-04 BR-05 BR-06 BR-07 BR-08 BR-10 BR-16 BR-31 BR-33 BR-CO-18 BR-CO-21 BR-G-01 BR-G-03 BR-G-06. For the corrected document: BR-01 BR-02 BR-03 BR-04 BR-05 BR-06 BR-07 BR-08 BR-10 BR-16 BR-31 BR-33 BR-CO-18 BR-CO-21 BR-G-01 BR-G-03.

Read that pair of lists honestly. A unit case is not a complete invoice: the upstream suite strips the document down to the elements this rule reads, so the engine also reports every mandatory element the fragment leaves out — 16 other rule ids here. Those are noise for this page. The signal is the difference: BR-G-06 is reported for the failing document and gone for the corrected one, and it is the only id that moves.

Reproduce it yourself: save the failing block as invoice.xml and run einvoice validate invoice.xml --profile en16931 --format json, or paste it into the browser validator, which runs this same engine locally with no upload. Then apply the edit the passing block shows and run it again.