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.
This requires user input to resolve. Provide the correct value for `cac:PaymentMeans` (BG-16). Invoice Navigator detects this error and prompts for the required business data before applying a safe fix.
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.
BR-49 requires specific business data to resolve. Invoice Navigator detects the error and guides you through providing the needed information, then applies the fix with full audit documentation.
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.
Related Content
Last updated: 3 March 2026
Resolve BR-49 with Guided Input
The compliance engine detects this error and prompts for the required business data before applying a safe, auditable fix.