CII-SR-003:Invalid document type code
CII TypeCode must be valid UNTDID 1001 code (380=Invoice, 381=Credit Note).
Engine Classification
Business data required · Explicit input workflow · No assumptions made
Required input: Document Type Code
What is CII-SR-003?
CII-SR-003 is a fatal validation rule defined in the cii-d16b specification. It validates the ram:TypeCode element under rsm:CrossIndustryInvoice > rsm:ExchangedDocument 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:ExchangedDocument/ram:TypeCode
Why This Error Matters
Type code determines document processing rules.
CII-SR-003 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-003
- ·Specification: cii-d16b
How to Fix It
Check document type
380 for invoice, 381 for credit note
Other valid codes
384=corrected invoice, 389=self-billing
Set correctly
In ExchangedDocument/TypeCode
XML Example
Generic example based on the rule's target XPath. Your actual XML structure may differ.
<!-- Triggers validation error --> <ram:TypeCode></ram:TypeCode>
<!-- Corrected --> <ram:TypeCode>VALID_VALUE</ram:TypeCode>
Technical Reference
XPath: /rsm:CrossIndustryInvoice/rsm:ExchangedDocument/ram:TypeCodeCode Example
<rsm:ExchangedDocument>
<ram:ID>INV-001</ram:ID>
<ram:TypeCode>380</ram:TypeCode>
<ram:IssueDateTime>
<udt:DateTimeString format="102">20241219</udt:DateTimeString>
</ram:IssueDateTime>
</rsm:ExchangedDocument>Common Causes
- ·Wrong code
- ·Using text instead of code
- ·Invalid UNTDID 1001 value
Seeing this in production? The API handles CII-SR-003 automatically. See the fix response →
Commonly Seen In
Frequently Asked Questions
CII TypeCode must be valid UNTDID 1001 code (380=Invoice, 381=Credit Note).
Use valid document type code. Invoice Navigator detects this error and prompts for the required business data before applying a safe fix.
Yes, CII-SR-003 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-003 requires specific business data to resolve. Invoice Navigator detects the error and guides you through providing the needed information, then applies the fix with full audit documentation.
CII-SR-003 is commonly seen in exports from CII/ZUGFeRD systems. These software packages sometimes generate invoices that need adjustment to meet full compliance standards.
Related Content
Last updated: 3 March 2026
Resolve CII-SR-003 with Guided Input
The compliance engine detects this error and prompts for the required business data before applying a safe, auditable fix.