Salary statement & payroll correction: the most expensive 20-minute mistake in a Swiss SME payroll run (2026)
Why a small payroll error becomes expensive in a Swiss SME: payroll corrections, the annual salary statement, retroactive social-security deductions and pain.001 under control. The assistant prepares the payroll run, a human approves.
In short: A wrong payslip is not like a wrong invoice amount. It lands directly in a person’s bank account, it triggers retroactive corrections for AHV (OASI), ALV (unemployment insurance), the pension fund and withholding tax, and at year-end it ends up on the salary statement (Lohnausweis). The actual work therefore begins after the mistake. This guide shows where payroll mistakes arise in a Swiss SME, what a correction really triggers — and why human approval of the payroll run is not a brake, but a duty.
Why a payroll mistake is not like an accounting mistake
A wrongly posted supplier invoice you correct quietly, internally, without anyone noticing. A wrong payslip is the opposite: it is immediately visible, it concerns a person, and it triggers a chain of follow-up processes that reaches well beyond accounting.
Imagine an employee accidentally receives an inflated allowance in March, or a shift bonus is forgotten for a month. The amount itself — say CHF 400 — is manageable. What it triggers is not:
- Social-security deductions (AHV/IV/EO, ALV) were calculated on the wrong gross wage and have to be corrected retroactively.
- The pension-fund contribution (BVG / 2nd pillar) may be affected.
- For employees subject to withholding tax, the withholding-tax basis changes.
- The correction has to be reflected in the next payroll run as a dedicated payroll correction (Korrekturlohn) — not simply «netted off next month».
- And at year-end, everything has to appear correctly on the salary statement (Lohnausweis), otherwise the report to the compensation office and the tax authority doesn’t add up.
The original mistake may have taken twenty seconds — a value entered wrong. The correction costs twenty minutes, often more, and touches several systems at once. Hence the title: it is the most expensive short mistake in an SME.
Where payroll mistakes actually arise in a Swiss SME
Payroll mistakes are rarely calculation errors in the strict sense. They arise at the interfaces where information flows from one process into the payroll run — usually by hand.
1. Hours and bonuses from time tracking. Overtime, flexitime balances, shift or weekend bonuses are transferred into the payroll run manually. Every manual transfer is a source of errors.
2. Mutations that arrive too late. A salary increase effective on the 1st reported only on the 10th. A leave, a hire, a change of employment level in the middle of the month.
3. Expenses mixed with salary. Tax-free expenses and taxable salary must stay cleanly separated — otherwise the salary statement is wrong.
4. Absences and daily sickness benefits. A sickness case with daily-benefit payments changes the salary basis. If that is not captured correctly, the SME pays too much or the employee too little.
5. Withholding-tax tariff changes. Marriage, child, change of canton — everything changes the applicable tariff and is often updated late in the SME.
Each of these points is mundane on its own. They become dangerous because they arise scattered across the business and only converge in the payroll run — where they get processed under time pressure, because payday is fixed.
What a payroll correction really triggers — a worked example
Take a Swiss SME with 25 employees. Experience suggests that one to three payroll runs per month need a correction — through late mutations, forgotten bonuses or mistyped hours.
Note: the figures below are a transparent model based on industry-standard assumptions, not a measured value from a single customer.
| Step of a payroll correction | Time per case (manual) |
|---|---|
| Spot the error and trace its cause | 5 min |
| Recalculate the correct gross / net salary | 6 min |
| Adjust retroactive social-security deductions (AHV/ALV/BVG) | 8 min |
| Check / correct withholding tax (if applicable) | 5 min |
| Reflect the correction cleanly in the next run | 6 min |
| Inform the employee and document | 5 min |
| Total per correction | ≈ 35 min |
At two corrections per month, that’s around 70 minutes a month, roughly 14 hours per year — just for the corrections, not for the regular payroll run. At an internal hourly cost of CHF 70 (HR / fiduciary level), that’s close to CHF 1’000 per year, plus year-end, when every correction has to line up consistently on the salary statement.
And here too the most expensive item is the invisible one: trust. An employee who receives a wrong payslip three times a year loses trust in their employer — regardless of how quickly things are corrected.
The decisive point: the assistant prepares, a human approves
This is where we at hegyon.ai deliberately think differently than a classical HR or payroll module.
A payroll module gives you screens: one for hours, one for bonuses, one for mutations, one for the payroll run. You have to know what changed, enter everything correctly, and run the correction yourself. The tool calculates — but only with what you feed it correctly.
An operational AI assistant starts one step earlier. It prepares the payroll run by pulling together the scattered information before a mistake can happen:
- It pulls hours, overtime and flexitime balances directly from the time-tracking module — without manual transfer.
- It surfaces open mutations (hire, leave, employment-level change, salary change) and flags the affected employees.
- It keeps tax-free expenses and taxable salary separated.
- If a correction is needed, it calculates the payroll correction including retroactive social-security deductions and lays out the difference transparently.
- It prepares the payment as a pain.001 file (ISO 20022) and checks consistency with the later salary statement.
And then — this is not negotiable in payroll — a human approves. The assistant presents the prepared run, the HR lead reviews the flagged cases and the corrections, approves or intervenes. Only after that does money move.
Why human approval in payroll is not a brake, but a duty
For invoicing, you can argue about degrees of automation. For payroll, you can’t.
A salary is a legally delicate, personally sensitive and only reversibly recoverable payment. Money that has been transferred isn’t casually «clawed back» — a reclaim against employees is heavy in employment-law and human terms. That is why every payroll run deserves a deliberate human approval, ideally under a four-eyes principle.
This is exactly where our architecture aligns with modern AI governance. The EU AI Act requires effective human oversight for high-risk AI systems (Art. 14) — that is, systems designed so that humans can actually supervise them, in order to prevent risks to health, safety or fundamental rights. Whether a pure payroll-preparation assistant falls into that category is a context-dependent assessment, and by no means self-evident. But independently of that, we consider human approval in payroll the right thing to do anyway: that no system pays out salaries autonomously is a deliberate design decision at hegyon.ai — no black box, but a prepared run that a human approves. An assistant that does the legwork and leaves the decision to the human is not a compromise here, it’s the right way to build. Preparation gets fast; responsibility stays where it belongs.
What to watch for in the payroll run — even without us
Whether with an assistant, payroll software or a fiduciary: these four points lower your error rate immediately.
- Connect time tracking and payroll without manual transfer. Most payroll errors are transfer errors. Where nothing is retyped, nothing wrong is created.
- Treat corrections as a separate, documented process. A payroll correction is not «net it off next month», it is a traceable step with retroactive deductions.
- Keep expenses and salary strictly separate. That is the most common cause of a wrong year-end salary statement.
- Insist on human approval. A system may prepare the payroll run. Only a human may trigger it.
Conclusion
The expensive part of a payroll mistake is never the mistake itself — it is the correction it triggers: retroactive deductions, withholding tax, payroll correction, salary statement and the employee’s trust. Twenty seconds of mistake, twenty minutes of clean-up, and at year-end everything still has to line up.
The 2026 question is therefore not «Which payroll software do I buy?», but «How much of the payroll run can be prepared without errors, so that my HR lead only has to review and approve — not retype and recalculate?».
hegyon.ai is an operational AI assistant for Swiss SMEs — with integrated modules for ERP, HR, CRM, ticketing, inventory, project management and wiki. The assistant prepares the work; your people decide. Swiss hosting, FADP/revDSG compliant, EU AI Act guardrails.