BR-66:An Invoice shall contain maximum one Payment Card account (BG-18).
Fix: Invoice Navigator automatically fixes this issue by correcting the `cac:CardAccount` element in your Invoice. Upload your invoice to fix this automatically.
The invoice contains multiple Payment Card accounts (BG-18). Only one card payment method is allowed per invoice.
Engine Classification
Recalculate line extension amount from quantity and price
Confidence: 85% · Applied automatically in pipeline
What is BR-66?
BR-66 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 card should be used?
BR-66 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-66
- ·Specification: EN 16931
How to Fix It
Locate Payment Card sections
Count Payment Card accounts
Compare card details
Keep first or flag for review
Remove duplicate sections
Validate the result
Before / After
<cac:PaymentMeans> <cac:CardAccount><!-- invalid or missing value --></cac:CardAccount> </cac:PaymentMeans>
<cac:PaymentMeans> <cac:CardAccount>correct-value</cac:CardAccount> </cac:PaymentMeans>
Technical Reference
//cac:InvoiceLine/cbc:LineExtensionAmountCommon Causes
- ·Multiple PaymentCard sections added to invoice
- ·ERP allows multiple card payment options but EN16931 only permits one
- ·Template duplicated payment card section
- ·Data migration merged multiple payment records
- ·Manual XML editing introduced duplicate card details
Seeing this in production? The API handles BR-66 automatically. See the fix response →
Frequently Asked Questions
The invoice contains multiple Payment Card accounts (BG-18). Only one card payment method is allowed per invoice.
Invoice Navigator automatically fixes this issue by correcting the `cac:CardAccount` element in your Invoice. You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.
Yes, BR-66 is a critical error that will cause invoice rejection. It must be fixed before submission.
Many instances of BR-66 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
Validate your invoice
Drop your XML here to check for BR-66
Auto-fix BR-66 in seconds
Upload your invoice and we fix this error automatically. Financial fields are never touched.