What it means
The check looks in the agreement part of the invoice header for a reference to a requisition (ram:RequisitionerReferencedDocument), the internal request in the buyer's organisation that led to the order. EN 16931 has no field for it.
Why it matters
This is a warning, so the invoice is still accepted. A recipient that follows the standard does not read the requisition reference, so it is not used to route or approve the invoice. It is worth fixing if the buyer asked you to quote it, because it will not reach them in this field.
How to fix it
Remove the requisition reference from the invoice in your invoicing software, or from the export settings that send it. In the XML, delete the ram:RequisitionerReferencedDocument block. Ask the buyer which reference they need: the buyer reference (BT-10) and the purchase order number (BT-13) are the fields the format provides for what the buyer wants quoted.
The rule as published
RequisitionerReferencedDocument 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-304 still fails, and which other rules do.
Related rules
- CII-SR-305 Do not name an agent acting for the buyer
- CII-SR-306 Do not add a purchase conditions reference
- CII-SR-307 Leave the project description out of the invoice
- CII-SR-308 Leave shipment (consignment) details out of the invoice
- CII-SR-309 Delivery party must not carry a role code
- CII-SR-310 Delivery party must not carry a free-text description