SE-R-011:Swedish suppliers using Bankgiro or Plusgiro must use PaymentMeansCode 30...
Swedish suppliers using Bankgiro or Plusgiro must use PaymentMeansCode 30 with FinancialInstitutionBranch ID as SE:BANKGIRO or SE:PLUSGIRO.
Engine Classification
Set payment means code to 30 for Swedish Bankgiro/Plusgiro payments
Confidence: 90% · Applied automatically in pipeline
What is SE-R-011?
SE-R-011 is a fatal validation rule defined in the Peppol BIS 3.0 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
Why This Error Matters
Invoice will be rejected by Swedish validation. Proper payment structure required for Bankgiro/Plusgiro.
SE-R-011 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
- ·Rejected by PEPPOL Access Points
- ·Error returned: SE-R-011
- ·Specification: Peppol BIS 3.0
Before / After
<Invoice> <!-- Issue: For Swedish suppliers using Bankgiro or Plusgiro, use Paymen --> </Invoice>
<Invoice> <!-- Issue resolved per Peppol BIS 3.0 --> </Invoice>
Technical Reference
//cac:PaymentMeans/cbc:PaymentMeansCodeCommon Causes
- ·Wrong payment means code for Bankgiro/Plusgiro
- ·Institution branch ID not set correctly
- ·Generic payment code used instead of 30
- ·SE:BANKGIRO or SE:PLUSGIRO identifier missing
- ·Payment structure incorrect for Swedish giro
Seeing this in production? The API handles SE-R-011 automatically. See the fix response →
See Also
Last updated: 27 February 2026
Handle SE-R-011 Automatically in Your Pipeline
The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.