Sign in to access your secure office database
Staff accounts are provisioned via the Firebase Authentication console.
| Company | Work Type | Staff | Due Date | Priority | Status | Billing | Remarks | Actions |
|---|
Computed from the client list already loaded — no extra cost to check this. Email greetings go out automatically to everyone shown here with an email on file. WhatsApp wishes go out automatically too, but only to Priority clients — check the column below before sending anything by hand.
Loading…
Overdue and upcoming work for whoever is currently selected in the Staff scope above — switch to All staff for the full picture. Reminders themselves go out automatically each morning; this is only to check the contact details are actually reachable before that happens.
Loading…
One record per client. Used to fill in details when adding a task, to decide which recurring work each client needs, and to tell apart clients with similar names.
Loading…
Requests clients have submitted through the Portal. These are not tasks yet — review each one and convert it into a proper task with a due date and assignee.
Loading…
Notices picked up automatically from the office inbox. This is an alert list, not a task list — open the notice on the department portal, deal with it there, then update the status here so it stops showing as pending.
Loading…
KYC documents that are expiring, documents clients sent from the Portal, and changes clients told us about. A change of place of business, partners/directors or signatory needs GST REG-14 within 15 days of the change (CGST Rule 19).
Net worth, turnover, drawing power, RERA Form 3 / Form 5 and others. Staff prepare and send for signing; only the admin signs; a signed certificate is issued to the client's Portal. A signed certificate is never edited — it is voided and a corrected copy made.
Partnership and LLP deeds, declarations, and office HR letters. They are signed by the parties, not by Chandan sir — no UDIN. Fill, check the warnings, preview, then make it final to get a Word file (to print on stamp paper) and a PDF. Client documents are also saved in the client's Drive folder "Deeds & Agreements".
Confirmation letters the client signs for us — books, cash, bank, stock, debtors, creditors, sales, purchases, loans, MSME, appointment, management representation. Sent to the client's Portal; only a signatory set by the admin can sign there, or a signed scan is uploaded and checked here.
GST refunds stage by stage (RFD-01 → RFD-05) with the last date to file, when the department must act, and indicative interest; income-tax refunds as simple records. Dates marked "rule NOT verified" come from a rule the admin has not yet checked.
Client e-mail addresses that Google refused (wrong format) or that bounced back ("address not found"). Open the client, correct the e-mail, save — and when asked, update the open tasks too — then press Mark corrected. If the address goes wrong again later, it comes back here.
Paragraphs we reuse in notice replies, our past replies and how they ended, and case law. Case law can be copied into a reply only after the admin has read the judgment and verified it; the verification must be renewed every 12 months.
Retainer clients only. Load the Tax Power "GSTR-3B vs GSTR-1" file and the GSTR-2B Excel, type the Tally figures, then send each month to the client to confirm on the Portal. No reply in 7 days = deemed confirmed (reminder e-mail on day 5).
Every loan file we help a client with, stage by stage, with the next follow-up date so no bank, DSA or client follow-up is lost. Staff only — clients do not see this.
Download the card and share it from your phone or e-mail. Send it only to clients, or to someone who asked for it — sending it to people who did not ask can count as solicitation under the ICAI Code of Ethics.
Send a document to a client (it appears in their Client Portal under Documents), and download what clients sent through Send Us Something. Files are kept in the office Google Drive; nobody here needs access to it.
Invoices, ledgers and receipts are shared from Billing (admin and staff with Billing access), so their amounts reach the client's Pay Fees.
Every UDIN generated on the ICAI portal, read from ICAI's e-mails: which client, what document, and its purpose. ICAI's e-mail does not name the client — it is found from the PAN typed in the UDIN particulars. Where there is no PAN, or the PAN belongs to more than one client record, choose the client here (nothing is guessed). Tip: when generating a UDIN for a certificate, type the client's PAN in the particulars.
Invoices are still made in the Billing Software — it stays the only set of books. Here you mark finished work as billed, share invoices, ledgers and receipts with the client (they appear in the Portal under Pay Fees), check the payments clients tell us about, and keep each firm's UPI ID.
Work marked Done whose Billing Status is still Unbilled. Tick the tasks that go on ONE invoice (one client at a time), then enter the firm and the invoice number from the Billing Software.
Clients who tapped "I've paid" on the Portal, with their reference (UTR) and any proof they attached. Nothing here is confirmed money — check each one against the bank statement, then mark it. Record the receipt in the Billing Software as usual.
Loading…
Each firm that bills clients, the name clients see when they pay, and its UPI ID. The Portal shows a client only the firms on that client's own invoices and ledgers, plus the default firm for "pay any amount". Only the admin can change this — a wrong UPI ID sends a client's money to the wrong account. Every change is recorded below.
Monthly review points for each client. The client sees an observation under Our Observations in the Portal only after the admin publishes it, and can answer it there. Client suggestions from the Portal arrive here; they can be marked, not deleted by staff.
What clients see under Updates & Due Dates in the Client Portal. Staff can write and edit drafts; only the admin can publish. A published item shows clients the date you reviewed it and its source.
How many clients carry each tag. Tag one client in Clients → Edit, or many at once with a CSV (admin).
Blank line = new block · lines starting - = bullet list · a block starting ! = caution box · lines with | = table (first line = headings).
Ready-made prompts filled in from a task. Nothing is sent from this screen — copy the prompt, open Gemini yourself, and paste it there.
Who may open the Task Tracker, and which client each Client Portal login belongs to. Only an admin can change these.
Add the email address each staff member signs in with. It must match exactly. Everyone who uses the Tracker must be listed here before the new security rules are published — anyone missing will be locked out.
Loading…
Link a client's email address to their client record. A client who signs into the Portal sees nothing at all until you link them here — signing in with an email does not prove who someone is, so this step is deliberate and cannot be automatic.
Loading…
The Client Portal's security rules only let a client see tasks that carry their
clientId — no task has one yet. This checks every task against your Clients
list by GST/PAN, then by company name, and shows you the counts. Nothing is
written until you review the numbers and press Apply below. Safe to run more
than once — it only touches tasks that don't already have a clientId.
New and edited tasks get this automatically from now on; this is only for tasks that
already existed before today.
You marked this task as Done. Would you like to notify the client?
Are you sure you want to delete this task?
Creates recurring work from the client list. Nothing is created until you have seen the preview and pressed the button.
Upload the client spreadsheet. Nothing is saved until you have seen the preview and pressed Apply. Clients are matched on GSTIN where present, otherwise PAN — so re-importing updates existing records rather than creating duplicates.
Save the client first, then open this section.
For a company, firm or trust, the date of birth field above belongs to the entity's date of incorporation, not a person — so it is never used for birthday greetings. Add each partner or director here instead, and they will each be wished on their own birthday. For a proprietor or individual, this section isn't needed.
Upload an Excel (.xlsx) or CSV file to bulk import clients and tasks.
Only the account(s) below can delete tasks or restore a backup. Everyone else can add, edit, and update tasks normally.
To change who's an admin, edit ADMIN_EMAILS near the top of this file's code and redeploy — and update your Firestore Security Rules to match (see SETUP_GUIDE.md).
A full backup downloads every task as stored, except portal login passwords, which are deliberately left out (admin only), so it can restore your data later — unlike the CSV/PDF reports, which are for reading, not restoring.
Portal logins used to be stored on each task, so the same login was repeated many times. This copies them onto the matching client records, removing repeats. Nothing is deleted from the tasks, so the originals remain if anything looks wrong. Run it once.
Links each login to the staff name used on tasks. Once someone is listed here, opening the Tracker shows their own work straight away, and the edit history records their name rather than their email address.
This overwrites any existing task that shares an ID with the backup. Use this to undo an accidental mass-deletion or data problem — not for routine use.
Same idea, for client records (PAN, GSTIN, contact details) instead of tasks — reads a
CCA_Backup_Clients_...json file (from the automated nightly backup) and overwrites
any existing client that shares an ID with the backup.
Restoring a backup is an admin-only action.
| Work Type & Period | Due Date | Status | Billing |
|---|