What it means
For the Minimum profile, the test checks a non-empty ram:TypeCode inside rsm:ExchangedDocument against the permitted document type codes. An empty value does not fail this test. FX-SCH-A-000020 separately checks that the element occurs exactly once.
Why it matters
A shared document type code lets the recipient distinguish the kind of document without relying on a written description.
How to fix it
Correct the document type in your invoicing software so its export writes the appropriate permitted code in ram:TypeCode inside rsm:ExchangedDocument. Do not change a credit note into an invoice merely to change its code. 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 MINIMUM | 1.0.9-2 |
| ZUGFeRD 2.5 MINIMUM | 2.5.2 |
Check your file
Drop your e-invoice to see whether FX-SCH-A-000023 still fails, and which other rules do.
Related rules
- FX-SCH-A-000024 An invoice can name at most one business process
- FX-SCH-A-000025 The invoice must say which specification it follows
- FX-SCH-A-000026 The specification identifier must match the Minimum profile
- FX-SCH-A-000027 The invoice must contain exactly one seller
- FX-SCH-A-000028 The invoice must contain exactly one buyer
- FX-SCH-A-000029 Include one purchase order number per reference