errorcii-d16b
CII-SR-002:Missing ExchangedDocument context
CII documents must include the ExchangedDocumentContext header.
Fix this in your source system
MANUALCII 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.
See the step-by-step instructions below to fix this error manually.
Why This Error Matters
Document context identifies the profile and rules for processing.
How to Fix It
1
Add context
ExchangedDocumentContext is required
2
Specify profile
EN16931 or country-specific profile
3
Add BusinessProcessSpecifiedDocumentContextParameterID
For Peppol or specific process
Code Example
<rsm:ExchangedDocumentContext>
<ram:GuidelineSpecifiedDocumentContextParameterID>
urn:cen.eu:en16931:2017
</ram:GuidelineSpecifiedDocumentContextParameterID>
</rsm:ExchangedDocumentContext>Technical Details
XPath: /rsm:CrossIndustryInvoice/rsm:ExchangedDocumentContextCommon Causes
- Missing context block
- Wrong profile identifier
- Incomplete context
Commonly Seen In
ZUGFeRD/Factur-X generators
Frequently Asked Questions
CII documents must include the ExchangedDocumentContext header.
Add ExchangedDocumentContext with GuidelineSpecifiedDocumentContextParameterID. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.
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.
Many instances of CII-SR-002 can be automatically corrected using Invoice Navigator's Fixer tool. Upload your invoice and the tool will identify and fix common issues, including missing exchangeddocument context.
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 Errors
Last updated: 18 January 2026
Share this guide: