Introduction
GST, TDS, PF, ESI and ROC across multiple registrations, and why the spreadsheet gets rebuilt every quarter.
Why the spreadsheet always comes back
Every growing company builds a compliance calendar. Every one of them abandons it within a few quarters, because maintaining it is work that produces no visible output until the month you miss something.
The underlying issue is that due dates are known but filing status is not. Whoever maintains the calendar has to ask someone whether a return went in, and that asking is the part that stops happening.
Status has to be automatic
A calendar becomes useful the moment filing status updates itself. If the system prepared the return, it knows whether it has been filed, and the acknowledgement is attached to the period rather than sitting in someone email.
At that point the calendar stops being a to-do list somebody maintains and becomes a report.
The multi-registration multiplier
A business with four tax registrations has four times the filings and, with most vendors, four times the software charge. The charge is a pricing decision rather than a technical necessity — the work of preparing a second return from the same system is close to zero.
It is worth asking any vendor directly what a second registration costs, before rather than after.
Where an agent fits
Preparation is assembly: pull the data, apply the rules, reconcile what can be reconciled, flag what cannot. That is mechanical and suits automation well.
What is not mechanical is judgement on the exceptions — the classification question, the disputed input credit, the position that needs a view taken. That should stay with your accountant, and it should be all your accountant has to do.
Giving your CA the right access
Most compliance friction is a communication problem: the accountant does not have live access, so everything moves by email and WhatsApp forward. Read access to the actual books, scoped appropriately, removes most of it.
In summary
None of this requires a transformation programme. It requires deciding where each piece of data is created, making sure it is only created once, and letting everything downstream read from that record instead of keeping its own copy.
Aditya Kulkarni, Head of Product at easyto.work.
