BT-3: Invoice Type Code
Code specifying the functional type of the invoice (e.g. 380 for commercial invoice, 381 for credit note).
Technical Specification
Mandatory (1..1) coded from UNTDID 1001
Semantic data format according to European Standard EN 16931-1
What does BT-3 mean?
The invoice type code (BT-3) defines the functional nature of the invoice based on UNTDID 1001 code list. It determines how receiving ERP systems account for amounts (e.g. standard invoice, credit note, advance payment invoice).
XML Syntax & Code Example
<cbc:InvoiceTypeCode listVersionID="1.0">380</cbc:InvoiceTypeCode>Codelist Values: UNTDID 1001 Invoice Types
| Code | Meaning | Description & Usage |
|---|---|---|
| 380 | Commercial invoice | Standard invoice for goods or services. |
| 381 | Credit note | Document crediting an amount to the buyer. |
| 384 | Corrected invoice | Invoice correcting a previously issued invoice. |
| 386 | Prepayment invoice | Invoice requesting payment in advance. |
| 389 | Self-billed invoice | Invoice issued by the buyer instead of the supplier. |
| 261 | Partial invoice | Invoice for part of a total agreed amount. |
| 325 | Proforma invoice | Preliminary bill of sale sent to buyers in advance. |
Business Rules & Schematron Checks
An invoice shall have an Invoice type code (BT-3) from UNTDID 1001.
Check BT-3 in your invoice
Use the XML paths above to locate BT-3. 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.
Related Business Terms (BTs)
Create compliant E-Invoices easily
Create XRechnung and ZUGFeRD invoices in Billance and check the exported file locally. Use this guide to understand BT-3 and review your invoice details before sending.