<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Accounting on Tarif590</title><link>https://tarif590.ch/en/blog/topics/accounting/</link><description>Recent content in Accounting on Tarif590</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 10 Sep 2026 18:30:54 +0200</lastBuildDate><atom:link href="https://tarif590.ch/en/blog/topics/accounting/index.xml" rel="self" type="application/rss+xml"/><item><title>Why tarif590 does not currently offer a Bexio integration</title><link>https://tarif590.ch/en/blog/why-no-bexio-integration/</link><pubDate>Wed, 09 Sep 2026 09:00:00 +0200</pubDate><guid>https://tarif590.ch/en/blog/why-no-bexio-integration/</guid><description>&lt;p&gt;We briefly assessed the technical side of a Bexio integration. A connection
using Bexio’s REST API would be feasible for us. We then reviewed the
commercial terms, which were decisive for our decision.&lt;/p&gt;
&lt;p&gt;An integration could save work for practices that already use Bexio for their
accounting because they would not have to transfer invoice data a second time.&lt;/p&gt;
&lt;p&gt;The two programs handle different tasks. A practice records patient details,
treatments, and insurance information in tarif590. tarif590 uses these details
to create the correct Tarif 590 invoice. Bexio, by contrast, is designed for
general accounting. It manages items such as income, expenses, supplier
invoices, and bank payments.&lt;/p&gt;</description></item></channel></rss>