What it means
For an earlier invoice reference (BG-3), this rule compares a non-empty ram:TypeCode value with the Extended profile's allowed list. An empty value is not flagged by this rule.
Why it matters
The type code describes the document you are referring to, which may have a different type from the invoice or credit note you are checking.
How to fix it
Under ram:ApplicableHeaderTradeSettlement/ram:InvoiceReferencedDocument, correct the ram:TypeCode value to an allowed code matching the earlier document, such as 380 for an invoice. If you do not need to supply the optional type, remove that ram:TypeCode element. 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-000863 still fails, and which other rules do.
Related rules
- FX-SCH-A-000864 Keep at most one invoicee identifier
- FX-SCH-A-000865 The invoicee must have exactly one name
- FX-SCH-A-000866 Keep at most one invoicee role code
- FX-SCH-A-000867 Keep at most one invoicee electronic address entry
- FX-SCH-A-000868 Keep at most one invoicee tax registration
- FX-SCH-A-000869 An invoicee email contact needs exactly one address