What it means
The invoice header contains a BuyerRequisitionerTradeParty element, which names the person or department at the buyer who requested the purchase. EN 16931 has no such party. It uses references instead: the buyer reference (BT-10) and the purchase order number (BT-13).
Why it matters
This is only a warning, so the file is still accepted. The requisitioner has no field in the EN 16931 data model, so the buyer's software will not read it. The buyer matches the invoice by its references, not by this party.
How to fix it
Look for a requested by, requisitioner or internal contact field on the invoice in your invoicing software and stop it being exported. Ask the buyer which reference they want on the invoice, usually a buyer reference or a purchase order number, and enter it in those fields. This is worth fixing if the buyer uses that name to route the invoice internally.
The rule as published
BuyerRequisitionerTradeParty 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-279 still fails, and which other rules do.
Related rules
- CII-SR-280 Do not name the buyer's accountant in the invoice header
- CII-SR-281 Do not name the seller's accountant in the invoice header
- CII-SR-282 Do not name a tax representative for the buyer
- CII-SR-283 Seller's tax representative should not carry a global ID
- CII-SR-284 Seller's tax representative should not carry a role code
- CII-SR-285 Seller's tax representative should not carry a description