No more manual re-typing
A morning's stack of forty bills gets read and drafted automatically, freeing the hour that used to go into typing vendor names, dates, and amounts by hand into a spreadsheet.
Available now
In build
The whole team
Nineteen specialists, each with a defined job and an honest status label.
See all nineteenThe owner no longer types out every item, date, vendor, and amount from a receipt by hand — Khata reads it and fills the fields.
Works with
What it does
An OCR and document-understanding model reads each captured receipt or invoice and extracts vendor name, date, line items, tax amounts, and total, presenting them for the owner's one-tap confirmation. Anything the model is unsure about is flagged for manual review rather than silently guessed.
A trader who has just captured a stack of forty supplier bills still faces the slower job: typing out each vendor name, date, item, and tax amount into a spreadsheet by hand, squinting at a faded stamp or a handwritten total that could be a seven or a one. An hour of typing for a single morning's bills is a familiar, unpaid tax on running a small business.
OCR line item extraction reads each captured bill and pulls out the vendor, date, line items, tax amounts, and total, presenting them for a one-tap confirmation instead of manual typing. Anything the model isn't confident about gets flagged for a human to check rather than quietly guessed at, and every confirmed entry keeps its link back to the original image, so a fast read never becomes an unverifiable one for the CA later.
Khata runs this directly on the platforms your customers already use — no separate app for them to install.
How it works
An OCR and document-understanding model scans each captured receipt or invoice and pulls out the vendor name, date, line items, tax amounts, and total, presenting all of it as a draft entry rather than a finished one ready to post.
Anything the model isn't confident about — a smudged total, an unfamiliar vendor name, a handwritten figure — is routed to a review queue instead of being filled in silently as though it were already certain and correct.
The extracted fields display next to the original image for a quick visual check, and the owner accepts or corrects each one before it becomes part of the books, rather than letting it enter automatically without review.
Once confirmed, the entry stays permanently linked back to the source image it came from, so a later question about a specific figure can be checked against the actual document in seconds, rather than relying on memory or guesswork.
Why it matters
A morning's stack of forty bills gets read and drafted automatically, freeing the hour that used to go into typing vendor names, dates, and amounts by hand into a spreadsheet.
A smudged total or an unfamiliar vendor name is flagged for review rather than silently guessed at, which is exactly where a fast OCR read could otherwise go quietly wrong.
A confirmed line item stays linked to the original image, so a question about a number six months later is answered by opening the actual bill, not by relying on memory.
The detail
Extraction produces a draft, and only a draft, until the owner confirms it. This distinction matters more in Indian small-retail settings than it might elsewhere: a blurry photo of a crumpled thermal-paper receipt, a handwritten vegetable-market chit, or a faded carbon-copy invoice are all common inputs, and OCR error rates rise sharply on exactly this kind of source material. Khata never auto-posts an unconfirmed read as a final ledger entry — the model's job is to save typing, not to make a silent decision that a smudged four was actually a nine.
Confidence scoring is what makes the review step useful rather than performative. A clean, printed invoice is likely to extract cleanly and need only a glance; a handwritten chit is far more likely to need correction, and the system flags that difference rather than presenting both with equal, false certainty. Vendor name variants — the same supplier as "Sharma Traders" and "M/s Sharma" on different bills — can fragment one vendor's history if nothing reconciles the spelling.
What this capability changes for a CA reviewing the books is the starting point. Instead of opening a spreadsheet full of manually typed figures with no way to check them against anything, they see confirmed entries that already carry a link to the bill they came from. Extraction speeds up the owner's side of the work; it does not remove the CA's role in deciding what any of those figures actually mean for the return being prepared, now or later.
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 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 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
Confirm each one before it enters the books rather than assuming it's correct. Khata flags anything the model is unsure about — a smudged total or an unfamiliar vendor name — for a closer look, but even a confident-looking read is a draft until you tap to confirm it, precisely so an OCR misread never becomes a silent, uncorrected error sitting in your ledger.
A handwritten or heavily creased receipt is exactly the kind of source where OCR is more likely to misread a figure, which is why extraction never auto-posts anything unconfirmed. You see the extracted fields next to the original image, so a misread total or date is easy to catch and correct before it enters the books, rather than only after.
OCR reads exactly what's printed or written on each bill, and the same vendor can appear as "Sharma Traders" on one invoice and "M/s Sharma" on another if the supplier itself isn't consistent about it. Reconciling these variants under one vendor record keeps that supplier's full expense history in one place rather than split across near-identical entries that look separate but genuinely aren't.
It reads what's printed on the bill — the tax amount the supplier already charged — rather than calculating or deciding a GST figure independently on its own judgement. If the supplier's invoice itself is wrong or unclear, that's a question for your CA to resolve directly with the supplier, not something extraction is built to correct, guess at, or override silently on its own.
The rest of your stack
No rip-and-replace — extract line items from documents works alongside the systems already running your business.
Coming soon