errorEN 16931

BR-05:Missing document currency code

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.

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 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: /Invoice/cbc:DocumentCurrencyCode

Why This Error Matters

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

BR-05 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.

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

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

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.

See Also

Related Errors

Last updated: 27 February 2026

Share this guide:

Handle BR-05 Automatically in Your Pipeline

The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.