errorbusinessEN 16931

BR-53:VAT amount in accounting currency is missing

Fix: Update the `cbc:TaxCurrencyCode` element to use a value from the allowed code list.

Your invoice declares a tax accounting currency (different from the invoice currency), but the total VAT amount in that accounting currency is not provided. When using a separate tax currency, you must include the VAT total in both currencies.

Severity
Fatal
Rule set
EN 16931
Country
All EU
Fix type
BLOCKED
Confidence
97%

Engine Classification

Financial or legal field · Modification blocked by policy

Reason: The missing VAT amount in accounting currency cannot be derived safely without the authoritative exchange rate and accounting currency settings used by the source system on the invoice date.

What is BR-53?

BR-53 is a fatal validation rule defined in the EN 16931 specification. It validates the AccountingCost element under Invoice > InvoiceLine 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:AccountingCost or /Invoice/cac:InvoiceLine/cbc:AccountingCost

This error requires manual correction — financial fields are protected by policy.

Why This Error Matters

Invoice rejected. Tax reporting requires VAT amounts in the accounting currency for proper bookkeeping.

BR-53 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.

Validators reject invoices that declare a tax accounting currency without providing the corresponding VAT amount. Tax authorities require the VAT to be reported in the accounting currency for cross-border transactions.

Validator Behavior

  • ·Causes invoice rejection
  • ·Error returned: BR-53
  • ·Specification: EN 16931

How to Fix It

.

.

.

.

.

Before / After

Failing XML
<Invoice>
  <cbc:TaxCurrencyCode>999.99</cbc:TaxCurrencyCode>
  <!-- Does not match expected calculation -->
</Invoice>
Corrected XML
<Invoice>
  <cbc:TaxCurrencyCode>100.00</cbc:TaxCurrencyCode>
  <!-- Matches expected calculation -->
</Invoice>

Technical Reference

XPathXPath: /Invoice/cbc:AccountingCost or /Invoice/cac:InvoiceLine/cbc:AccountingCost
SpecEN 16931
StrategyDo not auto-fix. This rule concerns a required VAT amount expressed in accounting currency, which depends on the document's accounting currency context and the applicable exchange rate from the source ERP/accounting system.

Code Example

<cbc:AccountingCost>CC-4500-001</cbc:AccountingCost>
<!-- Or per line -->
<cac:InvoiceLine>
  <cbc:AccountingCost>PROJECT-ABC</cbc:AccountingCost>
</cac:InvoiceLine>

Common Causes

  • ·VAT accounting currency specified but amount missing
  • ·TaxCurrencyCode set without TaxAmount in that currency
  • ·Dual currency invoice missing converted VAT total
  • ·Currency conversion not applied to tax amounts
  • ·Template has currency code but not converted amount field

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

Commonly Seen In

All invoicing software

Frequently Asked Questions

AccountingCost can provide buyer cost center or account code.

Update the `cbc:TaxCurrencyCode` element to use a value from the allowed code list. This error involves a protected field — Invoice Navigator flags it in your pipeline so your team can correct it at the source.

BR-53 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-53 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-53 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

Share this guide:

Validate your invoice

Drop your XML here to check for BR-53

Detect BR-53 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.