What it means
This checks ram:TypeCode inside rsm:ExchangedDocument against the Extended profile's document type code list. A non-empty value must match a listed code. An empty value passes this particular check; the test does not establish which other rule would report missing information.
Why it matters
The code identifies the document's business type independently of its printed title. It needs to describe the document you issued.
How to fix it
Check whether your document is an invoice, credit note, self-billed invoice or another supported type. Correct its document type in the export and the corresponding header ram:TypeCode. Do not change the business type simply to clear the message. 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: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-000635 still fails, and which other rules do.
Related rules
- FX-SCH-A-000636 Check the Extended profile specification identifier
- FX-SCH-A-000637 Add the invoiced object reference date format
- FX-SCH-A-000638 Check the invoiced object reference date format
- FX-SCH-A-000639 Check the invoiced object identifier scheme
- 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