What it means
In the EN 16931 profiles of Factur-X and ZUGFeRD, this rule checks each ram:TypeCode in a ram:AdditionalReferencedDocument under ram:ApplicableHeaderTradeAgreement that already contains a type code of 130. A non-empty value must be on the referenced code list. An empty value passes this test; the number of type-code elements is checked separately.
Why it matters
The type code identifies the purpose of the reference. An unsupported value does not follow the code list used for this reference.
How to fix it
Check the invoiced object reference (BT-18) in your source invoice. In the XML, keep one ram:TypeCode containing 130 in the affected ram:AdditionalReferencedDocument. Put any genuinely separate reference in its own ram:AdditionalReferencedDocument. If your software writes extra type-code elements, report the problem to its supplier. 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
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-000559 still fails, and which other rules do.
Related rules
- 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
- FX-SCH-A-000565 A supporting document must use the type code 916