What causes the CII-SR-003 error?

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

How do I fix CII-SR-003?

Use valid document type code. Invoice Navigator detects this error and prompts for the required business data before applying a safe fix.

Is CII-SR-003 a critical error?

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.

Can CII-SR-003 be automatically fixed?

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.

Which accounting software causes CII-SR-003?

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.

Error codes · cii-d16b

CII-SR-003Fixable here

BusinessProcessSpecifiedDocumentContextParameter must occur maximum once

This is the rejection, word for word: „[CII-SR-003] CII-SR-003 is an EN 16931 assertion on the CII binding. The element ram:BusinessProcessSpecifiedDocumentContextParameter must appear at most once.“

What to have readyDocument Type Code

What we doUse valid document type code.

Choose the rejected invoiceor drop it here

XRechnung XML or ZUGFeRD PDF. Checking is free · corrected file €1.90 · the first every 30 days is free · no sign-up.

What the finding looks likeExample

FindingValue missing · CII-SR-003

Location/rsm:CrossIndustryInvoice/rsm:ExchangedDocument/ram:TypeCode

From youDocument Type Code

ThenPassed

ProofSHA-256 and /verify link after the check

Often appears together with

BR-04Missing invoice type code CII-SR-001SpecifiedTransactionID element must not be present