Electronic invoice in Norway

One of Europe’s most mature e-invoicing markets with mandatory EHF format for public sector

Select a country

Overview

Norway has been sending structured invoices to the public sector over Peppol for more than a decade. On 19 June 2026 it went further: Act No. 39 amending the Bookkeeping Act (bokføringsloven) introduced a mandatory B2B e-invoicing obligation, adopted by the Storting on 8 June and sanctioned by the King eleven days later.

The design is unusually pragmatic. From 1 January 2027 you must send a structured invoice to any business customer that is already able to receive one — no more. Only from 1 January 2030 does every covered business have to be able to receive. That deliberate asymmetry means nobody is forced to build a receiving capability they do not yet have, while the network fills up from the sending side.

0192:NO:ORG

the only current identifier scheme — VAT-based schemes are deprecated

No clearance

nothing is sent to Skatteetaten, no approval code, no reporting

EHF = Peppol BIS

no separate Norwegian CIUS or national extensions

Timeline

Fourteen years of public-sector groundwork, then a B2B mandate built on top of it.

Already in force

1 July 2012

EHF becomes a contract requirement for central government

Government bodies must write an EHF invoice and credit note requirement into new contracts. The municipal sector followed from 2015.

2 April 2019

The public procurement e-invoicing regulation takes effect

Forskrift om elektronisk faktura i offentlige anskaffelser extends standard e-invoicing to all contracting authorities covered by procurement law, over the Peppol infrastructure.

19 June 2026

Act No. 39 amending the Bookkeeping Act is sanctioned

The legal basis for mandatory B2B e-invoicing and digital bookkeeping. The Storting adopted it on 8 June 2026.

Ahead

15 December 2026

Deadline for the B2C study

Skattedirektoratet must report on consumer e-invoicing, standardised electronic receipts and possible regulation of service providers. This is a reporting deadline, not the start of a mandate.

1 January 2027

The obligation to send takes effect

Bookkeeping-obligated businesses must send structured e-invoices to business customers who are registered to receive them. The three conditions all have to be met.

1 January 2030

Digital bookkeeping and mandatory receiving

Covered businesses must use a digital accounting system that receives and processes e-invoices automatically. Spreadsheets and word processors stop qualifying as primary bookkeeping tools.

The law is passed, but the detail is not. The mandatory format, the exemptions and the transitional rules are still to be set out in secondary legislation from Skattedirektoratet. The government assignment names EHF as the intended format, and exemptions are expected for very small businesses and certain financial institutions — but until the regulation is published, none of that is settled law.

B2G

Public-sector e-invoicing has been settled practice for years. Under the 2019 regulation, contracting authorities must require an electronic invoice in the contract, accept it in an approved standard format, process it electronically and use the Peppol infrastructure.

Norwegian supplierSends EHF Fakturering 3.0 over Peppol

Foreign supplierSends Peppol BIS Billing 3.0 over Peppol — no Norwegian access point required

Below EEA thresholdsEHF Billing 3.0 and Peppol BIS Billing 3.0 are the named formats

Above EEA thresholdsOther approved standard formats implementing EN 16931 are also admissible

A PDF sent by e-mail does not satisfy the B2G requirement. In practice a non-compliant invoice is rejected technically, returned to the supplier and the payment term does not start — a commercial consequence that usually bites faster than any regulatory one.

The B2B mandate

From 1 January 2027 the obligation to send applies when all three of the following are true of your customer. If any one fails, you are not obliged to send a structured invoice for that transaction.

1The recipient is a bokføringspliktig virksomhet — a business subject to the bookkeeping obligation

2The recipient is registered in ELMA or another Peppol SMP

3The recipient is technically able to receive electronic invoices

Why the asymmetry matters

Between 2027 and 2029 the duty falls on the sender only, and only towards customers already connected. There is no obligation on the buyer side to get connected until 2030. The practical effect is that your systems must be able to look up whether a given customer is reachable, and route accordingly — a per-invoice decision, not a one-off configuration.

What is outside the mandate

Sales to consumers and cash sales are excluded from the adopted act

Customers not registered to receive — you may keep invoicing them as before

Foreign suppliers that are not themselves Norwegian bookkeeping-obligated businesses are not caught by the Norwegian sending duty

Norway's banking solution eFaktura, which delivers invoices into a consumer's online bank, is a different legal and technical regime from EHF/Peppol B2B and should not be confused with it.

Because Norway is not part of the EU VAT system — the VAT Directive is not incorporated into the EEA Agreement — ViDA does not apply directly to Norway from 1 July 2030. It applies to a Norwegian group's EU subsidiary, fixed establishment or EU VAT registration, but not to a Norwegian domestic invoice or to an export from Norway.

Formats and standards

Norway is one of the cleanest implementations of the European standard in Europe, for a simple reason: it did not build a national variant on top of it.

EHF Fakturering 3.0

The Norwegian name for Peppol BIS Billing 3.0, implemented without Norwegian additions or extra rules. Peppol BIS Billing 3.0 is itself a CIUS of EN 16931.

OASIS UBL 2.1

The working syntax: Invoice and CreditNote, Peppol BIS Billing 3.0 CustomizationID and ProfileID, with VAT rules selected by the seller's country.

UN/CEFACT CII is not the everyday Norwegian syntax. An EN 16931 compliant CII invoice can have legal standing for public contracts above the EEA thresholds, but for day-to-day Norwegian B2G and B2B you should assume UBL / Peppol BIS Billing 3.0.

The 2027 format is not formally fixed yet

The adopted act defines an e-invoice technology-neutrally: an invoice that can be issued, sent and received in a structured electronic format allowing automatic processing. The binding syntax comes in the Skattedirektoratet regulation. Still open: the full list of permitted syntaxes, whether CII is admissible for domestic B2B, transitional carve-outs for EDIFACT, E2B and sector EDI, and exemptions for small businesses.

PDF

The government's explanatory memorandum is explicit: an electronic document or image file such as a PDF is not an e-invoice, because it contains no structured data an accounting system can process automatically. A PDF may accompany the XML as a visual representation, and remains usable outside the mandate and in B2C — but it does not replace EHF where a structured invoice is required. The act also requires the e-invoice to be stored in its original format, so keeping only a rendered PDF is not enough.

The Peppol model

Norway runs the standard Peppol four-corner model: the seller's system (C1) hands the invoice to the seller's access point (C2), which locates the buyer's access point (C3) via SML and SMP and delivers over AS4, and C3 passes it into the buyer's system (C4).

There are central components, but they handle addressing and discovery — not tax control. The most accurate description is a decentralised network of access points with centralised address lookup.

What Norway does not require

Sending the invoice to Skatteetaten in advance

Obtaining a clearance code or tax authorisation

Waiting for validation before the invoice reaches the buyer

Routing through a state platform as a mandatory intermediary

The validation an access point performs checks the XML against EHF and Peppol BIS technical and business rules. It is a technical check, not a fiscal approval.

No fifth corner

In Peppol CTC designs a fifth participant — the tax authority — receives transaction data from C2 or C3. Norway's adopted model has no such mandatory C5. The explanatory memorandum notes that e-invoicing could lay the groundwork for transaction-based tax reporting in future, but building that is expressly not part of the act. Norway participates in Nordic Smart Government & Business pilots around ViDA and CTC; pilots create no legal reporting duty.

Identifiers and ELMA

DFØ — the Peppol Authority

The Norwegian Agency for Public and Financial Management (Direktoratet for forvaltning og økonomistyring) governs Peppol nationally, develops EHF and represents Norway towards OpenPeppol.

ELMA — the national SMP

Elektronisk mottaker- og adresseregister, operated by the Norwegian Digitalisation Agency (Digdir). Your access point registers you there; public bodies must be in ELMA, private participants may use another Peppol SMP.

Participant identifiers

0192 — NO:ORGUse this. The nine-digit Norwegian organisation number from Enhetsregisteret, e.g. 0192:123456789

9908 — NO:ORGNRRemoved from the current code list

9909 — NO:VATDeprecated

For new Norwegian onboardings use 0192 plus the organisation number — not the VAT number with its NO prefix and MVA suffix. Public lookup that used to run directly against ELMA now goes through the Peppol Directory, but ELMA continues to operate as the SMP.

Requirements for providers

The Norwegian Peppol Authority Specific Requirements record Service Provider Accreditation as No. There is no separate national licence comparable to the Slovak digitálny poštár, and no requirement for a Norwegian legal entity, local office, local tax representative or an official electronic mailbox in order to serve Norwegian customers. A certified Peppol service provider established elsewhere in Europe can onboard Norwegian companies directly.

What the provider does still have to do:

—Hold a Peppol Service Provider Agreement, pass conformance testing and maintain a valid Peppol PKI certificate

—Verify the organisation: the Norwegian end user must be a legal entity registered in Enhetsregisteret, and the nine-digit organisation number checked against Brønnøysundregistrene

—Verify authority: the individual signing on behalf of the Norwegian company must hold signature rights or power of procuration, and the provider needs a procedure to check it

—Maintain SMP data quality: validate organisation numbers, keep entries current, deactivate participants removed from the register, keep document and process identifiers correct

—Report end-user and transaction statistics under the Norwegian PA and OpenPeppol procedures

—Support the applicable EHF specifications and Norwegian validation rules

A single centralised SMP is not mandatory for private businesses — the Norwegian PASR records No for that too. Public organisations must be registered in ELMA. Note that the Ministry of Finance included regulation of e-invoicing service providers in the follow-up study, so additional provider duties may be proposed after December 2026.

Archiving

Under the Bookkeeping Act, primary accounting documentation — invoices included — must be retained for five years after the end of the financial year, with shorter periods for certain secondary documentation and longer ones in specific sectors.

The new act requires the electronic invoice to be kept in its original format — the XML, not a rendering of it

Storing only a visualised PDF instead of the original XML will not satisfy the requirement

Records must remain accessible and readable and be producible on inspection

This is the requirement most often missed in a first implementation. Plenty of accounting systems display the invoice and quietly discard the source file; from 2027 that is a compliance gap, and from 2030 it sits inside a broader digital bookkeeping obligation.

Enforcement

The act sets no fixed fine per wrongly formatted invoice. Because the duty sits inside the Bookkeeping Act, it is enforced through the general bookkeeping and tax machinery — which is escalating rather than fixed.

01 Skatteetaten issues a bokføringspålegg — a binding order to correct the breach

02 A deadline for compliance is set

03 If the deadline passes, a daily tvangsmulkt — a coercive fine — accrues until the breach is fixed

The design matters: a single mis-sent PDF is not the target. Systematically continuing to send PDFs after an order from the tax authority is, and the amount compounds daily until you stop.

Criminal liability

Serious breaches of bookkeeping rules can qualify as an accounting offence: up to two years imprisonment or a fine in ordinary cases, up to six years for gross breaches. These are the general maxima for material accounting violations — scale, systematic conduct, intent, consequences and concealment are what matter, not an isolated formatting error.

Is an e-invoice the only basis for deducting VAT?

No. The right to deduct input VAT rests on two things: that the purchase relates to VAT-liable business activity, and that the input VAT is evidenced by proper sales documentation containing the statutory particulars. Where an invoice has material defects, the deduction can be refused or postponed until it is corrected.

Norwegian practice does not treat every minor formal defect as fatal where the substantive conditions are met and the supplier is genuinely VAT-registered. So a PDF sent instead of a required EHF is a breach of the invoicing and bookkeeping rules — but it does not automatically destroy the buyer's deduction. In practice the safer course for the buyer is to require a corrected structured invoice before claiming.

How we help

Norway needs no local licence — what it needs is correct identifiers, correct validation and a reachability check on every invoice. As a certified Peppol Access Point we cover:

Sending and receiving via a certified Peppol Access Point — no Norwegian entity required

EHF Fakturering 3.0 and Peppol BIS Billing 3.0 in UBL 2.1

Onboarding on 0192:organisation-number with Enhetsregisteret verification

SMP registration and upkeep of participant data

Recipient reachability lookup before dispatch — the check the 2027 rule turns on

Validation against EN 16931 and Norwegian VAT rules before sending

Retention of the original XML, not just a rendering

Integration via API, SFTP and CSV, with ERP and IDoc source data

Frequently asked questions

Do I have to send e-invoices to every Norwegian business customer from 2027?

No — only to those who can already receive them. All three conditions must hold: the customer is a bookkeeping-obligated business, is registered in ELMA or another Peppol SMP, and is technically able to receive. Customers outside that set can still be invoiced as before, until the receiving obligation arrives on 1 January 2030.

Which format will actually be mandatory?

The act itself is technology-neutral — it requires a structured electronic format allowing automatic processing. The binding syntax will be set in a Skattedirektoratet regulation, and the government assignment named EHF as the intended format. EHF Fakturering 3.0 is therefore the sensible thing to build for, but the final regulation has not been published, so the complete list of permitted syntaxes and the transitional carve-outs for EDIFACT, E2B and sector EDI are not yet settled.

Does Norway send invoice data to the tax authority?

No. There is no clearance, no fifth corner, no obligation to send a copy to Skatteetaten and no real-time or near-real-time VAT reporting. The new act does not introduce one. The explanatory memorandum acknowledges that e-invoicing could form a basis for transaction-based reporting later, but developing such a regime is expressly not part of the adopted law.

Does ViDA apply to Norway from 2030?

Not directly. Norway is not in the EU VAT system and the VAT Directive is not part of the EEA Agreement, so ViDA introduces no digital reporting for Norwegian domestic invoices, no requirement for exports from Norway and no CTC on imports. It does apply to a Norwegian group's EU subsidiary, EU fixed establishment or EU VAT registration — that is EU law applying to activity in the EU, not to Norway.

Can a foreign Peppol access point serve Norwegian clients?

Yes. A service provider signs its agreement with the Peppol Authority of the country where it is established and may then serve customers in other jurisdictions. Norway records Service Provider Accreditation as "No", so no separate Norwegian agreement, entity, office or representative is needed. The provider must still meet the Norwegian requirements when serving Norwegian participants — organisation verification, signature-rights checks, SMP data quality and EHF validation rules.

Is there a B2C mandate coming?

Not yet, and nothing is decided. Consumer and cash sales are excluded from the adopted act. The Ministry of Finance asked Skattedirektoratet to study mandatory consumer e-invoices, standardised electronic receipts and possible regulation of service providers, with the study due by 15 December 2026. That is a deadline for a report, not a mandate date.

Which identifier should I register my Norwegian customers under?

EAS 0192 (NO:ORG) with the nine-digit organisation number from Enhetsregisteret — for example 0192:123456789. Scheme 9908 has been removed from the current code list and 9909 (NO:VAT) is deprecated, so do not build new integrations on the VAT number with its NO prefix and MVA suffix.

What happens if we keep sending PDFs?

There is no per-invoice fine. Skatteetaten would issue a bookkeeping order with a deadline, and if that passes, a daily coercive fine accrues until the breach is remedied. Serious and systematic accounting breaches can in principle be criminal, with maxima of two years, or six for gross cases — but that is aimed at material misconduct, not at formatting. For B2G the practical consequence arrives sooner: the invoice is rejected and the payment term does not start.

Summary

Norway has moved from a mature B2G system to a legislated B2B mandate without changing its architecture. Peppol four-corner, EHF as an unmodified Peppol BIS Billing 3.0, UBL 2.1, no clearance, no tax reporting, no national access point licence. Companies already exchanging over Peppol have most of the work behind them.

Two dates matter: 1 January 2027 for the duty to send to customers who can receive, and 1 January 2030 for digital bookkeeping and the duty to receive. In between, the obligation is conditional — which makes recipient lookup, not format conversion, the interesting engineering problem.

The open item is the Skattedirektoratet regulation that fixes the format, the exemptions and the transitional rules. Build for EHF, register on 0192, keep the original XML — and watch for that regulation before treating any exemption as available.

Resources

EHF Billing 3.0 — the official specification DFØ's technical documentation, including the confirmation that no Norwegian extensions apply Forskrift om elektronisk faktura i offentlige anskaffelser The B2G regulation on Lovdata, with the approved formats and threshold rules Bokføringsloven — the Bookkeeping Act The act the new e-invoicing obligation was written into, with the retention rules ELMA — the electronic recipient register Digdir's page on the national SMP and how recipients are registered Brønnøysundregistrene Verify organisation numbers and signature rights in Enhetsregisteret European Commission — Norway eInvoicing country sheet Confirms EN 16931 adoption and the absence of a national CIUS Peppol Directory Check whether a Norwegian business partner is reachable on the network

Need support with e-invoicing requirements?

As a certified Peppol Access Point we provide solutions for sending and receiving electronic invoices securely across Europe — including format conversion, validation and integration with national systems.

Start your free trial