For most accountants and CA firms, the hardest part of monthly GST work is not the return itself — it is getting complete, correct data out of every client on time. GST client management is the set of habits, checklists, and tools that turn a chaotic "chase everyone before the due date" cycle into a repeatable process. Done well, it is what separates a firm that files calmly every month from one that is always one WhatsApp reminder away from a missed deadline.
This article covers onboarding, data collection SLAs, status tracking, and the audit trail that keeps a growing client book manageable.
Client management is not the same as a generic CRM
A sales CRM tracks deals and follow-ups. GST client management has a different rhythm: it is recurring, monthly or quarterly, tied to hard statutory deadlines, and involves collecting sensitive financial data rather than just contact details. The things worth tracking per client are less "last contacted date" and more "has this client sent this month's sales data, and has it been reviewed."
Getting onboarding right the first time
A rushed onboarding is the single biggest source of recurring back-and-forth later. Before the first return is filed for a new client, collect and confirm:
| Item | Why it matters |
|---|---|
| GSTIN(s) and registration certificates | Confirms legal name, address, and registration type (regular/composition) |
| Sales channels (marketplaces, own website, offline) | Determines what data sources need to be collected each period |
| Bank account details and statement access | Needed for reconciliation and, eventually, books |
| Prior period filing status | Flags any pending returns, notices, or mismatches inherited from before onboarding |
| Authorised contact for approvals | Avoids delays waiting on someone who cannot actually sign off |
Document this once, clearly, and the monthly cycle becomes far more predictable.
Setting data collection SLAs that actually hold
Most firms lose time not because clients refuse to send data, but because there is no agreed deadline for when it should arrive relative to the filing due date. A workable SLA structure looks like this:
- Data due from client: a fixed number of days after month-end, before the GSTR-1 due date, giving the firm a buffer.
- First reminder: sent automatically a few days before the client's data deadline.
- Escalation reminder: sent if data has not arrived by the deadline, ideally to both the day-to-day contact and the authorised approver.
- Internal cutoff: a firm-side deadline after which a return is prepared with whatever data exists and flagged for follow-up, rather than risking a missed filing altogether.
WhatsApp tends to work better than email for these reminders in practice, simply because it gets read faster. A workflow that can send reminders and receive documents over WhatsApp messaging removes a step that otherwise depends on someone remembering to check their inbox.
Tracking status across a growing client book
Once a firm handles more than a handful of clients, "I think everyone is done" stops being a reliable answer. A simple status board per client, per period, tends to work better than trying to remember it:
| Status | Meaning |
|---|---|
| Awaiting data | Client has not yet shared sales/purchase information for the period |
| Data received, in preparation | Return is being prepared from received data |
| Ready for client review | Draft return summary sent back to the client for confirmation |
| Approved, ready to file | Client has signed off; return can be filed |
| Filed | Return submitted on the GST portal |
This kind of board, even a basic one, is what lets a firm answer "which clients are at risk of missing the deadline this week" in seconds rather than by scrolling through chats.
Why an audit trail matters more than it seems
When a client questions a figure months later, or a departmental query comes in, being able to show exactly who prepared a return, who approved it, and when it was filed protects the firm as much as the client. Role-based access — so that a junior preparer can enter data but only a senior can approve and file — also reduces the risk of an error going out the door unnoticed.
An audit trail also matters internally, separate from any client dispute. Firms that grow past a handful of staff eventually need to answer questions like which preparer has the highest rate of returns sent back for correction, or which client relationships are consuming disproportionate staff time relative to the fees billed. Neither question is answerable without a record of who touched what and when, tied to each client and each filing period rather than scattered across individual staff members' memory or personal notes.
Handling the client that never sends data on time
Every firm has at least one client who is chronically late, regardless of how many reminders go out. Rather than treating this as a communication problem to keep solving manually every month, it is worth building a fixed escalation path for it: a defined number of reminders, a defined point at which the authorised approver (not just the day-to-day contact) is looped in, and a defined point at which the firm files based on available data and flags the return for later correction rather than risking an outright miss. Having this path agreed with the client in advance, ideally in the engagement letter, removes the awkwardness of improvising an escalation in the moment.
Where OneBooks GST supports this workflow
OneBooks GST is built for firms managing several clients and GSTINs at once. Its CRM and support ticketing keep client communication and document requests in one place, WhatsApp messaging handles reminders and data collection, and role-based permissions let a firm control who can prepare versus approve a filing. Once data arrives — whether from marketplace exports or direct upload via Admin > Upload Files — GSTR-1 automation handles the preparation, and Admin > Detailed Reports gives a per-client, per-period view of what is done and what is pending. If your client book spans several GSTINs per client, pair this with a clear approach to managing multiple GSTINs so registration-level data never gets mixed up. For a broader look at automating the collection-to-filing pipeline itself, see our guide on GST automation for CA firms.
Firms evaluating a platform for this should check the OneBooks GST plans for multi-client, multi-user support before committing.
Frequently asked questions
What is the first thing a firm should fix to improve client management?
Onboarding. A consistent checklist collected once at the start of the relationship removes most of the repeated back-and-forth that shows up every filing cycle afterward.
How early should client data be requested before the filing due date?
Enough buffer to prepare, get the client's review, and still file before the statutory deadline — many firms aim for several days of internal buffer, but the right number depends on your client volume and complexity. Always verify current due dates on www.gst.gov.in before finalising your internal calendar.
Should every team member be able to file a client's return?
No. Role-based permissions that separate data entry, review, and final filing/approval reduce errors and create accountability if something needs to be traced back later.
Is WhatsApp a reliable channel for collecting client data?
It works well for reminders and quick document sharing because response rates tend to be higher than email, but sensitive financial files should still flow into a proper system of record rather than staying scattered across chat threads.
How can a firm track which clients are at risk of missing a deadline?
A simple status board per client and period — awaiting data, in preparation, ready for review, approved, filed — makes it easy to see at a glance who is behind, rather than relying on memory.
