Mismatches surface before, not after
A gap between the books and supplier filings shows up as soon as 2A/2B data is imported, giving the CA the chance to chase a supplier before a claim is made at all.
Available now
In build
The whole team
Nineteen specialists, each with a defined job and an honest status label.
See all nineteenThe owner (and their CA) can see which purchase invoices are actually reflected in supplier filings before claiming input tax credit, avoiding a later mismatch notice.
Works with
What it does
Khata imports the downloaded GSTR-2A/2B data the CA or owner pulls from the GST portal and automatically compares it line-by-line against Khata's own recorded purchase invoices. Mismatches — invoices in the books but not in 2A/2B, or vice versa — are listed clearly so the CA can chase the supplier or hold the credit.
A travel agency claims input tax credit on hotel and transport bills from several vendors for a client's tour, only to get a mismatch notice months later because two suppliers hadn't reported the invoices in their own filings yet. By the time the notice arrives, chasing the supplier is a slower, more awkward conversation than it would have been at the time of the original bill.
GSTR-2A/2B purchase matching compares 2A/2B data the CA has downloaded from the GST portal against Khata's own recorded invoices, line by line, listing mismatches clearly — an invoice in the books but not in 2A/2B, or the reverse. Khata never connects to the GST Network to pull this data automatically, and never decides which ITC to claim; it shows exactly where books and supplier filings disagree, so the CA can act with the full picture in front of them.
Khata runs this directly on the platforms your customers already use — no separate app for them to install.
How it works
The CA or owner downloads GSTR-2A or 2B data directly from the GST portal in its native format, and imports that file into Khata — by design, there is no automatic pull from GSTN itself, ever.
Khata compares the imported 2A/2B lines against its own recorded purchase invoices, accounting for minor formatting differences in invoice numbers that would otherwise cause a genuinely real match to be missed entirely by a stricter comparison.
Any invoice that's in the books but absent from 2A/2B, or present in 2A/2B but missing from the books, is listed as a mismatch the CA can act on, rather than buried inside a long undifferentiated comparison.
Armed with the mismatch list, the CA decides whether to chase a supplier for a missing filing or hold back an ITC claim until the supplier's return catches up — a determination Khata surfaces but never makes.
Why it matters
A gap between the books and supplier filings shows up as soon as 2A/2B data is imported, giving the CA the chance to chase a supplier before a claim is made at all.
Line-by-line comparison against imported 2A/2B data replaces a CA or owner cross-checking dozens of purchase invoices against a government download entirely by eye, slowly and manually.
Fuzzy matching accounts for invoice-number formatting differences between the books and 2A/2B, so a genuine match isn't wrongly flagged as missing purely because of formatting quirks.
The detail
This capability is deliberately built around a manual import, not a live connection, and that choice is itself part of the boundary. Khata does not connect to the GST Network to pull 2A/2B automatically — the CA or owner retrieves that data from the government portal themselves and imports the file into Khata for comparison. This keeps retrieval firmly on the CA's own credentials and the government's systems, and Khata's role starts only once that data already exists locally.
The comparison itself carries two real failure modes worth understanding clearly. A false negative — a genuine match the logic fails to recognise, usually from an invoice-number formatting difference — can wrongly suggest ITC is at risk on a fine purchase, sending a CA chasing a supplier unnecessarily. And because 2A/2B is downloaded at a point in time, the data can go stale the moment a supplier amends their own return afterward; a mismatch flagged today might resolve itself next week if the CA doesn't re-import an updated download from the portal.
What this capability never does is decide which ITC to claim, at any point. It shows exactly where the books and the supplier's own filing disagree, invoice by invoice, and stops there — holding a credit back, chasing a supplier for a correction, or proceeding with a claim despite a mismatch are all professional judgement calls that depend on facts beyond what a line-by-line comparison can capture, including confidence in the supplier relationship — a mismatch report lets the CA hold back only the claims still genuinely unverified.
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 moreExpenses land in the right category (rent, salaries, supplies, utilities) automatically instead of the owner deciding from scratch every time.
Learn moreQuestions
No — this is by design. The CA or owner downloads 2A/2B data directly from the GST portal using their own credentials, and then imports that same file into Khata afterward for comparison. Khata never connects to GSTN itself to retrieve this data, which keeps that entire retrieval step firmly on the government's own systems and the CA's personal login.
A mismatch flag means the invoice in your books isn't currently reflected in the supplier's reported 2A/2B data — it doesn't decide the claim for you at all. Your CA reviews the mismatch and decides whether to chase the supplier for a correction, hold the credit, or proceed based entirely on their own professional judgement of the specific situation at hand.
Fuzzy matching accounts for common invoice-number formatting differences, but it can occasionally still miss a genuine match if the discrepancy is unusual enough to slip past it. It's also worth checking whether the 2A/2B data was downloaded before or after the supplier's most recent filing, since that timing gap alone can fully explain the mismatch entirely on its own, with nothing else wrong.
Since suppliers can amend their own GST filings after the fact, a mismatch flagged from an older download can resolve itself once a fresher one is imported and compared. Re-importing shortly before a return is due, rather than relying on a download from weeks earlier, keeps the mismatch report reflecting what's actually current, rather than what a supplier's filing looked like weeks earlier.
The rest of your stack
No rip-and-replace — match purchases against supplier-reported gst data works alongside the systems already running your business.
Coming soon