BR-22:Invoice currency code required
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: Document 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 non-compliant and will be rejected by Peppol access points and national validation services. The sending system receives a rejection response and the invoice does not reach 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. Invoices that trigger this rule are rejected at the access point and never reach the recipient. In Peppol networks, this means your sending system receives an MLR (Message Level Response) with a rejection status. The invoice must be corrected and re-sent, adding delay to your payment cycle.
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.
Add DocumentCurrencyCode with valid ISO currency. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.
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.
Many instances of BR-22 can be automatically corrected using Invoice Navigator's Fixer tool. Upload your invoice and the tool will identify and fix common issues, including invoice currency code required.
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.
See Also
Related Errors
Last updated: 27 February 2026
Handle BR-22 Automatically in Your Pipeline
The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.