warningEN 16931

BR-CO-25:In case the Amount due for payment (BT-115) is positive, either the Payment...

Each invoice line must have unique ID within document.

Severity
Warning
Rule set
EN 16931
Country
All EU
Fix type
INPUT REQUIRED

Engine Classification

Business data required · Explicit input workflow · No assumptions made

Required input: Line IDs (comma-separated)

What is BR-CO-25?

BR-CO-25 is a warning validation rule defined in the EN 16931 specification. It validates the ID element under Invoice > InvoiceLine in the UBL invoice XML.

This is a soft validation failure. The invoice may pass initial transmission, but non-compliant values in this field can cause problems during tax audits, buyer-side processing, or downstream VAT reconciliation.

Target path: XPath: /Invoice/cac:InvoiceLine/cbc:ID

Why This Error Matters

Invoice rejected. Buyers need to know when payment is expected.

BR-CO-25 is a soft failure. The invoice may pass initial validation, but the non-compliant field can cause issues at the receiving end — tax authorities may flag it during audits, buyer ERP systems may fail to process it, or VAT reconciliation may produce mismatches. Fixing warnings before they accumulate prevents larger compliance gaps.

Validator Behavior

  • ·Generates validation warning
  • ·Error returned: BR-CO-25
  • ·Specification: EN 16931

How to Fix It

1.

Check all line IDs

Review InvoiceLine/ID values

2.

Make unique

Use sequential numbers or unique identifiers

Before / After

Failing XML
<cac:LegalMonetaryTotal>
  <cbc:PayableAmount><!-- invalid or missing value --></cbc:PayableAmount>
</cac:LegalMonetaryTotal>
Corrected XML
<cac:LegalMonetaryTotal>
  <cbc:PayableAmount>correct-value</cbc:PayableAmount>
</cac:LegalMonetaryTotal>

Technical Reference

XPathXPath: /Invoice/cac:InvoiceLine/cbc:ID
SpecEN 16931
StrategyRequires user input: Payment due date or payment terms text. Cannot auto-generate because payment terms depend on customer agreements and business policies.

Common Causes

  • ·Positive amount due but no payment date or terms
  • ·Invoice has payable amount without due date (BT-9)
  • ·PaymentTerms/Note also missing when amount > 0
  • ·Payment instructions incomplete for payable invoice
  • ·Export missing payment timing information

Seeing this in production? The API handles BR-CO-25 automatically. See the fix response →

Frequently Asked Questions

Each invoice line must have unique ID within document.

Ensure each line ID is unique. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.

Yes, BR-CO-25 is a critical error that will cause invoice rejection. It must be fixed before submission to ensure your invoice is accepted by the recipient's system.

Many instances of BR-CO-25 can be automatically corrected using Invoice Navigator's Fixer tool. Upload your invoice and the tool will identify and fix common issues, including duplicate invoice line identifiers.

See Also

Related Errors

Last updated: 27 February 2026

Share this guide:

Handle BR-CO-25 Automatically in Your Pipeline

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