Integration Consultant, Switzerland

Which systems a Swiss ERP usually has to talk to

The first deliverable is an integration inventory. For a Swiss company it tends to include more file-based links than people expect, because banking and payroll still run largely on structured file exchange rather than live APIs.

For each line I record who maintains the link today, how errors are noticed and what happens at month-end if it fails. That record often shows a critical flow running through one person's desktop or an old script nobody can explain. The inventory then feeds the master data decisions, which come before any technical choice. My system integration page describes the general method in more detail.

Bank files, QR references and automatic matching

Swiss receivables work well when every incoming payment can be tied to an open item without a person looking at it. That depends on several pieces lining up.

• Outgoing invoices carry a QR-bill payment part with a structured reference generated by the ERP, using the correct account type for that reference.
• Incoming credits arrive in the bank's statement or notification files with the reference intact, and the ERP reads them on a schedule rather than by manual upload where the bank allows it.
• Matching rules close the open item when reference and amount agree, and route partial payments, overpayments and unknown references to a review queue.
• Supplier QR-bills are scanned or read from PDF, and the payment data is checked against the supplier master before it enters a payment run.

Payment files going the other way need the same care. Each bank may interpret the standard slightly differently, so I plan a test exchange with every bank you use, including a rejected payment and a returned file. Changes to supplier bank details get an approval step, because a quietly edited account number is one of the more expensive integration failures. Your fiduciary or auditor may also have views on these controls. The Swiss ERP business analyst page explains how these points become requirement lines.

Payroll, webshops and logistics providers

Most Swiss companies run payroll in a dedicated package or through a provider, because salary reporting to authorities and social insurance bodies follows its own standards. The ERP rarely needs individual payslips. It needs a summarized journal by account and cost center, posted on a known date and reconciled to the payroll summary. I map each pay element with finance, define how corrections are posted and decide whether the link is a file import or a connector. Questions about what payroll must report remain with your payroll provider or fiduciary.

Sales channels bring different issues. A webshop may sell in francs and euros, charge Swiss VAT on domestic orders and treat exports differently, and the ERP must receive each order with the right tax code and currency. I specify how often stock and prices are published, how discounts, shipping charges and gift cards map to order lines, and how a refund in the shop becomes a credit note in the ERP. Payment providers usually settle net of fees, so the mapping splits gross receipts, fees and payouts.

For goods leaving through a logistics provider or a cross-border forwarder, I agree which party prepares export documents and how shipment confirmations and tracking come back to the ERP. Customs requirements themselves are confirmed with your forwarder or customs advisor. Companies in ecommerce and distribution feel these links most directly.

Connector, integration platform or bespoke code for a Swiss setup

No single route suits every Swiss company. The choice turns on the number of systems in play, the speed at which data has to move and the people who will look after the result once the project team has gone. I compare the options in a short decision paper:

• Native connectors between the ERP and a webshop, CRM or bank are the cheapest to run when they cover your cases. I test them against real scenarios, including multi-currency orders and returns, before relying on them.
• Middleware or an integration platform earns its place once several applications exchange records and mapping, logging and retries should be managed centrally. It adds a subscription and another tool your team must understand.
• Custom API services suit high volumes or unusual logic, but every line of code becomes something a developer must maintain.
• Scheduled files remain valid for banks and payroll, provided they are automated and monitored rather than uploaded by hand.

Hosting deserves a question as well. If the ERP is hosted in Switzerland but the middleware runs elsewhere, customer and payroll data may leave the country on its way between systems. I list where each component runs and pass that to your data protection advisor for review. When the integration is part of a wider ERP change, it is planned together with ERP integration and data migration so codes and identifiers change once.

Testing, monitoring and who owns the integration later

An integration is not finished when the first record arrives. I write test cases from real transactions: a payment with a QR reference, one without, a partial payment, a rejected bank order, a webshop order in euros with a return, a payroll correction and a connection failure halfway through a batch. Finance reconciles a sample across systems before sign-off, and the cutover plan says which interfaces switch off, which switch on and how in-flight orders are handled on the first day.

After go-live the integration needs an owner. I agree that before the developers leave:

• Failed records go to an error queue and an alert reaches a named person, not a shared inbox.
• Daily control totals compare payments, orders or journal amounts between systems.
• A runbook explains common failures, who fixes them and how to reprocess a record safely.
• Credentials belong to dedicated integration users with limited permissions.

The work is delivered remotely, with sessions in the hours that overlap between Switzerland and India and visits by arrangement. If the integration also feeds a CRM, the sales side is covered on my CRM consultant page for Switzerland. For the wider ERP picture, see my ERP consultant page for Switzerland or the Switzerland overview.