errorbusinessen16931

BR-CO-02:Payment means code must be valid

Fix: Use valid UNCL4461 payment code. Provide the required value in the free validator.

Payment means type code must be from UNCL4461.

Severity
Fatal
Rule set
en16931
Country
All EU
Fix type
INPUT REQUIRED

Engine Classification

Business data required · Explicit input workflow · No assumptions made

Required input: Payment Means Code

What is BR-CO-02?

BR-CO-02 is a fatal validation rule defined in the en16931 specification. It validates the PaymentMeansCode element under Invoice > PaymentMeans 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/cac:PaymentMeans/cbc:PaymentMeansCode

Why This Error Matters

Payment codes enable automated payment processing.

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

Validator Behavior

  • ·Causes invoice rejection
  • ·Fails EN 16931 business rule validation
  • ·Error returned: BR-CO-02
  • ·Specification: en16931

How to Fix It

1.

Check payment code

Find PaymentMeansCode value

2.

Use valid code

30=Credit transfer, 58=SEPA credit, 59=SEPA direct debit, 48=Card

XML Example

Generic example based on the rule's target XPath. Your actual XML structure may differ.

Before
<!-- Missing or empty element triggers cbc:PaymentMeansCode error -->
<cbc:PaymentMeansCode></cbc:PaymentMeansCode>
After
<!-- Provide the required value -->
<cbc:PaymentMeansCode>VALID_VALUE</cbc:PaymentMeansCode>

Technical Reference

XPathXPath: /Invoice/cac:PaymentMeans/cbc:PaymentMeansCode
Specen16931

Common Causes

  • ·Invalid code value
  • ·Using deprecated code

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

Frequently Asked Questions

Payment means type code must be from UNCL4461.

Use valid UNCL4461 payment code. Invoice Navigator detects this error and prompts for the required business data before applying a safe fix.

Yes, BR-CO-02 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.

BR-CO-02 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.

Related Errors

Related Content

Last updated: 3 March 2026

Share this guide:

Validate your invoice

Drop your XML here to check for BR-CO-02

Fix BR-CO-02 with guided input

Upload your invoice and we'll ask for the missing data, then apply a safe, auditable fix.