The most expensive document in a CA firm is not a return you filed late. It is a notice you never opened. A Section 143(1) intimation proposing an adjustment, a defective-return notice under 139(9), a GST scrutiny query, a TDS short-deduction default — each arrives quietly in a portal, each carries a response window, and each turns into something worse if that window closes unanswered. The firm that files hundreds of returns beautifully can still be undone by one intimation that sat unread until it hardened into a demand with interest attached.

We build practice software, so we spend our time in the part of the job that happens after 'return filed'. This is an honest look at why notices are a firm-level problem, not a per-client afterthought, and how to make sure not one of them slips.

Why notices are a firm problem, not a per-return one

When you file a return, you are looking at one client. When notices come back, they come back across your whole book — from different tax heads, on different portals, with different clocks, all landing in different inboxes and logins. No single client is generating enough of them to feel like a system. The firm, in aggregate, is drowning in them. And because each one lives on the authority's portal rather than in your workflow, the default state of a notice is 'invisible until someone happens to log in and look'. That is not a process. That is luck.

Notices arrive across your whole book, on different portals, on different clocks — and none of them come to you.
Notices arrive across your whole book, on different portals, on different clocks — and none of them come to you.

Different notices, different clocks

Part of what makes this hard is that no two notices behave the same way. An intimation under 143(1) may simply confirm your figures — or it may propose an adjustment you typically have around thirty days to contest before it is made final. A 139(9) defective-return notice gives you a window to fix the defect before the return is treated as invalid. A 143(2) opens scrutiny. On the GST side, an ASMT-10 wants an explanation for a discrepancy, with a reply expected within the time stated. TDS defaults quietly accrue interest until someone corrects the statement. Treat them all as 'a notice' and you will apply the wrong urgency to the wrong one. Each needs its own deadline, owner and response, tracked to closure.

What quietly gets missed

  • The intimation whose proposed adjustment window lapsed, so the adjustment simply became the assessment.
  • The defective-return notice fixed a week after the return was already treated as invalid.
  • A GST scrutiny query answered late, converting a routine explanation into a formal proceeding.
  • A TDS default nobody actioned, accruing interest month after month.
  • A notice sent to a client who forwarded it to the wrong person at the firm, where it died in an inbox.
  • The response that was drafted, discussed, and then never actually filed — because no one owned the last step.

The cost of a closed window

Almost every one of these starts small and cheap to fix, and ends large and expensive to argue. A proposed adjustment you could have knocked out with one reconciliation becomes a demand you now have to contest through appeal. An accruing interest figure that was a rounding error in month one is a real number by month six. The damage is rarely the notice itself. It is the silence after it. And silence is precisely what an unmanaged, portal-scattered notice pile produces by default.

Almost every notice starts small and cheap to fix, and ends large and expensive to argue. The damage is the silence after it.

There is a quieter cost too: the client who first learns of a notice from a demand rather than from you. A firm that tracks notices is not only protecting itself from a lapse — it is protecting the relationship. When you can tell a client 'we saw the intimation the day it landed, here is our reply, here is where it stands', you are the advisor who is ahead of their tax life instead of the one explaining, after the fact, why a routine query hardened into a bill. Trust is built or lost in exactly those moments, and a tracked notice is how you stay on the right side of it.

Filing tools file. They don't chase the aftermath.

Let us be fair to the software you already use. Genius, CompuTax, Winman, Suvit and TaxOne are good at computing and filing — that is their job and they do it well. But filing is the beginning of a client's tax life, not the end of it. The notice that comes back three months later is outside the filing tool's world; it has no view of your whole book's open notices, no deadline that gets loud, no owner assigned, no record that a response was actually filed and the matter closed. That is not a flaw in the filing engine. It is simply a different job — the job of running the practice around the returns.

Filing is where a client's tax year begins. The notice that comes back later is a different job entirely.

How BizRevolt tracks notices to a response

BizRevolt gives every notice a home: logged against the client, classified by type, given its response deadline, assigned to a person, and tracked until a reply is actually filed and the matter is closed — not just discussed. The deadline board that treats a missed statutory date as near-malpractice covers notices too, so an approaching window gets loud before it lapses, not after. It sits beside your filing engine, not on top of it: keep computing and filing where you do it well, and let the practice layer make sure nothing that comes back afterward dies in a portal. Pricing is flat and legible — ₹1,499 a month for a Solo practitioner, ₹4,999 for a Firm — not per notice, not per client.

We are building this with practising CAs, in the open, and the sharpest feedback we get is someone showing us the exact notice that got away and what it cost. If you have one of those, we want to hear about it. Message us, or call and talk to a human on +91 91 0657 4865 — we would rather learn from your firm than lecture you about ours.