Business Process Consultant, Sweden

Following an order from quote to paid invoice

Order to cash is where a Swedish customer feels your processes most directly, so it is usually the first map I draw. I trace one real order through every step and every person who touches it, asking what information they need and where they get it.

The questions that tend to reveal the most are specific to how Swedish invoicing works:

• Where is the customer's buyer reference or order number captured, and who notices when it is missing before an invoice to a public body or a large company goes out?
• Is the OCR payment reference generated on every invoice, or do some invoices leave without it because they were made outside the normal flow?
• Who decides when a reminder is sent, and who decides when an overdue invoice moves to a collection service?
• How are credit notes, partial deliveries and price disputes handled, and do they reach finance before the next reminder run?

The answers usually show that most problems are created early in the flow and discovered late. A missing reference becomes a rejected invoice, then a delayed payment, then a manual match. In the redesigned flow, every check happens where the data first appears. Whether a public customer requires an electronic invoice, and in what form, is confirmed with that customer and your advisor rather than assumed.

Attest chains, approval limits and the summer gap

Most Swedish companies already have an attest routine for supplier invoices. What they often lack is a written one. The rule exists in the heads of the finance team: this supplier goes to the warehouse manager, that cost center goes to the CEO, anything for the new project goes to whoever is running it this month.

I turn that into an explicit approval matrix covering procure to pay from purchase request to payment proposal:

• Review versus attest: who checks that goods or services were received, and who approves the cost against the budget.
• Limits: which amounts each role may attest alone, and when a second person must approve.
• Deputies: who covers each approver during parental leave, sickness and the long summer holiday, when attest queues in many companies quietly grow.
• Conflicts: nobody attests invoices from a supplier they set up, or payments to themselves.
• Payment release: who approves the final payment batch, separate from those who attested the invoices.

The matrix is agreed with management and checked by your auditor or accounting firm where they have a view on controls. It then becomes a requirement for any system, whether that is today's accounting service or a future ERP. The approval workflow page explains how such rules are later configured.

Month-end with the accounting firm in the map

Many Swedish companies keep an external accounting firm involved in bookkeeping, closing, the VAT return or the annual accounts. That relationship is part of the record to report process, yet it rarely appears on anyone's process map. The result is a month-end where both sides wait for each other.

I map record to report across that boundary. For each task, the map shows who does it, what they need, when they need it and what they hand back:

• Bank and payment reconciliations, including receipts that did not match automatically.
• Accruals, prepayments and project revenue adjustments.
• Supplier invoices still waiting for attest at the cut-off.
• The VAT basis and who reviews it before filing.
• The SIE export or other handover to the accounting firm, and the corrections that come back.

Writing this down tends to remove a surprising amount of friction. Questions that used to arrive by email late in the close are answered by a checklist instead. Where your bookkeeping must meet Swedish rules on documentation and archiving, your accounting firm or advisor confirms what applies, and the process records where each voucher is kept. The detail of what a future system must produce for the accountant sits on my Swedish ERP business analyst page.

Hours, expenses and the inputs to payroll

Hire to pay is often split across a payroll provider, a time reporting app, an expense tool and the accounting service. Each part may work well alone, while the handoffs between them depend on reminders from one person in finance or HR.

In a mapping session I follow the inputs rather than the payroll calculation itself, which stays with your provider:

1. How a new employee is set up, and who tells payroll, IT and the project manager.
2. How hours are reported, who approves them and what happens to late or corrected time sheets.
3. How travel and expense claims are submitted, attested and paid, and how receipts are kept.
4. How absence such as sick leave, parental leave and holiday reaches payroll on time.
5. How approved hours feed project invoicing for consultancies and service firms.

The target design names one owner for each input and a cut-off that everyone can see. For project-based companies, it also links hire to pay with project delivery, so billable time is approved before invoicing starts rather than corrected afterwards. Questions about employment law, collective agreements or payroll taxes go to your payroll provider or advisor, not into my maps.

Process owners, documentation and what comes next

Process work in Sweden tends to succeed when people feel consulted, and fail when a new routine simply arrives by email. I plan workshops so the people who do the work help shape the target process, and I ask management to name one owner for each end-to-end flow before the handover.

The documentation is deliberately short:

• One swimlane map per process, current and target.
• An approval matrix with limits and deputies.
• Role-based procedures of a page or two each.
• A gap list stating what needs a policy change, a configuration change or a new tool.

Everything is written in English. If warehouse or service staff prefer Swedish procedures, your team adapts them, and I keep the English version as the reference so updates stay consistent.

Only then does software enter the conversation. Some gaps can be closed by changing how the current system is used. Others become requirements for selection or for business automation in Sweden. If a new ERP is on the table, the agreed processes feed straight into the work described on my ERP consultant page for Sweden. The Sweden overview lists every way I support Swedish companies remotely, and the method behind this page is described under business process consulting.