Skip to main content
Invoice-Converter.comInvoice-Converter
BlogPricing
Convert InvoiceConvert
Convert
โŒ˜K
Documentation overview
Understand formats and standards
Compliance Guides
XRechnung Standard
ZUGFeRD Format
PDF/A-3 for ZUGFeRD
CII Cross Industry Invoice
UBL Universal Business Language
DIN EN 16931-1 Standard
PEPPOL Network
Country and regulatory rules
EU E-Invoicing Mandate
EU E-Invoicing
EU e-invoicing in 2026: what to implement (and why)
EU top markets playbook (DE, FR, IT, ES, PL, NL)
PEPPOL in the EU: how exchange actually works
CTC/clearance and portals in the EU: how to build reliable integrations
Country Guides
Germany
France
Italy
Spain
Poland
Netherlands
Belgium
Austria
Denmark
Sweden
Finland
Fix validation and submission issues
Leitweg-ID Validation
Support playbooks
Support
Why invoices need review
API errors
API automation
Handling schema errors
Review validation help
Support
Missing information
Buyer reference
Payment and IBAN
VAT and reverse charge
Totals and rounding
Prepayments
Line items
ZUGFeRD PDF warnings
Validation playbooks
Observed validation fixes
Due date or terms
Bank transfer IBAN
PDF/A-3 readiness
VATEX exemption reason
Review vs download
Public test invoice fixture library
Valid XRechnung UBL basic invoice
Invalid XRechnung missing payment terms
Factur-X/ZUGFeRD EN 16931 CII XML
XRechnung rounding and IBAN edge case
KoSIT Validator Errors
ERROR
BR-DE-1
BR-DE-2
BR-DE-3
BR-DE-4
BR-DE-5
BR-DE-6
BR-DE-7
BR-DE-8
BR-DE-9
BR-DE-10
BR-DE-11
BR-DE-12
BR-DE-13
BR-DE-14
BR-DE-15
BR-DE-16
BR-DE-17
BR-DE-18
BR-DE-19
BR-DE-20
BR-DE-21
BR-CO-3
BR-CO-4
BR-CO-9
BR-CO-10
BR-CO-11
BR-CO-13
BR-CO-14
BR-CO-15
BR-CO-16
BR-CO-17
BR-CO-25
BR-CO-26
BR-S-1
BR-S-5
BR-S-8
BR-61
BR-AE-02
BR-AE-10
BR-E-01
BR-E-05
BR-05
BR-22
BR-23
BR-24
BR-25
BR-26
BR-47
BR-57
BR-DE-22
BR-DE-30
BR-DE-31
PEPPOL-EN16931-R001
PEPPOL-EN16931-R010
PEPPOL-EN16931-R020
PEPPOL-EN16931-R046
PEPPOL-EN16931-R120
PEPPOL-EN16931-R130
WARNING
BR-DE-26
BR-DE-27
BR-DE-28
Look up reference data
Glossary
E
EN 16931
E-reporting
e-Factura RO
EAS (Electronic Address Scheme)
ebInterface
C
CIUS
CII
Code list
Credit note
Contract reference
Chorus Pro
Codice Destinatario
X
XRechnung
XML Schema (XSD)
XML
Z
ZUGFeRD
F
Factur-X
Finvoice
U
UBL
Unit code
P
PEPPOL
PEPPOL BIS
Participant ID
PDF/A-3
Payment means
Purchase order (PO)
PDP (Plateforme de Dรฉmatรฉrialisation Partenaire)
A
Access Point
Allowance / charge
S
SMP
SML
Schematron
SDI (Sistema di Interscambio)
Svefaktura
L
Leitweg-ID
K
KoSIT
KSeF
KvK number
V
Validation
VAT ID
ViDA
VeriFactu
ViDA Pillar 1: Digital Reporting Requirements
ViDA Pillar 2: Single VAT Registration
ViDA Pillar 3: Platform Economy
B
Business Term (BT)
Business Group (BG)
BIC
R
Reverse charge
Real-time reporting
Real-time invoice reporting (RTIR)
T
Tax category
TicketBAI
I
IBAN
Invoice type code
Invoice line item
ISO 6523
D
Document reference
D-U-N-S Number
Digipoort
Q
QR code payment
G
GLN (Global Location Number)
O
OVT-tunnus
OIOUBL
N
NemHandel
Code Lists
Currency codes (common)
Country codes (common)
VAT category codes
Payment means type codes
Unit of measure codes (common)
Invoice type codes (common in XRechnung)
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
MINIMUM
BASIC WL
BASIC
EN 16931
EXTENDED
Compare formats and tools
Comparisons
PDF24 Tools
sevDesk
Integrate and implement
Platform incident help
Support
Temporary unavailable
Missing result
Validation unavailable
Browser errors
Account and rate limits
Credits and subscriptions
Authoritative validation
ERP export validation guides
DATEV
Lexware
SAP Business One
Odoo
Microsoft Dynamics
Trust & Security
Developer API
  1. E-Invoicing Resources
  2. XRechnung Fields
  3. BT-3

Reference

Markdown export

BT-3 Invoice Type Code

A code specifying the functional type of the Invoice (UNTDID 1001). XRechnung supports specific invoice type codes: 326 (Partial invoice), 380 (Commercial invoice), 384 (Corrected invoice), 389 (Self-billed invoice), 381 (Credit note), 875 (Partial construction invoice), 876 (Partial final construction invoice), 877 (Final construction invoice).

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-3 (Invoice type code) classifies the document under UNTDID 1001. Mandatory under EN 16931, it tells the receiver whether the document is a commercial invoice (380), credit note (381), or corrected invoice (384). XRechnung restricts the code list further. Example: 380.

BT-3 ยท EN 16931 / XRechnung 3.x

BT Reference Card#

Canonical EN 16931 / XRechnung facts for this business term โ€” citable from this anchor.

BT code
BT-3
Name
Invoice Type Code
Cardinality
Mandatory (M)
Business group
Document
Data type
Code
Example value
380
Common error
BR-4: An Invoice shall have an Invoice type code. The code must come from UNTDID 1001; XRechnung restricts the allowed subset to commercial invoices (380), credit notes (381), corrected invoices (384), self-billed (389), and partial invoices (326).

Quick answer#

A code specifying the functional type of the Invoice (UNTDID 1001). XRechnung supports specific invoice type codes: 326 (Partial invoice), 380 (Commercial invoice), 384 (Corrected invoice), 389 (Self-billed invoice), 381 (Credit note), 875 (Partial construction invoice), 876 (Partial final construction invoice), 877 (Final construction invoice).

Invoice basics

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

Quick actions

Validate XMLConvert invoice

In plain language#

A code specifying the functional type of the Invoice (UNTDID 1001). XRechnung supports specific invoice type codes: 326 (Partial invoice), 380 (Commercial invoice), 384 (Corrected invoice), 389 (Self-billed invoice), 381 (Credit note), 875 (Partial construction invoice), 876 (Partial final construction invoice), 877 (Final construction invoice).

A code specifying the functional type of the Invoice (UNTDID 1001). XRechnung supports specific invoice type codes: 326 (Partial invoice), 380 (Commercial invoice), 384 (Corrected invoice), 389 (Self-billed invoice), 381 (Credit note), 875 (Partial construction invoice), 876 (Partial final construction invoice), 877 (Final construction invoice).

The invoice type code classifies the purpose and legal nature of the document. Most common is 380 (Commercial invoice) for standard invoices and 381 (Credit note) for refunds or corrections.

What you usually enter here#

Three-digit numeric code from UNTDID 1001

Typical valid values include: 380, 381, 384, 389

Mandatory according to EN 16931-1. XRechnung restricts to specific codes for German e-invoicing compliance.

What goes wrong often#

Avoid values like: 01, 02, 05, 999

Relevant rule codes: BR-2, BR-DE-17

Examples in context#

The invoice type code classifies the purpose and legal nature of the document. Most common is 380 (Commercial invoice) for standard invoices and 381 (Credit note) for refunds or corrections.

Mandatory according to EN 16931-1. XRechnung restricts to specific codes for German e-invoicing compliance.

Valid Examples#

Use these points as the practical checks for this section.

  • 380
  • 381
  • 384
  • 389
  • 326
  • 875
  • 876
  • 877

Invalid Examples#

Use these points as the practical checks for this section.

  • 01
  • 02
  • 05
  • 999
  • INV
  • CN

Related Fields#

The invoice type code classifies the purpose and legal nature of the document. Most common is 380 (Commercial invoice) for standard invoices and 381 (Credit note) for refunds or corrections.

BT-1 Invoice Number
BT-2 Invoice Issue Date
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-3

Data Type:

code

Cardinality:

1..1

Requirement:

Mandatory

Since Version:

XRechnung 1.0+

XML Implementation#

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

Validation Rules#

BR-2

BR-2

BR-DE-17

BR-DE-17

Why the standard cares about this field#

Business Context

The invoice type code classifies the purpose and legal nature of the document. Most common is 380 (Commercial invoice) for standard invoices and 381 (Credit note) for refunds or corrections.

Legal Requirement

Mandatory according to EN 16931-1. XRechnung restricts to specific codes for German e-invoicing compliance.

FAQ#

What is the most common invoice type code?

Code 380 (Commercial invoice) is the most commonly used for standard business invoices.

When should I use code 381 instead of 380?

Use code 381 (Credit note) when issuing a refund, correction, or reduction of a previously issued invoice amount.

What are the construction-specific invoice type codes?

Codes 875, 876, and 877 are used for construction invoices: 875 (Partial construction invoice), 876 (Partial final construction invoice), 877 (Final construction invoice).

Official sources and tools#

KoSIT Validator
Invoice Converter
XRechnung Standard
Test Suite
BT-2BT-5
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