Answers to common questions about Norway e-invoicing implementation.

Can I reuse an invoice number after a failed submission?

It depends on the failure point.

• If your invoice reached status 401 (Error), Sovos rejected it before the document was sent to the PEPPOL network. The invoice number wasn't consumed on the network and can be reused.

• If the invoice reached status 204 (Distributed), the document was delivered to the buyer's Access Point and the invoice number is consumed in the PEPPOL network. Don't reuse it.

• If you're unsure whether a document was transmitted, contact Sovos support before resubmitting. The PEPPOL network doesn't enforce duplicate invoice number checks at the Access Point level. Compliance Network does implement its own duplicate check to prevent duplicate submissions within the platform.

The NO-R-002 validation warning appears in my validation response. Is my invoice rejected?

No. NO-R-002 has a severity of fatal and submission will fail. You must include Foretaksregisteret in the supplier's cac:PartyTaxScheme[TAX]/cbc:CompanyID field. Resolve the issue to ensure your invoices are legally compliant before go-live.

My endpoint creation returned HTTP 201 but registeredDirectories is empty. What does this mean?

An empty registeredDirectories array means the endpoint was created in Sovos but the PEPPOL SMP (ELMA) publication step didn't complete. Your endpoint isn't yet visible to other PEPPOL participants. Buyers can't route invoices to you, and you can't send to the PEPPOL network from this endpoint. Delete the endpoint and create a new one, either if it is for outbound or inbound.

How long does PEPPOL delivery take for Norway?

PEPPOL network delivery is near real-time. A successfully validated invoice typically reaches the buyer's Access Point within seconds to a few minutes (status 204). Invoice Response from the buyer (if sent) is buyer-dependent and may take longer. There are no known scheduled maintenance windows for Norway's ELMA infrastructure. For integration, poll at reasonable intervals: 30 seconds initially, then every 1-5 minutes for the first hour. Norway uses Compliance Network standard polling intervals, no Norway-specific overrides.

My invoice reached status 204 (Distributed) but the buyer says they haven't received it. What should I check?

Status 204 confirms that the buyer's Access Point acknowledged receipt at the PEPPOL network level. Processing and delivery within the buyer's internal systems is the buyer's Access Point's responsibility and is outside Sovos's visibility. Ask the buyer to check with their Access Point provider or ERP system for the invoice with your document ID and orgnr. You can provide the correlationId from the notification payload to help trace the document.

Can I cancel a sent invoice?

Norway doesn't support invoice cancellation through Compliance Network. To reverse a sent invoice, issue a credit note (document type code 381) that references the original invoice number in cac:BillingReference. A credit note follows the same PEPPOL submission flow as a standard invoice.

What is the difference between the error codes I see (NS-17xxx, M-NO-3xxxxx, M-PPL-21xxxxx)?

These are three distinct code families that operate at different layers:

NS-17xxx

Sovos document pipeline codes. Emitted during document processing (validation, routing, delivery) regardless of country. Examples: NS-17011004 (schematron validation failed), NS-17035002 (buyer endpoint not found).

M-NO-3xxxxx

Norway-specific extension codes. Emitted by the Norway PEPPOL plugin during ELMA registration, endpoint management, and Norwegian orgnr validation. You see these when managing endpoints or when Norwegian-specific routing checks fail.

M-PPL-21xxxxx

PEPPOL network codes. Emitted when events occur at the PEPPOL network layer (SMP/ELMA lookup, Access Point communication). M-PPL-2104006 is the primary "buyer not in PEPPOL" code for Norway.

All three families can appear in the same notification alongside SCICloudStatusCode. See Norway-specific codes for the full reference.