The Norway B2B E-Invoicing Mandate introduces significant changes to how businesses exchange electronic invoices in 2026. The obligation affects Norwegian businesses of all sizes and requires the exchange of structured electronic invoices in EHF 3.0 or Peppol BIS Billing 3.0 format through the Peppol network. Businesses that have not yet begun their compliance preparations face real operational risks as the mandate’s deadlines move from policy to enforcement.
The Norwegian mandate builds on the existing B2G (business-to-government) e-invoicing requirement that has been in place since 2012, when public sector entities in Norway were first required to accept EHF invoices. The extension to B2B transactions reflects Norway’s broader digital economy strategy and aligns with the European Union’s VAT in the Digital Age (ViDA) initiative, even though Norway is not an EU member state.
This guide covers every aspect of the 2026 B2B e-invoicing mandate: who must comply, the key dates, the accepted formats, mandatory invoice fields, archiving rules, the step-by-step path to compliance, and the penalties that apply to businesses that fail to meet the requirements.
| Key Takeaways | |
| • | The Norwegian B2B e-invoicing mandate requires all registered Norwegian businesses to send and receive structured electronic invoices in EHF 3.0 or Peppol BIS Billing 3.0 format from the mandate’s effective date. |
| • | Invoices must be exchanged through the Peppol network via a certified Norwegian access point provider — email PDF delivery does not satisfy the mandate even if the PDF is labelled as an e-invoice. |
| • | Mandatory invoice fields include the supplier’s Norwegian organization number (orgnummer), the buyer’s orgnummer, invoice date, due date, line-item descriptions, applicable MVA rates, and total amounts including and excluding MVA. |
| • | Invoices must be archived in accordance with the Norwegian Accounting Act (Bokføringsloven) for a minimum of five years in a format that remains readable and verifiable throughout the retention period. |
| • | The Norwegian Tax Administration (Skatteetaten) may impose penalties for non-compliance, including denial of VAT input tax deductions for invoices received outside the mandated electronic format. |
Who Must Follow the Norwegian B2B E-Invoicing Mandate?
The B2B e-invoicing mandate applies to all businesses registered in the Norwegian Business Registry (Foretaksregisteret) and the Norwegian VAT Register (Merverdiavgiftsregisteret). This includes sole traders (enkeltpersonforetak), limited companies (aksjeselskap, AS), limited liability partnerships (ansvarlig selskap, ANS), and branches of foreign companies registered in Norway.
The obligation covers both the sending and receiving dimensions of e-invoicing. A Norwegian business must be capable of sending structured EHF or Peppol BIS invoices to its Norwegian B2B customers and must be registered in the Peppol directory so that its Norwegian B2B suppliers can send structured invoices to it. A business that is ready to send but not configured to receive — a common gap in early compliance implementations — does not satisfy the full mandate.Small businesses and sole traders are not automatically exempt from the mandate. The Norwegian Tax Administration has indicated that the mandate applies across the full spectrum of registered businesses, with compliance support available through accounting software providers who have integrated EHF and Peppol capabilities. The practical compliance path for small businesses is through cloud accounting software (Fiken, Tripletex, Visma eAccounting) that handles the Peppol registration and invoice exchange automatically.
| Business Type | Mandate Applies | Compliance Path |
|---|---|---|
| AS/ASA (Limited Company) | Yes | ERP or accounting software with Peppol integration |
| ENK (Sole Trader, VAT-registered) | Yes | Cloud accounting software with EHF support |
| ANS/DA (Partnership) | Yes | Accounting software or access point service |
| Foreign Branch in Norway | Yes | ERP integration or Norwegian access point |
| Non-VAT-registered small business | Verify with Skatteetaten | May be exempt — confirm registration status |
Timeline and Key Dates for the 2026 Mandate
The Norwegian B2B e-invoicing mandate follows a phased implementation timeline that reflects the different readiness levels of large enterprises, mid-market companies, and small businesses. Understanding which phase applies to your organization is the first step in planning your compliance programme.
Large enterprises — defined as businesses with annual turnover above the threshold set by the Norwegian Tax Administration — were required to comply from the earliest effective date. These organizations have had the longest preparation period and are expected to have operational Peppol sending and receiving capability by the mandate’s first phase.Mid-market and smaller businesses follow in subsequent phases, with the Norwegian Tax Administration providing transition guidance to support businesses that need time to upgrade their accounting systems or procure access point services. Businesses that begin their compliance preparations immediately have sufficient time to complete registration, software integration, and testing before their applicable phase deadline.
| Phase | Business Category | Compliance Deadline |
|---|---|---|
| Phase 1 | Large enterprises (turnover above threshold) | From 2026 effective date |
| Phase 2 | Mid-market businesses | Six months after Phase 1 |
| Phase 3 | Small businesses and sole traders | Twelve months after Phase 1 |
| All phases | B2G (government suppliers) | Already mandatory since 2012 |
Which E-Invoice Formats Does Norway Accept?
Norway accepts two structured electronic invoice formats under the 2026 B2B mandate: EHF 3.0 (Electronic Handelformat, version 3.0) and Peppol BIS Billing 3.0. Both formats are based on the same underlying UN/CEFACT Cross-Industry Invoice (CII) standard and are technically compatible — an invoice created in EHF 3.0 is a valid Peppol BIS Billing 3.0 document and vice versa.
EHF 3.0 is the Norwegian national profile of the Peppol BIS Billing 3.0 standard, developed and maintained by the Norwegian Agency for Public Management and eGovernment (Digitaliseringsdirektoratet). It includes Norwegian-specific validation rules for organization numbers, MVA registration numbers, and Norwegian address formats. EHF 3.0 replaced the earlier EHF 2.0 format, which remains in use for some legacy B2G transactions but is not the recommended format for new B2B implementations.
PDF invoices, even structured PDF/A-3 invoices with embedded XML data, do not satisfy the Norwegian B2B mandate. An invoice that arrives as an email PDF attachment — however well-formatted and however clearly labelled — is not an EHF or Peppol invoice and does not count as compliance. This is a common misunderstanding: the mandate requires structured electronic exchange through the Peppol network, not digital delivery of a document.
Mandatory Fields and Archiving Requirements
Every EHF 3.0 or Peppol BIS Billing 3.0 invoice sent under the Norwegian B2B mandate must include a defined set of mandatory fields. Missing fields cause invoice validation failures at the access point and result in the invoice being rejected before it reaches the buyer’s system. Building correct invoice data into your accounting or ERP system at the outset avoids the rework of correcting and resubmitting rejected invoices.
Mandatory fields include: supplier legal name and Norwegian organization number (orgnummer, nine digits); buyer legal name and organization number; supplier Peppol endpoint ID (formatted as 0192:[orgnummer] for Norwegian businesses); invoice number (unique within the supplier’s numbering sequence); invoice date; payment due date; currency code (NOK for domestic Norwegian transactions); line-item descriptions with quantities and unit prices; applicable MVA rate for each line (25%, 15%, 12%, or 0%); line-item net amounts; total net amount excluding MVA; total MVA amount per rate; and invoice total including MVA.
Archiving requirements under the Norwegian Accounting Act (Bokføringsloven) mandate that invoices be retained for a minimum of five years from the end of the accounting year in which the transaction occurred. The archived invoice must be stored in a format that is readable, verifiable, and unaltered throughout the retention period. The original EHF XML file satisfies this requirement; storing only a PDF rendering of the invoice does not, because the PDF cannot be verified as an unaltered representation of the original structured data. Businesses using SAP ERP invoice records should also consider how structured invoice data is retained and associated with the original transactions.
Step-by-Step Guide to Compliance
The path to B2B e-invoicing compliance follows a clear sequence: registration in the Peppol directory, selection of an access point provider, integration of your accounting or ERP system, testing, and go-live. Each step builds on the previous, and skipping steps — particularly testing — creates operational risk at go-live.
Step one is confirming your Norwegian organization number is correct in your accounting system. The Peppol endpoint identifier for Norwegian businesses is your organization number prefixed with the scheme code 0192. An error in the organization number prevents your business from being correctly listed in the Peppol directory and means that suppliers cannot find your endpoint to send invoices.
Step two is selecting a Norwegian Peppol access point provider. Access points are certified by the Peppol Authority (OpenPeppol) and listed in the Norwegian Peppol directory. Providers include software companies (Visma, Uni Micro, Accountor) that bundle access point services with accounting software, and standalone access point services (DIFI Peppol, Basware, Pagero) that integrate with any ERP system. Your selection should be based on your accounting software’s native integration, the provider’s Norwegian support capability, and the pricing model.
Step three is configuring your accounting or ERP system to generate EHF 3.0 XML output rather than PDF invoices. Most Norwegian accounting software includes this configuration as a setting change rather than a development project. ERP systems (SAP, Oracle, Microsoft Dynamics, Workday) require configuration of the Peppol output channel and mapping of your invoice data to the EHF field structure.
Step four is sending test invoices through the Peppol test network before going live on the production network. The Norwegian test network allows businesses to validate that their invoice XML is correctly formatted, that their endpoint is reachable, and that the end-to-end exchange works with specific trading partners. Test network validation prevents production errors that delay payment.
Penalties, Exemptions, and Common Mistakes
The Norwegian Tax Administration’s enforcement approach for the B2B e-invoicing mandate focuses primarily on VAT compliance consequences rather than direct penalties for format non-compliance. The key risk for businesses that continue to send and receive PDF invoices after the mandate’s deadline is the potential denial of VAT input tax deductions for invoices received in non-compliant format.
Norway’s VAT rules require that a VAT deduction claim be supported by a valid invoice that meets the formal requirements of the mandate. An invoice received as a PDF after the B2B e-invoicing deadline may be treated as not meeting those formal requirements, exposing the recipient business to VAT assessments, interest charges, and penalties in a Skatteetaten tax audit. The commercial risk of losing input VAT deductions — which represent 25% of the gross invoice amount for standard-rated purchases — is a stronger compliance driver than direct mandate penalties for most businesses.
Common mistakes in B2B e-invoicing compliance include using e-invoicing software in Japan without correctly configuring the accounting system to send EHF invoices (making the business reachable but not sending correctly); sending invoices with incorrect or missing MVA rates; using the old EHF 2.0 format rather than EHF 3.0; and failing to test with specific trading partners before going live. Each mistake can be corrected, but correction after go-live causes invoice processing delays and, in some cases, disputed payment terms.
Conclusion
Norway’s 2026 B2B e-invoicing mandate marks a fundamental shift in how Norwegian businesses exchange invoices. The mandate eliminates PDF and paper invoices from compliant B2B transactions and replaces them with structured EHF 3.0 or Peppol BIS Billing 3.0 documents exchanged through the Peppol network. Businesses that complete their registration, access point selection, system configuration, and testing before their applicable phase deadline will be well-positioned for compliance. The VAT deduction risk for non-compliant invoice receipt makes early action commercially prudent, not merely regulatory.
Frequently Asked Questions
What is the Norwegian B2B e-invoicing mandate?
The mandate requires all VAT-registered Norwegian businesses to send and receive structured electronic invoices in EHF 3.0 or Peppol BIS Billing 3.0 format through the Peppol network, replacing PDF and paper invoice exchange for B2B transactions.
Does the mandate apply to sole traders in Norway?
Yes. VAT-registered sole traders (enkeltpersonforetak) are included in the mandate. Cloud accounting software with built-in EHF support (Fiken, Tripletex, Visma eAccounting) provides a straightforward compliance path for small businesses.
Can I still send PDF invoices after the mandate deadline?
No. PDF invoices do not satisfy the mandate. An invoice that arrives as an email PDF does not count as a valid EHF or Peppol invoice and may result in loss of VAT input tax deductions for the recipient.
What is the difference between EHF 3.0 and Peppol BIS Billing 3.0?
EHF 3.0 is the Norwegian national profile of Peppol BIS Billing 3.0. Both are based on the same underlying standard and are technically compatible. EHF 3.0 includes Norwegian-specific validation rules for organization numbers and MVA rates.
How do I register my business in the Peppol network?
Registration is handled through your Peppol access point provider. Your provider submits your organization number and endpoint details to the Peppol directory (SMP). You do not register directly with Peppol — the access point handles this on your behalf.
What happens if I receive a non-compliant invoice?
A non-compliant invoice received after the mandate deadline may not support a valid VAT input tax deduction claim. Businesses should notify non-compliant suppliers of the requirement and request resubmission in EHF format.
How long must I keep e-invoices in Norway?
A minimum of five years from the end of the accounting year in which the transaction occurred, under the Norwegian Accounting Act (Bokføringsloven). The original EHF XML file must be retained — a PDF rendering alone does not satisfy the archiving requirement.
What is a Norwegian Peppol access point?
An access point is a certified service provider that connects your accounting or ERP system to the Peppol network. It handles the technical transmission of EHF invoices to and from trading partners and manages your registration in the Peppol directory.
Source by:
Image by Pexels
