errorsyntaxcii-d16b

CII-SR-002:Missing ExchangedDocument context

Fix: Add ExchangedDocumentContext with GuidelineSpecifiedDocumentContextParameterID.

CII documents must include the ExchangedDocumentContext header.

Severity
Fatal
Rule set
cii-d16b
Country
All EU
Fix type
BLOCKED

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 rejected by Peppol access points and never reaches the buyer.

Target path: XPath: /rsm:CrossIndustryInvoice/rsm:ExchangedDocumentContext

This error requires manual correction — financial fields are protected by policy.

Why This Error Matters

Document context identifies the profile and rules for processing.

CII-SR-002 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.

Validator Behavior

  • ·Causes invoice rejection
  • ·Fails CII schema validation
  • ·Error returned: CII-SR-002
  • ·Specification: cii-d16b

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

XML Example

Generic example based on the rule's target XPath. Your actual XML structure may differ.

Before
<!-- Triggers validation error -->
<rsm:ExchangedDocumentContext></rsm:ExchangedDocumentContext>
After
<!-- Corrected -->
<rsm:ExchangedDocumentContext>VALID_VALUE</rsm:ExchangedDocumentContext>

Technical Reference

XPathXPath: /rsm:CrossIndustryInvoice/rsm:ExchangedDocumentContext
Speccii-d16b

Code 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

ZUGFeRD/Factur-X generators

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 Errors

BR-01Invoice must have specification identifierCII-SR-001Invalid CII namespace

Related Content

Errors
CII GuidelineSpecifiedDocumentContextParameter requiredCII namespace declaration required
Regulations
EN 16931XRechnung

Last updated: 3 March 2026

Share this guide:

Validate your invoice

Drop your XML here to check for CII-SR-002

Detect CII-SR-002 before submission

This error involves a financial field that can't be auto-modified. We'll flag it with a clear diagnosis so you can fix it at the source.

Fix it nowAutomate via API