EHF Faktura (Elektronisk HandelsFormat faktura) is Norway’s Peppol-based electronic invoice standard, mandatory for B2G invoice submissions and increasingly adopted for B2B e-invoicing. This guide explains EHF Faktura VAT Requirements, Norwegian NO-R validation rules, mandatory invoice fields, Peppol network integration and how to resolve rejected EHF invoices. Understanding these requirements is essential for suppliers invoicing the Norwegian public sector.
The ehf faktura 2026 technical standard is based on Peppol BIS Billing 3.0 — the European electronic invoicing schema used across the EU and EEA Peppol network. Norway adds a layer of country-specific validation rules (NO-R rules, published by Digdir) on top of the base Peppol schema. Every EHF invoice must pass both layers of validation before the Peppol network routes it to the government buyer’s receiving system. A single validation error causes the invoice to be rejected and returned to the sender with an error code.
| Key Takeaways | |
|---|---|
| ● | Norwegian electronic invoice is Norway’s implementation of Peppol BIS Billing 3.0 — mandatory for all Norwegian government (B2G) invoices |
| ○ | The EHF XML must pass both the base Peppol schema validation and the Norwegian NO-R rules before routing |
| ● | Sellers must be registered in the ELMA Peppol participant directory before the first EHF invoice can be sent |
| ○ | Peppol Access Point providers certified by OpenPeppol handle EHF invoice transmission on the seller’s behalf |
| ● | MLR (Message Level Response) from the buyer’s Peppol Access Point is the legally recognised proof of delivery |
| ○ | Five-year retention of EHF invoice XML files and MLR responses is mandatory under Bokforingsloven §13 |
What Are the Key Facts About EHF Faktura VAT Rules?
Norwegian electronic invoice VAT rules require all EHF invoices sent to Norwegian government buyers to include Norwegian-specific VAT data elements that go beyond the base Peppol BIS Billing 3.0 minimum. The seller’s Norwegian organisation number must be present in the Accounting Supplier Party element in 0192::NNNNNNNNN Peppol format. The invoice must use Norwegian VAT category codes (S for 25% standard, SR for the 15% food rate, SA for the 12% reduced rate, Z for zero-rated and E for exempt) rather than EU-standard codes where they differ. Businesses using ERP systems can also review Oracle E-Invoicing integration for their invoice processing requirements.
The buyer’s Peppol Participant Identifier — their unique address in the Peppol network — must be verified in the ELMA registry (elma.difi.no) before the invoice is sent. Using an incorrect or outdated Peppol ID will cause the invoice to fail routing. The peppol norway network uses ELMA as its central directory for identifying and routing Norwegian EHF invoice participants; any Peppol Access Point that handles Norwegian EHF traffic queries ELMA for routing decisions on every invoice transmission.
| Norwegian electronic invoice Element | VAT Data Required | Norwegian-Specific Rule |
|---|---|---|
| InvoiceTypeCode | 380 (commercial invoice) or 381 (credit note) | No change from standard Peppol BIS Billing 3.0 |
| TaxCategoryCode | S (25%), SR (15%), SA (12%), Z (0%), E (exempt) | Norwegian category codes required under NO-R rules |
| Seller Tax Registration | Norwegian org number in Accounting Supplier Party | Mandatory under NO-R rule NO-R-001 |
| BuyerPeppolID | 0192::NNNNNNNNN format from ELMA | Mandatory for Peppol routing in Norway |
| PaymentMeans IBAN | Norwegian IBAN (NO + 15 digits) | Domestic payment IBAN strongly recommended |
| InvoiceDate | YYYY-MM-DD ISO 8601 format | Non-ISO date format causes validation error |
Which Rules Apply to Norwegian electronic invoice VAT Rules in Norway?
Norwegian electronic invoice VAT rules in Norway are governed by two rule sets applied in sequence. The first is the Peppol BIS Billing 3.0 CIUS (Core Invoice Usage Specification) maintained by OpenPeppol, which defines the base XML structure, cardinality (which elements are mandatory vs optional) and code lists for all Peppol invoices across Europe. The second is the Norwegian CIUS extension — the NO-R validation rules — published by Digdir, which adds approximately 40 additional validation rules on top of the base schema specifically for Norwegian government invoicing.
NO-R rules address Norwegian-specific e-invoicing requirements including: mandatory presence of the seller’s Norwegian organisation number (NO-R-001), correct Norwegian VAT category codes (NO-R-010), Norwegian IBAN for payment (recommended in NO-R guidance), and restrictions on certain optional Peppol elements that Norwegian government accounts payable systems do not process. Violations of NO-R rules generate error codes beginning with “NO-R-” in the Peppol transport layer response, which your Peppol Access Point provider will surface in their dashboard or API response.
| Rule Set | Authority | Rule Count | Scope |
|---|---|---|---|
| Peppol BIS Billing 3.0 CIUS |
OpenPeppol | ~120 rules | All Peppol invoice participants across Europe |
| Norwegian NO-R rules | Digdir | ~40 additional rules | Norwegian B2G Norwegian electronic invoice only |
| Bokforingsloven retention rules | Finansdepartementet | §13 archive rule | All Norwegian VAT invoice formats |
| ELMA routing requirements | Digdir | Participant ID validation | Required for all Peppol Norway transactions |
How Do You Set Up Norwegian electronic invoice VAT Rules Step by Step?
The how to ehf faktura setup process has five steps. Step one: obtain a Norwegian organisation number from Bronnoysumdregistrene (brreg.no) — for most Norwegian businesses this is already in place. Step two: select a certified OpenPeppol Access Point provider that supports Norwegian NO-R validation and offers ELMA registration as part of their onboarding. Step three: complete the provider’s onboarding form, including your organisation number, company name, accounting software details and the invoice document types you need to send.
Step four: the Access Point provider registers your organisation number in ELMA as a Peppol Participant — confirm the registration by searching your org number at elma.difi.no. The Peppol Participant Identifier that appears should be in the format 0192::NNNNNNNNN, where NNNNNNNNN is your 9-digit Norwegian organisation number. Step five: configure your QuickBooks accounting software or electronic invoicing system to connect to the Access Point provider’s API or Peppol network entry point, then run a sandbox test invoice to a government buyer’s test Peppol ID before going live with the first real EHF invoice.
For businesses using an electronic invoicing system that already includes a built-in Peppol Access Point — such as Tripletex, Fiken or Visma eAccounting — steps two through four are handled within the accounting platform setup rather than with a separate provider. The platform registers the business in ELMA automatically as part of the EHF activation process. The test invoice step is still important: most platforms include a sandbox or test mode that validates the EHF XML against NO-R rules before the invoice is transmitted to a live government buyer.
Which Integrations Help With Norwegian electronic invoice VAT Rules?
The most effective integrations for Norwegian electronic invoice VAT compliance connect the business’s existing order management or e-commerce platform to a Norwegian accounting system that handles EHF generation and transmission. For Shopify merchants in Norway, the Tripletex Shopify integration and the Fiken Shopify integration are the most widely used — they sync order data from Shopify to the accounting platform, which then generates and sends EHF invoices to government buyers automatically when orders are marked as invoiced.
For businesses running SAP, Microsoft Dynamics 365 or Oracle NetSuite integration with the peppol norway network is achieved through a certified third-party Peppol Access Point connector available in each ERP’s app marketplace. The connector receives invoice data from the ERP in the ERP’s native format, converts it to Peppol BIS Billing 3.0 XML with NO-R validation applied, and transmits it through the Access Point to the buyer. MLR delivery confirmations are returned to the ERP and stored against the original invoice record.
| Source System | EHF Integration Method | Recommended Tool |
|---|---|---|
| Shopify Norway store | Accounting platform integration app | Tripletex or Fiken Shopify app |
| WooCommerce Norway store | Accounting platform plugin | Tripletex or Fiken WooCommerce plugin |
| SAP S/4HANA | Certified Peppol Access Point connector | Ensure OpenPeppol certified + NO-R support |
| Microsoft Dynamics 365 | Certified Peppol Access Point connector | Verified NO-R and ELMA support required |
| Oracle NetSuite | Certified Peppol Access Point connector | Check Norwegian CIUS compliance in specs |
| Standalone billing software | Direct Access Point API integration | Via provider’s REST API or SFTP channel |
Which Errors Should You Avoid With Norwegian electronic invoice VAT Rules?
The most frequent Norwegian electronic invoice error is an incorrect or missing seller organisation number (NO-R-001 violation). The organisation number in the AccountingSupplierParty element must be the seller’s registered Norwegian 9-digit organisation number in the format 0192::NNNNNNNNN. A common mistake is entering the number with spaces (as it appears in Norwegian addresses: 123 456 789) rather than as a continuous 9-digit string. Spaces in the number string cause a NO-R-001 validation failure.
The second most common error is a stale or incorrect buyer Peppol ID. Government buyers occasionally change their Peppol Access Point provider, which may result in a new participant ID entry in ELMA. If your accounting software caches the buyer’s Peppol ID from a previous setup, the cached value may no longer route correctly. Running a fresh ELMA lookup for each major government buyer at the start of each calendar year reduces stale-ID routing failures significantly.
| Error Code | Error Description | Fix |
|---|---|---|
| NO-R-001 | Seller organisation number missing or invalid format | Enter 9-digit org number without spaces in AccountingSupplierParty |
| NO-R-010 | Invalid Norwegian VAT category code | Use S/SR/SA/Z/E codes — not numeric rates |
| BII2-T10-R002 | Missing mandatory BuyerParty Peppol ID | Verify buyer Peppol ID in ELMA and update customer record |
| Date format error | Non-ISO date format in InvoiceDate | Set accounting system to YYYY-MM-DD output |
| Routing failure — no MLR received | Buyer Access Point offline or stale Peppol ID | Check ELMA; contact buyer AP team; resubmit after 24h |
What Should You Check Before Choosing Norwegian electronic invoice VAT Rules?
Before selecting an Norwegian electronic invoice solution, verify that the Peppol Access Point provider or accounting platform holds current OpenPeppol certification. OpenPeppol maintains a public list of certified Access Points at peppol.eu/registration/list-of-certified-providers. A provider that lacks current OpenPeppol certification may have outdated schema support that fails NO-R validation rules or misroutes invoices. Certification must be renewed annually, so check that the listed date is within the last 12 months. Businesses operating across Nordic markets can also review Sweden e-invoicing requirements.
The Norwegian electronic invoice 2026 provider checklist should also include: Norwegian NO-R rule support confirmed in writing, ELMA registration service included in the subscription, an online dashboard showing invoice delivery status and MLR responses, a 5-year invoice archive service, and Norwegian-language customer support. For businesses with high invoice volumes (over 500 per month), check whether the provider offers volume pricing and a dedicated technical account contact for incident resolution during onboarding.
Conclusion
Norwegian electronic invoice is the cornerstone of B2G invoicing in Norway and an increasingly important tool for B2B electronic invoicing as the Peppol network expands. Getting Norwegian electronic invoice VAT rules right — correct NO-R validation, accurate Peppol IDs, Norwegian VAT category codes and a 5-year archive — means government invoices are delivered and paid without delay, and the supplier maintains an auditable electronic record of every transaction. Choosing a certified Peppol Access Point with Norwegian NO-R support is the single most important implementation decision.
For most Norwegian businesses, the practical path is to use a Norwegian accounting platform that includes Peppol Access Point functionality — Tripletex, Fiken or Visma — rather than configuring a standalone Access Point separately. This keeps invoice generation, EHF transmission, MLR receipt and archiving in a single system, reduces the number of vendor relationships to manage and ensures that NO-R rule updates are applied automatically when Digdir publishes revisions. Once set up, EHF invoice sending becomes a routine one-click operation for every government invoice.
Frequently Asked Questions
What is Norwegian electronic invoice norway and who must use it?
Norwegian electronic invoice Norway is Norway’s electronic invoice format based on Peppol BIS Billing 3.0, mandatory for all suppliers invoicing Norwegian central government ministries, directorates, county municipalities and local municipalities registered in the ELMA Peppol directory. Any Norwegian business or foreign supplier that has sold goods or services to a Norwegian government entity and needs to submit an invoice must use Norwegian electronic invoice norway through a certified Peppol Access Point. B2B invoicing between private companies currently uses Norwegian electronic invoice on a voluntary basis.
What does how to Norwegian electronic invoice setup involve for a small business?
How to Norwegian electronic invoice setup for a small business takes three to five business days: sign up with a Norwegian accounting platform that includes EHF capability (Tripletex or Fiken are the most popular choices for small businesses), activate the EHF setting and enter your organisation number, wait for ELMA registration confirmation from the platform (usually one to three days), then enter the government buyer’s Peppol ID in the customer record and issue a test invoice. If the test shows a valid MLR response, the EHF setup is live and ready for production invoices.
What is peppol norway and how does it relate to Norwegian electronic invoice?
Peppol Norway refers to the Norwegian implementation of the international Peppol network, operated locally through Digdir’s ELMA participant directory. Norwegian electronic invoice is the invoice document type transmitted across Peppol Norway. The Peppol network handles routing — finding the correct Access Point to deliver the invoice to — while Norwegian electronic invoice defines the content and structure of the invoice XML being routed. A Norwegian business needs both a Peppol Access Point registration (to join peppol norway) and a correctly formatted Norwegian electronic invoice XML (to have something compliant to send).
Is Norwegian electronic invoice 2026 different from earlier EHF versions?
Norwegian electronic invoice 2026 uses Peppol BIS Billing 3.0, which replaced the earlier EHF 2.0 standard several years ago. Businesses that set up EHF sending under BIS Billing 3.0 do not need to make changes for 2026 — the standard itself is the same. What evolves year-on-year are the Norwegian NO-R validation rules maintained by Digdir, which may be updated periodically to address new mandatory field requirements or close validation gaps. OpenPeppol-certified Access Point providers update their validation engines automatically when NO-R rule revisions are published.
What is an electronic invoicing system and do I need one for Norwegian electronic invoice?
An electronic invoicing system is any software that generates, transmits and receives structured electronic invoice documents — in Norway, this means Norwegian electronic invoice XML through the Peppol network. You need an electronic invoicing system if you invoice Norwegian government buyers. The simplest electronic invoicing system for Norwegian SMEs is a Norwegian accounting platform (Tripletex, Fiken, Visma) with built-in EHF capability. Larger businesses may use a standalone electronic invoicing system connected to their ERP through an API, but the end result is the same: EHF XML transmitted to the government buyer through a certified Access Point.
Source by:
Image by Magnific
