Mandatory e-invoicing in Norway 2027: the complete guide
From 1 January 2027, Norwegian businesses must send invoices to each other electronically. This is no longer a proposal: parliament passed the amendments to the Bookkeeping Act on 1 June 2026 and the law was sanctioned on 19 June (LOV-2026-06-19-39, cf. Prop. 44 L (2025–2026)).
It is worth being precise about what applies when, because the two obligations do not arrive together:
- 1 January 2027 — the obligation to send. Businesses with bookkeeping obligations must issue invoices in electronic format (EHF) to other such businesses.
- 1 January 2030 — the obligation to receive, together with the requirement for digital bookkeeping. From then you need an electronic accounting system that receives and processes e-invoices.
Commencement itself is by royal decree — the statute says the law applies "from the time the King determines" — but the dates above are the ministry's stated plan as set out in the proposition.
This guide covers what the requirement actually means, who it applies to, what separates EHF from a PDF attached to an email, and how to get into position without launching a large IT project.
Key takeaways
- • EHF/PEPPOL becomes mandatory for B2B in Norway on 1 January 2027
- • The deadline was brought forward a year from the original 2028
- • A PDF on email does not count as an electronic invoice
- • You need an access point — not necessarily a new ERP
- • Anyone already invoicing the public sector has most of it in place
What the requirement actually says
Today EHF is mandatory only towards the public sector. If you trade with the state, a county or a municipality, you already send EHF over PEPPOL. What changes is that the requirement extends to all invoicing between Norwegian businesses.
In practice you must be able to send invoices in a structured electronic format by 2027. You have three more years on the receiving side — but as we come back to below, receiving is where the gain actually sits, and your customers will ask for it long before 2030.
A PDF is not an electronic invoice
This is the most common misunderstanding. A PDF attached to an email is a picture of an invoice. A human can read it; an accounting system cannot process it without interpretation, scanning or manual keying.
EHF is structured data. Invoice number, organisation number, lines, VAT codes and amounts sit in defined fields the receiving system reads directly. That is why the requirement makes sense: it is the structure, not the digital format in itself, that removes the manual work.
Who it applies to
The requirement lands broadly. Every Norwegian business invoicing other Norwegian businesses has to deal with it, regardless of industry and in practice regardless of size. This is not a rule that only reaches large groups.
If you already supply the public sector, most of the work is done. You have an access point, you have EHF configured, and extending to B2B is more a question of volume than of new technology.
What you need
To send and receive EHF over PEPPOL you need access to the network through an access point. The access point is the connection between your systems and the PEPPOL network — roughly what an internet provider is between your office and the internet.
- An access point: either bought as a service or included in your procurement or accounting platform
- Correct ERP setup: organisation numbers, VAT codes and chart of accounts mapped to the EHF fields
- A plan for receiving: who approves, how invoices match against orders, what happens to exceptions
Note that you do not necessarily need a new ERP. In most cases this is an integration question rather than a system replacement. Read more about ERP integration and what PEPPOL is.
What to do now
The deadline is some way off, but anyone who waits until autumn 2026 will be competing for the same consulting hours as everyone else. The order below is the one we recommend.
1. Map where you stand
Do you send EHF today? To whom? Do you receive EHF, or does everything arrive as PDF? The answer decides whether this is a small extension or a real change.
2. Check what your ERP supports
Most modern Nordic ERP systems handle EHF either natively or through integration. Visma, SAP, Unit4, Xledger, Tripletex and PowerOffice all do. The question is not whether, but how.
3. Choose an access point
Look for a DFØ-approved access point with operations and monitoring included. An access point approved for the public sector handles B2B without further work.
4. Take receiving at the same time as sending
Many solve sending first because that is what customers ask for, and postpone receiving. That is a missed opportunity: the gain sits on the receiving side. Automatic matching against order and goods receipt is what actually removes hours.
💡 The gain is bigger than the requirement
The requirement is about format. The value sits in what becomes possible once invoices are structured: automatic three-way matching, shorter processing time and fewer reminders. Businesses on PEPPOL report a 70–90 % reduction in time spent handling invoices.
What happens if you are not ready
The practical consequence arrives before the formal one. Your customers have to meet the requirement too, and from 2027 they will increasingly demand EHF from their suppliers. A supplier still sending PDFs becomes an exception that has to be handled by hand — and exceptions are expensive.
The experience from the public-sector transition is clear: businesses that were ready in good time used the change to automate. Those who waited used it to put out fires.
Are you ready for 2027?
Vieri is a DFØ-approved PEPPOL access point. We will walk through where you stand today and what concretely needs to be in place — without it becoming an IT project.
Book a review →
