What it means
The context selects ram:AdditionalReferencedDocument under ram:ApplicableHeaderTradeAgreement when at least one ram:TypeCode equals 130. It then checks every ram:TypeCode child of that selected reference, not just the child containing 130. Empty values pass; non-empty values must be listed. This rule does not check how many TypeCode elements there are.
Why it matters
The type code distinguishes an invoiced object reference from other reference types. The selection condition alone does not prove that every code in the selected reference is appropriate.
How to fix it
Inspect all ram:TypeCode values in the affected header reference. Correct accidental extra or unrelated codes without removing a valid BT-18 reference. If 130 is the only value, ask support to verify the Extended rule set and its code list before changing that code. Recheck after the verified correction.
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-000640 still fails, and which other rules do.
Related rules
- FX-SCH-A-000641 Add the tender or lot reference date format
- FX-SCH-A-000642 Check the tender or lot reference date format
- FX-SCH-A-000643 Check the tender or lot reference type code
- FX-SCH-A-000644 Check the supporting attachment's file type
- FX-SCH-A-000645 Add a format attribute to the supporting document date
- FX-SCH-A-000646 Check the supporting document date format