Reference
Payment means type codes
Codes describing how payment is (or will be) settled (transfer, SEPA, card, cash, etc.).
How these codes are used on invoices
Payment means type codes is a standardized UNCL 4461 code list used in structured invoices. Instead of free-text values, buyers, suppliers, ERP systems, and validators expect normalized codes such as 10 (Cash), 30 (Credit transfer (bank transfer)), 48 (Bank card). Common codes used in e-invoices and SEPA/European workflows.
This article treats Payment means type codes 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.
UNCL 4461
Common codes used in e-invoices and SEPA/European workflows.
Payment means type codes
| Code | Meaning | Notes |
|---|---|---|
| 10 | Cash | — |
| 30 | Credit transfer (bank transfer) | — |
| 48 | Bank card | — |
| 49 | Direct debit | — |
| 54 | Credit card | — |
| 58 | SEPA credit transfer | — |
| 59 | SEPA direct debit | — |
| 68 | Online payment service | — |
| 69 | Telephone payment | — |
| 70 | Mobile payment | — |
Practical tips before you send an e-invoice
Practical tips before you send an e-invoice is where the general explanation of Payment means type codes becomes operational. The section focuses on Use the exact code from UNCL 4461 and keep the spelling and casing expected by the standard, Make sure the chosen Payment means type codes 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 UNCL 4461 and keep the spelling and casing expected by the standard.
- Make sure the chosen Payment means type codes 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 Payment means type codes value for an invoice or ERP export. Frequently asked questions answers the practical questions that usually appear after reading the main explanation of Payment means type codes. The answers focus on What is Payment means type codes on an invoice, Which Payment means type codes codes are used most often and Where do I enter a Payment means type codes code in structured e-invoices and are written to clarify implementation choices quickly.
What is Payment means type codes on an invoice?
Payment means type codes is the standardized UNCL 4461 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 Payment means type codes codes are used most often?
Common examples on this page include 10 (Cash), 30 (Credit transfer (bank transfer)), 48 (Bank card). The right choice depends on your transaction, tax treatment, recipient requirements, and the invoice profile you are sending.
Where do I enter a Payment means type codes 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 Payment means type codes codes?
Use only values allowed by the relevant implementation guide, keep the code exactly as defined in UNCL 4461, 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 UNCL 4461 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 Payment means type codes 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 Payment means type codes with the next useful reference pages and tools. These links are included to support a complete workflow, from understanding UN/CEFACT code list UNCL 4461, Free XRechnung Validator and API Playground to validating or converting the invoice file.