What it means
The invoice-level settlement section (ApplicableHeaderTradeSettlement) holds a CreditReasonCode element, a code meant to say why a credit is given. EN 16931 has no field for such a code, so the rule expects the element to be absent.
Why it matters
This is a warning, so the file is still accepted. Software that reads EN 16931 only picks up the fields the standard defines, so the buyer never sees the reason you tried to give. If your invoice was rejected, the cause is a different rule, because this one alone does not reject it.
How to fix it
Delete the CreditReasonCode element from the settlement section. If the buyer needs to know why you are crediting them, write the reason in words in an invoice note (BT-22). On a credit note, also point to the original invoice in the preceding invoice reference (BG-3). If your accounting software writes the file, look for a credit reason setting in its e-invoice export, or ask the software's supplier to stop writing the element.
The rule as published
CreditReasonCode 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-348 still fails, and which other rules do.