What it means
The check requires UltimateCustomerOrderReferencedDocument to be absent directly under ApplicableHeaderTradeAgreement. It does not prohibit the buyer's purchase order number (BT-13) in its supported field.
Why it matters
The end customer's order and the buyer's purchase order are different references. EN 16931 does not map this separate header element to the buyer's purchase order number.
How to fix it
Remove UltimateCustomerOrderReferencedDocument from ApplicableHeaderTradeAgreement. If its value actually identifies the buyer's purchase order, enter it as the purchase order number (BT-13). If it identifies the buyer's customer's order, do not relabel it; ask the buyer how to include any information they still need. Recheck your 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
UltimateCustomerOrderReferencedDocument 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-448 still fails, and which other rules do.
Related rules
- CII-SR-449 Do not mix delivery location identifier types
- CII-SR-450 Use ID or GlobalID for the buyer, not both
- CII-SR-451 Use ID or GlobalID for the payee, not both
- CII-SR-452 Use at most one payment terms block
- CII-SR-453 Give the payment terms text at most once
- CII-SR-454 Use exactly one VAT entry per line settlement