What section 4 says
The regulation splits the question in two. In the Norwegian text:
«Godkjente standardformater for fakturaer knyttet til kontrakter under EØS-terskelverdi er EHF (Elektronisk handelsformat) fakturering versjon 3.0 eller nyere og PEPPOL BIS (PEPPOL Business Interoperability Specification) Billing v3.0 eller nyere.
Godkjente standarder for fakturaer knyttet til kontrakter over EØS-terskelverdi er EHF fakturering versjon 3.0 eller nyere, PEPPOL BIS Billing v3.0 eller nyere og andre godkjente standardformater som implementerer den europeiske normen for elektronisk faktura (EN16931).»
In English: for contracts below the EEA threshold the approved standard formats are EHF invoicing version 3.0 or newer and Peppol BIS Billing v3.0 or newer. For contracts above the EEA threshold they are EHF 3.0 or newer, Peppol BIS Billing v3.0 or newer, and other approved standard formats implementing EN 16931.
| Contract value | Formats the regulation approves |
|---|---|
| Below the EEA threshold | EHF invoicing 3.0+ or Peppol BIS Billing 3.0+. Those two only. |
| At or above the EEA threshold | EHF 3.0+, Peppol BIS Billing 3.0+, or any other approved standard format implementing EN 16931. |
The third paragraph of section 4 adds that Digitaliseringsdirektoratet is to publish links to the approved formats on its own pages, as part of the reference catalogue of IT standards that are mandatory or recommended for the public sector. The authoritative list therefore sits outside the regulation, and can change without the regulation changing.
Why the smaller contracts have the narrower choice
The reason is on the face of the instrument. The regulation's EEA note records that it implements Directive 2014/55/EU, which obliges contracting authorities to receive and process invoices conforming to the European standard. Above the threshold, Norway cannot refuse a compliant EN 16931 invoice. Below it, Norway is outside that obligation and has chosen to be stricter. That is the natural reading of the split rather than something the regulation states, but it is the only reading that makes the asymmetry coherent.
The practical consequence runs the other way from the intuition. A foreign supplier bidding for a large Norwegian public contract may invoice in its own EN 16931 format. The same supplier on a small contract must produce EHF or Peppol BIS. Projects scoped around the large contracts tend to discover this on the small ones.
The threshold itself moved on 1 July 2026
Section 2 of the regulation does not state a value. It says the regulation applies to invoicing connected to procurements covered by the Procurement Act, and to contracting authorities as set out in that Act's section 2. The number therefore lives in the Act, not the regulation.
Section 2 of anskaffelsesloven, as amended by lov 6. mars 2026 nr. 8 and in force from 1 July 2026, now applies to contracts with an estimated value equal to or exceeding NOK 500,000 excluding VAT. The figure was previously NOK 100,000.
This is worth saying plainly because the government's own recent preparatory work carries the old number. Prop. 44 L (2025–2026), dated 20 March 2026, describes the state sector position as mandatory e-invoicing for procurements worth «minst 100 000 kroner ekskl. merverdiavgift». That description was written before the new threshold took effect and was accurate when drafted. Secondary material published in 2026 and sourced from that proposition will reproduce the superseded figure. Check the Act, not the commentary.
Who the duty actually falls on
This is the point most summaries get backwards. The regulation does not order suppliers to send EHF. It orders the contracting authority to require it:
«Oppdragsgiveren skal i sine kontrakter stille krav om bruk av elektronisk faktura i godkjent standardformat.»
The authority shall, in its contracts, impose a requirement to use an electronic invoice in an approved standard format. A supplier's obligation is therefore contractual in form, flowing from the clause the authority is obliged to insert. That matters when you are reading a contract that is silent, or that names a format the regulation does not approve: the question becomes one of contract, and of the authority's own compliance, rather than of direct regulatory breach by the supplier.
The enforcement mechanism is your payment clock
Section 5's second paragraph is the operative sanction, and it is more pointed than a penalty would be:
«Dersom leverandøren ikke etterkommer krav om bruk av elektronisk faktura stilt i medhold av første ledd, kan oppdragsgiveren holde tilbake betaling inntil elektronisk faktura i godkjent standardformat leveres. Oppdragsgiveren skal uten unødig opphold gi melding om dette. Dersom slik melding er gitt, løper opprinnelig betalingsfrist fra tidspunktet elektronisk faktura i godkjent standardformat er levert.»
If the supplier does not comply, the authority may withhold payment until an electronic invoice in an approved standard format is delivered. The authority must give notice without undue delay. Where such notice has been given, the original payment deadline runs from the time the compliant invoice is delivered.
So a wrong-format invoice does not earn a late-payment claim. It resets the clock. Thirty days from a corrected submission in week six is week ten, and the supplier has no interest claim for the gap, because the deadline never started. For a business with a working-capital model built on public-sector receivables, the format question is a cash-flow question.
The rest of section 5
- The authority must be able to receive an electronic invoice in standard format through the Peppol network.
- The authority must process invoices electronically.
- The authority must be able to report to Direktoratet for forvaltning og økonomistyring how many invoices it receives in total and how many in an approved standard format.
What counts as an electronic invoice here
Section 3 defines it, and the definition is about capability rather than file type:
«Med elektronisk faktura menes betalingskrav som er utformet, oversendt og mottatt elektronisk fra fakturautsteder til fakturamottaker, og som kan behandles automatisk i fakturamottakers økonomisystem.»
A payment claim drawn up, transmitted and received electronically from issuer to recipient, and capable of being processed automatically in the recipient's accounting system. A PDF emailed to an invoice inbox satisfies the first half and fails the second.
Two carve-outs worth knowing
Confidential content (section 6). Where the invoice or the material behind it contains information subject to a statutory duty of confidentiality and there would be a risk of disclosure, the e-invoice requirement may be departed from — unless satisfactory technical security solutions exist that preserve confidentiality. The carve-out is conditional on the absence of a technical answer, not on the sensitivity alone.
Which procurements (section 7). The regulation came into force on 2 April 2019 and applies to invoicing connected to procurements initiated after that date. A procurement is initiated when it is announced; one that is not announced is initiated when the authority has sent a request to one or more suppliers to register interest or submit a tender. Long-running framework arrangements predating April 2019 therefore need checking against their own initiation date rather than against the invoice date.
None of this settles the business-to-business question
Norway now has an adopted statutory duty to issue electronic invoices between parties subject to the bookkeeping obligation. It names no format.
The amendment to the Bookkeeping Act (section 10, second paragraph) requires that documentation for sales of goods and services to other bokføringspliktige be issued «i elektronisk fakturaformat, jf. § 3 nr. 3». Section 3 number 3 then defines the concept:
«elektronisk faktura: et salgsdokument som kan utstedes, sendes og mottas i et strukturert, elektronisk format, som er egnet for automatisert behandling i regnskapssystemet.»
A sales document capable of being issued, sent and received in a structured electronic format suitable for automated processing in the accounting system. That is a category, not a specification. The Act then hands the specification to the ministry:
«Departementet kan i forskrift fastsette ytterligere krav til dokumentasjonens format og kan i forskrift eller enkeltvedtak gjøre unntak fra kravene i annet ledd om elektronisk fakturaformat.»
As at the date on this page, no Norwegian regulation names a format for business-to-business invoicing. Anyone who tells you Norway will require EHF between businesses from 2027 is describing a commercial expectation, not a rule. It is a reasonable expectation — EHF and Peppol BIS are the only formats Norwegian law names anywhere, and the ministry drafting the regulation is drafting against that estate — but the distinction matters if you are writing a contract clause, a system requirement or a compliance paper that has to be defensible later.
For what the business-to-business duty does say, and when its parts take effect, see the companion page on the mandate.
Frequently asked questions
Is EHF the same thing as Peppol BIS?
The regulation lists them as two approved standard formats, not as one. Both appear in section 4 in the same breath for both value bands, which means a supplier satisfying either is compliant, and an authority cannot insist on EHF where the regulation permits Peppol BIS.
Can a Norwegian public body insist on its own portal instead?
Section 5's third paragraph requires the authority to be able to receive an electronic invoice in standard format through the Peppol network. A portal can be offered; it does not displace that obligation.
Our contract says NOK 100,000. Is it wrong?
Not necessarily, and the drafting date decides it. The Procurement Act's threshold became NOK 500,000 excluding VAT on 1 July 2026. A contract or policy drafted before that is describing the law as it then stood.
Does the 2019 regulation apply to our sales to Norwegian private companies?
No. Its section 2 ties it to procurements covered by the Procurement Act and to the authorities that Act lists. Private-sector trade is governed by the Bookkeeping Act amendments, which name no format.
If we already send EHF, are we finished?
For public-sector invoicing, on these formats, yes. The open items are the receiving duty and mandatory digital bookkeeping, which are separate obligations with separate timing, and the format regulation for business-to-business invoicing, which does not yet exist.
In practice
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.
46 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
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
Enterprise: written quote by email within two business days. No sales call.
Sources
- Forskrift 1. april 2019 nr. 444 om elektronisk faktura i offentlige anskaffelser (FOR-2019-04-01-444), §§ 1–7, as amended by forskrift 16. oktober 2020 nr. 2063. Made under anskaffelsesloven § 16 third paragraph. EEA reference: EEA Agreement Annex XVI no. 6e (Directive 2014/55/EU).
- Lov 17. juni 2016 nr. 73 om offentlige anskaffelser (anskaffelsesloven) §§ 2 and 16, as amended by lov 6. mars 2026 nr. 8, in force 1 July 2026 per res. 6. mars 2026 nr. 358.
- LOV-2026-06-19-39, endringer i bokføringsloven og enkelte andre lover på finansmarkedsområdet (pliktig digital bokføring og e-fakturering mv.), §§ 3, 7, 10 and 13. Parliamentary stage: Lovvedtak 52 (2025–2026), source document Innst. 262 L (2025–2026), cf. Prop. 44 L (2025–2026).
- Prop. 44 L (2025–2026), Finansdepartementet, 20 March 2026, chapter 3.