# 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-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.

## 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

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

## Invalid Examples

- 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](/resources/xrechnung/bt-1-invoice-number)
- [BT-2 Invoice Issue Date](/resources/xrechnung/bt-2-invoice-issue-date)
- [BT-25 Preceding invoice reference](/resources/xrechnung/bt-25-preceding-invoice-reference)
- [BT-26 Preceding invoice issue date](/resources/xrechnung/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](https://erechnungsvalidator.service-bw.de/)
- [Invoice Converter](/pdf-to-xrechnung)
- [XRechnung Standard](https://xeinkauf.de/xrechnung/)
- [Test Suite](https://github.com/itplr-kosit/xrechnung-testsuite)