What it means
Each ram:SpecifiedTradeSettlementPaymentMeans under ram:ApplicableHeaderTradeSettlement must contain one ram:TypeCode for BT-81. This rule counts code elements within each set of payment instructions; it does not check the code's value or require a payment instructions group to exist.
Why it matters
The payment means code identifies how payment is to be made. It distinguishes methods such as a bank transfer and a direct debit.
How to fix it
Check the payment method for the affected set of instructions in your invoicing software. In XML, keep one ram:TypeCode inside each ram:SpecifiedTradeSettlementPaymentMeans. Use the code for the actual method, such as 30 for a bank transfer, 58 for a SEPA bank transfer or 59 for a SEPA direct debit. 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
Element 'ram:TypeCode' must occur exactly 1 times. Where this rule applies
| Rule set | Version |
|---|---|
| Factur-X 1.09 BASIC WL | 1.0.9-2 |
| Factur-X 1.09 BASIC | 1.0.9-2 |
| Factur-X 1.09 EN 16931 | 1.0.9-2 |
| Factur-X 1.09 EXTENDED | 1.0.9-2 |
| ZUGFeRD 2.5 BASIC WL | 2.5.2 |
| ZUGFeRD 2.5 BASIC | 2.5.2 |
| ZUGFeRD 2.5 EN 16931 | 2.5.2 |
| ZUGFeRD 2.5 EXTENDED | 2.5.2 |
Check your file
Drop your e-invoice to see whether FX-SCH-A-000488 still fails, and which other rules do.
Related rules
- FX-SCH-A-000489 Use an allowed payment means code (Basic WL)
- FX-SCH-A-000490 Use an allowed invoice note subject code (Basic)
- FX-SCH-A-000491 Use an allowed invoice date format code (Basic)
- FX-SCH-A-000492 Use an allowed invoice type code (Basic)
- FX-SCH-A-000493 Use a specification identifier allowed by Basic
- FX-SCH-A-000494 Use an allowed buyer identifier scheme (Basic)