What it means
In the EN 16931 profiles of Factur-X and ZUGFeRD, the invoiced object identifier (BT-18) uses a header ram:AdditionalReferencedDocument with ram:TypeCode 130. Its optional scheme (BT-18-1) is in ram:ReferenceTypeCode. This test accepts an empty value; a non-empty value must match the profile's permitted UNTDID 1153 list.
Why it matters
The scheme identifies the kind of reference identifier you have supplied. A non-empty scheme outside the permitted list does not meet this code-list check.
How to fix it
Find the affected ram:AdditionalReferencedDocument under ram:ApplicableHeaderTradeAgreement with ram:TypeCode 130. Replace its ram:ReferenceTypeCode with the applicable permitted code, or remove that optional element if you are not supplying a scheme. Keep the invoiced object identifier and document type code unchanged. Export again and recheck.
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 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-000282 still fails, and which other rules do.
Related rules
- FX-SCH-A-000283 A supporting document can have only one description (EN 16931 and Extended)
- FX-SCH-A-000284 A supporting document can hold only one attached file (EN 16931 and Extended)
- FX-SCH-A-000285 An attached document must say what type of file it is
- FX-SCH-A-000286 An attached document must have a file name
- FX-SCH-A-000287 The file type of an attachment must be an allowed one
- FX-SCH-A-000288 The buyer can have only one contact