What it means
A non-empty ram:TypeCode inside a line's ram:AdditionalReferencedDocument must belong to the Extended profile's permitted document type codes from UNTDID 1001. An empty value passes this particular check. This rule does not check whether the element exists.
Why it matters
The document type code identifies what the reference points to. A code outside the profile's permitted list does not meet its coding requirements.
How to fix it
Correct the document type of the affected line's reference. In the XML, update ram:TypeCode inside ram:AdditionalReferencedDocument under ram:SpecifiedLineTradeAgreement. Use a permitted code that matches the reference; 130 identifies an invoiced object, so use it only when that describes your reference. Export again 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 EXTENDED | 1.0.9-2 |
| ZUGFeRD 2.5 EXTENDED | 2.5.2 |
Check your file
Drop your e-invoice to see whether FX-SCH-A-001025 still fails, and which other rules do.
Related rules
- FX-SCH-A-001026 Line delivery terms need exactly one delivery terms code
- FX-SCH-A-001027 The delivery terms code on a line is not allowed
- FX-SCH-A-001028 The country code in line delivery terms is not allowed
- FX-SCH-A-001029 The date of the line purchase order reference needs a format code
- FX-SCH-A-001030 The date format code on the line purchase order is not allowed
- FX-SCH-A-001031 The date of the line contract reference needs a format code