Today, the handovers between bexio and your other tools are manual work. We close that gap: we connect bexio to your other systems through the official interface and let the data move on its own. Quotes, invoices, contacts and project hours, without double entry.
bexio covers the core process of a Swiss SME well. As soon as a second system comes in, such as an online shop, a CRM, a time tracking tool or a form on your website, a gap appears. Someone closes that gap by hand. Usually you or your assistant.
It typically looks like this: an inquiry comes in through a form, and someone types the contact into bexio. A project starts, the hours end up in another tool, and at the end of the month someone copies the lines into the invoice. The shop makes a sale, and the order is entered as a sales order afterwards.
bexio itself does not help here. Its own support article on API access says so clearly: bexio does not offer custom programming or implementation support (source: help.bexio.com, article 000001665, retrieved on July 31, 2026). The interface is open, but whoever uses it has to build the integration or have it built.
We don’t automate processes that happen once a quarter. Automation makes sense where the same manual step happens several times a week and a mistake costs money.
A form inquiry on your website creates a contact in bexio and a prepared quote with the right items. When the quote is accepted, the order and the task for delivery are created automatically.
Logged project hours become invoice items at the end of the month. Recurring invoices run without anyone touching them. Incoming payments are matched to the document, and open items trigger a reminder before the dunning stage starts.
Contacts are synced between bexio and your CRM in both directions, with a clearly defined leading system per field. Duplicates are detected before anything is written.
Logged hours flow from your project tool into bexio projects, assigned to customer, order and rate. Unbilled hours become visible before the month closes.
Orders from Shopify or WooCommerce become bexio sales orders, stock levels stay in sync, and invoices are created with the correct Swiss QR reference.
Then we check in the initial call whether it can be reached through the bexio API. We tell you honestly if it isn’t technically possible or not worth the effort.
The bexio API is a REST interface. It uses HTTPS methods and exchanges data in JSON format (source: docs.bexio.com, retrieved on July 31, 2026). You get access through OpenID Connect or a personal access token. Personal tokens expire after 60 days at most and are only suitable for testing. For production use, bexio provides OpenID Connect (source: developer.bexio.com, retrieved on July 31, 2026). An automation built on a personal token stops after two months. That is why we build with the method that holds up in production from day one.
The interface gives access to contacts, quotes, orders, invoices, credit notes, dunning, projects, time tracking and items, among others.
bexio offers an official Zapier connector in its own marketplace. That is enough for simple connections made of one trigger and one action. As soon as a workflow needs conditions, error handling or more than a handful of steps, the per-run bill gets expensive and the logic gets hard to follow.
We use n8n. The reason is practical: n8n can be self-hosted in Switzerland, the data doesn’t leave the country, and the cost doesn’t depend on the number of runs. The detailed comparison is on our business process automation page. If your case is solved with the Zapier connector, we tell you so and don’t build anything on top.
Not everything you can do in the interface works through the API. Bank connections run through bLink and are limited to the connected banks, currently including UBS, Raiffeisen, Zürcher Kantonalbank and Thurgauer Kantonalbank (source: help.bexio.com, article 000002294, retrieved on July 31, 2026). In the initial call we check whether your process can be reached technically at all, before you order anything.
Enter how often a bexio task happens at your company and how long it takes. The numbers come from you, we just add them up. None of it leaves your browser unless you request a report.
That is about 0 working days per year freed up for other work. Estimates, not a quote.
Your report is on its way (in German). Check your inbox, and if nothing arrives, your spam folder too. We will get in touch within the next few working days.
We map your processes and check what the bexio API can reach. Then we build the first workflow, test it in parallel with your manual work and only switch over once the results match. After that we monitor operations. The full four-step approach is described on the business process automation page.
We look at your processes and check what the bexio API offers. The result is a prioritized list with effort estimates.
Test data first, then parallel operation next to your current manual work. We switch over once the results are correct across several runs.
We monitor the workflows and adapt them when bexio changes its interface. You get an alert before you notice anything is stuck.
At SEOX, bexio automation is led by Enzo, our data architect. He knows how the data models behind contacts, documents and projects are built, and where the interface has quirks you only notice in production.
Add to that 25+ years in digital business and 46+ client projects. SEOX GmbH is based in Kreuzlingen, Thurgau. Your contact is a person, not a ticket system, and you can work with us in English.
Three building blocks, each available on its own. We work with fixed prices per automation instead of hourly billing. We name the price once we know what it’s about.
How you get to a price:
Operation is cancellable monthly. With a 12-month term you get a 5% discount.
We work with fixed prices per automation instead of hourly billing. The price depends on how many systems are involved and how many special cases the workflow has to cover. A simple link between a web form and a bexio contact is at the lower end, a two-way sync between shop, warehouse and bexio well above that. In the initial call you get a price range, and after the process analysis a binding fixed price.
You need API access. You request it through docs.bexio.com, and it is free. Before we start, we check whether your plan includes the modules your workflow touches, such as projects or time tracking. We tell you in advance if an upgrade would be needed.
No. Every workflow first checks whether a record already exists, then decides by clearly defined rules which system leads for which field. Where it makes sense, we create documents as drafts so you can look at them before sending. What the workflow writes and what it doesn’t is set down in writing before we start.
Not automatically. That is why monitoring is part of operations. We check the workflows continuously and get in touch before you notice something has stopped working. Adjustments to changes in the bexio API are included in the operations package. Without it, you get the automation handed over with documentation and can maintain it yourself or have someone else maintain it.
For simple cases, yes. bexio offers the connector officially, and if your workflow consists of one trigger and one action, you don’t need us. As soon as conditions, intermediate steps or error handling come in, Zapier’s cost per run goes up and the logic gets hard to follow. The comparison of Zapier, Make and n8n is on our business process automation page. In the initial call we tell you which category your case falls into.
Yes. bexio creates invoices with a Swiss QR reference by default, and automatically generated invoices are no exception. Payment matching runs through the bank connection. Via bLink, that is limited to the connected banks, including UBS, Raiffeisen, Zürcher Kantonalbank and Thurgauer Kantonalbank. We check in advance whether your bank is among them.
We run n8n on servers in Switzerland. The data moves between bexio and your systems without a detour through US services. Only what the workflow needs is processed. What is stored and for how long is in the documentation you receive for the project.
30 minutes, free, no sales pitch. You show us what you do by hand today, and we tell you what can run through the bexio API and what can’t. If nothing is worth it, we tell you that too.