What it means
This checks ram:ReferenceTypeCode in a header ram:AdditionalReferencedDocument whose ram:TypeCode is 130, under ram:ApplicableHeaderTradeAgreement. A non-empty scheme code must appear in the profile's list based on UNTDID 1153. An empty value passes this check. The scheme code is separate from the reference type code 130.
Why it matters
The scheme describes what kind of identifier you supplied, such as a subscription reference. It is not the document reference type or a free-text description.
How to fix it
Identify what your BT-18 value refers to and select the corresponding code from the Extended profile's UNTDID 1153-based list. Put that code in ram:ReferenceTypeCode. Keep ram:TypeCode 130 for an invoiced object reference; do not replace it with the scheme code. Export the corrected file and recheck it.
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:ReferenceTypeCode' 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-000639 still fails, and which other rules do.
Related rules
- FX-SCH-A-000640 Check all type codes in the invoiced object reference
- 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