What it means
Checks that no ram:ReceivableSpecifiedTradeAccountingAccount under ram:ApplicableHeaderTradeSettlement contains a ram:TypeCode child. It does not target the invoice type code (BT-3), such as 380 for an invoice or 381 for a credit note.
Why it matters
The accounting account type code is outside this EN 16931 CII structure. The warning does not establish how your buyer books the invoice or whether the file will be accepted.
How to fix it
Remove ram:TypeCode only from ram:ReceivableSpecifiedTradeAccountingAccount in the header settlement. Keep ram:ID if it holds your buyer accounting reference (BT-19). Do not remove the invoice type code (BT-3); this correction does not require changes to TypeCode elements elsewhere. 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 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-429 still fails, and which other rules do.
Related rules
- CII-SR-430 Remove the accounting amount type code
- CII-SR-431 Remove the accounting account name
- CII-SR-432 Remove the accounting cost reference pattern
- CII-SR-433 Remove the purchase accounting account
- CII-SR-434 Remove the sales accounting account
- CII-SR-435 Remove the separate payment card element