GST Notice Risk Score: Catch the Patterns That Trigger a GST Audit Before You File

A GST notice rarely shows up because someone did something dishonest. Most scrutiny notices start with a pattern in the numbers: a month where turnover jumped or fell sharply against your own history, input tax credit that offsets almost all of what you owe for months in a row, or ITC you claimed that your supplier never actually reported in their own return. None of these require intent. They are simply the shapes GSTN's own risk-parameter systems are built to flag, and most small businesses only learn their filing pattern looked risky after a notice arrives.

A GST notice risk score checks your own filing data against the same kinds of triggers before you submit a return, so a shop can see "this month's turnover swing looks unusual" while there is still time to double-check the numbers, not three months later when a scrutiny letter lands.

Why ordinary filing mistakes turn into GST notices

GST scrutiny isn't random. The department runs automated checks against every return, and three patterns come up again and again in what tax practitioners describe as routine risk parameters:

• A turnover that doesn't match its own trend. A sharp spike invites the question of why last year's numbers didn't show the same growth. A sharp drop invites the question of where the missing turnover went.
• ITC that wipes out almost all of your output tax, month after month. Paying close to zero cash tax for several months running, because input credit keeps absorbing nearly all of the liability, is one of the most cited audit risk parameters in GST practice.
• Input credit your supplier never filed. Every rupee of ITC you claim should show up in your supplier's own GSTR-1, which then flows into your GSTR-2B. When it doesn't, that mismatch is a direct, automatically detectable flag, not a matter of opinion.

Each one of these is checkable from data a GST-registered business already files every month: GSTR-3B's own tables and the GSTR-2B reconciliation most shops already run to claim ITC correctly. The problem for most small businesses isn't that the data doesn't exist, it's that nobody is watching the trend across months until a notice forces the question.

How Astra Atlas computes the risk score

Astra Atlas runs three checks automatically, every period, using the GSTR-3B and GSTR-2B figures the app has already computed for your filing, with no separate data entry and no new report to fill in.

1. Turnover swing

The app compares this period's outward taxable turnover against your trailing three-month average. A swing of 45% or more in either direction gets flagged as medium risk, rising to high risk past 75%. Small shops with naturally low turnover don't get flagged on noise, the check only runs once turnover clears a minimum base so a slow month for a tiny business doesn't register as a false alarm.

2. Sustained high ITC utilization

If input tax credit has offset 92% or more of your gross GST liability for three consecutive months, the score flags it, with severity rising further past 97%. One high month is normal, plenty of genuine businesses have a month where a big purchase drives ITC up. Three months running is the pattern that draws attention, because it suggests a structural mismatch between what you're declaring as sales and what you're claiming as credit, not a one-off timing effect.

3. ITC not in your supplier's GSTR-2B

This reuses the reconciliation Astra Atlas already runs for GSTR-2B matching. If 15% or more of the ITC you claimed this period doesn't appear in your suppliers' filed 2B data, severity rises to high past 35%, and the alert states the exact rupee amount at risk, not just a percentage. This is the easiest of the three to act on directly: it tells you which suppliers to chase for a correction before you file, rather than after a notice asks you to explain the gap.

Every alert carries a specific, plain-language reason and a rupee or percentage figure, not a generic warning. "High risk" on its own tells a shop owner nothing useful. "₹18,400 of ITC claimed this period doesn't appear in your suppliers' filed GSTR-2B" tells them exactly what to check and roughly how much is at stake.

What this is not

The GST Notice Risk Score does not predict whether the department will actually send you a notice, and it is not a substitute for a CA's judgment on a specific filing. It checks your own numbers against publicly documented risk-parameter patterns and shows you where your filing looks unusual by its own history, same as a lender checks a loan applicant's income consistency before approving anything. Compliance still depends on your invoices, filings, and purchase records telling the same consistent story. A clean risk score does not mean a filing is error-free; a flagged one does not mean you did anything wrong. It means a specific number moved in a way worth a second look before you submit, not after.

Why this sits outside what a billing app normally does

Vyapar, myBillBook, and Tally generate GST bills and reports. None of their public comparison pages describe checking a filing for audit-risk patterns before submission, that work is left entirely to the business owner or their CA, done by memory rather than by a system watching the trend across months. Astra Atlas already computes the GSTR-3B and GSTR-2B figures these three checks run on, which is the same underlying data this app uses to power Loan Readiness scoring and the Money Leaks report. The pattern across all three features is the same: data a shop is already generating by billing through Atlas gets turned into something the owner can act on, instead of sitting unused in a filing nobody revisits until a problem forces the question.

What to check before every filing

• Compare this month's outward turnover against the last three months. A swing past roughly 45% either way is worth a second look before you file, even if the number is correct.
• If ITC has been offsetting nearly all of your output liability for three months running, check whether that reflects real, large purchases, or whether some input credit is being claimed on invoices that shouldn't qualify.
• Run your GSTR-2B reconciliation before filing, not after. Chase a supplier who hasn't filed their GSTR-1 while there's still time to get a corrected invoice, rather than explaining a mismatch to the department later.
• Keep a GSTIN on file and your invoice numbering clean. Both matter for Loan Readiness scoring too, see the Loan Readiness guide for how compliance data feeds into creditworthiness beyond GST itself.

If you are still deciding on GST billing software and want to know what a modern option should check for beyond basic invoicing, our GST billing software comparison covers what to look for. For the compliance basics before risk scoring becomes relevant at all, start with our GST registration guide.

A GST notice is expensive mainly because of how late it arrives, often months after the pattern that triggered it. Checking the same signals the department checks, every period, before you file, turns a surprise into a routine review. Astra Atlas computes this automatically once GSTR-3B and GSTR-2B data exist for your tenant, no extra setup, no separate report to run.