Every process, five times over
Most of your clients are on Xero. A good number are on QuickBooks because that is what their last bookkeeper used. A few are on Sage, one on FreeAgent because it came with their business bank account, and one long-standing client still sends you a desktop backup file.
Each package does things slightly differently. Your month-end checklist has footnotes for each one. New staff learn Xero first and panic when handed a Sage file. Firm-wide reports, like which clients have unreconciled items, can only be built for the package that happens to have the best reporting.
Why the mix persists
Clients choose their software for their own reasons, often before they meet you. Moving them costs them effort and you time, and there is rarely a good moment. So the firm grows by accepting whatever each client brings, and over the years the mix becomes permanent.
Practice tools and add-ons tend to favour one ledger. A firm-wide dashboard might work beautifully for Xero clients and simply leave the rest out, which is how the minority clients become the ones nobody is watching.
What a mixed base costs you
Training takes longer and mistakes are more likely on the less familiar packages. Checks that should be firm-wide cover only part of the base. Staff allocation is constrained, because only certain people can pick up certain clients. And decisions about moving clients are made on instinct rather than on what each move would save.
| Area | With one ledger | With a mix |
|---|---|---|
| Month-end checks | One checklist | A checklist per package |
| Firm-wide reports | Built once | Only for some clients |
| Staff cover | Anyone can pick up a file | Only those who know that package |
| Add-on apps | One integration each | Some clients left out |
How we build one working layer across ledgers
- We connect to each package through its own API where one exists: Xero, QuickBooks Online, Sage Business Cloud and FreeAgent all have them. For desktop packages, we work from scheduled exports.
- The data is mapped into one common shape for the things your firm cares about: bank accounts and reconciliation position, suspense and uncoded items, VAT periods, receivables, payables and key balances.
- Your firm-wide views, such as month-end status, review checks and client reports, are built on that common shape, so every client appears in them whatever package they use.
- Each view links back into the client's own ledger for the actual work, so staff still do the bookkeeping in the native package.
- A per-client summary shows how much of your effort that client takes compared with similar clients on other packages, to support decisions about migration.
- For clients you do decide to move, we script the opening balances, contacts and chart mapping as far as the packages allow, with a checklist for what must be done by hand.
We do not push clients to change. The layer makes the mix manageable; the migration view simply gives you facts for the conversations you choose to have.
A firm that works the same way for every client
Managers see the whole client base in one place instead of only the majority package. Checks and reports apply to everyone. Staff still need to know several ledgers, but the firm's own processes stop being written five times. And moving a client, when it makes sense, becomes a planned piece of work rather than a dreaded one.
Signs the ledger mix is hurting
- Your procedures have different versions for each package.
- Firm-wide dashboards leave out clients on the less common ledgers.
- Only one or two staff can handle certain clients.
- You have thought about moving clients but not worked out the case.
- At least one client is still on a desktop package.