Reference
Invoice 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.
This article treats Invoice type codes (common in XRechnung) as a practical reference, not just a navigation page. It explains the term or workflow in context, shows why it matters for European e-invoicing, and connects the topic to invoice creation, validation, routing, archiving, and ERP implementation decisions.
UNTDID 1001
Subset aligned with the invoice type codes commonly accepted in German XRechnung workflows.
Invoice type codes (common in XRechnung)
| Code | Meaning | Notes |
|---|---|---|
| 326 | Partial invoice | — |
| 380 | Commercial invoice | — |
| 381 | Credit note | — |
| 384 | Corrected invoice | — |
| 389 | Self-billed invoice | — |
| 875 | Partial construction invoice | — |
| 876 | Partial final construction invoice | — |
| 877 | Final construction invoice | — |
Practical tips before you send an e-invoice
Practical tips before you send an e-invoice is where the general explanation of Invoice type codes (common in XRechnung) becomes operational. The section focuses on 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… and Validate the final XRechnung, ZUGFeRD/Factur-X, UBL, or CII file before sending it to the…, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- 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.
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. Frequently asked questions answers the practical questions that usually appear after reading the main explanation of Invoice type codes (common in XRechnung). The answers focus on What is Invoice type codes (common in XRechnung) on an invoice, Which Invoice type codes (common in XRechnung) codes are used most often and Where do I enter a Invoice type codes (common in XRechnung) code in structured e-invoices and are written to clarify implementation choices quickly.
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. Download connects Invoice type codes (common in XRechnung) with the next useful reference pages and tools. These links are included to support a complete workflow, from understanding Download JSON and Download CSV to validating or converting the invoice file.
Official resources
Official resources connects Invoice type codes (common in XRechnung) with the next useful reference pages and tools. These links are included to support a complete workflow, from understanding UNTDID 1001 (document/invoice type codes), Free XRechnung Validator and API Playground to validating or converting the invoice file.