No more email loops
A CA's question about an unclear line item gets asked and answered inside the workspace, replacing the days-long email back-and-forth of a spreadsheet sent and resent.
Available now
In build
The whole team
Nineteen specialists, each with a defined job and an honest status label.
See all nineteenThe business's CA can log in, see exactly the books and documents they need for the current period, and leave notes — without the owner emailing spreadsheets back and forth.
Works with
What it does
The owner invites their CA (or firm) into a shared workspace scoped to their business, where the CA sees the ledger, source documents, and prepared summaries with role-based permissions (view, comment, request changes). Every action the CA takes is itself captured in the audit trail like any other user's.
An edutech founder used to email a spreadsheet of the month's receipts to their CA, get a reply three days later asking about two unclear line items, and then email a corrected spreadsheet back, losing a week to a back-and-forth that should have taken an afternoon. Each email thread was its own version of the truth, and nobody was sure which one was current by the time the return was due.
The accountant collaboration workspace replaces that with a shared space scoped to the business, where the CA sees the ledger, source documents, and prepared summaries directly, with role-based permissions covering view, comment, and request-change. Every action the CA takes is captured in the same audit trail as anyone else's. There is no "certify," "file," or "sign off" action inside Khata; that stays on the CA's own letterhead entirely.
Khata runs this directly on the platforms your customers already use — no separate app for them to install.
How it works
The business owner sends an invitation scoped to their specific business, and the CA or their firm accepts it to gain access to exactly that business's books, not a shared pool across other unrelated clients.
The CA sees the ledger, source documents, and prepared summaries according to permissions set as view, comment, or request-change, so access matches exactly what that particular engagement actually requires, no more and no less than agreed at setup.
Instead of emailing a spreadsheet back and forth, the CA comments directly on a specific transaction or figure inside the workspace, and the owner sees and responds to that same feedback directly inside the same shared workspace.
A comment, a change request, or anything else the CA does inside the workspace is logged in the same append-only audit trail as any other user's actions, with no exception carved out anywhere for anyone, regardless of role.
Why it matters
A CA's question about an unclear line item gets asked and answered inside the workspace, replacing the days-long email back-and-forth of a spreadsheet sent and resent.
Both owner and CA look at the same live ledger and documents, so there's no ambiguity about which spreadsheet version, among several email attachments, is current.
Role-based permissions mean the CA sees exactly the ledger and documents relevant to that business, at exactly the access level that specific engagement genuinely calls for, nothing broader.
The detail
The workspace is built around a specific, deliberate limitation: there is no action inside Khata labelled "certify," "file," or "sign off," for the CA or for anyone else at all. This reflects that only an ICAI member, on their own letterhead, can attest to or certify financial statements, a role reserved to them under Section 26 of the Chartered Accountants Act, 1949. A software workspace has no standing to grant that role a digital action that could be mistaken for it.
What the workspace does grant is meaningfully useful without ever brushing against that boundary: view access to the ledger and source documents, the ability to comment on a specific figure or transaction, and the ability to request a change the owner then acts on themselves. This mirrors what a CA already does in an engagement — asking questions, flagging issues, requesting corrections — without the multi-day email loop that used to carry it. The CA's actual professional work, deciding what a figure means and ultimately signing whatever needs signing, happens exactly where it always has: on the CA's own systems and letterhead.
Access control carries its own real risk, separate from the certification boundary entirely. Misconfigured permissions can expose more financial and personal data than an engagement calls for, particularly if a CA's junior staff inherit the same access without a narrower scope. And a CA relationship ending without the invitation revoked leaves an orphaned access grant open — a workspace outliving its engagement is a real, if easily fixed, hazard to manage.
Industry use cases
13 industries where Khata applies this directly.
A car service center owner photographs a stack of spare-parts supplier invoices at month-end, Khata extracts the HSN codes and tax amounts from each, and the owner's CA opens the shared workspace to review the compiled purchase summary before filing.
See the automotive playbookA wholesale distributor pays several transport contractors during the month, and Khata flags which payments likely crossed the TDS threshold for Section 194C, compiling a worksheet the CA reviews before determining the actual deduction and filing.
See the b2b sales playbookA small lending intermediary's CA needs to confirm the edit-log audit trail has been continuously active all year before signing the Rule 11(g) audit trail reporting requirement, and pulls the full log directly from Khata's audit trail view rather than requesting IT logs separately.
See the banking and finance playbookA beauty product retailer sells both services and boxed skincare products, and Khata separates the two revenue streams in the ledger while calculating a consistent closing valuation for the unsold stock ahead of the CA's year-end review.
See the beauty and cosmetics playbookAn online tutoring business receives course-fee payments through multiple gateways during the month, and Khata reconciles each gateway payout against recorded receivables so the CA sees one consolidated income summary instead of three separate statements.
See the education playbookA freelance designer invoices three clients in a month and photographs a handful of software-subscription receipts, and Khata compiles both sides into a period summary the freelancer forwards to their CA before the quarterly GST filing.
See the freelancers and consultants playbookA physiotherapy clinic owner uploads a batch of supplier invoices for consumables, and Khata extracts amounts and HSN codes while keeping patient names on any attached billing documents restricted to the clinic's own staff and CA, not broadly visible in reports.
See the health and wellness playbookA furniture retailer with showrooms in two states ships a large order that crosses the e-way bill value threshold, and Khata pre-fills the consignment and HSN details from the invoice so the dispatch team only needs to generate the bill itself on the government portal.
See the home decor and furnishing playbookA marketing agency pays several freelance video editors as contractors during a campaign, and Khata's TDS worksheet flags the professional-fee payments likely requiring deduction under Section 194J for the CA's review before the agency deducts and deposits tax.
See the marketing agencies playbookA real-estate broker running two project-specific entities under separate GSTINs views a consolidated cash-position dashboard for planning, while their CA still receives two entirely separate GST summaries, one per GSTIN, for filing.
See the real estate playbookA restaurant owner's UPI and card settlements land in the bank account a day after the sale, and Khata's reconciliation queue matches each day's POS batch total against the corresponding bank credit, flagging any settlement that hasn't landed within the expected window.
See the restaurants and food playbookA spa sells packaged skincare products in addition to treatments, and Khata applies the correct HSN code to product line items and the correct SAC code to service line items on the same invoice, keeping the tax split accurate for the CA's review.
See the spas and salons playbookA travel agency books hotel and transport packages from several vendors for a client tour, and Khata's purchase-matching report shows which of those vendor invoices are already reflected in GSTR-2B, letting the CA hold back ITC claims on the ones that aren't yet visible.
See the travel and tourism playbookMore from Khata
A business owner stops losing paper receipts because every bill is captured the moment it's created, from a phone camera, a forwarded email, or a bulk upload.
Learn moreThe owner no longer types out every item, date, vendor, and amount from a receipt by hand — Khata reads it and fills the fields.
Learn moreThe business creates invoices that already carry the correct GSTIN, HSN/SAC code, and tax split so nothing needs re-keying at return time.
Learn moreEvery sale, purchase, payment, and receipt lands in a proper double-entry ledger instead of a loose spreadsheet or paper khata.
Learn moreEvery edit to the books is permanently recorded with who changed what and when, satisfying the statutory requirement companies already face.
Learn moreExpenses land in the right category (rent, salaries, supplies, utilities) automatically instead of the owner deciding from scratch every time.
Learn moreQuestions
No — there is no "certify," "file," or "sign off" action anywhere in Khata, for a CA or anyone else at all. Under Section 26 of the Chartered Accountants Act, 1949, only an ICAI member can attest to financial statements in a professional capacity, and that happens on the CA's own professional letterhead and systems, never through any in-app action here.
Depending on the role-based permissions set for the engagement, the CA can view the ledger and source documents, leave comments on specific figures or transactions, and request changes for the owner to act on. It replaces the spreadsheet-by-email loop with a shared, current view — but every substantive review and professional judgement remains the CA's own, outside the app entirely.
Yes — a comment, a change request, or any other action the CA takes inside the workspace hits the same append-only audit trail as any other user's action, with no exception made for the CA's role at all. This keeps the full record of who did what, and precisely when, entirely complete regardless of who's acting on the account at any time.
Access needs to be actively revoked by the owner when a CA relationship ends — it doesn't expire automatically on its own accord. An unrevoked invitation left open after an engagement ends is an orphaned access grant, so treating revocation as a standard, deliberate step whenever a CA relationship changes is genuinely worth building into the business's own regular routine.
The rest of your stack
No rip-and-replace — share books with your ca securely works alongside the systems already running your business.
Coming soon