What it means
This rule checks a non-empty ram:ID inside rsm:ExchangedDocumentContext/ram:GuidelineSpecifiedDocumentContextParameter against the EN 16931 profile's permitted specification identifiers. An empty value passes this particular test; BR-01 addresses the identifier's presence separately. The rule does not establish whether the rest of the invoice follows the declared specification.
Why it matters
The specification identifier declares which requirements the invoice claims to follow. That declaration needs to match the profile used to create the file.
How to fix it
Confirm the intended invoice profile. For the EN 16931 profile of Factur-X or ZUGFeRD, put urn:cen.eu:en16931:2017 without added spaces in ram:GuidelineSpecifiedDocumentContextParameter/ram:ID. Correct the export profile and invoice content together where necessary. If you intended another profile, use an export for that profile rather than simply relabelling the file. Check the new 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:ID' 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-000556 still fails, and which other rules do.
Related rules
- 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
- FX-SCH-A-000560 A tender or lot reference needs exactly one identifier
- FX-SCH-A-000561 A tender or lot reference needs exactly one type code
- FX-SCH-A-000562 A tender or lot reference must use the type code 50