If you're the CFO, COO, or the founder who also handles procurement at a 100- to 500-person Indian company, you've almost certainly signed a SaaS contract without reading it properly. Not because you're careless. Because it's a 40-page PDF drafted in Delaware that arrived at 5 PM on a Friday, and the vendor's sales rep said "it's our standard agreement."
Here's the problem: most SaaS contracts are US-drafted templates with Indian rupee signs pasted in. The TDS treatment is ambiguous. The GST clause is missing. The auto-renewal window is buried in the definitions section. And the data portability right you assumed you had? It's limited to a proprietary export format that no migration tool can read.
SaaS vendor due diligence template SaaS renewals, we've found 12 specific clauses that cost companies lakhs before anyone notices. Some are negotiable. Some aren't. All of them are worth knowing before you sign or — just as importantly — before you renew.
Why Indian SaaS Contracts Are a Different Beast
The standard SaaS Master Service Agreement was written for a US corporate buyer. It assumes a Delaware entity, USD billing, US GAAP accounting, and dispute resolution in a California or New York court. Indian businesses plug into this template as an afterthought, and vendors add a line or two about GST without rethinking the underlying structure.
What that means practically: TDS obligations under Section 194J and Section 195, IGST under the reverse charge mechanism, FEMA compliance on outward remittances, and now DPDP Act 2023 data rights — none of these are addressed in standard vendor paper. Finance teams review these contracts once at signing. Then the renewal machine runs on autopilot, and the same gaps compound year after year.
We've seen this pattern clearly across our customer base. The contracts that cause the most pain aren't the ones with overtly bad terms. They're the ones with missing terms — silence where there should be clarity.
Watch out: If your SaaS contract doesn't explicitly mention TDS treatment, GST responsibility, and data export rights, treat those gaps as active financial and operational risks, not minor omissions.
Red Flags 1–3: The Auto-Renewal Trap
Auto-renewal clauses are the single most expensive thing most Indian SMBs never read. Here's how they actually work in practice.
Clause 1: Silent auto-renewal with a 60–90 day cancellation window. The contract renews automatically unless you send a written cancellation notice at least 60 or 90 days before the renewal date. That window is almost always buried in Section 12 under "Term and Termination," not on the order form where you'd think to look. Miss the window by a week and you're committed for another 12 months.
SaaS auto-renewal price increasestrong> This one is written as a grace note, something like "rates applicable at renewal are subject to change with 30 days' written notice." On its face, reasonable. In practice, it means the vendor can raise prices by 20% and your only options are to accept it or scramble to cancel before the new rate kicks in — which you can't do in 30 days if your cancellation window was 90 days.
exit clause India negotiations exit. You pay the full year upfront on renewal. If you want to leave at month 4, you've already paid for month 12. There's no contractual path to a refund. This isn't illegal. It's just bad procurement to accept it without at least asking for a pro-rata exit right in the first 60 days.
What to push for: mutual written confirmation before any auto-renewal triggers. Most vendors at the ₹5 lakh and above annual contract value will accept this on an enterprise or mid-market agreement. Smaller plans on self-serve tiers are harder to negotiate, but worth asking.
Run a free SaaS spend audit — find every hidden subscription
Key takeaway: Auto-renewal clauses cost Indian businesses lakhs not through bad intent but through missed calendar windows — know every renewal date at least 90 days in advance.
Red Flags 4–5: Price Caps and Escalation Clauses That Aren't There
Clause 4: No cap on year-over-year price increases. Since 2022, US SaaS vendors have raised list prices anywhere from 15% to 40%. If your contract has no explicit price cap, you're exposed to whatever the vendor decides to charge at renewal. Most Indian buyers assume the price they negotiated will hold. It won't, unless it's written down.
Clause 5: "List price at time of renewal" language. This is sneakier. You negotiated a 20% discount off list price at signing. The contract says you renew at "the then-current list price, subject to your applicable discount." What it doesn't say is that the list price itself has gone up 30% since you signed. Your "discount" now applies to a higher base, and you're paying more than you were before.
A negotiated discount on a rising list price is not a stable price. It's a moving target dressed up as a commitment.
The fix isn't complicated: push for a specific percentage ceiling on annual increases — something like "price increases at renewal shall not exceed 5% per year or Indian CPI, whichever is lower." Many vendors will accept 7–10%. The ones who refuse are telling you something worth knowing.
There's also an India-specific amplifier here. If you're paying in USD for a US SaaS tool, currency fluctuation adds to uncapped price increases. A 10% vendor price increase on a $50,000 contract looks like a 14% increase in rupee terms when the dollar strengthens. Your pricing exhibit and order form need to be read together — they frequently contradict each other on whether the quoted amount is fixed or subject to FX adjustment.
Red Flags 6–7: TDS and GST Treatment Left Ambiguous
This is where Indian SaaS procurement differs most sharply from any US benchmark, and where the financial exposure is most concrete.
Clause 6: Contract silent on whether the quoted price is gross or net of TDS. Under Section 194J of the Income Tax Act, payments for professional or technical services to Indian vendors attract TDS at 10%. If your contract quotes ₹12 lakh annually but doesn't specify whether that's the gross amount or the net amount you'll actually transfer, you have a problem. The vendor expects ₹12 lakh. You deduct ₹1.2 lakh as TDS. The vendor receives ₹10.8 lakh and can't reconcile it. Either you gross up the payment or the vendor disputes the shortfall. Neither is pleasant.
Clause 7: GST responsibility clause missing or contradictory. For foreign SaaS vendors with no Indian GST registration, the reverse charge mechanism applies. The Indian recipient (you) is liable to self-assess and remit IGST at 18% on the transaction value. A ₹12 lakh contract becomes ₹14.16 lakh in total compliance cost before you've touched the product. Most contracts don't mention this at all. Some mention GST but attribute responsibility to the vendor, which is incorrect under Indian law for cross-border services.
What finance teams should insist on: explicit gross-up language, a clear statement of who bears Indian tax obligations, a vendor GSTIN (if applicable), and an invoice format that complies with Indian GST rules. If the vendor has an Indian entity, they should be invoicing through it. If they don't, the reverse charge position should be documented in the contract or at minimum in a side letter.
You can also reference our pricing page to see how we handle GST-clean consolidated invoicing for the SaaS your company procures through us — it's one of the concrete things that disappears from your finance team's to-do list.
Action: Before signing any SaaS contract, ask your vendor two questions in writing: "Is the quoted price gross or net of applicable Indian TDS?" and "Who is responsible for IGST under the reverse charge mechanism?" Their answers will tell you more than the contract text.
Key takeaway: Tax ambiguity in SaaS contracts isn't a technicality — a ₹12 lakh deal can quietly become a ₹14+ lakh obligation once TDS grossing and GST reverse charge are accounted for.
Red Flags 8–9: Data Portability and Exit Provisions
Clause 8: No meaningful data export right. The contract says you can export your data. What it doesn't say: the export is a proprietary JSON format that no competing tool imports, or it's only available through an API that requires developer time to use, or the export button generates a file that omits historical metadata. You're technically free to leave. Practically, you're stuck.
Clause 9: Deletion timeline that outpaces export access. This is a structural trap. The vendor's data deletion policy says they purge customer data 30 days after contract termination. The actual export process, documented in a help article no one reads until they're leaving, takes 45–90 days for large datasets. You trigger the termination, the deletion clock starts, and you're in a race you were never told you were running.
The operational cost here isn't just legal. Migration from a locked-in SaaS platform can cost 3–6 months of IT and data engineering time, plus business continuity risk during the transition. That's before you pay the new vendor's onboarding fees.
What good data portability language includes: machine-readable standard formats (CSV, JSON with open schemas), at least 90 days of post-termination read access, no additional fees for data export, and a clear process owner on the vendor side. The Digital Personal Data Protection Act 2023 gives Indian companies a new basis for demanding these terms, even if enforcement is still evolving. Start referencing it in negotiations — vendors' legal teams are aware of it and it shifts the conversation.
If you want to see how vendor contract terms compare across specific tools in your stack, the AI CIO feature surfaces this as part of ongoing vendor management.
Book a 15-minute call to see what's actually in your SaaS stack before the next renewal hits
Red Flags 10–11: Liability Caps and Indemnity Gaps
Clause 10: Vendor liability capped at fees paid in the prior 12 months. This is standard SaaS boilerplate, and it's almost universally accepted without challenge. The problem is the math. You pay ₹3 lakh a year for a data management tool. The vendor has a breach. Your customer data is exposed. Your remediation cost, regulatory exposure under DPDP, and business impact is ₹50 lakh. The vendor's contract liability: ₹3 lakh. The cap is not a negotiation artifact — it's a deliberate architecture to limit vendor exposure.
Clause 11: IP indemnity that protects the vendor, not the buyer. Most SaaS contracts include mutual indemnity language, but the carve-outs are one-sided. The vendor indemnifies you against third-party IP claims arising from the product — unless you modified it, combined it with other software, or used it outside the specified documentation. For a company running integrations across 20 tools, these exclusions cover nearly every real-world scenario.
The practical negotiation posture for a mid-market Indian company: you probably won't move the liability cap much on standard enterprise terms. What you can do is require the vendor to carry cyber liability insurance and provide a current certificate of coverage. It doesn't increase your contractual recovery, but it signals that actual recoverable funds exist behind the cap. For vendors handling sensitive customer data, this is a minimum bar.
Action: For any SaaS tool handling customer PII or financial data, request a current cyber liability insurance certificate as a condition of signing. If the vendor can't produce one, factor that into your risk assessment — not just your legal review.
Red Flag 12: Governing Law and Dispute Resolution Clauses
Clause 12: Exclusive jurisdiction in Delaware or California courts. For an Indian SMB with a ₹10–30 lakh annual SaaS contract, litigating a dispute in a US federal court is not a realistic option. The legal costs alone would exceed the contract value in the first month. Vendors know this. Exclusive US jurisdiction is effectively a dispute-resolution waiver for any Indian company that can't afford a US litigation budget.
What to push for: international arbitration with a seat in India. SIAC (Singapore International Arbitration Centre) with Delhi as the seat is increasingly accepted by US SaaS vendors. DIAC (Delhi International Arbitration Centre) works for India-based vendors. If the vendor insists on ICC rules, push for ICC arbitration with a Delhi seat rather than US courts. Arbitration clauses are the most commonly negotiated element of SaaS MSAs — vendors expect this conversation and most mid-market deals can be moved.
The practical reality: most SaaS disputes between Indian buyers and US vendors are resolved through non-renewal, chargebacks, or escalation to account management, not litigation. So prioritize your negotiating energy accordingly. Fix the auto-renewal clause, the tax treatment, and the data portability terms first. Governing law matters but it's often the last resort in a situation where the relationship has already failed.
Key takeaway: Exclusive US jurisdiction in a SaaS contract isn't just a legal technicality — it's a practical bar on enforcing your rights, and most vendors will negotiate it if you raise it early.
A Review Checklist Before You Sign (or Renew)
Here's how to prioritize the 12 flags by financial risk.
- Auto-renewal window (Clause 1): Find the exact date and set a 90-day calendar alert. Non-negotiable to track.
- Price increase at renewal (Clause 2): Cap it at a fixed percentage or CPI. Negotiable on mid-market plans above ₹5 lakh.
- Annual commitment billing (Clause 3): Request a pro-rata exit window in the first 60 days. Often accepted quietly.
- Price escalation cap (Clause 4): Must be explicit. No cap means no budget predictability.
- "List price at renewal" language (Clause 5): Ask for a fixed discount off a fixed base price, not a percentage off a floating list.
- TDS gross-up language (Clause 6): Get a written confirmation of whether quoted price is inclusive or exclusive of TDS before signing.
- GST reverse charge responsibility (Clause 7): Document who handles IGST filing. Should be in the contract or a side letter.
- Data export format (Clause 8): Require machine-readable standard formats, not proprietary exports.
- Post-termination data access (Clause 9): Minimum 90 days. No ransom fees. Written into the agreement.
- Liability cap (Clause 10): Accept it for standard tools. Require cyber insurance certificates for data-sensitive tools.
- IP indemnity carve-outs (Clause 11): Read what's excluded. Integration and modification carve-outs are common; understand your exposure.
- Governing law and arbitration (Clause 12): Push for India-seated arbitration. Most vendors will move on this.
On role clarity: contract review shouldn't land on one person. Finance owns TDS and GST treatment. Legal owns indemnity and governing law. IT procurement owns data portability and exit provisions. If one team signs without the others' input, at least one of these gaps will slip through. Renewal reviews deserve the same scrutiny as initial contracts — but because auto-renewal kills the urgency, they rarely get it.
What We Do Differently at Easexpense
We sit inside the payment layer. That means we see renewal charges hit before most finance teams open their email. Our renewal alert engine fires at 90, 60, and 30 days out — which gives you actual time to review a contract rather than a 72-hour scramble after a charge lands on the corporate card.
Our vendor partnerships with Microsoft, Google, AWS, Slack, and Zoho aren't just about price. Negotiated terms are part of the relationship — which means several of the red flags we've described above are pre-cleared in the agreements we've already worked through with anchor vendors. You inherit better contract terms, not just a better rate.
On the GST and TDS problem specifically: because we're the procurement intermediary, your invoices flow through our entity with clean GST-compliant formatting. The reverse charge ambiguity, the missing GSTIN, the gross-vs-net TDS question — these stop being your problem to solve contract by contract. You get one consolidated invoice with correct tax treatment built in.
If you don't know which SaaS contracts are renewing in the next 90 days, or what you're actually paying across your stack, the fastest place to start is a free SaaS spend audit. It scans your work inbox, surfaces every recurring subscription, and shows you renewal dates and amounts in one view. No manual data entry. Takes about 30 seconds to connect. Run the audit here.
Frequently asked questions
What is the standard TDS rate on SaaS payments in India?
SaaS subscription fees paid to Indian vendors are typically subject to TDS under Section 194J at 10% if the payments qualify as professional or technical services. For payments to foreign SaaS vendors, the applicable rate under Section 195 depends on the Double Taxation Avoidance Agreement (DTAA) between India and the vendor's country of residence — rates vary significantly, and some treaties bring the effective rate down to 10–15% on royalties or fees for technical services. The contract should explicitly state whether the quoted price is gross (inclusive of TDS deduction) or net (the amount you'll actually transfer), because ambiguity here creates reconciliation disputes between buyer and vendor. Finance teams should confirm TDS applicability with their tax advisor before signing, not after the first invoice arrives.
Can I negotiate auto-renewal clauses with large SaaS vendors?
Yes, more often than buyers assume. Enterprise and mid-market tiers of most major SaaS vendors will accept a mutual written-confirmation requirement before auto-renewal triggers, particularly on annual plans above ₹5 lakh. The key is raising the issue during initial contract negotiation, not 30 days before renewal when you have essentially no leverage and the vendor knows it. The specific language to request is something like: "Neither party's renewal obligation shall activate without written confirmation from both parties no less than 30 days prior to the renewal date." Some vendors also accept an opt-out window extension — changing a 60-day cancellation notice to 30 days — which meaningfully reduces the risk of missing the window in practice.
What does data portability mean in a SaaS contract, and why does it matter for Indian companies?
Data portability refers to your contractual right to export your company's data in a format that's actually usable when you leave a SaaS platform. Contracts that restrict export to proprietary formats, or give you only 30 days post-termination to retrieve data, create effective vendor lock-in regardless of what the termination clause says about your freedom to leave. For Indian companies, this is increasingly relevant under the Digital Personal Data Protection Act 2023, which gives data principals certain rights over their personal data that your vendor contracts should begin to reflect. Migration costs from a poorly documented or export-restricted platform can easily run into months of engineering time and significant business continuity risk — the financial exposure is real, not theoretical.
Who is liable for GST on imported SaaS services under the reverse charge mechanism?
Under Indian GST rules, when a registered Indian business receives services from a foreign vendor — such as a US-based SaaS company with no Indian GST registration — the Indian recipient is liable to self-assess and remit IGST under the reverse charge mechanism. The applicable rate is typically 18% on the transaction value, which the Indian company must pay directly to the government and report in its GST returns. The foreign vendor cannot collect this GST on your behalf, and many SaaS contracts are entirely silent on this obligation, leaving finance teams to calculate and remit independently without clear guidance in the agreement. Companies that miss reverse charge compliance face interest and penalty exposure, not just the unpaid tax.
How do I find out which SaaS contracts are up for renewal in the next 90 days?
Most companies don't have a clean answer to this question. Renewal dates are scattered across email inboxes, credit card statements, individual team members' calendars, and sometimes nowhere documented at all. The fastest path to visibility is running a SaaS spend audit that scans your work email for recurring subscription invoices and confirmation emails — this surfaces renewal dates, amounts, and the tools involved in a single consolidated view without requiring manual data entry from every team. Once you have that baseline, setting 90-, 60-, and 30-day calendar alerts for each renewal date is straightforward. The problem isn't usually tracking renewals after you know about them; it's finding the ones no one in finance knows exist.
What governing law should Indian SMBs negotiate for in SaaS contracts?
Ideally, push for Indian law with arbitration seated in India under SIAC, DIAC, or ICC rules with a Delhi seat. If the vendor insists on US governing law, the practical priority is getting international arbitration rather than US federal or state court jurisdiction, since litigating in Delaware is cost-prohibitive for most Indian mid-market companies. Many vendors will accept this change while holding firm on pricing and product terms, because their standard contract position on US courts is more about template inertia than a hard business requirement. Include a clear notice requirement and an escalation ladder (account management escalation before any formal dispute process triggers) — in practice, most SaaS disputes are resolved through relationship management, not formal proceedings.
Is there a standard SaaS contract review checklist for Indian startups?
There's no single industry-standard checklist, but the critical areas to review in order of financial exposure are: auto-renewal and cancellation windows, price escalation caps, TDS and GST treatment, data portability and deletion timelines, liability and indemnity limits, and governing law. Indian startups often miss the tax clauses entirely because they're reviewing US-drafted templates without a finance lead in the room during procurement, and the compliance implications of Section 194J, Section 195, and reverse charge GST aren't obvious from the contract text if you don't know to look for them. A practical starting point is getting visible on every SaaS tool and its renewal date — from there, you can stage contract reviews by financial exposure rather than trying to review everything at once.