CII-SR-002:Missing ExchangedDocument context
CII documents must include the ExchangedDocumentContext header.
Engine Classification
Financial or legal field · Modification blocked by policy
Reason: CII documents require the ExchangedDocumentContext header element. This structural requirement must be implemented in your CII document generator. Contact your software vendor for CII format compliance.
What is CII-SR-002?
CII-SR-002 is a fatal validation rule defined in the cii-d16b specification. It validates the rsm:ExchangedDocumentContext element under rsm:CrossIndustryInvoice in the UBL invoice XML.
When this rule fires, the invoice is non-compliant and will be rejected by Peppol access points and national validation services. The sending system receives a rejection response and the invoice does not reach the buyer.
Target path: XPath: /rsm:CrossIndustryInvoice/rsm:ExchangedDocumentContext
Why This Error Matters
Document context identifies the profile and rules for processing.
CII-SR-002 is a hard failure. Invoices that trigger this rule are rejected at the access point and never reach the recipient. In Peppol networks, this means your sending system receives an MLR (Message Level Response) with a rejection status. The invoice must be corrected and re-sent, adding delay to your payment cycle.
Validator Behavior
- ·Causes invoice rejection
- ·Fails CII schema validation
- ·Error returned: CII-SR-002
- ·Specification: cii-d16b
How to Fix It
Add context
ExchangedDocumentContext is required
Specify profile
EN16931 or country-specific profile
Add BusinessProcessSpecifiedDocumentContextParameterID
For Peppol or specific process
XML Example
Generic example based on the rule's target XPath. Your actual XML structure may differ.
<!-- Triggers validation error --> <rsm:ExchangedDocumentContext></rsm:ExchangedDocumentContext>
<!-- Corrected --> <rsm:ExchangedDocumentContext>VALID_VALUE</rsm:ExchangedDocumentContext>
Technical Reference
XPath: /rsm:CrossIndustryInvoice/rsm:ExchangedDocumentContextCode Example
<rsm:ExchangedDocumentContext>
<ram:GuidelineSpecifiedDocumentContextParameterID>
urn:cen.eu:en16931:2017
</ram:GuidelineSpecifiedDocumentContextParameterID>
</rsm:ExchangedDocumentContext>Common Causes
- ·Missing context block
- ·Wrong profile identifier
- ·Incomplete context
Seeing this in production? The API handles CII-SR-002 automatically. See the fix response →
Commonly Seen In
Frequently Asked Questions
CII documents must include the ExchangedDocumentContext header.
Add ExchangedDocumentContext with GuidelineSpecifiedDocumentContextParameterID. This error involves a protected field — Invoice Navigator flags it in your pipeline so your team can correct it at the source.
Yes, CII-SR-002 is a critical error that will cause invoice rejection. It must be fixed before submission to ensure your invoice is accepted by the recipient's system.
CII-SR-002 involves a financial or legal field that cannot be auto-modified by policy. Invoice Navigator detects and flags this error immediately, but the correction must be made manually in your ERP or invoicing software.
CII-SR-002 is commonly seen in exports from ZUGFeRD/Factur-X generators. These software packages sometimes generate invoices that need adjustment to meet full compliance standards.
Related Content
Last updated: 3 March 2026
Detect CII-SR-002 Before Submission
This error involves a financial or legal field that cannot be auto-modified. The compliance engine flags it immediately with a clear diagnosis so your team can fix it at the source.