BR-49:A Payment instruction (BG-16) shall specify the Payment means type code (BT-81)
A Payment instruction (BG-16) shall specify the Payment means type code (BT-81). This applies to the `cac:PaymentMeans` element in the invoice XML.
Engine Classification
Business data required · Explicit input workflow · No assumptions made
What is BR-49?
BR-49 is a fatal validation rule defined in the EN 16931 specification. It validates the Name element under PayeeFinancialAccount 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: //cac:PaymentMeans/cac:PayeeFinancialAccount/cbc:Name
Why This Error Matters
Invoice rejected. Buyer needs to know the accepted payment method.
BR-49 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.
Validator Behavior
- ·Causes invoice rejection
- ·Error returned: BR-49
- ·Specification: EN 16931
How to Fix It
Add registration
Company registration number
Add scheme
schemeID for identifier type (0002=SIRENE, 0106=KVK)
Different from VAT
Legal ID vs VAT ID
Before / After
<Invoice> <cac:PaymentMeans>INVALID_CODE</cac:PaymentMeans> </Invoice>
<Invoice> <cac:PaymentMeans>VALID_CODE</cac:PaymentMeans> </Invoice>
Technical Reference
//cac:PaymentMeans/cac:PayeeFinancialAccount/cbc:NameCode Example
<cac:PartyLegalEntity>
<cbc:RegistrationName>ACME Trading BV</cbc:RegistrationName>
<cbc:CompanyID schemeID="0106">12345678</cbc:CompanyID>
</cac:PartyLegalEntity>Common Causes
- ·Payment instruction missing payment means code
- ·PaymentMeansCode field not mapped in export
- ·Payment details added without method specification
- ·Template missing payment type code field
- ·Payment means code stored as text not UNCL4461 code
Seeing this in production? The API handles BR-49 automatically. See the fix response →
Commonly Seen In
Frequently Asked Questions
Seller and buyer should include legal registration identification.
Add CompanyID in PartyLegalEntity. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.
BR-49 is a warning that may not always cause rejection, but it indicates a potential compliance issue that should be addressed to ensure full compatibility.
Many instances of BR-49 can be automatically corrected using Invoice Navigator's Fixer tool. Upload your invoice and the tool will identify and fix common issues, including party legal registration recommended.
BR-49 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-49 Automatically in Your Pipeline
The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.