Operations

Accounting Software for Accountants in Kenya

What actually matters when you are managing books for multiple clients, and how to tell the difference between single-business tools and software built for a practice.

Sentibooks · · 5 min read

Most accounting software is built for one business. One set of books, one chart of accounts, one login that sees one company. That works fine if you are the owner of a single SME.

It does not work if you are an accountant serving fifteen clients.

This guide covers what breaks when a single-business tool meets a practice, what a multi-client system actually needs to do, and how to evaluate any provider before you commit.

What breaks when you use a single-business tool for a practice

Three problems show up within the first month.

You run out of logins. A single-business tool gives you one workspace. To serve fifteen clients you either buy fifteen subscriptions, or you share credentials, or you use your own login and take on the risk that one client’s records sit next to another’s.

Reconciliation becomes a schedule. Downloading statements, matching, exporting, sending. Multiply that by fifteen clients and the month disappears.

You lose the audit trail. When a client asks “who changed this entry”, a tool designed for one owner cannot tell you. It was you. That is the answer. There is no way to prove it was not the client, because there is only one login.

The cost of these three problems is not the software subscription. It is the unbilled hours. Most practices lose between 30 and 50 percent of their capacity to client admin that a proper multi-client system handles automatically.

What multi-client software actually needs to do

Six capabilities, in order of how often they come up in practice.

Separate workspaces per client. Not a tag on a transaction. A proper separation where each client’s books, chart of accounts, and users are distinct. One login, switch between workspaces, no cross-contamination.

Client access controls. Some clients want to see their own books. Some want to enter transactions themselves. Some want both, with approval. The system needs to support read-only access, entry-level access, and a way to review before anything posts to the books.

Cross-client reporting. When you want to know how many of your clients are overdue for VAT filing, or which ones have a cash flow issue in the next 30 days, you need a report that spans workspaces. Not fifteen exports stitched together in Excel.

Deadline tracking. KRA deadlines do not move. PAYE and SHIF by the 9th, VAT by the 20th, annual returns by the 30th of June. A practice system should show you which clients have what due, and which ones have not filed yet.

Fast, standardised onboarding. A new client should be ready to take their first transaction in under an hour, not a week. The chart of accounts, tax profile, and reporting structure should all come from a template the practice controls. Every client set up the same way, so reports are comparable across the whole book and staff can move between workspaces without relearning the setup.

Activity logging. Every entry, who made it, and when. This is what protects you when a client disagrees about a number three months later.

If a tool does not have all six, it is a single-business tool with a client list. Not a practice system.

The Kenyan layer

Most international practice management tools assume a foreign tax system. For a Kenyan practice, the software also needs to handle:

  • VAT on invoices and purchases, with the correct treatment for zero-rated and exempt items
  • PAYE, SHIF, NSSF, and Housing Levy calculations per employee
  • KRA PIN fields on every invoice, per client
  • The Kenyan chart of accounts, per client, without rebuilding it from scratch every time
  • iTax-ready VAT summaries you can hand to the client or file yourself

If a provider cannot explain how it handles each of those, it has not been built for this market.

What to ask before committing

Six questions, in a written demo where the provider shows the answer on screen rather than describing it.

  1. Show me one login that has fifteen client workspaces and how you switch between them.
  2. Show me a client with read-only access to their own books, alongside my full access to the same books.
  3. Show me a report that lists every client who has not filed VAT this month.
  4. Show me setting up a new client workspace from a template, end to end.
  5. Show me the audit log for one transaction, from entry to current state.
  6. Show me a Kenya VAT return produced for one client, exported without manual edits.

If any of the six takes more than two minutes to demonstrate, the answer is no.

What Sentibooks actually does

Sentibooks is a multi-client system from the ground up. One login, separate workspaces per client, each with its own chart of accounts, users, and permissions. Activity is logged per workspace, so when a client asks who changed what, the answer is a record, not a memory.

The Kenyan layer is built in. VAT calculates automatically on invoices and purchases. Payroll handles PAYE, SHIF, NSSF, and Housing Levy. The chart of accounts is preloaded per workspace. Reports export ready for iTax.

For a practice, the difference is capacity. The admin hours that go into reconciliation, exports, chasing, and rebuilding client data come back. Most of our accounting customers recover their software cost in the first month of running fifteen or more clients.

Start a free trial and set up your first ten client workspaces.

Try Sentibooks free

Manage invoicing, expenses, payroll, VAT and full accounting in one place.

Start free trial