If you send invoices to other Norwegian businesses, your PDFs stop counting on January 1, 2027. From that date, every business-to-business invoice you issue must travel as a structured electronic file — not a PDF attached to an email, but machine-readable data your customer's accounting system can ingest without a human retyping a single line. Norway's government just moved that deadline forward by a full year, and the practical window to get ready is now roughly a year, not two. Here is what the mandate requires, who it catches, and the checklist that gets you compliant in time.
The announcement in 60 seconds
On March 16, 2026, Norway's Ministry of Finance announced it will put a bill before parliament (the Storting) making B2B e-invoicing and digital bookkeeping mandatory for Norwegian businesses. The proposal follows a public consultation that ran in the summer of 2025 — and it contains one surprise: the deadline for mandatory e-invoice issuance moved from January 1, 2028 to January 1, 2027, a full year earlier than consulted on.
The government's stated reason is Norway's digital maturity: Norwegian businesses are already so digitized, and the national e-invoicing infrastructure so established, that waiting until 2028 buys little and delays the payoff. Whether or not you share that confidence about your own systems, the direction is set — the bill is expected to move through parliament during 2026, with the Tax Administration (Skatteetaten) writing the detailed implementing rules afterward.
The two-phase timeline
The mandate arrives in two waves. Confusing them is the single most expensive mistake you can make, so pin this to your wall:
Phase 1 — January 1, 2027: you must SEND structured e-invoices. Every B2B invoice your business issues has to be a structured electronic invoice in the approved national format. Emailing PDFs, paper invoices, and portal uploads that produce unstructured documents will no longer satisfy your invoicing obligation toward business customers.
Phase 2 — January 1, 2030: you must RECEIVE them too, inside a digital accounting system. From 2030, bookkeeping-obligated businesses must use an electronic accounting system capable of receiving and automatically processing e-invoices — plus meet a broader digital bookkeeping requirement. The 2027 duty is one-directional (outbound); the 2030 duty closes the loop (inbound plus systems).
Note the asymmetry working in your favor early: in 2027 your customers are not yet legally required to be able to receive your e-invoices automatically. In practice, though, most Norwegian accounting systems already handle structured invoices, and sending compliant files from day one means you never have to run two invoicing processes in parallel.
What counts as a "real" e-invoice
This is where small businesses get tripped up, because the everyday meaning of "electronic invoice" and the legal meaning are different things:
- A PDF sent by email is NOT an e-invoice under the mandate — even if your accounting software generated it. It is an unstructured document a human still has to read.
- A real e-invoice is structured data: a file in a standardized machine-readable format that flows directly from your system into your customer's system, carrying every legally required invoice field (seller and buyer identity, line items, VAT amounts, totals) as tagged data, not pixels.
Norway's proposed standard format is EHF (Elektronisk handelsformat), the Norwegian national format built on the Peppol network — specifically EHF Billing 3.0, which implements the European e-invoicing standard EN 16931. For cross-border invoices, the underlying Peppol BIS Billing 3.0 format applies. In practice the journey of an invoice looks like this: your ERP or accounting system creates the structured file, sends it through a certified Peppol access point, the network looks up your customer in the ELMA registry (Norway's electronic address directory), and the invoice lands directly in the customer's accounting system.
If you already invoice the Norwegian public sector, this will sound familiar: structured EHF invoicing for government suppliers has been required for years. The 2027 mandate essentially extends the discipline the public sector already demands to all business-to-business trade.
Who is in scope — and who is out
The mandate is expected to cover all businesses with bookkeeping obligations (bokføringspliktige). That is a broad net:
- Limited companies (AS) and other companies with statutory bookkeeping duties
- Sole traders (enkeltpersonforetak) above the bookkeeping threshold
- State-owned enterprises, financial institutions, investment funds, larger cooperatives and associations, housing cooperatives, and foundations
Two carve-outs matter:
- B2B only — for now. Invoices to private consumers and cash sales are outside the mandate at this stage. If you run a pure consumer-facing shop with no business customers, 2027 does not touch your invoicing (though read the "still undecided" section below before relaxing completely).
- The micro-business exemption. Businesses with annual turnover below NOK 50,000 (roughly €4,300) that have neither accounting nor VAT registration obligations are expected to be exempt. This is a genuinely small-business floor: if you are VAT-registered or keep statutory accounts, assume you are in scope regardless.
The exact conditions of the small-business exemption will be nailed down in the implementing regulations — another reason to follow Skatteetaten's publications through 2026 rather than assuming you qualify.
What is still undecided
The March announcement is a bill proposal, not the final rulebook. Three things remain open, and each affects your planning:
- The parliamentary vote. The Storting must pass the bill. Given the consultation history and cross-party support for digitization, passage is widely expected — but until it happens, treat timelines as near-certain rather than certain.
- The implementing regulations. After parliament approves the bill, Skatteetaten drafts the technical detail: the finally approved invoice format, transmission requirements, archiving rules, and the precise small-business exemption conditions. Expect these during 2026. Your software vendor's compliance roadmap depends on them, so ask your vendor what they are waiting for and when they will ship it.
- The scope-expansion study. Alongside the announcement, the Ministry ordered the Tax Administration to investigate extending the mandate beyond B2B — to consumer transactions, mandatory digital sales receipts (e-receipts), and possibly regulatory requirements for accounting-system providers themselves. That report is due by December 2026. If you sell to consumers, the 2027 mandate may not touch you — but the 2026 study will tell you whether a B2C wave is coming next. Do not rebuild your point-of-sale invoicing in 2026 in a way you would have to tear out in 2028.
Your readiness checklist for January 2027
With roughly a year of practical implementation time, here is the sequence that works, in order:
1. Confirm you are in scope
Are you bookkeeping-obligated? Are any of your customers businesses rather than consumers? Is your turnover above NOK 50,000 or are you VAT-registered? Three yeses — or even two — means you prepare as if covered. Document the conclusion; if you claim the micro-exemption later, you will want the working papers showing why.
2. Audit how you invoice today
List every way an invoice currently leaves your business: accounting software, manual Word or Excel templates, invoicing apps, agent or marketplace payouts, recurring-billing tools. Every channel that produces PDFs, paper, or emails must be migrated or retired for B2B sales. Businesses usually discover at least one forgotten channel — the service technician emailing invoices from the road is the classic.
3. Ask your accounting vendor the hard questions
Can your system issue EHF 3.0 invoices today, or is compliant output on the roadmap with a ship date before year-end? Does it include Peppol connectivity (an access point) or require a separate provider? What does the upgrade cost, and does your current plan include it? Get answers in writing. If your vendor is vague, that vagueness is itself an answer — start evaluating alternatives now, while switching is a choice rather than a panic.
4. Arrange Peppol connectivity
If your accounting system does not bundle it, contract a certified Peppol access point provider and register your business in the ELMA directory so customers' systems can find you. This is plumbing, not strategy — but plumbing installed in December fails at the worst moment. Do it in the autumn and send test invoices to a friendly customer.
5. Clean your master data
Structured invoices reject what humans forgive. Validate every business customer's organization number (organisasjonsnummer), legal name, and registered address; fix your own company details, VAT number, and bank/account information in your system. Bad master data is the number-one cause of rejected e-invoices in every country that has mandated them — and a rejected invoice is, legally, an invoice you have not properly issued.
6. Rebuild approval and archiving workflows
Map who approves what before an invoice goes out, and confirm your archive stores the structured file, not just a PDF rendering — auditors and tax authorities will want the machine-readable original. Norway already operates SAF-T-based accounting data exchange with Skatteetaten, so assume your invoice data will eventually be cross-checked against filed figures. Archive like someone will reconcile it, because someone will.
7. Onboard your trading partners early
Tell your regular business customers when you will switch, and ask your suppliers when they will. A mandate with a hard date creates a December pile-up of everyone testing at once; businesses that coordinate in September and October get their counterparties' attention while it is still available.
8. Budget for 2030 while you are at it
If your current setup can send but not automatically receive and process e-invoices, you have a second project waiting: the 2030 digital-bookkeeping and receipt mandate. Choosing 2027 tooling that already handles inbound automation turns two migrations into one. Ask every vendor you evaluate about their 2030 readiness, not just 2027.
Common mistakes to avoid
- "Our PDFs are electronic, so we are fine." No — unstructured documents do not satisfy a structured-data mandate. This misunderstanding is the most common and the most dangerous.
- "The deadline is 2030." No — 2030 is receipt plus digital bookkeeping. Issuance starts 2027. Planning for 2030 means missing 2027 by three years.
- "Our accountant handles invoicing." Your accountant cannot issue compliant invoices from a system that cannot produce them. Responsibility stays with your business; capability must live in your systems.
- "We only have a few business customers." One in-scope invoice stream is enough to trigger the obligation. Volume affects cost, not coverage.
- "We will sort out archiving later." Later is when the auditor asks for the structured originals. Store them from the first compliant invoice.
Keep your books mandate-ready
E-invoicing mandates reward businesses whose underlying records are already clean: correct organization numbers, separated revenue streams, reconciled accounts. Every checklist item above gets easier when your chart of accounts is tidy and your customer master data is accurate — and much harder when invoices, receipts, and bank transactions live in disconnected piles. As Norway's requirements tighten through 2027 and toward 2030, maintaining clear, complete financial records is essential. Beancount.io provides plain-text accounting that gives you complete transparency and control over your financial data — no black boxes, no vendor lock-in. Get started for free and see why developers and finance professionals are switching to plain-text accounting.
