Business Process Consultant, Switzerland

Where Swiss back-office processes lose time

Most process problems in Swiss companies are not dramatic. They are small waits that add up. An invoice goes out late because nobody told accounts that the delivery left the warehouse. A supplier invoice sits in a shared mailbox until someone recognizes the cost center. A payment run waits because the person who releases it is on holiday. The month-end close slows down because intercompany balances with an EU subsidiary are agreed by email.

Lean teams make this worse in a specific way: a single person often handles a whole chain, so the rules live in their head rather than anywhere written. When that person is away, colleagues guess, and the fiduciary later finds the gaps.

My first job is to make these waits visible. In short online workshops I map each end-to-end flow with the people who do the work: order to cash, procure to pay, record to report and the inputs that go to your payroll provider. Every handoff, re-keyed figure and side spreadsheet goes on the map, along with the exceptions that rarely make it into any manual.

None of this starts with software. The maps describe the business, and they stay valid whether you keep your current package, move to a new ERP or simply change a few rules. The method itself is set out on my business process consulting page.

QR-bills, references and the receivables process

The QR-bill gives a Swiss invoice a structured payment part, and the reference on it can make matching receipts far more reliable. Whether it does depends on the process around it, not only on the format.

When I map order to cash, I follow the invoice from the order confirmation to the moment the money is matched:

• Who triggers the invoice, and does it wait for a delivery confirmation or a signed timesheet?
• Which reference scheme is used, and does it survive credit notes and partial deliveries?
• What happens when a customer pays without the reference, pays several invoices at once or pays in euros?
• Who decides when a customer moves through the reminder stages or goes on hold?
• Where do disputes get recorded, and who closes them?

Each answer becomes a rule with an owner. The technical side of the QR-bill, such as account types and data layout, is a question for your bank and software provider. The process question is simpler and often neglected: who acts when a payment does not match, and how fast. Clear answers here usually shorten the list of open items far more than any new screen would.

The requirement detail for a later system choice belongs to my Swiss ERP business analyst work; this stage simply agrees how the business wants receivables to behave.

Approval limits, signing authority and payment release

Swiss companies register who may sign on their behalf, and many require joint signatures for important commitments. That legal signing authority is not the same as an internal approval matrix, yet the two are often blurred. A buyer may hold approval rights for small orders without any registered signing authority, while a director with signing authority may not be the right person to approve a technical purchase.

In the procure-to-pay map I separate these clearly:

1. Purchase request and approval by amount, cost center and entity.
2. Order, goods or service receipt, and who confirms it.
3. Supplier invoice arrival, check against order and receipt, and approval of differences.
4. Payment proposal prepared by one person.
5. Release in e-banking by people with the right authority, under the bank's dual control where you use it.

I also design the awkward cases: deputies during holidays, urgent payments, changes to a supplier's bank details confirmed through a known contact, and payments in foreign currency. The result is an approval matrix and release procedure that your management signs off. Your legal advisor confirms anything touching registered signing rights; I make sure the daily process respects them. Approval design is also covered on my approval workflows page.

Procedures that work in German, French and Italian

A process that exists only as a diagram rarely changes behavior. People need short, role-based procedures that tell them what to do in their own working language. For Swiss companies with sites in several language regions, that raises a practical question: which version is the master, and how do the others stay in line?

The engagement runs in English, and I write the master procedures in English. Your staff or a local partner write or check the German, French or Italian versions. To keep them aligned, I set up a few simple rules with you:

• A short glossary of process terms, so an approval or a credit note means the same thing in every version.
• A version number and owner on every procedure, with changes made to the master first.
• Screenshots and examples taken from real documents, with personal data removed.
• One storage location everyone can find, rather than copies in mailboxes.

Some processes touch personal data, especially hiring, payroll inputs and expense claims. The maps show where that data travels and who sees it, so your data protection advisor can check it under the Swiss data protection act, plus GDPR for any EU-based staff or customers. I raise the questions; the legal judgment remains theirs.

The close, the fiduciary and when software enters

Many Swiss companies work with an external fiduciary for VAT returns, statutory accounts or payroll. The record-to-report map shows exactly what passes between your team and theirs: which reconciliations you finish before they start, which documents they need for the VAT period, how foreign currency balances are handled and who answers their questions. When this handoff is written down, the close stops depending on a few long email threads.

Groups add another layer. Groups spanning Switzerland and the EU, in either direction of ownership, need a single process map per flow with the local variants clearly flagged. I keep those variants to what the law or the market genuinely requires, so the rest of the process can be standard.

Only after the processes are agreed does the software question come back. Sometimes the answer is a better-configured current system. Sometimes the agreed process and its requirements lead into a structured choice, described on my ERP consultant page for Switzerland and my Swiss ERP selection service. Where the maps reveal repetitive manual steps, the next stop is my Swiss business automation work.

You keep everything: maps, approval matrix, procedures, issue log and requirement list. Everything else I offer Swiss companies is on the Switzerland overview.