Reference
Markdown exportInvoice type codes (common in XRechnung)
Codes specifying the functional type of the document (invoice, credit note, partial invoice, etc.).
How these codes are used on invoices
Invoice type codes (common in XRechnung) is a standardized UNTDID 1001 code list used in structured invoices. Instead of free-text values, buyers, suppliers, ERP systems, and validators expect normalized codes such as 326 (Partial invoice), 380 (Commercial invoice), 381 (Credit note). Subset aligned with the invoice type codes commonly accepted in German XRechnung workflows.
UNTDID 1001
Subset aligned with the invoice type codes commonly accepted in German XRechnung workflows.
How to use this code list in production
Use Invoice type codes (common in XRechnung) when you need stable values across ERP source data, generated XML, and validation checks. Lock the allowed values before go-live, map legacy values before export, and make sure finance teams know which business cases require manual review.
Invoice type codes (common in XRechnung)
| Code | Meaning | Notes |
|---|---|---|
| 326 | Partial invoice | — |
| 380 | Commercial invoice | — |
| 381 | Credit note | — |
| 383 | Debit note | — |
| 384 | Corrected invoice | — |
| 386 | Prepayment invoice | — |
| 387 | Hire invoice | — |
| 389 | Self-billed invoice | — |
| 390 | Delcredere invoice | — |
| 393 | Factored invoice | — |
| 875 | Partial construction invoice | — |
| 876 | Partial final construction invoice | — |
| 877 | Final construction invoice | — |
Practical tips before you send an e-invoice
Use these points as the practical checks for this section.
- Use the exact code from UNTDID 1001 and keep the spelling and casing expected by the standard.
- Make sure the chosen Invoice type codes (common in XRechnung) value matches the business context and any related fields on the invoice.
- Validate the final XRechnung, ZUGFeRD/Factur-X, UBL, or CII file before sending it to the recipient.
Common code-list mistakes
Use these points as the practical checks for this section.
- Letting free-text values pass through the ERP export instead of mapping them to the official code list.
- Using a technically valid code without checking whether the recipient profile or country rule actually allows it.
- Fixing the XML output only, while leaving the upstream ERP source value inconsistent for the next invoice.
Frequently asked questions
These are common end-user questions when choosing the right Invoice type codes (common in XRechnung) value for an invoice or ERP export.
What is Invoice type codes (common in XRechnung) on an invoice?
Invoice type codes (common in XRechnung) is the standardized UNTDID 1001 code list that tells the receiving system which business value was intended. Using the correct code improves interoperability across XRechnung, ZUGFeRD/Factur-X, UBL, CII, and PEPPOL workflows.
Which Invoice type codes (common in XRechnung) codes are used most often?
Common examples on this page include 326 (Partial invoice), 380 (Commercial invoice), 381 (Credit note). The right choice depends on your transaction, tax treatment, recipient requirements, and the invoice profile you are sending.
Where do I enter a Invoice type codes (common in XRechnung) code in structured e-invoices?
Enter the code in the structured invoice field that matches its meaning, for example the currency field, VAT category field, payment means field, unit field, or invoice type field. The exact XML path depends on whether you send XRechnung, ZUGFeRD/Factur-X, UBL, or CII.
How do I avoid validation errors with Invoice type codes (common in XRechnung) codes?
Use only values allowed by the relevant implementation guide, keep the code exactly as defined in UNTDID 1001, and provide all related data required by that choice. Many validation errors happen when a code is correct in isolation but inconsistent with the rest of the invoice.
Can I use codes outside this page?
Often yes, but recipients and national profiles frequently accept only a practical subset of the full UNTDID 1001 list. This page focuses on common invoice values, so confirm buyer-specific or country-specific rules before sending production documents.
Download
Use this code list in your systems or validation rules.