Skip to content

Fatal

CII-SR-014: The invoice must have exactly one document type code

In short

Fatal: fails the selected checks.

CII-SR-014 fails when your CII invoice has no ram:TypeCode in rsm:ExchangedDocument, or has more than one. Add the missing element or remove extra elements so that exactly one remains, then recheck your file.

On this page

What it means

Counts the direct ram:TypeCode children of rsm:ExchangedDocument and requires exactly one. This element carries the document type code (BT-3). The rule does not check whether the value is empty or allowed.

Why it matters

BT-3 distinguishes document types, such as 380 for an invoice, 381 for a credit note and 389 for a self-billed invoice. The element count and the permitted code values are separate checks.

How to fix it

Add a missing ram:TypeCode inside rsm:ExchangedDocument or remove extra TypeCode elements there. Set the remaining element to the code for your document type, using a code permitted by the rules that apply to your invoice. Recheck the file.

Once the file is corrected, check it again for free: Validate an invoice against EN 16931

Or fix the invoice in a form and download the corrected file, for 1 credit: Fix a rejected e-invoice

The rule as published

TypeCode must exist exactly once

Where this rule applies

Rule set Version
EN 16931 (CII) 1.3.17
XRechnung 3.0 (CII) 3.0.2
NLCIUS (CII) 1.0.3.13
France CTC (CII) 1.4.0-04
Rule text from phive-rules 4.6.4.

Check your file

Drop your e-invoice to see whether CII-SR-014 still fails, and which other rules do.

Updated 6 November 2026