Skip to content

BT-32: Seller Tax Registration Identifier

The local tax registration number assigned to the seller by the tax authority.

BT-32Conditional RequirementEN 16931-1 / XRechnung 3.0 / ZUGFeRD 2.3

Technical Specification

Requirement & Cardinality
0..1(Conditional)

Conditional (0..1), alternative to BT-31

Data Type
Text (national tax number)

Semantic data format according to European Standard EN 16931-1

XML Syntax Mappings
UBL 2.1(XRechnung / Peppol BIS)
Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme/cbc:CompanyID (mit TaxScheme/ID = FC)
UN/CEFACT CII D16B(ZUGFeRD 2.3 / Factur-X)
rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:SpecifiedTaxRegistration/ram:ID[@schemeID="FC"]

What does BT-32 mean?

The tax registration identifier (BT-32) represents the local fiscal code (scheme FC). Commonly used by small business owners or freelancers without an EU VAT ID. In compliance with German tax rules, either BT-31 or BT-32 must be provided.

XML Syntax & Code Example

OASIS UBL 2.1 (XRechnung)
<cac:PartyTaxScheme>
  <cbc:CompanyID>123/456/78901</cbc:CompanyID>
  <cac:TaxScheme>
    <cbc:ID>FC</cbc:ID>
  </cac:TaxScheme>
</cac:PartyTaxScheme>

Check BT-32 in your invoice

Use the XML paths above to locate BT-32. A snippet illustrates this field; it is not a complete invoice. After correcting a value in the source application, export and check the entire file again.

Official specifications and rule sets

Requirements depend on the invoice profile and version. Consult the matching specification for mandatory fields, code lists and rules; Peppol-specific requirements do not automatically apply to every ZUGFeRD invoice.

Create compliant E-Invoices easily

Create XRechnung and ZUGFeRD invoices in Billance and check the exported file locally. Use this guide to understand BT-32 and review your invoice details before sending.