What it means
In the EN 16931 and Extended profiles of Factur-X and ZUGFeRD, this rule selects ram:AdditionalReferencedDocument elements under ram:ApplicableHeaderTradeAgreement that already contain ram:TypeCode equal to 130. It then requires one ram:TypeCode per selected element. Because the context already requires a type code of 130, this rule fails on repeated type-code elements, not on a missing type code.
Why it matters
The type code classifies the reference as an invoiced-object reference. Repeating the element breaks the required structure even when the repeated values are identical.
How to fix it
Correct the affected ram:AdditionalReferencedDocument so it contains one ram:TypeCode with the value 130. Put any genuine references of other types in their own appropriately coded blocks. If your invoicing software generates the repeated elements, give its supplier this rule id and ask for an export correction. Export the corrected invoice and check it again.
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 EN 16931 | 1.0.9-2 |
| Factur-X 1.09 EXTENDED | 1.0.9-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-000558 still fails, and which other rules do.
Related rules
- FX-SCH-A-000559 A reference to the invoiced object must use the type code 130
- FX-SCH-A-000560 A tender or lot reference needs exactly one identifier
- FX-SCH-A-000561 A tender or lot reference needs exactly one type code
- FX-SCH-A-000562 A tender or lot reference must use the type code 50
- FX-SCH-A-000563 A supporting document needs exactly one reference
- FX-SCH-A-000564 A supporting document needs exactly one type code