Business Central Consultant, Switzerland

Standard Swiss version, partner apps and extensions

Business Central has a Swiss country version from Microsoft that handles the core of local bookkeeping. Many Swiss-specific needs, such as QR-bill output and scanning, payment files for Swiss banks, statement processing with references and some reporting, are commonly delivered through apps from partners or independent software vendors. Partner proposals often bundle these apps without explaining which requirement each one covers.

Before any configuration, I build a simple table with three columns for each Swiss requirement:

• Standard. Covered by the Swiss version as delivered, confirmed in a sandbox.
• App. Covered by a named app, with its publisher, license model and support arrangement recorded.
• Extension. Not covered, so custom development is needed, with an estimate and an owner for future updates.

This table changes the conversation with partners. Overlapping apps become visible, extensions that a standard feature could replace get challenged, and the long-term cost of each app appears alongside its benefit. Because Business Central receives regular updates from Microsoft, every app and extension also needs a clear answer to the question of who tests and updates it.

The general product scope is on my Business Central consultant page, and the wider Swiss Dynamics context, including hosting, is on Dynamics 365 consultant Switzerland.

Swiss VAT posting combinations and import VAT

Every Swiss VAT outcome in Business Central comes from a setup line that joins a customer or vendor category with a goods or service category. The fiduciary's scenario list tells us which lines must exist, and the VAT statement then adds them up into the figures the Swiss form asks for.

Scenarios I test with your fiduciary:

• domestic supplies at the rates relevant to your goods and services
• exports, with turnover reported separately from taxable supplies
• services purchased from abroad where tax may have to be self-declared
• exempt or non-taxable income your company receives
• input tax on materials separated from input tax on investments where the form asks for it

Import VAT needs a dedicated design. Customs assesses the tax when goods enter, and it may be paid directly or charged by a forwarder together with freight. I set up a booking method, often a specific general journal template or purchase posting, that links each entry to the customs assessment and keeps import VAT out of freight cost.

Before go-live, the VAT statement for a test period is compared line by line with the fiduciary's own figures. When posting groups change later, the statement is reviewed again, because new combinations do not appear on the return automatically.

Francs, euros and exchange rate adjustment

Swiss entities in Business Central usually keep the local currency in francs while trading in euros, dollars and sometimes other currencies. The design decisions are simple to list but costly to change later:

• Customer and vendor currencies. Fixed on each account, so documents default correctly and balances are tracked in the original currency.
• Bank accounts by currency. Each foreign currency account set up with its currency, so statements reconcile without conversion.
• Rate updates. Which service supplies exchange rates, how often and who reviews them.
• Exchange rate adjustment. Which balances are adjusted at period end, which accounts receive gains and losses, and how dimensions are treated on those entries.
• Additional reporting currency. Whether group reporting needs a second currency held on every entry, which must be decided before go-live.

A sandbox run covers the whole sequence: euro invoice, partial payment at a new rate, period-end adjustment, final payment, and the resulting entries compared with a worked example prepared in advance.

If the Swiss company owns or belongs to entities in other countries, Business Central's intercompany features can exchange documents between companies, with consolidation run centrally. I design the intercompany partner codes and account mapping alongside the currency rules. My multi-currency ERP page discusses the general pattern.

What I check in a Swiss partner's statement of work

Swiss Business Central partners, whether based in Switzerland or serving it from abroad, usually propose a package of configuration, apps, extensions, migration and support. My review compares that package with your requirement list and flags what is vague or missing:

• App inventory. Every app named, with the requirement it covers, its license model and who supports it after Microsoft updates.
• Extensions. Description, estimate, code ownership and how they are maintained.
• Language scope. Which user interface languages, document templates and training sessions are included for German, French and Italian speaking staff. Translations are written or checked by your team or the partner.
• Bank testing. Whether payment files and statement imports are tested with your actual banks, and who coordinates with them.
• Data migration. What the partner loads, what you must clean, and how many trial migrations are planned.
• Acceptance. Who writes test scripts, how defects are rated and what constitutes sign-off.
• Rollout. If foreign entities follow later, whether the Swiss design is treated as a template and what changes per country.

You receive the findings as negotiation points with suggested contract wording. My vendor proposal review page explains the approach, and testing and UAT covers acceptance.

Swiss situations where Business Central is the wrong choice

Business Central suits many Swiss mid-sized firms and regional entities of Microsoft-centered groups. I suggest an alternative when:

• The company is small and finance needs are basic. Zoho Books in Switzerland may be enough, with the fiduciary handling the rest.
• The business wants one open database it can adapt internally. Odoo Accounting in Switzerland is worth comparing.
• Physical commodity trading requires position and risk management that belongs in a specialist system, with an ERP only underneath.
• Ongoing partner support cannot be funded, since apps, updates and changes usually run through a partner.
• The app list keeps growing. If Swiss requirements can only be met by stacking many third-party apps, the long-term support burden deserves a hard look before signature.

Comparing platforms for a Swiss entity is the subject of my ERP consultant Switzerland page, and the overview for Switzerland explains remote delivery. If partner choice is still open, my ERP vendor selection service runs a structured comparison.