Catch GST errors before the department does
The GST Error Catcher scans your invoices for the mistakes that trigger notices — IGST charged where CGST+SGST applied (or vice-versa), wrong HSN/rate pairings, rate anomalies on the same product, missing HSN above the threshold, and duplicate invoices — all offline.
Place-of-supply errors are the #1 cause of GST notices; this finds them while you can still fix them.
Place-of-supply guard
Flags invoices where the wrong tax head was charged for the company-vs-party states.
HSN & rate anomalies
Same product billed at different rates, wrong HSN/rate pairs, missing HSN above the turnover threshold.
Duplicates
Duplicate invoice numbers and same party+amount+date repeats are surfaced.
What’s included
- Place-of-supply error flags
- HSN/rate mismatch detection
- Rate-anomaly detection
- Missing-HSN checks
- Duplicate-invoice detection
- Runs fully offline
Frequently asked
Why focus on place of supply?
Charging IGST on a local sale (or CGST+SGST on an inter-state one) is the single most common GST notice trigger — so it’s the first thing checked.
Does it change my invoices?
No — it only flags issues for you to review and correct.
What exactly is included in Intelligence · Errors?
place-of-supply error flags, HSN/rate mismatch detection, rate-anomaly detection, missing-HSN checks, duplicate-invoice detection and runs fully offline. Every item on that list is a working screen you can open in the trial rather than a capability described in the abstract.
How is intelligence · errors handled differently here?
It rests on place-of-supply guard, HSN & rate anomalies and duplicates. The distinction that matters is that these are structural rather than cosmetic — the behaviour is built into how records are posted, not layered on as a report you have to remember to run.
Does Intelligence · Errors work offline?
On the Desktop edition, yes — completely. place-of-supply error flags and HSN/rate mismatch detection run against a local database on your own machine, so the screens behave the same with the network unplugged as with it connected. AI and billing are the only two things that reach out. On the Cloud edition intelligence · errors runs in the browser and needs a connection.
Where does Intelligence · Errors get its data from?
From your own posted books, not a separate register you maintain twice. place-of-supply guard is built from the invoices, masters and rates already entered, so there is nothing to re-key before filing and nothing that can quietly disagree with the ledger it was drawn from.
How does Intelligence · Errors affect my GST?
It feeds it directly rather than sitting alongside it. CGST/SGST and IGST are split from HSN or SAC and place of supply as each document is raised, so whatever intelligence · errors produces is already correct when GSTR-1, 3B and 2B reconciliation are drawn off the same books. The return matches the accounts because it was never a separate exercise.
Does Intelligence · Errors cost extra?
No. Intelligence · Errors is part of the accounting core rather than a paid add-on, so HSN & rate anomalies is there on the entry tier exactly as it is on the highest one. What the tiers change is reach and depth — devices, multi-branch and multi-warehouse reporting, and whether the conversational AI copilots are switched on.
Can I try Intelligence · Errors before committing?
Yes — 14 days, no card. Test intelligence · errors against your own masters and your own transactions rather than sample data: the questions worth answering here are about your business's edge cases, and a demo dataset is built not to have any.
Is anything in Intelligence · Errors generated by AI?
None of the figures. Everything place-of-supply guard produces is computed by tested engines and would be identical with the model switched off — what AI contributes is the sentence around a number and the routing that brings the right one to your attention. Nothing it writes posts to your books without your approval.