What causes the CII-SR-002 error?

CII documents must include the ExchangedDocumentContext header.

How do I fix CII-SR-002?

Add ExchangedDocumentContext with GuidelineSpecifiedDocumentContextParameterID. This error involves a protected field — Invoice Navigator flags it in your pipeline so your team can correct it at the source.

Is CII-SR-002 a critical error?

Yes, CII-SR-002 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-002 be automatically fixed?

CII-SR-002 involves a financial or legal field that cannot be auto-modified by policy. Invoice Navigator detects and flags this error immediately, but the correction must be made manually in your ERP or invoicing software.

Which accounting software causes CII-SR-002?

CII-SR-002 is commonly seen in exports from ZUGFeRD/Factur-X generators. These software packages sometimes generate invoices that need adjustment to meet full compliance standards.

Error codes · cii-d16b

CII-SR-002Partly

TestIndicator element must not be present

This is the rejection, word for word: „[CII-SR-002] CII-SR-002 is an EN 16931 assertion on the CII binding. The element ram:TestIndicator must not be present in the document.“

What to have readyThe correct figures from your bookkeeping; we show you which field is affected.

What we doAdd ExchangedDocumentContext with GuidelineSpecifiedDocumentContextParameterID.

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

FindingNeeds your check · CII-SR-002

Location/rsm:CrossIndustryInvoice/rsm:ExchangedDocumentContext

From youThe correct figures

ThenChecked again

ProofSHA-256 and /verify link after the check

Often appears together with

BR-01An Invoice shall have a Specification identifier (BT-24)CII-SR-001SpecifiedTransactionID element must not be present