BR-22:Invoice currency code required
Fix: This requires user input to resolve. Provide the correct value for `cbc:InvoicedQuantity`. Provide the required value in the free validator.
The invoice must specify the document currency using ISO 4217 alpha-3 code.
Engine Classification
Business data required · Explicit input workflow · No assumptions made
Required input: Currency Code
What is BR-22?
BR-22 is a fatal validation rule defined in the EN 16931 specification. It validates the DocumentCurrencyCode element under Invoice 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: /Invoice/cbc:DocumentCurrencyCode
Why This Error Matters
Invoice rejected. Quantity is required for price verification and inventory/procurement matching.
BR-22 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-22
- ·Specification: EN 16931
How to Fix It
Add currency code
Common: EUR, USD, GBP, SEK, NOK, DKK
Use ISO 4217
Three-letter uppercase code
Match amounts
All amount currencyID must match
Before / After
<cac:InvoiceLine> <!-- cbc:InvoicedQuantity is missing --> </cac:InvoiceLine>
<cac:InvoiceLine> <cbc:InvoicedQuantity>valid-value</cbc:InvoicedQuantity> </cac:InvoiceLine>
Technical Reference
XPath: /Invoice/cbc:DocumentCurrencyCodeCode Example
<cbc:DocumentCurrencyCode>EUR</cbc:DocumentCurrencyCode>Common Causes
- ·InvoicedQuantity field not mapped in export
- ·Service invoice without quantity concept (needs 1)
- ·Lump sum pricing without unit quantity breakdown
- ·Quantity stored in wrong field in source system
- ·Export template missing quantity field mapping
Seeing this in production? The API handles BR-22 automatically. See the fix response →
Commonly Seen In
Frequently Asked Questions
The invoice must specify the document currency using ISO 4217 alpha-3 code.
This requires user input to resolve. Provide the correct value for `cbc:InvoicedQuantity`. Invoice Navigator detects this error and prompts for the required business data before applying a safe fix.
Yes, BR-22 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.
BR-22 requires specific business data to resolve. Invoice Navigator detects the error and guides you through providing the needed information, then applies the fix with full audit documentation.
BR-22 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: 15 April 2026
Validate your invoice
Drop your XML here to check for BR-22
Fix BR-22 with guided input
Upload your invoice and we'll ask for the missing data, then apply a safe, auditable fix.