Reference
Unit of measure codes (common)
Common unit codes used for invoice line quantities (e.g., piece, hour, kilogram).
How these codes are used on invoices
Unit of measure codes (common) is a standardized UNECE Rec 20/21 code list used in structured invoices. Instead of free-text values, buyers, suppliers, ERP systems, and validators expect normalized codes such as C62 (One), EA (Each), PCE (Piece). This list focuses on units commonly used on invoices; official lists contain many more codes.
This article treats Unit of measure codes (common) 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.
UNECE Rec 20/21
This list focuses on units commonly used on invoices; official lists contain many more codes.
Unit of measure codes (common)
| Code | Meaning | Notes |
|---|---|---|
| C62 | One | — |
| EA | Each | — |
| PCE | Piece | — |
| HUR | Hour | — |
| MIN | Minute | — |
| SEC | Second | — |
| DAY | Day | — |
| WEE | Week | — |
| MON | Month | — |
| ANN | Year | — |
| MMT | Millimetre | — |
| CMT | Centimetre | — |
| MTR | Metre | — |
| KMT | Kilometre | — |
| MTK | Square metre | — |
| MTQ | Cubic metre | — |
| GRM | Gram | — |
| KGM | Kilogram | — |
| TNE | Tonne | — |
| LTR | Litre | — |
Practical tips before you send an e-invoice
Practical tips before you send an e-invoice is where the general explanation of Unit of measure codes (common) becomes operational. The section focuses on Use the exact code from UNECE Rec 20/21 and keep the spelling and casing expected by the…, Make sure the chosen Unit of measure codes (common) value matches the business context and any… 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 UNECE Rec 20/21 and keep the spelling and casing expected by the standard.
- Make sure the chosen Unit of measure codes (common) 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 Unit of measure codes (common) value for an invoice or ERP export. Frequently asked questions answers the practical questions that usually appear after reading the main explanation of Unit of measure codes (common). The answers focus on What is Unit of measure codes (common) on an invoice, Which Unit of measure codes (common) codes are used most often and Where do I enter a Unit of measure codes (common) code in structured e-invoices and are written to clarify implementation choices quickly.
What is Unit of measure codes (common) on an invoice?
Unit of measure codes (common) is the standardized UNECE Rec 20/21 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 Unit of measure codes (common) codes are used most often?
Common examples on this page include C62 (One), EA (Each), PCE (Piece). The right choice depends on your transaction, tax treatment, recipient requirements, and the invoice profile you are sending.
Where do I enter a Unit of measure codes (common) 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 Unit of measure codes (common) codes?
Use only values allowed by the relevant implementation guide, keep the code exactly as defined in UNECE Rec 20/21, 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 UNECE Rec 20/21 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 Unit of measure codes (common) 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 Unit of measure codes (common) with the next useful reference pages and tools. These links are included to support a complete workflow, from understanding UNECE Recommendation 20/21 unit codes, Free XRechnung Validator and API Playground to validating or converting the invoice file.