BR-04:Missing invoice type code
An Invoice shall have an Invoice type code (BT-3). The most common value is 380 for a standard commercial invoice.
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 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: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. 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-04
- ·Specification: EN 16931
How to Fix It
Determine document type
Is this a standard invoice (380), credit note (381), or other type?
Add InvoiceTypeCode
Insert <cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode> after IssueDate
Verify position
InvoiceTypeCode must come after IssueDate and before DocumentCurrencyCode
Before / After
<cbc:InvoiceTypeCode></cbc:InvoiceTypeCode>
<cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
Technical Reference
/Invoice/cbc:InvoiceTypeCodeCode 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
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.
See Also
Related Errors
Last updated: 27 February 2026
Handle BR-04 Automatically in Your Pipeline
The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.