What it means
This rule checks ram:SubjectCode within rsm:ExchangedDocument/ram:IncludedNote against the EN 16931 profile's permitted subject codes for Factur-X and ZUGFeRD. An empty value passes this particular test. The rule does not check the note text (BT-22).
Why it matters
The subject code classifies the note for software. Its code-list check is separate from the meaning or suitability of the note itself.
How to fix it
Check what your note is about. Replace ram:SubjectCode with a permitted code that describes that subject, or remove ram:SubjectCode while retaining the text in ram:Content. Do not put a subject label or an abbreviation of your own in the code field. Export the corrected invoice and check it again.
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:SubjectCode' is not allowed. Where this rule applies
| Rule set | Version |
|---|---|
| Factur-X 1.09 EN 16931 | 1.0.9-2 |
| ZUGFeRD 2.5 EN 16931 | 2.5.2 |
Check your file
Drop your e-invoice to see whether FX-SCH-A-000553 still fails, and which other rules do.
Related rules
- FX-SCH-A-000554 Use a permitted invoice date format code
- FX-SCH-A-000555 Use a permitted invoice type code
- FX-SCH-A-000556 Use a permitted specification identifier
- FX-SCH-A-000557 Give the invoiced-object reference one identifier
- FX-SCH-A-000558 Keep one type code in the invoiced-object reference
- FX-SCH-A-000559 A reference to the invoiced object must use the type code 130