The EHF Faktura vs PDF Invoice comparison is one of the most important decisions Norwegian businesses face when choosing how to manage their invoicing operations in 2026. PDF invoicing has been the default for decades, but the rise of Norway’s EHF e-invoicing mandate and the upcoming B2B e-invoice requirement are making the shift to structured electronic invoices unavoidable. This guide breaks down the key differences between EHF Faktura and PDF Invoice formats, explains why PDF invoices are no longer compliant for Norwegian government buyers, and helps businesses understand the benefits of Norwegian e-invoice adoption.
Norwegian e-invoice benefits go far beyond legal compliance. Structured EHF invoices are processed automatically by buyer ERP systems, paid faster than PDFs, archived with full delivery proof and linked to Peppol routing confirmation. PDF invoices require manual data entry at the buyer, create payment delays, offer no delivery guarantee and will be rejected by public sector buyers under current Norwegian e-invoicing law. Understanding the structured e-invoice difference is the first step toward building an invoicing process that is efficient, compliant and future-proof.
Key Takeaways
- EHF Faktura vs PDF Invoice: EHF is a structured XML document processed automatically; a PDF is an unstructured image requiring manual data entry by the buyer.
- PDF invoice Norway: PDF invoices are not compliant for invoicing Norwegian public sector buyers — they will be rejected and not paid until resubmitted as EHF.
- structured e-invoice difference: EHF data flows directly into buyer ERP systems without manual input; PDF data must be manually keyed in or OCR-extracted.
- e-invoice vs email invoice: even a PDF sent by email is not a structured e-invoice — structured e-invoices are XML delivered via Peppol, not email attachments.
- Norwegian e-invoice benefits include faster payment, automated AP processing at the buyer, delivery confirmation, reduced errors and a compliant archive.
- EHF faktura format (Peppol BIS Billing 3.0 + NO-R) replaces PDF for B2G now and is expected to replace PDF for B2B from 2027.
What Is the Difference Between EHF and PDF Invoices?
The EHF Faktura vs PDF Invoice difference is fundamental: an EHF invoice is a structured data document that computers read and process automatically, while a PDF invoice is a visual image of an invoice that only humans can read. When a buyer receives an EHF invoice, their accounting or ERP system reads the XML data directly — supplier name, invoice number, date, VAT amounts, line items, payment details — and creates the payable record in their system without any human intervention. When a buyer receives a PDF invoice, an accounts payable clerk must read the PDF and manually type all the invoice data into their system.
This is the structured e-invoice difference that drives the economics of EHF adoption. A large Norwegian public sector buyer that receives 50,000 invoices a year processes them all automatically in EHF — the cost per invoice is a fraction of a cent. Processing the same volume as PDFs would require dozens of AP clerks. For sellers, the benefit of EHF is that invoices processed automatically are approved and paid faster than invoices waiting in an AP queue to be manually entered. Average payment time for EHF invoices to Norwegian government buyers is significantly shorter than for PDF alternatives processed through workaround channels. Businesses looking to automate this process can explore EHF invoice processing to understand how electronic invoice workflows can support structured invoice exchange.
| Invoice Characteristic | EHF Faktura | PDF Invoice |
|---|---|---|
| Format | Structured XML (UBL 2.1 or CII) — Peppol BIS Billing 3.0 | Unstructured image — PDF, scanned paper, Word saved as PDF |
| Data readability | Machine-readable buyer ERP processes automatically |
Human-readable only — requires manual data entry at buyer |
| Delivery channel | Peppol network via certified access point | Email attachment or postal mail |
| Delivery confirmation | AS4 acknowledgement from buyer access point within seconds | No confirmation — you do not know if buyer received the PDF |
| Pre-send validation | Access point validates NO-R rules and Peppol BIS schema |
No validation — errors discovered only when buyer reads PDF |
| B2G compliance in Norway | Required — all public sector invoicing must use EHF |
Not compliant — rejected by Norwegian government buyers |
| B2B compliance in Norway | Voluntary 2026; expected mandatory from 2027 | Acceptable for B2B in 2026; deadline approaching |
| Processing at buyer | Automatic — ERP posts invoice without human input |
Manual — AP clerk reads PDF and keys data into system |
| Payment speed | Faster — automated processing shortens AP cycle | Slower — manual queue; data entry errors cause further delays |
| Archive | Electronic archive with Peppol delivery confirmation |
Email archive only; no structured delivery proof |
Is a PDF Invoice Valid Under Norway's E-Invoicing Rules?
A PDF invoice is not valid for B2G invoicing in Norway. Under Norwegian e-invoicing regulations implementing EU Directive 2014/55/EU, all invoices to Norwegian public sector bodies must be structured electronic invoices delivered via the Peppol network. A PDF sent by email — regardless of how professionally formatted — is not a structured e-invoice and is not compliant with Norwegian government e-invoicing requirements. If you send a PDF to a Norwegian municipality, ministry, hospital or university, the invoice will be rejected and payment withheld until you resubmit as a proper EHF Faktura vs PDF Invoice-compliant EHF via Peppol.
For B2B transactions between private Norwegian companies, PDF invoices remain legally acceptable in 2026 — the B2B e-invoicing mandate has not yet been enacted. However, many large Norwegian private sector buyers are already requesting EHF invoices from their suppliers for AP efficiency reasons. As the B2B mandate approaches (expected 2027 for larger businesses), the window for using PDF as your default B2B invoicing method is closing. Businesses that switch to EHF now avoid a future forced migration and start benefiting from Norwegian e-invoice benefits immediately. Businesses using QuickBooks can explore options for supporting structured electronic invoicing within their accounting workflow.
What Is the EHF Faktura Format and How Does It Work?
The EHF faktura format is a Peppol BIS Billing 3.0 XML document with Norwegian NO-R business rules applied. For the EHF Faktura vs PDF Invoice format comparison: an EHF invoice file is an XML text document, typically 3-20 KB in size, containing all invoice data in a structured hierarchy of XML elements. The key elements are: invoice header (type, number, date, currency), seller information (name and 9-digit Organisation Number with scheme 0192), buyer information (name and Organisation Number), VAT breakdown by rate (25%, 15%, 12%, 0%), line items (description, quantity, unit price, VAT code) and payment details (IBAN, OCR reference, due date).
The EHF faktura format is created by your accounting software or passed to a Peppol access point that creates it from your invoice data. Most Norwegian businesses never see the raw XML — their accounting software shows them a normal invoice creation screen and the EHF XML is generated and transmitted automatically when they click "Send." For businesses using international MYOB accounting software, a Peppol access point provider takes invoice data via API and handles EHF XML creation and Peppol delivery. The format difference from PDF is invisible to the user but decisive for buyer processing efficiency.
| EHF Faktura Format Element |
Content | Why It Is Structured Data |
|---|---|---|
| Invoice type code | 380 (standard invoice) or 381 (credit note) | Numeric code — system knows invoice type without reading text |
| Seller ID (0192:ORGNUMBER) | 0192:123456789 | Scheme + 9-digit Org Number zero ambiguity; routes automatically in ELMA |
| Buyer ID (0192:ORGNUMBER) | 0192:987654321 | Identical format buyer ERP matches to vendor record automatically |
| Tax category code | S (standard), Z (zero-rated), E (exempt) | System codes — buyer VAT engine processes without human interpretation |
| VAT amount per line | Numeric; 2 decimal places; e.g. 250.00 | Exact numeric value no rounding or calculation required at buyer |
| Payment ID (KID/OCR) | 12-22 digit modulus-10 reference | Auto-match bank statement to invoice at buyer without clerk lookup |
How Do Structured E-Invoices Differ From PDF Invoices in Practice?
The practical EHF Faktura vs PDF Invoice process difference for a Norwegian AP department: when an EHF invoice arrives via Peppol, the buyer's ERP system receives the XML, validates it against their vendor master and purchase order records, and either auto-approves the invoice for payment (if it matches a PO) or creates a workflow task for approval (if no PO match). The AP clerk's only job is to review exceptions — the majority of EHF invoices are processed without any AP intervention in a well-configured Oracle ERP. Payment runs execute against approved EHF invoices automatically on the due date.
For a PDF invoice, the AP process is: email arrives in the AP inbox, clerk opens the PDF, reads supplier name and looks up vendor record, reads invoice number and checks for duplicates, reads and enters invoice date, reads and enters each line item, calculates VAT and enters totals, enters payment reference — then routes the manually-created payable for approval. Every step is manual and every step is a potential source of error. Data entry errors in PDF processing cause payment delays (wrong bank account, wrong amount), fraud risk (misrouted payments) and AP cost that EHF eliminates completely.
Is an E-Invoice Sent by Email Compliant in Norway?
This is a critical EHF Faktura vs PDF Invoice distinction: an e-invoice sent by email — whether as a PDF attachment, an XML attachment or any other email-delivered document — is NOT compliant with Norwegian B2G e-invoicing requirements. "Electronic invoice" in the context of Norwegian law means a structured electronic invoice delivered via the Peppol network, not any document sent electronically. The Peppol network provides the delivery infrastructure, participant registry (ELMA) and AS4 transport protocol that Norwegian regulations require — email has none of these.
Some suppliers and buyers in Norway use "PDF via email" and call it "electronic invoicing" colloquially, but this is not what Norwegian e-invoicing law requires. The e-invoice vs email invoice distinction is: a true Norwegian e-invoice (EHF/Peppol) is a structured XML document delivered through the certified Peppol four-corner network with AS4 acknowledgement. An email invoice — even with an XML file attached — does not use the Peppol network and does not generate the ELMA-based routing and delivery confirmation required by Norwegian regulations. For B2G compliance, Peppol delivery is non-negotiable.
What Are the Benefits of EHF Invoices for Norwegian Businesses?
Norwegian e-invoice benefits for businesses sending EHF invoices include: faster payment processing by public sector and large private buyers (automated AP shortens approval and payment timelines significantly); guaranteed delivery confirmation (Peppol AS4 acknowledgement proves the invoice was received — no more "we never received your invoice" disputes); reduced rejection risk (EHF is validated by your access point before sending, catching errors before they reach the buyer); lower invoicing cost at scale (no printing, enveloping, postage or email management); and compliance-ready archive (EHF Peppol delivery logs satisfy the Norwegian Bookkeeping Act 5-year retention requirement). Understanding the EHF Faktura vs PDF Invoice tradeoffs makes the case for EHF clear.
For buyers, Norwegian e-invoice benefits are even more substantial: automated AP processing eliminates manual data entry cost; early payment discounts are more achievable when invoice approval is automated and predictable; duplicate invoice detection is automatic (same invoice number from same supplier Organisation Number is flagged); VAT reclaim processing is faster when structured VAT data flows directly into the tax system. For ecommerce businesses, Shopify e-invoicing integration can help connect sales transactions with electronic invoicing workflows.
How Can Businesses Choose Between EHF and PDF Invoicing?
The EHF Faktura vs PDF Invoice choice is being made for many Norwegian businesses by regulation and market pressure. For any business that invoices Norwegian public sector bodies — the choice is already made: EHF is mandatory. For businesses that invoice large Norwegian private companies, EHF is increasingly preferred or required as a commercial condition by sophisticated buyers. For businesses that invoice only small private Norwegian companies or consumers, PDF remains acceptable in 2026 — but the window is shortening as the B2B mandate approaches.
The practical question is not whether to adopt EHF but when and how. Norwegian accounting software (Fiken, Tripletex, Visma, PowerOffice) includes EHF sending built-in with minimal setup. For international accounting software users, a Peppol access point provider adds EHF capability via API integration in 1-3 weeks. The cost of EHF invoicing (access point subscription: typically NOK 100–500/month) is repaid many times over in faster payment, reduced AP admin and zero printing costs. Businesses can also explore e-invoicing solutions in Australia to understand electronic invoicing options for Australian businesses.
Conclusion
The EHF Faktura vs PDF Invoice comparison has a clear winner for Norwegian businesses: EHF Faktura is the compliant, efficient and future-proof choice. PDF invoice Norway compliance has ended for B2G invoicing and will end for B2B when the mandate arrives. Norwegian e-invoice benefits — speed, automation, error reduction, delivery confirmation and archive quality — make EHF the superior invoicing method on every dimension. The structured e-invoice difference is fundamental: machine-readable data processed automatically beats a visual image requiring manual entry every time. Adopt EHF now through Norwegian accounting software or a certified Peppol access point, and your invoicing infrastructure is ready for both current and future requirements.
FAQs
Can Norwegian businesses still use paper invoices in 2026?
Paper invoices are not compliant for B2G invoicing in Norway and will be rejected by public sector buyers. For B2B invoicing, paper invoices remain legally acceptable in 2026 but are commercially impractical — postage cost, delivery delays and the absence of any electronic record make them a poor choice. Most Norwegian businesses that still use paper have already moved to PDF or EHF for practical reasons. With the B2B e-invoice mandate approaching, paper is a practice worth eliminating now.
Does a scanned PDF count as an EHF invoice?
No. A scanned PDF is the least structured invoice format available — it is an image of a paper invoice, often with lower readability than a digitally created PDF. A scanned PDF is not an EHF invoice, not a structured e-invoice and not compliant with Norwegian B2G e-invoicing requirements. EHF invoices are XML documents with structured data, not images of any kind. Buyers that receive scanned PDFs cannot process them automatically and Norwegian public sector buyers will reject them entirely.
If my buyer requests EHF but I only have PDF invoicing, what should I do?
Contact a Norwegian accounting software provider (Fiken, Tripletex, Visma) or a Peppol access point provider and arrange EHF invoicing setup. This typically takes 1-3 weeks and costs NOK 100-500/month depending on invoice volume and provider. Do not attempt to "convert" a PDF to XML — proper EHF invoicing requires structured data from your accounting system, not a PDF conversion tool. Your access point provider will guide you through the Organisation Number and ELMA registration steps as part of onboarding.
Is there a way to send both EHF and PDF for the same invoice?
Some Peppol access point providers and accounting software platforms generate both an EHF XML delivered via Peppol and a human-readable PDF version attached to a notification email. The EHF XML is the legally valid invoice for Norwegian B2G purposes; the PDF is a convenient reference copy for the buyer. This dual-format approach is common in practice and means buyers can read the invoice details without navigating their ERP, while the EHF XML processes automatically in the background.
When will PDF invoices become non-compliant for Norwegian B2B invoicing?
The Norwegian B2B e-invoicing mandate is expected to make EHF mandatory for larger businesses from approximately 2027 and for all businesses from approximately 2030. The exact dates depend on the legislative process, which was ongoing as of late 2026. When enacted, the mandate will require structured electronic invoices via Peppol for B2B transactions — PDF invoices will cease to be compliant. The EHF Faktura vs PDF Invoice comparison will have a definitive regulatory answer once the B2B mandate legislation is enacted.
Source by:
Image by Magnific
