Filing season, without the spreadsheet

A compliance practice’s work looks different from a typical project, but it isn’t, really. GST returns, TDS filings, ROC compliance, advance tax — the same set of obligations repeats for every client, every period. Nothing about any single filing is hard. The difficulty is scale: dozens of clients, each with their own due dates, staggered across the month, all of it depending on one person remembering to check.

That’s usually where it lives — a spreadsheet with a tab per client, or a single sheet with dozens of columns, understood fully by exactly one person in the firm. When that person is on leave, or a junior handles a filing without knowing the sheet needs updating, the practice is one missed cell away from a missed date. The risk was never technical competence. It was tracking.

A project per client, or per cycle

In Kaarya, each client becomes a project, or each recurring filing cycle becomes one if that fits the practice’s rhythm better — a GST-return project running month to month, a ROC-compliance project running through the year. Recurring tasks handle the part that used to mean re-typing the same row every period: a task that’s due monthly or quarterly is set up once and reappears on schedule, rather than being manually re-created.

Due dates carry the weight statutory deadlines need. A task that slips past its due date surfaces as overdue — visible in the project, not buried in a sheet that only gets opened when someone remembers to.

Statutory dates on a timeline

Filing due dates aren’t just line items; some of them are the moments the whole engagement turns on. Kaarya’s milestones let a practice mark those explicitly — the GST filing deadline, the ROC due date — as points on a timeline, distinct from the everyday task list. A partner glancing at a client’s project sees not just what’s overdue today, but where the next real deadline sits.

The digest replaces the phone calls

The daily WhatsApp digest is where this stops being “another tool to check.” A partner doesn’t log into anything — the digest lands in WhatsApp each day with what’s due. For a practice used to phone calls and WhatsApp messages to chase status, this flips the direction: the update comes to the partner instead of the partner having to go get it.

It works the other way too. Junior staff can close out items by replying directly from WhatsApp — a filing gets marked done from the same place the reminder arrived, without opening a dashboard mid-filing-season.

Sign-off before anything goes out

Compliance work usually has a point where a partner needs to review before a return is actually filed. Kaarya’s approvals cover exactly that: a step for “partner sign-off before filing” that has to clear before the task can be considered done. It’s a checkpoint built into the task itself, not a separate email asking someone to confirm.

And because every change is logged, the activity trail gives the practice something a spreadsheet never could: a record of who changed a due date, when, and what happened before and after. If a client asks why a deadline moved, or a partner needs to reconstruct a filing’s history, the trail is there — not a defensible compliance certification, but a defensible internal record of what the team actually did.

Seeing across the whole client list

Filing season doesn’t hit one client at a time — it hits all of them in the same window. Portfolio and workload views let a partner step back from any single client and look across the practice: which projects are piling up, which staff member is carrying more open tasks than they should be in a peak week. That’s the view a spreadsheet with one tab per client can’t give you, because nothing in a spreadsheet tells you a person is overloaded until they say so.

Getting the existing sheet in

None of this requires starting from a blank slate. CSV import brings the existing spreadsheet across — client names, due dates, whatever structure the sheet already has — so the switch is a migration, not a rebuild.

What this is not

Kaarya tracks the work. It does not file GST returns, does not calculate TDS, does not generate ROC forms, and does not know compliance law. It has no built-in knowledge of statutory rules or due-date calendars — every due date and milestone is one the practice enters itself. It is not a replacement for a CA’s judgment, and it is not a compliance or filing product. It’s a place for a practice to keep recurring deadlines, statuses, and approvals in one system that a WhatsApp message can update — nothing more, and for a business built on dates that can’t slip, nothing less.