What it means
Within rsm:ExchangedDocument, the test counts ram:ID elements. There must be exactly one. This rule checks the number of elements, not whether the number is filled in or correct.
Why it matters
The invoice number identifies the document when you or the recipient refer to it. The profile provides one header element for this number.
How to fix it
Check the invoice number field and correct the export so it writes one ram:ID inside rsm:ExchangedDocument. Add the missing entry or remove duplicate elements, keeping the correct invoice number. Export again and recheck the 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
Element 'ram:ID' must occur exactly 1 times. Where this rule applies
| Rule set | Version |
|---|---|
| Factur-X 1.09 MINIMUM | 1.0.9-2 |
| Factur-X 1.09 BASIC WL | 1.0.9-2 |
| Factur-X 1.09 BASIC | 1.0.9-2 |
| Factur-X 1.09 EN 16931 | 1.0.9-2 |
| Factur-X 1.09 EXTENDED | 1.0.9-2 |
| ZUGFeRD 2.5 MINIMUM | 2.5.2 |
| ZUGFeRD 2.5 BASIC WL | 2.5.2 |
| ZUGFeRD 2.5 BASIC | 2.5.2 |
| ZUGFeRD 2.5 EN 16931 | 2.5.2 |
| ZUGFeRD 2.5 EXTENDED | 2.5.2 |
Check your file
Drop your e-invoice to see whether FX-SCH-A-000019 still fails, and which other rules do.
Related rules
- FX-SCH-A-000020 Give exactly one document type code
- FX-SCH-A-000021 The invoice date must say how it is written
- FX-SCH-A-000022 The invoice date format must be one the Minimum profile allows
- FX-SCH-A-000023 The document type code must be allowed in the Minimum profile
- FX-SCH-A-000024 An invoice can name at most one business process
- FX-SCH-A-000025 The invoice must say which specification it follows