Back to modules

Run the whole practice on one system.

Every client, every domain, every deadline. NITIVAR gives the firm Practice Management for the operating layer and GST, TDS, labour law, and secretarial modules for the filing work — one calendar across all of it, one login for the whole team.

One calendar, every clientThe full financial year generates from service templates — GST, TDS, labour law, and ROC deadlines by client and domain.
The filing work in the same systemReturns, challans, and forms run in dedicated modules — not in a tracker pointing at five portals and a shared drive.
The firm's registers built inDSC custody and expiry, UDIN records with evidence, and encrypted portal credentials with reveal history.

How a firm actually runs on NITIVAR

The year starts with engagements: each client signs up for services, and the service templates generate the work — tasks with stages, due dates from the statutory obligation catalog, document request lists. The firm-wide calendar assembles itself, and every partner sees the same one.

The work runs in the modules built for it: the GST module files the GSTINs, the TDS module runs the TANs, Secretarial tracks the entities to SRN, and labour law obligations carry their evidence. Status rolls up to the Practice statutory summary — one control page across every client and domain.

Around the work, the firm's machinery runs itself: notices carry reply deadlines into the daily queues, DSC and UDIN registers stay current as they are used, credentials sit encrypted with reveal history, and time logged on engagements becomes WIP, fee notes, and invoices in Accounting.

A day in the firm

A day in the firm

What each seat sees — from the article clerk to the managing partner.

The team opens on queues

Every staff member starts on the Today view: due this week, overdue, waiting on client. Tasks carry their stage, their documents, and their client context — the morning triage meeting becomes a screen everyone already read.

  • Due, overdue, and waiting-on-client queues
  • Tasks with stages and review states
  • Documents attached where the work happens

Reviewers gate the filings

Work moves to review before it moves to a portal — GST returns, TDS returns, ROC forms, resolutions, and certifications all queue for a checker. Errors get caught in review, where they cost minutes, not in resubmission, where they cost credibility.

  • Maker-checker across every domain
  • Review queues per module
  • Solo mode where a firm of one needs speed

Partners read one control page

The statutory summary shows GST, TDS, and labour law status across all clients at once, and analytics show response times, notice exposure, workload, and billing signals. 'Are we on top of everything?' takes a glance — and the follow-up question has a drill-down.

  • Cross-client statutory status, live
  • Notice and governance exposure visible
  • Workload and billing signals per team

Billing happens by construction

Time logs against the engagement while the work happens, WIP accumulates, fee notes raise, and Accounting invoices and collects. Unbilled work is a weekly report someone acts on — not a year-end archaeology project nobody finishes.

  • Time to WIP to fee note to invoice
  • Unbilled work as a standing report
  • The firm's own books in the same suite
What the firm stops worrying about

What the firm stops worrying about

The risks that live in spreadsheets and inboxes today, moved into registers.

Deadlines nobody re-types

The compliance year generates from the obligation catalog per client — nobody builds the deadline sheet in April, and nobody discovers in November that one client's new GSTIN never made it in.

  • Calendar generated, not maintained
  • New engagements bring their own deadlines
  • Gaps flagged instead of discovered

Credentials that leave a trail

Client portal credentials sit encrypted, revealed only with a logged reveal history — who, what, when. The password spreadsheet, the firm's single most dangerous file, gets deleted.

  • Encrypted vault, not a shared sheet
  • Reveal history per credential
  • Access scoped by role

DSCs and UDINs on register

Digital signatures carry custody, expiry, and usage records; UDINs run from draft to generated with evidence attached. The two registers an ICAI or ICSI review asks about first are current by default, because using them updates them.

  • DSC custody and expiry tracked
  • UDIN records with evidence
  • Current by use, not by cleanup

Notices that find you first

Department notices and hearings register with reply deadlines and become tracked work in the queues. The show-cause notice surfaces as a countdown on a dashboard — not as a forwarded PDF two days before the date.

  • Notices registered with deadlines
  • Hearings tracked as work
  • Countdowns in the daily queues

Firms that fit this stack

From a practitioner with a hundred clients to a multi-partner, multi-domain firm.

Compliance-led CA firms

GST, TDS, and labour law work across many clients — generated from templates, filed in the modules, rolled up on one control page.

CS firms and company secretaries

Client entities on computed ROC calendars, filings tracked to SRN, certification work through review, and UDIN records that maintain themselves.

Multi-partner firms

Review discipline on every filing, workload and billing visibility per team, and a firm memory that lives in the activity log instead of in inboxes.

Solo practitioners scaling up

Start in solo mode with the same system — and switch on review workflows, roles, and teams as the first hires arrive.

What changes when the firm moves

The four spreadsheets die, and the partner stops being the system.

The job register dies

Engagements generate tasks with stages — the Excel register that only one person understood is gone.

The deadline sheet dies

The obligation catalog drives a generated calendar — no April rebuild, no missed additions.

The password file dies

Encrypted credentials with reveal history replace the most dangerous spreadsheet in the office.

The status meeting shrinks

Queues, review states, and the statutory summary answer what the Monday meeting used to ask.

The billing leak closes

Time logs where the work happens — WIP and unbilled reports catch what memory-based billing lost.

The knowledge stays

Client history, documents, and communication live on the record — a resignation stops being a data loss event.

CA & CS firm FAQs

What managing partners ask before moving the firm.

Can the whole team work in it with different permissions?

Yes. Role-based permissions scope every module — article clerks see their tasks, managers see their teams' work and reviews, and partners see everything including analytics, billing, and the registers. Confidential areas like credentials stay locked to the roles you choose.

Does the filing work happen inside the system or do we still use portals?

The preparation, review, tracking, and evidence live in NITIVAR — the GST, TDS, and Secretarial modules run the work to filed status with acknowledgements and SRNs recorded. Government portals remain the filing endpoint; NITIVAR is the system of record around them.

How do clients send us documents?

Document request lists go out per engagement and track what was asked, what arrived, and what is pending — and the inbox keeps client communication and follow-ups triaged and assigned instead of scattered across personal email.

Can we bill from it?

Yes. Time logs against engagements, WIP accumulates, and fee notes raise with a handoff to the Accounting module for invoicing and collections — the firm's own books run in the same suite.

We are two partners and six staff. Is this too heavy?

No — the modules are priced and adopted separately, and solo mode exists precisely for small setups. Most firms start with Practice Management plus their heaviest domain module and switch on the rest as the client base grows.

Bring three clients. Watch the year generate.

In a 30-minute walkthrough we'll set up three of your actual clients, generate their compliance calendars from templates, and show the statutory summary your partners would read every morning.