What it means
In the BASIC WL profiles of Factur-X and ZUGFeRD, this rule checks ram:TypeCode directly under rsm:ExchangedDocument. A non-empty value must match the profile's document type list. Examples are 380 for an invoice and 381 for a credit note. An empty value passes this particular code-list check; that does not establish that the document type can be omitted.
Why it matters
The document type code records what kind of document you issued, so the code needs to preserve that meaning.
How to fix it
Check the actual document type (BT-3) and use its corresponding code from the BASIC WL list. Use 380 for an invoice or 381 for a credit note only when that is the correct type. Do not replace another correctly described, allowed type merely because it is less common. The XML parent is rsm:ExchangedDocument, not ram:ExchangedDocument. If your software maps the type incorrectly, ask its supplier to correct the export. Export 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 BASIC WL | 1.0.9-2 |
| ZUGFeRD 2.5 BASIC WL | 2.5.2 |
Check your file
Drop your e-invoice to see whether FX-SCH-A-000417 still fails, and which other rules do.
Related rules
- FX-SCH-A-000418 Use an allowed Basic WL specification identifier
- FX-SCH-A-000419 Give the buyer one postal address
- FX-SCH-A-000420 Add the buyer identifier scheme
- FX-SCH-A-000421 Use an allowed buyer identifier scheme
- FX-SCH-A-000422 Give the buyer's address one country code
- FX-SCH-A-000423 Use an allowed buyer country code