Setting up EHF and Peppol e-invoicing for a Norwegian company in 2026 requires following an EHF and Peppol Setup Checklist covering preparation, provider selection, directory registration, system configuration, testing, and staff training. Companies that approach the setup in sequence — addressing each step before moving to the next — complete their implementation more quickly and with fewer errors than those who attempt to configure systems before the preparatory steps are complete.
This checklist-style guide walks through every phase of the EHF Peppol setup process for Norwegian companies: what to prepare before starting, how to select a Peppol access point provider, how to register in the Peppol directory, how to configure accounting software, how to send a test invoice, and how to train staff. Each section includes the specific actions required and the common errors to avoid at that stage.
Norwegian companies with complex ERP environments (SAP, Oracle, Microsoft Dynamics, Workday) will find that the EHF Peppol setup checklist applies equally to enterprise implementations as to cloud accounting software — the steps are the same, but the configuration work in enterprise systems typically requires more time and specialist involvement.
Key Takeaways
- The EHF Peppol setup process follows a clear sequence: prepare your organization number and accounting system data, select and onboard an access point provider, register in the Peppol directory, configure invoice output in your accounting software, test on the Peppol test network, and train staff.
- Before starting, verify that your Norwegian organization number is correctly recorded in your accounting system and that your business is registered in the Norwegian VAT register (Merverdiavgiftsregisteret) if you intend to issue MVA-bearing invoices.
- Access point selection should be based on your accounting software’s native integrations — using a provider that is already integrated with your software minimizes configuration work and support complexity.
- Testing on the Peppol test network before go-live is mandatory, not optional. Test invoice exchange validates end-to-end delivery and catches format errors before they affect real trading partner relationships.
- Staff training should cover both invoice sending (how to issue invoices that generate valid EHF XML) and invoice receiving (how to process EHF invoices that arrive in the accounting system from the Peppol network).
What Should You Prepare Before Starting?
The preparation phase of EHF Peppol setup identifies and corrects data quality issues before they become configuration errors. Poor data — an incorrect organization number, a missing MVA registration, or an outdated bank account in the system — surfaces during Peppol setup as failed validations or directory registration errors. Identifying and correcting these issues before engaging an access point provider saves time and avoids troubleshooting during setup.
Verify your Norwegian organization number (orgnummer). The orgnummer is the nine-digit identifier that becomes your Peppol participant ID (formatted as “0192:[orgnummer]”). Check that the orgnummer recorded in your Accounting System Integration matches the number in the Norwegian Business Registry (Brønnøysundregistrene) at brreg.no. An organization number with a digit transposition or an old predecessor number (for businesses that have been restructured) will cause Peppol directory registration failure.
Confirm your MVA registration status. Businesses registered in the Norwegian VAT register (Merverdiavgiftsregisteret) must include “MVA” after the organization number on invoices and must apply the correct MVA rates to invoice lines. Verify your registration status at skatteetaten.no. Businesses that are not MVA-registered issue invoices without MVA but must still comply with the EHF format and Peppol delivery requirements for B2B invoicing.Audit your customer master data. For each Norwegian B2B customer you invoice, verify that their organization number is correctly recorded in your accounting system. The organization number is the look-up key for the Peppol directory — if a customer’s organization number is wrong in your system, your access point cannot find their Peppol endpoint and invoice delivery will fail. Use brreg.no to verify organization numbers for key customers before go-live.
| Preparation Item | Action Required | Where to Verify |
|---|---|---|
| Organization number | Verify 9-digit orgnummer in accounting system | brreg.no |
| MVA registration | Confirm registration in VAT register | skatteetaten.no |
| Customer organization numbers | Audit key customers’ orgnummer data | brreg.no |
| Accounting software version | Confirm EHF 3.0 support is available | Vendor documentation |
| Access point compatibility | Check which providers integrate with your software | Software vendor/provider list |
How Do You Pick a Peppol Access Point?
Selecting a Peppol access point provider for your Norwegian company is one of the most consequential decisions in the EHF setup process. The access point connects your accounting system to the Peppol network, handles your directory registration, and transmits and receives invoices on your behalf. The quality, reliability, and support capability of your access point provider directly affect the smoothness of your e-invoicing operations.
The primary selection criterion for most Norwegian companies is accounting software integration. If your accounting software (Visma, Tripletex, Fiken, Uni Micro, 24SevenOffice, or an ERP system) has a native partnership with a specific Peppol access point provider, selecting that provider minimizes integration complexity. Native integrations typically mean that the access point is already tested with your software version, that support calls involve fewer hand-offs between teams, and that updates to the EHF format version are handled jointly by the software vendor and the access point provider.
For enterprise ERP implementations (SAP, Oracle, Microsoft Dynamics, Workday), the access point selection is more open, as enterprise systems typically support standard Peppol transport protocols (AS4) that are compatible with any certified access point. Enterprise ERP buyers should evaluate access points on their Norwegian support capability (Norwegian-speaking support, understanding of Norwegian compliance requirements), their SLA for invoice delivery and error resolution, and their experience with enterprise ERP integrations in the Norwegian market.
How Do You Get Your Company Listed in the Peppol Directory?
Peppol directory registration is handled entirely by your access point provider — Norwegian companies do not register directly with the Peppol directory. When you sign up with an access point provider, the provider creates your Service Metadata Provider (SMP) entry in the Peppol directory as part of the onboarding process. This entry maps your Peppol participant ID (0192:[orgnummer]) to your access point’s endpoint address and lists the document types you can receive.
The registration process typically requires you to provide your organization number, your legal business name, and confirmation of the document types you wish to receive (EHF invoice, EHF credit note, Peppol BIS Billing 3.0 invoice, Peppol BIS Order, etc.). Your Peppol access point provider may also require confirmation that the organization number you’re registering belongs to your business — some providers check the Brønnøysundregistrene to validate this.
After registration, you can verify that your company appears in the Peppol directory using the public lookup tool at peppol.helger.com. Enter your participant ID (0192:[orgnummer]) and confirm that the correct access point endpoint address is returned. This verification step takes two minutes and confirms that trading partners will be able to find your endpoint and route invoices to you. Completing this verification before your go-live date gives confidence that the receiving side of your e-invoicing setup is operational.
How Do You Configure Your Accounting Software?
Accounting software configuration for EHF Peppol in Norway involves three changes: enabling EHF 3.0 XML invoice output (replacing PDF generation for B2B invoices), connecting the software to your access point (providing the API credentials or integration settings supplied by your provider), and mapping your invoice data to the EHF 3.0 field structure (ensuring that organization numbers, MVA rates, and payment terms are correctly mapped).
In most Norwegian cloud accounting platforms, enabling EHF output is a settings change rather than a development task. Visma eAccounting, Tripletex, Fiken, and Uni Micro all include EHF Peppol output as a configurable feature that can be enabled in the settings menu. The software handles the XML generation and Peppol submission automatically once the feature is enabled and the access point credentials are entered. For businesses using these platforms, configuration time is typically under one hour.
Enterprise ERP configurations are more involved. SAP users configure the Peppol output channel through the Document and Reporting Compliance (DRC) module, mapping the internal invoice document type to the EHF 3.0 output format and configuring the access point connection in the communication system settings. Oracle Fusion Cloud ERP uses the Norwegian localization pack for EHF invoice generation, with the Peppol submission handled through the e-invoicing service component. Microsoft Dynamics 365 uses the Electronic Reporting (ER) framework for EHF format configuration. Workday Financial Management uses the Norwegian EHF invoice output configuration in the customer invoice settings. Enterprise ERP configurations typically require a certified implementation consultant and two to four weeks of configuration and testing work.
How Do You Send a Test Invoice?
Testing is the step most often skipped in Peppol implementations — and the most consequential skip. A test invoice sent through the Peppol test network validates the complete chain from accounting software to access point to Peppol network to receiver’s access point to receiver’s system. Issues that tests catch include XML format validation failures (missing mandatory fields), incorrect participant ID formats, access point connectivity problems, and receiver-side processing errors. Each of these issues, caught in testing, can be corrected before affecting a real trading partner relationship.
The Peppol test network (PEPPOL TEST environment) is a parallel Peppol infrastructure that mirrors the production network but is used only for testing. Your access point provider will have a test environment that connects to the Peppol test network. Send at least five test invoices covering: a standard invoice with 25% MVA; an invoice with multiple MVA rates (25% and 15%); an invoice with 0% MVA (export); a credit note referencing a previous invoice; and an invoice with multiple line items. This set covers the most common EHF validation scenarios and confirms that your configuration handles all Norwegian MVA rate combinations correctly. Businesses exploring e-invoicing software in Egypt can also review Advintek’s solutions for electronic invoice processing and business accounting workflows.
Test invoice exchange with specific trading partners — particularly large Norwegian customers you invoice frequently — is strongly recommended before go-live. A bilateral test with a key customer confirms that their access point receives and processes your invoices correctly and that their accounting system handles the incoming EHF data as expected. Some large Norwegian buyers (major retailers, public sector entities) have their own onboarding processes for new EHF suppliers; completing their onboarding requirements before the mandate deadline avoids processing delays on go-live.
How Do You Train Staff?
Staff training for EHF Peppol covers two groups: the accounts payable and receivable staff who process invoices daily, and the finance or IT administrators who manage the accounting system configuration and access point integration. Each group needs different training content.
Accounts receivable staff issuing invoices need to understand that EHF Peppol-eligible customers (registered Norwegian businesses) will now receive their invoices through the Peppol network rather than by email. They need to know: how to confirm that a customer is Peppol-registered before issuing their first EHF invoice (using the brreg.no lookup or the Peppol directory lookup in their accounting software); what to do when a customer is not Peppol-registered (issue a PDF invoice in the interim and follow up to request their Peppol registration); and how to handle EHF invoice rejection notifications (review the error, correct the invoice data, resubmit). Businesses can use EHF Peppol Integration Services to connect their invoicing systems with the Peppol network and support electronic invoice delivery.
Accounts payable staff receiving invoices need to understand how EHF invoices arrive in the accounting system (directly from the Peppol integration, without an email), how to process them using the three-way matching workflow if applicable, and what to do if an incoming EHF invoice has validation errors or data mismatches. Finance or IT administrators need to understand how to monitor the Peppol integration for errors, how to update access point credentials if they change, and how to add new customers and suppliers to the Peppol-enabled workflow.
Conclusion
The EHF Peppol setup process for Norwegian companies is predictable and manageable when approached in the right sequence. Preparation ensures the data is correct before configuration begins. Access point selection determines the integration complexity. Directory registration makes the business reachable. Software configuration enables EHF output. Testing validates the end-to-end process. Staff training ensures operational capability after go-live. Norwegian companies that complete all six phases before their mandate deadline will be well-positioned for compliant, automated invoice exchange — and those that invest the time in thorough testing will avoid the operational disruptions that underprepared implementations create.
Frequently Asked Questions
How long does the full EHF Peppol setup process take for a Norwegian company?
For companies using Norwegian cloud accounting software (Visma, Tripletex, Fiken), the full setup typically takes one to three weeks including testing. For enterprise ERP implementations, allow six to twelve weeks for configuration, testing, and staff training.
Do I need a separate Peppol access point if my accounting software already includes one?
No. If your accounting software includes a bundled Peppol access point service, you do not need to procure a separate access point. Use your software’s built-in integration unless there is a specific reason (custom ERP integration, multi-software environment) to use a standalone access point.
Can I test EHF invoicing before my accounting software is fully configured?
Yes. Most access point providers offer test portal environments where you can submit EHF XML files manually for format validation, without requiring full accounting software integration. This is useful for validating your XML structure before connecting your software.
What is the most common cause of Peppol invoice delivery failure?
The most common cause is an incorrect or missing Peppol participant ID for the receiver. Always verify the receiver’s Peppol registration at peppol.helger.com before issuing your first EHF invoice to a new customer.
Do I need to train all staff, or just the finance team?
Primarily the finance team (accounts receivable and payable staff) and the system administrator responsible for the accounting software integration. Other staff rarely interact directly with the EHF Peppol system.
What should I do if a customer says they cannot receive EHF invoices?
Check the Peppol directory to confirm whether the customer is registered. If they are not registered, continue sending PDF invoices until they complete their Peppol registration. If they are registered but report non-receipt, contact your access point provider to diagnose the delivery issue.
Is there a Norwegian government resource for EHF Peppol setup?
Yes. The Norwegian Digitalisation Agency (Digitaliseringsdirektoratet, digdir.no) publishes guidance on EHF and Peppol for Norwegian businesses, including access point lists, format specifications, and compliance guidance. The Norwegian Tax Administration (Skatteetaten) publishes mandate compliance guidance.
What happens to my existing PDF invoice workflow after the mandate?
For B2B invoices to Norwegian registered businesses, PDF delivery no longer satisfies the mandate. Your PDF invoice workflow should be replaced by EHF Peppol delivery for registered Norwegian business customers. PDF delivery continues to be appropriate for non-registered customers, foreign customers, and B2C transactions.
Source by:
Image by Pexels
