What it means
This rule counts ram:TypeCode elements in each ram:AdditionalReferencedDocument under ram:ApplicableHeaderTradeAgreement that contains a type code of 50. Because that code is already present, a failure means there are multiple type-code elements, even if they all contain 50. It applies to the EN 16931 and Extended profiles of Factur-X and ZUGFeRD.
Why it matters
One type-code element identifies the reference as a tender or lot reference. Repeating that element does not follow the required structure, even when the values agree.
How to fix it
In the affected tender or lot reference, retain one ram:TypeCode containing 50 and remove the extra type-code elements. If another code belongs to a separate reference, give that reference its own ram:AdditionalReferencedDocument. If your invoicing software creates the duplicates, ask its supplier to correct the export. Export and recheck the file.
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-000561 still fails, and which other rules do.
Related rules
- 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
- FX-SCH-A-000565 A supporting document must use the type code 916
- FX-SCH-A-000566 The buyer contact email needs one address element
- FX-SCH-A-000567 The scheme of the buyer identifier must be an ISO 6523 code