What it means
For each invoice line (BG-25), the rule checks that ram:AssociatedDocumentLineDocument has no direct ram:LineStatusReasonCode child, except in NLCIUS, where it checks ram:IncludedSupplyChainTradeLineItem instead. The line number (BT-126) is a separate field.
Why it matters
The EN 16931 CII mapping does not use this line status reason field. Any explanation you need to preserve should not depend on this unsupported code element.
How to fix it
If the reason matters to the buyer, express its meaning in the line note (BT-127). Remove ram:LineStatusReasonCode from the affected ram:AssociatedDocumentLineDocument or, for NLCIUS, directly from ram:IncludedSupplyChainTradeLineItem. If ram:LineStatusCode is also present there, address it under CII-SR-037. Check the file again.
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
LineStatusReasonCode should not be present 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 |
Check your file
Drop your e-invoice to see whether CII-SR-038 still fails, and which other rules do.
Related rules
- CII-SR-039 Use at most one note per invoice line
- CII-SR-040 Use at most one note text element per invoice line
- CII-SR-041 Remove subject codes from line notes
- CII-SR-042 Remove identifiers from line notes
- CII-SR-043 Remove the subject element from the line note
- CII-SR-044 Remove the content code from the line note