ERP Implementation Consultant, Sweden

Where Swedish ERP rollouts tend to slip

Swedish projects seldom fail on a dramatic technical problem. They drift in quieter ways, and most of them can be predicted from the first planning meeting.

• The accountant joins too late. The chart of accounts and VAT codes are configured by the implementer, and the accounting firm sees the result only when the first SIE file arrives at quarter end. Corrections then touch every posted transaction.
• Payment references are treated as cosmetic. If invoices do not carry OCR references the bank can return, customer payments land unmatched and receivables work doubles.
• Peppol is switched on at the last minute. Sending to public buyers gets tested, but receiving supplier invoices in the new system is forgotten until bills stop arriving.
• Payroll is assumed to be someone else's job. The payroll provider keeps running, but nobody has tested whether its journal file posts cleanly into the new dimensions.
• Swedish-language outputs are discovered in the final week. Invoice texts, reminder letters and delivery notes need translation and approval, and arrive untested.

I build each of these into the plan from the start, with an owner and a test. The requirement work behind them is described on the ERP business analyst page for Sweden.

Overseeing the implementer without slowing the project

Good Swedish implementers welcome an organized client counterpart, because decisions get made faster and scope disputes shrink. My role is not to second-guess every setting. It is to make sure the business has read, understood and agreed what is being built.

In practice that means a few routines. Each design area, such as sales, purchasing, stock or finance, gets a short design document that the process owner signs before configuration starts. The implementer demonstrates each build iteration on your scenarios, and I note where the result departs from the requirement. New requests go into a change log with an estimate and the sponsor's decision, rather than being absorbed quietly into the budget.

I pay particular attention to the Swedish localization layer. If it comes from a separate app or the implementer's own extension, I want to know who maintains it, how updates are tested and whether your support agreement covers it when file formats change. Those answers shape the risk register and the handover.

For platform-specific questions I often refer to the notes on Odoo Accounting in Sweden and Business Central in Sweden. The general method is on my ERP implementation page.

Bringing data across from Fortnox, Visma and older systems

Many Swedish companies arrive at an ERP from a cloud accounting service such as Fortnox or a Visma product, sometimes alongside a separate stock or order tool. Others leave an older on-premise system that has been customized over many years. Each source needs a slightly different migration plan.

An SIE export from the old system is useful, but it is not the whole migration. It carries the ledger, balances and, depending on the file type, transactions. It does not normally carry open customer and supplier items with their due dates and payment references, item master data, price lists, open orders or attachments. Those come through separate exports and templates, and each needs its own reconciliation.

I agree with your finance lead and accountant what moves in detail and what stays as history in the old system or an archive. Then every trial load is checked: trial balance by account, aged receivables and payables against control accounts, stock quantities and values against the last count, and a sample of customers and suppliers against source records. Differences get an owner and an explanation before the next load.

Old vouchers and attachments must stay accessible for as long as Swedish rules require, so the archive decision is confirmed with your accountant. My ERP data migration service and the migration checklist cover the wider method.

Go-live details specific to Sweden

A Swedish cutover has a few moving parts that generic plans miss. I write them into the runbook with named owners and rehearse them where the platform allows.

• Period boundaries. Going live mid-year is common and workable, but the cutover point should line up with a VAT reporting period and a closed month in the old system. Your accountant agrees how provisional balances are trued up later.
• Peppol receiving. Incoming e-invoices follow your registration on the network, and a registration generally points to one access point at a time. Moving it from the old provider to the new one needs a planned date so supplier invoices are not lost in between.
• Bank files and OCR. The bank needs to deliver payment and statement files to the new system, and invoices from the new system must carry references the bank recognizes.
• Payroll handoff. The payroll provider's journal file is mapped to the new accounts and dimensions and tested with a real pay run before the switch.
• Last documents from the old system. Number series, credit notes against old invoices and open orders all need a rule.

Confirm current e-invoicing and bank requirements with your providers and advisor. The wider cutover method is on my ERP go-live support page.

Testing, Swedish training material and hypercare

Testing is where a Swedish rollout either earns trust or loses it. I write end-to-end scripts with your process owners and include the local cases: an SIE export checked by the accountant, a Peppol invoice to a public buyer, an OCR payment matched from a bank file, a reverse-charge purchase confirmed by your advisor, and a payroll journal posted to the right cost centers. Business users run them, and defects are triaged with the implementer as defect, design gap, training need or new request.

The engagement runs in English. Training material for staff who prefer Swedish is written or adapted by your own team or a local partner, usually by key users who took part in UAT, because they know both the system and the vocabulary your people use. I review the content for process accuracy and make sure Swedish invoice texts and letters are tested like any other output.

After go-live, hypercare runs on a shared issue log and a short daily call while the first weeks settle. It continues through the first VAT period and month-end close, so the first handover to your accounting firm is checked before it is sent. Testing methods are covered on my ERP testing and UAT page. If you are still choosing a system, start with the ERP selection consultant page for Sweden or return to the Sweden overview. All of this is delivered remotely, with visits only by arrangement.