Norway E-Invoicing Compliance

Who has to issue structured e-invoices in Norway?

From 1 January 2027, every business with a bookkeeping obligation in Norway must issue invoices to other bookkeeping-obligated businesses in a structured electronic format (bokføringsloven § 10, as amended by lov 19 juni 2026 nr. 39). Regulation FOR-2026-09-29-1933 approves EHF Fakturering, Peppol BIS Billing, EHF Selvfakturering and Peppol BIS Self-Billing, version 3.0 or later; until 31 December 2029 the parties may agree on another electronic invoice format. The Tax Administration says that until 2030 the duty applies in practice only when the buyer can receive e-invoices, meaning it is registered in ELMA/Peppol, and that a PDF cannot be used for a buyer that can receive.

The second step lands on 1 January 2030: businesses must be able to receive e-invoices and must keep their books in a digital bookkeeping system that can process them. The consultation of 1 July 2025 had proposed 2028; the government brought issuing forward to 2027 in Prop. 44 L (2025–2026), which the Storting adopted in June 2026. From 1 January 2028 the buyer’s organisation number must appear on the sales document, followed by MVA if the buyer is VAT-registered (bokføringsforskriften § 5-1-2).

The regulation exempts businesses with turnover of NOK 50,000 or less a year from the receiving duty, and for them the issuing duty applies only if they invoice from a system that can issue e-invoices; the exemption ends once the threshold is passed (bokføringsforskriften § 1-2). Bankruptcy estates and certain financial-services and insurance businesses are also exempt.

Which format does Norway require?

EHF (Elektronisk handelsformat), version 3.0 or newer. EHF Billing 3.0 is not a separate standard: it is Peppol BIS Billing 3.0, in UBL 2.1, compliant with EN 16931, with the Norwegian rules applied whenever the seller is Norwegian. An EHF invoice is a Peppol invoice and is delivered over the Peppol network — there is no national platform in the middle.

Two Norwegian rules matter most. NO-R-001 requires the seller’s VAT identifier as NO + organisation number + MVA. NO-R-002 expects a limited company (AS or ASA) to state Foretaksregisteret. The Norwegian usage guide also covers the KID payment reference, a Norwegian bank account written as a BBAN without a BIC, and CO₂ data per line. GoRoute exposes each as a named field, so your ERP posts the value and the XML comes out right.

The VAT categories are where most EHF invoices fail first. All four Norwegian rates above zero — 25%, 15%, 12% and 11.11% — carry the same category code S, with the rate in the percentage field; a code invented for a reduced rate is rejected by BR-CL-17. Which VAT category code carries each Norwegian rate sets out the full code set, what each one requires, and how to read a rejection report.

Document type codes follow UNCL1001: 380 for an invoice and 381 for a credit note. If you are unsure how Peppol BIS relates to the newer PINT specifications used in Oman and Australia, we explain the difference here.

The identifier: why Norwegian companies use scheme 0192

On Peppol a Norwegian business is identified by its nine-digit organisation number from the Brønnøysund Register Centre, under scheme 0192. The Norwegian Peppol Authority’s requirements allow no other identifier for a Norwegian participant. Scheme 9908 was removed from Peppol’s code list in 2023 and 9909 (NO:VAT) is deprecated, and the VAT form NO123456789MVA is a tax identifier, not a Peppol address.

The last digit is a mod-11 check digit. Peppol validates it, and an invoice carrying a malformed number is rejected with rule PEPPOL-COMMON-R041. GoRoute enforces the scheme and the check digit at registration, so a bad identifier is caught before it reaches the network. Other avoidable rejections are covered in invoice validation errors you can prevent.

ELMA and the one-SMP rule

ELMA is Norway’s central Peppol registry, run by Digdir. Public-sector bodies must be registered there, and a large share of private companies are too — Norway has the highest Peppol coverage of any country, so most Norwegian buyers can already receive EHF.

The network allows one SMP per participant. Before publishing a Norwegian company, GoRoute checks the organisation number in Enhetsregisteret and refuses a sub-unit (naming the legal entity to use), a deleted entity, a public body (which belongs in ELMA) and any company another SMP already hosts — naming the provider. To receive through GoRoute, the company’s current provider removes its registration first. Sending to a Norwegian company needs none of this.

If you are choosing a provider for the first time, how to choose a Peppol access point sets out what matters, and our onboarding checklist for finance teams covers the internal work.

For the registration itself — who publishes you, what your provider must check first, and why there is no form for a private company to file — see how a Norwegian business becomes reachable for EHF invoices.

What does the law mean for a foreign business registered for Norwegian VAT?

On our reading, it places that business inside the mandate. The law applies to entities with bookkeeping obligations, and Norway’s Bookkeeping Act settles who those are. Section 2 of bokføringsloven gives a bookkeeping obligation to anyone required to file a Norwegian VAT return, for the activity that return covers — so a foreign company that is VAT-registered in Norway is bookkeeping-obliged there, whether or not it has a Norwegian parent, staff or office. That reading follows the statute rather than any statement by the Ministry of Finance about foreign businesses specifically, and it is marked here as our reading of the adopted law, not as a confirmed position: the Tax Administration has not yet said how the duty applies to foreign businesses.

The practical question that follows is one of identity rather than obligation. A foreign business becomes reachable on Peppol in Norway only through an organisation number in Enhetsregisteret, because the Norwegian Peppol Authority Specific Requirements allow no other identifier for a Norwegian participant. A home-country VAT number will not route, and neither will a Norwegian VAT number on its own — the routing value is the bare nine digits under scheme 0192.

Most foreign businesses trading into Norway already have one. A NUF — norskregistrert utenlandsk foretak, a Norwegian-registered foreign enterprise — holds an ordinary nine-digit organisation number and is registered on Peppol exactly like a Norwegian company. This is a large population rather than an edge case: Enhetsregisteret’s own open data API returned 25,821 NUF entries when we queried it on 24 September 2026.

Three consequences are worth planning around now, before the issuing duty starts on 1 January 2027:

• Decide which entity invoices. A group invoicing Norwegian customers from a foreign entity, while also holding a NUF, has two candidate senders and only one of them has a Norwegian Peppol identity. That choice drives the ERP configuration, not the other way round.
• Sending needs no Norwegian identity; receiving does. You can send EHF to any Norwegian buyer today through a certified access point established anywhere. Being reachable for incoming invoices is what requires the organisation number and the SMP registration.
• A VAT representative is not a Peppol address. Where a foreign business is VAT-registered through a representative, the representative’s own organisation number is that firm’s identity, not yours. Invoices addressed to it are addressed to the wrong legal entity.

If your business is VAT-registered in Norway and you do not know whether it also sits in Enhetsregisteret, that is the first thing to establish — a free lookup answers it, and every other decision here follows from the answer.

Three EHF specifications Peppol BIS Billing 3.0 does not cover

Norway’s invoice itself is not special: EHF billing is Peppol BIS Billing 3.0, which is why an invoice that validates for Belgium or Italy validates for Norway once the national rules are applied. What is Norwegian is the set of billing documents that sit alongside the invoice. DFØ publishes them at anskaffelser.dev as part of EHF Post-Award G3, each with its own implementation guideline and its own Schematron rules, and Peppol BIS Billing 3.0 contains no equivalent of any of them.

• EHF Reminder 3.0 — the electronic payment reminder, purring. There is no Peppol BIS reminder.
• EHF Forward Billing 3.0 — gjennomfakturering, Norwegian electricity practice: a grid company’s network-services invoice forwarded to the end customer through that customer’s power supplier.
• EHF Payment Request 3.0 — betalingsforespørsel, a request to an organisation’s own payment function to pay somebody entitled to money. Not a sale, and not a VAT invoice.

Each document is a separate opt-in in your SMP entry, because Peppol routes on a document-type and process pair and all three declare their own. A participant published for Billing only will not receive a reminder, and the sender’s access point sees that at lookup time rather than on delivery. What each document is for, what is different inside it, and how to check a Norwegian partner before you build are set out in the three Norwegian billing documents Peppol does not have. The same lookup answers the question that stalls most provider migrations, which is whether a company is already registered somewhere and with whom — check a Norwegian company’s Peppol registration before you plan around an assumption about it.

GoRoute built all three on 17 September 2026 against the official EHF rules and delivered each end to end on our test network, alongside EHF Selvfakturering (self-billing), Catalogue, Ordering, Order Agreement, Advanced Ordering and Despatch Advice. Two areas we do not support, and say so rather than leave to discovery: the pre-award G2 documents, which are public tendering rather than invoicing, and the Payment domain, for which DFØ lists additional testing as still to be announced. The Payment domain is not the same thing as the payment details inside an invoice — how KID, IBAN and BBAN payment details travel in an EHF invoice sets out where each value belongs, and why a wrong KID passes every validation rule and still loses the payment.

Can a foreign provider handle Norwegian e-invoicing?

Yes. The Norwegian Peppol Authority is DFØ, the Agency for Public and Financial Management, and it has confirmed that a certified Peppol access point established elsewhere needs no separate Norwegian agreement to serve Norwegian businesses. What DFØ does require is that the provider applies the Norwegian rules — EHF, scheme 0192, the register check, and confirmation that whoever registers a company may sign for it (a power of attorney, or fullmakt, when they hold no signing role) — which GoRoute does on every registration.

GoRoute operates its own certified access point and SMP, so your invoices are not relayed through a third party’s infrastructure — see the API integration guide or test it free in the sandbox, where Norwegian test receivers are available.

Getting started: a realistic sequence

1. Confirm your organisation number and that it is the legal entity, not a sub-unit. This is your Peppol identity under scheme 0192.
2. Find out where you are registered today. If you are already in ELMA or with another provider and want to receive through GoRoute, that registration moves first.
3. Appoint an access point and have it register you. Registration is the provider’s obligation, not yours.
4. Connect your ERP or accounting system. Post your existing invoice data over a REST API or an existing connector — you should not have to author UBL by hand.
5. Validate before you send. Run real documents against EN 16931, the Peppol rules and the NO-R rules in a test bed first.
6. Plan for 2030 — receiving and digital bookkeeping — while you are in the code, rather than reopening it in three years.