How do I fix UBL-SR-47?

Invoice Navigator automatically fixes this Invoice compliance issue by updating the relevant XML elements (UBL-SR-47). You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

Is UBL-SR-47 a critical error?

Yes, UBL-SR-47 is a critical error that will cause invoice rejection. It must be fixed before submission.

Can UBL-SR-47 be automatically fixed?

Many instances of UBL-SR-47 can be automatically corrected using Invoice Navigator's compliance engine. The fix is applied in your pipeline with full audit evidence.

errorEN 16931

`UBL-SR-47`:Multiple different payment methods on one invoice

Your invoice has multiple payment means sections with different payment method codes. The UBL standard requires that all payment means on a single invoice use the same payment method code.

Severity

Fatal

Rule set

EN 16931

Country

All EU

Fix type

AUTO-FIX

Confidence

75%

Engine Classification

Present user with the conflicting payment means codes and ask them to choose which one applies to the entire invoice

Confidence: 75% · Applied automatically in pipeline

What is UBL-SR-47?

UBL-SR-47 is a fatal validation rule defined in the EN 16931 specification. It validates the PaymentMeansCode 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: //cac:PaymentMeans/cbc:PaymentMeansCode

Get API Access Test This Error ↓

Why This Error Matters

Invoice will be rejected. EN16931 requires a single payment method type, though multiple accounts for that method are allowed.

UBL-SR-47 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: UBL-SR-47
·Specification: EN 16931

How to Fix It

Before / After

Failing XML

<Invoice>
  <!-- Issue: When there are more than one payment means code, they shall  -->
</Invoice>

Corrected XML

<Invoice>
  <!-- Issue resolved per EN 16931 -->
</Invoice>

Technical Reference

XPath//cac:PaymentMeans/cbc:PaymentMeansCode

SpecEN 16931

Operationset_value

StrategyPresent user with the conflicting payment means codes and ask them to choose which one applies to the entire invoice

Common Causes

·Multiple payment options offered (e.g., bank transfer AND credit card)
·ERP allows different payment methods per payment instruction
·Template supports multiple payment types not allowed in EN16931
·Migration from system that supported multiple payment types
·Manual editing added payment means with different codes

Seeing this in production? The API handles UBL-SR-47 automatically. See the fix response →

Handle UBL-SR-47 Automatically in Your Pipeline

The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.

Get API Access View API Documentation

UBL-SR-47:Multiple different payment methods on one invoice