One CA login. Many client workspaces.
Your clients invite you in. You get one cockpit ranked by which client needs you this morning, a calendar that merges every client's GST, TDS and ITR dates, bulk reminders you review once, and a one-tap ZIP at filing time.
You already know the pain.
Chasing clients over WhatsApp is not filing.
Every quarter you spend half your billable time hunting for invoices, payment proofs and updated ledgers. Some clients send a Tally backup, some send a screenshot, some go silent until the deadline.
One login per client is one login too many.
You already juggle a dozen client Tally files. Signing into a dozen different accounting portals doesn't help.
Thirty clients, one Monday morning.
Somebody's GSTR-3B is due Saturday, somebody else hasn't deposited a TDS challan, and a third has ₹6 lakh sitting 90 days overdue. Working out which of those matters most means opening thirty files.
Marketplace TCS is a black box.
Your seller clients get TCS collected on their behalf but rarely check whether Amazon's GSTR-8 matches their own GSTR-1. You catch the mismatch after the notice arrives.
A notice arrives and the clock starts.
The client forwards a PDF, you reconstruct the year from their books, and the reply gets typed under time pressure — with figures re-keyed from a screen into a letter that goes to a tax officer.
What Finocket does for you.
Multi-client cockpit, ranked worst-first
Every client workspace as a card carrying a 0–100 health score, folded from the same overdue, GST-deadline, low-stock and exception signals that client sees on their own home screen — healthy from 80 up, critical below 50. The grid is worked out fresh each time you open it, so there is no stale nightly score, and a client whose workspace can't be read is skipped rather than blanking the page. One tap switches you into their books.
One compliance calendar across every client
Each client's GST returns, TDS challan-deposit and 26Q dates and ITR deadlines merged into a single agenda with per-client chips, plus a file-early hint when a due date lands on a weekend or beside a festival. Export the whole agenda as an .ics for your own calendar. A client with no GST profile is shown as exactly that, never given an invented deadline — and this is a calendar, not a filing queue: nothing is submitted from it.
Bulk reminders across clients, reviewed once
One worst-first plan across up to 25 client workspaces — 20 invoices per client, 50 sends in all, with a 24-hour guard so nobody gets chased twice in a day. Consent and suppression are re-checked for each recipient at the moment of sending, and every executed client gets one signed row in their own activity log, so your bulk action is never invisible to the business owner. Running it needs the write-level invite; a read-only accountant invite can open the page and read the plan, and the screen says so.
Filing-pack prep, N clients at a time
The same screen builds a per-client pack — GSTR-1 section CSVs plus a GSTR-1-vs-3B summary — and zips it. It is preparation for the portal, not a filing: Finocket does not submit returns to the GSTN, and it never pretends to.
GST notice register & reply drafting
Log the notice exactly as your client received it — every field is declared by a human, because a notice fact the app invented would be quoted back at a tax authority. Then assemble the reply from a frozen pack of that client's own rows: a figure in the letter can only be a reference into that pack, so an uncited number is not even expressible. Approval binds the document to a hash of itself and freezes it, and the reply cannot be marked complete while a rupee is unexplained. Finocket does not submit it, and where the statutory window isn't verified it leaves the due date blank rather than guessing one.
Monthly client statements that send themselves
The month-end statement is built and emailed on a schedule, at most once per period — the claim to send is a database update, so a cron that fires twice can't email twice — and every outcome is logged, including the honest 'no email provider configured'. Delivery needs a configured email provider.
Read-only, enforced at the database
Your invite carries the read-only role, and Postgres row-level security is what enforces it: every insert, update and delete on a client's books is refused at the database, not merely hidden in the app. You can read, export and reconcile — you cannot change a figure.
Hand-to-CA ZIP
One archive with every invoice PDF, statement of account, Day Book, Outstanding, GSTR-1 CSV, GSTR-3B PDF and a plain-English manifest.
GSTR-8 reconciliation
Diff every seller client's own invoices against each marketplace's settlement view. Catch mismatches before the tax officer does.
Tally vocabulary respected
Toggle 'accountant mode' and Voucher / Ledger / Party / Narration replace Payment / Client / Client / Description throughout the app.
On your phone
Progressive Web App — install on your iPhone or Android, and entries you add with no signal queue and sync when you are back. Reminders you run from the bulk screen go out by email through the consent chokepoint; WhatsApp is a separate channel that needs a provider connected on that client's workspace.
The bar we hold ourselves to
I stopped asking my clients for Tally backups. They already keep Finocket up to date; I just log in.
What we set out to fix for every CA who spends Sundays chasing client files