The guide
Guide: business process automation for Swiss SMEs
Which administrative tasks to automate first, how to write a Skill the agent will carry out correctly, which trigger to choose, how to automate payment reminders in line with the Swiss Code of Obligations and how to automate accounting without losing control. A practical guide for management, administration leads and fiduciaries.
Where should an SME start with business process automation?
The best candidates for automation are tasks that are frequent, regular and easy to check. In a Swiss SME of 20 to 150 people, the same ones almost always come up: reminders for overdue invoices, entering supplier invoices received by email, reconciling incoming payments, month-end accruals, chasing missing expense reports, preparing the month’s obligations (VAT, AHV/AVS, withholding tax). Each one takes little time, but it keeps coming back and eventually gets forgotten.
Take stock over one month: note every repeated task, how often it occurs and how long it takes. Start with the one that costs the most when it is forgotten, often payment reminders, because every week of delay erodes cash flow. Automate it first in cautious mode, with approval of every outgoing message, then relax control on the steps that prove reliable. An automation that runs smoothly for a month is a better argument than a large transformation project.
What is a Skill and how do you write a good one?
A Skill is a procedure written in everyday language that the Numezis agent carries out. It contains three elements: instructions, a list of authorised tools and one or more triggers. The instructions are written like a brief to a competent but new colleague: what to look for, which rules to apply, when to ask for approval, and how to report on the outcome.
A few principles make a Skill reliable. Be precise about thresholds: “invoices more than ten days overdue” rather than “late invoices”. Name the exceptions: “never send a reminder to a customer with an open dispute”. State explicitly what requires approval, even if company policy already provides for it. Keep the tools to the strict minimum: a reminder Skill has no reason to be able to create a payment. Finally, test the draft on real data before publishing the first version.
Event, schedule, webhook or manual: which trigger should you choose?
The event trigger suits tasks that must follow a fact immediately: a supplier invoice arrives, a payment is reconciled, a deal is won, an employee joins the company. The Skill receives the record concerned and acts straight away. The scheduled trigger suits tasks that follow a rhythm: weekly reminders, a daily cash check, closing preparation on the last working day, a quarterly VAT reminder.
The incoming webhook connects Numezis to an external system that knows nothing about your modules: an online shop, a booking tool, industry software. The system calls a signed address, and the Skill processes the payload it receives. Finally, the manual launch is for one-off tasks, tests and catch-ups; it can also be requested from the agent in conversation. A single Skill can combine several triggers, for example a weekly schedule plus a manual launch before the holidays.
How do you automate invoice reminders in Switzerland?
Under Swiss law, a debtor owing a debt that has fallen due is put in default by the creditor’s demand for payment, or without any reminder if a specific due date was agreed (CO Art. 102). From the moment of default, interest of 5% per year is owed, unless a different contractual rate applies (CO Art. 104). In practice, SMEs send a polite first reminder, a firmer second one, then a third that states the interest and announces, where necessary, a debt enforcement request under the Debt Enforcement and Bankruptcy Act (DEBA/LP).
A reminder Skill reproduces exactly this practice. Every Monday it lists the overdue invoices, picks the reminder level based on the history, attaches the QR-bill to make payment easy and records the reminder on the invoice. The first reminders can go out on their own; the third, which quantifies the interest and puts the customer relationship at stake, is held for approval. Customers in dispute are excluded, and payments received in the meantime, reconciled by QR reference, stop the reminder automatically.
Automate accounting without losing control
Automating accounting does not mean letting a machine post to the general ledger unsupervised. The right model combines three safeguards. First, a closed list of tools per Skill: a reconciliation automation can propose entries, not create payments. Second, an approval policy that pauses the run at every sensitive step and enforces segregation of duties. Third, a complete history of every run, available to management, the fiduciary and the statutory auditor.
Within this framework, a great deal of accounting work lends itself well to automation: recurring monthly accruals, bank charge entries, scheduled depreciation, pre-closing checks, preparation of the VAT return, reminders of AHV/AVS and occupational pension (BVG/LPP) obligations. Locked periods remain out of reach, regulated calculations are deterministic and supporting documents are retained for ten years under CO Art. 958f. You gain the regularity of a machine and keep the judgement of a human.