What it means
The settlement section (ApplicableHeaderTradeSettlement) should not contain a PaymentCurrencyCode. EN 16931 has one invoice currency (BT-5) for all amounts, and optionally a VAT accounting currency (BT-6). It has no separate currency for payment.
Why it matters
This is a warning, so the file is still accepted. Receiving software reads every amount in the invoice currency and normally ignores a payment currency. A buyer who expects to pay in another currency will not see it.
How to fix it
Remove the payment currency from the file and check that the invoice currency is correct. If VAT must be shown in a second currency, use the VAT accounting currency (BT-6). If you have agreed payment in another currency, say so in the payment terms (BT-20). Fix it when the amounts to pay differ from the invoice currency.
The rule as published
PaymentCurrencyCode 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-344 still fails, and which other rules do.
Related rules
- CII-SR-345 Leave out the invoice issuer reference
- CII-SR-346 Leave out the invoice date in the settlement section
- CII-SR-347 Leave out the next invoice date and time
- CII-SR-348 Leave out the credit reason code
- CII-SR-349 Leave out the credit reason text
- CII-SR-350 Do not name a separate invoicing party