ERP Business Analyst in Sweden

SIE files, account plans and the accounting firm

When an external accounting firm stays involved in bookkeeping, closing or annual reporting after an ERP goes live, the relationship depends on clean data exchange, and Sweden has a long-standing standard for it: the SIE file format. Whether a new platform can produce and read the right kind of SIE file, with the right content, is a requirement, not a detail for later.

With your finance lead and your accountant, I document:

• Which SIE file types the accounting firm needs, how often and for which periods.
• Whether your account plan follows the BAS structure your accountant works with, and how any group chart of accounts maps onto it.
• Which dimensions, such as cost centers, projects or departments, must travel with the transactions.
• How opening balances and historical periods are loaded at migration.
• Who locks periods, and how late adjustments from the accountant flow back into the system.

During demonstrations I ask each vendor to export a file from realistic test data so your accountant can open it in their own tools. That single test can separate platforms with a mature Swedish localization from those relying on a generic export. The broader platform view is on my Odoo in Sweden and Dynamics 365 in Sweden pages.

Peppol invoices, payment references and bank flows

If you sell to municipalities, regions or government agencies, they will generally expect structured electronic invoices, commonly sent over the Peppol network, rather than PDFs. Some private buyers ask for the same. That turns invoice delivery into a requirements topic: how the ERP sends invoices, through which access point or connector, how buyer references and order numbers are captured, and how rejections are handled.

The other side of the cash cycle matters just as much. Swedish invoices often carry a structured payment reference so incoming payments can be matched automatically, and suppliers are paid through bank files. I write requirements covering:

• Generating payment references on outgoing invoices and matching them against bank statements.
• Supplier payment runs, approval steps and the bank file format your bank accepts.
• Receiving supplier invoices electronically and routing them for approval.
• Multi-currency receipts, for exporters invoicing in euros or dollars.

Each requirement becomes a test case: send an invoice to a public buyer in a test environment, import a bank statement, run a payment proposal. Rules and formats change, so current requirements should be confirmed with your bank, your accountant or the receiving organization. For how these topics fit into the whole decision, see my ERP consultant page for Sweden.

VAT treatments and sector rules worth writing down

Most platforms handle a standard sale with Swedish VAT. Fit is decided by the less common transactions, and those are the ones people forget to mention in a sales meeting. I build a plain-language inventory of every VAT treatment and sector rule the business actually uses, then ask your accountant or tax advisor to confirm it before it becomes a requirement.

Depending on your business, that inventory can include:

• Sales of goods and services to customers in other EU countries, and the reporting that follows from them.
• Purchases from abroad where reverse charge applies.
• Construction services where the domestic reverse charge applies between businesses in the sector.
• Household work for private customers, where tax deductions such as ROT or RUT affect how the invoice is built and how the remainder is claimed.
• Mixed invoices, credit notes, prepayments and deposits.

I do not decide how any transaction is taxed. My role is to make sure every case your advisor confirms appears in the BRD, the fit-gap matrix and the UAT scripts, so nobody discovers a missing scenario after go-live. The requirements gathering page describes how these inventories are built.

Subsidiaries, group reporting and payroll interfaces

Swedish entities owned by international groups have a dual reporting life. Locally, the books must satisfy Swedish rules and the accountant. Upward, the parent wants figures in its own structure, currency and calendar. When the ERP choice is made centrally, the Swedish requirements are easy to overlook, and when it is made locally, group reporting becomes a monthly spreadsheet exercise.

My requirements work covers both directions. I map local accounts and dimensions to the group chart, document intercompany sales, recharges and loans, and record the timing the group close imposes on the Swedish team. Where the parent already runs a platform, the fit-gap analysis checks what its Swedish localization covers and what must be added.

Payroll usually runs through a specialist Swedish payroll provider rather than inside the ERP. The requirements then focus on the interface: how salary journals arrive, at what level of detail, with which cost centers or projects, and how expense claims and time records feed payroll. Employee personal identity numbers and HR data fall under GDPR, so the BRD also states which data the ERP really needs to hold, who can see it and how long it is kept.

English-language analysis with Swedish review

All interviews, workshops and documents are in English. Where Swedish is needed, such as invoice texts, reminder letters, customer-facing labels and short procedures for warehouse or service staff, bilingual members of your team or a local partner produce or check those items. The BRD lists them with owners and due dates relative to the plan, so they are not discovered during the final week of testing.

For people who are hard to pull into meetings, such as field technicians or production leads, I use short questionnaires and screen-recorded walkthroughs of how they do a task today. Those recordings often reveal the workarounds behind the official process.

Remote delivery fits the work well. The Swedish morning and early afternoon overlap with my afternoon and evening in India, which leaves room for workshops without stretching anyone's day. Drafts are shared between sessions, comments are resolved in writing and every process area gets its own approval. See the Sweden overview for the other ways I support Swedish companies, and my guide on how to create an ERP BRD for the document structure.