Vai al contenuto

Practice software for accounting firms

We do not sell you a practice system. We make the ones you have work together, and build the pieces that are missing.

In breve

An accounting firm does not have a practice-system problem: it usually has three or four systems that do not talk to each other, plus the spreadsheets filling the gaps between them. Xion does not sell a competing system: it makes the ones you have communicate, removes the double entry, and builds to measure the pieces no standard product covers. The flow analysis is free.

We do not replace your practice system

Whoever knows it is an asset and should be kept. The problem is almost never the system - it is what sits between one application and the next.

Double entry can be removed

Every figure rekeyed by hand is time lost and a point where the chain can break. Almost always it is avoidable.

Custom only where needed

We build something new when no standard product covers it, not as a matter of principle.

The problem is not the practice system. It is what sits in between

When an accounting firm calls us about “a software problem”, in the great majority of cases the practice system works perfectly well. What does not work is everything around it.

An average firm uses three or four different applications — accounts, payroll, tax filings, document management — often from different vendors, each perfectly in order on its own. Between one and the next there is nothing, and that nothing gets filled by a person rekeying data, by a spreadsheet somebody keeps updated, and by a habit nobody has ever written down.

The cost of that nothing appears on no invoice, and it is high: hours of qualified work spent copying, and it is also the point where a figure can go wrong without anybody noticing.

Where data gets lost in a firm

It is always the same four points, and you will recognise them immediately.

Between accounts and payroll. The same client records and the same transactions, entered twice into two systems that do not talk.

In the documents arriving from clients. Invoices, receipts, contracts, in every imaginable format, which somebody opens, looks at, renames and files by hand. It is the most repetitive and most easily automated work there is in a firm.

Towards the authorities’ portals. Filings, submissions, receipts to download and reconcile. Much of this is already automatable and almost nobody automates it.

In the client records. The same client company exists in three systems with three versions of the data, and nobody knows which is the right one. It is the dullest problem and the one that generates the most errors downstream.

What we do, in order

First we look at the flow, not the software. We follow a document from the moment it enters the firm to when it leaves, noting every time a person touches it. It is a few days’ work and it almost always produces the first real map of how the firm actually functions.

Then we verify what is technically possible. Some practice systems expose a way of being queried from outside, others do not, as a commercial choice. This has to be established before promising anything, and the answer changes the options.

Then we automate the stretch with the best return. Not everything: the step that consumes the most hours and has the fewest exceptions. An automation that works in eighty per cent of cases and leaves the rest to a person is worth far more than one that tries to cover everything and breaks.

Custom only where needed. We build something new — a portal, a web app, an internal tool — when no standard product covers that process. Not as a matter of principle, and not before verifying that it does not already exist.

The client portal, when it makes sense

It is the most frequent request after integration, and it is worth being honest about when it pays.

It pays if the firm exchanges documents with many clients and does so today by email — which is awkward to search, heavy to file, and questionable when third parties’ data is inside. A portal gives each client their own space, with the right permissions and a record of who uploaded what and when.

It does not pay if there are few clients, or if they will not use it. A portal nobody opens is worse than email, because it adds a channel instead of replacing one. The question to ask beforehand is how your clients actually work, not how elegant the tool is.

The rest of the firm’s IT

A project like this rests on things that have to be in order already: individual logins rather than one shared account, client credentials kept in a manager rather than a spreadsheet, backups that genuinely restore and that capture the practice databases properly.

See also IT, AI and security for accounting firms, AI for accounting firms for the document side, and custom software development for the method.

The first step

We follow a document from entry to exit and count how many times somebody touches it. Out of that comes the list of what can be taken out of the way, with priorities. Free and without obligation.

Frequently asked questions

Are you going to suggest we change practice system?

Almost never, and it is the first thing we make clear. Whoever knows your system and its automations is an asset to the firm, and replacing it carries a learning cost that is rarely repaid. The problem we usually find is not inside the application - it is at the point where two different applications ought to talk and do not, so somebody bridges the gap with a keyboard.

What can be integrated in practice?

The most frequent cases are passing data between the accounting and payroll systems, automatically acquiring the documents clients send, connecting to the portals where filings are submitted, and aligning client records, which in firms often live in three different places with three versions of the same company. Which of these are possible depends on what your vendor exposes to the outside, and it gets verified before anything is promised.

What if the vendor does not allow integration?

It happens, and it should be said at the outset rather than discovered once work has started. Some applications expose nothing externally as a commercial choice. In those cases there are two routes - working with the import and export formats that exist anyway, or moving the automatable part of the process outside the system. Neither is elegant, but both work better than rekeying by hand.

How long does a project like this take?

The flow analysis closes within a few days. Individual integrations are measured in weeks rather than months, because we work in steps with a useful result at the end of each rather than one release after six months. We avoid the filing-deadline windows regardless, since they are the worst possible moment to introduce any change.

Who maintains what you build?

The same team that built it. An integration is not a finished object: when the vendor updates their version, the connection has to be checked. It is why this work makes sense inside an ongoing relationship rather than as a one-off delivery.

Tell us about the process you do by hand today

The projects that work start from one precise, repetitive activity rather than from a list of features. Describe it and we will tell you whether automating it is worth it.