What it means
In the Basic profiles of Factur-X and ZUGFeRD, this rule checks a non-empty payment means code against the permitted UNTDID 4461 list. Examples are 30 for bank transfer, 58 for SEPA bank transfer, 59 for SEPA direct debit, 49 for direct debit, 48 for bank card and 10 for cash. It checks the code, not whether the chosen method or payment details are appropriate.
Why it matters
Payment means codes distinguish transfers, direct debits, cards and other payment methods. The code should describe how you intend the invoice to be paid.
How to fix it
Check the intended payment method (BT-81). Use 58 only for a SEPA bank transfer, not simply because the transfer is within Europe. In XML, put the appropriate code in ram:SpecifiedTradeSettlementPaymentMeans/ram:TypeCode without explanatory text. If your software exports an invalid code, report this rule id to its supplier. Export and recheck.
Once the file is corrected, check it again for free: Validate a ZUGFeRD invoice
Or fix the invoice in a form and download the corrected file, for 1 credit: Fix a rejected e-invoice Beta
The rule as published
Value of 'ram:TypeCode' is not allowed. Where this rule applies
| Rule set | Version |
|---|---|
| Factur-X 1.09 BASIC | 1.0.9-2 |
| ZUGFeRD 2.5 BASIC | 2.5.2 |
Check your file
Drop your e-invoice to see whether FX-SCH-A-000527 still fails, and which other rules do.
Related rules
- FX-SCH-A-000528 Use a valid VAT accounting currency code
- FX-SCH-A-000529 A line note needs exactly one text element
- FX-SCH-A-000530 A price discount needs exactly one charge indicator
- FX-SCH-A-000531 A price discount needs exactly one amount element
- FX-SCH-A-000532 The net price needs exactly one amount element
- FX-SCH-A-000533 Use a valid unit code for the price base quantity