EHF and Peppol in Norway: How E-Invoicing Works in 2027

If you are preparing for Norway's 2027 B2B e-invoicing mandate, you will quickly encounter three names:

EHF. Peppol. ELMA.

They are closely connected, but they do not mean the same thing.

Understanding how they work together is one of the easiest ways to understand Norway's e-invoicing system.

What Is EHF?

EHF stands for Elektronisk Handelsformat, Norway's established framework for structured electronic business documents.

Unlike an invoice created only as a PDF, an EHF invoice contains structured information that software can identify and process automatically.

Supplier details, buyer information, invoice lines, VAT information, payment data and totals can therefore move directly between financial systems without somebody having to manually re-enter the invoice.

This structured-data approach is central to Norway's move toward mandatory B2B e-invoicing.

What Is Peppol in Norway?

Peppol is the interoperability network used to exchange structured electronic documents between organizations.

Instead of every supplier building a different direct connection to every customer, Peppol provides a standardized exchange model.

A sender connects through a Peppol Access Point.

The recipient connects through its own Peppol service.

The network determines how the document reaches the correct destination.

For businesses operating internationally, this is particularly useful because the same Peppol infrastructure is used across a growing number of European and global e-invoicing markets.

What Is ELMA?

ELMA stands for Elektronisk mottakeradresseregister.

In simple terms, it helps identify businesses that can receive electronic documents.

Before an electronic invoice is sent, the sending environment needs to know whether the recipient is registered for electronic document exchange and where the invoice should be delivered.

Recipient registration therefore becomes an important part of successful Peppol invoicing.

How Does an E-Invoice Travel Through Peppol?

The process can be simplified into four steps.

1. Create the invoice

The supplier creates an invoice inside its ERP, accounting or billing system.

Instead of relying only on a PDF representation, the invoice data is prepared in a structured electronic format.

2. Validate the invoice

Before transmission, the invoice should be checked for required information and technical errors.

Incorrect identifiers, missing invoice data or invalid structures can prevent automated processing.

3. Send through a Peppol Access Point

The invoice is transmitted through the supplier's Peppol Access Point.

The recipient's electronic capabilities and routing information are identified through the relevant directory and service metadata infrastructure.

4. Deliver to the recipient

The structured invoice reaches the recipient's connected accounting or ERP environment, where it can be processed with far less manual intervention than an emailed PDF.

What Is a Peppol ID?

A Peppol ID is an electronic identifier used within the Peppol ecosystem to identify participating organizations.

Businesses searching for a customer on Peppol may encounter identifiers based on organization numbers or other approved identifier schemes.

Correct master data is therefore extremely important.

An incorrect company identifier can become a routing problem, not simply a typo on an invoice.

Do Businesses Need to Register for Peppol in Norway?

Businesses that need to receive invoices through the Peppol environment must have the appropriate electronic receiving capability and registration.

In most cases, this is arranged through a Peppol service or Access Point provider rather than by building direct Peppol infrastructure internally.

For Finance and IT teams, the practical question is therefore not simply:

“Are we on Peppol?”

It is:

“Can our ERP create, validate, send, receive and monitor the required electronic documents through Peppol?”

EHF, Peppol and Norway's 2027 Mandate

Norway's mandatory e-invoicing rules make this infrastructure increasingly important.

From 1 January 2027, the first phase of the B2B e-invoicing obligation begins. By 1 January 2030, digital bookkeeping and automated e-invoice reception become much more significant.

That means companies should use 2026 to review their ERP data, recipient identifiers, Peppol connectivity and invoice validation processes.

For businesses already operating across several European countries, Norway can also be an opportunity to move away from isolated country integrations and toward a scalable Peppol and e-invoicing architecture.

For the SAP perspective, read our related guide on EHF and Peppol in Norway for SAP e-invoicing.

Related E-Invoicing Resources

Read the original article and explore Docnova e-invoicing insights.

For SAP-integrated compliance, visit the Melasoft SAP e-invoicing solution.