Skip to content
Back to blog
NorwayPublished 13 October 20269 min read

Norway 2027: the mandate is law, and it arrived a year early

Norway’s B2B e-invoicing obligation starts 1 January 2027, with digital bookkeeping from 2030. What EHF requires, how ELMA works, who is in scope including foreign businesses, and how to prepare.

For most of 2025, Norway’s B2B e-invoicing mandate was a 2028 problem. In March 2026 the Ministry of Finance pulled it forward a full year. On 1 June 2026 the Storting passed the amendments to the Bookkeeping Act, and the law was sanctioned on 19 June.

It is no longer a proposal. From 1 January 2027, businesses with bookkeeping obligations in Norway must issue invoices to other bookkeeping-liable businesses in a structured electronic format. A PDF attached to an email does not satisfy it.

If you have been tracking Norway as a 2028 item, you are fourteen months from a mandate rather than twenty-six.

The two dates

  • 1 January 2027 — sending. Bookkeeping-liable businesses must issue structured e-invoices for domestic B2B supplies.
  • 1 January 2030 — receiving and digital bookkeeping. Businesses must use an electronic accounting system capable of receiving and processing e-invoices automatically. This is the heavier obligation of the two, and the three-year gap is deliberate: it gives you time to change accounting systems rather than just invoicing systems.

The sequencing is unusual. Most mandates require receiving capability first and sending later, on the reasonable theory that you cannot send to someone who cannot receive. Norway inverted it, because the receiving side is bundled into a much bigger digital-bookkeeping reform.

Practically, that gap creates a transitional question: what happens when you are obliged to send and your customer is not yet obliged to receive? The design intent is that the obligation bites where the buyer is reachable — that is, registered in ELMA. Detailed regulations were being developed by the Directorate of Taxes with a delivery deadline of 15 December 2026, so the precise handling here is the thing to watch between now and year end.

Who is in scope

Everyone with bookkeeping obligations in Norway, regardless of where the business is established. A foreign company with Norwegian bookkeeping obligations — including certain VAT-registered foreign businesses — is expected to comply on the same terms as a Norwegian entity.

That is the sentence most non-Norwegian finance teams miss. “We do not have a Norwegian subsidiary” is not the test. The test is whether you have bookkeeping obligations there.

Foreign businesses without Norwegian bookkeeping obligations may use e-invoicing voluntarily but are not compelled to. And the mandate does not apply when a Norwegian business invoices a foreign customer for exports.

Exemptions have been signalled for the very smallest operators: sole proprietorships without accounting obligations and turnover below NOK 50,000 (roughly €4,500) are expected to be outside the reception requirement.

The format: EHF over Peppol

Norway’s national format is EHF (Elektronisk Handelsformat), version 3.0 or newer. EHF 3.0 is built on Peppol BIS Billing 3.0 and complies with EN 16931. Exchange runs over the Peppol network.

This is genuinely good news, and it is worth saying plainly rather than manufacturing alarm. If you already produce Peppol BIS 3.0 for Belgium, or XRechnung for Germany, or NLCIUS for the Netherlands, you are producing something structurally very close to EHF. Norway did not invent a national XML schema the way Italy did. It restricted the European one.

The delta is a CIUS, not a rewrite.

ELMA

ELMA is Norway’s national e-invoicing address register — the Peppol SMP lookup layer for the Norwegian market. Obligated businesses are expected to register in ELMA so that counterparties can find them and route to them.

Two things follow.

  • Registration is a prerequisite, not an afterthought. You can produce perfect EHF and still be unreachable.
  • Reachability is how you determine whether an invoice must go electronically. Before you send, you look up whether the recipient is registered. That lookup has to be part of your invoicing process, not a manual check.

How participant lookup works across Peppol in general — EAS codes, SMP, SML — is a topic in its own right; the mechanics in Norway are the standard ones, with ELMA as the national register behind them.

The one advantage Norway has

Norway has mandated e-invoicing to the public sector for years, over Peppol, in EHF. The result is a market where most accounting and ERP software already speaks the format, most service providers already operate access points, and a large share of businesses have sent an EHF invoice at some point.

If you already invoice Norwegian public bodies, you have most of the infrastructure. What you likely do not have is coverage of your entire B2B customer base, ELMA lookup wired into your process, and a plan for the counterparties who are not yet reachable.

That is a smaller project than a from-scratch mandate. It is not a zero project.

What to do now

  • Establish whether you have Norwegian bookkeeping obligations. Do this per legal entity. Foreign companies are caught if the obligation exists.
  • Check your ELMA registration — that you are in it, and that your details are current. Build reachability lookup into the send process, so the decision to send electronically is made by the system rather than by a person.
  • Confirm your provider’s EHF version support. The mandate specifies 3.0 or newer; EHF has been revised since and profiles do get retired.
  • Start the 2030 conversation now if you are changing accounting systems anyway. Digital bookkeeping is the larger reform, and system replacement cycles are longer than three years.
  • Watch for the detailed regulations. The Directorate of Taxes was due to deliver draft regulations by 15 December 2026, covering format specifics and exemptions. That document will settle several open questions.

Where MyInvoice fits

We take what your ERP exports — SAP IDoc INVOIC02, EDIFACT, CSV, Excel, or UBL you already produce for another market — and emit EHF-compliant output validated against XSD and Schematron before transmission. Sending and receiving run over Peppol through our access point partner:

curl -X POST https://api.myinvoice.llc/v1/convert \
  -H "X-API-Key: ek_live_..." \
  -F "[email protected]" \
  -F "format=csv" \
  -F "profile=ehf-3"

If you are already live in another Peppol market, tell us and we will be straight with you about how much of Norway is genuinely new work. Usually it is less than a vendor would like it to be.

Try the sandbox — send a sample invoice, get EHF output and a validation report back

Related reading

EHF is a restriction of Peppol BIS 3.0, which is itself a restriction of EN 16931 — so the two layers underneath are worth understanding.

Peppol BIS 3.0 and the Peppol network explained

The European standard that EHF, XRechnung and NLCIUS all narrow down.

What is EN 16931?

Norway is outside the EU, but its 2030 digital-bookkeeping date sits alongside ViDA’s cross-border reporting; if you trade across that border, both will apply to you.

What is ViDA?

General information, not tax or legal advice. Norwegian secondary regulations were still in development at the time of writing — check current requirements with Skatteetaten before making compliance decisions.

Read the API docs