What it means
Within each rsm:ExchangedDocumentContext, the test allows zero or one ram:BusinessProcessSpecifiedDocumentContextParameter. It counts entries even if they contain the same identifier. This rule does not itself require a business process entry.
Why it matters
The profile provides at most one business process entry in the document context. Repeating it exceeds that structural limit.
How to fix it
Check the business process identifier (BT-23) in your export. Inside rsm:ExchangedDocumentContext, keep no more than one ram:BusinessProcessSpecifiedDocumentContextParameter. Do not remove a required identifier merely because this particular rule permits its absence. Export again 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
Element 'ram:BusinessProcessSpecifiedDocumentContextParameter' may occur at maximum 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-000024 still fails, and which other rules do.
Related rules
- FX-SCH-A-000025 The invoice must say which specification it follows
- FX-SCH-A-000026 The specification identifier must match the Minimum profile
- FX-SCH-A-000027 The invoice must contain exactly one seller
- FX-SCH-A-000028 The invoice must contain exactly one buyer
- FX-SCH-A-000029 Include one purchase order number per reference
- FX-SCH-A-000030 The buyer must have exactly one name