Is e-invoicing mandatory between businesses in Norway?

Yes, for issuing, from 1 January 2027. The Storting adopted the amendments to the Bookkeeping Act on 8 June 2026 and they were sanctioned in the Council of State on 19 June 2026 as LOV-2026-06-19-39. The duty to receive an e-invoice and the requirement to keep the books in an electronic accounting system take effect on 1 January 2030. Many English-language trackers still record Norway as having no B2B requirement; that was correct only until June 2026.

Who is caught by the Norwegian e-invoicing duty?

Every bokføringspliktig — every person or entity subject to the Norwegian bookkeeping obligation — selling to another bokføringspliktig. This includes foreign companies that are bokføringspliktige in Norway, so a foreign parent with a Norwegian branch or subsidiary should not assume it is outside the scope. Sales to consumers are not covered.

Which format will be mandatory in Norway?

It is not finally settled. The Act requires a structured electronic invoice format, but the detailed format requirements are set by regulation. The Directorate of Taxes was to deliver proposals for format requirements and exemption criteria by 15 December 2026. EHF 3.0 over Peppol is the expected outcome but is not confirmed in regulation, so architecture should not be locked to it.

Is there real-time reporting or clearance to the Norwegian tax administration?

No. Norway uses the Peppol four-corner model: decentralised and post-audit. There is no clearance, no real-time reporting and no central invoice archive, which is a material difference from Poland, Slovakia and Italy. SAF-T Financial is submitted on request during an audit rather than periodically.

What does it mean that an e-invoice must be kept in its original format?

Section 13 second paragraph of the Bookkeeping Act requires the electronic invoice to be retained in the form in which it was issued or received. A central archive that normalises documents into a house schema, converts them to PDF, or stores only extracted fields does not satisfy this even if no information is lost. For a group running one archive across several countries, this is the requirement most likely to be missed, because normalisation is precisely what the integration layer is built to do.

Norway's e-invoicing mandate starts 1 January 2027

When does the duty start, and what exactly starts?

From	What applies
1 July 2026	Certain other provisions of the Act.
1 January 2027	Duty to issue sales documentation in an electronic invoice format to other bokføringspliktige.
1 January 2030	Duty to receive e-invoices, and mandatory digital bookkeeping — the books must be kept in an electronic accounting system.

The split is unusual and worth noticing: the issuing duty arrives three years before the receiving duty. In practice, from 2027 you must send e-invoices to recipients who are under no obligation to be able to accept them. How that is handled operationally — in particular whether the duty is conditioned on the recipient being registered in ELMA — is one of the questions the regulations are to settle.

The amendments

Bookkeeping Act section 10, second paragraph — sales documentation to other bokføringspliktige is to be issued in an electronic invoice format, and correspondingly received in that format.
Section 7, new fourth paragraph — bookkeeping is to be carried out in an electronic accounting system, unless the ministry determines otherwise.
Section 13, second paragraph — an electronic invoice is to be retained in its original format.

Who is caught, and is a foreign parent's Norwegian entity in scope?

All bokføringspliktige — those subject to the bookkeeping obligation: private and public limited companies, state enterprises, financial undertakings, securities funds, certain cooperatives and others. Foreign companies that are bokføringspliktige in Norway are also covered. Sales to consumers fall outside.

For a group finance function, that last sentence is the whole scoping question, and it does not map onto the tests used elsewhere. The trigger is bokføringsplikt, not VAT registration and not Norwegian incorporation. A branch, a permanent establishment or a foreign entity carrying on taxable activity in Norway can be bokføringspliktig without being a Norwegian company. Groups that scope e-invoicing projects off the VAT registration list will therefore miss entities, and groups that scope off the list of Norwegian-incorporated subsidiaries will miss branches. Settle it entity by entity and write down the reasoning, because the same determination decides the 2030 receiving duty and the digital bookkeeping requirement.

There is a second scoping question the Norwegian-language material does not need to raise, and a group does: intragroup invoicing. The duty is framed as applying to sales documentation issued to another bokføringspliktig, and it draws no distinction between a third-party customer and a sister company. Where two entities in the group are each bokføringspliktige in Norway, the intercompany invoices between them appear on the face of the provision to be within scope. Groups that treat intercompany billing as an internal process running on a different system from external AR should establish the position before the regulations arrive, because it is the flow most likely to have been left out of the project.

Proposed exemptions — not final

The following are proposed but are to be set by regulation and are not final: sole proprietorships with turnover below NOK 50,000 that are not otherwise subject to bookkeeping or VAT obligations; bankruptcy estates that do not carry on business; and possible transitional relief for small businesses.

Why are the implementing regulations not out yet?

The Act and the date are settled. The regulations under the bookkeeping regulation have not been made. The Directorate of Taxes was tasked with delivering proposals for format requirements and exemption criteria by 15 December 2026.

That means the following are not confirmed:

which format will specifically be required — EHF 3.0 over Peppol is the expected outcome, but it is not in a regulation yet;
whether the duty is conditioned on the recipient being registered in ELMA;
the final exemptions for small businesses.

One thing the Act does settle, before any regulation: it requires a structured electronic invoice format. A PDF is not one, even when it is generated automatically and emailed. The criterion is machine processability, not electronic delivery — the same distinction that catches out organisations which believe they already invoice electronically because nothing is printed. Scanned paper and image files fail for the same reason.

For planning, this means you can safely build towards Peppol and EHF but should avoid locking the architecture to details that are not yet fixed. The regulations land roughly two weeks before the duty bites — that is very little time, and it argues for starting now rather than waiting for them. It also argues for keeping the format mapping behind an interface, so that a change in December 2026 is a configuration change rather than a rebuild in the last fortnight of the year.

What technical model does Norway use?

Norway uses the Peppol four-corner model: decentralised and post-audit. There is no clearance, no real-time reporting and no central invoice archive — a material difference from Poland, Slovakia and Italy, and one that changes what an implementation actually costs.

EHF (Elektronisk handelsformat, UBL-based) domestically
Peppol BIS Billing 3.0 cross-border
ELMA as the address register — Norway's Peppol SMP, with roughly 360,000 registered recipients

Public sector

B2G has been mandatory since 2 April 2019 under the regulation on electronic invoicing in public procurement. Suppliers must send e-invoices for public contracts above NOK 100,000 excluding VAT. Format: EHF Billing 3.0 / Peppol BIS Billing 3.0. The responsible body is DFØ.

SAF-T

SAF-T Financial is still delivered on request through Altinn during an audit, not periodically. Version 1.30 applies to 31 December 2026; version 1.40 is mandatory from 1 January 2027 and can be adopted already. Same date as the e-invoicing duty — worth combining into one project.

What does a group finance function have to do differently from a domestic filer?

Five differences are worth designing for.

The original-format rule collides with a central archive. Section 13 second paragraph requires the e-invoice to be kept in its original format. A group archive that normalises every document into one house schema — which is exactly what a shared integration layer is built to do — does not satisfy this, even though no content is lost. The fix is architectural and cheap if made early: keep the transmitted artefact alongside the normalised record, and test it by retrieving a stored invoice and comparing it byte for byte with what was sent.

The duty attaches to the Norwegian entity, not to the shared service centre. Where invoices are issued centrally by a European AR function, the obligation still sits with the bokføringspliktig Norwegian entity. Decide explicitly who produces the evidence and how quickly. It is an intercompany control question before it is a technical one.

The 2027–2030 asymmetry has to be modelled, not assumed away. From 2027 you must issue while the recipient has no duty to be able to receive. The process must tolerate a counterparty who cannot be resolved in Peppol without stopping invoicing — and without becoming a silent failure that first surfaces at reconciliation, which for a group means at month-end close in a different country.

Retries create duplicates and nobody will tell you. A timeout does not mean the invoice did not arrive. Without a durable operation identifier assigned before the first attempt, a retry produces a second document. In a four-corner model there is no central authority to flag the duplicate — the customer finds it.

Two Norwegian changes land on the same day. The issuing duty and SAF-T 1.40 both start on 1 January 2027 and both touch ledger extraction. Running them as one change is materially cheaper than running them as two, and it is the only version of the plan that survives regulations arriving on 15 December 2026.

How does this compare with the neighbouring regimes?

Norway is now ahead of several EU member states on B2B, which is not where most group timetables place it. Estonia, by contrast, has no general B2B mandate: what exists there is a duty to issue an e-invoice on the buyer's request where the buyer is registered as an e-invoice recipient. A group running one Nordic-Baltic e-invoicing programme should not apply a single scoping rule across both.

Separately, and regardless of national timetables, Council Directive (EU) 2025/516 introduces digital reporting for cross-border intra-EU B2B transactions from 1 July 2030. That applies to the group's EU entities on its own timetable. Norway, outside the EU VAT system, is not on that clock — so the Norwegian date and the EU date are separate deadlines that happen to be near each other, not one programme.

How should you prepare before the regulations arrive?

Establish whether the entity is bokføringspliktig and therefore in scope — per entity, including branches.
Obtain Peppol access through an access point provider and register the entity in ELMA.
Build towards EHF 3.0 / Peppol BIS Billing 3.0 but keep the format layer separate until the regulations arrive in December 2026.
Verify that the archive preserves the invoice in its original format, byte for byte.
Introduce idempotency control: a retry after a timeout must not create a new document.
Handle the case where the recipient is not in ELMA — this will be routine in the 2027–2030 window.
Take SAF-T 1.40 into the same project; it is mandatory from the same date.
Define approval thresholds for automated issuing above given amounts.

And what about NIS2?

It does not apply in Norway. The NIS2 directive is not incorporated into the EEA Agreement; it is marked EEA-relevant, but there is no EEA Joint Committee decision. What applies is the digitalsikkerhetslov, in force 1 October 2025, implementing NIS1 — seven sectors, registration with NSM and the sector authority, and notification of significant incidents within 24 hours. The practical consequence is that a Norwegian entity is not subject to NIS2 as such, while a group company established in an EU member state is, and Norwegian suppliers are routinely drawn in by contract through EU customers' supply chain duties. The full analysis is under why NIS2 does not apply in Norway.

The EU AI Regulation is likewise not incorporated into the EEA Agreement. A draft Norwegian AI act went to consultation on 30 June 2025; Nkom is proposed as coordinating supervisory authority and Digdir is to run the regulatory sandbox through KI Norge. After the EU amending regulation of July 2026 the government announced on 4 August 2026 a further consultation round in autumn 2026, with the ambition of a proposition in spring 2027.

In practice

BarzelVault applies policy and approval thresholds before an operation executes and issues a signed audit receipt for each one, which is what answers the question that follows the format question: who authorised this document. BarzelOps runs the cross-system workflow with durable state and approval checkpoints where issuing spans an ERP, an access point and an archive.

How Barzel applies here

Frequently asked questions

Is e-invoicing mandatory between Norwegian businesses?

Yes — an issuing duty from 1 January 2027 under LOV-2026-06-19-39, adopted 8 June 2026 and sanctioned 19 June 2026. The duty to receive and mandatory digital bookkeeping follow on 1 January 2030.

Who is caught?

Every bokføringspliktig — every party subject to the Norwegian bookkeeping obligation — selling to another, including foreign companies that are bokføringspliktige in Norway. B2C is excluded.

Which format will be mandatory?

Not finally determined. EHF 3.0 over Peppol is expected, but the regulation follows the Directorate of Taxes' proposals due by 15 December 2026, and format requirements and exemptions were not fixed as at the position date.

Is there real-time reporting to the tax administration?

No. Norway uses a post-audit model with no clearance and no central archive. SAF-T is delivered on request.

What does retention in the original format require?

That the invoice is kept as issued or received. An archive that normalises, converts or stores only extracted fields fails the requirement even where nothing is lost.

Does NIS2 apply in Norway?

No. The directive is not incorporated into the EEA Agreement. The digitalsikkerhetslov, in force 1 October 2025, implements NIS1.

The control has to run before the invoice becomes irreversible.

An accepted structured invoice can be corrected but never deleted, and from the penalty date every defect has a price. Barzel puts the approval threshold, the duplicate check and the signed record in front of submission, so the process can be defended on the day an auditor or the tax authority asks.

94 days leftMandatory e-invoicing in Norway from 1 January 2027

BarzelVault

The AI action firewall: decide what an agent may do before it does it.

Approval thresholds and policy checks enforced before execution; human approvals that expire and escalate.
Cryptographically signed audit receipts: trigger, inputs, policy version, approver, outcome.
Credential isolation, spend and action limits, and an emergency kill switch.

Free tier: 10,000 calls a monthPaid plans from $199 a monthLive on MCPize

Start free Ask by email Product page Documentation

BarzelOps

Governed workflow automation across the systems that run the business.

Durable, idempotent execution: a timeout is retried once, never filed twice.
Human approval checkpoints that pause the workflow and resume it.
Isolation per entity or client, signed evidence receipts and a portable manifest; HubSpot, Xero, Gmail, Google Drive and Slack.

Free tier: 100 calls a dayPaid plans from $19 a monthLive on MCPize