Skip to content

BT-126: Invoice Line Identifier

Unique identifier for the individual invoice line.

BT-126Mandatory (1..1)EN 16931-1 / XRechnung 3.0 / ZUGFeRD 2.3

Technical Specification

Requirement & Cardinality
1..1(Mandatory)

Mandatory (1..1) within each invoice line (BG-25)

Data Type
Text (unique line identifier, e.g. 1, 2, 3)

Semantic data format according to European Standard EN 16931-1

XML Syntax Mappings
UBL 2.1(XRechnung / Peppol BIS)
Invoice/cac:InvoiceLine/cbc:ID
UN/CEFACT CII D16B(ZUGFeRD 2.3 / Factur-X)
rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem/ram:AssociatedDocumentLineDocument/ram:LineID

What does BT-126 mean?

BT-126 provides an unambiguous line identifier within the invoice dataset, referenced by validation logs and order matching systems.

XML Syntax & Code Example

OASIS UBL 2.1 (XRechnung)
<cac:InvoiceLine>
  <cbc:ID>1</cbc:ID>
  <cbc:InvoicedQuantity unitCode="HUR">10</cbc:InvoicedQuantity>
  <cbc:LineExtensionAmount currencyID="EUR">1200.00</cbc:LineExtensionAmount>
</cac:InvoiceLine>

Business Rules & Schematron Checks

BR-21

Each Invoice line shall have an Invoice line identifier (BT-126).

Check BT-126 in your invoice

Use the XML paths above to locate BT-126. 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-126 and review your invoice details before sending.