What causes the CII-SR-001 error?

CII (Cross Industry Invoice) documents must use the correct namespace declaration.

How do I fix CII-SR-001?

Use the correct CII D16B namespace. 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-001 a critical error?

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.

Can CII-SR-001 be automatically fixed?

CII-SR-001 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-001?

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.

Error codes · cii-d16b

CII-SR-001Partly

SpecifiedTransactionID element must not be present

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

XPath: /rsm:CrossIndustryInvoice namespace

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

What we doUse the correct CII D16B namespace.

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

From youThe correct figures

ThenChecked again

ProofSHA-256 and /verify link after the check

Often appears together with

UBL-CR-002UBLVersionID must be 2.1 or absent