SE-R-003:Swedish organisation numbers should be numeric.
Swedish organization numbers must contain only numeric characters. No letters or special characters allowed.
Engine Classification
Remove non-numeric characters (spaces, hyphens) from Swedish organisation number
Confidence: 90% · Applied automatically in pipeline
What is SE-R-003?
SE-R-003 is a fatal validation rule defined in the Peppol BIS 3.0 specification. It validates the CompanyID element under Party > PartyLegalEntity 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:AccountingSupplierParty/cac:Party/cac:PartyLegalEntity/cbc:CompanyID
Why This Error Matters
Invoice will be rejected by Swedish validation. Organization number must be purely numeric.
SE-R-003 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-003
- ·Specification: Peppol BIS 3.0
Before / After
<Invoice> <!-- Issue: For Swedish suppliers, organisation numbers should be numeri --> </Invoice>
<Invoice> <!-- Issue resolved per Peppol BIS 3.0 --> </Invoice>
Technical Reference
//cac:AccountingSupplierParty/cac:Party/cac:PartyLegalEntity/cbc:CompanyIDCommon Causes
- ·Non-numeric characters in org number
- ·Hyphen included in number
- ·Letters or spaces present
- ·Formatting not removed
- ·Wrong identifier used
Seeing this in production? The API handles SE-R-003 automatically. See the fix response →
See Also
Last updated: 27 February 2026
Handle SE-R-003 Automatically in Your Pipeline
The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.