Troubleshooting

Endpoint creation errors

Endpoint creation returns an M-NO-3001xxx error code.


Code	Cause	Resolution
`M-NO-3001007`	Participant already registered in ELMA under another service provider	Contact the current service provider to arrange a migration or SMP transfer, then retry endpoint creation.
`M-NO-3001010`	ELMA requires a contact name	Supply `contact.name` and `contact.email` on the endpoint request. Both fields are required when either is provided.
`M-NO-3001009`	ELMA credentials rejected	This is a Sovos configuration issue, contact Sovos support.
`M-NO-3001022`	No ELMA process could be resolved	The document type being registered doesn't map to a supported BIS Billing 3.0 process. Verify the `productId` and `supportedDocuments` values in your request.
`M-NO-3001008`	ELMA API read failure	If transient, retry. If persistent, check ELMA (Digdir) service status.
`M-NO-3001006`	ELMA registration write failure	If transient, retry. If persistent, check ELMA (Digdir) service status and contact Sovos support.
`M-NO-3001014`	Outbound endpoint creation rejected for this document type	Outbound endpoints accept only `LifeCycle` document types in `supportedDocuments`. Invoice and CreditNote subTypes belong on the inbound endpoint.

Submitted invoice returns a transaction status of Rejected with NS-17011002 or NS-17011004.

NS-17011002: Payload couldn't be converted to validation format

Verify that:

The root element is <Invoice> in the urn:oasis:names:specification:ubl:schema:xsd:Invoice-2 namespace.
cbc:UBLVersionID is 2.1.
cbc:CustomizationID is exactly urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0.
cbc:ProfileID is urn:fdc:peppol.eu:2017:poacc:billing:01:1.0.
Mapping.InputSchema in the SBDH is set to ALL-PEPPOLBISUBL-3.0-INVOICE-1.0.

NS-17011004: Schematron validation failed

The notification payload lists each failing rule ID. For Norway-specific rule failures:


Rule	Fix
NO-R-001	Set supplier VAT ID to `NO<orgnr>MVA` in `cac:PartyTaxScheme[VAT]/cbc:CompanyID`.
NO-R-002	Add a `cac:PartyTaxScheme` with `TaxScheme/ID = TAX` and `cbc:CompanyID = Foretaksregisteret` on the supplier party. Applies to AS, ASA, and NUF entities.
PEPPOL-COMMON-R041	Fix any `schemeID="0192"` identifier — must be a bare 9-digit orgnr passing MOD-11. No `NO` prefix, no `MVA`, no separators.

Invoice rejected with M-PPL-2104006, M-NO-3004003, or NS-17035002. Distribution may also show NS-17020002.

Before sending an invoice, verify that the buyer is registered in the PEPPOL network:

Look up the buyer at 0192:<orgnr> in the PEPPOL Directory.
If the buyer isn't listed, they have no PEPPOL Access Point and the invoice can't be delivered through PEPPOL.
If the buyer's organization exists in Brønnøysundregistrene but isn't in ELMA, ask the buyer to register with a PEPPOL Access Point, or deliver the invoice by another channel.

M-NO-3008xxx, M-NO-3001002, M-NO-3001012, M-NO-3004005, M-NO-3004006, or schematron rule PEPPOL-COMMON-R041.

Norwegian organisasjonsnummer rules:

Format: 9 digits, no prefix, no separators. Example: 123456789.
MOD-11 checksum: The 9th digit is a calculated check digit. Verify any orgnr against Brønnøysundregistrene before using it.
In UBL identifiers (schemeID="0192"): Use the bare 9-digit orgnr.
In the VAT field only: Use NO<orgnr>MVA. Example: NO123456789MVA.
Duplicate: M-NO-3008005 means this orgnr is already registered in your workspace. Retrieve the existing endpoint record rather than creating a new one.