errorbusinessEN 16931

BR-04:Missing invoice type code

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

An Invoice shall have an Invoice type code (BT-3). The most common value is 380 for a standard commercial invoice.

Severity
Fatal
Rule set
EN 16931
Country
All EU
Fix type
AUTO-FIX
Confidence
85%
Category
structural

Engine Classification

Set to 380 (Commercial Invoice) if missing or invalid

Confidence: 85% · Applied automatically in pipeline

What is BR-04?

BR-04 is a fatal validation rule defined in the EN 16931 specification. It validates the InvoiceTypeCode 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:InvoiceTypeCode

Why This Error Matters

Invoice rejected. Receiver cannot determine how to process the document (as payment request vs. credit).

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

Currency code is required for proper processing of payments and VAT calculations across different countries. Without it, amounts cannot be interpreted correctly.

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

How to Fix It

1.

Determine document type

Is this a standard invoice (380), credit note (381), or other type?

2.

Add InvoiceTypeCode

Insert <cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode> after IssueDate

3.

Verify position

InvoiceTypeCode must come after IssueDate and before DocumentCurrencyCode

Before / After

Failing XML
<cbc:InvoiceTypeCode></cbc:InvoiceTypeCode>
Corrected XML
<cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>

Technical Reference

XPath/Invoice/cbc:InvoiceTypeCode
SpecEN 16931
Operationset_default
StrategySet to 380 (Commercial Invoice) if missing or invalid

Code Example

<cbc:DocumentCurrencyCode>EUR</cbc:DocumentCurrencyCode>

Common Causes

  • ·Invoice type code (380/381/etc) not mapped in export
  • ·Source system doesn't distinguish between invoice types
  • ·Template using wrong field for InvoiceTypeCode
  • ·Credit note exported without type code change
  • ·Default type code not configured in export settings

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

Commonly Seen In

All invoicing software

Frequently Asked Questions

The invoice must specify the document currency using an ISO 4217 three-letter code.

Add the correct three-letter ISO currency code. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.

Yes, BR-04 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-04 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 a currency code.

BR-04 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: 27 February 2026

Share this guide:

Validate your invoice

Drop your XML here to check for BR-04

Auto-fix BR-04 in seconds

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