Buyer's guideNo named competitors

Choosing bookkeeping software you can hand to a CA

The books your accountant actually trusts are the ones where nothing can be quietly edited after the fact. Six questions about append-only entries, honest reconciliation, and what a tool should never claim to do on your behalf — with Automix's own answer to each.

See what Khata already does Read the technical docs

What this guide will not do

No named or characterised competitorNo invented statistic or ratingHonest where our own answer is a limit

Before you buy

A CA does not want a summary. A CA wants to know nothing was quietly changed.

Bookkeeping software gets judged on two contradictory things at once: how easy it is for a business owner with no accounting background to use day to day, and how much a qualified accountant can actually trust the resulting books once handed over. The second requirement is the one most demo videos skip, because it shows up as friction — a correction that cannot just overwrite the original entry, a closed period that refuses a write even from the owner.

Six questions worth asking any bookkeeping tool follow, with Automix's own answer to each about Khata, the bookkeeping-preparation agent. One structural fact worth stating up front: Khata is built to get your books into a reviewable state and stop there. Under India's Chartered Accountants Act, only an ICAI member may sign off in a professional capacity — so nothing in this product, now or after any future change, claims to certify, sign, or file on your behalf. That is a boundary by design, not a missing feature.

Ask what it refuses to do

A tool with no refusals has not thought about the edges of your business.

These are specific refusals in Automix's own code, named so you can ask the same question of anything else you evaluate.

It will not let a posted journal entry be edited or deleted

There is no PATCH or DELETE route on the ledger — a mistake is corrected by a new, linked entry that leaves the original visible, never by erasing it.

It will not accept a write against a closed accounting period

A closed period refuses every write outright. Reopening it is a separate, reason-required, audited action — not a setting a workspace can quietly flip back.

It will not claim to certify, sign, or file your books

The handoff status model has no value meaning certified, signed off, or filed — because only a qualified accountant may do that. Khata's job ends at getting the books into a reviewable state.

Evaluation criteria

6 questions to ask any vendor in this category.

Ask these of Automix and of anything else on your shortlist. The status pill is how the honest answer scores today, not a claim of perfection.

Once an entry is posted, can it be edited or deleted — or only corrected with a visible trail?

Why it matters. Books that can be quietly edited after the fact are books a CA cannot certify without re-deriving everything from source documents, which defeats the purpose of digital bookkeeping altogether. The honest version of a ledger treats every entry as a historical fact: wrong entries get corrected by a new, linked entry, never erased.

How Automix answers it. Journal entries are append-only. A correction is a new entry linked to the original, and there is no PATCH or DELETE route on the ledger at all — not a permission that is usually off, a route that does not exist. Money is stored as integer minor units beside a currency column, never a float, and the trial balance is recomputed rather than cached.

Works today

Is the audit trail actually unmodifiable, or just a log screen nobody has tested against?

Why it matters. An 'audit trail' that has a delete or edit route sitting next to it, even one an admin uses rarely, is not really an audit trail — it is a log that happens to survive most days. The test worth applying: does any route in the product write to, or remove from, the audit log, or only read it?

How Automix answers it. Every mutating handler writes an append-only entry naming the actor, the action, the entity and the detail. The only public surface over the audit trail is a GET — no route in the product writes, edits, or deletes it.

Works today

When a period is closed, does it actually refuse writes — and can reopening happen quietly?

Why it matters. A 'closed' period that still silently accepts a backdated entry is worse than no period-locking feature at all, because it looks safe. The reopen path matters just as much: reopening a closed period with no record of who did it or why is the same problem one step removed.

How Automix answers it. A closed period refuses every write outright. Reopening is a separate, explicit route that requires a stated reason, and every reopen is counted and audited. The year-end checklist itself is built too: an eight-task standard template — close every period, reconcile every bank account, clear the low-confidence document queue, confirm categorisation rules still match real vendors, compile the GSTR and TDS worksheets, value closing stock or waive it with a reason, prepare the accountant handoff pack — generates once per fiscal year and returns the same tasks on a repeat request rather than duplicating them. Each task can be marked done or waived, waiving requires a stated reason, and the checklist also lists every ledger entry posted into a period after it was reopened, recomputed from the ledger and reopen history on every call rather than cached in a table that could go stale. It states plainly that 'checklist complete' means ready for a Chartered Accountant to review, not an audit sign-off — only closing a period actually stops writes.

Works today

When bank reconciliation cannot match a transaction, does it tell you, or quietly shrink the unmatched list with a guess?

Why it matters. Automated matching that silently accepts a low-confidence suggestion to make the unmatched count look smaller is the single easiest way for a reconciliation tool to look more finished than it is. The honest version keeps every unconfirmed match visible until a human confirms it.

How Automix answers it. A CSV upload is parsed with no credential and no per-bank template — you name your own column headers (amount, or separate debit/credit, plus date and description) and it handles the format variation that would otherwise need one. Imported statement lines get scored match suggestions, but matching itself always needs a human confirmation — the unmatched remainder is always returned in full and never shrunk by an unconfirmed suggestion. Excel and PDF exports still need a manual CSV re-export first, and a live bank-feed connection is not built.

Works today

When it suggests an expense category, does it say why — and stay silent when it is not confident?

Why it matters. A categorisation feature that always returns a guess, even a low-confidence one, trains you to stop checking it. The more useful behaviour is narrower: suggest only when a real rule matches, and say nothing rather than default to the most common category.

How Automix answers it. Categorisation is driven by priority-ordered vendor and narration rules that a workspace writes, each suggestion naming the rule that produced it. When no explicit rule matches, it now falls back to how this exact vendor was categorised before — read straight from the audit trail rather than a second learned-weight table, so the count behind the suggestion is the same number you could verify by reading the log yourself, and it is labelled as vendor history, never presented as a rule. With neither a rule nor any history, the route still returns nothing rather than a default guess.

Works today

Does the tool ever claim to certify, sign off, or file your books on your behalf?

Why it matters. This is the boundary that matters most for anything called 'bookkeeping software.' A tool that implies it can replace a qualified accountant's sign-off is making a claim it has no legal standing to make, and a business that relies on it could find that out at the worst possible time — during an audit or a filing deadline.

How Automix answers it. No. The handoff pack Khata produces is a recorded state carrying a stored trial-balance snapshot and everything outstanding for review — but the status model behind it has no value meaning 'certified,' 'signed off,' or 'filed.' That absence is structural: Khata gets the books into a reviewable state and stops, because only a qualified accountant may sign off in a professional capacity. Inviting an accountant is built: a one-time bearer token this deployment never stores in the clear, accepted by link into real workspace membership, plus comments and change requests that hit the same audit trail as any other action. The one gap is delivery — this deployment has no ZeptoMail key configured, so the invitation is created and can still be accepted by link, but the email carrying that link is not actually sent.

Needs your setup

Where we do not measure up yet

In one place: which of the answers above is not a green light.

Pulled straight from the criteria above, not a separate list — a guide that scores itself full marks on every criterion is not one you should believe, ours included.

Does the tool ever claim to certify, sign off, or file your books on your behalf?

No. The handoff pack Khata produces is a recorded state carrying a stored trial-balance snapshot and everything outstanding for review — but the status model behind it has no value meaning 'certified,' 'signed off,' or 'filed.' That absence is structural: Khata gets the books into a reviewable state and stops, because only a qualified accountant may sign off in a professional capacity. Inviting an accountant is built: a one-time bearer token this deployment never stores in the clear, accepted by link into real workspace membership, plus comments and change requests that hit the same audit trail as any other action. The one gap is delivery — this deployment has no ZeptoMail key configured, so the invitation is created and can still be accepted by link, but the email carrying that link is not actually sent.

Needs your setup

Questions

Common questions.

Does Khata replace my chartered accountant?

No, and it is built specifically not to imply that it does. It prepares books, flags what is outstanding, and produces a handoff pack — the sign-off itself is a qualified accountant's responsibility, and the product's own status model has no way to represent that step happening.

Can I fix a mistake in an already-posted entry?

Yes, but not by editing it — a correction is posted as a new entry linked to the original, so anyone reviewing the books later can see both the mistake and the fix rather than a silently altered number.

What happens if I need to reopen a closed period?

You can, but it needs a stated reason and is recorded in the audit trail every time — there is no quiet way to reopen a period and change something without a record of it.

Can Khata read a photographed or scanned receipt?

The register, duplicate-checksum refusal and document lifecycle work locally today. Reading a scanned image specifically still needs an OCR credential this deployment does not have configured — that half is not built yet.

If bank reconciliation cannot match a transaction, will it guess?

No — an unmatched transaction stays in the unmatched list until a human confirms a suggested match. Nothing is auto-accepted to make the unmatched count look smaller.

Is Khata available to use today?

Not yet — its status is Coming soon, the same honest label shown next to every agent that is still in build on this site.

Apply it

Apply these six questions to Khata, and to whatever you use today.

The ledger, the audit trail and the period lock are real today. Ask any bookkeeping tool you evaluate to show you its equivalents, not just describe them.

See what Khata already does Read the technical docs

Khata's own status today:Coming soon

More buyer's guides

Buyer's guide

How to choose a WhatsApp business tool

Six questions that matter more than the feature list any vendor hands you — plus the one constraint every tool built on Meta's Cloud API shares, whether its marketing page mentions it or not.

Read the guide

Buyer's guide

What to look for in a CRM for a small sales team

The feature list on a CRM's homepage is never the reason a required field gets skipped six months in. Six questions about what actually holds under an import, a bulk edit, or a rushed Friday afternoon — plus Automix's own honest answers.

Read the guide

Buyer's guide

Choosing a social media scheduling tool

The word 'scheduled' hides more than it reveals. Six questions about approvals, invented engagement data, and what actually happens when a post's date arrives — with Automix's own honest answer, including the one place nothing actually publishes yet.

Read the guide

Choosing bookkeeping software you can hand to a CA

What this guide will not do

No named or characterised competitorNo invented statistic or ratingHonest where our own answer is a limit

Choosing bookkeeping software you can hand to a CA

A CA does not want a summary. A CA wants to know nothing was quietly changed.

A tool with no refusals has not thought about the edges of your business.

It will not let a posted journal entry be edited or deleted

It will not accept a write against a closed accounting period

It will not claim to certify, sign, or file your books

6 questions to ask any vendor in this category.

Once an entry is posted, can it be edited or deleted — or only corrected with a visible trail?

Is the audit trail actually unmodifiable, or just a log screen nobody has tested against?

When a period is closed, does it actually refuse writes — and can reopening happen quietly?

When bank reconciliation cannot match a transaction, does it tell you, or quietly shrink the unmatched list with a guess?

When it suggests an expense category, does it say why — and stay silent when it is not confident?

Does the tool ever claim to certify, sign off, or file your books on your behalf?

In one place: which of the answers above is not a green light.

Does the tool ever claim to certify, sign off, or file your books on your behalf?

Common questions.

Apply these six questions to Khata, and to whatever you use today.

Evaluate the rest of your stack.

How to choose a WhatsApp business tool

What to look for in a CRM for a small sales team

Choosing a social media scheduling tool

Choosing bookkeeping software you can hand to a CA

A CA does not want a summary. A CA wants to know nothing was quietly changed.

A tool with no refusals has not thought about the edges of your business.

It will not let a posted journal entry be edited or deleted

It will not accept a write against a closed accounting period

It will not claim to certify, sign, or file your books

6 questions to ask any vendor in this category.

Once an entry is posted, can it be edited or deleted — or only corrected with a visible trail?

Is the audit trail actually unmodifiable, or just a log screen nobody has tested against?

When a period is closed, does it actually refuse writes — and can reopening happen quietly?

When bank reconciliation cannot match a transaction, does it tell you, or quietly shrink the unmatched list with a guess?

When it suggests an expense category, does it say why — and stay silent when it is not confident?

Does the tool ever claim to certify, sign off, or file your books on your behalf?

In one place: which of the answers above is not a green light.

Does the tool ever claim to certify, sign off, or file your books on your behalf?

Common questions.

Apply these six questions to Khata, and to whatever you use today.

Evaluate the rest of your stack.

How to choose a WhatsApp business tool

What to look for in a CRM for a small sales team

Choosing a social media scheduling tool