Zum Inhalt springen

MCP for Abacus and Bexio

Query Abacus and Bexio in the chat without exporting data

In Swiss SMEs and fiduciary firms, accounting, receivables, orders and receipts sit in Abacus or Bexio. The data is there, but every analysis means clicking through screens or exporting lists to Excel. An MCP server makes these records queryable via your AI platform without creating a copy.

The way in: the official interfaces

Bexio offers a public REST API with OAuth 2.0. Each person signs in with their own Bexio account, so their permissions automatically apply in the chat as well. For Abacus, we use the interfaces your installation provides; which ones these are depends on the version, operating model and licensed modules. We clarify this before the proposal, because this is exactly what the effort depends on.

The MCP server runs in your infrastructure or in a Swiss data centre and is the only point that talks to Abacus or Bexio. Direct access by the language model to your ERP is not intended.

Permissions: what someone cannot see in Abacus, they cannot see in the chat either

A pilot with a single technical user sees everything or nothing. In production, each request is assigned to the requesting user and executed with that user's permissions. In Bexio, this follows from the per-person sign-in; in Abacus, from the assignment to users or roles. Payroll data and other particularly sensitive areas remain excluded unless you explicitly approve them.

What SMEs and fiduciary firms actually use it for

Receivables and liquidity
“Which open items over CHF 10,000 are older than 60 days, and who sent the last reminder?” instead of an open-items list that first has to be filtered.
Preparing closings and VAT
Have anomalies, missing receipts and unusual postings compiled before the quarterly or annual closing. The return itself remains with a human.
Orders and quotes
Query the status of quotes, orders and deliveries across customers, for example before a customer meeting.
Clients of fiduciary firms
Questions about the client base in plain language, with client separation through employees' permissions.

Data protection under the FADP

Anyone who has a platform provider work with personal data generally needs a data processing agreement (Art. 9 FADP). If the provider is located abroad, the rules on disclosure abroad also apply (Art. 16 FADP). We set out the options: enterprise offerings with data residency and without storage of inputs, operation in Switzerland, or local models where no data leaves the premises.

We provide the architecture information that the person responsible for data protection in your organisation needs for the assessment. This does not replace legal advice.

Limits we state up front

  • No write access by default. No postings, no payments, no changes to master data without explicit approval.
  • No circumvention of the Abacus or Bexio permission model.
  • No submission of VAT returns or other filings by the AI.
  • No copy of the records into a search database.

Frequently asked questions

Does our Abacus or Bexio data leave the company?

Not as a data set. The MCP server reads, per request, only the data needed for the answer and passes it to the language model. Whether the model runs in the cloud or locally is up to you. With local models, no data leaves the premises.

Does this work with Abacus in the cloud and on premises?

In both cases, provided your installation offers a suitable interface. Which interface is available depends on the version and licensed modules. We check this in the feasibility study of one to two weeks.

Does every employee see all the data?

No. Each request runs with the permissions of the requesting user. What someone is not allowed to see in Abacus or Bexio, they do not see in the chat either. Payroll data remains excluded unless it is explicitly approved.

Which AI platforms are supported?

All platforms that speak MCP, including ChatGPT, Claude and Langdock, as well as local models. Kapitel H is an official partner of OpenAI, Anthropic and NVIDIA and recommends the platform that fits your requirements for data protection and cost.

Let’s check whether it holds up for your systems.

The feasibility study takes one to two weeks and ends with a document you can keep working with even without us. If an interface cannot meet your requirement, it says so.

Request a first call