errorcii-d16b

CII-SR-05:ApplicableHeaderTradeAgreement required

CII must specify seller and buyer.

Severity
Fatal
Rule set
cii-d16b
Country
All EU
Fix type
BLOCKED

Engine Classification

Financial or legal field · Modification blocked by policy

Reason: CII documents require the ApplicableHeaderTradeAgreement element containing seller and buyer information. Update your CII document generator to include this mandatory element.

What is CII-SR-05?

CII-SR-05 is a fatal validation rule defined in the cii-d16b specification. It validates the ram:ApplicableHeaderTradeAgreement element under rsm:CrossIndustryInvoice > rsm:SupplyChainTradeTransaction in the UBL invoice XML.

When this rule fires, the invoice is non-compliant and will be rejected by Peppol access points and national validation services. The sending system receives a rejection response and the invoice does not reach the buyer.

Target path: XPath: /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement

This error requires manual correction — financial fields are protected by policy.

Why This Error Matters

Trade agreement contains party details.

CII-SR-05 is a hard failure. Invoices that trigger this rule are rejected at the access point and never reach the recipient. In Peppol networks, this means your sending system receives an MLR (Message Level Response) with a rejection status. The invoice must be corrected and re-sent, adding delay to your payment cycle.

Validator Behavior

  • ·Causes invoice rejection
  • ·Fails CII schema validation
  • ·Error returned: CII-SR-05
  • ·Specification: cii-d16b

How to Fix It

1.

Add agreement

ApplicableHeaderTradeAgreement element

2.

Add parties

SellerTradeParty and BuyerTradeParty

XML Example

Generic example based on the rule's target XPath. Your actual XML structure may differ.

Before
<!-- Triggers validation error -->
<ram:ApplicableHeaderTradeAgreement></ram:ApplicableHeaderTradeAgreement>
After
<!-- Corrected -->
<ram:ApplicableHeaderTradeAgreement>VALID_VALUE</ram:ApplicableHeaderTradeAgreement>

Technical Reference

XPathXPath: /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement
Speccii-d16b

Common Causes

  • ·Missing trade agreement
  • ·Missing parties

Seeing this in production? The API handles CII-SR-05 automatically. See the fix response →

Frequently Asked Questions

CII must specify seller and buyer.

Add HeaderTradeAgreement with party information. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.

Yes, CII-SR-05 is a critical error that will cause invoice rejection. It must be fixed before submission.

Related Errors

Last updated: 18 January 2026

Share this guide:

Handle CII-SR-05 Automatically in Your Pipeline

The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.