Repeat vendors need no re-decision
The electrician, cement supplier, and site labour contractor get the same category suggested every month, instead of the owner choosing from a dropdown eleven times for the same answer.
Available now
In build
The whole team
Nineteen specialists, each with a defined job and an honest status label.
See all nineteenExpenses land in the right category (rent, salaries, supplies, utilities) automatically instead of the owner deciding from scratch every time.
Works with
What it does
Khata learns from how the owner (or their CA) has categorized similar vendors and expense descriptions before, and suggests the same category for new, matching transactions. The owner accepts or overrides each suggestion, and Khata remembers the correction for next time.
A contractor paying the same electrician, the same cement supplier, and the same site labour contractor every month used to pick a category from a dropdown for every single payment, even though the answer was almost always identical to the last one made. A year of that adds up to hours spent re-deciding something that was already decided eleven times before, without changing.
Expense categorisation learns from how the owner, or their CA, has categorised similar vendors and descriptions in the past, and suggests the same category the next time a matching transaction appears. The owner accepts or overrides each suggestion, and a correction is remembered for next time — but the suggestion is a time-saving draft, never a tax determination. Whether an expense is actually deductible, or how it should be treated for tax, stays entirely the CA's call to make.
Khata runs this directly on the platforms your customers already use — no separate app for them to install.
How it works
Khata looks at how the owner or CA has categorised similar vendor names and expense descriptions before, and proposes the same category for a new transaction that resembles them closely enough to genuinely match, most of the time.
Each suggestion is reviewed and either accepted with one tap or corrected to a different category, so nothing is ever filed away without the owner having actually seen and deliberately confirmed exactly where it landed.
An override updates the underlying rule, so the next matching transaction from that vendor or description gets the corrected category suggested automatically instead of repeating the exact same original mistake all over again on the next matching bill.
Because the learned rule reflects what the owner picked, not necessarily what the CA would prefer, a periodic CA review checks for any categories that have quietly drifted from how the CA actually wants them classified going forward.
Why it matters
The electrician, cement supplier, and site labour contractor get the same category suggested every month, instead of the owner choosing from a dropdown eleven times for the same answer.
Overriding a wrong suggestion updates the rule for that vendor going forward, so the same mistake doesn't need fixing again on every future transaction from that supplier.
Expenses arrive already sorted into categories close to what the CA expects, turning their review into spot-checking and adjusting rather than classifying every line from scratch.
The detail
Category suggestions exist to save the owner a repetitive decision, not to make a tax decision on their behalf. Khata never decides whether an expense is deductible or how it should be tax-treated — a category label like "office supplies" or "site materials" is a bookkeeping bucket the CA later reviews and, where the tax treatment requires it, reclassifies or adjusts as needed. The suggestion engine's only job is pattern-matching against how this owner and this CA have categorised similar things before; it has no independent view of tax law.
The learning mechanism carries a specific, quiet risk worth understanding clearly. A single wrong correction can miscategorise a whole vendor's future expenses until someone notices the pattern. If an owner mistakenly recategorises one supplier's payment under the wrong bucket, every subsequent payment inherits the same wrong suggestion, compounding the error rather than catching it. A periodic CA review is meant to surface exactly this drift — not because the system is unreliable, but because a learned rule reflects what was clicked, not necessarily what was correct.
The more common and less dramatic version of this same risk is simple drift between what an owner picks day to day and what a CA would actually prefer for that category. An owner categorising quickly between customers optimises for speed; a CA reviewing months later optimises for correctness against the tax treatment the category implies. Neither is wrong exactly, but they can diverge, which is why the suggestion is framed as a draft awaiting the CA's review, not a settled classification once accepted.
Industry use cases
12 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 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 moreThe owner can see at a glance which bank transactions already match a recorded invoice or expense, and which ones still need attention.
Learn moreQuestions
No. A category suggestion is a bookkeeping label based on how similar transactions were categorised before — it says nothing about whether the expense is deductible or how it should be tax-treated. That determination is your CA's, made when they review the prepared books, not something the categorisation feature decides independently on its own, however confident the suggestion looked at the time.
The correction gets remembered and applied to future matching transactions from that vendor or description, which means an incorrect override can propagate forward until it's noticed and properly fixed again. This is exactly why a periodic review, ideally with your CA, is worth doing rather than assuming every learned rule stayed accurate indefinitely without ever properly checking it against what the CA would actually prefer for that vendor.
A category you pick quickly while running the business day to day can drift from what your CA would classify the same expense as, once they're looking at it with the tax treatment in mind rather than speed. A periodic review catches that drift before it affects a return, which is a normal, expected part of the CA's role rather than a sign something went wrong.
A suggestion appears for you to accept or override, but it's a draft until you act on it — categorisation doesn't happen silently in the background without your input at all. This keeps every category that ends up in the books traceable to a decision you actually made, or explicitly accepted, rather than one applied silently and automatically without your knowledge or explicit say.
The rest of your stack
No rip-and-replace — auto-sort expenses into categories works alongside the systems already running your business.
Coming soon