What it means
In the Basic profiles of Factur-X and ZUGFeRD, this rule checks rsm:ExchangedDocument/ram:TypeCode against the profile's document type code list. An empty checked value passes. Codes identify document types, such as 380 for an invoice, 381 for a credit note and 389 for a self-billed invoice; any code used must belong to the profile's list.
Why it matters
The type code distinguishes documents with different meanings, including invoices, credit notes and self-billed invoices. This check does not establish whether the document's content matches its declared type.
How to fix it
Confirm which document type you intend to issue. Select that type in your invoicing software and ensure it is supported by Basic. In XML, correct ram:TypeCode inside rsm:ExchangedDocument to the corresponding permitted code. Do not change the type 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 BASIC | 1.0.9-2 |
| ZUGFeRD 2.5 BASIC | 2.5.2 |
Check your file
Drop your e-invoice to see whether FX-SCH-A-000492 still fails, and which other rules do.
Related rules
- FX-SCH-A-000493 Use a specification identifier allowed by Basic
- FX-SCH-A-000494 Use an allowed buyer identifier scheme (Basic)
- FX-SCH-A-000495 Use an allowed buyer country code (Basic)
- FX-SCH-A-000496 Use an allowed buyer registration scheme (Basic)
- FX-SCH-A-000497 Use an allowed buyer tax registration scheme (Basic)
- FX-SCH-A-000498 Check the buyer's electronic address scheme