errorcii-d16b
CII-SR-001:Invalid CII namespace
CII (Cross Industry Invoice) documents must use the correct namespace declaration.
Fix this in your source system
MANUALCII (Cross Industry Invoice) documents require correct XML namespace declarations. This is a fundamental format issue that must be fixed in your invoicing software or XML generation tool. The namespace must be urn:un:unece:uncefact:data:standard:CrossIndustryInvoice:100.
See the step-by-step instructions below to fix this error manually.
Why This Error Matters
Incorrect namespaces prevent CII validation and processing.
How to Fix It
1
Check root element
Must be rsm:CrossIndustryInvoice
2
Verify namespace
urn:un:unece:uncefact:data:standard:CrossIndustryInvoice:100
3
Add component namespaces
Include ram, udt, qdt namespaces
Code Example
<rsm:CrossIndustryInvoice
xmlns:rsm="urn:un:unece:uncefact:data:standard:CrossIndustryInvoice:100"
xmlns:ram="urn:un:unece:uncefact:data:standard:ReusableAggregateBusinessInformationEntity:100"
xmlns:udt="urn:un:unece:uncefact:data:standard:UnqualifiedDataType:100">Technical Details
XPath: /rsm:CrossIndustryInvoice namespaceCommon Causes
- Wrong namespace version
- Missing component namespaces
- Typos in namespace URIs
Commonly Seen In
ZUGFeRD generatorsCII exporters
Frequently Asked Questions
CII (Cross Industry Invoice) documents must use the correct namespace declaration.
Use the correct CII D16B namespace. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.
Yes, CII-SR-001 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-001 can be automatically corrected using Invoice Navigator's Fixer tool. Upload your invoice and the tool will identify and fix common issues, including invalid cii namespace.
CII-SR-001 is commonly seen in exports from ZUGFeRD generators, CII exporters. These software packages sometimes generate invoices that need adjustment to meet full compliance standards.
Related Errors
Last updated: 18 January 2026
Share this guide: