Contact Info
What does a Swiss ERP audit include?
An ERP audit for a Swiss company is an independent review of a live system, not a statutory or financial audit. I compare configuration with how the business runs, test QR-bill payment matching and currency revaluation, list VAT code questions for your fiduciary, check access rights, payroll postings, interfaces and licenses, and deliver ranked findings. The work is remote and tied to no vendor.
Last reviewed by Vikas Saroj
A Swiss company can have an ERP that posts invoices, pays suppliers and closes the books, yet still leaves finance uneasy. Incoming payments land in a suspense account, the euro bank account never quite agrees, and the fiduciary asks the same VAT questions every quarter. Nothing is broken enough to escalate, so nobody looks at the whole picture.
I carry out remote ERP audits for Swiss headquarters, trading companies and exporters. This is a health check of the software and the way people use it, not a financial or statutory audit, and it does not replace your statutory auditor, fiduciary or tax advisor. I compare the configuration with how the business really runs, then rank what needs fixing.
No vendor pays me a commission or referral fee, which keeps the findings free of any motive to sell you a new platform. The engagement runs in English; where a German, French or Italian layout or report needs checking, a member of your staff reviews it with me.
Each area ends in findings with evidence, an owner and a suggested fix, so the report can be acted on rather than filed.
Finance, sales, purchasing and logistics staff show me how they complete real tasks. I note every step taken outside the ERP and trace it back to a configuration choice, a missing rule or a training gap.
Samples of open receivables, payables and bank balances in francs, euros and dollars, checked for unmatched payments, stale items and revaluation entries that do not follow a consistent rule each period.
A structured list of how tax codes are set up and used, including imports and services from abroad, written as questions your fiduciary or tax advisor can answer. I do not decide tax treatment.
Who can create suppliers, change bank details, approve invoices and generate payment files. I look for combinations one person should not hold, dormant accounts and old integrator logins still active.
Bank statement imports, logistics links, group reporting feeds and the journal your payroll provider sends each month, reviewed for error handling, ownership and the manual fixes staff make when they fail.
Which management reports people trust, which are rebuilt in spreadsheets, and whether the licenses or subscriptions you pay for match the users and modules that are actually in use.
Agree the questions to answer
Evidence from people and data
Findings ranked by business risk
The word audit carries weight in Switzerland, so I define the scope precisely before any work begins. What I offer is an ERP audit in the sense of a structured system review: is the software configured for the way your company now trades, are the controls inside it working, and can management rely on what it reports? It is not an audit of your financial statements, it gives no assurance opinion, and it does not replace the statutory auditor, your fiduciary or your tax advisor.
The review tends to be useful at particular moments:
In each case the aim is the same: replace opinions with evidence. I work from interviews, walkthroughs and read-only access to configuration and data, then report findings your team, the integrator or a new advisor can act on. The general method is set out under ERP health check; this page covers what changes when the system serves a Swiss company.
Receivables are often the first place a Swiss system shows strain. When invoices carry a QR-bill with a structured reference, incoming payments should match automatically from the electronic bank statement. If customers pay with the wrong reference, if some invoices were sent without one, or if the matching rules were never finished, payments pile up in a clearing account and someone matches them by hand. I sample those clearing entries and trace each pattern to its cause.
Currencies are the second test. Many Swiss companies hold euro and dollar accounts beside the franc account, and the questions are practical:
None of this requires me to form an accounting opinion. The audit shows whether the system applies the rules your advisors set, consistently, and where it does not. Findings in this area often lead to work on multi-currency setup or a tidy-up of bank reconciliation rules rather than anything dramatic.
Swiss VAT sits outside the EU system, and many international platforms reach it through a localization package, a partner app or custom setup. Over time, codes get copied, renamed or reused for purposes nobody documented. I list every tax code, how often it is used, which accounts it posts to and how it feeds the VAT report, and I flag patterns that look inconsistent: a code used for both domestic and import cases, manual journals that bypass tax logic, or services bought from abroad booked without a tax code.
Each observation is written as a question, not a verdict. Your fiduciary or tax advisor decides whether the treatment is right and what correction, if any, is needed. My part is to make the questions specific enough to answer quickly and to note where the system would need to change.
Payroll gets the same treatment. Most Swiss companies run it with an external provider or a separate payroll package, so the ERP only receives a journal. I check that the journal lands on the agreed accounts and cost centers, that someone reconciles it each month against the payroll summary, and that salary data is visible only to the people who need it. Social insurance and withholding questions stay with your payroll provider.
Access rights tend to grow quietly. A finance employee covers for a colleague and keeps the extra rights. The integrator's administrator account stays open after the project. A shared login is created for the warehouse. None of this is unusual, but together it can mean one person can create a supplier, change its bank details, approve an invoice and generate the payment file.
I export the user list and role assignments, then test them against a simple matrix of duties your management agrees should be separated. The usual areas are:
I also check dormant accounts, users who left the company, and whether personal data in HR or customer records is limited by role, which matters under Swiss data protection law and, where you serve EU customers, under GDPR. Legal interpretation stays with your advisor. The same review covers licenses: users billed but inactive, modules paid for and never switched on, and named users sharing one seat.
The final strand follows data across system borders. Electronic bank statements, payment files, logistics or forwarding portals, a web shop, a CRM and the feed into group consolidation each need an owner, an error routine and a way to notice when something stopped. I check the logs where they exist and ask the people who fix things by hand what they fix and how often.
Side spreadsheets are evidence, not embarrassment. A margin file maintained outside the ERP tells me which report management does not trust and why. I record each one with its owner and purpose.
The report itself is short and written for decision-makers:
| Section | What it contains |
|---|---|
| Summary | Overall condition, top risks and the quickest valuable fixes |
| Findings | Evidence, business effect, likely cause and recommended action |
| Advisor questions | VAT and payroll points for your fiduciary and payroll provider |
| Sequence | Suggested order of work, owners and dependencies |
Sessions run remotely during the Swiss morning and early afternoon; a meeting in person is possible by arrangement. If the system turns out to be in worse shape than a tune-up can fix, the Swiss ERP rescue page explains the next step, and fixes that fit the current platform continue as ERP optimization. Everything else I do for Swiss companies is linked from the Switzerland hub, starting with my ERP consultant work in Switzerland.
Tell me about your business and current systems. I’ll suggest the most sensible first step.
Book a Consultation
Not sure which ERP you need?
Share your business requirements with me and I will help you understand the right process, architecture and platform before implementation.
No. It reviews how the ERP is configured, controlled and used, and it expresses no view on your financial statements or tax position. Your statutory auditor, fiduciary and tax advisor keep those roles. Findings that touch tax or accounting are written as questions for them, and the evidence I collect can make their work easier.
Viewing rights to configuration, roles, logs and transactions are normally enough, together with screen-shared walkthroughs where staff show real tasks. Your IT team or integrator grants the access, decides how long it lasts and can withdraw it at any time. Personal data in samples is kept to what each check needs.
I will show how tax codes are set up and used, and where the pattern looks inconsistent, for example codes reused across different cases or entries that bypass tax logic. Whether the treatment is correct is a decision for your fiduciary or tax advisor. I turn their answers into configuration changes if you want help with that.
Then the report says so plainly and explains why: a platform limit, a design that no longer fits the business, or data too damaged to trust. The next step might be a re-scoped project, a recovery plan with your integrator or a fresh selection. I describe the options and their cost drivers, without pushing any of them.
Every business is different. Share where you are today and what you want to fix, and I’ll tell you honestly whether and how I can help.
Book a Consultation
Book a consultation to talk through your processes, systems and goals. I’ll reply with practical next steps - no obligation.