Independent NetSuite consultancy · London, UK
NetSuite consultant for Swedish and Nordic subsidiaries.
If your group runs NetSuite OneWorld and has a company in Sweden, Norway, Denmark or Finland, the first question is simple: does that entity live in NetSuite, or does it keep a local ledger such as Fortnox that feeds NetSuite? I help you choose, then build it so the Nordic books stay compliant and the group sees one set of numbers.
I built a native SuiteScript 2.1 integration between NetSuite and Fortnox for Cape.io across eight OneWorld subsidiaries, so this page draws on real work rather than theory.
When you need this
You are adding a Swedish or Nordic subsidiary to NetSuite OneWorld, your Swedish team wants to keep Fortnox, or your Nordic entities need Peppol e-invoicing and local tax reports that tie back to the group ledger.
What I cover
- Fortnox or NetSuite: which ledger for the Swedish entity
- Native NetSuite ↔ Fortnox integration in SuiteScript 2.1
- Swedish VAT reports and SIE files
- Peppol e-invoicing for public-sector customers
- Norway's 2027 B2B e-invoicing requirement
- SEK, NOK, DKK and EUR consolidation in OneWorld
The first decision
Keep Fortnox, or move the Swedish entity into NetSuite OneWorld?
Many groups inherit Fortnox when they buy or open a Swedish business. Neither answer is always right; these are the signs I look for.
Keep Fortnox and integrate it when
- A Swedish accounting firm keeps the books in Fortnox and wants to carry on
- Local e-invoicing and Skatteverket reporting already run well from Fortnox
- The entity is small, stable or recently acquired, and the group mainly needs consolidated numbers
Move it into NetSuite when
- The group wants one order-to-cash and procure-to-pay process across every country
- Two ledgers mean double entry, timing differences or month-end reconciliation work
- The entity trades heavily with other group companies, or you are adding more Nordic entities
If you keep Fortnox, the integration has to be audit-grade: every account and VAT code mapped explicitly, and failures shown to finance, not hidden. I explain how I approach it in integrating NetSuite with Fortnox: a native, audit-grade approach.
Swedish statutory and tax reporting in NetSuite
A Swedish company files VAT returns (momsdeklaration) with Skatteverket monthly, quarterly or annually, plus an EC sales list (periodisk sammanställning) for EU sales. The accountant and auditor will also expect accounting data in SIE format, the Swedish open standard for moving accounting data between systems.
If the entity runs in NetSuite, Oracle provides the building blocks:
- Sweden VAT reports through Oracle's International Tax Reports, or SKV4700 and Intrastat through the Sweden Tax Reports SuiteApp where you use SuiteTax
- SIE file generation in the Sweden Localization SuiteApp (see Oracle's SIE file generation guide)
If the entity stays on Fortnox, Fortnox remains the source for local reporting. Its API can return a SIE file under the bookkeeping scope (Fortnox developer documentation), which is useful for reconciling the two ledgers. On Cape.io, the Swedish team kept Fortnox for local e-invoicing and Skatteverket reporting, while VAT reconciled line by line between SuiteTax and Fortnox.
Filing deadlines depend on the company's size and accounting year, so confirm them with your Swedish accountant or auditor.
E-invoicing: Peppol for the public sector, Svefaktura and Norway's 2027 rule
Sweden. Public-sector buyers and their suppliers must exchange e-invoices in Peppol BIS Billing 3 for procurements started after 1 April 2019. The Swedish procurement agency notes that Svefaktura cannot be carried over the Peppol network and needs to be phased out (Upphandlingsmyndigheten). B2B e-invoicing is not yet mandatory; a government inquiry into domestic e-invoicing and the EU's ViDA package is due to report by 30 November 2027.
Norway. From 1 January 2027, businesses with bookkeeping obligations must issue e-invoices to other such businesses, in EHF Billing or Peppol BIS Billing version 3.0 or later (Skatteetaten). This is the nearest hard deadline for most Nordic groups.
Denmark and Finland. Oracle's EU Electronic Invoicing SuiteApp handles Danish Peppol invoices, credit memos, vendor bills and vendor credits in both directions (Oracle documentation). Finland requires EN 16931 e-invoices for the public sector, and businesses with turnover above €10,000 can ask their suppliers for e-invoices.
For Sweden, Norway and Finland, NetSuite reaches Peppol through an access point; the work is mostly in clean buyer identifiers, VAT codes and units. The wider picture is on my NetSuite e-invoicing and tax reporting page and the NetSuite e-invoicing by country table.
Multi-currency and consolidation across SEK, NOK, DKK and EUR
Sweden reports in SEK, Norway in NOK, Denmark in DKK and Finland in EUR. In NetSuite OneWorld each subsidiary keeps its own base currency, and the parent consolidates using the consolidated exchange rates table, with average, current and historical rates applied to the right accounts.
Two things I check on every Nordic set-up:
- Intercompany. Nordic entities often sell services to each other and to the parent. Intercompany items, accounts and elimination rules need agreeing early so consolidated figures are right first time.
- Two-ledger currency handling. Where Fortnox stays, every transaction must carry its currency code and exchange rate. On Cape.io, SEK, EUR, GBP, USD, NOK and AUD were each mapped to their NetSuite equivalents.
A native NetSuite ↔ Fortnox integration across eight subsidiaries
Cape.io runs NetSuite OneWorld across eight subsidiaries in Japan, the UK, Sweden, France, Germany, Hungary, Italy and Poland. I led a bidirectional integration with Fortnox built entirely in SuiteScript 2.1, with no iPaaS. It syncs six entity types: customers, suppliers, sales invoices, credit memos, journals, and customer and supplier payments.
- 256 GL accounts mapped explicitly; unmapped accounts fail loudly rather than defaulting
- Swedish VAT mapped between SuiteTax and Fortnox: 25, 12 and 6%, EC reverse charge and exports
- A last-sync hash on every transaction to stop echo loops, and the Fortnox document number stamped back on each NetSuite record
How I can help
Typical engagements for Nordic subsidiaries:
- Ledger decision and design. A short review of the Swedish or Nordic entity: Fortnox or NetSuite, chart of accounts, VAT codes, intercompany and consolidation.
- Fortnox integration. A native SuiteScript 2.1 build, or a review of an existing one, through my NetSuite integration services. If a current integration keeps failing, the Integration Rescue Sprint stabilises it in one to two weeks.
- Peppol and local tax reports. Access point choice, Norway's 2027 requirement and Swedish VAT and SIE outputs, through NetSuite e-invoicing compliance.
- Monitoring. See how failed records can be watched and replayed in the Integration Control Tower demo.
FAQ
NetSuite in Sweden and the Nordics: common questions.
Should our Swedish subsidiary keep Fortnox or move into NetSuite?
It depends on who keeps the Swedish books and how much the entity trades. If a local accountant runs Fortnox and the entity is small or stable, keeping Fortnox and integrating it is usually the lower-risk choice. If the group wants one process, one chart of accounts and fewer systems, moving the entity into NetSuite OneWorld with the Sweden Localization SuiteApp is cleaner. I help you weigh the two before anyone builds anything.
Can NetSuite produce a SIE file?
Yes. Oracle's Sweden Localization SuiteApp can generate an SIE file, the open standard Swedish accountants and auditors use to move accounting data between systems. Fortnox can also provide SIE files through its API.
Do we have to send e-invoices to Swedish public-sector customers?
Generally, yes. Sweden's public-sector rules require e-invoices in Peppol BIS Billing 3 for procurements started after 1 April 2019. Svefaktura cannot travel over the Peppol network and is being phased out. In NetSuite this goes through a Peppol access point. Check your contracts and your adviser for your exact position.
What changes in Norway in 2027?
From 1 January 2027, businesses with bookkeeping obligations must issue e-invoices to other such businesses, using EHF or Peppol BIS Billing version 3.0 or later. If you have a Norwegian subsidiary, now is the time to confirm your access point and test the flow.
How do you handle SEK, NOK, DKK and EUR in one group?
Each Nordic subsidiary keeps its own base currency in NetSuite OneWorld, and the group consolidates into its reporting currency using NetSuite's consolidated exchange rates. Where a local ledger such as Fortnox stays in place, the integration carries the currency code and exchange rate on every transaction, as it did on the Cape.io project.
Keep reading
Related case study, insight and demo.
Cape.io
NetSuite and Fortnox kept in step across eight OneWorld subsidiaries, natively in SuiteScript 2.1.
Read the case study →NetSuite and Fortnox integration
Bidirectional sync, audit-grade account and VAT mapping, and echo-loop protection.
Read the insight →Live demo: Integration Control Tower
Queues, mappings and replay for integrations like NetSuite ↔ Fortnox.
Try the demo →Adding a Nordic company to NetSuite?
Book a free 30-minute call. Tell me about the entity and its accountant, and I'll tell you honestly whether Fortnox should stay and what the set-up will take.