# BR-AF-04: Missing identifiers for category L (charge)

Source: https://veriport.io/einvoice-rules/br-af-04 (published 2026-11-17)

An invoice with a document-level charge (BG-21) in category L (« IGIC ») must contain the seller’s VAT identifier (BT-31), the seller’s tax registration identifier (BT-32, a national tax number) or the tax representative’s VAT identifier (BT-63). Below: the message, the cause and the fix, and an invoice our validator checked, failing and fixed.

- **Specification:** [EN 16931 business rules](/einvoice-rules/en16931), CEN EN 16931 validation artefacts 1.3.16
- **Severity:** error
- **Business terms:** BT-31, BT-32, BT-63, BT-102, BG-21
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-AF-04 is a rule of the EN 16931 business rules (CEN validation artefacts 1.3.16) for UBL and CII. It is an error (fatal): a validator rejects the invoice.

```text
[BR-AF-04]-An Invoice that contains a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "IGIC" shall contain the Seller VAT Identifier (BT-31), the Seller Tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63).
```

## What it checks

An invoice with a document-level charge (BG-21) in category L (« IGIC ») must contain the seller’s VAT identifier (BT-31), the seller’s tax registration identifier (BT-32, a national tax number) or the tax representative’s VAT identifier (BT-63). These identify who is liable for, or exempt from, the VAT on the amount.

## Why invoices fail it

The seller writes its tax number in a note or only on the PDF, so none of the identifiers is in the XML.

## How to fix it

Write the seller’s VAT identifier in BT-31, or its national tax number in BT-32.

## A failing invoice and its fix, checked

We start from our sample invoice (two lines at 19 %, Berlin to Stuttgart), written by our own generator as EN 16931 in UBL. The change below (`-` the failing version, `+` the fixed one) makes the rule fail. Both versions went through our validator on 2026-11-17 (the XML schema and the official rule files, as `POST /einvoice/validate` runs them): the fixed one is valid, the failing one reports BR-AF-04 and 2 other rules, as a real file with this mistake would.

| Rule | Severity | Where | Message |
|---|---|---|---|
| [BR-AF-02](/einvoice-rules/br-af-02) | error | `/ubl:Invoice` | An Invoice that contains an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "IGIC" shall contain the Seller VAT Identifier (BT-31), the Seller tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63). |
| **BR-AF-04** | error | `/ubl:Invoice` | An Invoice that contains a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "IGIC" shall contain the Seller VAT Identifier (BT-31), the Seller Tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63). |
| [BR-CO-26](/einvoice-rules/br-co-26) | error | `/ubl:Invoice/cac:AccountingSupplierParty` | In order for the buyer to automatically identify a supplier, the Seller identifier (BT-29), the Seller legal registration identifier (BT-30) and/or the Seller VAT identifier (BT-31) shall be present. |

```diff
  …
          </cac:Country>
        </cac:PostalAddress>
+       <cac:PartyTaxScheme>
+         <cbc:CompanyID>DE136695976</cbc:CompanyID>
+         <cac:TaxScheme>
+           <cbc:ID>VAT</cbc:ID>
+         </cac:TaxScheme>
+       </cac:PartyTaxScheme>
        <cac:PartyLegalEntity>
          <cbc:RegistrationName>Lena Hartmann — Webdesign</cbc:RegistrationName>
  …
```

## The rule as published

Where the rule applies (`context`) and what must hold (`test`), unmodified from CEN EN 16931 validation artefacts 1.3.16. An `assert` fails when its test is false.

Text and test: © CEN/TC 434, EN 16931 validation artefacts, EUPL 1.2. Quoted unmodified; the explanations on this page are Veriport’s.

```xpath
context: /ubl:Invoice | /cn:CreditNote
test:    (exists(//cac:AllowanceCharge[cbc:ChargeIndicator=true()]/cac:TaxCategory[normalize-space(cbc:ID)='L'][cac:TaxScheme/normalize-space(upper-case(cbc:ID))='VAT']) and (exists(//cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme/cbc:CompanyID) or exists(//cac:TaxRepresentativeParty/cac:PartyTaxScheme[cac:TaxScheme/(normalize-space(upper-case(cbc:ID)) = 'VAT')]/cbc:CompanyID))) or not(exists(//cac:AllowanceCharge[cbc:ChargeIndicator=true()]/cac:TaxCategory[cbc:ID='L'][cac:TaxScheme/normalize-space(upper-case(cbc:ID))='VAT']))
```

```xpath
context: //ram:SpecifiedTradeAllowanceCharge[ram:ChargeIndicator/udt:Indicator=true()]/ram:CategoryTradeTax[ram:CategoryCode = 'L'][upper-case(ram:TypeCode) = 'VAT']
test:    /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:SpecifiedTaxRegistration/ram:ID[@schemeID = ('VA', 'FC')] or /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTaxRepresentativeTradeParty/ram:SpecifiedTaxRegistration/ram:ID[@schemeID = 'VA']
```

## Check your own invoice

Drop your XRechnung, ZUGFeRD or Peppol file into a free validator ([Peppol BIS](/tools/peppol-validator), [XRechnung](/tools/xrechnung-pruefen), [Factur-X](/tools/valider-factur-x)): each runs the same rule files and links every finding to its rule page. From your own code, `POST /einvoice/validate` ([reference](/docs/einvoice)) returns the same check as JSON, each finding with an `explanation` field pointing here (5 calls a check, anonymous within the daily allowance).

## Read next

- [BR-AF-02: Missing identifiers for category L (line)](https://veriport.io/einvoice-rules/br-af-02)
- [BR-AF-03: Missing identifiers for category L (allowance)](https://veriport.io/einvoice-rules/br-af-03)
- [BR-AF-05: Category L: wrong rate on a line](https://veriport.io/einvoice-rules/br-af-05)
- [BR-AF-06: Category L: wrong rate on an allowance](https://veriport.io/einvoice-rules/br-af-06)
- [BR-37: Document charge VAT category (BT-102) missing](https://veriport.io/einvoice-rules/br-37)
- [BR-AG-04: Missing identifiers for category M (charge)](https://veriport.io/einvoice-rules/br-ag-04)
- [All EN 16931 business rules](https://veriport.io/einvoice-rules/en16931)
- [All e-invoice rules, search](https://veriport.io/einvoice-rules)
- [Check an e-invoice free (XRechnung prüfen)](https://veriport.io/tools/xrechnung-pruefen)
- [Create a valid e-invoice free (German form)](https://veriport.io/tools/e-rechnung-erstellen)

## Sources

- EN 16931 validation artefacts 1.3.16 (UBL and CII schematron, the business rules BR-*) — https://github.com/ConnectingEurope/eInvoicing-EN16931/releases/tag/validation-1.3.16 (2026-10-28)
- EN 16931 validation artefacts: licence, European Union Public Licence (EUPL) v1.2 (LICENSE.txt, the README « License » section and the release notes of validation-1.3.16) — https://github.com/ConnectingEurope/eInvoicing-EN16931/blob/master/LICENSE.txt (2026-11-17)
