Skip to content

Warning

CII-SR-105: Remove the requester from the line's trade agreement

In short

Warning: worth checking.

CII-SR-105 flags BuyerRequisitionerTradeParty inside an invoice line's SpecifiedLineTradeAgreement. Remove that party block from the line and agree with the buyer how to supply any requester details they need.

On this page

What it means

The check looks for BuyerRequisitionerTradeParty directly inside SpecifiedLineTradeAgreement on an invoice line (BG-25). This block identifies the requisitioner on the buyer's side.

Why it matters

EN 16931 does not provide a separate requester field at this location. The warning does not prove that the recipient discards the information or accepts the invoice.

How to fix it

Remove BuyerRequisitionerTradeParty from each affected line's SpecifiedLineTradeAgreement. If the buyer needs the details for internal routing, ask how they want them supplied. Use the invoice-level buyer reference (BT-10) only if that is the reference the buyer requests. Re-export and 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

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
Rule text from phive-rules 4.6.4.

Check your file

Drop your e-invoice to see whether CII-SR-105 still fails, and which other rules do.

Updated 6 November 2026