The input tax credit you’re about to lose
ITC-at-Risk flags input tax credit you could forfeit: credit blocked because a vendor has no GSTIN, credit whose claim window is expiring under the 30-November rule, ineligible expenses, and your total exposure ranked by vendor — all computed offline from your purchases.
Most lost ITC isn’t fraud — it’s missed deadlines and missing GSTINs. This radar makes both impossible to ignore.
Deadline-aware
Credit whose claim window is closing under the 30-November rule is flagged before it lapses.
Blocked & ineligible
No-GSTIN vendors and ineligible expenses are separated out so you don’t over-claim.
Vendor exposure
Your ITC exposure is ranked by vendor so you chase the biggest gaps first.
What’s included
- ITC register (purchases + expenses)
- 30-Nov claim-window aging
- No-GSTIN blocked credit
- Ineligible-expense flags
- Vendor-wise exposure
- Runs fully offline
Frequently asked
What is the 30-November rule?
ITC for a financial year must generally be claimed by 30 November of the following year; LekhaPro ages your credit against that window and warns you in time.
Does it need the GST portal?
No — ITC-at-Risk is computed offline from your purchases and expenses. Cross-checking against 2B uses the reconciliation screen.
What exactly is included in ITC · At risk?
ITC register (purchases + expenses), 30-Nov claim-window aging, no-GSTIN blocked credit, ineligible-expense flags, vendor-wise exposure 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 itc · at risk handled differently here?
It rests on deadline-aware, blocked & ineligible and vendor exposure. 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 ITC · At risk work offline?
On the Desktop edition, yes — completely. ITC register (purchases + expenses) and 30-Nov claim-window aging 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 itc · at risk runs in the browser and needs a connection.
Where does ITC · At risk get its data from?
From your own posted books, not a separate register you maintain twice. deadline-aware 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.
Does ITC · At risk cost extra?
No. ITC · At risk is part of the accounting core rather than a paid add-on, so blocked & ineligible 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 ITC · At risk before committing?
Yes — 14 days, no card. Test itc · at risk 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 ITC · At risk generated by AI?
None of the figures. Everything deadline-aware 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.
Can I get my itc · at risk data out again?
Yes. On the Desktop edition everything ITC · At risk records sits in a local database on a disk you choose, with scheduled encrypted backups you control — stopping payment leaves you holding a readable file. On the Cloud edition your data is isolated to your business by row-level security and exportable from the reports it feeds.