Skip to main content
Invoice-Converter.comInvoice-Converter
BlogPricing
Convert InvoiceConvert
ConvertConvert Invoice
⌘K
Documentation overview
Glossary
Code Lists
XRechnung Fields
Invoice basics
BT-1
BT-2
BT-3
BT-5
BT-6
BT-7
BT-8
BT-10
BT-11
BT-12
BT-14
BT-15
BT-16
BT-17
BT-18
BT-19
BT-21
BT-22
BT-23
BT-24
BT-25
BT-26
Delivery and payment
BT-9
BT-13
BT-20
BT-59
BT-60
BT-61
BT-70
BT-71
BT-72
BT-73
BT-74
BT-75
BT-76
BT-77
BT-78
BT-79
BT-80
BT-81
BT-82
BT-83
BT-84
BT-85
BT-86
BT-87
BT-88
BT-89
BT-90
BT-91
Seller details
BT-27
BT-28
BT-29
BT-30
BT-31
BT-32
BT-33
BT-34
BT-35
BT-36
BT-37
BT-38
BT-39
BT-40
BT-41
BT-42
BT-43
BT-62
BT-63
BT-64
BT-65
BT-66
BT-67
BT-68
BT-69
Buyer details
BT-44
BT-45
BT-46
BT-47
BT-48
BT-49
BT-50
BT-51
BT-52
BT-53
BT-54
BT-55
BT-56
BT-57
BT-58
Discounts and charges
BT-92
BT-93
BT-94
BT-95
BT-96
BT-97
BT-98
BT-99
BT-100
BT-101
BT-102
BT-103
BT-104
BT-105
Taxes and totals
BT-106
BT-107
BT-108
BT-109
BT-110
BT-111
BT-112
BT-113
BT-114
BT-115
BT-116
BT-117
BT-118
BT-119
BT-120
BT-121
BT-122
BT-123
BT-124
BT-125
Line items
BT-126
BT-127
BT-128
BT-129
BT-130
BT-131
BT-132
BT-133
BT-134
BT-135
BT-136
BT-137
BT-138
BT-139
BT-140
BT-141
BT-142
BT-143
BT-144
BT-145
BT-146
BT-147
BT-148
BT-149
BT-150
BT-151
BT-152
BT-153
BT-154
BT-155
BT-156
BT-157
BT-158
BT-159
BT-160
BT-161
BT-162
BT-163
BT-164
BT-165
BT-185
BT-186
ZUGFeRD Profiles
  1. E-Invoicing Resources
  2. XRechnung Fields
  3. BT-1

Reference

Markdown export

BT-1 Invoice Number

A unique identification of the Invoice. The identification scheme shall provide uniqueness within the business relationship between the Seller and the Buyer.

BT Reference CardQuick answerIn plain languageWhat you usually enter hereWhat goes wrong oftenExamples in contextValid ExamplesInvalid ExamplesRelated FieldsXML mapping and field factsXML ImplementationValidation RulesWhy the standard cares about this fieldFAQOfficial sources and tools

BT-1 (Invoice number) is the unique identifier the seller assigns to the invoice. It is mandatory under EN 16931 and German UStG §14, must be unique per supplier per fiscal year, and is the primary key both buyer and tax authorities use to reference the document. Example: 2024-INV-0042.

BT-1 · EN 16931 / XRechnung 3.x

BT Reference Card#

Canonical EN 16931 / XRechnung facts for this business term — citable from this anchor.

BT code
BT-1
Name
Invoice Number
Cardinality
Mandatory (M)
Business group
Document
Data type
Identifier
Example value
2024-INV-0042
Common error
BR-2: An Invoice shall have an Invoice number. The number must be unique per supplier per fiscal year (German UStG §14 sequential numbering).

Quick answer#

A unique identification of the Invoice. The identification scheme shall provide uniqueness within the business relationship between the Seller and the Buyer.

Invoice basics

Core document identifiers, dates, process identifiers, and high-level invoice context.

In plain language#

A unique identification of the Invoice. The identification scheme shall provide uniqueness within the business relationship between the Seller and the Buyer.

A unique identification of the Invoice. The identification scheme shall provide uniqueness within the business relationship between the Seller and the Buyer.

The invoice number serves as the primary identifier for the invoice and is essential for accounting, payment processing, and legal compliance. It must be unique within the business relationship.

What you usually enter here#

Alphanumeric string without spaces or special characters except hyphens

Typical valid values include: INV-2024-001, RE20240327001, R-2024-03-15-001, 2024-INV-12345

Mandatory according to EN 16931-1. German tax law (UStG) requires invoices to have consecutive numbering within one or more series.

What goes wrong often#

Avoid values like: , , INV 001, INV/001/2024

Relevant rule codes: BR-2

Examples in context#

The invoice number serves as the primary identifier for the invoice and is essential for accounting, payment processing, and legal compliance. It must be unique within the business relationship.

Mandatory according to EN 16931-1. German tax law (UStG) requires invoices to have consecutive numbering within one or more series.

Valid Examples#

Use these points as the practical checks for this section.

  • INV-2024-001
  • RE20240327001
  • R-2024-03-15-001
  • 2024-INV-12345
  • F-20240327-001

Invalid Examples#

Use these points as the practical checks for this section.

  • INV 001
  • INV/001/2024

Related Fields#

The invoice number serves as the primary identifier for the invoice and is essential for accounting, payment processing, and legal compliance. It must be unique within the business relationship.

BT-2 Invoice Issue Date
BT-3 Invoice Type Code
BT-25 Preceding invoice reference
BT-26 Preceding invoice issue date

XML mapping and field facts#

Open the technical reference if you need XML paths, validator rule codes, legal wording, or schema-specific mapping details.

Field ID:

BT-1

Data Type:

text

Cardinality:

1..1

Requirement:

Mandatory

Max Length:

35 characters

Since Version:

XRechnung 1.0+

XML Implementation#

UBL 2.1 Syntax
/Invoice/cbc:ID
CII (UN/CEFACT) Syntax
/CrossIndustryInvoice/ExchangedDocument/ram:ID

Validation Rules#

BR-2

BR-2

Why the standard cares about this field#

Business Context

The invoice number serves as the primary identifier for the invoice and is essential for accounting, payment processing, and legal compliance. It must be unique within the business relationship.

Legal Requirement

Mandatory according to EN 16931-1. German tax law (UStG) requires invoices to have consecutive numbering within one or more series.

FAQ#

Can I use the same invoice number for different customers?

Yes, the invoice number only needs to be unique within the business relationship between you and each specific customer.

What are the requirements for invoice numbering in Germany?

German tax law requires consecutive numbering within one or more series. The numbering system must be designed to prevent gaps and duplicates.

Official sources and tools#

KoSIT Validator
Invoice Converter
XRechnung Standard
Test Suite
XRechnung FieldsBT-2
On this page
BT Reference CardQuick answerIn plain languageWhat you usually enter hereWhat goes wrong oftenExamples in contextValid ExamplesInvalid ExamplesRelated FieldsXML mapping and field factsXML ImplementationValidation RulesWhy the standard cares about this fieldFAQOfficial sources and tools

Invoice-Converter.com

Empowering businesses across Europe to effortlessly comply with XRechnung regulations. Join hundreds who've automated their invoice conversion process.

20,000+ invoices processed
Fast & Secure
Trusted by hundreds

Features

Convert PDFs & create

  • PDF to XRechnung
  • PDF to UBL
  • PDF to XRechnung (CII)
  • PDF to ZUGFeRD
  • PDF to Factur-X
  • Create XRechnung
  • XRechnung to PDF

View & validate

  • XRechnung/XML Viewer
  • XRechnung Validator

Quick Links

  • Resources
  • Trust & Security Center
  • Developer API Documentation
  • Blog
  • FAQ
  • Pricing
  • Climate Contribution

Legal

  • Imprint
  • Privacy Policy
  • Data Processing Agreement
  • Terms & Conditions
  • Money-Back Guarantee

Get in Touch

contact@invoice-converter.com
Start Converting
© 2026 Invoice-Converter.com.Made with in Europe
GDPR Compliant
German Server