How do you connect Bexio to Claude? It is possible, and fairly simple. The problem is not the technique. It is knowing what you give in exchange. A Bexio token opens the whole of the company’s accounts. You may as well create it, store it and use it knowing what that means.
The short answer: you create a personal token on Bexio’s developer portal, you hand it to Claude through a safe channel, and you start with read-only questions. The token lasts 60 days, cannot be restricted by permissions and acts with your rights. Treat it like your bank password.
Why connect Bexio to Claude (and why not right away)
Bexio already holds everything you would ask an AI to read: invoices, contacts, payments, entries, accounts. Without a connection, you have to export, copy, paste, explain. With the connection, Claude fetches the information itself, and you ask the question as you would ask a colleague: “Which invoices have been open for more than 60 days?”
It is appealing. It is also where people rush. Before plugging anything in, three questions deserve a minute:
- Which question do you want to ask that you cannot settle in two clicks in Bexio?
- Which data will be read, and does it belong to you alone or to clients as well?
- Who answers if Claude gets it wrong or changes something it should not have?
If those three answers are clear, move on.
How to connect Bexio to Claude: the three steps
To connect Bexio to Claude, you need three things in order: unlock access to the Bexio API, create the token, then hand it to Claude through a safe channel. Here is how to do it, step by step.
Step 1: unlock access to the Bexio API
The personal token is not created in Bexio’s settings. It goes through the developer portal, a separate site, with your usual Bexio login.
- Go to developer.bexio.com/pat (the personal access tokens page).
- Sign in with your Bexio account, then accept the developer portal’s terms of use if you are asked to.
- Check that you can see your company. If the portal refuses access or shows nothing, the blockage may come from the account’s rights.
Two points to know before going further:
- The token acts with your rights. It cannot read what the user who created it cannot read in Bexio. This is also what lets you limit the damage (see below).
- Managing API access is in principle reserved for the super administrator. That is what one specialist guide says. We could not confirm it in Bexio’s official documentation: if you are not the administrator of your Bexio, ask the person who is, or contact Bexio support.
Step 2: create the Bexio API token
Once you are on the tokens page:
- Start creating a new token.
- If the portal allows it, give it a name that says what it is for, for example “Claude, trial, to delete”. Avoid “read-only”: the token itself is not. In two months, you will be glad to find it.
- Check that it applies to the right company.
- Copy the token immediately, in full.
Then two details that many people discover too late.
It lasts 60 days. According to Bexio’s documentation, a personal token expires 60 days after it is created. After that, the connection stops, and nothing guarantees you will be warned. Put a reminder in your calendar for day 55.
It covers everything. A personal token carries all rights by default. You cannot say “invoices read-only, nothing else”. To restrict permissions, Bexio’s documentation points to an OAuth application, but it requires a server and some development. For SME use, it is generally not the right way in.
Watch out: a personal token gives access to all of the company’s data, including contacts and amounts. If you want a safety margin, create it, if the portal allows it, from a Bexio user whose rights are deliberately limited (read access, no access to salaries or settings). Access also depends on that user’s rights, so the token should not go beyond what that user is allowed to do. Test it before trusting it.
Step 3: give the token to Claude
This is where things get complicated, and where shortcuts cost you. There are three ways to do it, and none is perfect.
Option A: paste it into the conversation
This is the quickest: you write “Here is my Bexio token” and Claude uses it. The price: the token stays written in the conversation history. If you forget it there, it is still there a month later. Avoid it with your real accounts. If you want to try, do it on a test account (Bexio offers a sandbox account to developers) or with a token you will delete straight afterwards, and never with a token used for anything else.
Option B: store it in a .md file
Many guides recommend a small text file that Claude rereads at the start of each session: practical, readable, easy to update. It is also the option that traps the most people, for very concrete reasons:
- the file is in plain text: anyone who opens it sees the token;
- it is often in a synchronised folder (OneDrive, Dropbox) and ends up on other devices;
- a single Git repository is enough to publish it by mistake, with the history keeping it;
- it has the same lifespan as the token: 60 days, then an out-of-date file that nobody remembers creating.
If you choose this route anyway: a file in a local, non-synchronised folder, outside any Git repository, added to the ignore list, with the expiry date written on the first line. Put only the token in this file, never a password.
Option C: an environment variable (or a password manager)
This is the method we recommend as soon as you use Claude on your computer with a tool able to run commands. The token is saved in an environment variable, or retrieved from a password manager. Claude uses the variable without you having to paste the token into the conversation (still check that the commands shown do not repeat it). No more copy and paste, no stray file, a single value to change every two months.
What about connectors (MCP)?
MCP servers for Bexio exist: they present Claude with a list of actions (list contacts, create a project), and it is the server that keeps the token. The advantage: the token no longer goes through the conversation. The drawback: it is stored elsewhere, sometimes with a third party. At the date of this article, we did not find an official connector from Bexio: the ones in circulation are built by the community or by automation tool vendors. Before plugging one in, look at who hosts it, where the token is kept and which actions it allows.
Good to know: depending on the environment where you use Claude, network access may be limited and prevent calls to the Bexio API. Run a simple test before building anything on it. Conversely, if network access is wide, booby-trapped content (a document, a web page) could push Claude to send data elsewhere: one more reason to give it only a token you can delete at any time.
Recommended first test: ask Claude to read one harmless piece of information, for example the list of your accounting accounts, and to tell you which user it is acting as. If the answer matches what you expect, the connection is good.
The risks, without drama or understatement
A Bexio token is not a gadget. Here is what can really happen.
- Token leak. Pasted into a message, a shared document or a code repository, it gives full access to anyone. Deleting it in the portal takes up to an hour to be fully effective.
- Unwanted writing. Bexio’s API can create and change. A poorly guided AI can create a duplicate contact, change an invoice or post an entry you have not approved. An entry in a closed period is another trap.
- Third-party data. What Claude reads is processed by an external service. If Bexio holds client or employee data, check what your contract and the nFADP (nLPD in French) provide. For an accounting firm, it is also a matter of professional confidentiality.
- False reassurance. Claude can present a wrong result in a very confident tone. A VAT total recalculated by an AI remains a hypothesis until someone has reconciled it with the supporting documents.
- API limits. Bexio limits requests per minute and per company (error 429 beyond that). A very broad analysis can stop midway, and it shares the quota with everything already connected.
- A token that expires. After 60 days, everything stops and, if nobody looks after it, you believe the automation is running when it is dead.
Key takeaway: most of these risks are handled with three habits: start read-only, never leave the token in a plain-text file, and require written confirmation before any writing in Bexio.
What you can do once connected
This is the part that justifies the effort. Here are concrete uses, ranked from least to most risky.
Read-only (start here)
- List invoices open for more than 30 or 60 days, by client, with a draft reminder.
- Spot duplicates in contacts, or incomplete client records.
- Summarise expenses by account over a quarter, and flag anything unusual.
- Prepare a check before the VAT return: entries without a VAT rate, unusual accounts.
- Export a list to Excel, formatted and ready to send.
- Explain an account, a balance or a variance in two sentences to someone who is not an accountant.
With your confirmation (open only after trials)
- Create contacts from a list.
- Prepare a draft invoice or quote to review before sending.
- Suggest postings for documents waiting to be processed.
To avoid or to supervise very strictly
- Posting entries without review.
- Changing or deleting invoices that have already been sent.
- Touching salaries, settings or closed periods.
All of this assumes clean accounts to begin with: an AI working on badly allocated entries only produces errors faster. Our guide to the bookkeeping obligations of a self-employed person sets out the basics to have in place.
Free, no-obligation first conversation. Request a quote
Six things to remember
- Create the token at developer.bexio.com/pat, with a clear name and, if possible, from a user with limited rights.
- Note the expiry: 60 days, a calendar reminder on day 55.
- Choose where to store it: a password manager or an environment variable. A plain-text .md file only outside synchronisation and outside Git.
- Test with a harmless read before any real question.
- Stay read-only until you have checked several answers by hand.
- Delete the token in the developer portal as soon as you no longer need it, or if in doubt.
We can help you set it up
Connecting Bexio to Claude is mostly about choices: which access, which storage, which uses, which limits. We work in Bexio every day and can help you set up the connection and define use cases that make sense for your business, while keeping control over what is written in your accounts. The first conversation is free and without obligation, and we can hold it in French or in English. Official filings with the Geneva authorities, however, are made in French.
This article gives general guidance. Bexio’s access conditions may change: check them on the developer portal before you start. For a specific situation, let’s talk during a first conversation.