errorbusinessEN 16931

BR-67:An Invoice shall contain maximum one Payment Mandate (BG-19).

Fix: Invoice Navigator automatically fixes this issue by correcting the `cac:PaymentMandate` element in your Invoice. Upload your invoice to fix this automatically.

The invoice contains multiple Payment Mandates (BG-19). Only one direct debit mandate is allowed per invoice.

Severity
Fatal
Rule set
EN 16931
Country
All EU
Fix type
AUTO-FIX
Confidence
85%
Category
calculation

Engine Classification

Ensure line extension amount is not negative

Confidence: 85% · Applied automatically in pipeline

What is BR-67?

BR-67 is a fatal validation rule defined in the EN 16931 specification. It validates the LineExtensionAmount element in the UBL invoice XML.

When this rule fires, the invoice is rejected by Peppol access points and never reaches the buyer.

Target path: //cac:InvoiceLine/cbc:LineExtensionAmount

Why This Error Matters

Invoice rejected. Ambiguous payment instructions - which mandate authorizes the debit?

BR-67 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.

Invoice Navigator can automatically correct this error in your pipeline. The fix is applied with full audit evidence, so your compliance trail remains intact.

Validator Behavior

  • ·Causes invoice rejection
  • ·Error returned: BR-67
  • ·Specification: EN 16931

How to Fix It

1.

Locate Payment Mandate sections

2.

Count Payment Mandates

3.

Compare mandate details

4.

Keep first mandate

5.

Remove duplicate sections

6.

Validate the result

Before / After

Failing XML
<cac:PaymentMeans>
  <cac:PaymentMandate><!-- invalid or missing value --></cac:PaymentMandate>
</cac:PaymentMeans>
Corrected XML
<cac:PaymentMeans>
  <cac:PaymentMandate>correct-value</cac:PaymentMandate>
</cac:PaymentMeans>

Technical Reference

XPath//cac:InvoiceLine/cbc:LineExtensionAmount
SpecEN 16931
Operationnormalize
StrategyEnsure line extension amount is not negative

Common Causes

  • ·Multiple PaymentMandate sections added to invoice
  • ·Direct debit configured with multiple mandate references
  • ·Template duplicated payment mandate section
  • ·Data migration merged multiple mandate records
  • ·Manual XML editing introduced duplicate mandates

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

Frequently Asked Questions

The invoice contains multiple Payment Mandates (BG-19). Only one direct debit mandate is allowed per invoice.

Invoice Navigator automatically fixes this issue by correcting the `cac:PaymentMandate` element in your Invoice. You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

Yes, BR-67 is a critical error that will cause invoice rejection. It must be fixed before submission.

Many instances of BR-67 can be automatically corrected using Invoice Navigator's compliance engine. The fix is applied in your pipeline with full audit evidence.

Related Errors

Related Content

Last updated: 27 February 2026

Share this guide:

Validate your invoice

Drop your XML here to check for BR-67

Auto-fix BR-67 in seconds

Upload your invoice and we fix this error automatically. Financial fields are never touched.