errorcii-d16b

CII-SR-003:Invalid document type code

CII TypeCode must be valid UNTDID 1001 code (380=Invoice, 381=Credit Note).

We can help you fix this

NEEDS INPUT

Answer a few questions and we will fix it for you.

Simple form - we handle the XML for you
Upload and Answer Questions

Why This Error Matters

Type code determines document processing rules.

How to Fix It

1

Check document type

380 for invoice, 381 for credit note

2

Other valid codes

384=corrected invoice, 389=self-billing

3

Set correctly

In ExchangedDocument/TypeCode

Code 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>

Technical Details

XPath: /rsm:CrossIndustryInvoice/rsm:ExchangedDocument/ram:TypeCode

Common Causes

  • Wrong code
  • Using text instead of code
  • Invalid UNTDID 1001 value

Commonly Seen In

CII/ZUGFeRD systems

Frequently Asked Questions

CII TypeCode must be valid UNTDID 1001 code (380=Invoice, 381=Credit Note).
Use valid document type code. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.
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.
Many instances of CII-SR-003 can be automatically corrected using Invoice Navigator's Fixer tool. Upload your invoice and the tool will identify and fix common issues, including invalid document type code.
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 Errors

BR-04

Missing invoice type code

CII-SR-001

Invalid CII namespace

Last updated: 18 January 2026

Share this guide: