Claimstack Tech • Updated November 2026
📝 Buyer's Guide • 12 min read

Practice Management Software for Indian Law Firms: DPDP Act, GST and What to Budget

DPDP breach clocks, reverse-charge GST invoices and hosting questions now decide which matter system an Indian firm should buy. Here's what to require, what to budget and how long rollout takes.

SPONSORED CONTEXTUAL PLACEMENT
💼
Evaluating Enterprise Software Deployments in 2026?

Request our confidential total cost of ownership matrix and vendor RFP templates.

Launch Calculator →

Why Indian firms can't simply buy from a global shortlist

Most Indian firms shopping for practice management software in 2026 are replacing the same patchwork: Excel matter trackers, a clerk's cause-list diary, TallyPrime for accounts and WhatsApp for client updates. Whether to move off that patchwork is mostly settled. The harder question is which system passes three India-specific tests that global buyer's guides skip.

First, the software has to support the Digital Personal Data Protection Act, 2023 (DPDP Act) and the DPDP Rules notified in November 2025. Second, its billing module has to produce correct GST invoices for legal services, most of which fall under reverse charge. Third, its hosting and incident-response setup has to work with Indian reporting rules and with the hosting clauses your larger clients write into their contracts.

Advertisement

Global platforms such as Clio and Actionstep are mature at time capture, billing and document workflows. They were built around trust accounting and court calendars in other countries, though. India-built software is often stronger on eCourts case-status tracking, High Court cause lists and Tally export, but it can be thinner on security certifications and integrations.

This guide covers what to require, how costs scale with firm size and how long a rollout realistically takes. It explains how the rules generally work. Your own counsel and chartered accountant should confirm how they apply to your firm.

RECOMMENDED SOLUTION

Looking to streamline vendor RFP selection?

Access pre-negotiated tier discounts through our independent institutional network.

Compare Pricing →

What DPDP compliance looks like inside a matter system

For client, staff and prospect data, your firm is the Data Fiduciary. The software vendor is a Data Processor. Using a vendor doesn't shift accountability, so the system has to make your own obligations easy to meet and easy to prove.

In practice, DPDP compliance for law firms comes down to five capabilities:

  • Notice and consent records. A notice has to stand on its own, itemize the data and purposes in plain language, and be available in English or any language in the Eighth Schedule of the Constitution on request. The intake workflow should store which version of the notice each client saw, with a timestamp and the consent given.
  • Withdrawal that is as easy as consent. If a client can consent through a portal checkbox, they must be able to withdraw the same way. An email to a partner who forgets to update the system doesn't count.
  • Retention schedules per matter. Personal data should be erased once its purpose is served, unless a law requires you to keep it. You need configurable retention by matter type, legal-hold flags and deletion logs. The Rules also expect certain processing logs to be kept for at least a year.
  • Role-based access. Clerks, associates and accounts staff should see only the data their role needs.
  • Verifiable parental consent for children's data. Family, custody and guardianship practices need this.

There's a useful carve-out. Section 17 exempts processing that is necessary to enforce a legal right or claim from most of the consent and notice provisions. That covers much of the opponent and witness data in litigation files. The duty to take reasonable security safeguards still applies, so the exemption reduces paperwork but not security requirements. Have counsel confirm where its limits fall for your practice areas.

Timing matters too. Most substantive obligations take effect 18 months after the Rules were notified, which lands around mid-2027. Any three-year contract you sign now will run well past that date.

Breach duties: the reporting clock your vendor has to beat

Under the DPDP Rules, after a personal data breach the Data Fiduciary must inform each affected person without delay. It must also notify the Data Protection Board without delay and follow up with a detailed report within 72 hours, unless the Board allows more time. Penalties are steep: up to INR 250 crore for failing to take reasonable security safeguards and up to INR 200 crore for failing to notify a breach.

DPDP isn't the only clock. CERT-In's 2022 directions require specified cyber incidents to be reported within six hours of noticing them, and require ICT logs to be kept for 180 days within India. The directions are written broadly, so ask counsel whether and how they apply to your firm. Either way, build the vendor contract around a six-hour alert.

The data processing agreement (DPA) should commit the vendor to the following:

  • An initial alert to you within a stated number of hours of a suspected incident. Push for six or fewer. "Without undue delay" alone isn't good enough.
  • A named incident contact reachable during Indian working hours, and ideally around the clock.
  • Exportable audit and access logs kept for at least a year.
  • A current list of sub-processors, including any OCR, e-signature or AI-assistant providers, with advance notice of changes.
  • Cooperation with forensic investigations, and enough detail for you to tell clients what was exposed.

GST invoicing for legal services: getting reverse charge right

GST on legal services follows rules that most global billing engines don't model by default. When an individual advocate or a firm of advocates supplies legal services to a business entity above the registration threshold, the client pays 18% GST under reverse charge. Legal services are generally exempt when supplied to individuals who aren't acting as a business, to business entities below the threshold, or to another advocate or law firm.

Because of this, many firms that supply only reverse-charge or exempt services aren't required to register for GST at all. Registered firms, often because they make other taxable supplies, must state on the invoice that tax is payable on a reverse-charge basis. Services to clients outside India can qualify as zero-rated exports if conditions such as receipt of payment in convertible foreign exchange are met. Your CA should confirm your registration position and export documentation.

The billing module therefore needs:

  • A tax profile for each client that records whether it is an individual or a business entity, whether it is above or below the threshold, its GSTIN and its state (for place of supply).
  • Invoice templates that switch between the exempt, reverse-charge and export formats, including the required declaration text.
  • Tracking of TDS receivables. Corporate clients typically deduct TDS on professional fees, so you need to reconcile what was deducted against the annual tax statements. The Income-tax Act, 2025 renumbered the provisions from April 2026, so check that the vendor's reports were updated.
  • Ledger export to TallyPrime or Zoho Books, and GST return-ready exports if you are registered.

A simple test catches most weak billing engines. Ask every vendor to produce three sample invoices: one to a large corporate client under reverse charge, one to an exempt individual client, and one to a client in Singapore or the UK.

RECOMMENDED SOLUTION

Looking to streamline vendor RFP selection?

Access pre-negotiated tier discounts through our independent institutional network.

Compare Pricing →

Data localisation in India: required, or just preferred?

The DPDP Act doesn't impose blanket data localisation. Section 16 allows personal data to be transferred abroad unless the government restricts transfers to a particular country by notification. Before signing, check whether any such restriction is in force. On the Act alone, a firm can lawfully use a platform hosted in the EU, UK or US.

Client contracts are a different matter. Banks, NBFCs, insurers and listed companies work under RBI, IRDAI and SEBI outsourcing and cloud rules, and they increasingly pass India-hosting and audit-right clauses down to their law firm panels. Government and public-sector clients may require MeitY-empanelled cloud services.

Hosting in India is easy to get, since the major hyperscalers (AWS, Microsoft Azure, Google Cloud and Oracle) all operate Indian regions. The useful questions concern everything other than the primary database: where backups, logs, search indexes and document previews live, and where support staff connect from.

Our position: if more than about a quarter of your revenue comes from banking, financial services, insurance or government clients, make India hosting a hard requirement. Otherwise, treat it as a strong preference and judge the vendor on its security controls.

Local versus global vendors: where each wins

The vendors named below are examples for a long list, not endorsements. Features change, so confirm current capabilities in a demo.

CriterionGlobal platforms (e.g., Clio, Actionstep)India-built tools (e.g., Provakil; Legistify for in-house teams; Zoho-based builds)
Indian court trackingUsually none native; needs a third-party toolOften native eCourts and High Court cause-list tracking
GST and reverse-charge invoicesNeeds custom templates or a separate billing layerOften built in; test the edge cases anyway
Tally integrationRareCommon
Hosting regionTypically US, EU, UK or Australia; India region uncommonUsually India
Security attestationsSOC 2 / ISO 27001 typicalVaries widely; ask for ISO 27001 or a recent VAPT report
Integrations and APIDeep marketplaces (Microsoft 365, e-signature, accounting)Narrower; check Microsoft 365 and Google Workspace support
Support hoursOften outside IST business hoursIST, often with phone support

For litigation-heavy firms under about 50 lawyers, an India-built tool is usually the better fit. Court tracking and GST billing are daily work, and global tools need extra components to cover them. Corporate and cross-border firms with many international clients tend to get more from a global platform's document, time and integration depth. They should plan for a GST billing layer or a Tally bridge alongside it.

What to budget by firm size

These are typical 2026 market ranges. They vary by contract, user mix and negotiation, so confirm figures with vendors. India-built tools generally cost INR 800 to 3,000 per user per month (about USD 9 to 35). Global platforms generally list at USD 50 to 150 per user per month. Conversions assume roughly INR 88 to the dollar, and the rate moves.

Firm profile (users)Annual subscription: India-builtAnnual subscription: globalOne-time setup and migration
Small practice (3)INR 0.3 to 1.1 lakh (USD 330 to 1,250)USD 1,800 to 5,400INR 0 to 40,000
Boutique (15)INR 1.4 to 5.4 lakh (USD 1,650 to 6,150)USD 9,000 to 27,000INR 1 to 4 lakh
Mid-size (50)INR 4.8 to 18 lakh (USD 5,500 to 20,500)USD 30,000 to 90,000INR 4 to 15 lakh
Large (150)INR 14 to 54 lakh before volume discountsUSD 90,000 to 270,000 before discountsINR 15 to 50 lakh

Two cost drivers catch buyers out. The first is GST on the software itself. Subscriptions carry 18% GST, and a firm that isn't GST-registered can't claim input credit, so that 18% is a real cost. The second is user count. Clerks, paralegals and accounts staff usually need licenses too, so seats often run well above the number of fee earners.

Worked example (hypothetical): Say a 20-lawyer litigation firm in Delhi needs 28 seats. An India-built tool at INR 1,500 per seat per month costs INR 5.04 lakh a year, or about INR 5.95 lakh with GST. Add INR 2.5 lakh for implementation, or about INR 2.95 lakh with GST, and year one comes to roughly INR 8.9 lakh (about USD 10,100). The same firm on a global platform at USD 90 per seat would pay about USD 30,000 a year before GST and before any separate court-tracking or billing add-on.

Rollout timelines and what slows them down

The timelines below are planning ranges, not vendor promises. Your own data quality will move them more than the software will.

PhaseUp to 10 users10 to 50 users50+ users
Requirements and vendor selection2 to 3 weeks4 to 6 weeks8 to 12 weeks
Contract, DPA and security review1 week2 to 4 weeks4 to 8 weeks
Data clean-up and migration1 to 2 weeks3 to 6 weeks6 to 12 weeks
Configuration (GST templates, retention, roles)1 week2 to 4 weeks4 to 8 weeks
Training and parallel run1 to 2 weeks3 to 4 weeks4 to 8 weeks
Typical total4 to 8 weeks3 to 5 months6 to 10 months

Phases overlap, so the totals are shorter than the sum of the rows. Migration is usually what slips. Client records without GSTINs or turnover status, duplicate entries for the same corporate group, hearing dates kept in partners' personal diaries, and Tally ledgers that don't map cleanly to matters all take longer to fix than expected. Assign one person to clean the client tax profiles before migration starts.

Switch billing over at the start of a month, and ideally at the start of the financial year in April. That way, GST and TDS reconciliations never have to span two systems within one period.

Red flags and a shortlisting rule

Drop a vendor, or escalate the issue in negotiation, if you see any of these:

  • It can't say where backups, logs and support access are located.
  • The DPA has no breach-notification deadline, or says only "without undue delay."
  • Invoices have only a GST rate field, with no reverse-charge or exempt format.
  • Court tracking depends on scraping portals, with no fallback or service commitment for when the eCourts or High Court sites change.
  • Full data export in open formats isn't included, or exit fees are charged per gigabyte or per matter.
  • DPDP notice and consent amount to a single checkbox, with no record of versions or withdrawals.
  • A smaller vendor can't show ISO 27001 certification or a recent VAPT report from a CERT-In-empanelled auditor.

Then apply this decision rule. If more than half your billable hours come from litigation in Indian courts, start your shortlist with India-built tools and make the security evidence above mandatory. If more than a third of revenue comes from foreign clients or cross-border transactions, start with global platforms and budget for a GST billing layer or Tally bridge from the start.

Before any demo, send every shortlisted vendor the same five requests: their hosting region for primary data and backups, their breach-alert commitment in hours, three sample invoices (reverse charge, exempt and export), their full-export format, and a walkthrough of how notices, consent and withdrawal are recorded. Vendors that can't answer in writing within a week shouldn't reach the demo stage.

Quick Answers

Does the DPDP Act require us to host client data in India? +
If our firm isn't GST-registered, do we still need GST features in the billing module? +
The main DPDP obligations start around mid-2027. Can we wait before choosing software? +
CT
Claimstack Tech Editorial Team
Independent research desk
Guides on Claimstack Tech are produced by our editorial team. Pricing, features and regulations change often - confirm details with the vendor or a licensed professional before making decisions.
SPONSORED 2026 Vendor Pricing Benchmarks: Model exact seat pricing, setup fees, and ROI across our verified database.
Launch Calculator →