BR-05EN 16931fatalbusiness

Missing document currency code

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

An Invoice shall have an Invoice currency code (BT-5). This specifies the currency used for all monetary amounts in the invoice using ISO 4217 three-letter codes.

Where is this in my invoice?

Shown on a sample invoice. The marked row is the field this rule checks; on your own invoice it sits in the same place.

Sample invoice · not your document

Invoice

SAMPLE-INV-001 · issued 4 Jan 2026 · due 4 Feb 2026 · EUR

Seller

Seller nameSample Supplier B.V.
Seller streetHerengracht 100
Seller postcode1015 BS
Seller cityAmsterdam
Seller countryNL
Seller VAT numberNL123456789B01
Seller registration number12345678
Seller electronic addressNL123456789B01

Buyer

Buyer nameSample Buyer NV
Buyer streetRue de la Loi 42
Buyer postcode1000
Buyer cityBrussels
Buyer countryBE
Buyer VAT numberBE0123456789
Buyer electronic addressBE0123456789

Invoice details

Invoice numberSAMPLE-INV-001
Issue date4 Jan 2026
Due date4 Feb 2026
Invoice type380
CurrencyEUR BR-05
Buyer referencePO-12345

Payment

Payment method30
Payment IBANNL91ABNA0417164300

Line items

No.ItemQuantityUnit priceVAT rate (%)Line amount
1Consulting Services1€100.0021%€100.00

Totals

Sum of line amounts€100.00
Total without VAT€100.00
Total VAT€21.00
Total with VAT€121.00
Amount due€121.00

VAT breakdown

VAT categoryVAT rate (%)Taxable amountVAT amount
S21%€100.00€21.00

How to Fix It

1.

Identify currency

Determine the currency from amount attributes (currencyID) or business context

2.

Add DocumentCurrencyCode

Insert <cbc:DocumentCurrencyCode>EUR</cbc:DocumentCurrencyCode> after InvoiceTypeCode

3.

Verify consistency

All monetary amounts should use the same currency code in their currencyID attribute

See this rule against your own invoice: every finding is pinned to the row it concerns.

Severity
Fatal
Rule set
EN 16931
Country
All EU
Fix type
Auto-fix
Category
party_info

Engine Classification

Auto-fix: Derive currency from amount fields if they contain currency symbols or codes. If all amounts are in the same currency, extract and use that code. Falls back to EUR for European invoices if cannot derive.

What is BR-05?

BR-05 is a fatal validation rule defined in the EN 16931 specification. It validates the DocumentCurrencyCode 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: /Invoice/cbc:DocumentCurrencyCode

Why This Error Matters

Invoice rejected. Receiver cannot process payment without knowing the currency.

BR-05 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-05
  • ·Specification: EN 16931

Before / After

Failing XML
<cbc:DocumentCurrencyCode></cbc:DocumentCurrencyCode>
Corrected XML
<cbc:DocumentCurrencyCode>EUR</cbc:DocumentCurrencyCode>

Technical Reference

XPath/Invoice/cbc:DocumentCurrencyCode
SpecEN 16931
Operationderive_or_default
StrategyAuto-fix: Derive currency from amount fields if they contain currency symbols or codes. If all amounts are in the same currency, extract and use that code. Falls back to EUR for European invoices if cannot derive.

Code Example

<cac:PartyLegalEntity>\n  <cbc:RegistrationName>Acme Corporation B.V.</cbc:RegistrationName>\n</cac:PartyLegalEntity>

Common Causes

  • ·Currency code field not mapped in export template
  • ·Multi-currency system didn't specify document currency
  • ·Currency assumed from locale but not explicitly set
  • ·Template missing DocumentCurrencyCode field
  • ·Currency stored as symbol (€) not ISO code (EUR)

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

Commonly Seen In

QuickBooksXeroSageCustom ERP

Frequently Asked Questions

The invoice must contain the legal name of the seller/supplier.

Add the seller's legal registered name. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.

Yes, BR-05 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-05 can be automatically corrected using Invoice Navigator's Fixer tool. Upload your invoice and the tool will identify and fix common issues, including invoice must have seller name.

BR-05 is commonly seen in exports from QuickBooks, Xero, Sage, Custom ERP. These software packages sometimes generate invoices that need adjustment to meet full compliance standards.

Related Errors

Related Content

Last updated: 14 June 2026

Share this guide:

Validate your invoice

Drop your XML here to check for BR-05

Auto-fix BR-05 in seconds

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