errorsyntaxcii-d16b

CII-SR-03:ExchangedDocument element required

Fix: Add ExchangedDocument with document number and type.

CII must have ExchangedDocument with ID and TypeCode.

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 ExchangedDocument element containing document ID and type code. This is a mandatory CII structure element that must be generated by your invoicing software.

What is CII-SR-03?

CII-SR-03 is a fatal validation rule defined in the cii-d16b specification. It validates the rsm:ExchangedDocument 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:ExchangedDocument

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

Why This Error Matters

ExchangedDocument contains document identification.

CII-SR-03 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-03
  • ·Specification: cii-d16b

How to Fix It

1.

Add ExchangedDocument

Document header information

2.

Include required

ram:ID and ram:TypeCode

XML Example

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

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

Technical Reference

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

Common Causes

  • ·Missing document header
  • ·Missing ID or TypeCode

Seeing this in production? The API handles CII-SR-03 automatically. See the fix response →

Frequently Asked Questions

CII must have ExchangedDocument with ID and TypeCode.

Add ExchangedDocument with document number and type. 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-03 is a critical error that will cause invoice rejection. It must be fixed before submission.

Related Errors

Related Content

Last updated: 3 March 2026

Share this guide:

Validate your invoice

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

Detect CII-SR-03 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.