ValidateFin

BT-3 - Invoice type code

A code specifying the functional type of the invoice, from UNTDID 1001 (e.g. 380 commercial invoice, 381 credit note).

BT-3 - Invoice type code

A code specifying the functional type of the invoice, from UNTDID 1001 (e.g. 380 commercial invoice, 381 credit note).

Business termCardinality: 1..1Data type: CodeFactur-X: MINIMUM

Definition

A code specifying the functional type of the invoice, from UNTDID 1001 (e.g. 380 commercial invoice, 381 credit note).

Syntax mapping

Where this term appears in each of the three EN 16931 syntaxes.

SyntaxPath
UBL 2.1cbc:InvoiceTypeCode
UN/CEFACT CIIrsm:ExchangedDocument/ram:TypeCode
Factur-X / ZUGFeRDFactur-X profile: MINIMUM

The lowest Factur-X / ZUGFeRD profile in which this term is available.

Validation rules for this term

The EN 16931 / Peppol / XRechnung rules that reference this term.

BR-04Invoice type code is requiredBR-CL-01Invoice type code: UNTDID 1001PEPPOL-EN16931-P0100Invoice type code must match the Peppol profilePEPPOL-EN16931-P0101Credit note type code must match the Peppol profilePEPPOL-EN16931-P0112Type codes 326 and 384 are reserved for German tradeBR-DE-17Invoice type code should use the allowed UNTDID codes

Validate an invoice carrying this term

This term is defined by EN 16931. Check your invoice with the validator that matches your format:

UBL / PeppolXRechnungFactur-X / ZUGFeRD

Related terms

BT-1Invoice numberBT-2Invoice issue dateBT-5Invoice currency codeBT-6VAT accounting currency codeBT-7Value added tax point dateBT-8Value added tax point date codeBT-9Payment due dateBT-10Buyer reference

Source: EN 16931 semantic model. UBL paths checked against the official OASIS UBL 2.1 schema; rule links from the EN 16931 validation artefacts (EUPL 1.2, release 1.3.16) · Last verified: 2026-07-15

Not verified against: CEN/TS 16931-3-2 (UBL) and -3-3 (CII), the authoritative syntax bindings: paid specifications, not consulted

All business terms