What it means
This rule counts ram:IssuerAssignedID elements in each ram:AdditionalReferencedDocument under ram:ApplicableHeaderTradeAgreement whose ram:TypeCode is 50. There must be one identifier element. The test does not check its text, so an empty identifier element still counts. It applies to the EN 16931 and Extended profiles of Factur-X and ZUGFeRD.
Why it matters
The identifier names the tender or lot associated with the invoice. Its XML representation has one place for that identifier; missing or repeated identifier elements do not follow that structure.
How to fix it
Check your invoice's tender or lot reference (BT-17). In the affected ram:AdditionalReferencedDocument with ram:TypeCode 50, add the correct reference in one ram:IssuerAssignedID and remove duplicate identifier elements. If no tender or lot reference applies, remove the whole ram:AdditionalReferencedDocument instead of leaving an empty entry. Export and recheck your invoice.
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:IssuerAssignedID' 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-000560 still fails, and which other rules do.
Related rules
- 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
- 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