Reference
Markdown exportPayment 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), 1 (Instrument not defined), 20 (Cheque). Common codes used in e-invoices and SEPA/European workflows.
UNCL 4461
Common codes used in e-invoices and SEPA/European workflows.
How to use this code list in production
Use Payment means type codes 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.
Payment means type codes
| Code | Meaning | Notes |
|---|---|---|
| 10 | Cash | — |
| 1 | Instrument not defined | — |
| 20 | Cheque | — |
| 30 | Credit transfer (bank transfer) | — |
| 42 | Payment to bank account | — |
| 48 | Bank card | — |
| 49 | Direct debit | — |
| 54 | Credit card | — |
| 57 | Standing agreement | — |
| 58 | SEPA credit transfer | — |
| 59 | SEPA direct debit | — |
| 68 | Online payment service | — |
| 69 | Telephone payment | — |
| 70 | Mobile payment | — |
| 97 | Clearing between partners | — |
Practical tips before you send an e-invoice
Use these points as the practical checks for this section.
- 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.
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 Payment means type codes value for an invoice or ERP export.
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), 1 (Instrument not defined), 20 (Cheque). 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.