What it means
This rule checks ram:TypeCode inside ram:SpecifiedTradeSettlementPaymentMeans. A non-empty value must belong to the profile's UNTDID 4461 code list. Examples include 30 for a bank transfer, 58 for a SEPA bank transfer, 59 for a SEPA direct debit and 48 for a bank card. Empty values pass this code-list check.
Why it matters
The code identifies the payment method. It should describe the payment arrangement rather than a different method chosen merely to pass the check.
How to fix it
Check the agreed payment method in your invoice data. If you generate XML, correct ram:SpecifiedTradeSettlementPaymentMeans/ram:TypeCode to the matching code. Use 58 only for a SEPA bank transfer, not automatically for every payment within the euro area. Generate the file again and recheck it.
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 EN 16931 | 1.0.9-2 |
| ZUGFeRD 2.5 EN 16931 | 2.5.2 |
Check your file
Drop your e-invoice to see whether FX-SCH-A-000609 still fails, and which other rules do.
Related rules
- FX-SCH-A-000610 Use a recognised VAT accounting currency code
- FX-SCH-A-000611 Check the unit for the price before discount
- FX-SCH-A-000612 The net price quantity needs a valid unit code
- FX-SCH-A-000613 The invoiced quantity needs a valid unit code
- FX-SCH-A-000614 A line can have at most one buyer accounting reference
- FX-SCH-A-000615 Each line reference needs one identifier element