What it means
This checks ram:SpecifiedAdvancePayment/ram:InvoiceSpecifiedReferencedDocument/ram:TypeCode against the profile's document-type list. An empty code value passes this test. It does not check whether the chosen type accurately describes the referenced document.
Why it matters
The type code identifies what kind of document the advance payment reference names.
How to fix it
Check the type of the document you are referencing. Correct ram:TypeCode inside ram:SpecifiedAdvancePayment/ram:InvoiceSpecifiedReferencedDocument using the permitted list. Code 380 denotes an invoice and 386 denotes a prepayment invoice; use the appropriate permitted code rather than choosing one merely to clear the error. Export 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: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-000961 still fails, and which other rules do.
Related rules
- FX-SCH-A-000962 Each financial adjustment needs one amount element
- FX-SCH-A-000963 One description per logistics charge
- FX-SCH-A-000964 One tax type code per logistics charge tax block
- FX-SCH-A-000965 One VAT category per logistics charge tax block
- FX-SCH-A-000966 Permitted VAT category code for a logistics charge
- FX-SCH-A-000967 Permitted exemption reason code for a logistics charge