Built from inside practice. Built by Mr H Hammad FCCA, ACA, ICAEW Chartered Accountant and current CEO of a UK accountancy practice.
ProductFor ClientsWhy BalansixPricingResourcesSupportBook a demoContact
BalansixWhy Balansix

We did not start with software. We started with a practice.

Balansix was conceived from first-hand experience of running an accountancy practice across disconnected systems and repeatedly rebuilding the same client information and accounting work.

Built for UK accountancy practices.

The fragmented stack

One client, many handoffs

Practice managementProposal & engagementBookkeepingYear-end spreadsheetsAccounts productionAdvisory reporting
VS
The Balansix approach

One client, one connected record

Services feed recurring workRecords feed accountingAccounting feeds year endSchedules feed journalsTrial balance feeds accountsAccounts feed advisory
Mr H Hammad FCCA, ACA, founder of BalansixAdd your photograph as
assets/brand/founder.jpg
Mr H Hammad FCCA, ACAFounder, principal architect, designer and developer of BalansixICAEW Chartered Accountant · CEO of a UK accountancy practice
Founder principle

The objective was not to build another accounting application. It was to build the operating platform we wanted to use inside an accountancy practice.

Balansix was built by Mr H Hammad FCCA, ACA, an ICAEW Chartered Accountant and the current CEO of a UK accountancy practice. That practical context shapes the workflows, controls, terminology and emphasis on professional review.
Three product principles

The design decisions come from the work.

1

Do the work once

Information and accounting outputs should move forward instead of being re-keyed into the next application.

2

Automate certainty

Routine repeatable outcomes can be automated; incomplete and judgement-heavy items should remain visible.

3

Keep professional control

Permissions, audit trail, review states, accounting locks and controlled finalisation remain part of the product architecture.

The case for changing

Six reasons a practice moves to Balansix.

Changing software is a professional risk, not just a purchase. These are the reasons that justify taking it.

01

You stop paying five times

Receipt capture, a bookkeeping ledger, a final-accounts package, an engagement-letter tool, an advisory report builder and a timesheet spreadsheet become one subscription with one renewal date, one support relationship and no integrations to keep alive.

02

Year end becomes a review

Depreciation, accruals, prepayments, accrued and deferred income, loan schedules and payroll journals post as the year runs. You open the file to check work already done properly rather than to reconstruct twelve months of it in January.

03

Nothing is re-keyed

The trial balance the bookkeeping produces is the same trial balance the accounts are built from. No exports, no rounding differences between packages, no reconciling two systems that should already agree.

04

Compliance is native, not bolted on

FRS 102 Section 1A and FRS 105 statutory accounts, iXBRL tagging, CIS, director loan accounts and multi-entity clients are handled inside the platform because the person who specified them prepares them for a living.

05

Advisory stops being a separate project

The numbers that produced the accounts produce the advisory report. Turning a compliance client into an advisory fee stops requiring an evening of spreadsheet work per client.

06

Your recovery rate becomes visible

Staff time is captured as work happens against the job it belongs to, so you can see which clients are profitable and which are quietly subsidised — without asking anyone to fill in a timesheet on a Friday.

Practice-first, not business-first

Where Balansix differs from the tools you already use.

Xero and QuickBooks are established bookkeeping ecosystems and increasingly offer practice-facing tools in different combinations. Balansix takes a different starting point: it was designed around one connected UK practice workflow, from the client relationship and recurring work through bookkeeping, year end, final accounts and insight.

Statutory accounts
Produced natively from the same ledger under FRS 102 Section 1A and FRS 105, rather than exported into a separate accounts package.
Built around a firm
Many clients, jobs, statutory deadlines and team workload are first-class concerns, not an add-on to a single-entity product.
Year-end adjustments
Posted through the year by the platform, not left to the practice to calculate in a spreadsheet and journal in at the end.
One client record
Engagement, records, ledger, accounts, advisory and staff time on a single record instead of five that must be kept in step.
Why the name

Balance, and six pillars.

The six segments of the mark are the six pillars the platform is built on. Each one feeds the next rather than sitting in its own system, which is the whole argument in a single image.

01

Practice management

Clients, jobs, statutory deadlines, engagement letters and team responsibility, held once and used everywhere.

02

OCR & Capture

Client records arriving through their own portal, indexed against the right client and the right period.

03

Bookkeeping

A controlled ledger with scored bank matching, VAT and CIS, and a suspense queue for anything that should not be guessed at.

04

Final accounts

Statutory accounts from the agreed trial balance, with notes and disclosures drafted and iXBRL tagging built in.

05

AI Insights

Plain-English advisory reporting on performance, position and tax, built from the same figures.

06

Cloud & Secure

Individual user access, role-based permissions, audit trail and controlled cloud workflows designed around professional responsibility.

Professional risk

Why an accountant can trust the engine.

The reason most practices hesitate over new accounting software is not price. It is the professional exposure of relying on figures they did not calculate themselves.

Deterministic, not generative

The calculations, schedules and journals are coded logic. Depreciation, loan splits between amounts falling due within and after one year, accruals and deferred income are computed by rules that produce the same answer every time and can be explained line by line. No figure in your accounts is a model output.

Park it, never guess it

Bank matching is scored into three outcomes: confident matches post, borderline items are offered for a one-click confirm, and anything genuinely unclear goes to a suspense queue for a person to decide. Software that guesses to look clever creates review work, it does not remove it.

The file stands up to scrutiny

Every posting traces back to the document it came from, with review states and controlled finalisation part of the workflow. If a figure is questioned — by a client, a lender or an inspector — you can show where it came from.

Support that speaks accounting

Questions are answered by an ICAEW Chartered Accountant who runs a practice and wrote the specification, not by a first-line agent following a script. Most support questions in this profession are accounting questions wearing a software costume.

Before you decide

The questions practice owners ask.

Why should I move from software that works?

Only if the joins between your systems are costing you. The test is simple: count how many times one client is set up, and how much of your year-end file is reconstruction rather than review. If those numbers are high, the saving is real. If they are low, stay where you are.

Is it safe to rely on a new platform for statutory accounts?

Judge it the way you would judge a new member of staff — on a live file with a year end you already know the answer to. The accounting engine is deterministic coded logic, every figure traces to its source, and the first set of accounts produced on the platform is reviewed with you before anything is filed.

What happens to my existing clients and opening balances?

Migration covers opening balances, comparatives, fixed asset registers and outstanding items, reviewed together before the practice relies on the data. Practices are onboarded in small numbers precisely so this stage is done properly rather than quickly.

Can I keep using Xero or QUickBooks for some clients?

Yes. Practices rarely move everything at once, and there is no requirement to. Balansix is built around the practice's workflow, so it can carry the clients where the compliance work sits while others stay where they are.

Who is behind it if something goes wrong?

Mr H Hammad FCCA, ACA — an ICAEW Chartered Accountant, the current chief executive of a UK accountancy practice, and the founder, principal architect, designer and developer of the platform. He is subject to the same professional standards you are, and answers support himself.

Is it built for firms like mine?

It is built for UK accountancy practices from sole practitioners to multi-partner firms. It is not a bookkeeping product for business owners, and it is not an enterprise suite that needs a consultant to configure.

See the workflow that came out of real practice problems.

Bring one of your existing client journeys to the demo and compare how many handoffs Balansix can remove.