BR-50:A Payment account identifier (BT-84) shall be present if Credit transfer...
Fix: Review and correct the `cbc:ID` element in your Invoice XML to satisfy this validation rule.
A Payment account identifier (BT-84) shall be present if Credit transfer (BG-17) information is provided.. This applies to the `cbc:ID` element in the invoice XML.
Engine Classification
Financial or legal field · Modification blocked by policy
Reason: Quantity precision affects pricing accuracy and inventory counts. Rounding changes could cause discrepancies with order systems.
What is BR-50?
BR-50 is a fatal validation rule defined in the EN 16931 specification. It validates the InvoicedQuantity 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: XPath: //cbc:InvoicedQuantity
Why This Error Matters
Invoice rejected. Buyer cannot make payment without knowing the destination account.
BR-50 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.
Validator Behavior
- ·Causes invoice rejection
- ·Error returned: BR-50
- ·Specification: EN 16931
How to Fix It
Check precision
Up to 6 decimal places allowed
Unit matters
KGM may need 3 decimals, C62 typically whole numbers
Avoid excess
Dont use more precision than meaningful
Before / After
<cac:PayeeFinancialAccount> <cbc:ID><!-- invalid or missing value --></cbc:ID> </cac:PayeeFinancialAccount>
<cac:PayeeFinancialAccount> <cbc:ID>correct-value</cbc:ID> </cac:PayeeFinancialAccount>
Technical Reference
XPath: //cbc:InvoicedQuantityCode Example
<cbc:InvoicedQuantity unitCode="KGM">12.500</cbc:InvoicedQuantity>
<cbc:InvoicedQuantity unitCode="C62">10</cbc:InvoicedQuantity>Common Causes
- ·Credit transfer details without account identifier
- ·PayeeFinancialAccount/ID not mapped
- ·Bank details section missing IBAN field
- ·Payment account number field empty
- ·Account stored in wrong field in source system
Seeing this in production? The API handles BR-50 automatically. See the fix response →
Commonly Seen In
Frequently Asked Questions
Quantity values should use appropriate decimal precision.
Review and correct the `cbc:ID` element in your Invoice XML to satisfy this validation rule. This error involves a protected field — Invoice Navigator flags it in your pipeline so your team can correct it at the source.
BR-50 is a warning that may not always cause rejection, but it indicates a potential compliance issue that should be addressed to ensure full compatibility.
BR-50 involves a financial or legal field that cannot be auto-modified by policy. Invoice Navigator detects and flags this error immediately, but the correction must be made manually in your ERP or invoicing software.
BR-50 is commonly seen in exports from All invoicing software. These software packages sometimes generate invoices that need adjustment to meet full compliance standards.
Related Errors
Related Content
Last updated: 3 March 2026
Validate your invoice
Drop your XML here to check for BR-50
Detect BR-50 before submission
This error involves a financial field that can't be auto-modified. We'll flag it with a clear diagnosis so you can fix it at the source.